Integrating to the customer channels of a bank

Most of the message formats exchanged on this interface by default are the standard message formats as defined by the relevant payment scheme in use. It is therefore quite likely that the bank's customer channels can originate or consume these formats.

However, the FTM Channel Notification to Channel is using an ISF format and customers may need to change this. An example of this format is shown.

Figure 1. Example ISF for Notification to Channel message

<isf:ISFMessage xmlns:isf="http://www.ibm.com/xmlns/prod/ftm/isf/v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<Header>
		<BusinessConcept>IP_TO_CDTR_CREDIT_NOTIF</BusinessConcept>
		<MasterTransactionId>16858005</MasterTransactionId>
		<TransactionId>16853039</TransactionId>
	</Header>
	<isf:AccountReport>
		<Identification>12345678901230567</Identification>
		<Account>
			<Entry xsi:type="isf:ISFReportCashEntry">
				<Amount Currency="USD">332.10</Amount>
				<EntryDetails>
					<RelatedPayment xsi:type="isf:ISFPayment">
						<ChargeBearer>SLEV</ChargeBearer>
						<EndToEndIdentification>E2E-TxPrefix20160513223041395000584</EndToEndIdentification>
					       <PartyRole xsi:type="isf:DebtorRole">
                                              ...    </PartyRole>
						<PartyRole xsi:type="isf:DebtorAgentRole">
                                              ...    </PartyRole>
						<PartyRole xsi:type="isf:CreditorAgentRole">
                                              ...    </PartyRole>
						<PartyRole xsi:type="isf:CreditorRole">
                                              ...    </PartyRole>
						<PaymentExecution xsi:type="isf:ISFPaymentInstruction">
                                              ...    </PaymentExecution>
						<PaymentObligation xsi:type="isf:ISFPaymentObligation">
                                              ...    </PaymentObligation>
						<AlternativeTransactionIdentification>
							<IdentificationIssuer>MsgId</IdentificationIssuer>
							<IdentificationValue>M20170313IBMFININST1uc1.1x...000584</IdentificationValue>
						</AlternativeTransactionIdentification>
						<TransactionIdentification>TxPrefix....20160513223041395000584</TransactionIdentification>
					</RelatedPayment>
				</EntryDetails>
			</Entry>
			<PartyRole xsi:type="isf:AccountServicerRole">
				<Player xsi:type="isf:FinancialInstitution">
					<Identification xsi:type="isf:OrganisationIdentification">
						<OtherIdentification xsi:type="isf:GenericIdentification">
							<Identification>020010001</Identification>
						</OtherIdentification>
					</Identification>
				</Player>
			</PartyRole>
		</Account>
		<AdditionalInformation>Company Details No.2</AdditionalInformation>
	</isf:AccountReport>
</isf:ISFMessage>

Note: This sample XML is only indicative of the document structure.

Model Changes

Create an appropriate FTM format in the customer application model. This format defines the format and structure of the message that should be used for the notifications.
Copy the FTM Mapper ISFToChannelNotificationMapper from the ‘Common IP’ model into the customer application model. Modify the following properties:
- Name
- ID
- Description
- Format (select new format)
Copy the FTM Channel Notification to Channel from the ‘Common IP’ model into the customer application model. Modify the following properties:
- Format (select the new format)
- Mapper (select the new mapper)
Review other properties such as CCSID, Validation, Transport and change as needed.
Save and validate the changes.
Extract and deploy a new config script.

Note: Due to a known issue in the FTM Config Extractor the artifacts copied above from the ‘Common IP’ Model should be deleted from the ‘Common IP’ model after they are copied.

Code Changes

Implement an IBM® App Connect Enterprise message model or import or select a suitable XML schema or other type of format descriptor for use with the new format defined in step 1 above.
Implement a new outbound mapper following a standard FTM mapping template (or copy an existing outbound mapper). Create the new mapper in a customer named application IBM App Connect Enterprise library. Ensure that the mapper ‘label’ is changed to match the name assigned in step 2 above.
Ensure that the mapper is added to the customer application ‘Event Processing Wrapper’ flow. Ensure the BusinessConcept property is promoted and connected to the wrapper flow BusinessConcept property.
Rebuild and deploy the new customer workspace.