Updating the SWIFT Currency table in SWIFTNet Portal

Currency table update: General procedure

Importing the add-on Integration-Process

Creating the Composer objects

Updating the Table

Currency table update: General procedure

1. Import the add-on Integration-Process for the SWIFTNet Portal Currency table.
2. Create the set of Composer objects to support the Currency table update.
3. Execute the Table update.

Importing the add-on Integration-Process for the SWIFTNet Portal Currency table

The FEX installation package includes an add-on Integration-Process that you can use to update the SWIFTNet Portal Currency table. To import the add-on:

1. Unzip the FEX installation package to extract the files.
2. Start Composer.
3. In the Composer Integration-Services workbench, click to select a user folder in the object tree structure.
4. From the Composer Tools menu, execute Import Object. Composer displays the Import Wizard.
5. In the Import Wizard, navigate to the FEX installation package directory \Software\integrator\composer 
6. Select to import the file ip_swiftnet_update_currency.xml
7. Click Finish.
8. Composer imports the file and creates the IP_SWIFTNET_UPDATE_CURRENCY Integration-Process in the Integration-Process folder of the Composer navigation pane.
9. You can now open and display the IP_SWIFTNET_UPDATE_CURRENCY Integration-Process in Composer.

Associated Composer objects

After you import the Integration-Process, in Composer you require the following objects:

• Integrator Axway Server
• JDBC CommAdapter
• FTP Partner
• JDBC Partner
• FTP input Channel
• JDBC output Channel
• Integration-Task

These objects operate as a set with the IP_SWIFTNET_UPDATE_CURRENCY Integration-Process. Together these objects enable you to update the Currency table in SWIFTNet Portal.

Creating the Integrator Axway Server object

In most cases, you will already have created an Axway Server object in Composer to represent the Integrator Server instance where the SWIFT tables reside. If this is the case, you reuse the same object for SWIFTNet Portal Table updating procedures.

If for any reason you need to create a new Integrator Axway Server object, refer to the topic that describes the Axway Server creation procedure.

Creating the JDBC CommAdapter

If you have already created a JDBC CommAdapter that you want to use, this procedure is not necessary.

1. In Composer, open the Topography workbench.
2. In the Topography workbench open the Axway Server object that represents your Integrator Server instance.
3. Composer displays the Axway Server properties window.
3. In the Axway Server properties window select the Communication tab.
4. In the Communication tab, add a TCP-type CommNetwork.
5. Right-click the CommNetwork and from the context menu select Add a CommAdapter.
6. Composer adds a CommAdapter node to the tree structure in the left pane, and displays the CommAdapter configuration fields in the right pane.
6. In the right pane, complete the configuration fields:
   • CommAdapter type: Select JDBC from the drop-down list
   • Template: If you have created a template to configure this CommAdapter, you can optionally select the template from the drop-down box.
7. Check, save and close the Axway Server object.

Creating the FTP Partner

When you imported the Currency tables to Integrator, you created an FTP Partner. You can reuse the same object for SWIFTNet Portal Table updating procedures.

View FTP Partner creation topic

Prerequisites

Before you create the Partner object, you must create:

• CommNetwork object that defines the network protocol you use to communicate between Integrator and Messaging.
  
  
• Host object that defines characteristics of the machine where the Messaging Server instance runs. 
• Optionally, a HostGroup object that defines characteristics of the machine where the Messaging application is situated. 

Procedure

1. In the Composer Integration-Services workbench Transport tab, double-click a HostGroup to display a list of Hosts.
2. Right-click the Host where you want to define the Partner. From the context menu, select Partner.
3. Composer opens the Partner properties window.
3. In the General tab, enter a name for the Partner object. For example, you could enter JDBC_SWIFTNET.
4. In the Communication tab:
   • In the left pane, add a TCP CommNetwork.
   • Right-click the TCP CommNetwork node and from the context menu, select Add a CommAdapter.
• Composer adds a CommAdapter node as a child node of the CommNetwork node in the left pane, and opens the CommAdapter properties window in the right pane.
• In the CommAdapter type field select JDBC.
• Composer adds a JDBC parameters sub-tab for configuring the CommAdapter.
5. Complete the JDBC parameters sub-tab.
View field descriptions

Field	Description
Driver type	Enter name database type. For example: Oracle
Driver class	Enter the name of the Java class to be used by Integrator for the database connection. . For example: oracle.jdbc.driver.OracleDriver
URL template	Enter the URL structure for access to the database type. For example: jdbc:oracle.thin@hpxll.my_company:1542:Integrator View Oracle RAC option
Database	Enter the name of the database. Integrator uses this name in the <databaseName> attribute of the URL template, above.
Port	Enter the access port number for the database. To connect to the database, Integrator uses this port number in the <databasePort> attribute of the URL template, above.

