WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Common help terms (text entities) for reuse

SIB service:

SIB service
Configuration reload enabled

SIB resources:

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
Unavailable
Unknown
Successful connection to WebSphere MQ Server {0}
WebSphere MQ Server configuration invalid
Data store
UUID
Data source name
Schema name
Authentication alias
Create tables
Number of permanent tables
Number of temporary tables
User
Password
Mediation thread pool
Minimum size
Maximum size
Thread inactivity timeout
milliseconds
Allow thread allocation beyond maximum thread pool size
Destinations
Destination
Identifier
UUID
Type
Description
Default reliability
Enable producers to override default reliability
Default priority
Maximum failed deliveries
Maximum reliability
Exception destination
Send allowed
Receive allowed
Quiesce mode
Receive exclusive
Maintain message order
Reply destination
Reply destination bus
Default forward routing path
Select destination type
Create new destination
Create new queue
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
Set WebSphere MQ queue point attributes
Configure the WebSphere MQ attributes of your new queue point
WebSphere MQ queue name
Inbound nonpersistent message reliability  
Inbound persistent message reliability  
Use RFH2 header when sending messages to WebSphere MQ  
Confirm queue creation
Queue identifier is required
There must be one or more bus members on the bus before you can create a queue
There must be a WebSphere MQ Queue name specified
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
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}".
There must be one or more bus members on the bus before you can create a mediation execution point
Message points
Identifier
UUID
Destination type
High message threshold
Send allowed
Receive allowed
Target UUID
Current message depth
Run-time ID
Queue
Mediation points
Inbound persistent reliability
Inbound non-persistent reliability
Port
Mediation points
Web service
Mediation points
Queue points
Messages
User
Temporary
System
Topic space
Topic access check required
Mediation points
Publication points
Mediation points
WebSphere MQ mediation points
WebSphere MQ mediation execution points
Initial state
Status
Reason
Messages
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
Custom properties
Custom property
Messaging engines
Bus members
Destinations
Mediations
Name
UUID
Description
Secure
Inter-engine authentication alias
Mediations authentication alias
Inter-engine transport chain
Discard messages
Configuration reload enabled
High message threshold
Bus Defaults
Bus members
Name
Node
Server
Cluster
Description
Add a new bus member
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
Specify connection details
You must enter a host when overriding the WebSphere MQ Connection Properties
You must enter a valid Port when overriding the WebSphere MQ Connection Properties
Override WebSphere MQ Server properties
Override Connection Settings
Transport Chain Name
Security
Security Authentication Alias
Trust user identifier received in message
Host
Port
Channel
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
Data store
Mediation thread pool
Message Points
Queue points
WebSphere MQ Queue points
Publication points
Mediation points
WebSphere MQ Mediation points
Custom properties
Custom property
Name
UUID
Description
Initial state
High message threshold
Target groups
Bus name
Bus UUID
Status
Stopped
Started
WebSphere MQ links
WebSphere MQ client links
Best effort nonpersistent
Express nonpersistent
Reliable nonpersistent
Reliable persistent
Assured persistent
Service integration
Buses
WebSphere MQ link receiver channel
Receiver MQ channel name
Inbound nonpersistent message reliability
Inbound persistent message reliability
Initial state
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
Transmission stream
Sender MQ channel name
Host name
Port
Transport chain
Disconnect interval
seconds
Short retry count
Short retry interval
seconds
Long retry count
Long retry interval
seconds
Initial state
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
seconds
bytes
Saved batch status
WebSphere MQ link
Sender channel
Receiver channel
Publish/subscribe broker profiles
Name
UUID
Description
Foreign bus name
Queue manager name
Batch size
Maximum message size
bytes
Heartbeat interval
seconds
Sequence wrap
Nonpersistent message speed
Adoptable
Initial state
Inactive
Starting
Binding
Initializing
Retrying
Standby
Running
Stopping
Paused
Stopped
Multiple
Unknown
Status
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
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
Name
UUID
Description
MQ channel name
Queue manager name
Default queue manager
Maximum message size
bytes
Heartbeat interval
seconds
Initial state
Status
Advanced properties
Client connections
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
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
Status
Inactive
Stopped
Starting
Binding
Running
Stopping
Multiple
Unknown
Client server status
Number of messages sent
Number of messages received
Number of buffers sent
Number of buffers received
Number of bytes sent
Number of bytes received
Channel start time
Channel start date
Last message send time
Last message send date
Last message receive time
Last message receive date
Heartbeat interval
seconds
Maximum message length
bytes
Stop requested
Local address
Number of API calls serviced
WebSphere MQ client link advanced properties
Inbound persistent message reliability
Inbound nonpersistent message reliability
Broker control queue
Broker publication queue
Broker subscription queue
Broker durable subscription queue
Broker connection consumer subscription queue
Broker connection consumer durable subscription queue
Default topic space
Reliable
Assured
Best effort
Express
Reliable
Delete all
Mediate
Unmediate
WebSphere MQ sender channel saved batch status
Queue manager
MQ channel name
In doubt
Current LUWID
Current sequence number
Last LUWID
Last sequence number
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
Receiver channel connections
Saved batch status
WebSphere MQ receiver channel saved batch status
Queue manager
MQ channel name
Last LUWID
Last sequence number
WebSphere MQ receiver channel connections
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
seconds
bytes
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
Topic mappings
Transactionality
Name
Description
Broker queue manager
Topic Mapping
Transactionality
Topic name
Topic space
Direction
Broker stream queue
Subscription point
Bi-directional
To WebSphere MQ
From WebSphere MQ
Subscriptions
Number of subscriptions
Broker profile subscriptions
Topic name
Topic space
Direction
Broker stream queue
Subscription point
Message count
Status
Unsubscribe
Active
In doubt
Unknown
Broker profile unsubscribe successful
Broker profile unsubscribe failed
Transactionality
Message persistence type
Batch size
Persistent
nonpersistent
Transactionality
Message type
Batch size
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
Global transaction
Allow concurrent mediation
Selector
Discriminator
UUID
Description
Mediation name
Handler list name
Subscriptions
Name
Subscriber ID
Destination
NoLocal
Selector
Topic
User
Messages
Foreign buses
Destination defaults
Default priority
Default reliability
Maximum reliability
Send allowed
Enable producers to override default reliability
Context properties
Foreign buses
Foreign bus
Name
UUID
Description
Send allowed
Destination defaults
Create a routing definition
Create foreign bus routing definition
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
Name
Inbound user ID
Outbound user ID
Next bus in route
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
UUID
Inbound user ID
Outbound user ID
Service integration bus link routing properties
Link Ref
Topic space mapping
WebSphere MQ link routing properties
Link Ref
Indirect routing properties
Next bus in route
SIBLinkRef
Engine
Name
Topic space mapping
Description
Topic space map entries
Topic space map entries
Local topic space
Remote Topic space
Service integration bus links
Service integration bus link
Name
UUID
Description
Foreign bus name
Remote messaging engine name
Target inbound transport chain
Bootstrap endpoints
host:port<:transport chain>
Authentication alias
Initial state
Status
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
Inactive
Active
Unknown
Click here for activity text
Service integration bus link
Context properties
Context property
Name
Context type
Context value
Context property value {0} is not valid for type {1}.
Boolean
Byte
Character
Double
Float
Integer
Long
Short
String
Overrides
Alias
Create new alias 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
Default priority
Receive allowed
Send allowed
Enable producers to override default reliability
Maximum reliability
Default reliability
Target bus
Target identifier
Bus
Identifier
Delegate authorization check to target destination
Inherit
Best effort nonpersistent
Express nonpersistent
Reliable nonpersistent
Reliable persistent
Assured persistent
Inherit
True
False
Foreign
Create new foreign destination
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
Default priority
Send allowed
Enable producers to override default reliability
Maximum reliability
Default reliability
Bus
Identifier
Messages
Position
Message body
Message properties
Identifier
State
Transaction ID
Locked
Unlocked
Awaiting delivery
In doubt
Run-time message properties
Message type
Approximate length
Time stamp
Message wait time
milliseconds
Current messaging engine arrival time
Redelivered count
Security user ID
Producer type
API message ID
Correlation ID
API Message properties
Message ID
Correlation ID
User ID
Format
JMS Message properties
JMS delivery mode
JMS expiration
JMS destination
JMS reply to destination
JMS redelivered
JMS type
JMSX delivery count
JMSX application ID
Bus message properties
Discriminator
Priority
Reliability
Time to live
milliseconds
Reply discriminator
Reply priority
Reply reliability
Reply time to live
milliseconds
Short ID
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
bytes
Displayed message body size
Bytes
Mediate destination
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
Set WebSphere MQ mediation point attributes
Assign a bus member where the mediation will process the messages
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
Cluster messaging
Cluster member messaging
Select...
other, please specify
WebSphere MQ link inbound transports
Messaging engine inbound transports
JFAP inbound channel
Heart beat interval
seconds
Heart beat timeout
seconds
MQFAP inbound channel
Add messaging engine
Remove messaging engine
Failed to add a new messaging engine to the cluster.
Failed to remove messaging engine {0} from the cluster.
System
None
Specify
Stop mode:
Immediate
Force
Mediation
messages
Remote message points
Remote queue points
Remote publication points
Remote queue points
Identifier
Messaging engine
Current outbound messages
Outbound messages sent
Current message requests
Completed message requests
Message requests issued
Message Requests
Request ID
Times out at
Selector
Status
Outbound messages
Priority
Reliability
Number of messages
Status
Messages
View messages
Messages
Sequence ID
API message ID
Time produced
State
Delete all messages
Move all messages
Remote mediation points
Remote mediation points
Identifier
Messaging engine
Current outbound messages
Outbound messages sent
Remote Publication Points
Identifier
Message engine
Current outbound messages
Outbound messages sent
Outbound properties
Inbound properties
Messages
Topics
Remote subscriptions
Topics
Topic
Remote subscription
Name
Current message requests
Completed message requests
Message requests
You must select a remote subscription
Known remote queue points
Known remote queue points
Messaging engine
Current inbound messages
Inbound messages received
Current messages requests
Completed messages requests
Message requests received
Inbound messages
Message requests
Known remote publication points
Known remote publication points
Messaging engine
Current inbound messages
Inbound messages received
Inbound messages
Known remote subscription points
Known remote subscription points
Messaging engine
Current messages requests
Completed messages requests
Message requests received
Message requests
Inbound messages
Priority
Reliability
Number of messages
Last delivered message sequence ID
Status
Messages
View messages
Best effort nonpersistent
Express nonpersistent
Reliable nonpersistent
Reliable persistent
Assured persistent
Active
Messages
Sequence ID
Previous sequence ID
API message ID
Message requests
Request ID
Times out at
Selector
State
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
Clear all
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
WebSphere MQ servers
WebSphere MQ Servers
WebSphere MQ Server
Name
UUID
WebSphere MQ Queue Manager name
Description
Server Type
Use bindings transport mode if available
Host
Port
Transport Chain Name
Channel
Security
Authentication Alias
Trust user identifiers received in messages
Resource Discovery
Automatic discovery of resources
Reply-to queue
Queue manager
Queue sharing group
Connection properties
Security
Resource discovery
Test connection
WebSphere MQ servers
WebSphere MQ Servers
WebSphere MQ Server
Name
UUID
Override WebSphere MQ server connection properties
Host
Port
Transport Chain Name
Channel
Authentication Alias
Trust user identifiers received in messages
Connection Properties
Security
WebSphere MQ Mediation points
WebSphere MQ Queue points
WebSphere MQ Server
Create SIB destination

