IBM App Connect Enterprise Deployment

Use the IBM App Connect Toolkit to deploy the sample application to the IBM App Connect Enterprise.

If not already present, ensure that the following core and generic projects are imported into the IBM App Connect Toolkit workspace:

The core projects found in the \FXH_Core_Projects_WMB.zip\FXH\wmb\core\FXH_Core_Projects_WMB_PI.zip file.
The Generic Model Actions project found in the \FXH_GenericModel.zip\FXH\wmb\generic\FXH_GenericModel_WMB_PI.zip file.

Import the sample application projects into the workspace from the \FXH_Sample.zip\FXH\samples\Sample App\FXH_Sample_PI.zip file.

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

The "FTM Sample App Svr Proj" project contains six prebuilt broker archive (BAR) files that include all 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.

To rebuild the BAR files before deployment:

Open the BAR file and select the Prepare tab.

Select the resources for each of the BAR files as follows:

Table 1. BAR resources
Resource	BAR files
	EventWrapper	PTWrapperBAT	PTWrapperTxn	MiscFlows	MsgSets	Simulators
Libraries
FTM Core CBE					Y
FTM Core Flows					Y
FTM Core Flows Ext					Y
FTM Core ISF for Payments V3
FTM EndMapper					Y
FTM Generic Model Actions					Y
FTM Sample App ISF V3					Y
FTM Sample App LIB					Y
FTM Sample App pain.001.001.03					Y
FTM Sample App pain.002.001.03					Y
FTM SWIFT MT Flows					Y
FTM SWIFT MT Flows Current
FTM SWIFT MT Flows fin2014
FTM SWIFT MT Flows fin2015
FTM SWIFT MT Flows fin2016
FTM SWIFT MT Flows finsample					Y

Flows
EventProcessingWrapper	Y
HeartbeatWrapper				Y
LogErrorWrapper				Y
PaymentGatewaySimulator						Y
LiquidityServiceSimulator						Y
PT_Wrapper_Command				Y
PT_Wrapper_LiqdResp			Y
PT_Wrapper_PmtGWResp			Y
PT_Wrapper_PmtMT103			Y
PT_Wrapper_PmtPain		Y
PT_Wrapper_RepResp

Message Sets
messageSet					Y

Click Build and Save.

Configurable Properties

The default configuration values that are used in the supplied BAR files match the default configuration values in the supplied FSM and configuration data scripts.

The following table lists the configurable properties in each of the BAR files:

Table 2. Configurable properties
BAR file	Flow	Configurable properties
EventWrapper	EventProcessingWrapper.msgflow->EventProcessingFlow\EventProcessingWrapper	AppVer Application DB_SCHEMA ErrorsQueueName EventsQueueName FailedEventsQueueName dataSource
MiscFlows	HeartbeatWrapper.msgflow->Heartbeat\HeartbeatWrapper	AppVer Application DB_SCHEMA Data source ErrorsQueueName EventsQueueName FailedQueueName Timeout Interval(sec) Unique Identifier
	LogErrorWrapper.msgflow->Common\LogErrorWrapper	AppVer Application DB_SCHEMA Data source ErrorsQueueName EventsQueueName FailedQueueName UniqueCacheMonotorId
	PT_Wrapper_Command.msgflow->PhysicalTransmissionFlow\PT_Wrapper_Command	AppVer Application DB_SCHEMA Chan_Command_QueueName Chan_Failed_QName_Prefix ChannelName DB_SCHEMA ErrorsQueueName EventsQueueName FailedQueueName QueueManagerOut dataSource
	PT_Wrapper_RepResp.msgflow->PhysicalTransmissionFlow\PT_Wrapper_RepResp	AppVer Application Chan_Failed_QName_Prefix Chan_RepairResponse_QueueName ChannelName DB_SCHEMA ErrorsQueueName EventsQueueName FailedQueueName QueueManagerOut dataSource
PTWrapperBat	PT_Wrapper_PmtPain.msgflow->PhysicalTransmissionFlow\PT_Wrapper_PmtPain	AppVer Application Chan_Failed_QName_Prefix Chan_PmtPain_QueueName ChannelName DB_SCHEMA ErrorsQueueName EventsQueueName FailedQueueName QueueManagerOut dataSource
PTWrapperTxn	PT_Wrapper_LiqdResp.msgflow->PhysicalTransmissionFlow\PT_Wrapper_LiqdResp	AppVer Application Chan_Failed_QName_Prefix Chan_LiquidityResponse_QueueName ChannelName DB_SCHEMA ErrorsQueueName EventsQueueName FailedQueueName QueueManagerOut dataSource
	PT_Wrapper_PmtGWResp.msgflow->PhysicalTransmissionFlow\PT_Wrapper_PmtGWResp	AppVer Application Chan_Failed_QName_Prefix Chan_PmtGWResponse_QueueName ChannelName DB_SCHEMA ErrorsQueueName EventsQueueName FailedQueueName QueueManagerOut dataSource
	PT_Wrapper_PmtMT103.msgflow->PhysicalTransmissionFlow\PT_Wrapper_PmtMT103	AppVer Application Chan_Failed_QName_Prefix Chan_PmtMT103_QueueName ChannelName DB_SCHEMA ErrorsQueueName EventsQueueName FailedQueueName QueueManagerOut dataSource
Simulators	PartnerSimulator1.msgflow->PartnerSimulator\PartnerSimulator1	LiquidityResponseQueue LiquidityRequestQueue
Simulators	PartnerSimulator2.msgflow->PartnerSimulator\PartnerSimulator2	PaymentRequestQueue PaymentResponseQueue
MsgSets	No flows require configuration.	n/a

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 Figure 1 can be configured (in their respective BAR files) in the BAR file editor before deployment.

For more information about configurable properties, see Deployment Configuration Properties.

If you are deploying from IBM App Connect Toolkit, you need to be connected to an Integration Node (Broker) instance. You can do this by selecting an existing Integration Node in the 'Integration Nodes' tab of the IBM App Connect Toolkit. This needs to have at least one running Integration Server (you might need to create an Integration Server if a suitable one does not exist). As the application is divided across multiple BAR files, it can be deployed across multiple Integration Servers, or only one (typical). 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.