Migrating IBM Business Automation Workflow (BAW) from 8.5.7 to 21.0.3: A Transition from DB2 to Oracle and AIX to Linux

Migrating IBM Business Automation Workflow (BAW) from an older version (8.5.7) to a newer one (21.0.3) is an important step in modernizing enterprise processes.

This migration, however, comes with its own set of complexities, especially when considering a shift not only from an older version of BAW but also when transitioning the database from DB2 to Oracle, and moving the entire system from AIX to Linux. In this blog, we'll walk through the challenges and best practices for successfully migrating IBM BAW to version 21.0.3, making the switch from DB2 to Oracle, and moving from AIX to Linux.

Why Migrate IBM BAW to Version 21.0.3?

IBM BAW 21.0.3 brings a host of new features, including better cloud integration, more flexible architecture, and improved user interface and performance optimizations. However, a migration to this version is not just about installing the latest version; it's also an opportunity to update your infrastructure and enhance the underlying technologies. This migration brings several benefits:

• Improved Performance and Scalability: IBM BAW 21.0.3 offers better performance and more efficient scaling capabilities compared to older versions.
• Cloud-Readiness: With growing adoption of cloud-based infrastructure, version 21.0.3 has enhanced support for containerization and cloud environments like Kubernetes and Docker.
• AI and Automation Features: New machine learning capabilities, improved automation, and advanced analytics are part of the BAW 21.0.3 release, which can help you modernize your workflows.

The migration, however, needs careful planning, particularly when considering the platform and database changes.

For this scenario, we are also considering the migration from DB2 to Oracle Database, and transitioning from AIX OS to Linux.

Migration Path Overview

The migration path from IBM BAW 8.5.7 to BAW 21.0.3 involves several key steps:

1. Setting Up a New Environment with Oracle and Linux
2. Data Migration from DB2 to Oracle
3. Upgrading Process Models and Application Configurations
4. Testing and Validation
5. Go-Live and Post-Migration Activities

Let's dive deeper into each of these stages.

---

1. Setting Up a New Environment with Oracle and Linux

Moving from AIX to Linux

