User Tools

Site Tools


replicator_snc_multiple_subscriber_jobs

Multiple Subscriber Jobs

Dubnium

The Perspectium Replicator Subscriber job in ServiceNow pulls and processes the messages from your MBS server’s inbound queues. However, you can also choose to prioritize the processing of your inbound messages by configuring the Perspectium Replicator Inbound Processor job to apply various filters.

Note that you are encouraged to learn more about the Perspectium Replicator Subscriber and Perspectium Replicator Inbound Processor jobs before continuing with the procedure below.

Procedure

(!) WARNINGS: This is a advanced capability for the Replicator so we recommend running this through your test environments first. It is important to know that the purpose of this is to have greater control in how / when you are Subscribing your data.

To configure the Perspectium Replicator Inbound Processor job, follow these steps:

1. In ServiceNow’s left-hand navigation sidebar, navigate to Perspectium > Replicator Properties.

2. In the Perspectium Replicator Properties form, check the box for “Enable to allow the Replicator Inbound messages to go to a state of ready instead of being consumed immediately. Thus allowing multiple configurable scheduled jobs to pick up messages and run concurrently.”

3. Navigate to Perspectium > Control and Configuration > All Scheduled Jobs. Then, in this table, search for and click to open the Perspectium Replicator Inbound Processor job.

4. Within the script for this job, scroll to locate the *’addCustomQuery’* function on line 50. Here, you can modify the script by adding any customer queries.

(a) By Key Examples

Example 1:

key in message must be equal to “dev12345” in order to be consumed by the Inbound Processor job.

function addCustomQuery(igr) {
    // Example: igr.addQuery("key", "=", "dev12345");
}

Example 2:

key in message must not be equal to “dev12345” in order to be consumed by the Inbound Processor job.

function addCustomQuery(igr) {
    // Example: igr.addQuery("key", "!=", "dev12345");
}

(b) By name Examples

Example 1:

Only process messages that contain the “name” of “incident”.

function addCustomQuery(igr) {
    // Example: igr.addQuery("name", "CONTAINS", "incident");
}

Example 2:

Only process the messages that are either incident or task.

function addCustomQuery(igr) {
    // Example: igr.addQuery("name", "IN", "incident, task");
}

NOTE: By default, if no filters are added to the Perspectium Replicator Inbound Processor, all messages coming in the inbound table will go to a state of Ready and be consumed by the order in which they arrived.

5. Click Update to save your modified script.

replicator_snc_multiple_subscriber_jobs.txt · Last modified: 2019/01/02 12:12 by timothy.pike