Mediation modules make use of resources provided by the service integration technologies of WebSphere Application Server. Mediation
modules can also make use of a range of resources, including those provided
by the Java Message Service (JMS) and common event infrastructure.
To administer the resources for mediation modules, you can use the WebSphere
administrative console, commands, and scripting tools.
For more information about managing resources for mediation modules, see
the related topics.
Service integration technologies
Service
integration resources, such as bus destinations, enable a mediation module
to use
service integration technologies.
Queue destinations are used by the SCA runtime exploited by the mediation
module as a robust infrastructure to support asynchronous interactions between
components and modules. When you install a mediation module into
WebSphere ESB,
the destinations used by a module are defined on a member of the
service integration bus called
SCA.SYSTEM.
cell_name.Bus. These bus destinations are used
to hold messages that are being processed for components of the mediation
module that use asynchronous interactions:
- Queue sca/module_name
- This is the destination used to buffer asynchronous requests sent to module module_name
- Queue sca/module_name/export/export_name
- This is the destination used to buffer asynchronous requests routed to
module export export_name.
- Queue sca/module_name/exportlink/export_name
- This is the destination used by the export to send asynchronous requests
into the module. Requests are routed to the component target linked to the
export.
- Queue sca/module_name/component/component_name
- This is the destination used to buffer asynchronous requests sent to component component_name
- Queue sca/module_name/component/component_name/source/source_name
- This is the destination used to buffer asynchronous requests routed to
the component source import source_name.
- Queue sca/module_name/component/component_name/target/target_name
- This is the destination used to buffer asynchronous requests routed to
the component target export target_name.
- Queue sca/module_name/import/import_name
- This is the destination used to buffer asynchronous requests sent to import import_name.
- Queue sca/module_name/importlink/import_name
- This is the destination used by the import to send asynchronous requests
out of the module. Requests are routed to the module export linked to the
import.
- Queue sca/module_name/import/sca/dynamic/import/scaimport
[for SCA binding]
- Queue sca/module_name/import/sca/dynamic/import/wsimport
[for Web service binding]
- Queue sca/contextStore/module_name

For each of the destinations, a queue point is also created
defined on the messaging engine of the bus member.
You can deploy and
use mediation modules without needing to manage these resources. However,
you might want to adjust the configuration of the resources (for example,
to modify the maximum messaging quality of service used) or to use them in
locating messages for troubleshooting.
Java Message Service (JMS)
JMS resources enable
a mediation module to use asynchronous messaging as a method of communication
based on the Java Message Service (JMS) programming interface. For mediation
modules, JMS support is provided by the default messaging provider of WebSphere Application Server. To
manage use of the Java Message Service, you can administer the following resources:
- JMS connection factory
- A JMS connection factory is used to create connections to the associated JMS provider of JMS destinations, for both point-to-point and publish/subscribe messaging. Use connection factory administrative objects to manage JMS connection factories for the default messaging provider.
- JMS queue
- A JMS queue is used as a destination for point-to-point messaging. Use JMS queue destination administrative objects to manage JMS queues for the default messaging provider.
- JMS topic
- A JMS topic is used as a destination for publish/subscribe messaging. Use topic destination administrative objects to manage JMS topics for the default messaging provider.
- JMS activation specification
- A JMS activation specification is associated with one or more message-driven beans and provides the configuration necessary for them to receive messages.
common event infrastructure (CEI)
CEI
resources enable a mediation module to use standard formats and mechanisms
for managing event data. To manage use of the common event infrastructure,
you can administer the following resources:
- Data Store Profile
- Defines properties used by the default data store. The default data store is the data store supplied by the Common Event Infrastructure.
- Emitter Factory Profile
- This profile defines the options for an event emitter.
- Event Bus Transmission Profile
- This profile defines the EJB entry into the event bus.
- Event Group Profile
- This profile defines a list of events which are determined through selector expressions. JMS queues and a JMS topic can be associated with each event group. If the event server distribution service is enabled and an event matches an event group the event is distributed to any topic or queues configured for that particular event group.
- Event Server Profile
- This profile defines the properties for the event server.
- Filter Factory Profile
- This profile defines the properties of a filter. The filter uses the filter configuration string to determine whether an event will be passed to the bus.
- JMS Transmission Profile
- The database schema that contains the event tables.