Migrating deployable resources

You can continue to use existing resources in IBM® App Connect Enterprise. However, if you want to continue developing resources created in previous versions, you must migrate them.

About this task

The following table summarizes the type of resource that you must migrate into IBM App Connect Enterprise 13.0 if you want to continue developing them.
Table 1. Existing resources that require extra migration tasks
Resource to continue developing in Version 13.0 Resource that is created in Version 10.0
Message sets You must enable the menus for message set development (see Migrating message sets).
Message maps You must complete the migration of message maps to graphical data maps for those existing message maps that you did not convert when you migrated to Version 10.0. New maps that are created in Version 10.0 are graphical data maps. See Migrating message maps.
Message flows If your message flows include message flow nodes that are no longer available, rework your message flows to use available message flow nodes. See Migrating message flows.
Subflows You must complete the migration of the existing subflows that you did not convert when you migrated to Version 10.0. New subflows that are created in Version 10.0 are created as .subflow files. See Migrating subflows.
Custom integration applications If you have applications that use the IBM Integration API, check that they access the correct resources. See Migrating custom integration applications.

Migrating message sets

About this task

Platform-independent message sets were introduced in WebSphere® Message Broker Version 6.0. If the integration node backup file contains a message set from a release earlier than Version 6.0, the message set is not extracted; such message sets are platform-specific. Redeploy the BAR files containing such message sets or rebuild the message set or BAR file so that it is platform-independent.

In IBM App Connect Enterprise, message model schema files contained in applications, integration services, and libraries are the preferred way to model messages for most data formats. Message sets are required if you use the MRM or IDOC domains. For more information about message modeling, see Message modeling concepts.

You can import message flows that contain message sets from previous versions into IBM App Connect Enterprise 13.0. Your existing message sets can be viewed, modified, and deployed in the usual way. However, by default, the menu options for creating new message sets or message definition files are hidden. To complete these tasks, you must first enable message set development in the IBM App Connect Enterprise Toolkit Preferences. For more information, see Enabling message set development.

Migrating message maps

About this task

IBM App Connect Enterprise 13.0 includes a graphical data mapping capability, which is used when you add a Mapping node to a message flow.

You can import message flows containing the following nodes, which use message mapping into IBM App Connect Enterprise 13.0:
  • DataDelete
  • DataInsert
  • DataUpdate
  • Extract
  • Mapping
  • Warehouse

The message map (.msgmap) on these nodes can be viewed but they cannot be deployed to the runtime environment because they are not available in IBM App Connect Enterprise 13.0. The message-mapping operations from previous versions are accessible only in read-only mode and cannot be modified or deployed.

To deploy a message flow that uses an existing message map (.msgmap file), you must first replace the existing node with a new Mapping node. You must also convert the existing message map to a graphical data map that can be used by the new Mapping node (.map file). For more information, see Converting a message map from a .msgmap file a .map file.

Migrating message flows

About this task

The message flow nodes that are available in IBM App Connect Enterprise 13.0 might be different from the nodes that are available in the version from which you are migrating. If your message flows contain message flow nodes that are no longer available, you must rework them to use only those message flow nodes that are available at IBM App Connect Enterprise 13.0.

Migrating subflows

About this task

Since WebSphere Message Broker Version 8, you create subflows as .subflow files.

Subflows from earlier versions of the product were created as .msgflow files. You must convert them into .subflow files if you want to continue developing them in IBM App Connect Enterprise 13.0. You convert these subflows by using the function Convert to subflow. For more information, see Converting between message flows and subflows.

Migrating custom integration applications

About this task

Your existing Version 10.0 custom integration applications can be migrated to work with Version 13.0 integration nodes. However, if you are writing new applications, ensure that you use the com.ibm.integration.admin.proxy.* classes rather than the deprecated com.ibm.broker.proxy.*.

The IBM Integration API is no longer asynchronous because it is backed by synchronous REST calls. As a result, the AdministeredObjectListener framework is no longer available, and no processModify(), processDelete() callbacks exist. You must call refresh on the proxy objects to get the latest property values, such as for the deprecated Execution Group Proxy myExecutionGroupProxy.refresh().

Procedure

  1. For custom integration applications that connect to an integration node, update the connection details that are used by your custom integration applications to connect to the appropriate integration node.

    In IBM App Connect Enterprise 13.0, the IBM Integration API connections are no longer dependent on IBM MQ, and so connections are no longer made by using IBM MQ queues.

  2. If you are connecting to a remote integration node, update your connection details to use the web administration port. For more information, see Configuring the IBM App Connect Enterprise web user interface.
    For information about using SSL on these connections, see Connecting to an integration node by using the Toolkit. If you are connecting to a local integration node, you can use a direct local connection.
  3. If administration security is enabled, in IBM App Connect Enterprise 13.0, user credentials are needed by integration applications that use a remote connection. If the connection is local, you must run the application under a user ID that is part of the mqbkrs group. For new integration applications, you can provide user details during application development. For existing compiled applications, you must supply the security credentials by using one of the methods that is described in Connecting to an integration node from a custom integration application.