Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Help

Blue Integrator Messages

To Blue Integrator, each message consists of a Message Body and a Message Context. The Message Body is the physical message content. The Message Context is a set of named properties.

Message Context properties can be set automatically on Message Receive or Message Send (configured via the Receive Port Configuration Form and the Send Port Configuration Form), can be set by a Map (configured as output parameters in the Map Editor), or can be set explicitly in VSTA code for a Workflow. Every message has MessageID and Timestamp Message Context properties.  Additionally, different Receive Transport providers populate various Message Context properties as messages are received, such as ReceiveLocationType, FileName and ReceiveFolder.  You can see the Message Body and Message Context Properties using Tracking.

See A Simple Messaging Scenario for an example.