SIB JMS resources:

Application
Nonpersistent
Persistent
Express
Reliable
As connection
Enabled
Disabled
As connection factory
JMS connection factory
Bus name
Client identifier
Nonpersistent message reliability
Read ahead
Temporary queue name prefix
Temporary topic name prefix
Durable subscription home
Share durable subscriptions
Remote target group
Remote target type
Target
Target type
Target significance
Target inbound transport chain
Provider endpoints
host:port<:transport chain>
Connection proximity
Component-managed authentication alias
Authentication mechanism
Log missing transaction contexts
Manage cached handles
Share data source with CMP
XA recovery authentication alias
Persistent message reliability
JMS queue
Queue name
Nonpersistent message reliability
Delivery mode
Time to live
milliseconds
Priority
Read ahead
Bus name
JMS queue connection factory
Bus name
Messaging engine names
Server name
Port number
Client identifier
Nonpersistent message reliability
Read ahead
Temporary queue name prefix
Remote target group
Remote target type
Target
Target type
Target significance
Target inbound transport chain
Provider endpoints
Connection proximity
Component-managed authentication alias
Authentication mechanism
Log missing transaction contexts
Manage cached handles
Share data source with CMP
XA recovery authentication alias
Persistent message reliability
Share durable subscriptions
JMS topic
Topic name
Topic space
Nonpersistent message reliability
JMS delivery mode
Time to live
milliseconds
Message priority
Read ahead
Bus name
JMS topic connection factory
Bus name
Messaging engine names
Server name
Port number
Client identifier
Nonpersistent message reliability
Read ahead
Temporary topic name prefix
Durable subscription home
Share durable subscriptions
Remote target group
Remote target type
Target
Target type
Target significance
Target inbound transport chain
Provider endpoints
Connection proximity
Component-managed authentication alias
Authentication mechanism
Log missing transaction contexts
Manage cached handles
Share data source with CMP
XA recovery authentication alias
Persistent message reliability
Default
Enabled
Disabled
Default messaging provider
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
Bus name
Client identifier
Durable subscription home
Destination JNDI name
Authentication alias
Destination type
Message selector
Acknowledge mode
Subscription durability
Share durable subscriptions
Subscription name
Maximum batch size
Maximum concurrent endpoints
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
In cluster
Always shared
Never shared
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
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.
Share data source with CMP
Read ahead
Target inbound transport chain

