Message Sender - Main

To define a new sender, open Admin, and then Integration, and then 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.

Indicate the Message Class for this sender, which indicates the method used to route the message. The valid 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.

Note:

For backward compatibility, the sender class HTTPSNDR is also supported, but should only be used if indicated by a specific integration configuration.

Indicate whether or not this sender is currently Active.

For JMS related senders, indicate whether the Message 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.