Creating Composer objects for the Banque de France repository

Overview

Creating the Axway Server object

Creating the FTP CommAdapter

Creating the FTP Partner

Creating the FTP input Channel

Creating the JDBC CommAdapter

Creating the JDBC Partner

Creating the JDBC Channel

Creating the Integration-Task

Overview

This topic describes the Composer objects you need to create in order to populate the Banque de France repository and to keep the repository up to date.

After importing the Integration-Processes, you need to create the following objects in Composer:

• Axway Server (to represent the Integrator Server instance)
• FTP CommAdapter
• FTP Partner (to represent the FTP Server)
• FTP input Channel
• JDBC CommAdapter
• JDBC Partner (to represent the database)
• JDBC Channel
• Integration-Task

These objects operate as a set with the already imported IP_BDF_INSERT_SITUATION and/or IP_BDF_INSERT_MOUVEMENTS Integration-Process(es). Together these objects enable you to update the Etablissement and Guichet tables in the database, find the BIC value and validate the BIC value.

Creating the Axway Server object

In most cases, you have already created an Axway Server object in Composer to represent the Integrator Server instance. If this is the case, you can reuse the same object for the Banque de France table update procedures.

If for any reason you need to create a new Axway Server object, refer to Axway Server creation procedure.

Creating the FTP CommAdapter

If you have already created an FTP 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:

Field	Description
CommAdapter type	Select FTP 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 object.

Creating the FTP Partner

About the FTP Partner object

This Partner object specifies the machine, protocols and access mechanisms that enable Integrator to communicate with an FTP server.

Procedure

1. In the Composer Integration-Services workbench Transport tab, Directory sub-tab, right-click the Axway Server object that represents the Partner.
2. Select the folder 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, BDF_FTP.
   • In the left pane, add a TCP.
   • Right-click the TCP CommNetwork node and from the context menu, select Add a CommAdapter.
4. In the Communication tab:
• 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 FTP.
  • Composer adds a Configuration sub-tab for configuring the FTP CommAdapter.
5. Complete the Configuration sub-tab:

Field	Description
TCP/IP port	Enter a port or accept the default port: 21
Protocol timeout (seconds)	Enter a timeout limit for the connection.

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:

Field	Description
User	Enter the username for the FTP user on the remote FTP server.
Account	Enter the account to use.
Password	Enter the password to use.
Transfer timeout (Mandatory)	Enter the timeout in seconds.

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

Creating the FTP input Channel

If you are using both the Situation and Mouvements files, you need to create one input Channel for each file.

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

Field	Description
Name	Enter a name for the Channel. For example, IN.
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:
   • In the Receiver or Sender field, select Receiver.
   • Receive script field: Enter a receive script such as:

   CD $CORE_DATA"/ftp/public/bdf/situation"; -LIST "." INTO %F { -RECV %F; IF(%FTPSTATUS IN "200"-"299") { DELETE %F; } }

   • You can choose any folder hierarchy, but make sure that the Situation and Mouvements folders are separate.
4. Check, save and close the object.
5. Send the Channel object to production.
6. Composer sets the object status to committed.

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:

Field	Description
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 object.

Creating the JDBC Partner

This Partner object specifies the machine, protocols and access mechanisms that enable Integrator to communicate with a database.

1. In the Composer Integration-Services workbench Transport tab, Directory sub-tab, right-click the Axway Server object that represents the Partner.
2. Select the folder 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, BDF_JDBC.
   • In the left pane, add a TCP.
   • Right-click the TCP CommNetwork node and from the context menu, select Add a CommAdapter.
4. In the Communication tab:
• 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 Configuration sub-tab for configuring the JDBC CommAdapter.
5. Complete the Configuration sub-tab:

Field	Description
Driver type	Select the type of database you are using: Oracle or MySQL
Driver class	This value is filled in automatically.
URL template	Enter the URL structure (host name, database port number and database name) for access to the database type. For example: jdbc:oracle.thin@MyHostName:1521:AXWAY
Database	Enter the name of the database. Integrator uses this name in the <databaseName> attribute of the URL template.
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.

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:

Field	Description
User	Enter the username for the JDBC user on the remote JDBC server.
Password	Enter the password to use.

8. Click Save.
9. Confirm your password and click OK.
10. From the File menu, select:
    • Check to verify that all mandatory object definitions are correct
    • Save to save the object definition in the Composer database.
    • Close to close the object properties window.

Creating the JDBC Channel

If you are using both the Situation and Mouvements files, you can use the same output channel for both files.

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:

Field	Description
Name	Enter a name for the Channel. For example, BDF_JDBC.
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 JDBC CommAdapter.
Connection point 2	Select the JDBC CommAdapter (this is for the connection on the database side).

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

The Integration-Task object contains the technical information that is necessary to execute your Integration-Process on an Integrator Server. For Banque de France table integration you use the Integration-Task to link the Receive and Send Activities to the appropriate Channels.

Important: Make sure you have already defined the FTP input Channel and JDBC Channels accordingly to your system settings. You can choose any folder hierarchy, but make sure that the Situation and Mouvements folders are separate. If you are using both the Situation and Mouvements files, you can use the same output channel for both files.

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:

Field	Description
Name	Enter a name for the Integration-Task. For example: IT_BDF_INSERT_SITUATION or IT_BDF_INSERT_MOUVEMENTS
Integration-Process	From the drop-down list, select the Integration-Process IP_BDF_INSERT_SITUATION or IP_BDF_INSERT_MOUVEMENTS
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:

For the Situation file

Field	Description
ReceiveActivity1	Associate this Activity with the FTP input Channel.
LocalMapStage2
GUICHET_SELECT	Associate this Activity with the JDBC Channel you created for this procedure.
GUICHET_INSERT	Associate this Activity with the JDBC Channel you created for this procedure.
GUICHET_DELETE	Associate this Activity with the JDBC Channel you created for this procedure.
LocalMapStage3
ETA_SELECT	Associate this Activity with the JDBC Channel you created for this procedure.
ETA_INSERT	Associate this Activity with the JDBC Channel you created for this procedure.
ETA_DELETE	Associate this Activity with the JDBC Channel you created for this procedure.

For the Mouvements file

Field	Description
ReceiveActivity1	Associate this Activity with the FTP input Channel.
LocalMapStage1
ETA_SELECT	Associate this Activity with the JDBC Channel you created for this procedure.
ETA_DELETE	Associate this Activity with the JDBC Channel you created for this procedure.
ETA_INSERT	Associate this Activity with the JDBC Channel you created for this procedure.
ETA_UPDATE
LocalMapStage2	LocalMapStage2
GUICHET_SELECT	Associate this Activity with the JDBC Channel you created for this procedure.
GUICHET_INSERT	Associate this Activity with the JDBC Channel you created for this procedure.

4. Check, save and close the object.
5. Send the Integration-Task to the Integrator Server.
6. Check that the Integrator tasks are running.
7. Copy the input file inside the folder specified by the FTP input Channel. The database table will be updated as output.

What next?

Update the Banque de France repository