Other ui strings:

Servers
Application servers
Server messaging
Select this option if message ordering must be maintained.
Messages flow in both directions between the bus and WebSphere MQ.
Messages flow only from the bus to WebSphere MQ.
Messages flow only to the bus from WebSphere MQ.
The state of the message is unknown.
The acceptable reliability of message delivery for inbound persistent message flows from WebSphere MQ, from Reliable to Assured, in order of increasing reliability.
The acceptable reliability of message delivery for inbound nonpersistent message flows from WebSphere MQ, from Reliable to Assured, in order of increasing reliability.
Transmission of the message has been completed.
The message transmission is being committed.
The message is waiting to be sent.
The transmit message request is waiting for an acknowledgement that the message has been transmitted.
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 messaging engine has just activated and has not yet achieved any initial state. 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
Additional custom properties for this runtime component. Some components may make use of custom configuration properties which can be defined here.
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.
Allows sharing of durable subscriptions when connections are made from within a server cluster.
Durable subscriptions can be shared across connections.
Durable subscriptions are never shared across connections.
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.
The bus destination uses the default exception destination.
The bus destination has no exception destination.
The bus destination uses the exception destination specified in this field.
The message request has been made, but has not yet been acknowledged.
The message request is now waiting for acknowledgment.
The message request has been acknowledged.
The message request is being removed.
The message request has been rejected.
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 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.
The message state is in doubt.
The message is waiting to be consumed.
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.
Click this button to cancel all subscriptions.
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.
Clear all messages from this message point.
Text
Check box
Check box
Radio button
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

