Implementation > Electronic Signature > Integration with Gateway > Configuring Gateway

Configuring Gateway for Electronic Signature

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

Installing Gateway

Install Axway Gateway as described in the Axway 5 Suite Installation and Prerequisites Guide.

Configuring Gateway for Electronic Signature

After installing Electronic Signature with Gateway as communication layer, you have to configure Gateway in order to make the link with the back-end application.

Prerequisites

Gateway must be installed on the same machine as Electronic Signature.
Sentinel Universal Agent must be installed on the same machine as Electronic Signature.

Using Transfer CFT to connect to the back-end application

The FEX installation package includes a set of sample files that enable you to link Gateway and Electronic Signature to Transfer CFT to connect to the back-end application.

The sample files that are provided in the FEX installation package enable you to:

Automate a Send request (for example, to EBICS Server)
Automate a scheduled Fetch and send result to a Transfer CFT monitor
Automate a Fetch request and send the received file (for example, a PSR file) to a Transfer CFT monitor

This topic describes a generic implementation. You should adapt it to your specific internal application requirements.

Behavior principles: User message

The provided scripts are based on the User message parameter that can be used with the PeSIT or FTP protocols.

Send - User message syntax

where:

<orderTypeBL> is the full EBICS order type (for example FUL.pain.001.001.02.ict).

<bankId> is the EBICS HostId of the Bank.

<CustomerId> is the EBICS customerID.

<SystemId> is the EBICS userID of the user used as systemID (optional).

<userIdTransport> is the EBICS userID of the transport user (optional).

<PayloadId> is the id of the payload, this parameter is mandatory.

<Domain> is the domain of the payload. The domain is the organizational entity within a company.

<sender> is the sender of the payload. The sender is the application that initiates a payment flow.

<amount> is the global amount of the payment that is displayed in the Electronic Signature UI (optional). If a value is specified here it will override the amount parsed from the payload.

<Nb_of_operation> is the number of operation of the given payment file. This value is displayed in the Electronic Signature UI (optional). If a value is specified here it will override the number of operations parsed from the payload.

<comment> is any business information that might help the treasurers to sign a payment. This optional value is displayed in the Electronic Signature payments comment column. Note that special characters (!, ?, etc.) cannot be used.

<CustomerId> and <AdditionalUserId1> are mandatory unless a default Customer and User are defined inside the Bank.

Fetch - User message syntax

where:

<CustomerId> and <userIdTransport> are mandatory unless a default Customer for the Bank and a default User for the Customer are defined.

<FromDate> and <ToDate> are optional. They are defined in the format YYMMDD.

Configuring Gateway to connect to Transfer CFT

Refer to the following topics:

Operation	Refer to
Send and Fetch	Configuring Gateway for Send and Fetch
Fetch PSR	Updating payment status with PSR (in Gateway)