You are here:

User-Defined Message Processors

Note:

Before you re-assign processor groups from one group to another:
- Allow all messages being processed through the ScribeIn queue to complete
- Pause all publishers and IPs
Otherwise, messages may be orphaned and moved to the dead message queue.
Adding message queues is enabled through your Scribe Insight license. If you need to add message queues but the Integration Server Properties dialog box does not provide a means to do so, contact Sales to upgrade your license.

By default, Insight provides the following processor groups:

DEFAULT — A multiprocess group that processes queue Integration Processes (IP) using any available active processors. The queues associated with this group are:
- Input Queue — SCRIBEIN
- Retry Queue — SCRIBERETRY
- Dead Message Queue — SCRIBEDEADMESSAGE
You can modify these queue associations through Site Settings: Expand Administration and click the Site Settings node. In Site Main Queues, you can reassign these queues to any other shared queue.
SERIAL — A single-processor group that processes time, file, and query IPs using one processor. There are no queues associated with this group.

Integration server properties enable you to define the number of active processors, define message processor groups, and assign message queues to processor groups.

When you define a processor group, a set of SCRIBEIN, SCRIBERETRY, and SCRIBEDEADMESSAGE queues is created. Each queue in this set behaves the same as the queues associated with the DEFAULT group and is given the processor group name as a prefix.

For example, if you define a new processor group, NEWPROCGRP, the following queues are also defined:

NEWPROCGRP_ScribeIn
NEWPROCGRP_ScribeRetry
NEWPROCGRP_ScribeDeadMessage

To redirect generated messages from a File, Time, or Queue IP to NEWPROCGRP, on Step 1 of the Integration Process Properties, select NEWPROCGRP in Processor Group. When this IP runs, on Step 1, all generated messages are initially sent to the SCRIBEIN queue, then the message processor redirects those messages to the NEWPROCGRP_ScribeIn queue.

Note:

Messages are only processed from the SCRIBEIN queue to a NEWPROCGRP queue when the IP configured with NEWPROCGRP is active. For example, if you click Run Now for an IP that is not active, messages generated by that IP are written to the SCRIBEIN queue, but they are not processed to the NEWPROCGRP queues.

If you are running more than one IP and one IP depends on the output from another, assign both IP processes to the SERIAL processor group to ensure that one completes processing before the other begins.