Configuring Gateway for Send and Fetch

Only read this topic if you are using Gateway as the communication layer for Electronic Signature.

This topic explains how you configure Gateway to detect a Send or Fetch request and trigger the related action. Sample scripts are supplied that use Gateway and Transfer CFT.

About

To execute a Send or Fetch from a Transfer CFT client you require the following Gateway objects:

• Remote Site
• Application
• Local Site
• Model (only required for Fetch requests)
• Decision Rule

Configuring Gateway

Configuring Gateway using sample scripts

The sample script obj_gateway_client_ebics[.bat|.sh] creates all the required objects with the link to the required scripts. However you first need to customize the script.

1. Navigate to the Electronic Signature installation directory.
2. In the directory mft\install\client, locate the file obj_gateway_client_ebics.bat (or .sh for UNIX).
3. Open the file in a text editor, and modify the following parameters:

Parameter	Modification
C:\Axway\Synchrony\Gateway\run_time\etc\profile.bat	Enter the path to the Gateway profile file.
remote_cft_EBICS_client_address	Enter the Transfer CFT Server HostName.
remote_cft_EBICS_client_port	Enter the Transfer CFT Server port number.
orderType	Enter a Fetch OrderType. For example, HPB.
bank	EBICS Bank Host ID
CustomerId	EBICS Customer ID
UserId	EBICS User ID
From	FROM Date YYMMDD
To	TO Date YYMMDD

4. Save the file.
5. From the same directory, execute the script:
   • Windows: obj_gateway_client_ebics.bat
   • UNIX: obj_gateway_client_ebics.sh

To delete all objects, use the script delobj_gateway_client_ebics.[sh|bat] if the object name was not changed inside obj_gateway_client_ebics.[sh|bat].

Configuring Gateway manually

Create the following Gateway objects:

Remote Site

This object is necessary only if you connect to Transfer CFT as a back-end application.

In Gateway Navigator, create a new Remote Site object.

Application

In Gateway Navigator, create an Application object that specifies the record size, depending on your transfer requirements. This application is used inside the Decision Rule to trigger the right script.

Local Site

This object is necessary only if you connect to Transfer CFT as a back-end application.

In Gateway Navigator, create a new Local Site object.

Model (only for Fetch)

In Gateway Navigator, create a Model to be included in the Decision Rule. This Model is used to send the fetched file back to a Transfer CFT monitor. By defining several Models and Decision Rules, you can access several Transfer CFT monitors.

Decision Rule - for Fetch

In Gateway Navigator, create a Decision Rule that points to one of the scripts:

• Windows: EbicsFetchClient_GTW.bat
• UNIX: EbicsFetchClient_GTW.sh

These scripts are located in the directory \mft\Fetch

For EBICS T:

When you enter the script in the Gateway field, add the name of the Model to use and add one of the following parameters:

• test
• real

The test or real value sets the communication mode with EBICS Server.

Example on Windows:

EbicsFetchClient_GTW.bat ModelName test

For EBICS TS:

Refer to Updating payment status with PSR (in Gateway).

Decision Rule - for Send

In Gateway Navigator, create a Decision Rule that points to one of the scripts:

• Windows: EbicsSendClient_GTW.bat
• UNIX: EbicsSendClient_GTW.sh

These scripts are located in the directory \mft\Send

For EBICS T:

When you enter the script in the Gateway field, add one of the following parameters:

• test
• real

The test or real value sets the communication mode with EBICS Server.

Example on Windows:

EbicsSendClient_GTW.bat test

For EBICS TS:

When you enter the script in the Gateway field, add the following parameters:

• real
• waitUpdate

The waitUpdate indicates that the Send must wait for a signature.

Example on Windows:

EbicsSendClient_GTW.bat real waitUpdate

For more details about creating Gateway objects, refer to the Axway Gateway online documentation.

Configuring Transfer CFT

The sample script cft_ebics_client.cfg creates the required objects on the Transfer CFT side.

1. Navigate to the Electronic Signature installation directory.
2. In the directory mft\install\client locate the file cft_ebics_client.cfg.
3. Open the file in a text editor, and modify the following parameters:

Parameter	Modification
SYST	Enter the type of platform. Example values: 'WINNT' 'UNIX'
PROT	Enter 'PESITANY'
SAP	Enter '6330'
HOST	Enter the Gateway HostName

4. Save the file.
5. From the same directory, execute the script:
   • Windows: CFTUTIL #cft_ebics_client.cfg
   • UNIX: CFTUTIL @cft_ebics_client.cfg

Related topics

Configuring Gateway for Electronic Signature

Updating payment status with PSR