Viewing JMS bindings on references and services of SCA composites using scripting (deprecated)
You can view information on a Java™ Message Service (JMS) binding for a Service Component Architecture (SCA) composite. Use scripts for viewing composition units in business-level applications. The scripts display information on settings of a binding.jms element.
Before you begin
An SCA composite that uses JMS bindings must be a composition unit in a business-level application. To view settings for a JMS binding on references, the composite must have defined a JMS binding in the reference. Similarly, to view settings for a JMS binding on services, the composite must have defined a JMS binding in the service.
About this task
After deployment of an SCA composite that uses JMS bindings, you can view the JMS binding settings. For information on the settings, refer to JMS binding settings for SCA composites or Section 1.4 of the SCA JMS Binding specification, Version 1.00.
Procedure
Results
After the viewCompUnit command runs, the product displays information on the composition unit, including information on references or services that are defined in the JMS binding of the SCA composite.
Example
Suppose that you have an SCA composite composition unit
named myJmsBindingComposite
that has defined JMS
bindings and a business-level application named myJmsBLA
that
contains the composition unit.
Run the viewCompUnit command to view information on the JMS binding settings.
- Using Jython:
AdminTask.viewCompUnit('[-blaID WebSphere:blaname=myJmsBLA -cuID WebSphere:cuname=myJmsBindingComposite]')
- Using Jacl:
$AdminTask viewCompUnit {-blaID WebSphere:blaname=myJmsBLA -cuID WebSphere:cuname=myJmsBindingComposite}
Running the viewCompUnit command displays information resembling the following on the JMS binding sections:
JMS Binding attributes (ReferenceJMSBinding)
Specify JMS binding attributes for the composite defined in this SCA application.
Correlation Schema (correlationSchema): [RequestMsgIDToCorrelID]
Initial Context Factory (initialContextFactory): [com.ibm.websphere.naming.WsnInitialContextFactory]
jndiURL (jndiURL): [iiop://localhost:2809]
Request Connection (requestConnection): [myService]
Response Connection (responseConnection): [myReference]
Request Wire Format (requestWireFormat): [wireFormat.jmsTextXML]
Response Wire Format (responseWireFormat): [wireFormat.jmsTextXML]
JMS Binding Resources attributes (ReferenceJMSBindingResources)
Specify JMS binding resource attributes for the composite defined in this SCA application.
Component Name/Reference Name (resourceName): [myJMSFrontendComponent/helloWorldService]
Destination Name (destinationName): [jms/SCA_JMS_Request1]
Connection Factory Name (connectionFactoryName): [jms/SCA_JMS_CF]
Destination Type (destinationType): [queue]
JMS Binding Response Resources attributes (ReferenceJMSBindingResponseResources)
Specify JMS binding response resource attributes for the composite defined in this SCA application.
Component Name/Reference Name (resourceName): [myJMSFrontendComponent/helloWorldService]
Response Destination Name (responseDestinationName): [jms/SCA_JMS_Response1]
Response Connection Factory Name (responseConnectionFactoryName): [jms/SCA_JMS_CF]
Response Destination Type (responseDestinationType): [queue]
...
What to do next
Examine the displayed information to ensure that the JMS binding settings are correct.
Edit the JMS binding resource and response resource JNDI name settings as needed using the editCompUnit command.