Clicks this button to test the connection to the WebSphere MQ server.
Add
Click this button to add a new member (a server or cluster) to the bus.
Remove
Click this button to remove a member (a server or cluster) from the bus.
New
Click this button to create a new administrative object of this type.
Delete
Click this button to delete the selected items.
Click this button to delete the object displayed.
Click this button to delete all items in the list.
Start
Click this button to start selected items.
Stop
Click this button to stop selected items.
Commit
Click this button to commit the logical unit-of-work for the message batch.
Rollback
Click this button to roll back the logical unit-of-work for the message batch.
Click this button to apply a mediation to a destination, to modify the destination handling of messages.
Click this button to remove a mediation from the destination, to remove the effect of the mediation from the destination handling of messages.
Reset
Click this button to reset a selected channel sequence number to 1. If the channel is running, the reset request will take effect only when the channel has been stopped and restarted.
Click this button to start mediating messages at this mediation point.
Click this button to stop mediating messages at this mediation point.
Click this button to add a new messaging engine to the server cluster.
Click this button to remove the selected messaging engines from the server cluster.
Click this button to stop selected WebSphere MQ links.
Delete all messages from the outbound message stream of the selected remote queue point. Messages in 'Pending Acknowledgment' state may already have been received at the remote queue point. You cannot delete messages in 'Committing' state; you must first commit their transactions.
Move all messages from the outbound message stream of the selected remote queue point to the exception destination configured for the destination. Messages in 'Pending Acknowledgment' state may already have been received at the remote queue point. Moving these messages to the exception destination results in two copies of the message in the bus. You cannot move messages in 'Committing' state; you must first commit their transactions.
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.Move
Move the selected outbound messages to the exception destination configured for the destination. Messages in 'Pending Acknowledgment' state may already have been accepted to the remote queue point. Moving these messages to the exception destination results in two copies of the message in the bus. You cannot move messages in 'Committing' state; you must first commit their transaction.
Delete
Delete the selected outbound messages from the stream. Messages in 'Pending Acknowledgment' state may already have been accepted to the remote queue point. You cannot delete messages in 'Committing' state; you must first commit their transaction.

Common administrative console path strings (text entities) for reuse

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.

Panel tabs:

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
General properties

Paths to panels:

