Message Sender - Main
To define a new sender, open Admin > Integration > Message Sender.
Description of Page
Enter a unique Message Sender and Description.
CAUTION:
Important! When adding new records, carefully consider the naming convention of the message sender code. Refer to System Data Naming Convention for more information.
Set Invocation Type to Real-time.
Note:
The invocation type MPL remains in the product for upgrade purposes but is not recommended.
Indicate the Message Class for this sender, which indicates the method used to route the message. The real-time sender classes are as follows:
Message Class
Description
RTEMAILSNDR
Email sender.
RTHTTPSNDR
HTTP sender.
RTJMSQSNDR
JMS queue sender.
RTJMSTSNDR
JMS topic sender.
RTJSONSNDR
HTTP JSON sender.
SOAPSNDR
HTTP SOAP sender.
The following sender classes are related to MPL processing and remain in the product for upgrade purposes:
Message Class
Description
DWNSTGSNDR
Download Staging sender.
EMAILSENDER
Email sender.
FLATFILESNDR
Flat file sender.
HTTPSNDR
HTTP sender.
JMSSENDER
JMS Queue sender.
OUTMSGSNDR
Outbound Message sender.
STGSENDER
Staging Upload sender.
TPCSNDR
JMS Topic sender.
UPLDERRHNDLR
Upload Error Handler.
Indicate whether or not this sender is currently Active.
For JMS related senders, indicate whether the MSG Encoding is ANSI message encoding or UTF-8 message encoding. (Note that for all other types of senders, the Character Encoding context type is used to configure encoding.)
If the Message Class is one that connects to a JMS Queue or JMS Topic, indicate the appropriate JMS Connection
Fastpath:
Refer to JMS Connection for more information.
If the Message Class is one that connects to a JMS queue, indicate the name of the JMS Queue to define where the message is to be sent.
Fastpath:
Refer to JMS Queue for more information.
If the Message Class is one that connects to a JMS topic, indicate the name of the JMS Topic to define where the message is to be sent.
Fastpath:
Refer to JMS Topic for more information.
The XAI JDBC Connection remains for legacy purposes but is not applicable for supported functionality.