Creating the Integrator FTP input Channel
Creating the Integration-Process
This version of Axway Financial Exchange includes Java Custom-Functions for Integrator. These Custom-Functions are used inside the check constraints of each Business Document (SWIFT-FIN, SWIFT-XML, and so on).
This topic explains how to set up a link between a Java Custom-Function and the required database storage.
Only the following functions use such a database:
| Table name | Expected number of rows |
|---|---|
| BIC_IBAN (FI & BI) | 90000 (maximum) |
| IBAN_IS (IS) |
50 maximum (depends upon the list of countries that apply IBAN coding) |
In the Axway Composer Integration-Services workbench, Transport tab, Hierarchy sub-tab:
| Field | Description |
|---|---|
| Name | Enter a name for the Channel. For example: In_BIC |
| Label | Optionally enter a description |
| Status | You cannot directly change the status in this field. |
| Endpoints | |
| Terminus 1 | From the drop-down list, select Partner. Then from the Instance field drop-down list, select the Partner object that represents the FTP server application. |
| Terminus 2 | From the drop-down list, select Axway Server. Then from the Instance field drop-down list, select the Axway Server object that represents the Integrator Server. |
| Connection parameters | |
| Connection type | Select TCP/FTP |
| Connection point 1 | Select the FTP CommAdapter (this is for the connection on the Integrator side) |
| Connection point 2 | Select the FTP CommAdapter (this is for the connection on the FTP Server side) |
|
CD $CORE_DATA"/ftp/public/bic_iban"; -LIST "." INTO %F { -RECV %F; IF (%FTPSTATUS IN "200"-"299") { DELETE %F; } } |
If you have already created a JDBC CommAdapter that you want to use, this procedure is not necessary.
| Field | Description |
|---|---|
| Name | Enter a name for the Channel. For example: Update_BIC |
| Label | Optionally enter a description |
| Status | You cannot directly change the status in this field. |
| Endpoints | |
| Terminus 1 | From the drop-down list, select Partner. Then from the Instance field drop-down list, select the Partner object that represents the JDBC database. |
| Terminus 2 | From the drop-down list, select Axway Server. Then from the Instance field drop-down list, select the Axway Server object that represents the Integrator Server. |
| Connection parameters | |
| Connection type | Select FTP/Oracle (or other database type) |
| Connection point 1 | Select the FTP CommAdapter |
| Connection point 2 | Select the JDBC CommAdapter (this is for the connection on the database side) |
This Integration-Process must make use of one of the following Java Custom-Functions:
The Function Call may appear in any DML part of the Integration-Process:
They are most often used and found inside CheckConstraints delivered as part of the FEX libraries delivery.
You can import the sample Integration-Process ip_update_bic_table.xml delivered in the FEX installation package in the Software\BICUpdate directory. This Integration-Process enables you to update the BIC Repository.
| Field | Description |
|---|---|
| Name | Give a name to the integration task |
| Label | Optionally enter a description |
| Status |
You cannot directly change the status in this field. |
| Integration-Process | Select the IP created |
| Integrator Server | Select the Integrator Server |
| Sentinel | Log all events |
Importing Custom-Functions to Composer
Migration: Updating the Custom-Functions
Using the Banque de France Custom-Functions