Servers > Application servers > [Content Pane] server_name > [Server messaging] SIB service
Servers > Clusters > [Content Pane] cluster_name > [Additional Properties] Servers > [Content Pane] server_name > [Additional Properties] Messaging engines
Servers > Clusters > [Content Pane] cluster_name > [Additional Properties] Servers > [Content Pane] server_name > [Additional Properties] Messaging engines > [Content Pane] bus_member_name
Service integration > Buses
Service integration > Buses > [Content Pane] New
Service integration > Buses > [Content Pane] bus_name
Service integration > Buses > [Content Pane] bus_name > [Additional Properties] Custom properties
Service integration > Buses > [Content Pane] bus_name > [Topology] Bus members
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations
Service integration > Buses > [Content Pane] bus_name > [Topology] Foreign Buses
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Mediations
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines
Service integration > Buses > [Content Pane] bus_name > [Additional Properties] Custom properties
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] Data store
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] Message points
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] Service integration bus links
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] Mediation points
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ client links
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] Next hop buses
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] Custom properties

Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] destination_nameService integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] destination_name
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] destination_nameService integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] destination_name > [Additional Properties] Message points
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] destination_name > [Additional Properties] Message points > [Content Pane] message_point_name
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] queue_name
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] queue_name > [Additional Properties] Queue points
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] queue_name > [Additional Properties] Queue points > [Content Pane] queue_point_name
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane]
topicspace_name

Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane]
topicspace_name
> [Additional Properties]  Publication points

Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane]
topicspace_name
> [Additional Properties]  Publication points
> [Content Pane] publication_point_name

Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane]
topicspace_name
> [Additional Properties]  Publication points
> [Content Pane] publication_point_name
> Runtime

Service integration > Buses > [Content Pane] bus_name > [Destination resources] Mediations > [Content Pane] mediation_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] Mediation points > [Content Pane] mediation_point_name

Service integration > Buses > [Content Pane] bus_name > [Destination resources] Mediations > New

Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] port_name
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] webservice_name

Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Sender channels
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Sender channels > [Content Pane] channel_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Sender channels > [Content Pane] channel_name > Runtime > Saved batch statusService integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Receiver channels
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Receiver channels > [Content Pane] channel_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Receiver channels > [Content Pane] channel_name > Runtime > Receiver channel connections
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Receiver channels > [Content Pane] channel_name > Runtime > Receiver channel connections > [Content Pane] channel_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Receiver channels > [Content Pane] channel_name > Runtime > Saved batch statusService integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Publish/subscribe broker profiles
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Publish/subscribe broker profiles > [Content Pane] profile_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Publish/subscribe broker profiles
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Publish/subscribe broker profiles > [Content Pane] profile_name > [Additional Properties] Topic mappings
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Publish/subscribe broker profiles > [Content Pane] profile_name > [Additional Properties] Transactionality
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Publish/subscribe broker profiles > [Content Pane] profile_name > [Additional Properties] Topic mappings > [Content Pane] mapping_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Publish/subscribe broker profiles > [Content Pane] profile_name > [Additional Properties] Topic mappings > [Content Pane] mapping_name > [Additional Properties] Transactionality

Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] Service integration bus links > [Content Pane] link_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] Service integration bus links > New
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] Next hop buses > [Content Pane] bus_name

Service integration > Buses > [Content Pane] bus_name > [Topology] Bus members > [Content Pane] member_name

Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ client links > [Content Pane] link_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ client links > [Content Pane] link_name > [Advanced properties] > [Content Pane] property_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ client links > [Content Pane] link_name > [Additional Properties]  Client connections
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ client links > [Content Pane] link_name > [Additional Properties]  Client connections > [Content Pane] connection_name

Service integration > Buses > [Content Pane] bus_name > [Topology] Foreign Buses > [Content Pane] bus_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Foreign Buses > [Content Pane] bus_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Foreign Buses > [Content Pane] bus_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Foreign Buses > [Content Pane] bus_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Foreign Buses > [Content Pane] bus_name   > [Additional Properties] Destination defaults
Service integration > Buses > [Content Pane] bus_name > [Topology] Foreign Buses > [Content Pane] bus_name   > [Additional Properties] Routing definition
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] Next hop buses > [Content Pane] bus_name
one of the paths shown in the table Paths to this panel
Service integration > Buses > [Content Pane] bus_name > [Topology] Foreign Buses > [Content Pane] bus_name   > [Additional Properties] Destination defaults > [Additional Properties]  Context information
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Mediations > [Content Pane] mediation_name > [Additional Properties]  Context properties
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] destination_name > [Additional Properties]  Context information

