Configuring message partners
When
you configure an SAG, you must create and configure, for each OU,
one message partner for each entity that creates or processes SWIFTNet
primitives. Examples of such entities are:
- A FIN LT
- The MSIF transfer services
You
create and configure a message partner by issuing the addMessagePartner
command, which is described in addMessagePartner.
The application type of the message partner is specified by the -type
parameter, and can be one of:
- Client
- The message partner corresponds to a client application.
- Server
- The message partner corresponds to a server application.
- ClientServer
- The message partner corresponds to client or server application.
If you configure:
- A message partner for FTM SWIFT, you must use the MQ Host Adapter
- A server application or an application that acts as both a client and server application, the message partner automatically references an MQ connection, so you must also configure an MQ connection. If the message partner corresponds to a server application, do not specify a service list.
Before you can configure message partners for an SAG, you must first approve and deploy the SAG configuration as described in Approving and deploying SAG configuration data.
The
examples in Examples of how to configure an SAG illustrate
how to configure message partners. You might also find the descriptions
of the following SAG configuration and operating commands helpful: