User Tools

Site Tools


amqp_replicator

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
amqp_replicator [2016/09/28 14:49]
howie [Configuration]
amqp_replicator [2019/04/09 12:43] (current)
paul.jensen found another incorrect spelling of Perspectium
Line 9: Line 9:
 =====AMQP Handler===== =====AMQP Handler=====
  
-Perspectium’s Message bus leverages AMQP technology. Currently, the implementation in use is the Rabbit MQ platform. Data that is shared or published from a ServiceNow instance using either Perspectium’s bulk share or dynamic sharing solutions is staged within the Perspectium Cloud. In cases where a customer want to leverage their own Rabbit MQ platform to house the data replicated from the ServiceNow instance they can use the Perspectium AMQP handler which runs as a task within the Perspecitum ​Replicator Agent will move the replicated data from the Perspectium Cloud Message Bus to the customer’s on premise AMQP environment. The Replicator agent can be run from within the Perspectium Cloud or on the customer’s premise.+Perspectium’s Message bus leverages AMQP technology. Currently, the implementation in use is the Rabbit MQ platform. Data that is shared or published from a ServiceNow instance using either Perspectium’s bulk share or dynamic sharing solutions is staged within the Perspectium Cloud. In cases where a customer want to leverage their own Rabbit MQ platform to house the data replicated from the ServiceNow instance they can use the Perspectium AMQP handler which runs as a task within the Perspectium ​Replicator Agent will move the replicated data from the Perspectium Cloud Message Bus to the customer’s on premise AMQP environment. The Replicator agent can be run from within the Perspectium Cloud or on the customer’s premise.
  
 ====Replicated Data==== ====Replicated Data====
Line 51: Line 51:
 If the table had contained additional records or rows then they would also be published to the customer’s AMQP environment with the only difference being the value of the u_name column. If the table had contained additional records or rows then they would also be published to the customer’s AMQP environment with the only difference being the value of the u_name column.
  
-In the following example the action is update and the new value is ‘Mr. Billy Wong’. In cases where the publisher of the data is the Perspecitum ​technology running within a Service-Now instance the row will always include the sys_id column, which is a globally unique identifier for the row. This field can therefore be used to perform a lookup in another repository to determine if it already exists and if so a true update would be performed. If the row cannot be located using the sys_id then it could just be added to the repository.+In the following example the action is update and the new value is ‘Mr. Billy Wong’. In cases where the publisher of the data is the Perspectium ​technology running within a Service-Now instance the row will always include the sys_id column, which is a globally unique identifier for the row. This field can therefore be used to perform a lookup in another repository to determine if it already exists and if so a true update would be performed. If the row cannot be located using the sys_id then it could just be added to the repository.
  
 <code xml> <code xml>
amqp_replicator.1475099351.txt.gz · Last modified: 2016/09/28 14:49 by howie