one of the paths shown in the table Paths to this panel

Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] Custom properties
Service integration > Buses > [Content Pane] bus_name > [Additional Properties] Custom properties > [Content Pane] property_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] Custom properties > [Content Pane] property_name
JMS providers > Default messaging provider
JMS providers > Default messaging provider > JMS connection factories
JMS providers > Default messaging provider > JMS connection factories > [Content Pane] factory_name
JMS providers > Default messaging provider > JMS queue connection factories
JMS providers > Default messaging provider > JMS queue connection factories > [Content Pane] factory_name
JMS providers > Default messaging provider > JMS queues
JMS providers > Default messaging provider > JMS queues > [Content Pane] queue_name
JMS providers > Default messaging provider > JMS topic connection factories
JMS providers > Default messaging provider > JMS topic connection factories > [Content Pane] factory_name
JMS providers > Default messaging provider > JMS topics
JMS providers > Default messaging provider > JMS topics > [Content Pane] topic_name
JMS providers > Default messaging provider > JMS activation specifications
JMS providers > Default messaging provider > JMS activation specifications > [Content Pane] activation_specification_name
Servers > Application servers > [Content Pane] server_name > [Server messaging] WebSphere MQ link inbound transports > [Content Pane] chain_name > MQFAP inbound channel
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] Message points
one of the paths shown in the table Paths to this panel
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] queue_name > [Additional Properties] Queue points > [Content Pane] queue_point_name > Runtime > Messages
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] Mediation points > [Content Pane] mediation_point_name > Runtime > Messages
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] queue_name > [Additional Properties] Queue points > [Content Pane] queue_point_name > Runtime > Messages > [Content Pane] message_name
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] queue_name > [Additional Properties] Queue points > [Content Pane] queue_point_name > Runtime > Messages > [Content Pane] message_name > Message body
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] queue_name > [Additional Properties] Queue points > [Content Pane] queue_point_name > Runtime > Messages > [Content Pane] message_name
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] queue_name > [Additional Properties] Queue points > [Content Pane] queue_point_name > Runtime > Messages > [Content Pane] message_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Publish/subscribe broker profiles > [Content Pane] profile_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Publish/subscribe broker profiles > New
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Publish/subscribe broker profiles > [Content Pane] profile_name > Runtime > Subscriptions
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] Message points > Runtime
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] Mediation points > Runtime
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] queue_name > [Additional Properties] Queue points > Runtime
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane]
topicspace_name
> [Additional Properties]  Publication points
> Runtime

Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane]
topicspace_name
> [Additional Properties]  Publication points
> [Content Pane] publication_point_name
> Runtime
> Subscriptions

Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane]
topicspace_name
> [Additional Properties]  Publication points
> [Content Pane] publication_point_name
> Runtime
> Subscriptions
> [Content Pane] subscription_name

Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Publish/subscribe broker profiles > [Content Pane] profile_name > [Additional Properties] Topic space mapping
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Publish/subscribe broker profiles > [Content Pane] profile_name > [Additional Properties] Topic space mapping > [Additional Properties] Topic space map entries
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Publish/subscribe broker profiles > [Content Pane] profile_name > [Additional Properties] Topic space mapping > [Additional Properties] Topic space map entries > [Content Pane] map_entry_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Foreign Buses > [Content Pane] bus_name link_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Foreign Buses > [Content Pane] bus_name link_name
Servers > Application servers > [Content Pane] server_name > [Server messaging] Messaging engine inbound transports > [Content Pane] chain_name > JFAP inbound channel
General properties
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] Data store > New
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Message Points] Queue points > identifier_name > Known remote queue points
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Message Points] Queue points > identifier_name > Known remote queue points messaging_engine Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Remote Message Points] Remote publication points > identifier_name > [Inbound Properties] Remote subscriptions
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Remote Message Points] Remote publication points > identifier_name > [Inbound Properties] Remote subscriptions > [Content Pane] subscription_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Message Points] Publication points > identifier_name > [Additional Properties] Known remote publication points
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Message Points] Publication points > identifier_name > [Additional Properties] Known remote publication points messaging_engine_nameService integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Remote message points] Remote queue points
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Remote message points] Remote queue points identifier_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Remote message points] Remote publication points
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Remote message points] Remote publication points identifier_name Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Remote message points] Remote publication points > identifier_name > [Outbound properties] TopicsService integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Message points] Publication points > identifier_name > [Additional Properties] Known remote subscriptions
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Message points] Publication points > identifier_name > [Additional Properties] Known remote subscriptions messaging_engine
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Remote message points] Remote queue points identifier_name > [Additional Properties] Inbound messages
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Remote message points] Remote queue points identifier_name > [Additional Properties] Inbound messages
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Remote message points] Remote queue points identifier_name > [Additional Properties] Message requests
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Publish/subscribe broker profiles
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Remote message points] Remote mediation points
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Remote message points] Remote mediation points identifier_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Remote message points] Remote publication points identifier_name > [Outbound Properties] Messages
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Remote Message Points] Remote publication points > identifier_name > [Inbound Properties] Remote subscriptions > [Content Pane] subscription_name > [Additional Properties] Message requests
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Remote message points] Remote queue points identifier_name > [Additional Properties] Outbound messages
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Remote message points] Remote queue points identifier_name > [Additional Properties] Outbound messages
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Remote message points] WebSphere MQ Mediation Execution points
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Remote message points] WebSphere MQ Mediation Execution points mediation_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Remote message points] WebSphere MQ Mediation points
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > Runtime > [Remote message points] WebSphere MQ Mediation points mediation_name
Servers > WebSphere MQ servers
Servers > WebSphere MQ servers server_name
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] queue_name > [Message points] WebSphere MQ Queue points
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] queue_name > [Message points] WebSphere MQ Queue points name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > [Content Pane] engine_name > [Additional Properties] Mediation thread pool