6. Right-click the CommAdapter node in the left pane, and from the context menu, select Add a CommPoint.
7. Composer adds a CommPoint node as a child node of the CommAdapter node in the left pane, and opens the CommPoint properties window in the right pane.
7. Complete the Configuration sub-tab.
View field descriptions

Field	Description
User	Enter the user name for connecting to the database. This information corresponds to the information found in the Schema of the database in which the Currency, Country and BIC tables are stored.
Password	Enter the password for connecting to the database. This information corresponds to the information found in the Schema of the database in which the Currency, Country and BIC tables are stored.

8. From the File menu, select:
   1. Check to verify that all mandatory object definitions are correct
   2. Save to save the object definition in the Composer database.
   3. Close to close the object properties window.

Creating the FTP input Channel

1. In the Composer Integration-Services workbench, Transport tab / Hierarchy sub-tab, right-click the Axway Server object that represents Integrator and then select Channel from the context menu.
2. Composer displays the Channel properties window.
2. Complete the General tab:
View fields

Field	Contents
Name	Enter a name for the Channel. For example, IN_CURRENCY
Label	Optionally enter a description.
Status	You cannot directly change the status in this field.
Endpoints
Terminus1	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.
Terminus2	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)

3. In the Connection point 2 tab,:
4. In the Receiver or Sender field select Receiver.
5. Receive script field: Enter a receive script such as the following:
6. 
6. Check, save and close the object.
7. Send the Channel object to production.
8. Composer sets the object status to committed.Creating the Integration-Task

Creating the JDBC output Channel

1. In the Composer Integration-Services workbench, Transport tab /Hierarchy sub-tab, right-click the Axway Server object that represents Integrator and then select Channel from the context menu.
2. Composer displays the Channel properties window.
2. Complete the General tab:
View fields

Field	Contents
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
Terminus1	From the drop-down list, select Partner. Then from the Instance field drop-down list, select the Partner object that represents the JDBC Database.
Terminus2	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 / Oracle (or other database type)
Connection point 1	Select the FTP CommAdapter
Connection point 2	Select the JDBC CommAdapter

3. Check, save and close the object.
4. Send the Channel object to production.
5. Composer sets the object status to committed.Creating the Integration-Task
Create an Integration-Task as displayed in the following example:w²w²

Creating the Integration-Task

The Integration-Task object contains the technical information that is necessary to execute your Integration-Process on an Integrator Server.

For SWIFT table integration you use the Integration-Task to link the Receive and Send Activities to the appropriate Channels.

1. In the Composer Integration-Services workbench, from the File menu, select New > Integration > Integration-Task.
2. Composer displays the Integration-Task properties window.
2. Complete the General tab:
View fields

Field	Contents
Name	Enter a name for the Integration-Task. For example: IT_SWIFTNET_UPDATE_CURRENCY
Integration-Process	From the drop-down list, select the Integration-Process you imported for Currency table updates: IP_SWIFTNET_UPDATE_CURRENCY
Integrator Server	Select the name of the Integrator Server instance on which you want to run the integration.

3. When you associate an Integration-Process with the Integration-Task and specify the Integrator Server that runs the task, Composer automatically adds a Configuration tab to the Integration-Task definition screen.
3. Complete the Configuration tab:
View fields

Field	Contents
In Activity	Associate this Activity with the FTP input Channel
TRANSFER_CURRENCY_FILE	Associate this Activity with a Hierarchical processor Task
Out Activity	Associate this Activity with the JDBC output Channel

4. Check, save and close the object.
5. Send the Integration-Task to the Integrator Server.

Updating the Currency table with the CU.dat file

If you are a subscriber to the appropriate SWIFT services, SWIFT periodically supplies you with data file for Currency table updating: CU.dat

To use the CU.dat file to update the content of the SWIFTNet Portal Currency table:

1. Copy the file CU.dat from the file where you store your SWIFT-supplied data files to the input Channel folder specified in the input Channel script.
2. If it is not already started, start the Task CORE process in the Copilot Task Monitor. You need to start the task if you started the Integrator Server with the option core_servers –S.
3. Check the SWIFTNet Portal database to confirm that the Currency table has been updated.

Related topics

About updating SWIFT tables in SWIFTNet Portal