Aix installation and migration

However, the differences in syntax and directory structure must be addressed during migration for an application to function properly. RISC and x86 processors differ in endianness , a term used to describe how a system stores bytes in computer memory. This is a fundamental difference but consistent across systems, so when transferring application data from one system to another, you can convert the data.

The application type, Java-based or native, dictates the approach to migration for each category of software—that is, commercial off-the-shelf COTS or custom open source.

When Java applications are compiled, the result is Java bytecode, a machine-independent representation that runs in a Java virtual machine JVM. These applications are portable, because the JVM provides a level of application abstraction. The next thing to consider when migrating is the data. Fortunately, data portability is typically more flexible. You can migrate data from one database platform to another in several ways as described in the next section.

Note: Like Java, other application runtimes create a compiled version that can be migrated to Azure using the same methodology. Applications that do not run in a JVM or another application virtualization environment compile to native executables. These types of executables vary based on the CPU platform and run directly within the operating system. Native AIX applications do not run on the x86 platform. You must recompile them, which implies that you need the source code.

The other component of any application is the data tier. You can install the target database platform on Linux, and then port the data using any of a variety of data migration tools. This option is a good choice when your database includes stored procedures and triggers.

Even if you cannot migrate your database typically because of a dependency on the AIX system , some of the data can stay on AIX, and the application tier on Azure can integrate with it. Also known as packaged solutions, these are applications that are purchased from a software vendor and installed on the AIX system. This category of application typically does not have the source code, because it is proprietary IP owned by the software vendor, as is the case with most PC software.

You rely on the software vendor for upgrades, new features, enhancements, and bug fixes. Assuming you have the source code for your open source and custom applications, you have more flexibility and options for migrating native applications. For open source and custom Java-based applications, you can use the same approach as with COTS applications. Another option that became available in October is Azure Spring Cloud. This fully managed service allows you to run Java-based application in a cloud-native Java environment.

You can then move beyond a traditional VM deployment to a more flexible and agile microservices architecture. When you are migrating applications from AIX to Linux on Azure VMs, it can be very helpful to know if the application you are migrating is already available in a Linux version. Many are. This can be very beneficial in helping you decide the approach to take. Moving AIX workloads to the cloud can be a significant step toward datacenter modernization.

Depending on the types of applications you have in your AIX estate, you can use a number of approaches for migration to Azure. The goal is to minimize effort and mitigate risks on the way to gaining the cloud benefits that Azure provides, such as flexibility and scalability. For more information about migrating applications to Azure, see Azure migration center: Linux migration. You must be a registered user to add a comment.

If you've already registered, sign in. Otherwise, register and sign in. Products 72 Special Topics 41 Video Hub Most Active Hubs Microsoft Teams. Security, Compliance and Identity. Microsoft Edge Insider. Azure Databases. Autonomous Systems.

Education Sector. Microsoft Localization. Microsoft PnP. Healthcare and Life Sciences. Internet of Things IoT. Enabling Remote Work.

Small and Medium Business. Humans of IT. Green Tech. MVP Award Program. Video Hub Azure. Your system must have at least megabytes Mbytes of memory and. The following mainframe rehosting components have been qualified with Sun MTP 8. Documentation Advisory The documentation set shipped with this release contains information that does not apply to AIX platforms.

Some of this information relates to products or functionality that is not supported on the AIX platform. Other information is specific to the use of the product on Solaris platforms. These release notes contain general information that applies to all platforms on which the Sun MTP software operates. It also contains information that is applicable only to AIX environments.

Therefore, refer to this document if you are in doubt about whether a feature operates the same on Solaris and AIX platforms. When the term user is used in the documentation, it typically means a session. A single person who is a user could have multiple sessions. Because each user consumes Sun MTP session resources, set this field based on your region's requirements for terminals, printers, and intersystem communications ISC sessions.

To create the license file for the Sun MTP product, follow the instructions in the software enabling key letter that you receive from Sun Microsystems, Inc. Do not follow the license file instructions in the Sun Mainframe Transaction Processing Software Installation Guide , because they apply only to Solaris platforms.

The kixcnvtcat80 utility is used to convert the catalog, and the kixcnvtbl80 utility is used to convert the tables.