IBM App Connect Enterprise Deployment
To deploy the ODM integration sample application, you need to have an instance of the WebSphere® Message Broker Toolkit (V8.0 or later) or the bundled IBM App Connect Enterprise V9.0. Ensure that the Core FTM projects (found in the FXH_Core_Projects_WMB_PI.zip file) and FTM Generic Model Action project (found in the FXH_GenericModel_WMB_PI.zip file) are installed in a workspace on your IBM App Connect Toolkit instance. The projects from the ODM integration sample application (found in FXH_Rules_Driven_Sample_WMB_PI) must be installed in the same workspace as the core FTM projects. The following figure shows the main components that must be deployed to IBM App Connect Enterprise.
The FTM ODM Integration Sample Bar files project contains four prebuilt broker archive (BAR) files that include all these components.
- 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 issue is not expected to be a problem and is recommended as a precaution only.
- To check that the IBM App Connect Toolkit is able to build each BAR file.
- Application name
- Application version
- Data source names
- Database schema
- Queue names
Deployment notes
Only the flow components in Figure 1, in their respective BAR files, can be configured in the BAR file editor before deployment.
When you rebuilt a BAR file, you must save it before deployment.
If you are deploying from IBM App Connect Toolkit, you need to be connected to a broker instance. You can connect by selecting an existing broker instance in the Brokers tab of IBM App Connect Toolkit. The instance needs to have at least one running execution group. You might have to create an execution group if a suitable one does not exist. Because the application is divided across multiple BAR files, it can be deployed across multiple execution groups. It is recommended that you have more than one execution group. It is important to deploy the message sets to any execution group that requires them before you deploy other resources, such as flows and wrappers.
To deploy the application, drag each required BAR file to the appropriate running execution group.