Versions Compared

Old Version 2

changes.mady.by.user user-b885f

Saved on

compared with

New Version 3

changes.mady.by.user user-b885f

Saved on

Key

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

The below configurations are  The file that controls the configuration settings for Meshlet meshlet is the application-dev.yml file. This file contains configurations that are needed for the Meshlet meshlet to run. 

UI Text Box
typetip

The keys described below are only the essential configurations that must be set for your Meshletmeshlet. Additional configuration configurations will depend on your integration, see the respective documentation (such as  as DataSync for Snowflake or ServiceBond for Jira) or  for further details.



Spring

RabbitMQ Configuration

Meshlets connect to the Perspectium Integration Mesh over AMQP or AMQPS. To configure your connection to the Perspectium Integration Mesh, you  you will need to include the following keysconfigurations under spring.rabbitmq: 


KeyDefault ValueDescription

host


Host name for connecting to the Perspectium Integration Mesh.

Code Block
languageyml
spring:
   rabbitmq:
      host: localhost


port 

A port number that the transferring data will useThe AMQP or AMQPS port for connecting to the Perspectium Integration Mesh. The value for this configuration is generally 5672 (AMQP) or 5671 (AMQPS secure SSL connection).

Code Block
languageyml
spring:
   rabbitmq:
      port: 12345671


username

Username for connecting to the Perspectium Integration Mesh.

Code Block
languageyml
spring:
   rabbitmq:
      username: georvioloan


password

Password for connecting to the Perspectium Integration Mesh.

Code Block
languageyml
spring:
   rabbitmq:
      password: password123


vhost

 Virtual host name for connecting to  Your virtual space (VHost) in the Perspectium Integration Mesh. This value will generally be provided to you by Perspectium Support.

Code Block
languageyml
spring:
   rabbitmq:
      vhost: /


exclusivetrue

Sets the outbound queue as an exclusive consumer queue. 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 This can be use when you are running two Meshlets meshlets at once. The first Meshlet ran will be prioritized over the second Meshletmeshlet 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.

Code Block
languageyml
spring:
   rabbitmq:
      exclusive: true


ssl:

   enabled


false

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

Code Block
languageyml
spring:
   rabbitmq:
      exclusivessl: 
         enabled: true




Perspectium

Message Configuration

To configure which queue will receive or send messagesPerspectium-related properties including which queues to connect to in the Integration Mesh, you will need to include the following keysconfigurations under perspectium.message: 


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

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

KeyDefault ValueDescription

inboundQueue


Represents the shared queue on the provider instance. in the Integration Mesh that the meshlet will consume messages from.

Code Block
languageyml
perspectium: 
   message:
      inboundQueue: psp.in.meshlet.servicenow.incident.psp_demo

Queues are generally in the In DataSync integration, the value will have the following format:

DataSync:

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

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

In ServiceBond integration, the value will have the following format:

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

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

Code Block
languageyml
outboundQueue

Represents the subscribed queue on the provider 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. 

Code Block
languageyml
perspectium: 
   message:
      inboundQueue: psp.out.servicenow.dev123456


wrapCDATAfalse

Enabling the key 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.

Code Block
languageyml
perspectium: 
   message:
      wrapCDATA: false




Example of an application-dev.yml

The example below shows a basic configuration of the YAML file. Additional configuration will depend on your integration, i.e. a bi-directional integration between ServiceNow and Ivanti. 

Code Block
languageyml
spring:
   rabbitmq:
      host: localhost
      port: 5672
      username: georvioloan
      password: password123
      vhost: /
      exclusive: false
perspectium:
   message:
      inboundQueue: psp.in.meshlet.servicenow.incident.psp_demo
      outboundQueue: psp.out.servicenow.dev123456
      wrapCDATA: false