Task 2: Configuring the SWIFTNet Component

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 1: Prepare the Server to Handle Requests | Task 2: Configuring the SWIFTNet Component

Task 2: Configuring the SWIFTNet Component

To configure the SWIFTNet component

1. Install webMethods WebSphere MQ Adapter. If you have not already installed WebSphere MQ Adapter, see webMethods WebSphere MQ Adapter Installation and User’s Guide for installation instructions.

2. Set up the MQ queues. In WebSphere MQ Adapter, configure the adapter connection properties for the MQ server request and server reply queues 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 .

On the adapter's Configure Connection Type screen, specify the MQHA-specific information for connection settings for the queues as follows:

a. Specify the settings from SWIFT Module to the IBM MQ Server 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.SERVER.REQUEST

b. Specify the settings from IBM MQ Server 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.SERVER.REPLY

3. Create the MQ listener and configure the listener notification. You must create a single-queue listener to listen to all incoming requests from the SWIFT Network. This listener is associated with the connection configured for the IBM MQ Server Request Queue.

You must also configure an asynchronous WebSphere MQ Adapter notification for the MQ listener and define a document trigger for the notification document. This trigger calls the wm.swiftnet.server.mq.inbound.handleSWIFTRequest service that extracts the required values from the notification document and publishes the SNL primitive to Trading Networks. Configure the MQ listener notification document as described in step 6.

For instructions on how to create the listener and configure the listener notification, see webMethods WebSphere MQ Adapter Installation and User’s Guide . For more information about triggers, see Publish-Subscribe Developer’s Guide.

4. Create the MQ request/reply client service. This service sends and receives messages from the SAG client queues configured in MQ. This service is also used to start and stop the server application, since the primitives required for starting and stopping a server application are communicated to SAG through client queues. For detailed instructions on creating the request/reply service, see webMethods WebSphere MQ Adapter Installation and User’s Guide .

You must specify the following SWIFT-specific properties for this service:

a. The Wait Interval must have a value greater than 90 seconds. For more information, see the SWIFT documentation.

b. Define the msgHeader properties for the MQMD Header:

For this property...	Specify...
ReplyToQueueMgr	MQHA.SAG.QM (default value for MQHA)
ReplyToQ	MQHA.CLIENT.REPLY
MsgType	Datagram
Format	MQSTR

5. Create the MQ put server service. This service sends messages to the SAG response queue configured in MQ. For instructions on how to create the put service, see webMethods WebSphere MQ Adapter Installation and User’s Guide .

Define the msgHeader properties for the MQMD Header:

For this property...	Specify...
Format	MQSTR
MsgType	REPLY
Feedback	MQFB_APPL_FIRST (or 65536)

6. Configure the server application. Define how the server application connects to SAG using the MQHA transport:

a. From Integration Server Administrator, click Adapters> SWIFT.

b. In the SWIFT Module home page, click SWIFTNet Server Configuration > Edit.

c. In the SWIFTNet Server SAG Connection Properties section on the SWIFTNet Server Configuration screen, set the following properties.

Important:
When using MQHA, leave the default values in the fields in the Remote Process Connection Configuration and Server Environment Information sections. You must configure the fields in these sections only when you use the RAHA transport.

For this property...	Specify...
SAGMessagePartner	The Server message partner defined in SAG.
server_pki_profile	The user name of the configured profile that is used when opening a security context with SAG for sending the request to the SWIFT Network.
server_pki_password	The password associated with the user name of the server PKI profile defined in your SAG, used to unlock the Server PKI profile.
userDN	The Distinguished Name to use for sign, encryption, and authorization operations, for example, cn=encryptCN, o=bic, o=swift
encryptDN	The Distinguished Name used for encryption, for example, cn=encryptCN, o=bic, o=swift
Sign, Decrypt, and Authorization	Defines if the security context opened during server initialization should be used for sign on, decryption, or authorization. Valid values are True and False. At least one field must be set to True.
AllFileEvents	Indicates whether to populate Sw:SubscribeFileEventRequest primitive exchanged during server initialization. True—Default. SWIFT Module receives all events generated by the SAG file sub-system during file transfer. False—SWIFT Module receives only state transition events.
FullFileStatus	Indicates whether to populate Sw:SubscribeFileEventRequest primitive exchanged during server initialization. True—Default. SWIFT Module receives full details for each event report generated by the SAG system. False—SWIFT Module does not receive full details for each event report generated.
SwEventEP	The file transfer event end point to which file transfer events are posted by your SAG during FileAct operations. This value is used to populate the Sw:SubscribeFileEventRequest primitive exchanged during server initialization.
ReceptionFolder	The default folder for incoming files. If the specified folder does not exist, it is created. When this field is blank, the reception folder is created in: Integration Server_directory \packages\ WmSWIFTNetServer\pub\SWIFTNetReceptionFolder.
SwTransferEP	The default transfer endpoint of the remote file handler. This property is optional on Windows systems and required on UNIX systems. 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.
cryptoMode	Automatic or Manual to specify how your SAG performs encryption operations.
Transport	The transport type that SWIFT Module uses to initialize the application server to handle incoming responses from the SWIFT Network. The default value is MQHA.
MQ Request Reply Client Service	You can accept the default service or specify your own. For more information about this property, see step 4. The wm.swiftnet.config.sample.mq.services:getAndRecieveService sample service is the default. For information about this service, 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.
MQ Put Server Service	You can accept the default service or specify your own. For more information about this property, see step 5. The wm.swiftnet.config.sample.mq.services:serverResponse1 sample service is set as the default and is included with the SWIFT Module samples. For information about this service, see webMethods SWIFT Module Samples Guide. The default server queue and queue manager settings are used if you accept the default service. For more information on server queue settings, see SWIFT Alliance Gateway MQ Host Adapter Configuration Guide.
MQ Listener Notification Document	The MQ listener notification you created in step 3. This notification document will be published for an incoming request at the MQ server request queue.

Note:
The values specified for all properties in the table, except for the Transport, MQ Request Reply Client Service, MQ Put Server Service, and MQ Listener Notification Document properties, are used by the sample services. For information about the sample services, see webMethods SWIFT Module Samples Guide.

7. Click Save to save all configuration settings.