Common administrative console button strings (text entities) for reuse

New
Click this button to create a new instance of this object type.
Delete
Click this button to delete a selected instance of this object type. You must first have selected the object to be deleted.
Start
Click this button to start a selected server or service. You must first have selected the item to be started.
Stop
Click this button to stop a selected server or service. You must first have selected the item to be stopped.
Commit
Click this button to commit the logical unit-of-work for the message batch.
Rollback
Click this button to roll back the logical unit-of-work for the message batch.
Click this button to apply a mediation to a destination, to modify the destination handling of messages.
Click this button to remove a mediation from the destination, to remove the effect of the mediation from the destination handling of messages.

Other common ui strings

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"JNDI support in WebSphere Application Server" in the WebSphere Application Server information center.

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.

Type the alias for the application login configuration that you want to use. Select the alias from the list displayed on the panel at Security > Global security > [Authentication] JAAS Configuration > Application login Configuration.

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.

connectionProximity_more

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.

The J2EE programming model indicates that connections should always have a transaction context. However, some applications do not correctly have a transaction context associated with them.

Select this property to log connections being created without a transaction context.

This is the name of the service integration bus that this connection factory is used to create connections to.
If an application that uses this connection factory wants to use durable subscriptions, the client identifier must be set. If the application does not set the client identifier programmatically, the value set on this administrative property is used.

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.

If you want different reliability delivery options for individual JMS destinations, you can set this property to As bus destination. The reliability is then defined by the Reliability property of the bus destination that the JMS destination is assigned to.
If you want different reliability delivery options for individual JMS destinations, you can set this property to As bus destination. The reliability is then defined by the Reliability property of the bus destination that the JMS destination is assigned to.
Messages that are assigned to a consumer are locked on the server and cannot be consumed by any other consumers for that destination. Messages that are assigned to a consumer, but not consumed before that consumer is closed, are subsequently unlocked on the server and then available for receipt by other consumers.

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.

Messages that are assigned to a consumer are locked on the server and cannot be consumed by any other consumers for that destination. Messages that are assigned to a consumer, but not consumed before that consumer is closed, are subsequently unlocked on the server and then available for receipt by other consumers.

This property overrides the value set by the Read ahead property on the JMS connection factory.

This property is for administrative purposes; for example, to enable filtering of temporary queue names.

The default for this property is null, which causes temporary queues to be named without any prefix.

This property is for administrative purposes; for example, to enable filtering of temporary topic names
Temporary topic names are created with the leading characters "_T" followed by this topic prefix then a system-assigned value.
_T<topic_prefix>_<messaging_engine_id><destination_id>
Where
<topic_prefix>
is the value specified on this property.
<messaging_engine_id>
is a 16-character identifier for the messaging engine to which the temporary topic is assigned.
<destination_id>
is a 16-character identifier assigned to the temporary topic.

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.
To enable applications to use durable subscriptions, you must set this property.
Normally, only one session at a time can have a TopicSubscriber for a particular durable subscription. This property enables you to override this behavior, to enable a durable subscription to have multiple simultaneous consumers.
Type the name of the transport chain that the application should use when connecting to a messaging engine in separate process to the application. If a messaging engine in another process is chosen, a connection can be made only if the messaging engine is in a server that runs the specified transport chain.

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 Servers > Application servers > server > Messaging engine inbound transports panel. The following transport chains are provided, but you can define your own transport chains on that panel.

InboundBasicMessaging
This is a connection-oriented protocol, using a standard TCP/IP connection (JFAP-TCP/IP). It includes support for two-phase transactional (remote XA) flows, so that a message producer or consumer, running on a client or server system, can participate in a global transaction managed on that client or server system. The specific use for the XA flows is to support access from an application running in one server to a messaging engine on second server, perhaps because the first server does not have a suitable messaging engine. If the remote XA flows are used, a transaction coordinator must be available local to the application.
InboundSecureMessaging
This is the InboundBasicMessaging protocol wrapped in SSL.
This option is used as part of the task to enable container-managed persistence (CMP) entity beans to share the database connections used by the data store of a messaging engine. This has been estimated as a potential performance improvement of 15% for overall message throughput, but can only be used for entity beans connected to the application server that contains the messaging engine.

