Sample policies and applications are provided with the default pattern that configure sample policies and sample JNDI destinations.
The policies in WSRR also have a custom property field added called PolicySelector. For SampleRoutingSchedule01, this value is set to GID007 and for SampleRoutingSchedule02 this value is set to GID008. The PolicySelector value is provided by the client as part of the JMS message header and the matching policy is enforced by the message flow.
The default JNDI destinations
created in the SOA Policy Pattern: Create Sample JNDI Bindings
script
package are DESTINATION1_OUT and DESTINATION2_OUT, and the respective
MQ queues DESTINATION1_OUTQ and DESTINATION2_OUTQ.
Two sample JMS clients are provided with this pattern. The SendJMSMessage and ReceiveJMSMessage Java™ sample clients are located in /opt/ibm/mqsi/8.0.0.1/sample/JMSSendReceive in the installation directory.
java com.ibm.jms.SendJMSMessage <Location JNDI Bindings> <InputTextMessage>
<PolicySelector Value>
java com.ibm.jms.SendJMSMessage file:///home//virtuser//JNDI-DIR
'<data><msg>11</msg></data>' GID007
java com.ibm.jms.ReceiveJMSMessage <Location JNDI Bindings> <Output JMS Destination>
java com.ibm.jms.ReceiveJMSMessage file:///home//virtuser//JNDI-DIR DESTINATION1_OUT
SOA Policy Pattern: Create Sample Policiesand
SOA Policy Pattern: Create Sample JNDI Bindingsscript packages from the cloned IBM SOA Policy Pattern. After removing these optional script packages, you can deploy the cloned IBM SOA Policy Pattern and use the deployed instance of the pattern. For more details about WSRR policy management and managing JMS destinations on the deployed instance, see Working with the deployed instance.