This page provides a starting point for finding information about service integration.
Service integration provides asynchronous messaging services. In asynchronous messaging, producing applications do not send messages directly to consuming applications. Instead, they send messages to destinations. Consuming applications receive messages from these destinations. A producing application can send a message and then continue processing without waiting until a consuming application receives the message. If necessary, the destination stores the message until the consuming application is ready to receive it.
You can monitor your service integration environment by using notification events.
Application servers or clusters of application servers in a WebSphere® Application Server cell can cooperate to provide asynchronous messaging services. Service integration provides asynchronous messaging services, and a group of servers or clusters that cooperate in this way is called a service integration bus. Each of the cooperating servers or clusters is made a member of the bus. In the simplest case, a service integration bus consists of a single bus member, which is one application server.
These topics provide information about messaging engines, which provide the processing function on a service integration bus.
A message store enables a messaging engine to preserve operating information and to retain those objects that messaging engines need for recovery in the event of a failure. The default message store for a typical messaging engine is file store. You can also configure a messaging engine to use a data store.
Configure service integration bus destinations, so that applications can attach to them to exchange messages as producers, consumers, or both.
These topics provide information about mediations, which are used to change how messages are handled at destinations on a service integration bus.
The service that provides service integration functions.
Add a transport to the list of permitted transports.
An alias destination makes a destination available by another name and, optionally, overrides the parameters of the destination.
This pane provides an expandable tree view of all the applications and messaging resources that reference the current destination, both directly and indirectly. As many of the references as possible are resolved to links to the associated configuration panel for the referenced object.
Bus members, servers and clusters that client applications can target to bootstrap into the given bus.
Bus members are the servers, WebSphere MQ servers and clusters that have been added to the bus.
Bus members are the servers, WebSphere MQ servers and clusters that have been added to the bus.
A service integration bus supports applications using message-based and service-oriented architectures. A bus is a group of interconnected servers and clusters that have been added as members of the bus. Applications connect to a bus at one of the messaging engines associated with its bus members.
A service integration bus supports applications using message-based and service-oriented architectures. A bus is a group of interconnected servers and clusters that have been added as members of the bus. Applications connect to a bus at one of the messaging engines associated with its bus members.
Context information used to enable correct processing of messages. This information adds to the context information derived from processing the message header.
Context information used to enable correct processing of messages. This information adds to the context information derived from processing the message header.
Use this page to specify an arbitrary name and value pair. The value that is specified for the name and value pair is a string that can set internal system configuration properties.
Use this page to specify an arbitrary name and value pair. The value that is specified for the name and value pair is a string that can set internal system configuration properties.
Arbitrary name-value pairs of data, where the name is a property key and the value is a string value that can be used to set internal system configuration properties. Defining a new property enables you to configure a setting beyond that which is available in the administrative console.
The persistent store for messages and other state managed by the messaging engine.
This pane shows the role type assignments for the default access.
This pane displays a list of all destinations known by the bus: aliases, foreign destinations, ports, queues, temporary destination prefixes, topic spaces and web services.
This pane displays the role type assignments for the selected destinations.
A bus destination is defined on a service integration bus, and is hosted by one or more locations within the bus. Applications can attach to the destination as producers, consumers, or both to exchange messages.
Properties to be applied when applications use destinations on this foreign bus when there is no explicit foreign destination definition.
The persistent store for messages and other state managed by the messaging engine.
A foreign bus connection allows communication with another bus. The foreign bus can represent another Service Integration Bus, an instance of WebSphere MQ, or an indirect connection to another foreign bus.
This pane shows the role type assignments for the selected foreign buses.
A foreign bus connection allows communication with another bus. The foreign bus can represent another Service Integration Bus, an instance of WebSphere MQ, or an indirect connection to another foreign bus.
The name by which this foreign destination is known for administrative purposes.
The inbound message streams from the remote queue point.
The routing definition for the next service integration bus in a sequence of connected buses.
A channel which can be used in combination with the TCP Channel - or other channels that support the same application interface to accept inbound connections to a WebSphere system integration bus messaging engine.
This pane displays the inbound message streams from messaging applications that are connected to the remote messaging engine, and that are producing messages to this WebSphere MQ link sender channel transmitter.
This pane displays current messages on the inbound message stream.
This pane displays the inbound receiver queues for messaging applications connected to remote messaging engines, that are producing messages to this WebSphere MQ link sender channel transmitter.
The remote messaging engines that have remote producers connected to this publication point.
The remote messaging engines that have remote producers connected to this publication point.
A queue for point-to-point messaging.
The remote queue points that are producing or consuming messages to or from queue points on remote messaging engines.
The remote messaging engines that have remote producers or consumers connected to this queue point.
The remote queue points that are producing/consuming messages to/from queue points on remote messaging engines.
The remote messaging engines that have remote producers or consumers connected to this queue point.
The remote messaging engines that have remote consumers connected to this subscription point.
The remote messaging engines that have remote consumers connected to this subscription point.
This pane displays the current messages on the link receiver stream.
This pane displays the inbound message streams from messaging applications on the foreign bus for the link receiver.
A link can have multiple link receivers. For applications that use point-to-point messaging, there is one link receiver for each messaging engine in the foreign bus, that is, the bus that sends messages across the link. For applications that use publish/subscribe messaging, there is one link receiver for each topic space in the foreign bus. The link receiver acts as an inbound receiver queue for a messaging engine that has applications attached and that is producing messages across this service integration bus link.
A link can have multiple link transmitters. For applications that use point-to-point messaging, there is one link transmitter on each messaging engine in the source bus. For applications that use publish/subscribe messaging, there is one link transmitter for each topic space in the source bus. The link transmitter acts as a transmission queue where produced messages are persisted before transmission across the service integration bus link or WebSphere MQ link to the foreign bus.
This pane displays the outbound messages to the foreign bus link, on the link transmitter stream.
This pane displays the outbound message streams, by quality of service, for the link transmitter.
A foreign bus is another bus with which this bus can exchange messages.
Bus member (server or cluster) where the mediations for the destination run.
Bus member (server or cluster) where the mediations for the destination run.
Bus member (server or cluster) where the mediations for the destination run.
The thread pool used to allocate threads for the execution of mediation handlers.
A mediation that is associated with a bus destination to apply processing to messages on that destination.
A mediation that is associated with a bus destination to apply processing to messages on that destination.
The contents of the message body.
Queue points and publication points for the messaging engine.
A snapshot of the current message retrieval requests from the message point.
A snapshot of the current message retrieval requests from the remote message point.
A snapshot of the current outbound messages for the message point.
A snapshot of the current outbound messages for the message point.
The messages on the message point.
The properties for a message on the message point.
The properties for a message on the message point.
The properties for a message on the message point.
This pane shows all the messaging engine policies for this cluster and their current settings, that is, the settings that determine messaging engine behavior. This list of policies comprises all the core group policies that are associated with the messaging engines in the cluster. If required, you can make a messaging engine policy conform to the currently selected messaging engine policy assistance type. You can also access the associated core group policy settings, although you should not change these settings unless you already have experience of doing so.
A messaging engine is a component, running inside a server, that manages messaging resources for a bus member. Applications are connected to a messaging engine when they access a service integration bus.
A messaging engine is a component, running inside a server, that manages messaging resources for a bus member. Applications are connected to a messaging engine when they access a service integration bus.
This pane provides an expandable tree view of all the references to messaging resources declared in the deployment descriptors for the current application. As many of the references as possible are resolved to links to the associated configuration panel for the referenced object.
A permitted transport is a transport mechanism that this bus will allow remote clients to use.
Use this page to specify an arbitrary name and value pair. The value that is specified for the name and value pair is a string that can set internal system configuration properties.
The message point for a topic space, for publish/subscribe messaging.
The message point for a topic space, for publish/subscribe messaging.
The message point for a topic space, for publish/subscribe messaging.
Profiles used to define the topic mappings and transactionality for publishing and receiving (by subscription) topics across the publish/subscribe bridge between WebSphere Application Server and a message broker in a WebSphere MQ network.
Profiles used to define the topic mappings and transactionality for publishing and receiving (by subscription) topics across the publish/subscribe bridge between WebSphere Application Server and a message broker in a WebSphere MQ network.
The message point for a queue, for point-to-point messaging.
The message point for a queue, for point-to-point messaging.
The message point for a queue, for point-to-point messaging.
This pane shows all the core group policies that are associated with this cluster through their match criteria, but that are not associated with any messaging engine in this cluster. Use this pane to delete redundant core group policies that you do not want.
The remote mediation points that are producing messages to mediation points on remote messaging engines.
The remote mediation points that are producing messages to mediation points on remote messaging engines.
The outbound message streams from this remote message point to the remote localized message point.
The remote publication points that are producing messages to publication points on remote messaging engines.
The remote publication points that are producing messages to publication points on remote messaging engines.
The subscription that has been made from this messaging engine to a subscription home on a remote messaging engine.
The subscription that has been made from this messaging engine to a subscription home on a remote messaging engine.
The saved status of message batches for the sender channel saved for transmission to WebSphere MQ. You can choose to commit or rollback each batch.
The runtime status of message batches for the receiver channel of the WebSphere MQ link.
Configure the security settings for the security domain to which your service integration bus is assigned.
Configure the security settings for your service integration bus.
This pane displays the transmission queue for a WebSphere MQ link sender channel.
This pane displays the messages queued for transmission across the WebSphere MQ link sender channel.
The routing properties for a service integration bus link to a foreign service integration bus.
This pane displays links between this messaging engine and messaging engines in foreign service integration buses.
This pane displays links between this messaging engine and messaging engines in foreign service integration buses.
The active subscriptions for the topic space.
The list of current broker subscriptions for this broker profile.
The active subscriptions for the topic space.
A temporary destination prefix is a user-defined string that is used to create a temporary destination. When messaging security is enabled, users and groups require authority to create messaged and send them to temporary destinations. The authority is configured in the temporary destination prefix.
This pane displays the role type assignments for the selected temporary destination prefixes.
The mapping between a topic on the service integration bus and a stream queue and subscription point provided by a WebSphere MQ broker.
The mapping between a topic on the service integration bus and a stream queue and subscription point provided by a WebSphere MQ broker.
This pane displays the role type assignments for a topic. You can use this pane to add new assignments, and to modify and remove existing assignments.
The mapping between a topic space in the local bus and a topic space in the foreign bus.
The mapping between a topic space in the local bus and a topic space in the foreign bus.
The mapping between topic spaces in the local bus and topic spaces in the foreign bus.
A topic space is a location for publish/subscribe messaging.
Topics are defined hierarchically within topic spaces. To view the access roles for a topic, first select the topic space that contains the topic to be viewed.
Topics are defined hierarchically within topic spaces. To view a topic's access roles, select the topic from the hierarchical list of topics below.
The topics that have been subscribed to from this remote messaging engine.
This panel lists users and groups that do not exist in the user repository but have access role definitions.
The users and groups displayed here are not defined in the user registry, but do have roles defined. This could be because they were removed from the user repository after the role assignments were made.
Users in the bus connector role are able to connect to the bus to perform messaging operations. Users can have this role either by specifically having that role, or because they are in a group with that role.
Create a user or group in the bus connector role.
The connection between a WebSphere MQ client and the bus.
The connection between a WebSphere MQ client and the bus.
Advanced configurable properties, such as message reliability and broker queue names, for the WebSphere MQ client link.
A WebSphere MQ client link presents the messaging engine, and therefore the bus, as a WebSphere MQ queue manager to which WebSphere MQ clients can attach. This behavior enables WebSphere Application Server Version 5 JMS clients to use messaging resources on the bus.
A WebSphere MQ client link presents the messaging engine, and therefore the bus, as a WebSphere MQ queue manager to which WebSphere MQ clients can attach. This behavior enables WebSphere Application Server Version 5 JMS clients to use messaging resources on the bus.
The WebSphere MQ link connects the messaging engine as a queue manager to WebSphere MQ, providing a bridge between the bus and a WebSphere MQ network.
A channel that can be used in combination with the TCP Channel or other channels within the confines of WebSphere MQ support to facilitate communications between a WebSphere system integration bus and a WebSphere MQ client or queue manager.
The receiver channel that receives messages from the gateway WebSphere MQ queue manager. The receiver channel communicates with a WebSphere MQ sender channel on the gateway queue manager, and converts MQ format messages to service integration bus messages.
The receiver channel that receives messages from the gateway WebSphere MQ queue manager. The receiver channel communicates with a WebSphere MQ sender channel on the gateway queue manager, and converts MQ format messages to service integration bus messages.
The routing properties for a link to a foreign bus that represents a WebSphere MQ network.
This pane displays the sender channel that sends messages to the gateway queue manager. The sender channel communicates with a WebSphere MQ receiver channel on the gateway queue manager, and converts service integration bus messages to MQ format messages.
This pane displays the sender channel that sends messages to the gateway queue manager. The sender channel communicates with a WebSphere MQ receiver channel on the gateway queue manager, and converts service integration bus messages to MQ format messages.
The WebSphere MQ link connects the messaging engine as a queue manager to WebSphere MQ, providing a bridge between the bus and a WebSphere MQ network.
Mediation execution points for the processing of messages from mediation message points that are on a WebSphere MQ server.
Bus member (server or cluster) where the mediations for the destination run.
Bus member (server or cluster) where the mediations for the destination run.
A WebSphere MQ mediation point is a location from which a mediation takes messages.
A WebSphere MQ mediation point is a location from which a mediation takes messages.
A WebSphere MQ queue point is used when sending messages to and receiving messages from a WebSphere MQ queue.
A WebSphere MQ queue point is used when sending messages to and receiving messages from a WebSphere MQ queue.
A connection that exists on the receiver channel of the WebSphere MQ link.
A connection that exists on the receiver channel of the WebSphere MQ link.
A WebSphere MQ server bus member is used for assigning queue points and mediation points to WebSphere MQ queues.
A WebSphere MQ server represents a WebSphere MQ queue manager or (for WebSphere MQ for z/OS® ) queue-sharing group.
A WebSphere MQ server represents a WebSphere MQ queue manager or (for WebSphere MQ for z/OS ) queue-sharing group. Use this panel to view or modify the details of a WebSphere MQ server definition.
Use custom properties to configure advanced settings for service integration objects such as messaging engines.
You can use these administrative commands to manage service integration buses.
Use the createSIBus command to create a new service integration bus.
Use the deleteSIBus command to delete a specified service integration bus.
Use the listSIBuses command to list all service integration buses for a given scope.
Use the modifySIBus command to modify the properties of a service integration bus.
Use the showSIBus command to show the properties of a service integration bus.
Use the addSIBusMember command to add a member to a service integration bus by using the wsadmin tool. A bus member can be an application server, a WebSphere MQ server, or a server cluster.
Use the listSIBusMembers command to list the members of a service integration bus.
Use the modifySIBusMemberPolicy command to change the messaging engine configuration for a cluster that is a member of a service integration bus.
Use the removeSIBusMember command to remove a member from a service integration bus by using the wsadmin tool. A bus member can be an application server, a WebSphere MQ server, or a server cluster.
Use the showSIBusMember command to show the properties of a service integration bus member.
Use the listAllSIBBootstrapMembers command to list all the bootstrap members that can bootstrap into a selected bus.
Use the listSIBNominatedBootstrapMembers command to list all the nominated bootstrap members for a specified bus.
Use the addSIBBootstrapMember command to add a nominated bootstrap member to a specified bus.
Use the removeSIBBootstrapMember command to remove a nominated bootstrap member from a selected bus.
You can use these administrative commands to manage foreign buses. A foreign bus represents a service integration bus with which another service integration bus can exchange messages.
Use the createSIBForeignBus command to create a new service integration foreign bus.
Use the deleteSIBForeignBus command to delete a foreign bus.
Use the listSIBForeignBuses command to list all foreign buses for a specified service integration bus.
Use the modifySIBForeignBus command to modify the properties of a foreign bus.
Use the showSIBForeignBus command to show the properties of a foreign bus.
You can use these administrative commands to manage WebSphere MQ links. A WebSphere MQ link connects a messaging engine as a queue manager to WebSphere MQ, thereby providing a bridge between a service integration bus and a WebSphere MQ network.
Use the createSIBMQLink command to create a new WebSphere MQ link for a specified service integration bus.
Use the deleteSIBMQLink command to delete a WebSphere MQ link from a service integration bus.
Use the listSIBMQLinks command to list all WebSphere MQ links for a specified service integration bus.
Use the modifySIBMQLink command to modify the properties of a WebSphere MQ link.
Use the showSIBMQLink command to show the properties of a WebSphere MQ link.
You can use these administrative commands to manage service integration bus links. A service integration bus link defines a link between a messaging engine in one service integration bus and a messaging engine in a foreign service integration bus.
Use the createSIBLink command to create a new service integration bus link.
Use the deleteSIBLink command to delete a service integration bus link from a bus.
Use the listSIBLinks command to list all service integration bus links for a given bus.
Use the modifySIBLink command to modify the properties of a service integration bus link.
Use the showSIBLink command to show the properties of a service integration bus link.
You can use these administrative commands to manage messaging engines.
Use the createSIBEngine command to create a messaging engine for a server or cluster bus member by using the wsadmin tool. When you add a server or a cluster as a member of a service integration bus, at least one messaging engine is created automatically. Use the createSIBEngine command to create an additional messaging engine for a cluster bus member.
Use the listSIBEngines command to list the messaging engines for a service integration bus member.
Use the modifySIBEngine command to modify the properties of a messaging engine for a service integration bus member.
Use the showSIBEngine command to list properties of a messaging engine for a service integration bus member.
Use the deleteSIBEngine command to delete a messaging engine from a service integration bus member.
Use the createMissingSIBEnginePolicy command to create a core group policy for a messaging engine in a cluster that is a member of a service integration bus.
Use the correctSIBEnginePolicy command to change a core group policy for a messaging engine in a cluster that is a member of a service integration bus, so that the core group policy conforms to the current messaging engine policy set for the cluster.
When a server that is a member of a bus is converted to a cluster, use the migrateServerMEtoCluster command to migrate the messaging engine (ME) in the server to cluster scope. During the conversion, the bus membership is not automatically transferred to cluster scope. If you want the cluster to be a member of the bus, use this command to perform that transfer.
You can use these administrative commands to manage bus destinations.
Use the createSIBDestination command to create a new bus destination for a service integration bus.
Use the createSIBDestinations command to create new bus destinations for a service integration bus.
Use the deleteSIBDestination command to delete a bus destination.
Use the deleteSIBDestinations command to delete bus destinations.
Use the listSIBDestinations command to list the bus destinations for a service integration bus.
Use the mediateSIBDestination command to mediate a bus destination for a service integration bus.
Use the modifySIBDestination command to change properties of a bus destination for a service integration bus.
Use the showSIBDestination command to list the property values for a bus destination.
Use the unmediateSIBDestination command to remove a mediation from a service integration bus destination.
You can use these administrative commands to manage mediations.
Use the createSIBMediation command to create a new mediation.
Use the deleteSIBMediation command to delete a mediation.
Use the listSIBMediations command to list mediations on a service integration bus.
Use the modifySIBMediation command to change the properties of a mediation.
Use the showSIBMediation command to list the property values for a mediation.
Use command scripts to create, modify, list, show and delete WebSphere MQ servers and server bus members. These commands do not support the automatic resource discovery feature provided by the administrative console.
Use the createSIBWMQServer command to create a new WebSphere MQ server at cell scope.
Use the modifySIBWMQServer command to modify a WebSphere MQ server.
Use the listSIBWMQServers command to list the WebSphere MQ servers known to a cell.
Use the showSIBWMQServer command to show details of a WebSphere MQ server.
Use the deleteSIBWMQServer command to delete a specified WebSphere MQ server and remove the associated WebSphere MQ server bus members, assigned queue points and mediation points.
Use the modifySIBWMQServerBusMember command to modify the attributes of a WebSphere MQ server bus member.
Use the listSIBWMQServerBusMembers command to list the WebSphere MQ server bus members known to the bus.
Use the showSIBWMQServerBusMember command to show a list of attributes for a WebSphere MQ server bus member.
You can use these administrative commands to manage service integration bus security.
Use the populateUniqueNames command to add missing unique names to the authorization policy for a service integration bus.
Use the listGroupsInBusConnectorRole command to list all the groups in the connector role for a local bus.
Use the addGroupToBusConnectorRole command to add a group to the connector role for a local bus.
Use the removeGroupFromBusConnectorRole command to remove a group from the connector role for a local bus.
Use the listUsersInBusConnectorRole command to list users in the connector role for a local bus.
Use the addUserToBusConnectorRole command to add a user to the connector role for a local bus.
Use the removeUserFromBusConnectorRole command to remove a user from the connector role for a local bus.
Use the listGroupsInDefaultRole command to list the groups in the default roles for a local bus.
Use the addGroupToDefaultRole command to add a group to the default roles for a local bus.
Use the removeGroupFromDefaultRole command to remove a group from the default roles for a local bus.
Use the listUsersInDefaultRole command to list users in the default roles for a local bus.
Use the addUserToDefaultRole command to add a user to the default roles for a local bus.
Use the removeGroupFromDefaultRole command from remove a user from the default roles for a local bus.
Use the listGroupsInTopicRole command to list the groups in topic roles for a topic space on a local bus.
Use the addGroupToTopicRole command to add a group to a topic role within a specified topic space.
Use the removeGroupFromTopicRole command to remove a group from a topic role within a specified topic space.
Use the listUsersInTopicRole command to list users in the topic roles within a specified topic space.
Use the addUserToTopicRole command to add a user to a topic role within a specified topic space.
Use the removeUserFromTopicRole command to remove a user from a topic role within a specified topic space.
Use the listGroupInTopicSpaceRootRole command to list all the groups in topic space roles on the topic space root for a local bus.
Use the addGroupToTopicSpaceRootRole command to add a group to topic space roles on the topic space root.
Use the removeGroupFromTopicSpaceRootRole command to remove a group from access roles on the topic space root.
Use the listUsersInTopicSpaceRootRole command to list the users in the sender and receiver roles on the topic space root.
Use the addUserToTopicSpaceRootRole command to add a user to the sender and receiver roles on the topic space root.
Use the removeUserFromTopicSpaceRootRole command to remove a user from access roles on the topic space root.
Use the listGroupsInDestinationRole command to list the groups in the destination roles for a local bus.
Use the addGroupToDestinationRole command to add a group to the destination roles for a local or foreign bus.
Use the removeGroupFromDestinationRole command to remove a group from the destination roles for a local or foreign bus.
Use the listUsersInDestinationRole command to list users in the destination roles for a local bus.
Use the addUserToDestinationRole command to add a user to the destination roles for a local or foreign bus.
Use the removeUserFromDestinationRole command to remove a user from the destination roles for a local or foreign bus.
Use the listGroupsInForeignBusRole command to list the groups in the sender role for a foreign bus.
Use the addGroupToForeignBusRole command to grant a group permission to access a foreign bus from a local bus, in the sender role.
Use the removeGroupFromForeignBusRole command to remove a group from the sender role for a foreign bus.
Use the listUsersInForeignBusRole command to list users that can send messages from a local bus to a foreign bus.
Use the addUserToForeignBusRole command to grant a user permission to access a foreign bus from a local bus, in the sender role.
Use the removeUserFromForeignBusRole command to remove a user from the sender role for a foreign bus.
Use the removeGroupFromAllRoles command to remove a group from all access roles for a local bus.
Use the removeUserFromAllRoles command to remove a user from all access roles for a local bus.
By default, the inheritance of default permissions by destinations is allowed for all local destinations. Use this command to determine whether the inheritance of default permissions is enabled or disabled for a local destination.
By default, the inheritance of default permissions by destinations is allowed for all local destinations. Use this command to override inheritance for an individual destination, or to restore default inheritance in cases where you have previously overridden it.
Use these commands to define the inheritance of topic roles by child topics within a topic hierarchy.
Use these commands to list whether the child topics within a topic hierarchy currently have inheritance set or disabled.
When you are administering messaging security, use these commands to list the security roles that are associated with service integration bus destinations, foreign buses, topics within a topic space, users and groups.
Use these commands to remove authorization data for the default roles, or for a destination or a foreign bus.
Use the listSIBPermittedChain command to list the permitted transport chains for a service integration bus.
Use the addSIBPermittedChain command to add a new transport mechanism to the list of permitted transports for a service integration bus.
Use the removeSIBPermittedChain command to remove a selected transport chain from the list of permitted transport chains for a selected service integration bus.
A messaging engine needs data definition language (DDL) statements to create the DBMS (Database Management System) resources. These DBMS resources are generated by the sibDDLGenerator command.
Icons are used in the administrative console to represent users and groups that have access roles for service integration bus resources.
For each processing step taken by your JMS messaging application, check this table to see when and why there is a potential performance benefit in enabling the "pass message payload by reference" properties on the associated connection factory or activation specification.
The SIMessage metadata properties enable the main data types, and are supported by JMS Message Selectors.
The SIMessage metadata properties contain message metadata that you can use in mediation configuration selectors. You can work with these properties by using the SIMessage interface.
Support is provided by the SIMessage interface and the mediation configuration selector for JMS headers properties. JMS headers properties match in the SIMessage interface in the same way as they do for the JMS API, but you can only modify properties that map to SIMessage metadata.
Support is provided by the SIMessage interface and the mediation configuration selector for JMSX properties. You can use the SIMessage interface to match and access supported JMSX properties defined in the JMS API. You can only use the SIMessage interface to set properties that are not defined as set by the JMS provider.
Support is provided by the SIMessage interface and the mediation configuration selector for JMS_IBM properties and the equivalent SI_system properties. You can access JMS_IBM_ properties through the JMS API. Many of the values held by JMS_IBM_ properties apply to an SIMessage and have SI_ synonyms. You can access all these properties through the SIMessage interface, and can match and set many of them. You cannot set exception properties because they are controlled by the messaging engine.
The JMS_IBM_Feedback property identifies the type of report a message contains.
Support for user properties is provided by the SIMessage interface and the mediation configuration selector. The JMS API supports user properties of primitive wrapper or string types. The property name can be any valid Java™ identifier providing it does not have the prefix JMS. The SIMessage API also supports user properties of primitive wrapper or string types, and additionally supports byte[] and serializable types. Arbitrary serializable objects are stored as byte arrays, and are selected on as byte arrays only (using equals only).
The actions taken in the event of an error occurring during mediation processing are summarized in the following table:
The naming restrictions for WebSphere MQ queues, queue managers, and queue-sharing groups are more restrictive than those that apply to equivalent objects in WebSphere Application Server. Use this information to help you administer the WebSphere Application Server objects, so that the names of these objects can be passed successfully to and from WebSphere MQ.
The table below describes the default thread pool properties for the mediationsThreadPool object for a messaging engine.