WSO2 is now Choreo LabsLearn more

Trusted AI Governance
Build

Create agents and AI apps with the tools and languages your teams already use.

Connect

Link agents securely to your APIs, data, models and business systems.

Run

Deploy, observe and operate agents and AI apps reliably at any scale.

Govern

Control identity, access, cost and policy for every agent in production.

Agent Management

Developer Platform

  • API Management Cloud

    Design, secure and publish APIs with governance and analytics built in.

    Sign Up Now
  • Integration Cloud

    Connect apps, data and AI agents with low-code and pro-code integration.

    Sign Up Now
  • Identity & Access Management Cloud

    Secure sign-in and access for customers, partners, workforce and agents.

    Sign Up Now
  • Agent Management Cloud

    Build, run and govern AI agents with full visibility and control.

    Sign Up Now
  • Developer Platform Cloud

    Ship cloud-native apps faster on an internal developer platform.

    Sign Up Now

Self-Hosted

Full control over your stack. Deploy directly to your own servers, bare metal, cloud, or Kubernetes environment. Your data never leaves your perimeter.

Product Downloads
Choreo Labs
AI Governance
Platform
Solutions
Resources
Article

Copying the options' properties into RM messages

When reliable message exchanges take place with Apache Sandesha2/Java, you will observe that various RM control messages are exchanged while the application message exchange is taking place. They include RM sequence management messages and RM acknowledgment messages.

Sometimes you may want a certain property in the Options object to be available in all the messages that are created and sent through the handler chain. For example, you may be setting a certain security policy for configuring Apache Rampart/Java. However, you observe that this policy is available only for the application messages, and that the RM control messages are sent without adhering to this security policy.

The remedy for this is to add the following parameter to the Sandesha2 module.XML.

<parameter name="propertiesToCopyFromReferenceMessage">key1,key2</parameter>
<parameter name="propertiesToCopyFromReferenceRequestMessage">key1,key2</parameter>

When you set the first parameter, all the RM messages of the client side will contain the properties you set to the Options object with the keys Key1 and Key2.

The second parameter is for the server side. Here the properties are copied from the request message to the RM messages of the out path.

In addition to the above, if you also want to copy the property 'abc' to the RM messages with the key 'xyz', you can set the above parameter as follows.

<parameter name="propertiesToCopyFromReferenceMessage">key1,key2,abc:xyz</parameter>

You can use this to set two different security policies for Application messages and RM control messages. You may need to sign and encrypt the Application messages but the RM control messages may only need to be signed.

Applies To:

Apache Sandesha2/Java, 1.1 and above.