Use this page to view property settings for a Java Message Service (JMS) binding that connects Service Component Architecture (SCA) composite references or services. Also use this page to edit resources of the JMS binding. The settings shown on this page define a binding.jms element.
To view this administrative console page, your composition unit must support a JMS binding reference or service. In the administrative console, do the following:
You can use a JMS binding to identify existing JMS resources using Java Naming and Directory Interface (JNDI) names.
Specifies property settings that apply to all binding.jms elements. The settings pertain to both services and references. You cannot edit the settings.
The URI has the following format:
jms: jms_destination?
connectionFactoryName=connection_factory_name &
destinationType={queue|topic} &
deliveryMode=delivery_mode &
timeToLive=time_to_live &
priority=priority &
user_property=user_property_value & ...
Valid values are requestmsgidtocorrelid (the default), requestcorrelidtocorrelid, and none.
This setting is optional. If no factory is specified, the WebSphere® Application Server initial context factory is used.
A request is a message that is sent to an SCA service or sent by an SCA reference.
A response is a message received by a reference (that is, a reply from an invoked service) or a message sent by a service in response to a previous request message. A response in SCA is always a reply to a previous request.
For example, wireFormat.jmsObject.
A request is a message that is sent to an SCA service or sent by an SCA reference.
For example, wireFormat.jmsObject.
A response is a message received by a reference (that is, a reply from an invoked service) or a message sent by a service in response to a previous request message. A response in SCA is always a reply to a previous request.
Specifies resources for the JMS binding. You can both read and edit resource settings for Destination JNDI name, Activation specification JNDI name, and Connection factory JNDI name. All other resource settings are read-only.
This setting is for both services and references and is read-only.
@type is the destination type.
You can set a destination name for both services and references.
@name is the JNDI name of the destination.
Valid values are ifnotexist (the default), always, and never. When the value is ifnotexist, the product dynamically creates destination resources necessary for the SCA composite, if those resources do not exist and relate to the default messaging provider. The product creates the resources when adding the SCA composite to a business-level application.
The product validates a composite definition when adding an SCA asset to a business-level application. If the validation results in an error, the product does not add the asset to the application. If the value is always and the destination exists, deployment stops with an error.
You can set an activation specification for services only.
The attributes of this element follow those defined for the destination element.
Valid values are ifnotexist (the default), always, and never. When the value is ifnotexist, the product dynamically creates activation specification resources necessary for the SCA composite, if those resources do not exist and relate to the default messaging provider. If the value is always and the activation specification exists when the SCA composite is added to a business-level application, deployment stops with an error.
You can set a connection factory JNDI name for references only.
The attributes of this property follow those defined for the destination element. This property is mutually exclusive with the activationSpec property.
Valid values are ifnotexist (the default), always, and never. When the value is ifnotexist, the product dynamically creates connection factory resources necessary for the SCA composite, if those resources do not exist and relate to the default messaging provider. If the value is always and the connection factory exists when the SCA composite is added to a business-level application, deployment stops with an error.
Specifies the resources used for handling response messages, receiving responses for a reference, and for sending responses from a service. A response element defines the destination and either the connection factory or activation specification elements for handling response messages.
Response resources pertain to both services and references. You can both read and edit resource settings for Response destination JNDI name and Response connection factory JNDI name. All other resource settings are read-only.
This setting is for both services and references and is read-only.
You can set a destination name for both services and references.
Valid values are ifnotexist (the default), always, and never. When the value is ifnotexist, the product dynamically creates response destination resources necessary for the SCA composite, if those resources do not exist and relate to the default messaging provider. If the value is always and the response destination exists when the SCA composite is added to a business-level application, deployment stops with an error.
You can set a response connection factory for both services and references.
The attributes of this element follow those defined for the destination element. This element is mutually exclusive with the activationSpec element.
Valid values are ifnotexist (the default), always, and never. When the value is ifnotexist, the product dynamically creates response connection factory resources necessary for the SCA composite, if those resources do not exist and relate to the default messaging provider. If the value is always and the response connection factory exists when the SCA composite is added to a business-level application, deployment stops with an error.
Specifies JMS header properties that apply to requests from a reference. You cannot edit the header properties.
If a JMS header property is specified, the property must not appear in the URI.
Specifies JMS header properties that apply to responses from a service for outbound messages. You cannot edit the header properties.
If a JMS header property is specified, the property must not appear in the URI.