This section only describes message sender functionality that is only related to the XAI/MPL processing. Refer to Define the Message Sender for details about other types of senders that are supported independent of XAI/MPL.
Message senders are responsible for define outgoing message destinations and for " responding" to the XAI executer.
For each sender, you must reference an appropriate Message Class. The information in this section describes the sender classes that are provided with the system.
You must create senders to "respond" to the various staging table receivers in the system.
Next, design the senders for "responses" to other receivers, for example the JMS queue receiver or JMS topic receiver. The system provides message classes to use for these senders. Use the class JMSSENDER for a JMS queue sender and TPCSNDR for a JMS topic sender.
Finally, review all your outgoing messages and determine the mechanism for communicating with the target system for each message.
If you want XML messages to be written to a flat file, use a flat file sender. For example, it can be used in the notification download process to write a response message to a flat file. Flat file senders should reference an Message Class of FLATFILESNDR. In addition, the following context records should be defined for senders of this type.
Context Type | Description | Values |
---|---|---|
Flat file output directory | Directory in the file system where to write the file | |
Flat file filename pattern |
The name of the output file. The file name may be a literal constant, or generated dynamically. To create a dynamic filename use <file name>$$ID, where $$ID is replaced at run time by the ID of the NDS message that triggered the response message. If no file name is defined for the sender, the XAI server generates a file name with the following format 'XAI$$ID.xai'. |
|
Append data to file | This parameter controls whether the content of the response message is appended to an existing file, or a new file is created (possibly replacing an existing one). | YES or NO |
Character Encoding | Indicates if the message should be sent with character encoding. The sender will write the content of the file with encoding specified in the context value. If no value is specified, the sender uses the default Java system encoding, which is determined according to the operating system locale. | UTF-8 or UTF-16 |
The topics below describe configuration required for senders that route a message via an HTTP sender, a flat file sender or an email sender.
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]