Use this task to configure a JMS activation specification used
to deploy message-driven beans with the default messaging provider.
Use this task if you want to use a message-driven bean as a Java
Connector Architecture (JCA) 1.5 resource, to act as a listener on the default
messaging JMS provider.
To configure a JMS activation specification
for the default messaging provider, use the administrative console to complete
the following steps. This task contains an optional step for you to create
a new activation specification.
- Display the default messaging provider. In the navigation
pane, expand . This displays in the content pane a table of properties for the
default messaging provider, including links to the types of JMS resources
that it provides.
- Optional: Change the Scope check
box to the scope level at which the activation specification is to be visible
to applications, according to your needs.
- In the content pane, under the Activation specifications heading,
click JMS activation specification. This
lists any existing JMS activation specifications for the default messaging
provider in the content pane.
- Display the properties of the JMS activation specification. If you want to display an existing JMS Activation Specifications, click
one of the names listed.
Alternatively, if you want to create a new JMS
activation specification, click
New, then specify the
following required properties:
- Name
- Type the name by which the activation specification is known for administrative
purposes.
- JNDI name
- Type the JNDI name that is used to bind the activation specification into
the JNDI name space.
- Destination type
- Destination JNDI name
- Type the JNDI name that the message-driven bean uses to look up the JMS
destination in the JNDI name space.
Select the type of destination on the Destination type property.
- Bus name
Specify
the name of the service integration bus to which connections are made. This must be the name of the bus on
which the bus destination identified
by the Destination JNDI name property is defined. The server to which associated
message-driven beans are deployed must be a member of this bus.
You
can either select an existing bus or type the name of another bus. If you
type the name of a bus that does not exist, you must create and configure
that bus before the activation specification can be used.
- Specify properties for the JMS activation specification, according
to your needs .
- Optional: Specify custom properties of the JMS activation specification,
as J2C activation specification custom properties.
- Click OK.
- Save your changes to the master configuration.