For more information about using this option, see Enabling CMP entity beans and messaging engine data stores to share database connections.

When a client issues a client connect request, the processing attaches to the required bus according to the following logic:
  • If a target group is specified, connect to the first messaging engine that satisfies the following conditions for the target type:
    • Server Look for a messaging engine in the same server.
    • Cluster Look for a messaging engine in the same server, then on other servers in the same cluster.
    • Host Look for a messaging engine in the same server, then on other servers in the same cluster, then on other servers in the same host.
    • Bus Look for a messaging engine in the same server, then on other servers in the same cluster, then on other servers in same host, then any other messaging engine on the same bus.
  • If a target group is not specified, or a target group is specified but no suitable messaging engine is found and target significance is Preferred, connect to the first messaging engine that satisfies the following conditions for the target type:
    • Server Look for a messaging engine in the same server.
    • Cluster Connection fails.
    • Host Look for a messaging engine in the same server, then on other servers in the same host.
    • Bus Look for a messaging engine in the target group in same server, then on other servers in same host, then any other messaging engine on the same bus.
You only need to specify provider endpoints if the connection factory is used by client applications running outside of a server environment or is used by an application running on a server in one cell to connect to a target bus in another cell.
In these scenarios, the clients (or servers in another bus) cannot locate directly a suitable messaging engine to connect to in the target bus. The client must locate a suitable messaging engine by first using a bootstrap server running a SIB Service (see Servers > Application servers > server_name > SIB Service). The bootstrap server locates a suitable messaging engine on behalf of the client then tells the client how to connect to the selected messaging engine. When using a bootstrap server, one of the predefined bootstrap transport chains must be specified. The predefined bootstrap transport chains are:
BootstrapBasicMessaging
This corresponds to the server transport chain InboundBasicMessaging (JFAP-TCP/IP)
BootstrapSecureMessaging
This corresponds to the server transport chain InboundSecureMessaging (JFAP-SSL-TCP/IP)
BootstrapTunneledMessaging
Before you can use this bootstrap transport chain, you must define a corresponding server transport chain on the bootstrap server. (See Servers > Application servers > server_name > Messaging engine inbound transports.) This transport chain tunnels JFAP using HTTP wrappers.
BootstrapTunneledSecureMessaging
Before you can use this bootstrap transport chain, you must define a corresponding server transport chain on the bootstrap server. (See Servers > Application servers > server_name > Messaging engine inbound transports.) This transport chain tunnels JFAP using HTTP wrappers.

To specify endpoint addresses, type a comma-separated list of endpoint triplets, each of the form host_name:port_number:chain_name where:

host_name
is the name of the host on which the bootstrap server runs. It can be an IP address. In the case of an IPv6 address, put square braces ([]) around host_name as shown in the example below:
[2002:914:fc12:179:9:20:141:42]:7276:BootstrapBasicMessaging
If host_name is not specified, the default is localhost.
port_number
is the number of the port on which the bootstrap server listens. If not specified, the default is 7276.
chain_name
is the name of a predefined bootstrap transport chain used to connect to the bootstrap server. If not specified, the default is BootstrapBasicMessaging.
If you do not specify any endpoint value, the connection factory uses the default endpoint address:
localhost:7276:BootstrapBasicMessaging

You can create other transport chains and specify them as part of the provider endpoints.

If you want to forward messages to one or more bus destinations, type a list of bus destinations. Type each destination entry on a separate line, and in the form bus_name:destination_name or :destination_name
Where
bus_name
Is the name of the service integration bus on which the destination is configured. If you do not specify a bus name, the destination is assumed to be on the same bus as the destination for which you are setting this property.
destination_name
is the name of a bus destination.
Only messaging engines that are within the selected proximity setting can be chosen for applications to connect to.

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.

This property is intended for use with mediations on reply messages. For more information about the use of this property, see

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.

This field provides a drop-down selection list of J2C authentication aliases that have already been created. You can display details of the existing J2C authentication aliases and create new aliases on the J2EE Connector Architecture (J2C) authentication data entries panel Security > Global security > [Authentication] JAAS Configuration > J2C Authentication data.

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.


Reference topic

Terms of Use | Feedback

Last updated: 5 Oct 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\share\help-entities.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)