Properties tab

The Thread, Inbound, and Outbound tabs contain the configurations for the protocol thread.

The Properties tab (default) distinguishes each thread (connection) from other threads and to which process each thread belongs.

This table shows property parameters:
Parameter Description
Thread Name This is the connection name that displays on the thread icon.

The thread name is also used as the embedded recovery/error database’s user name. Because of this, there is a possible conflict when a configured thread has the same user name used by the hcidbdump utility. If you must have a thread named _hcidbdump_, then run hcidbdump with the -U option to select an alternate user name to use for hcidbdump.

Bitmap This is the file name that contains the bitmap for the connection icon. This is the image that displays on the thread icon. Click List to specify a bitmap in another file.
Process Name This is the name of the engine process that controls this thread. The menu lists all configured processes.
Group Names This is for the names of the thread groups to which this thread belongs. Use thread groups to control and monitor related threads. One or more strings can be used to limit views.
Engine Log Configuration This is the alias for Engine Output (EO) configuration information. This controls how much output to write to the process log for this thread. Click List to open the EO Configuration selection dialog box.
Protocol This is the communication protocol for the thread. Click the arrow to open a list of available formats. Then, click Properties to configure the protocol properties for that format.

Icons shown are based on the selected thread protocol. After a protocol is changed in the thread properties, the icon is also changed. If you have already specified a custom icon in the thread properties, then the custom icon is used regardless of the selected protocol.

Encoding The selection in this field applies to inbound and outbound messages. Inbound messages are converted from the specified encoding to Unicode and outbound messages are converted from Unicode to the specified encoding.

You can configure the menu list by editing the [encoding] list in %HCIROOT\server\i18n.ini.

XML Encoding This applies to inbound and outbound messages. It indicates that the encoding of each message is dynamically determined from an XML declaration in the message. If XML Encoding is selected and no XML declaration is found in a message, then UTF-8 encoding is assumed. This is the default for XML documents.
HL7 Encoding This applies to inbound and outbound messages. It indicates that the encoding of each message is dynamically determined from value of MSH.18 in the HL7 message. If HL7 Encoding is selected and no value of "MSH.18" is found in a message, then UTF-8 encoding is assumed. This is the default for HL7 message.
Inter-Site Routing Port Inter-site routing routes to a destination thread that is located in another site and even on another host. See Inter-site routing.
Error Database Procs The error database TPS gives you a control point before a message is written to the error database. This means you have the opportunity to change the error message content and to route the message to another context.
Retries This is the maximum number of times to attempt message transmission:
  • "0" is the initial transmission only.
  • "1" is the initial transmission plus one retry.
  • "-1" is unlimited retries.
Auto-Start Connection Select this to start the thread automatically whenever the specified engine process is started.
Use Recovery Database The use of the recovery database is determined at the inbound level. This controls saving inbound or outbound messages, and inbound message logging. The engine does not use the recovery database when the outbound thread is checked and the inbound thread is unchecked. Any file name can be entered.

After a message is marked for recovery, it is backed by the recovery database throughout its life in the engine.

Messages that are tagged for disk-based queuing are backed by the recovery database throughout their life in the engine.

The recovery database backs up the thread and process queues. If an engine process or thread stops running, then it retains the message data in the recovery database when the thread or process is restarted.

Enable message tracing (thread level) When this is selected, tracing information is saved with the message trace framework to the tracing database.

Message tracing is enabled on the process level or thread level.

If process level tracing is enabled, then there is no requirement to turn on tracing for each individual thread under the process. If process level tracing is disabled, then tracing for a thread is enabled with the thread level option.

In thread level tracing, selecting this turns on tracing for a specific thread.

Messages routed to this connection treated as inbound Select this to make the destination behave as inbound, not outbound, so that you can route messages that are delivered to the destination site.