Required in Krypton 8.0.5 Release and Newer

This must be set to true for the meshlet to run correctly as Krypton 8.0.5 and newer uses versions of the Spring library (for security fixes) that require this configuration.

spring:
    main:
      allow-circular-references: true

Host name for connecting to the Perspectium Integration Mesh.

spring:
   rabbitmq:
      host: localhost

The AMQP or AMQPS port for connecting to the Perspectium Integration Mesh. The value for this configuration is generally 5672 for connecting over AMQP or 5671 for a secure connection over AMQPS (SSL).

spring:
   rabbitmq:
      port: 5671

Username for connecting to the Perspectium Integration Mesh.

spring:
   rabbitmq:
      username: testuser

Password for connecting to the Perspectium Integration Mesh.

spring:
   rabbitmq:
      password: password123

 Your virtual space (vhost) in the Perspectium Integration Mesh. This value will generally be provided to you by Perspectium Support.

spring:
   rabbitmq:
      vhost: /

Sets the meshlet to be the exclusive consumer of messages in the queue specified in the below perspectium.message.inboundQueue configuration. When this value is true, any other meshlet that tries to connect to the queue will be denied access until this meshlet is no longer connected. Using this value as true prevents other meshlets (such as a test or dev meshlet) from consuming messages on accident.

This can also be useful for high availability when you are running two meshlets at once. The first meshlet ran will continue to access and consume the queue while the second meshlet will continually retry every 30 seconds. If the first meshlet should die and lose connection, then the second meshlet will start connecting to consume messages.

spring:
   rabbitmq:
      exclusive: true

Enables a secure connection over AMQPS (SSL) to RabbitMQ. The spring.rabbitmq.port configuration above will also need to be an AMQPS port that accepts secure connections. 

spring:
   rabbitmq:
      ssl: 
         enabled: true

Represents the queue in the Integration Mesh that the meshlet will consume messages from.

perspectium: 
   message:
      inboundQueue: psp.in.meshlet.servicenow.incident.psp_demo

Queues are generally in the following format:

DataSync:

psp.in.meshlet.<application>.<customer/key>

Example: psp.in.meshlet.servicenow.psp_demo.

ServiceBond:

psp.in.meshlet.<application>.<process>.<customer/key>

Example: psp.in.meshlet.servicenow.incident.psp_demo.

For more information on how to name your queues, contact Perspectium Support.

Represents the queue in the Integration Mesh that the meshlet will be publishing messages to. This is normally a ServiceNow instance, such as another application that is being integrated with ServiceNow sending messages (records) to the instance. 

perspectium: 
   message:
      inboundQueue: psp.out.servicenow.dev123456

Enabling this configuration will wrap all outbound message fields in a CDATA section. This is useful for when you have a ServiceBond integration with an API that receives XML payloads.

perspectium: 
   message:
      wrapCDATA: false

Enabling this feature will limit the meshlet to only process messages that have a key matching the value specified in this configuration. Perspectium applications generate messages that include a key field that represents the key of where the messages was generated from. In the case of ServiceNow, this is the instance name i.e. dev12345.

With this feature, the meshlet will only process messages with the matching key and skip all other messages. This allows you to filter out any messages so the meshlet is reading messages from only one source.

perspectium: 
   message:       
      instanceKey: dev12345

If this configuration is not specified, the meshlet will process all messages it consumes from its inbound queue.