SWIFT Module 7.1 SP10.July 2020 | Configuring SWIFT Module for FileAct and InterAct Message Exchange over SAG | Configuration Steps for InterAct and FileAct Messaging Services over SAG RAHA | Step 2: Prepare the Client to Handle Requests
Step 2: Prepare the Client to Handle Requests
To prepare your client application to receive and respond to requests using the SWIFTNet component of SWIFT Module, complete the following steps:
1. Install an RA client on the same machine as Integration Server. The RA client enables the SWIFTNet component to communicate with SAG and SNL through RAHA. To obtain an RA client, contact SWIFT.
2. Configure the client environment information:
a. From Integration Server Administrator, select Adapters > SWIFT.
b. On the SWIFT Module home page, select SWIFTNet Client Configuration > Edit.
c. On the Edit SWIFTNet Client Configuration screen, in the SWIFTNet Client Environment Information section, set the following environment properties according to the properties set for the RA client:
For this property...
The cfg folder of the RA instance in your system, for example, c:\SWIFTAlliance\RA\Ra1\cfg\
The system root folder. The value of this parameter depends on your operating system, for example, c:\windows.
The lib folder of the RA instance in your system, for example, c:\SWIFTAlliance\RA\lib.
The RA home folder, for example, c:\SWIFTAlliance\RA.
RMI Port
The Remote Method Invocation (RMI) port where the remote process listeners will be bound in the Java Naming and Directory Interface (JNDI) tree, for example, 10985.
d. In the SWIFTNet Client SAG Connection Configuration section, set the following properties to define how to connect to SAG using the RAHA transport:
For this property...
The Client message partner defined in SAG.
The user name of the configured profile used in opening a security context with SAG for sending the request to SWIFT Network.
The password associated with the user name of the client PKI profile defined in your SAG. This password is used to unlock the Client PKI profile.
Automatic or Manual to specify how your SAG performs encryption operations. The default value is Automatic.
The SWIFT BIC of the partner from where the message originates. Valid values are:
o=bic, o=swift
The SWIFT BIC of the partner that serves the request sent by the SWIFTNet client. Valid values are:
o=bic, o=swift
The default service to be used by SAG for processing the request from the client.
The Distinguished Name to be used for encryption. Valid values are:
cn=encryptCN, o=bic, o=swift.
The Distinguished Name to be used for sign, encryption, and authorization operations. Valid values are:
cn=encryptCN, o=bic, o=swift
Sign, Decrypt, and Authorization
Defines whether to use the security context opened during server initialization. Valid values: True or False.
The default folder to receive incoming files. If the specified folder does not exist, it is created. When this field is blank, the default value is: Integration Server_directory \packages\WmSWIFTNetServer\pub\SWIFTNetReceptionFolder.
The absolute path of the file to be transferred on the machine on which SAG is running, for example, c:/temp/log.log
The logical name of the file to be used during the transfer, for example, sample.
Default transfer endpoint of the remote file handler. If this field is specified, the value must match a remote file handler endpoint running on the same machine as Integration Server. For information about invoking the remote file handler, see Step 3: Invoke the Remote File Handler.
The file transfer event endpoint where file transfer events (associated with file transfers) should be sent, for example, File_Status_Event_EP.
When SnF Pull or Push is used to send the file transfer events to the application server host Integration Server, the value specified for this field must be the same on both the client and the application server.
e. Click Save to save all configuration settings.
The values specified for all properties in the table, except for the SAGMessagePartner and Transport properties, are used by the sample services. For information about the sample services, see webMethodsSWIFT Module Samples Guide.
3. Invoke the wm.swiftnet.client.services:swArguments service.
Before exchanging any primitives with SAG using the SWIFTNet component, the client application must invoke the wm.swiftnet.client.services:swArguments service in the WmSWIFTNetClient package at least once. The only parameter required to be passed to this service is SAGMessagePartner, which is the message partner defined as the "Client" in your SAG during configuration.