Migrating an SAP integration flow

Migrate an SAP integration flow that runs on IBM® Integration Bus Version 10.0 or Version 9.0 to IBM App Connect Enterprise Version 11.0.

About this task

The following steps describe how to create an SAP integration flow in IBM Integration Bus Version 10.0 or Version 9.0, then how to migrate it to IBM App Connect Enterprise Version 11.0. The steps describe two different migration options: migrating to an integration node or an independent integration server. This scenario uses an SAP outbound adapter as an example; the same steps apply to an inbound adapter.

Procedure

Creating an SAP integration flow in IBM Integration Bus Version 10.0 or Version 9.0

Procedure

  1. In IBM Integration Bus Version 10.0 or Version 9.0, create an SAP outbound adapter to fetch BAPI_BANK_GETDETAILS.
    1. In the IBM Integration Toolkit, click File > New > Adapter connection, then follow the instructions in the wizard.
    2. For service discovery, select RFC and set a filter to find objects for BAPI_BANK_*.
      Screenshot shows the Adapter Connection wizard where RFC has been selected.
    3. For the the BAPI_BANK_GETDETAIL configuration parameters , select the objects to import.
      Screenshot of Adapter Connection wizard showing optional export parameters selected.
      Screenshot of Adapter Connection wizard showing that the BAPI_BANK_GETDETAIL object is selected to be imported.
    4. Configure the objects.
      Screenshot of Adapter Connection wizard showing the Configure Objects page.
      Screenshot of Adapter Connection wizard showing service generation and deployment configuration.
  2. Create a simple SAP application to fetch BAPI BANK GETDETAILS.
  3. Configure the integration node with SAP JCo libraries by using the mqsichangeproperties command. 
    mqsichangeproperties IIBNODE -c EISProviders -o SAP -n jarsURL -v C:\SAP_JARS
mqsichangeproperties IIBNODE -c EISProviders -o SAP -n nativeLibs -v C:\SAP_JARS
    You can verify that the properties are set up correctly by running the command: mqsireportproperties IIBNODE -c EISProviders -o SAP -r
    Screenshot of the result of the mqsireportproperties command, showing the location of SAP JCo libraries.
  4. Deploy the resources to the integration server.
    Screenshot showing the SAP adapter resources deployed under the integration node.
  5. Create a configurable service for the SAP adapters connection.

    By using a configurable service, you can change the host name that is set in the adapter file without needing to redeploy the resources.

    1. Use the SAPConnection configurable service to change connection details for an SAP adapter. 
      mqsicreateconfigurableservice IIBNODE -c SAPConnection -o SAP_BAPI_BANK_GETDETAILS_OUT.outadapter -n applicationServerHost,client -v wmbsap.hursley.ibm.com,001
    2. To display all SAPConnection configurable services, use the mqsireportproperties command: 
      mqsireportproperties IIBNODE -c SAPConnection -o AllReportableEntityNames -r
      Screenshot showing the console output from the mqsireportproperties command.

Migrating an IBM Integration Bus Version 10.0 or Version 9.0 integration node to an IBM App Connect Enterprise Version 11.0 integration node

Procedure

  1. Back up the IBM Integration Bus Version 10.0 or Version 9.0 integration node by using the mqsibackupbroker command. 
    mqsibackupbroker IIBNODE -d C:\SAP_JARS
  2. Migrate the IBM Integration Bus Version 10.0 or Version 9.0 integration node and resources to IBM App Connect Enterprise Version 11.0 by using the mqsiextractcomponents command. 
    mqsiextractcomponents --source-integration-node IIBNODE --target-integration-node ACENODE --backup-file "C:\SAP_JARS\IIBNODE_190712_083247"

    This mqsiextractcomponents command creates a new integration node and integration server. If the integration node already exists, the mqsiextractcomponents command fails unless you specify –delete-existing-node. In this case, the existing integration node is deleted and a new integration node is created with the same name.

    All deployed resources are migrated under the /run directory of the created integration server. For example, on Windows: C:\ProgramData\IBM\MQSI\components\IntegrationNode\servers\IntegrationServer.

    During migration, the IBM Integration Bus Version 10.0 or Version 9.0 configurable services are converted to policies in IBM App Connect Enterprise Version 11.0. You can find the policy project in the integration node work directory. If you do not specify a policy project name, policies are created in a policy project called DefaultPolicies. The policy file that is created has the same name as the adapter.

  3. Start the IBM App Connect Enterprise Version 11.0 integration node by running the command mqsistart ACENODE.
    The application and policy files are listed under the IBM App Connect Enterprise Version 11.0 node in the Toolkit. You can confirm the location of the migrated JAR files by running the mqsireportproperties command on the IBM App Connect Enterprise Version 11.0 node. 
    mqsireportproperties ACENODE -c EISProviders -o SAP -r
  4. Test the integration flow by sending a message to fetch the record for BAPI BANK GETDETAILS.
    The following example shows the expected output message.
    Screenshot showing the expected output message for BAPI BANK GETDETAILS.

Migrating an integration flow from an IBM Integration Bus Version 10.0 or Version 9.0 integration node to an IBM App Connect Enterprise Version 11.0 independent integration server

Procedure

  1. Migrate an IBM Integration Bus Version 10.0 or Version 9.0 integration server to an IBM App Connect Enterprise Version 11.0 independent integration server by running the mqsiextractcomponents command. 
    mqsiextractcomponents --source-integration-node IIBNODE --source-integration-server default --target-work-directory "C:\temp\ACESIS" --backup-file "C:\SAP_JARS\IIBNODE_190712_083247.zip"
    If the work directory already exists, the mqsiextractcomponents command fails unless you specify –clear-work-directory. In this case, the configuration and resources are written to the work directory, and overwrite any data that might be present in the directory.
  2. Start the IBM App Connect Enterprise Version 11.0 integration server by running the IntegrationServer command. 
    IntegrationServer --name default --work-dir C:\temp\ACESIS

    All deployed resources are migrated to the /run subfolder in the work directory of the independent integration server.

    During migration, the values that are set by using the mqsichangeproperties command in IBM Integration Bus Version 10.0 or Version 9.0 are added to the server.conf.yaml file in the /overrides subfolder in the work directory of the IBM App Connect Enterprise Version 11.0 integration server.

    Also during migration, the IBM Integration Bus Version 10.0 or Version 9.0 configurable services are converted to policies in IBM App Connect Enterprise Version 11.0. You can find the policy project in the /run subfolder of the work directory for the integration server. If you do not specify the policy project name, policies are created in a policy project called DefaultPolicies. The name of the policy file that is created is the same as the adapter.

    The application and policy files are listed under the IBM App Connect Enterprise Version 11.0 integration server in the Toolkit.