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 MQHA | 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 from SAG over the IBM WebSphere MQ transport, you must complete the following steps:
1. Set up the MQ Queues. In WebSphere MQ Adapter, configure the adapter connection properties for the MQ server request queue and server reply queue to handle incoming requests from the SWIFT Network. For complete information about configuring adapter connections, see webMethods WebSphere MQ Adapter Installation and User’s Guide .
*Specify the MQHA-specific information for the connection settings from SWIFT Module to IBM MQ Client Request Queue:
For this property...
Specify...
Queue Manager Name
MQHA.SAG.QM
Host Name
The name of the server on which IBM WebSphere MQSeries is running.
Server Connection Channel
MQHA.CHANNEL
Queue Name
MQHA.CLIENT.REQUEST
*Specify the MQHA-specific information for the connection settings from IBM MQ Client Reply Queue to SWIFT Module:
For this property...
Specify...
Queue Manager Name
MQHA.SAG.QM
Host Name
The name of the server on which IBM WebSphere MQSeries is running.
Server Connection Channel
MQHA.CHANNEL
Queue Name
MQHA.CLIENT.REPLY
2. Define how the client application connects to SAG using MQHA transport as follows:
a. In Integration Server Administrator, click Adapters> SWIFT.
b. In the SWIFT Module home page, click SWIFTNet Client Configuration > Edit.
c. In the SWIFTNet Client SAG Connection Configuration section, set the following properties to define how to connect to SAG using MQHA transport:
Important:
When using MQHA, leave the default values in the fields in the SWIFTNet Client Environment Information section. Configure the fields in this section only when using RAHA transport.
For this property...
Specify...
SAGMessagePartner
The Client message partner defined in SAG.
client_pki_profile
The user name of the configured profile that is used for opening a security context with SAG (to send the request to SWIFT Network).
client_pki_password
The password associated with the user name of the client PKI profile defined in your SAG. This is used to unlock the Client PKI profile.
cryptoMode
Automatic or Manual to specify how your SAG performs encryption operations. The default value is Automatic.
requestor
The SWIFT BIC of the partner from where the message originates, for example, o=bic, o=swift
responder
The SWIFT BIC of the partner that will serve the request sent by the SWIFTNet client, for example, o=bic, o=swift
service
The default service to be used by SAG for processing the request from the client.
encryptDN
The Distinguished Name to be used for encryption, for example, cn=encryptCN, o=bic, o=swift
userDN
The Distinguished Name to be used for sign, encryption, and authorization operations, for example, cn=encryptCN, o=bic, o=swift
Sign, Decrypt, and Authorization
True or False to define if the security context opened during server initialization should be used for sign on, decryption or authorization.
ReceptionFolder
The default folder to receive incoming files. When this field is blank, the folder is created in the following path:
Integration Server_directory \packages\WmSWIFTNetClient\pub\SWIFTNetReceptionFolder.
If the specified folder does not exist, it is created.
physicalName
The absolute path of the file (to be transferred), for example, c:/temp/log.log.
For more information, see SWIFTNet Service Design Guide and SWIFTNet Link Interface Specification.
logicalName
The logical name of the file that should be used during the transfer, for example, sample.
SwTransferEP
The default transfer endpoint of the remote file handler. If SwTransferEP is specified, the value must match a remote file handler endpoint running on the same machine as Integration Server.
For information on invoking the remote file handler, see Step 3: Invoke the Remote File Handler.
SwEventEP
The file transfer event end point where file transfer events should be sent, for example, File_Status_Event_EP.
Note:
When SnF Pull or Push is used to send the file transfer events to the server application host Integration Server, the value specified for this parameter must be the same on both the client and the server application.
Transport
MQHA. This is the default value.
MQ Request Reply Client Service
You can accept the default service or specify your own. For more information about the MQ request/reply client service, see step 4 in Task 2: Configuring the SWIFTNet Component.
The default service is wm.swiftnet.config.sample.mq.services: getAndRecieveService, included in the SWIFT Module samples. For information about the sample services, see webMethods SWIFT Module Samples Guide.
If you accept the default service, the default client queue and queue manager settings are used. For more information on the queue settings, see SWIFT Alliance Gateway MQ Host Adapter Configuration Guide.
Note:
The values specified for all properties in the table, except for the Transport and MQ Request Reply Client Service properties, are used by the sample services. For information about the sample services, see webMethods SWIFT Module Samples Guide.
d. Click Save to save all configuration settings.