IBM App Connect Deployment

The FTM StoreAndRelease Sample Bar files project contains four prebuilt broker archive (BAR) files that include all these components.

Each BAR file should be rebuilt prior to deployment for the following reasons:
  • To ensure that the code loaded into the workspace matches with the requirements of the BAR files.
  • To ensure that any core updates that have been applied are included in the BAR files.
  • To remove the possibility of any compatibility issues. This is not expected to be an issue and is recommended as a precaution only.
  • To check that the 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 may 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 will have to check that the values are correct for all of the flows in the application.
Note: If these default properties are changed, ensure that the Override configurable property values check box is cleared before rebuilding each BAR file.

If you are deploying from you will need to be connected to a broker instance. You can do this by selecting an existing broker instance in the 'Integration Nodes' tab of the . This will need to have at least one running Integration Server (you may have to create an Integration Server if a suitable one does not already exist). As the application has been divided across multiple BAR files, it can be deployed across multiple Integration Servers. It is recommended to have more than one Integration Server. 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 Integration Server.