Moving from AIX (IBM's Unix operating system) to Linux is one of the biggest challenges in this migration. Linux is the preferred platform for most modern applications, including cloud-based deployments. IBM BAW 21.0.3 also has enhanced support for Linux, which makes this shift beneficial for performance, cost-efficiency, and future scalability. However, there are several important considerations:

• Hardware and Virtualization: If your existing AIX system is running on proprietary IBM hardware (e.g., Power Systems), you will need to ensure that the target Linux environment is sufficiently powerful. You may be moving to x86 architecture or a virtualized Linux environment running on VMware or public cloud platforms.

• Software Dependencies: Many software components in IBM BAW 8.5.7 may rely on AIX-specific libraries. Transitioning to Linux requires identifying any custom or third-party software dependencies and ensuring they are available or compatible with Linux.

• Environment Setup: After moving to Linux, install the necessary tools for IBM BAW 21.0.3:

  • Java Development Kit (JDK): IBM BAW 21.0.3 requires Java 11, so ensure that your Linux system has the appropriate JDK installed.
  • WebSphere Application Server (WAS): IBM BAW relies on WebSphere for runtime environments. You need to install and configure WebSphere Application Server (WAS) on your Linux system.
  • Docker/Kubernetes: If your new BAW deployment is going to be containerized, ensure that Docker and Kubernetes are set up on the Linux machine.

Oracle Database Setup

Since you're migrating from DB2 to Oracle, the first step is to install Oracle Database 19c (or any compatible version). Oracle Database has strong enterprise-level features and support, which makes it ideal for the requirements of IBM BAW 21.0.3. You need to:

• Install Oracle Database: Set up Oracle Database on a Linux system and create a new schema for IBM BAW. Follow the IBM BAW 21.0.3 documentation for Oracle-specific database configurations.

• Configure Database Tablespaces: Oracle and DB2 differ in terms of schema and tablespace management. Ensure that tablespaces are configured correctly for IBM BAW. IBM provides detailed documentation for Oracle database configuration, including setting up the necessary tablespaces for workflow, process, and audit data.

• JDBC Configuration: Ensure the JDBC connections are set up properly in IBM BAW to interact with Oracle. This includes updating the jdbc.properties and dataSource.properties files.

---

2. Data Migration from DB2 to Oracle

Migrating data from DB2 to Oracle is one of the most critical and time-consuming aspects of this process. These two database systems use different technologies, so a direct migration is rarely possible without adjustments.

Data Migration Tools

• IBM Data Migration Assistant (DMA): IBM provides tools like DMA to help facilitate the migration of data between DB2 and Oracle. DMA can help analyze your current schema in DB2 and provide recommendations for migrating to Oracle.

• Oracle GoldenGate: If you're dealing with large datasets or need minimal downtime, Oracle GoldenGate can be used to replicate data from DB2 to Oracle in real time. This is particularly useful for high-availability environments.

Schema and Data Type Conversion

• Schema Differences: DB2 and Oracle have different ways of managing data types, constraints, and indexing. For instance:
  • Character Sets: DB2 and Oracle use different default character sets, so you may need to convert text columns appropriately.
  • Data Types: DB2's DATE and TIME types might need to be mapped to Oracle's DATE or TIMESTAMP.
  • Stored Procedures and Triggers: If your DB2 environment relies on stored procedures or triggers, these will need to be converted into Oracle-compatible PL/SQL code.

Testing Data Integrity

After migrating the schema and data, it's crucial to test the integrity of the data. Ensure that no data is missing or corrupted during the migration process. You should also compare query execution times between DB2 and Oracle to ensure that performance is not negatively impacted.

---

3. Upgrading Process Models and Application Configurations

Once the database and OS migrations are complete, the next step is migrating your IBM BAW configurations.

• Upgrading Process Models: IBM BAW 21.0.3 offers new features and enhancements in process management, and some older models created in BAW 8.5.7 may need to be upgraded. IBM provides migration tools to help upgrade process models and business workflows.

• Custom Extensions and Integrations: Custom integrations or extensions developed in earlier versions of IBM BAW may require refactoring to ensure compatibility with BAW 21.0.3. Any custom scripts, APIs, or third-party integrations should be tested and updated as necessary.

• UI Changes: The user interface may have changed in IBM BAW 21.0.3, so the new version may require adjustments to your UI configurations.

---

4. Testing and Validation

Testing is one of the most critical parts of this migration. It's important to thoroughly validate the entire system before going live:

• Functional Testing: Ensure that all workflows, process models, and user interactions function as expected.
• Performance Testing: Oracle and Linux may perform differently compared to DB2 and AIX. Conduct performance testing to ensure the system can handle the expected workload.
• Regression Testing: Run regression tests to ensure that all legacy workflows and integrations are still functioning correctly.
• Database Testing: Validate that the data migration is successful, with no discrepancies between DB2 and Oracle, and that performance is optimized.

---

5. Go-Live and Post-Migration Activities

Once testing is complete, you can plan the cut-over to the new IBM BAW 21.0.3 system. Depending on your organization's requirements, this can be done in phases, or as a full-scale migration:

• Monitoring: Keep a close eye on system performance, especially during the early days after going live. Monitor the logs for errors or performance bottlenecks.
• User Training: If there are changes to the user interface or workflow, ensure that users are trained on how to use the new system.
• Backup and Disaster Recovery: Set up reliable backup and disaster recovery plans for your new Linux-based, Oracle-backed IBM BAW environment.

---

Conclusion

Migrating IBM Business Automation Workflow from 8.5.7 to 21.0.3, moving from DB2 to Oracle, and transitioning from AIX to Linux represents a significant change for any organization. It involves careful planning, a systematic database and application migration approach, and a thorough testing phase. By following best practices and leveraging the right tools, organizations can ensure a smooth transition, enabling them to take full advantage of the advanced features offered in BAW 21.0.3. Despite the complexities, this migration can modernize your infrastructure and position your organization for success in the digital

------------------------------
Mohammed Ghazali
------------------------------