Page History
ServiceNow App
Divbox | ||||||
---|---|---|---|---|---|---|
ui-expand | ||||||
| ||||||
|
DataSync Agent
UI Expand | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
ui-expand | |||||
---|---|---|---|---|---|
| |||||
|
UI Expand | |||||
---|---|---|---|---|---|
| |||||
|
UI Expand | |||||
---|---|---|---|---|---|
| |||||
|
UI Expand | |||||
---|---|---|---|---|---|
| |||||
|
UI Expand | |||||
---|---|---|---|---|---|
| |||||
|
ui-expand | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||
|
Divbox | |||||
---|---|---|---|---|---|
ui-expand | |||||
| Should I configure my DataSync Agent to connect to the Perspectium Mesh via HTTPS or AMQPS? | ||||
When you received your Perspectium Mesh credentials, you may have been given two different addresses. Such as: The choice between these different protocols will vary per customer (largely firewall rules). ServiceNow does not handle AMQP connections, so do not include AMQP within the ServiceNow instance URL for any of your <instance_connection> directives. | |||||
Divbox | |||||
| |||||
|
Security
UI Expand | |||||
---|---|---|---|---|---|
| |||||
|
UI Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
|
UI Expand | |||||
---|---|---|---|---|---|
| |||||
|
UI Expand | |||||
---|---|---|---|---|---|
| |||||
|
UI Expand | |||||
---|---|---|---|---|---|
| |||||
|
UI Expand | |||||
---|---|---|---|---|---|
| |||||
|
UI Expand | |||||
---|---|---|---|---|---|
| |||||
|
UI Expand | |||||
---|---|---|---|---|---|
| |||||
|
UI Expand | |||||
---|---|---|---|---|---|
| |||||
|
Expand | ||
---|---|---|
| ||
The DataSync Agent handles schema changes in your ServiceNow instance as follows:
|
Expand | ||
---|---|---|
| ||
The DataSync AQL Agent leverages the default connection commit strategy of the JDBC driver for which Oracle is auto commit. The agent does not explicitly decide when to perform a commit. The JDBC driver makes this decision. The Agent retrieves a message from the message store in the order they were published, performs the required processing such as decryption, validation etc., possibly determines the type of SQL operation required (such as update or insert), and then issues the request to the database. The Agent then determines the response and does any further processing required. Once completed, the Agent will fetch the next message from the message store in the queue.
|
Can't find what you're looking for?
See additional DataSync Agent troubleshooting topics or browse the Perspectium Community Forum.
...