Inbound pane

This table shows the configurable inbound pane parameters:

Parameter Description
Use byte order mark This applies to inbound messages only. A byte order mark is a pre-defined sequence of bytes at the start of a message that defines both the byte order and the encoding. When a byte order mark is found, it overrides any encoding specified in the Encoding field. A byte order mark also overrides an XML declaration in XML mode. The byte order mark is not required, and if one is not found, Encoding and XML Encoding operate as they should.

Supported byte order marks are:

  • FE FF

    Endian Order: Big

    Encoding: UTF-16BE

  • FF FE

    Endian Order: Little

    Encoding: UTF-16LE

  • EF BB BF

    Endian Order: N/A

    Encoding: UTF-8

Big Endian, or BE, means that the most significant bytes happen first and the least significant bytes happen last. Little Endian (LE) is the reverse.

The byte order does not apply to UTF-8 encoding, although the UTF-8 byte order mark is valid.

Because byte order marks are valid for more esoteric encodings similar to UTF-7, these are extremely rare and are not supported.

The byte order mark is stripped from the inbound message before encoding conversion.

Save Inbound Messages

Click this to save inbound message data to a SMAT database file. Messages are saved to this file before any further work in the engine. This provides a backup of the data as it was received from the sending system.

You can configure the file name to populate with a default value by configuring the default value on the Client Preferences NetConfig/NetMonitor tab. Click Advanced to open the Configure Default Values dialog box. Select an option from the menu, or specify one in the field.

For example, a thread named conn_1 has values of @threadname@_in and @threadname@_out. When Save Inbound Messages is selected, the file names automatically populate with conn_1_in and conn_1_out.

Save inbound resent messages

Select this to save inbound resent messages to the SMAT Database file.

This setting is related to the selection of Save inbound messages. This option is enabled only when Save inbound messages is selected.

For this option, the INSAVERESENTMSGTOSMAT key is in the NetConfig file.

For additional information, see the "Save inbound resent messages" after this table.

File Specify the file name for the SMAT file, if Save Inbound Messages is selected. This file is located in %HCISITEDIR\exec\processes\processname\smat file name.
Message Archiving Archives the inbound message after SMAT messages are saved. Both inbound and outbound messages are archived in UTF-8 encoding, but not the original encoding.

These messages should not be used for resending to system threads.

Message archiving is independent from SMAT.

When Message Archiving is selected, Setup is enabled. Clicking this opens the Setup Message Archiving dialog box.

Msg Engine Log Configuration This is the engine output alias that describes how much output to write to the process log for each message. Click List to open the In Message EO Config selection dialog box.

Saving inbound resent messages

The Save inbound resent messages function has been added to all Thread Properties and Resend dialog boxes. The thread properties setting takes precedence.

Note: Users decide if messages are traceable, or not.

This option is available only when resending messages to the engine, and not a file.

Usage:

  • In the Thread Properties dialog boxes, when you select Save inbound resent messages, resent messages are saved and the dialog box option is disabled. Users cannot change this setting.
  • In the Thread Properties dialog boxes, when you do not select Save inbound resent messages, the dialog box option is enabled. Select this to save the resent message.

Save inbound resent messages only takes effect when resending to inbound pre-TPS.

Resending to other queues is out-of-scope based on the current implementation of this flag.