SWIFT Module 7.1 SP10.July 2020 | Configuring SWIFT Module for Message Exchange over SAA | Configuring SWIFT Interfaces | Using the CASmf Services to Communicate with SWIFT | Configuring the CASmf Interface
 
Configuring the CASmf Interface
Important:
The following procedure assumes that you have already configured your CASmf server and SAA to communicate with one another. For more information, see your CASmf server and SWIFT documentation.
The configuration settings for the CASmf services are stored in the CASmf configuration file (wmcasmf.cnf). This file resides in the Integration Server_directory \packages\ WmFIN\config directory and contains parameters that determine how the services operate. Edit the file directly with a text editor.
*To configure the CASmf Interface for SWIFT Module
1. Install a CASmf client on the same machine as Integration Server. For more information, see your CASmf documentation.
Important:
Start the SWIFT CASmf Client before starting Integration Server.
2. Configure the CASmf services to work with SWIFT Module.
a. Open the Integration Server_directory \packages\WmFIN\config\wmcasmf.cnf file in a text editor.
b. Edit the following properties as needed:
Property
Description
wm.casmf.send.mapid
The sending and receiving mapIDs that you have defined for SAA. The default value is CASmfInput.
wm.casmf.receive.mapid
The mapIDs must match exactly the two l_mapid fields in the CASmf client dmapid.dat file. Usually, this file is located in the directory where the CASmf client is installed: $CASmfInstallationFolder\dat. You can also locate this file using the folder listed in your DATTOP environment variable. The default value is CASmfOutput.
wm.casmf.send.message.folder
The default folder in which all outbound SWIFT FIN messages are queued before being sent to SWIFT via the CASmf Interface: Integration Server_directory \ packages\WmFIN\config\outboundMessages. You can change this location if desired.
wm.casmf.authentication.type
The type of authentication that you want the webMethods CASmf services to perform with SAA. Specify one of the following:
*AUTH_ACCESS—Performs session authentication.
*AUTH_DATA—Performs data authentication.
*AUTH_BOTH—Performs session and data authentication.
*AUTH_NONE—Performs no authentication.
wm.casmf.authentication.sendKey
The keys used for authentication of the session:
*sendKey—The receive key that you defined for the CASmf input message partner on SAA.
*receiveKey—The send key that you defined for the CASmf output message partner on SAA.
Important:
Reverse the keys appropriately when defining this property. For example, use the value you defined for the sendKey in SAA for the wm.casmf.authentication.receiveKey property.
wm.casmf.authentication.receiveKey
wm.casmf.authentication.localSend Key
The keys used for local authentication of the data sent and received over a CASmf session on SAA:
*localSendKey—The receive key that you defined for the CASmf input message partner.
*localReceiveKey—The send key that you defined for the CASmf output message partner.
Important:
Reverse the keys appropriately when defining this property. For example, use the value you defined for the localSendKey in SAA for the wm.casmf.authentication.local.ReceiveKey property.
wm.casmf.authentication.local ReceiveKey
wm.casmf.receive.timeout
The number of seconds that CASmf services should maintain an active connection with SAA for receiving messages. If no messages are received within the specified time, the connection is closed. The default is 300 seconds.
For example, if the timeout value is 300 seconds and there are 10 messages that take 20 seconds to receive, the connection remains open for the 20 seconds it takes to receive the 10 messages, then remain idles for the next 280 seconds before being closed.
Save and close the file.
3. In the TPA for each type of SWIFT message that you will send and receive using CASmf, set the following field:
Set this field to...
To...
Transport
CASmf
For more information about TPAs, see Modifying the TPA.
4. In Integration Server Administrator, create a scheduling service to run the wm.casmf.trp:casmfSendReceiveSchedule service at intervals:
a. In the Server menu of the Navigation panel, click Scheduler.
b. Click Create a scheduled task.
c. To set the fields in the Service Information section, follow the instructions in webMethods Integration Server Administrator’s Guide.
d. In the Schedule Type and Details section, under Repeating Tasks With a Simple Interval, set the fields as follows:
*Select Repeating.
*In the Start Date and Start Time fields, enter the date and time of the first execution of the service. These fields are optional.
*In the End Date and End Time fields, enter the date and time of the last execution of the service. These fields are optional.
*Select the Repeat after completion check box.
*In the Interval field, Software AG recommends that you set this service to run at intervals of at least 15-20 minutes.
e. Click Save Tasks.
For more information about this service, see wm.casmf.trp:casmfSendReceiveSchedule.