IBM App Connect Deployment

To use the to deploy the fragmentation sample application on the IBM App Connect Enterprise, you need to have an instance of the at version 8.0 or higher.

Import the core FTM projects (found in the FXH_Core_Projects_WMB_PI.zip file) and the FTM Generic Model Actions project (found in the FXH_GenericModel_WMB_PI.zip file) into an workspace.

Import the FTM Sample App ISF V3 project (found in FXH_Sample_PI.zip) from the sample application.

Note: If the full sample application is imported into the workspace, when you import the fragmentation sample application in the next step you receive a warning message that the common "FTM Swift MT Flows finsample" project already exists.

Import the fragmentation sample application (found in FXH_Fragment_Sample_PI.zip).

The main components that must be deployed to IBM App Connect is shown in the following figure.

The FTM Fragmentation Sample project contains five prebuilt broker archive (BAR) files that include all of these components.

Each BAR file should be rebuilt before deployment for the following reasons:

To ensure that the code that is loaded into the workspace matches with the requirements of the BAR files.
To ensure that any core updates that were applied are included in the BAR files.
To remove the possibility of any IBM App Connect Toolkit compatibility issues. This is not expected to be an issue and is a precaution only.
To check that the IBM App Connect Toolkit is able to build each BAR file.

The initial configuration of the BAR files should match with the configuration in the installation scripts. If configuration changes are required before deployment, be aware that some BAR file changes might require the configuration scripts to be changed. Common configuration changes associated with the message flows are:

application name
application version
data source names
database schema
queue names

If you are not using the defaults, you must check that the values are correct for all of the flows in the application.

Notes:

If these default properties are changed, ensure that the Override configurable property values check box is cleared before rebuilding each BAR file.
Only the flow components in the previous figure can be configured (in their respective BAR files) in the BAR file editor before deployment.

After you rebuild a BAR file, you must save it before deployment.

If you are deploying from the IBM App Connect Toolkit, you must be connected to a broker instance. You can do this by selecting an existing broker instance in the Brokers tab of the IBM App Connect Toolkit. This needs to have at least one running execution group (you might need to create an execution group if a suitable one does not exist). As the application is divided across multiple BAR files, it can be deployed across multiple execution groups. It is recommended to have more than one execution group. In either case, it is important to deploy the message sets to any execution group that requires them, before deploying other resources, flows, wrappers, and so on.

To deploy the application, drag each required BAR file to the appropriate running execution group.