Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


HTML
<style>
.release-box {
	height: 30px; 
	width: 100px; 
	padding-top: 8px;
	text-align: center; 
	border-radius: 5px; 
	font-weight: bold; 
	background-color: #d4af37; 
	border-color: #FCE28A;
}

.release-box:hover {
  	cursor: hand;
    cursor: pointer;
    opacity: .9; 
}
</style>
<meta name="robots" content="noindex">

<div class="release-box">
<a href="https://docs.perspectium.com/display/gold" style="text-decoration: none; color: #FFFFFF; display: block;">
Gold
</a>
</div>



Outbound messages are sent out by a single job Perspectium MultiOutput Processing, which goes to your outbound messages table and sends the messages out per queue. This process should cover most cases for sending outbound messages. However, if you are sending a high volume of messages to a single queue or spreading your messages across a high volume of queues, then you can use Multiple MultiOutput JobsThe core concept behind Multiple MultiOutput Jobs is the ability to pass in an encoded query to the MultiOutput job to limit the scope of these jobs. In other words you can have multiple jobs responsible for their own unique subset of outbound messages.

(info) NOTE: We DO NOT recommend for you to clone the default Perspectium MultiOutput Processing without making the following changes. Doing so can cause you to send the same set of messages out multiple times.


Get started using Replicator Tools

Learn how to create multiple MultiOutput jobs using the replicator tool. 

Get started manually

Learn how to create multiple MultiOutput jobs by manually creating the MultiOutput jobs. 

Warnings

This is an advanced capability for the Replicator so we recommend running this through your test environment first.

(info) NOTEIt is important to know that the purpose of these strategies is to send outbound messages with multiple jobs without any overlap in data transit.

Original Job

The original job Perspectium MultiOutput Processing will go through each queue without any encoded query within it. If you do go down this path, you should either modify or de-activate this job to make sure your jobs are each processing their own subset of data.

You may place a X at the start of the name (XPerspectium MultiOutput Processing) to avoid the job from being auto restarted from the Start All Jobs. Follow Perspectium Update Set Releases to maintain these jobs.

Dot Walking

From an optimization standpoint, we do not recommend dot-walking with the queries. I.E. do not pass in an encoded query like:

Code Block
languagejs
var encodedQuery = "u_target_queue.u_nameLIKEdev18450"
var psp = new Perspectium();
psp.processMultiOutput(encodedQuery);

Overloaded Scheduler

A ServiceNow production instance will generally have 4 nodes that can execute 8 jobs each for a total of 32 available workers, so you can create a job per queue. Jobs can vary from a bulk share or a single MultiOutput processing.

(warning) WARNING: Be aware of the total available workers on your instance. For example, you should not create 16 individual MultiOutput processing jobs on a 4 node instance, doing so may take 16 of the 32 available workers and accelerate your processing. Thus, be aware of the environment of your instance to avoid affecting the job processing.




Similar topics


Content by Label
showLabelsfalse
max5
showSpacefalse
sortmodified
cqllabel = "optional-config" and parent = "6096035"

Contact Perspectium Support


US: 1 888 620 8880

UK: 44 208 068 5953

support@perspectium.com