SIB Service
The service that provides service integration functions.
Configuration reload enabled
Select this option to enable the dynamic reloading of the service integration configuration files for this server.
The bus {0} already exists.
At least one messaging engine must be selected to perform this action.
The messaging engine {0} cannot be started.
The messaging engine {0} cannot be stopped.
The messaging engine {0} is already started.
The messaging engine {0} is already stopped.
Uninitialized
Initializing
Initialized
Joining
Joined
Autostarting
Starting
Started
Stopping
Stopping member
Stopped
Destroying
Destroyed
Unknown
Data store
The persistent store for messages and other state managed by the messaging engine.
UUID
The universal unique identifier assigned by the system to this data store for administrative purposes.
Data source name
The JNDI name of the data source that the messaging engine uses to access the relational database management system (RDBMS) for the data store.
Schema name
The name of the database schema used to contain the tables for the data store.
Authentication alias
The name of the authentication alias used to authenticate the messaging engine to the data source.
Create tables
Select this option if the messaging engine creates the database tables for the data store. Otherwise, the database administrator must create the database tables.
User
Password
Destinations
Destination
A bus destination is a virtual place, within a service integration bus, to which applications attach as producers, consumers, or both to exchange messages.
Identifier
The identifier by which this destination is known for administrative purposes.
UUID
The universal unique identifier assigned by the system to this destination for administrative purposes.
Type
Whether this bus destination is for a queue, topic space, or some other type of destination.
Description
An optional description for the bus destination, for administrative purposes.
Default reliability
Enable producers to override default reliability
Select this option to enable producers to override the default reliability that is set on the destination.
Default priority
The default priority assigned to messages sent to this destination when a priority has not been set by the producer.
Maximum failed deliveries
The maximum number of failed attempts to process a message before the message is forwarded to the exception destination for the destination.
Maximum reliability
The maximum reliability of messages accepted by this destination.
Exception destination
The destination to which a message is forwarded by the system when it cannot be delivered to this destination.
Send allowed
Clear this option (setting it to false) to stop producers from being able to send messages to this destination.
Receive allowed
Clear this option (setting it to false) to prevent consumers from being able to receive messages from this destination.
Quiesce mode
Select this option (setting it to true) to indicate that the destination is quiescing. In quiesce mode, new messages for the destination cannot be added to the bus, but any messages already in the bus can still be sent to, and processed by, the destination.
Receive exclusive
Reply destination
The name of a destination to be appended to any non-empty reverse routing path of messages sent to this destination.
Reply destination bus
The bus on which the reply destination exists.
Default forward routing path
The value to which a message's forward routing path will be set if the message contains no forward routing path, in the format, <bus:>name or <:>name.
Select destination type
Select the type of destination to be created
Create new destination
Create a new destination on this bus.
Create new queue
Create a new queue for point-to-point messaging
Set queue attributes
Configure the attributes of your new queue
Assign the queue to a bus member
Assign the queue to a bus member that will store and process the messages for the queue.
Bus member
Confirm queue creation
Queue identifier is required
There must be one or more bus members on the bus before you can create a queue
The following is a summary of your selections. To complete creation of the queue, click Finish.
If you want to change any selections, click Previous.
New queue "{0}" will be created.
Queue points for "{0}" will be created for bus member "{1}" of bus "{2}".
A Queue point for "{0}" will be created for bus member "{1}" of bus "{2}".
Create new topic space
Create a new topic space for publish/subscribe messaging.
Set topic space Attributes
Configure the attributes of your new topic space
Confirm topic space creation
Topic space identifier is required
The following is a summary of your selections. To complete creation of the topic space, click Finish.
If you want to change any selections, click Previous.
New topic space "{0}" will be created.
Publication points for "{0}" will be created on all bus members of bus "{1}".
Message points
Queue points and publication points for the messaging engine
Identifier
The system generated name by which this message point is known.
UUID
The universal unique identifier assigned by the system to this message point for administrative purposes.
Destination type
Whether the message point is a queue or topic space.
High message threshold
A threshold above which the messaging system will take action to limit the addition of more messages to this message point.
Send allowed
Clear this option (setting it to false) to stop messages from being put onto this message point.
Receive allowed
Clear this option (setting it to false) to stop messages from being retrieved from this message point.
Target UUID
The UUID of the bus destination for which this is a message point.
Current message depth
The number of messages on the message point.
Run-time ID
The internal run-time identifier assigned to this message point.
Queue
A queue for point-to-point messaging.
Mediation points
A mediation point is a location in a messaging engine at which messages are mediated. A mediation point is created when a mediation is associated with a bus destination.
Port
Mediation points
Web service
Mediation points
Queue points
The message point for a queue, for point-to-point messaging.
Messages
Messages queued on the queue point.
User
Temporary
System
Topic space
A topic space is a location for publish/subscribe messaging.
Topic access check required
Whether or not authorization checks are required for access to topics.
Mediation points
The mediation points for the topic space. The locations in the messaging engine at which messages on the topic space are mediated.
Publication points
The message point for a topic space, for publish/subscribe messaging.
Mediation points
Locations in the bus at which messages on are mediated.
Initial state
Whether the mediation point is started or stopped when the hosting messaging engine is first started. Until started, the mediation point is unavailable.
Status
The run-time status of the mediation point.
Reason
Messages
Messages queued on the mediation point.
Started
Stopped
Waiting
Started
Stopping
Stopped
Deleting
Unknown
You must select a mediation point
Mediation point {0} started successfully
Mediation point {0} could not be started
Mediation point {0} stopped successfully
Mediation point {0} could not be stopped
Buses
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.
Custom properties
Custom property
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.
Messaging engines
A messaging engine manages bus resources and provides a connection point for applications.
Bus members
Bus members are the servers and clusters that have been added to the bus.
Destinations
A bus destination is a logical address within a service integration bus.
Mediations
Mediations define the information needed by a messaging engine to perform the mediation processing for associated destinations.
Name
The name of the service integration bus. Choose a unique name.
UUID
The universal unique identifier assigned by the system to this bus for administrative purposes.
Description
An optional description for the bus, for administrative purposes.
Secure
Select this option to inherit the Global Security setting of the cell. Deselect this option if you always wish to disable bus security.
Inter-engine authentication alias
The name of the authentication alias used to authorize communication between messaging engines on the bus.
Mediations authentication alias
The name of the authentication alias used to authorize mediations to access the bus.
Inter-engine transport chain
The transport chain used for communication between messaging engines in this bus.
Discard messages
Whether messages on a deleted message point should be retained at a system exception destination or can be discarded.
Configuration reload enabled
Select this option to enable certain changes to the bus configuration to be applied without requiring the messaging engines to be restarted.
High message threshold
A threshold above which the messaging system will take action to limit the addition of more messages to a message point.
Bus Defaults
Provide the default settings for these attributes on a new messaging engine.
Bus members
Bus members are the servers and clusters that have been added to the bus.
Name
The name of the bus member.
Node
The node on which the bus member is configured.
Server
Select a server.
Cluster
Select a cluster.
Description
An optional description for the bus member, for administrative purposes.
Add a new bus member
Add a server or server cluster as a new member of the bus.
Select server or cluster
Choose the server or cluster to add to the bus
Selection
You must select a server or cluster to be added as a bus member
Confirm the addition of a new bus member
The following is a summary of your selections. To complete the bus member creation, click Finish.
If there are settings you wish to change, click Previous to review bus member settings.
New bus member "{0}" will be added to bus "{1}".
Messaging engines
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 accessing a service integration bus.
Data store
The persistent store for messages and other state managed by the messaging engine.
Message Points
The locations (queue points or publication points) at which messages are held in a messaging engine.
Queue points
A queue point is created on each messaging engine to which a point-to-point destination is assigned. It is used to hold messages pending delivery to receiving applications.
Publication points
A publication point is created on each messaging engine in the bus when a publish/subscribe destination is created. The publication point on a messaging engine is used to hold messages published by applications connected to that messaging engine until they are delivered to subscribers.
Mediation points
A mediation point is created on each messaging engine to which the mediation of a mediated destination is assigned. It is used to hold messages pending delivery to the mediation.
Custom properties
Custom property
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.
Name
The name of the messaging engine.
UUID
The universal unique identifier assigned by the system to this messaging engine for administrative purposes.
Description
An optional description for the messaging engine, for administrative purposes.
Initial state
The initial state determines whether the messaging engine is started automatically.
High message threshold
The maximum total number of messages that the messaging engine can place on its message points.
Target groups
A list of names of target groups with which the messaging engine will register.
Bus name
The name of the service integration bus on which the messaging engine is configured.
Bus UUID
The universal unique identifier of the service integration bus on which the messaging engine is configured.
Status
Whether the messaging engine is currently started or stopped.
Stopped
Started
WebSphere MQ links
Links between the messaging engine and WebSphere MQ networks. Each WebSphere MQ link connects the messaging engine as a queue manager to WebSphere MQ, thereby providing a bridge between the bus and a WebSphere MQ network.
WebSphere MQ client links
A WebSphere MQ client link enables JMS client applications to connect, via this messaging engine, to the service integration bus, as though it were a WebSphere MQ queue manager.
Best effort nonpersistent
Express nonpersistent
Reliable nonpersistent
Reliable persistent
Assured persistent
Service integration
Buses
WebSphere MQ link receiver channel
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.
Receiver MQ channel name
The name of the receiver channel for the WebSphere MQ link, used to receive messages from WebSphere MQ onto the bus.
Inbound nonpersistent message reliability
The acceptable reliability of message delivery for nonpersistent message flows from WebSphere MQ through this WebSphere MQ link, from Best effort to Reliable, in order of increasing reliability.
Inbound persistent message reliability
The acceptable reliability of message delivery for inbound persistent message flows from WebSphere MQ through this WebSphere MQ link, from Reliable to Assured, in order of increasing reliability.
Initial state
Whether the receiver channel is started or stopped when the associated WebSphere MQ link is first started. Until started, the channel is unavailable.
Status
You must select a WebSphere MQ link receiver channel
The WebSphere MQ link receiver channel {0} started successfully
The WebSphere MQ link receiver channel {0} could not be started
The WebSphere MQ link receiver channel {0} stopped successfully
The WebSphere MQ link receiver channel {0} could not be stopped
WebSphere MQ link sender channel
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.
Transmission stream
Sender MQ channel name
The name of the sender channel for the WebSphere MQ link, used to send messages from the bus to WebSphere MQ.
Host name
The hostname or TCP/IP IP address for the gateway queue manager that is used to connect into the WebSphere MQ network.
Port
The TCP/IP port number on which the gateway queue manager is listening for the WebSphere MQ link.
Transport chain
The type of channel chain used for communication with the foreign bus.
Disconnect interval
The time in seconds for which the sender channel waits for new messages to arrive on the transmission queue after sending a batch of messages. The channel disconnects after this interval, and must be restarted manually or by triggering.
seconds
Short retry count
The maximum number of times that the sender channel tries to restart after a communication or partner failure. If the count of remaining retries reaches zero, and the channel has not restarted, then the long retry mechanism is invoked.
Short retry interval
The number of seconds between attempts by the sender channel to restart after a communication or partner failure.
seconds
Long retry count
The maximum number of times that the sender channel tries to restart after the short retry mechanism did not recover from a communication or partner failure. If the count of remaining retries reaches zero, and the channel has not restarted, then an error is logged and the channel is stopped.
Long retry interval
The number of seconds between attempts by the sender channel to restart after the short retry mechanism did not recover from a communication or partner failure.
seconds
Initial state
Whether the sender channel is started or stopped when the associated WebSphere MQ link is first started. Until started, the channel is unavailable.
You must select a WebSphere MQ link sender channel
WebSphere MQ link sender channel {0} started successfully
WebSphere MQ link sender channel {0} could not be started
WebSphere MQ link sender channel {0} stopped successfully
WebSphere MQ link sender Channel {0} could not be stopped
WebSphere MQ link sender channel {0} reset successfully
WebSphere MQ link sender channel {0} could not be reset
Queue manager
I/P address
Status
Current LUWID
Current sequence number
In doubt
Last LUWID
Last sequence number
Messages in current batch
Number of batches sent
Batch size
Number of messages sent
Buffers sent
Buffers received
Bytes sent
Bytes received
Channel start time
Channel start date
Last message send time
Last message send date
Heartbeat interval
Remaining long retry starts
Remaining short retry starts
Maximum message length
Nonpersistent message speed
Stop requested
The name of the virtual queue manager associated with the messaging engine, and by which the messaging engine is known to a remote WebSphere MQ network.
The TCP/IP IP address of the host on which the target queue manager runs.
The run-time status of the sender channel.
The current logical unit-of-work identifier for the message on the channel.
The current sequence number for the message on the channel.
Whether or not the message on the channel is in-doubt.
The last logical unit-of-work identifier for a message on the channel.
The last sequence number for a message on the channel.
The number of messages in the current batch on the channel.
The number of batches that have been sent on the channel.
The maximum number of messages that a batch can contain.
The number of messages that have been sent on the channel.
The number of message buffers sent.
The number of message buffers received.
The number of bytes sent.
The number of bytes received.
The time at which the channel was last started.
The date on which the channel was last started.
The time at which the last message was sent on the channel.
The date on which the last message was sent on the channel.
The negotiated time, in seconds, between heartbeat flows passed from the sender channel across the WebSphere MQ link when there are no messages on the transmission queue.
seconds
The remaining number of long retry attempts that can be used to start the sender channel. If the count of remaining retries reaches zero, and the channel has not restarted, then an error is logged and the channel is stopped.
The remaining number of short retry attempts that can be used to start the sender channel. If the count of remaining retries reaches zero, and the channel has not restarted, then the long retry mechanism is invoked.
The maximum message length, in bytes, that can be transmitted on the channel. This is compared with the value for the partner and the actual maximum used is the lower of the two values.
bytes
The class of service for nonpersistent messages on the sender channel.
Whether or not a manual stop request has been made for the sender channel.
Saved batch status
The run-time status of message batches for the sender channel of the WebSphere MQ link. You can choose to commit or roll back each batch.
WebSphere MQ link
A link between the messaging engine and a WebSphere MQ network. The WebSphere MQ link connects the messaging engine as a queue manager to WebSphere MQ, thereby providing a bridge between the bus and a WebSphere MQ network.
Sender channel
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.
Receiver channel
The receiver channel that receives messages from the gateway 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.
Publish/subscribe broker profiles
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 WebSphere MQ network.
Name
The name of the WebSphere MQ link, used for administrative purposes.
UUID
The universal unique identifier assigned by the system to this WebSphere MQ link for administrative purposes.
Description
An optional description for the WebSphere MQ link, for administrative purposes.
Foreign bus name
The foreign bus to which this link connects.
Queue manager name
The name of the virtual queue manager associated with the messaging engine, and by which the messaging engine is known to a remote WebSphere MQ network.
Batch size
The maximum number of messages that can be sent through a channel before taking a checkpoint.
Maximum message size
The maximum message length, in bytes, that can be transmitted on any channel for the WebSphere MQ link. This is compared with the value for the partner and the actual maximum used is the lower of the two values.
bytes
Heartbeat interval
The time, in seconds, between heartbeat flows passed from the sender channel across the WebSphere MQ link when there are no messages on the transmission queue.
seconds
Sequence wrap
The value at which message sequence numbers wrap to start again at 1.
Nonpersistent message speed
The class of service for nonpersistent messages on channels of this WebSphere MQ link.
Adoptable
Whether or not this WebSphere MQ link can be adopted by another messaging engine if the original hosting messaging engine is restarted or adopted on another machine.
Initial state
Whether the WebSphere MQ link is started or stopped when the hosting messaging engine is first started. Until started, the WebSphere MQ link is unavailable.
Inactive
Starting
Binding
Initializing
Retrying
Standby
Running
Stopping
Paused
Stopped
Multiple
Unknown
Status
The run-time status of the WebSphere MQ link.
You must select a WebSphere MQ link
WebSphere MQ link {0} started successfully
WebSphere MQ link {0} could not be started
WebSphere MQ link {0} stopped successfully
WebSphere MQ link {0} could not be stopped
Stop mode:
Target state:
Quiesce
Force
Inactive
Stopped
Fast
Normal
Create new WebSphere MQ link
Wizard to create a new WebSphere MQ link
The following is a summary of your selections. To complete creation of the WebSphere MQ Link, click Finish. If you want to change any selections, click Previous.
New WebSphere MQ Link {0} will be created to foreign bus {1}.
A Sender channel will be created with name: {0}.
A Receiver channel will be created with name: {0}.
General WebSphere MQ link properties
Sender channel WebSphere MQ link properties
Receiver channel WebSphere MQ link properties
Summary of WebSphere MQ link properties
Stopped
Started
WebSphere MQ client link
A WebSphere MQ client link presents the messaging engine, and thereby the bus, as a WebSphere MQ queue manager to which WebSphere MQ clients can attach. This enables WebSphere Application Server Version 5 JMS clients to use messaging resources on the bus.
Name
The name of the WebSphere MQ client link.
UUID
The universal unique identifier assigned by the system to this WebSphere MQ client link for administrative purposes.
Description
An optional description for the WebSphere MQ client link, for administrative purposes.
MQ channel name
The name of the channel for the WebSphere MQ client link, used to flow messages between WebSphere MQ clients and the bus.
Queue manager name
The queue manager name used to represent the bus as a WebSphere MQ queue manager to WebSphere MQ clients.
Default queue manager
Whether or not this is the default queue manager for the WebSphere MQ clients.
Maximum message size
The maximum message length, in bytes, that can be transmitted on the channel for the WebSphere MQ client link.
bytes
Heartbeat interval
The time, in seconds, to wait before checking that a client requesting an operation is still active.
seconds
Initial state
Whether the WebSphere MQ client link is started or stopped when the associated messaging engine is first started. Until started, the MQ client link is unavailable.
Status
The run-time status of the WebSphere MQ client link.
Advanced properties
Advanced configurable properties, such as message reliability and broker queue names, for the WebSphere MQ client link.
Client connections
The client connections that exist on the WebSphere MQ client link.
You must select a WebSphere MQ client link
WebSphere MQ client link {0} started successfully
WebSphere MQ client link {0} could not be started
WebSphere MQ client link {0} stopped successfully
WebSphere MQ client link {0} could not be stopped
Queue manager name can not contain the character ''{0}''
Stopped
Started
WebSphere MQ client connection
The connection between a WebSphere MQ client and the bus.
You must select a client connection
Client connection {0} started successfully
Client connection {0} could not be started
Client connection {0} stopped successfully
Client connection {0} could not be stopped
IP address
The TCP/IP IP address of the WebSphere MQ client.
Status
The run-time status of the WebSphere MQ client connection.
Inactive
Stopped
Starting
Binding
Running
Stopping
Multiple
Unknown
Client server status
The runtime status of the WebSphere MQ client.
Number of messages sent
The number of messages sent on the WebSphere MQ client link over the connection to a specific client.
Number of messages received
The number of messages received on the WebSphere MQ client link over the connection from a specific client.
Number of buffers sent
The number of message buffers sent on the WebSphere MQ client link over the connection to a specific client.
Number of buffers received
The number of message buffers received on the WebSphere MQ client link over the connection from a specific client.
Number of bytes sent
The number of bytes sent on the WebSphere MQ client link over the connection to a specific client.
Number of bytes received
The number of bytes received on the WebSphere MQ client link over the connection from a specific client.
Channel start time
The time at which the client connection channel was started.
Channel start date
The date on which the client connection channel was started.
Last message send time
The time at which the last message was sent on the client connection channel.
Last message send date
The date on which the last message was sent on the client connection channel.
Last message receive time
The time at which the last message was received on the client connection channel.
Last message receive date
The date on which the last message was sent on the client connection channel.
Heartbeat interval
The time, in seconds, between heartbeat flows passed across the WebSphere MQ client link when there are no messages on the transmission queue for the client connection.
seconds
Maximum message length
The maximum message length, in bytes, that can be transmitted on the WebSphere MQ client link. This is compared with the value for the partner client and the actual maximum used is the lower of the two values.
bytes
Stop requested
Whether or not a manual stop request has been made for the WebSphere MQ client link connection.
Local address
The local address of the WebSphere MQ client connection.
Number of API calls serviced
The number of API calls serviced for the WebSphere MQ client connection.
WebSphere MQ client link advanced properties
Advanced configurable properties, such as message reliability and broker queue names, for the WebSphere MQ client link.
Inbound persistent message reliability
The acceptable reliability of message delivery for inbound persistent message flows from WebSphere MQ through this WebSphere MQ client link, from Reliable to Assured, in order of increasing reliability.
Inbound nonpersistent message reliability
The acceptable reliability of message delivery for inbound nonpersistent message flows from WebSphere MQ through this WebSphere MQ link, from Reliable to Assured, in order of increasing reliability.
Broker control queue
The name of the message broker control queue to which all command messages (except publications and requests to delete publications) are sent.
Broker publication queue
The name of the message broker publication queue to which all publication messages for the default stream are sent.
Broker subscription queue
The name of the message broker subscription queue from which nondurable subscription messages are retrieved.
Broker durable subscription queue
The name of the message broker durable subscription queue from which durable subscription messages are retrieved.
Broker connection consumer subscription queue
The name of the message broker connection consumer subscription queue from which nondurable subscription messages are retrieved for a connection consumer request.
Broker connection consumer durable subscription queue
The name of the message broker connection consumer durable subscription queue from which nondurable subscription messages are retrieved for a connection consumer request.
Default topic space
The name of the default topic space for the WebSphere MQ client link.
Reliable
Assured
Best effort
Express
Reliable
WebSphere MQ sender channel saved batch status
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.
Queue manager
MQ channel name
In doubt
Current LUWID
Current sequence number
Last LUWID
Last sequence number
The name of the queue manager for the WebSphere MQ link sender channel.
The name of the channel used for the WebSphere MQ link sender channel.
Whether or not the saved batch is in doubt.
The current logical unit-of-work identifier for the saved batch.
The current sequence number for the saved batch.
The last logical unit-of-work identifier for the saved batch.
The last sequence number for the saved batch.
A saved batch status must be selected
Saved batch status for {0} committed successfully
Saved batch status for {0} could not be committed
Saved batch status for {0} rolledback successfully
Saved batch status for {0} could not be rolledback
Saved batch status for {0} is not in doubt
Confirm commit of selected units of work, Yes or No
Confirm rollback of selected units of work, Yes or No
The runtime status of the receiver channel.
Receiver channel connections
The connections that exist on the receiver channel of the WebSphere MQ link.
Saved batch status
The runtime status of message batches for the receiver channel of the WebSphere MQ link.
WebSphere MQ receiver channel saved batch status
The runtime status of message batches for the receiver channel of the WebSphere MQ link.
Queue manager
MQ channel name
Last LUWID
Last sequence number
WebSphere MQ receiver channel connections
A connection that exists on the receiver channel of the WebSphere MQ link.
WebSphere MQ receiver channel connection status
Queue manager
IP address
Status
Current LUWID
Current sequence number
Last LUWID
Last Sequence number
Messages in current batch
Number of batches received
Batch size
Number of messages received
Buffers sent
Buffers received
Bytes sent
Bytes received
Channel start time
Channel start date
Last message receive time
Last message receive date
Heartbeat interval
Maximum message length
nonpersistent message speed
Stop requested
The name of the queue manager for the WebSphere MQ link receiver channel connection.
The IP address of the queue manager for the WebSphere MQ link receiver channel connection.
The runtime status of the WebSphere MQ link receiver channel connection.
The current logical unit-of-work identifier of the WebSphere MQ link receiver channel connection.
The current sequence number for the message on the channel.
The last logical unit-of-work identifier for a message on the channel.
The last sequence number for a message on the channel.
The number of messages in the current batch on the channel.
The number of batches received on the channel.
The maximum number of messages that a batch can contain.
The number of messages received on the channel.
The number of buffers sent on the channel.
The number of buffers received on the channel.
The number of bytes received on the channel.
The number of bytes received on the channel.
The time at which the channel was last started.
The date on which the channel was last started.
The time at which the last message was received on the receiver channel connection.
The date on which the last message was received on the receiver channel connection.
The time, in seconds, between heartbeat flows passed from the receiver channel across the WebSphere MQ link when there are no messages on the transmission queue.
seconds
The maximum message length, in bytes, that can be transmitted on the channel. This is compared with the value for the partner and the actual maximum used is the lower of the two values.
bytes
The class of service for nonpersistent messages on the receiver channel.
Whether or not a manual stop request has been made for the receiver channel.
You must select a channel connection
Channel connection {0} started successfully
Channel connection {0} could not be started
Channel connection {0} stopped successfully
Channel connection {0} could not be stopped
Publish/subscribe broker profiles
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.
Topic mappings
Topic mappings for publishing and receiving (by subscription) messages across the publish/subscribe bridge between WebSphere Application Server and a message broker in a WebSphere MQ network.
Transactionality
The transactional characteristics for publishing and receiving (by subscription) messages across the publish/subscribe bridge between WebSphere Application Server and a message broker in a WebSphere MQ network.
Name
The name of the publish/subscribe broker profile.
Description
An optional description for the publish/subscribe broker profile, for administrative purposes.
Broker queue manager
The name of the queue manager for the WebSphere MQ broker.
Topic Mapping
The mapping between a topic on the service integration bus and a stream queue and subscription point provided by a WebSphere MQ broker.
Transactionality
The transactional characteristics for publishing and receiving (by subscription) messages across the publish/subscribe bridge between WebSphere Application Server and a WebSphere MQ broker.
Topic name
The name of the topic on the service integration bus. The name must be the same as the topic name on the message broker in a WebSphere MQ network.
Topic space
The name of the topic space that contains the topic.
Direction
Whether the mapping is for publishing message flows in both directions, or only to, or only from, WebSphere MQ.
Broker stream queue
The name of the stream queue at the message broker in a WebSphere MQ network.
Subscription point
The name of the WebSphere MQ broker subscription point that the topic consumes messages from.
Bi-directional
To WebSphere MQ
From WebSphere MQ
Subscriptions
The list of current broker subscriptions for this broker profile.
Number of subscriptions
The current number of broker subscriptions for this broker profile.
Broker profile subscriptions
The list of current broker subscriptions for this broker profile.
Topic name
The topic name for this subscription.
Topic space
The topic space for this subscription.
Direction
Whether the subscription is for message flows to or from WebSphere MQ.
Broker stream queue
The name of the WebSphere MQ broker stream queue that the topic publishes messages to.
Subscription point
The name of the WebSphere MQ broker subscription point that the topic consumes messages from.
Message count
The count of messages for this subscription.
Status
The current status of this subscription.
Active
In doubt
Unknown
Broker profile unsubscribe successful
Broker profile unsubscribe failed
Transactionality
The default transactional characteristics for publishing and receiving (by subscription) messages across the publish/subscribe bridge between WebSphere Application Server and a message broker in a WebSphere MQ network.
Message persistence type
The type of messages that are received and then re-published by the publish/subscribe bridge within a transaction.
Batch size
The maximum number of messages that can be sent across the publish/subscribe bridge before committing the transaction. If fewer messages are available, the commit action occurs when all messages have been received and re-published.
Persistent
nonpersistent
Transactionality
The transactional characteristics for publishing and receiving (by subscription) messages for the topic mapping across the publish/subscribe bridge.
Message type
Whether or not the messages for this topic are persistent, or inherit the type value defined for the publish/subscribe bridge.
Batch size
The maximum number of messages that can be sent for this topic across the publish/subscribe bridge before taking a checkpoint.
Inherit
Persistent
nonpersistent
n/a
Topic name contains illegal characters.
Topic name clashes with an existing topic mapping.
Broker stream queue is required for bi-directional or to-MQ topic mappings.
Subscription point is required for bi-directional or from-MQ topic mappings.
Destination mediations
A mediation that is associated with a bus destination to apply processing to messages on that destination.
Global transaction
Whether or not a global transaction is started for each message processed.
Allow concurrent mediation
Select this option (setting it to true) to apply the mediation to multiple messages concurrently. Message ordering is not preserved. The default option is false.
Selector
Controls which messages are sent to the mediation. If a message matches the rule defined by the selector text string, then the mediation is applied to the message.
Discriminator
Controls which messages have the mediation applied to them. If the topic of a message matches the rule specified by the discriminator text string, then the mediation is applied to the message. If both the selector and discriminator are specified, the message must match both rules for the mediation to be applied to the message.
UUID
The universal unique identifier assigned by the system to this mediation for administrative purposes.
Description
An optional description for the mediation, for administrative purposes.
Mediation name
The name by which this mediation is known for administrative purposes.
Handler list name
The name of the handler list that was defined when the mediation was deployed.
Subscriptions
The active subscriptions for the topic space.
Name
The name by which the active subscription is known for administrative purposes.
Subscriber ID
Destination
The name of the topic space that this subscription is for.
NoLocal
Selector
The text string that must be present in a message for the mediation to process the message.
Topic
The name of the topic that this subscription is for.
User
The user name by which the subscription is authenticated.
Messages
Messages being handled by this subscription.
Foreign buses
A foreign bus is another bus with which this bus can exchange messages.
Destination defaults
Properties to be applied when applications use destinations on this foreign bus when there is no explicit foreign destination definition.
Default priority
The default priority assigned to messages sent to this destination when a priority has not been set by the producer.
Default reliability
Maximum reliability
The maximum reliability of messages accepted by this destination.
Send allowed
Clear this option (setting it to false) to stop producers from being able to send messages to destinations on this foreign bus.
Enable producers to override default reliability
Select this option to enable producers to override the default reliability that is set on the destination.
Context properties
Context information passed to the mediation.
Foreign buses
Foreign bus
A foreign bus is another bus with which this bus can exchange messages.
Name
The name of the bus with which this bus will exchange messages.
UUID
The universal unique identifier assigned by the system to this foreign bus for administrative purposes.
Description
An optional description for the foreign bus, for administrative purposes.
Send allowed
Clear this option (setting it to false) to stop producers from being able to send messages to this foreign bus.
Destination defaults
Properties to be applied when applications use destinations on this foreign bus when there is no explicit foreign destination definition.
Create a routing definition
Select this link to define the routing definition for this foreign bus.
Create foreign bus routing definition
Create the routing definition for the foreign bus, to define the routing type and properties.
Select the type of routing to the foreign bus, a direct service integration bus link, a direct WebSphere MQ link, or an indirect route via another bus.
Routing type
Whether the foreign bus routing is a direct service integration bus link, a direct WebSphere MQ link, or an indirect route via another bus.
Name
The name by which the routing definition is known.
Inbound user ID
The user name used to authenticate inbound message flows from the foreign bus.
Outbound user ID
The user name used to authenticate outbound message flows to the foreign bus.
Next bus in route
The name of the intermediate foreign bus in cases where the foreign bus you are configuring is not directly connected to the local bus.
Direct, service integration bus link
Direct, WebSphere MQ link
Indirect
The following is a summary of your selections. Click the Finish button to complete the foreign bus routing creation.
Create a new foreign bus called "{0}".
Create a service integration bus link routing definition.
Create a WebSphere MQ link routing definition.
Use the existing direct link to the intermediary bus "{0}" as the first step in linking to the target foreign bus.
To complete the task of linking this bus to the foreign bus you must now create a service integration bus link on a messaging engine on this bus.
To complete the task of linking this bus to the foreign bus you must now create a WebSphere MQ link on a messaging engine on this bus.
Foreign bus properties
Routing definition type
Routing definition properties
Routing definition properties
Routing definition properties
Summary
Name
The name by which the routing definition is known.
UUID
The universal unique identifier assigned by the system to the routing definition (virtual link) for administrative purposes.
Inbound user ID
The user ID applied to messages arriving from the foreign bus and used to authorize their access to destinations.
Outbound user ID
The user ID applied to messages sent to the foreign bus.
Service integration bus link routing properties
The routing properties for a service integration bus link to a foreign service integration bus.
Link Ref
Topic space mapping
The mapping between topic spaces in the local bus and topic spaces in the foreign bus.
WebSphere MQ link routing properties
The routing properties for a link to a foreign bus that represents a WebSphere MQ network.
Link Ref
Indirect routing properties
The routing definition for the next service integration bus in a sequence of connected buses.
Next bus in route
The name of the next service integration bus in the sequence of connected buses.
SIBLinkRef
Engine
Name
Topic space mapping
The mapping between topic spaces in the local bus and topic spaces in the foreign bus.
Description
An optional description for the topic space mapping, for administrative purposes.
Topic space map entries
The mapping between topic spaces in the local bus and topic spaces in the foreign bus.
Topic space map entries
The mapping between a topic space in the local bus and a topic space in the foreign bus.
Local topic space
The name of the topic space in the local bus that you want to map to the topic space on the foreign bus.
Remote Topic space
The name of the topic space on the foreign bus that you want to map to the topic space on the local bus.
Service integration bus links
Service integration bus link
Links between this messaging engine and messaging engines in foreign service integration buses.
Name
The name by which the service integration bus link is known for administrative purposes.
UUID
The universal unique identifier assigned by the system to the service integration bus link for administrative purposes.
Description
An optional description for the service integration bus link, for administrative purposes.
Foreign bus name
The foreign bus to which this link connects.
Remote messaging engine name
The messaging engine on the foreign bus to which this link connects.
Target inbound transport chain
The type of transport chain used for communication with the foreign bus.
Bootstrap endpoints
The comma-separated list of endpoints used to connect to a bootstrap server.
host:port<:transport chain>
Authentication alias
The name of the authentication alias, used to authenticate access to the foreign bus.
Initial state
Whether the link is started automatically when the messaging engine is started.
Status
The run-time status of the service integration bus link.
You must select a service integration bus link
Service integration bus link {0} started successfully
Service integration bus link {0} could not be started
Service integration bus link {0} stopped successfully
Service integration bus link {0} could not be stopped
Stopped
Started
Stopped
Started
Unknown
Activity
Whether the service integration bus link is currently inactive, active, or its activity is unknown.
Inactive
Active
Unknown
Click here for activity text
Service integration bus link
A communications link between this messaging engine and a messaging engine in a foreign service integration bus.
Context properties
Context property
Context information used to enable correct processing of messages. This information adds to the context information derived from processing the message header.
Name
The name of this context property. The mediation will retrieve the context property using this name.
Context type
The type of the context property, for example, Boolean, Byte, or Character.
Context value
The value of the context property.
Context property value {0} is not valid for type {1}.
Boolean
Byte
Character
Double
Float
Integer
Long
Short
String
Overrides
Options that override the target destination.
Alias
An alias destination makes a destination available by another name and, optionally, overrides the parameters of the destination.
Create new alias destination
An alias destination makes a destination available by another name and, optionally, overrides the parameters of the destination.
Set alias destination attributes
Configure the attributes of your new alias destination
Confirm alias destination creation
Alias destination identifier is required
The following is a summary of your selections. To complete creation of the alias, click Finish. If you want to change any selections, click Previous.
If there are settings you wish to change, click Previous to review the alias destination settings.
New alias destination "{0}" will be created.
description
An optional description for the alias destination, for administrative purposes.
Default priority
The default priority assigned to messages sent to this destination when a priority has not been set by the producer.
Receive allowed
Clear this option (setting it to false) to prevent consumers from being able to receive messages from this alias destination.
Send allowed
Clear this option (setting it to false) to stop producers from being able to send messages to this alias destination.
Enable producers to override default reliability
Select this option to enable producers to override the default reliability that is set on the destination.
Maximum reliability
The maximum reliability of messages accepted by this destination.
Default reliability
Target bus
The name of the bus on which the destination for which this is an alias exists.
Target identifier
The name of the destination for which this is an alias.
Bus
The name of the bus on which this destination is known to applications.
Identifier
The name of the destination as known to applications.
Delegate authorization check to target destination
Indicates whether the authorization check is performed on the alias or the target destination.
Inherit
Best effort nonpersistent
Express nonpersistent
Reliable nonpersistent
Reliable persistent
Assured persistent
Inherit
True
False
Foreign
The name by which this foreign destination is known for administrative purposes.
Create new foreign destination
Create a new foreign destination (a destination on a foreign bus).
Set foreign destination attributes
Configure the attributes of your new foreign destination
Confirm foreign destination creation
You need to specify an identifier for the foreign destination
The following is a summary of your selections. To complete the foreign destination creation, click Finish.
If there are settings you wish to change, click Previous to review the foreign destination settings.
New foreign destination "{0}" for foreign bus "{1}" will be created.
Description
An optional description for the foreign destination, for administrative purposes.
Default priority
The default priority assigned to messages sent to this destination when a priority has not been set by the producer.
Send allowed
Clear this option (setting it to false) to stop producers from being able to send messages to this destination.
Enable producers to override default reliability
Select this option to enable producers to override the default reliability that is set on the destination.
Maximum reliability
The maximum reliability of messages accepted by this destination.
Default reliability
Bus
The name of the foreign bus on which this destination is defined.
Identifier
The identifier by which this destination is known for administrative purposes.
Messages
The messages on the message point.
Position
The position of the message on the message point list.
Message body
The contents of the message body.
Message properties
Identifier
The identifier of the message.
State
Whether this message is currently locked or unlocked.
Transaction ID
The local transaction identifier of the transaction that this message is currently part of.
Locked
Unlocked
Awaiting delivery
In doubt
Run-time message properties
Message type
The type of the message.
Approximate length
The approximate length of the message.
Time stamp
The time stamp of the message.
Message wait time
The time the message has been waiting to be consumed.
milliseconds
Current messaging engine arrival time
The time that the message arrived on the current messaging engine.
Redelivered count
The number of times that the message has been redelivered.
Security user ID
The security user ID.
Producer type
The producer type.
API message ID
The API message ID.
Correlation ID
The correlation ID.
API Message properties
Message ID
The message ID.
Correlation ID
The correlation ID.
User ID
The user ID.
Format
The Format of the message.
JMS Message properties
JMS delivery mode
The JMS delivery mode.
JMS expiration
The JMS expiration.
JMS destination
The JMS destination.
JMS reply to destination
The JMS reply to destination.
JMS redelivered
The JMS redelivered flag.
JMS type
The JMS type field.
JMSX delivery count
The JMSX delivery count.
JMSX application ID
The JMSX application ID.
Bus message properties
Discriminator
The bus discriminator.
Priority
The bus priority.
Reliability
The bus reliability.
Time to live
The time to live of the message.
milliseconds
Reply discriminator
The reply discriminator value of the bus.
Reply priority
The reply priority value of the bus.
Reply reliability
The reply reliability value of the bus.
Reply time to live
The reply time to live value of the bus.
milliseconds
Short ID
The short identifier of the bus.
System message ID
The bus system message ID.
Confirm deletion of selected messages; Yes or No
Confirm deletion of all messages on this message point; Yes or No
Approximate total message size
The approximate total length, in bytes, of the message including its header.
bytes
Displayed message body size
The amount in bytes of the message body data to be displayed.
Bytes
Mediate destination
Apply a mediation to a destination, to modify the destination handling of messages.
Please select a single destination to mediate
Cannot mediate destination as no bus members can be found on this bus.
Cannot mediate the selected type of destination.
This destination is already mediated. You can apply only one mediation to a destination.
No mediations exist on this bus
Select mediation
Select a mediation to apply to this destination
The bus destination to be mediated
The mediation to apply to this destination
Assign the mediation to a bus member
Assign the mediation to a bus member that will store and process the messages for the mediation.
The bus member where the mediation point is to be assigned
Confirm mediation of destination
The following is a summary of your selections. To complete the destination mediation, click Finish.
If there are settings you wish to change, click on the previous button to review destination mediation settings.
Mediation "{0}" will be applied to destination "{1}" on bus "{2}".
Mediation points will be created on bus member "{0}".
Message points
Server messaging
Select...
other, please specify
WebSphere MQ link inbound transports
Transport channel service chains that lead to the messaging engine WebSphere MQ link.
Messaging engine inbound transports
Transport channel service chains that lead to the messaging engine.
JFAP inbound channel
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.
Heart beat interval
The amount of idle time, in seconds, before the channel attempts to solicit a response from its peer to check that the peer is still active. The sum of this value and the heartbeat timeout value determines the maximum amount of time that it can take to discover that some types of network failure have occurred.
seconds
Heart beat timeout
The amount of time, in seconds, to wait for a response from a peer after deciding to check that the peer is still alive.
seconds
MQFAP inbound channel
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.
Failed to add a new messaging engine to the cluster.
Failed to remove messaging engine {0} from the cluster.
System
Default system exception destination
None
No exception destination is configured
Specify
Specify a named destination
Stop mode:
Immediate
Force
Mediation
The name of the mediation that mediates this destination.
The reliability assigned to a message produced to this destination when an explicit reliability has not been set by the producer.
The reliability assigned to a message produced to this destination when an explicit reliability has not been set by the producer.
The reliability assigned to a message produced to this destination when an explicit reliability has not been set by the producer.
The reliability assigned to a message produced to this destination when an explicit reliability has not been set by the producer.
Select this option to allow only one consumer to attach to each message point. If this option is not selected multiple consumers will be allowed to attach and receive messages from each message point.
messages
Remote message points
Remote queue points
The remote queue points that are producing/consuming messages to/from queue points on remote messaging engines.
Remote publication points
The remote publication points that are producing messages for publication points on remote messaging engines.
Remote queue points
The remote queue points that are producing/consuming messages to/from queue points on remote messaging engines.
Identifier
Messaging engine
Current outbound messages
Outbound messages sent
Current message requests
Completed message requests
Message requests issued
The remote queue point identifier.
The remote messaging engine where this queue point is localized.
The current number of outbound messages queued to the queue point.
The total number of messages sent to the queue point since the messaging engine started.
The current number of active message retrieval requests sent to the queue point from this remote queue point.
The total number of completed message retrieval requests sent to the queue point from this remote queue point since the messaging engine started.
The total number of active and completed message retrieval requests sent to the queue point from this remote queue point since the messaging engine started.
Message Requests
A snapshot of the current message retrieval requests from the message point.
Request ID
Times out at
Selector
Status
The request identifier.
The time at which the message retrieval request will timeout.
The retrieval request message selection critieria.
The state of the message retrieval request.
Outbound messages
The outbound message streams from this remote message point to the remote localized message point.
Priority
Reliability
Number of messages
Status
Messages
The stream priority.
The stream reliability.
The current number of messages on the stream.
The status of the stream.
View the messages on the selected stream.
View messages
Messages
A snapshot of the current outbound messages for the message point.
Sequence ID
API message ID
Time produced
State
The message sequence identifier.
The API message identifier.
The time the message was produced.
The state of the queued message.
Remote mediation points
The remote mediation points that are producing messages for mediation points on remote messaging engines.
Remote mediation points
The remote mediation points that are producing messages to mediation points on remote messaging engines.
Identifier
Messaging engine
Current outbound messages
Outbound messages sent
The remote mediation point identifier.
The remote messaging engine where this mediation point is localized.
The current number of outbound messages queued to the mediation point.
The total number of messages sent to the mediation point since the messaging engine started.
Remote Publication Points
The remote publication points that are producing messages to publication points on remote messaging engines.
Identifier
Message engine
Current outbound messages
Outbound messages sent
The remote publication point identifier.
The remote messaging engine where this publication point is localized.
The current number of outbound messages queued to the publication point.
The total number of messages sent to the publication point since the messaging engine started.
Outbound properties
Inbound properties
Messages
The messages queued outbound to the publication point on the remote messaging engine.
Topics
The topics that have been subscribed to from this remote messaging engine.
Remote subscriptions
The subscriptions that have been made from this messaging engine to subscription homes on remote messaging engines.
Topics
The topics that have been subscribed to from this remote messaging engine.
Topic
Remote subscription
The subscription that has been made from this messaging engine to a subscription home on a remote messaging engine.
Name
The name of the remote subscription.
Current message requests
The current number of active message retrieval requests sent to the publication point from this remote subscription point.
Completed message requests
The total number of completed message retrieval requests sent to the publication point from this remote subscription point since the messaging engine started.
Message requests
The total number of active and completed message retrieval requests sent to the publication point from this remote subscription point since the messaging engine started.
You must select a remote subscription
Known remote queue points
The remote messaging engines that have remote producers or consumers connected to this queue point.
Known remote queue points
The remote messaging engines that have remote producers or consumers connected to this queue point.
Messaging engine
The messaging engine where the remote queue point is located.
Current inbound messages
The current number of queued inbound messages for the queue point.
Inbound messages received
The total number of messages received on this queue point since the messaging engine started.
Current messages requests
The current number of active message retrieval requests from the remote queue point.
Completed messages requests
The total number of completed message retrieval requests from the remote queue point since the messaging engine started.
Message requests received
The total number of active and completed message retrieval from the remote queue point since the messaging engine started.
Inbound messages
The inbound message streams from the remote queue point
Message requests
The message retrieval requests from the remote queue point
Known remote publication points
The remote messaging engines that have remote producers connected to this publication point.
Known remote publication points
The remote messaging engines that have remote producers connected to this publication point.
Messaging engine
The messaging engine where the remote publication point is located.
Current inbound messages
The current number of queued inbound messages for the publication point.
Inbound messages received
The total number of messages received on this publication point since the messaging engine started.
Inbound messages
The inbound message streams from the remote publication point
Known remote subscription points
The remote messaging engines that have remote consumers connected to this subscription point.
Known remote subscription points
The remote messaging engines that have remote consumers connected to this subscription point.
Messaging engine
The messaging engine where the remote subscription point is located.
Current messages requests
The current number of active message retrieval requests from the remote subscription point.
Completed messages requests
The total number of completed message retrieval requests from the remote subscription point since the messaging engine started.
Message requests received
The total number of active and completed message retrieval from the remote subscription point since the messaging engine started.
Message requests
The message retrieval requests from the remote subscription point
Inbound messages
The inbound message streams from the remote queue point.
Priority
The stream priority.
Reliability
The stream reliability.
Number of messages
The current number of messages on the stream.
Last delivered message sequence ID
The sequence ID of the last message delivered.
Status
The status of the stream.
Messages
View the messages on the stream.
View messages
Best effort nonpersistent
Express nonpersistent
Reliable nonpersistent
Reliable persistent
Assured persistent
Active
Messages
A snapshot of the current inbound messages from the remote message point.
Sequence ID
The sequence identifier of the message.
Previous sequence ID
The sequence identifier of the message delivered before this message.
API message ID
The API message identifier.
Message requests
A snapshot of the current message retrieval requests from the remote message point.
Request ID
The request identifier.
Times out at
The time at which the message retrieval request will timeout.
Selector
The retrieval request message selection critieria.
State
The state of the message retrieval request.
Requested
Pending acknowledgment
Acknowledged
Removing
Rejected
Never
Cancel request
Cancel request and delete message
Confirm cancellation of selected message requests; Yes or No
Confirm cancellation of selected message requests and deletion of any assigned messages; Yes or No
Confirm deletion of all messages on this remote queue point; Yes or No
Confirm move of all messages on this remote queue point to the exception destination; Yes or No
Confirm deletion of all messages on this remote mediation point; Yes or No
Confirm move of all messages on this remote mediation point to the exception destination; Yes or No
Confirm deletion of all messages on this remote publication point; Yes or No
Confirm deletion of selected messages; Yes or No
Confirm the move of selected messages to the exception destination; Yes or No
Confirm clear all topics on this remote publication point; Yes or No
Request
Value
Locked
Acknowledged
Reject
Completed
Complete
Committing
Pending Send
Pending Acknowledgement
Active
Unknown
Topology
Destination resources
Services
Application
Nonpersistent
Persistent
Express
Reliable
As connection
Enabled
Disabled
As connection factory
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.
Bus name
The name of the service integration bus to connect to.
Client identifier
The JMS client identifier needed for durable topic subscriptions on all connections created using this connection factory.
Nonpersistent message reliability
The reliability applied to nonpersistent JMS messages sent using this connection factory.
Read ahead
Read ahead is an optimization that preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests.
Temporary queue name prefix
The prefix of up to twelve characters used for names of temporary queues created by applications that use this connection factory.
Temporary topic name prefix
The prefix of up to twelve characters used for names of temporary topics created by applications that use this connection factory.
Durable subscription home
The name of the messaging engine used to store messages delivered to durable subscriptions for objects created from this JMS connection factory.
Remote target group
The name of a target that resolves to a group of messaging engines.
Remote target type
The type of target named in the Remote target group property.
Target
The name of a target that identifies a group of messaging engines. Specify the type of target using the Target type property.
Target type
The type of target named in the Target property.
Target significance
This property specifies the significance of the target group.
Target inbound transport chain
The name of the protocol that resolves to a group of messaging engines.
Provider endpoints
The list of comma separated endpoints used to connect to a bootstrap server.
host:port<:transport chain>
Connection proximity
The proximity of messaging engines that can accept connection requests, in relation to the bootstrap messaging engine.
Component-managed authentication alias
This alias specifies a user ID and password to be used to authenticate connections to the JMS provider for application-managed authentication.
Authentication mechanism
The alias for the Java Authentication and Authorization Service (JAAS) login configuration that applications use to authenticate with the messaging provider.
Log missing transaction contexts
Whether or not the container logs that there is a missing transaction context when a connection is obtained.
Manage cached handles
Whether cached handles (handles held in instance variables in a bean) should be tracked by the container.
XA recovery authentication alias
The authentication alias used during XA recovery processing.
Persistent message reliability
The reliability applied to persistent JMS messages sent using this connection factory.
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.
Queue name
The name of the associated queue on the service integration bus.
Nonpersistent message reliability
The acceptable reliability of message delivery for nonpersistent JMS messages. Controls what happens to messages sent with a JMS delivery mode of NonPersistent if a delivery problem occurs.
Delivery mode
The delivery mode for messages sent to this destination. This controls the persistence of messages on this destination.
Time to live
The default length of time in milliseconds from its dispatch time that a message sent to this destination should be kept by the system.
milliseconds
Priority
The relative priority for messages sent to this destination, in the range 0 to 9, with 0 as the lowest priority and 9 as the highest priority.
Read ahead
Read ahead is an optimization that preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests.
Bus name
Enter the name of the bus on which the associated queue exists, or leave blank to use the bus to which the application connects.
JMS queue connection factory
A JMS queue connection factory is used to create connections to the associated JMS provider of JMS queues, for point-to-point messaging. Use queue connection factory administrative objects to manage JMS queue connection factories for the default messaging provider.
Bus name
The name of the service integration bus to connect to.
Messaging engine names
A comma-separated list of preferred messaging engine names.
Server name
The name of the remote server to connect to if a suitable in-process messaging engine is not found.
Port number
The port of the remote server to connect to if a suitable in-process messaging engine is not found.
Client identifier
The JMS client identifier needed for durable topic subscriptions on all connections created using this connection factory.
Nonpersistent message reliability
The reliability applied to nonpersistent JMS messages sent using this connection factory.
Read ahead
Read ahead is an optimization that preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests.
Temporary queue name prefix
The prefix used at the start of temporary queues created by applications using this connection factory.
Remote target group
The name of the WLM target group that refines where applications should be connected.
Remote target type
The type of target named in the Remote target group property.
Target
The name of a target that identifies a group of messaging engines. Specify the type of target using the Target type property.
Target type
The type of target named in the Target property.
Target significance
This property specifies the significance of the target group.
Target inbound transport chain
The name of the protocol that resolves to a group of messaging engines.
Provider endpoints
The list of endpoints that can be used to connect to a bootstrap messaging engine for initial connection to the bus.
Connection proximity
The proximity of messaging engines that can accept connection requests, in relation to the bootstrap messaging engine.
Component-managed authentication alias
This alias specifies a user ID and password to be used to authenticate connections to the JMS provider for application-managed authentication.
Authentication mechanism
The authentication mechanism to be used to authenticate connections to the JMS provider.
Log missing transaction contexts
Whether or not the container logs that there is a missing transaction context when a connection is obtained.
Manage cached handles
Whether cached handles (handles held in instance variables in a bean) should be tracked by the container.
XA recovery authentication alias
The authentication alias used during XA recovery processing.
Persistent message reliability
The reliability applied to persistent JMS messages sent using this connection factory.
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.
Topic name
The name of the topic that this JMS topic is assigned to, in the topic space defined by the Topic space property.
Topic space
The name of the topic space that contains the topic, on the service integration bus defined by the Bus name property
Nonpersistent message reliability
The acceptable reliability of message delivery for nonpersistent JMS messages. Controls what happens to messages sent with a JMS delivery mode of NonPersistent if a delivery problem occurs.
JMS delivery mode
The delivery mode for messages sent to this destination. This controls the persistence of messages on this destination.
Time to live
The default length of time in milliseconds from its dispatch time that a message sent to this destination should be kept by the system.
milliseconds
Message priority
The relative priority for messages sent to this destination, in the range 0 to 9, with 0 as the lowest priority and 9 as the highest priority.
Read ahead
Read ahead is an optimization that preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests.
Bus name
Name of bus hosting topic.
JMS topic connection factory
A JMS topic connection factory is used to create connections to the associated JMS provider of JMS topics, for publish/subscribe messaging. Use topic connection factory administrative objects to manage JMS topic connection factories for the default messaging provider.
Bus name
The name of the bus to connect to.
Messaging engine names
A comma-separated list of preferred messaging engine names.
Server name
The name of the remote server to connect to if a suitable in-process messaging engine is not found.
Port number
The port of the remote server to connect to if a suitable in-process messaging engine is not found.
Client identifier
The JMS client identifier needed for durable topic subscriptions on all connections created using this connection factory.
Nonpersistent message reliability
The reliability applied to nonpersistent JMS messages sent using this connection factory.
Read ahead
Read ahead is an optimization that preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests.
Temporary topic name prefix
The prefix used at the start of temporary topics created by applications using this connection factory.
Durable subscription home
The name of the messaging engine used to store messages delivered to durable subscriptions for objects created from this JMS connection factory.
Remote target group
The name of the WLM target group that refines where applications should be connected.
Remote target type
The type of target named in the Remote target group property.
Target
The name of a target that identifies a group of messaging engines. Specify the type of target using the Target type property.
Target type
The type of target named in the Target property.
Target significance
This property specifies the significance of the target group.
Target inbound transport chain
The name of the protocol that resolves to a group of messaging engines.
Provider endpoints
The list of endpoints that can be used to connect to a bootstrap messaging engine for initial connection to the bus.
Connection proximity
The proximity of messaging engines that can accept connection requests, in relation to the bootstrap messaging engine.
Component-managed authentication alias
This alias specifies a user ID and password to be used to authenticate connections to the JMS provider for application-managed authentication.
Authentication mechanism
The authentication mechanism to be used to authenticate connections to the JMS provider.
Log missing transaction contexts
Whether or not the container logs that there is a missing transaction context when a connection is obtained.
Manage cached handles
Whether cached handles (handles held in instance variables in a bean) should be tracked by the container.
XA recovery authentication alias
The authentication alias used during XA recovery processing.
Persistent message reliability
The reliability applied to persistent JMS messages sent using this connection factory.
Default
Enabled
Disabled
Default messaging provider
A JMS provider enables messaging based on the Java Messaging Service (JMS). It provides J2EE connection factories to create connections for JMS destinations. This panel is used to manage the default messaging provider and its JMS resources.
Default messaging provider
Default messaging
WebSphere MQ messaging provider
WebSphere MQ
Generic messaging provider
Generic
V5 default messaging provider
V5 default messaging
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.
Bus name
The name of the bus to connect to.
Client identifier
The JMS client identifier needed for durable topic subscriptions on all connections created using this activationSpec.
Durable subscription home
The name of the messaging engine used to store messages delivered to durable subscriptions for objects created from this JMS activationSpec. Required field when using a durable topic subscription.
Destination JNDI name
JNDI Name of destination
Authentication alias
The name of a J2C authentication alias used for component-managed authentication of connections to the service integration bus.
Destination type
Whether the message-driven bean uses a queue or topic destination.
Message selector
The JMS message selector used to determine which messages the message-driven bean receives.
Acknowledge mode
How the session acknowledges any messages it receives.
Subscription durability
Whether a JMS topic subscription is durable or nondurable
Subscription name
The subscription name needed for durable topic subscriptions. Required field when using a durable topic subscription.
Maximum batch size
The maximum number of messages received from the messaging engine in a single batch.
Maximum concurrent endpoints
The maximum number of endpoints to which messages are delivered concurrently.
Queue
Topic
Auto-acknowledge
Duplicates-ok auto-acknowledge
Durable
Nondurable
True
False
Server
Host
Group
Cluster
Bus
Bus member name
Bus destination name
Custom messaging engine group name
Messaging engine name
Messaging engine UUID
Bus member name
Custom messaging engine group name
Messaging engine name
None
Best effort nonpersistent
Express nonpersistent
Reliable nonpersistent
Reliable persistent
Assured persistent
As bus destination
None
Best effort nonpersistent
Express nonpersistent
Reliable nonpersistent
Reliable persistent
Assured persistent
As bus destination
Connection Factories
Destinations
Activation Specifications
Default messaging provider
Messaging provider for connection to the service integration bus.
Preferred
Required
Administration
Durable Subscription
Advanced Messaging
Advanced Administrative
Quality of Service
Connection
Advanced
Subscription Durability
Additional
Destination
Active Configuration
Runtime State
Connection State
V5 JMS servers
The JMS functions on a V5 node are served by the JMS server on that node. Use this panel to view or change the configuration properties of the selected JMS server.
A JMS provider enables asynchronous messaging based on the Java Message Service (JMS). It provides J2EE connection factories to create connections for specific JMS queue or topic destinations. V5 default messaging provider administrative objects are used to manage JMS resources for the internal V5 default messaging provider.
Queue destinations provided for point-to-point messaging by the internal V5 default messaging provider. Use WebSphere queue destination administrative objects to manage queue destinations for the internal v5 default messaging provider.
Queue destinations provided for point-to-point messaging by the internal V5 default messaging provider. Use WebSphere Queue Destination administrative objects to manage queue destinations for the internal V5 default messaging provider. NOTE: The queue name must also be added to the list of queue names in the configuration of the JMS server(s) where the queue is to be hosted.
Topic destinations provided for publish and subscribe messaging by the internal V5 default messaging provider. Use WebSphere topic destination administrative objects to manage topic destinations for the internal V5 default messaging provider.
A topic connection factory is used to create connections to the associated JMS provider of JMS topic destinations, for publish and subscribe messaging. Use WebSphere topic connection factory administrative objects to manage topic connection factories for the internal V5 default messaging provider.
A queue connection factory is used to create connections to the associated JMS provider of JMS queue destinations, for point-to-point messaging. Use WebSphere queue connection factory administrative objects to manage queue connection factories for the internal V5 default messaging provider.
A JMS provider enables asynchronous messaging based on the Java Message Service (JMS). It provides J2EE connection factories to create connections for specific JMS queue or topic destinations. WebSphere MQ messaging provider administrative objects are used to manage JMS resources for WebSphere MQ as the JMS provider.
Queue destinations provided for point-to-point messaging by the WebSphere MQ messaging provider. Use WebSphere MQ queue destination administrative objects to manage queue destinations for the WebSphere MQ messaging provider.
Topic destinations provided for publish/subscribe messaging by the WebSphere MQ messaging provider. Use WebSphere MQ topic destination administrative objects to manage topic destinations for the WebSphere MQ messaging provider.
A queue connection factory is used to create connections to the associated JMS provider of JMS queue destinations, for point-to-point messaging. Use WebSphere MQ queue connection factory administrative objects to manage queue connection factories for the WebSphere MQ messaging provider.
A topic connection factory is used to create connections to the associated JMS provider of JMS topic destinations, for publish and subscribe messaging. Use WebSphere MQ topic connection factory administrative objects to manage topic connection factories for the WebSphere MQ messaging provider.
A Generic JMS destination defines the configuration properties of either a queue (for point-to-point messaging) or a topic (for Publish and subscribe messaging) provided by the selected generic messaging provider.
A JMS connection factory is used to create connections to the associated JMS provider for JMS destinations. Use this panel to view or change the configuration properties of a JMS connection factory for the selected generic messaging provider.
Read ahead
Read ahead is an optimization that preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests.
Target inbound transport chain
The name of the protocol that resolves to a group of messaging engines.
The messaging engine has not been started. If you have tried to start the messaging engine but it remains in this state, check the logs to debug any associated problem.
The messaging engine is in a very early stage of starting. If the messaging engine remains in this state, check the logs to debug any associated problem.
The messaging engine has loaded it's classes, and is continuing to start. If the messaging engine remains in this state, check the logs to debug any associated problem.
The messaging engine is joining a DCS/HAM group. If the messaging engine remains in this state, check the logs to debug any associated problem.
The messaging engine has successfully joined a DCS/HAM group.
The messaging engine has successfully joined a DCS/HAM group, and has been notified by the HA manager to start. If the messaging engine remains in this state, check the logs to debug any associated problem.
This state follows on from the Autostarting state.
The messaging engine has successfully started, and is ready for work.
The messaging engine is trying to stop.
The messaging engine has been notified by the HA manager to stop for some reason.
The messaging engine has completed a Stop action.
The messaging engine is unloading its classes, and is continuing to stop. If the messaging engine remains in this state, check the logs to debug any associated problem.
The messaging engine has successfully unloaded its classes, and is continuing to stop. If the messaging engine remains in this state, check the logs to debug any associated problem.
The state of the messaging is unknown. If the messaging engine remains in this state, check the logs to debug any associated problem.
JNDI name
Transport Channel Name
Unique name for a given layer in a network protocol stack.
Discrimination weight
Discrimination weight is used determine the order in which the channels obtain access to the incoming connection in situations where transport channels are shared amongst several transport chains. In these cases, the lower discrimination weight will have the first opportunity to accept the incoming connection.
Custom 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 name of a bus member. This option retrieves the active messaging engines that are hosted by the named bus member (an application server or server cluster).
The name of a custom group of messaging engines (that form a self-declaring cluster). This option retrieves the active messaging engines that have registered with the named custom group.
The name of a messaging engine. This option retrieves the available endpoints that can be used to reach the named messaging engine.
It is preferred that a messaging engine be selected from the target group. A messaging engine in the target group is selected if one is available. If a messaging engine is not available in the target group, a messaging engine outside the target group is selected if available in the same service integration bus.
It is required that a messaging engine be selected from the target group. A messaging engine in the target group is selected if one is available. If a messaging engine is not available in the target group, the connection process fails.
JFAP inbound channel
MQFAP inbound channel
Data store
Alias
Destination default
Foreign destination
Destination mediation
Routing definition
Mediation point
Message
Messaging engine
Property
WebSphere MQ client link advanced property
WebSphere MQ client connection
WebSphere MQ client link
WebSphere MQ receiver channel connection
WebSphere MQ link receiver channel
WebSphere MQ link sender channel
WebSphere MQ link
Next hop bus
Port
Publish/subscribe broker profile
Transactionality
Topic mapping
Topic transactionality
Queue point
Queue
Subscription
Publication point
Topic space map entry
Topic space mapping
Topic space
Bus (new)
Virtual MQ link
Web service
Runtime service integration properties of the message.
Application Programming Interface properties of the message.
Java Message Service properties of the message.
Service integration bus properties of the message.
There is no message reliability for nonpersistent messages. If a nonpersistent message cannot be delivered, it is discarded.
Override producer quality of service
Controls the reliability delivery option for message flows between producers and the destination. Select this option to use the reliability defined for the destination instead of the reliability specified by producers.
Property
Custom properties for the type of service integration resource. Type the name and value of any custom properties that you need.
Name
The name of the custom property.
Value
The value of the custom property.
Description
An optional description of the custom property.
Required
Whether or not the custom property is required for processing to continue.
Validation Expression
An expression that is used to validate the value specified for the custom property.
The message-driven bean uses a JMS queue. The JNDI name of the JMS queue is specified on the Destination JNDI name property.
The message-driven bean uses a JMS topic. The JNDI name of the JMS topic is specified on the Destination JNDI name property.
Messages can be lost if a messaging engine fails, but are not lost under normal operating conditions.
The message provider preemptively assigns messages to consumers on nondurable subscriptions and unshared durable subscriptions. That is, read ahead optimization is turned on only when there can only be a single consumer.
The messaging provider preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests.
The messaging provider does not preemptively assign messages to consumers.
The messaging provider preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests for this destination.
The messaging provider does not preemptively assign messages to consumers for this destination.
Read ahead optimization is defined on the connection.
Retrieves the active messaging engines that are hosted by the named bus member.
Retrieves the active messaging engines that provide message points for the named destination.
Retrieves the active messaging engines that have registered with the named custom group.
Retrieves the available endpoints that can be used to reach the named messaging engine.
Retrieves the available endpoints that can be used to reach the messaging engine identified by this UUID value.
Connections can be made to messaging engines in the same application server.
Connections can be made to messaging engines in the same host.
Connections can be made to messaging engines in the same server cluster.
Connections can be made to messaging engines in the same bus.
The persistence of messages on this topic is defined by the producing application.
All messages sent to this topic are treated as nonpersistent.
All messages sent to this topic are treated as persistent.
The session automatically acknowledges the delivery of a message.
The session lazily acknowledges the delivery of messages, which can improve performance, but can lead to a message-driven bean receiving a message more than once.
The messaging provider stores messages while the message-driven bean is not available, and delivers the messages when the message-driven bean becomes available again.
The messaging provider does not store and redeliver messages if a message-driven bean is not available.
Clones are supported.
Clones are not supported.
The alias destination uses (inherits) the value of the corresponding property on the target destination.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable.
Messages are discarded when a messaging engine stops or fails.
Messages may be discarded when a messaging engine fails.
Messages are not discarded.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable.
Messages are discarded when a messaging engine stops or fails.
Messages may be discarded when a messaging engine fails.
Messages are not discarded.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable.
Messages are discarded when a messaging engine stops or fails.
Messages may be discarded when a messaging engine fails.
Messages are not discarded.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable.
Messages are discarded when a messaging engine stops or fails.
Messages may be discarded when a messaging engine fails.
Messages are not discarded.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable.
Messages are discarded when a messaging engine stops or fails.
Messages may be discarded when a messaging engine fails.
Messages are not discarded.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable.
Messages are discarded when a messaging engine stops or fails.
Messages may be discarded when a messaging engine fails.
Messages are not discarded.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable.
Messages are discarded when a messaging engine stops or fails.
Messages may be discarded when a messaging engine fails.
Messages are not discarded.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable.
Messages are discarded when a messaging engine stops or fails.
Messages may be discarded when a messaging engine fails.
Messages are not discarded.
If a message cannot be delivered, it is discarded.
Use the delivery option configured for the bus destination.
Use the delivery option configured for the bus destination.
This context has a boolean information type.
This context has a byte information type.
This context has a character information type.
This context has a double information type.
This context has a floating point information type.
This context has an integer information type.
This context has a long information type.
This context has a short information type.
This context has a string information type.
The alias destination uses (inherits) the value of the corresponding property on the target destination.
The alias destination uses the delivery option value specified by producers.
The alias destination uses the delivery option value specified by the Reliability property of the destination.
Producers can send messages to this destination.
Producers cannot send messages to this destination.
Consumers can get messages from this destination.
Consumers cannot get messages from this destination.
When the associated messaging engine is started, the gateway link is in a stopped state and cannot process any new requests for connections.
When the associated messaging engine is started, the gateway link is in a started state and can process any new requests for connections.
The gateway link is in a stopped state and cannot process any new requests for connections.
The gateway link is ready and enabled for connections.
The gateway link is not active.
The gateway link is active, processing messages for connections.
When the associated messaging engine is started, the WebSphere MQ client link is in a stopped state and cannot process any new requests for inbound connections from clients.
When the associated messaging engine is started, the WebSphere MQ client link is ready and enabled to receive inbound connections.
The WebSphere MQ client link is ready and enabled to receive inbound connections from clients, but no client connections have yet been established.
The WebSphere MQ client link is in a stopped state and cannot process any new requests for inbound connections from clients.
The WebSphere MQ client link has received an inbound connection from a client, and is in the process of starting this connection.
The WebSphere MQ client link is performing channel negotiation and is not yet ready to transfer messages.
The WebSphere MQ client link has an active session with a client, and data can be flowing between the client and the WebSphere MQ client link.
The WebSphere MQ client link, or a connection with that link, is in the process of being stopped.
The WebSphere MQ client link has established sessions with several clients, and the sessions can be in different states: Starting, Running Stopping, or Stopped.
The WebSphere MQ link is ready and enabled to create connections, but no connections have yet been established.
The WebSphere MQ link has received a connection request, and is in the process of starting this connection.
The WebSphere MQ link is performing channel negotiation and is not yet ready to transfer messages.
The WebSphere MQ link is initializing the session for a connection and is not yet ready to transfer messages.
The WebSphere MQ link is retrying a failed connection.
The channel is being used for standby purposes. Messages can be transferred only when the channel is active.
The WebSphere MQ link has an active session with WebSphere MQ, and data can be flowing between WebSphere MQ and the WebSphere MQ link.
The WebSphere MQ link, or a connection with that link, is in the process of being stopped.
The channel is waiting for the message-retry interval to finish.
The WebSphere MQ link is in a stopped state and cannot process any new requests for connections.
The WebSphere MQ link has established several sessions with WebSphere MQ, and the sessions can be in different states: Starting, Running, Stopping, or Stopped.
Nonpersistent messages can be lost if there is a transmission failure or if the channel stops when the messages are in transit.
Nonpersistent messages are not lost if there is a transmission failure or if the channel stops when the messages are in transit.
When the associated messaging engine is started, the WebSphere MQ link is started automatically and is enabled for communication with the WebSphere MQ network.
When the associated messaging engine is started, the WebSphere MQ link is in a stopped state and cannot communicate with the WebSphere MQ network.
True
The channel is in doubt about which messages have been committed by WebSphere MQ for the unit
of work that it has sent.
A stop request has been made for the connection.
A stop request has been made for the channel.
False
The channel is not in doubt about which messages have been committed by WebSphere MQ.
A manual stop request has not been made for the connection.
A manual stop request has not been made for the channel.
The name of the WebSphere MQ queue manager from which the message batch was received.
The name of the WebSphere MQ sender channel from which the message batch was received.
The last unit of work identifier for the message batch.
The last sequence number for the message batch.
When the associated messaging engine is started, the mediation is started and is available to process messages.
When the associated messaging engine is started, the mediation is stopped and is not available to process messages.
The mediation is waiting to start. This could be because the application server is not yet open for e-business, or because a previous instance of the mediation has not yet been deleted.
The mediation is started and is available to process messages.
The mediation is in the process of stopping.
The mediation is stopped. The reason why the mediation is stopped is shown in the Reason attribute.
The mediation is in the process of being deleted.
The message is locked.
The message is unlocked.
When the associated application server is started, the messaging engine is started and is available to process messages.
When the associated application server is started, the messaging engine is stopped and is not available to process messages.
Persistent messages are received and re-published.
Nonpersistent messages are received and re-published.
The mapping is used for publishing messages both from WebSphere Application Server to a WebSphere MQ network and from a WebSphere MQ network to WebSphere Application Server.
The mapping is used for publishing messages from WebSphere Application Server to a WebSphere MQ network.
The mapping is used for publishing messages from a WebSphere MQ network to WebSphere Application Server.
Inherit the value set on the Publish/subscribe broker profile.
Persistent messages are received and re-published.
Nonpersistent messages are received and re-published.
Name
The name by which this resource is known for administrative purposes.
JNDI name
The JNDI name for the resource.
Description
An optional description for the resource.
Category
An optional category string to use when classifying or grouping the resource.
J2EE Resource Provider
Allows the connection factory to be provided by different service providers. For example in JMS all of the connections will be provided by WebSphere MQ; however, it is conceivable that we would want to allow pluggability so that a customer could utilize a different provider implementation such as SonicMQ. Within the same domain, it may be possible to have more than one vendor's implementation of a resource defined; however, within the server, only one should be specified.
J2EEResourceProvider.gif
J2EEResourceProvider32X32.gif
Factories
Connection Factories
CMP Connection Factories
CMP Connection Factories are used by CMP beans to access any backend store.
JMS Destinations
JMS Connection Factories
URLs
Data Sources (Version 4)
Data Sources
Mail Sessions
Resource Env Entries
J2C Connection Factories
J2C Connection Factories represent a set of connection configuration values.
Custom Properties
Properties that may be required for Resource Providers and Resource Factories. For example, most database vendors require additional custom properties for data sources that will access the database.
Name
The name of the resource provider.
Description
A text description for the resource provider.
Classpath
A list of paths or JAR file names which together form the location for the resource provider classes. Classpath entries are separated by using the ENTER key and must not contain path separator characters (such as ';' or ':'). Classpaths may contain variable (symbolic) names which can be substituted using a variable map. Check your drivers installation notes for specific JAR file names which are required.
Native Library Path
An optional path to any native libraries (.dll, .so). Native path entries are separated by using the ENTER key and must not contain path separator characters (such as ';' or ':'). Native paths may contain variable (symbolic) names which can be substituted using a variable map.
Scope
The level to which this resource definition is visible; for example, the cell, node, cluster, or server level.
Connection pool
An optional set of connection pool settings.
All
Record all trace levels.
View the outbound topics for this publication point.
Text
Check box
Text area
Selection list
Selection list
Enable service at server startup
Select this option to start the service integration service when the application server starts.
Custom
Custom
Data type
Yes
No
Extra button strings
Cancel the selected message retrieval request and make any message that is allocated to the request available to other application requests.
Cancel the selected message retrieval request and delete any message that is allocated to the request.
In the administrative console page, to view this page click
To browse the properties of a listed item, select its name in the list.
To browse or change the properties of a listed item, select its name in the list.
To act on one or more of the listed items, select the check boxes next to the names of the items that you want to act on, then use the buttons provided.
To change what entries are listed, or to change what information is shown for entries in the list, use the Filter settings.
To create a new item, click New.
To add a server or cluster as a new member of the bus, click Add.
Configuration tab
Configuration properties for this object. These property values are preserved even if the runtime environment is stopped then restarted. See the information center task descriptions for information about how to apply configuration changes to the runtime environment.
Runtime tab
Runtime properties for this object. These properties directly affect the current runtime environment, but are not preserved when that environment is stopped. To preserve runtime property values, change the equivalent property values on the Configuration tab. See the information center task descriptions for information about how to apply configuration changes to the runtime environment.
Runtime properties for this object.
Topology tab
Topology properties for this object. These properties detail how this object relates to other objects in the system topology.
General properties
General properties
Additional properties
General properties
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane] [Content Pane] [Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane] [Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane] [Content Pane]
[Content Pane] [Content Pane] [Additional Properties]
[Content Pane] [Additional Properties]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane] [Additional Properties]
[Content Pane] [Additional Properties]
[Content Pane] [Additional Properties]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane] [Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane] [Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane] [Additional Properties]
[Content Pane] [Additional Properties]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
one of the paths shown in the table Paths to this panel
[Content Pane]
[Content Pane]
[Content Pane]
one of the paths shown in the table Paths to this panel
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
one of the paths shown in the table Paths to this panel
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane] [Additional Properties]
[Content Pane] [Additional Properties]
[Content Pane] [Additional Properties]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
[Content Pane]
General properties
[Content Pane]
[Content Pane] identifier
[Content Pane] identifier messaging_engine [Content Pane] identifier
[Content Pane] identifier name
[Content Pane] identifier
[Content Pane] identifier messaging_engine [Content Pane]
[Content Pane] identifier
[Content Pane]
[Content Pane] identifier [Content Pane] identifier [Content Pane] identifier
[Content Pane] identifier messaging_engine
[Content Pane] identifier
[Content Pane] identifier
[Content Pane] identifier
[Content Pane]
[Content Pane]
[Content Pane] identifier
[Content Pane] identifier
[Content Pane] identifier name
[Content Pane] identifier
[Content Pane] identifier
The scope displayed is for information only, and cannot be changed on this panel. If you want to browse or change this resource (or other resources) at a different scope, change the scope on the messaging provider settings panel, then click Apply, before clicking the link for the type of resource.
As a convention, use a JNDI name of the form jms/Name, where Name is the logical name of the resource. For more information about the use of JNDI and its syntax, see JNDI support in WebSphere Application Server.
This property provides a list of the J2C authentication data entry aliases that have been defined to WebSphere Application Server. You can select a data entry alias to be used to authenticate the creation of a new connection to the JMS provider.
If you have enabled global security for WebSphere Application Server, select the alias that specifies the user ID and password used to authenticate the creation of a new connection to the JMS provider. The use of this alias depends on the resource authentication (res-auth) setting declared in the connection factory resource reference of an application component's deployment descriptors.
The DefaultPrincipalMapping JAAS configuration is used by Java 2 Connectors to map users to principals that are defined in the J2C Authentication Data Entries. You can define and use other mapping configurations.
The bus looks for a suitable messaging engine in the same application server as the bootstrap messaging engine. If a suitable messaging engine is found, it is used. If a suitable messaging engine is not found, the bus fails the connection request.
The bus performs the Server-based check. If a suitable messaging engine is not found, the bus looks for a suitable messaging engine on the same host as the bootstrap messaging engine. If a suitable messaging engine is found, it is used. If a suitable messaging engine is not found, the bus fails the connection request.
The bus performs the Host-based check. If a suitable messaging engine is not found, the bus looks for a suitable messaging engine in the same custom group as the bootstrap messaging engine. If a suitable messaging engine is found, it is used. If a suitable messaging engine is not found, the bus fails the connection request.
The bus performs the Group-based check. If a suitable messaging engine is not found, the bus looks for a suitable messaging engine anywhere on the bus. If a suitable messaging engine is found, it is used. If a suitable messaging engine is not found, the bus fails the connection request.
Select this property to log connections being created without a transaction context.
The preferred way to assign a client identifier is for it to be configured on the connection factory and transparently assigned to connections that the factory creates. Alternatively, an application can set the client identifier immediately after creating the connection.
For more information about the use of client identifiers, see the "Client identifiers" section of the JMS Specification.
You can override this property for individual JMS destinations by setting the Read ahead property on the JMS destination.
You may not want to select this option if you have multiple clients attempting to receive from the same destination, because it can adversely affect message processing. For example, you allocate five messages to client A, but client A takes a long time processing the first of those messages. Meanwhile client B is available, but doing nothing, and could have been helping out with the other four messages. So, the "Default" behavior is to only have it on when there can only be one client (that is, for nondurable subscriptions and durable subscriptions in a non-clustered environment). However, if you are using a queue but you know that there is only ever one client attached to that queue at any one time, you could override the default behavior by selecting this option.
This property overrides the value set by the Read ahead property on the JMS connection factory.
The default for this property is null, which causes temporary queues to be named without any prefix.
_T<topic_prefix>_<messaging_engine_id><destination_id>
If the topic is to be used with WebSphere MQ, the topic prefix value should be a maximum of 12 characters.
The default for this property is null, which causes temporary topics to be named without any prefix.
This indicates the name of one of the following types of targets, as indicated by the Target type property
Connections are load balanced across the available messaging engines that satisfy the selection criteria.
If want applications to be able to connect to any messaging engine in the bus, do not set this property.If the selected messaging engine is in the same server as the application, a direct in-process connection is made and this transport chain property is ignored.
The transport chains represent network protocol stacks operating within a server. The name you specify must be one of the transport chains available in the server that hosts the messaging engine, as listed on the panel. The following transport chains are provided, but you can define your own transport chains on that panel.
To specify endpoint addresses, type a comma-separated list of endpoint triplets, each of the form host_name:port_number:chain_name where:
[2002:914:fc12:179:9:20:141:42]:7276:BootstrapBasicMessagingIf host_name is not specified, the default is localhost.
localhost:7276:BootstrapBasicMessaging
You can create other transport chains and specify them as part of the provider endpoints.
For an application running in an application server, this property defines how close messaging engines must be to the application server. For an application running outside an application server, this property defines how close messaging engines must be to the bootstrap server.
When searching for the most suitable messaging engine a closer messaging engine is always selected ahead of a more remote messaging engine.
Use this property to define what happens to any messages that cannot be delivered to this destination. By default, such messages are routed to the system default exception destination of the messaging engine that discovers the problem; _SYSTEM.Exception.Destination.engine_name.
If you want to messages to be sent to another exception destination, select Specify then type its name on this property. The exception destination must be a queue, on the same bus or a foreign bus, and must exist when the destination is created.
If you do not want undeliverable messages to be routed to an exception destination, select None.
If the message contains the discriminator text string, then the message is not processed by the mediation.
You should base the content of the discriminator text string on an understanding of which messages the mediation should process.
The format of the discriminator matches the topic discriminator specification.
If the message does not match the rule defined by the selector text string, then the message is not mediated.
You should base the content of the selector text string on an understanding of which messages the mediation should process.
The format of the selector string is the same as for JMS selector strings.
For non-transactional JMS message-driven beans and MessageListeners that use a JMS destination configured on the default messaging provider, best-effort nonpersistent messages are not recoverable. In this case, if a message is unlocked because the message-driven bean or MessageListener threw an exception, then the message is not redelivered or sent to the exception destination because it was deleted from the message store when it was passed to the listener. If you require higher message reliability for non-transactional JMS message-driven beans and MessageListeners, configure a different option for the Maximum reliability property of the bus destination.