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

Lookup table for admin console fields and descriptions

Application
Nonpersistent
Persistent
Express
Reliable
As connection
Enabled
Disabled
Inherit from 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
A queue name must be entered
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
A topicspace name must be entered
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
Target type
Target significance
Target inbound transport chain
Provider endpoints

A JMS connection factory is used to create connections to the associated JMS provider of JMS destinations, for both point-to-point and publish/subscribe messaging. Use connection factory administrative objects to manage JMS connection factories for the default messaging provider.
The name of the service integration bus to connect to.
The JMS client identifier needed for durable topic subscriptions on all connections created using this connection factory.
The reliability applied to nonpersistent JMS messages sent using this connection factory.
Read ahead is an optimization that preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests.
The prefix of up to twelve characters used for names of temporary queues created by applications that use this connection factory.
The prefix of up to twelve characters used for names of temporary topics created by applications that use this connection factory.
The name of the messaging engine used to store messages delivered to durable subscriptions for objects created from this JMS connection factory.
Controls whether or not durable subscriptions are shared across connections with members of a server cluster.
The name of a target that resolves to a group of messaging engines.
The type of target named in the Remote target group property.
The name of a target that identifies a group of messaging engines. Specify the type of target using the Target type property.
The type of target named in the Target property.
This property specifies the significance of the target group.
The name of the inbound transport chain that the application should target when connecting to a messaging engine in a 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 inbound transport chain. Refer to the InfoCenter for more information.
A comma-separated list of endpoint triplets, with the syntax hostName:portNumber:chainName, used to connect to a bootstrap server. For example Merlin:7276:BootstrapBasicMessaging,Gandalf:5557:BootstrapSecureMessaging. If hostName is not specified, the default is localhost. If portNumber is not specified, the default is 7276. If chainName is not specified, the default is BootstrapBasicMessaging. Refer to the InfoCenter for more information.
The proximity of messaging engines that can accept connection requests, in relation to the bootstrap messaging engine.
This alias specifies a user ID and password to be used to authenticate connections to the JMS provider for application-managed authentication.
The alias for the Java Authentication and Authorization Service (JAAS) login configuration that applications use to authenticate with the messaging provider.
Whether or not the container logs that there is a missing transaction context when a connection is obtained.
Whether cached handles (handles held in instance variables in a bean) should be tracked by the container.
Allow sharing of connections between JMS and container-managed persistence (CMP) entity beans.
The authentication alias used during XA recovery processing.
The reliability applied to persistent JMS messages sent using this connection factory.
A JMS queue is used as a destination for point-to-point messaging. Use JMS queue destination administrative objects to manage JMS queues for the default messaging provider.
The name of the associated queue on the service integration bus.
The acceptable reliability of message delivery for nonpersistent JMS messages. Controls what happens to messages sent with a JMS delivery mode of NonPersistent if a delivery problem occurs.
The delivery mode for messages sent to this destination. This controls the persistence of messages on this destination.
The default length of time in milliseconds from its dispatch time that a message sent to this destination should be kept by the system.
The relative priority for messages sent to this destination, in the range 0 to 9, with 0 as the lowest priority and 9 as the highest priority.
Read ahead is an optimization that preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests.
Enter the name of the bus on which the associated queue exists, or leave blank to use the bus to which the application connects.
A JMS queue connection factory is used to create connections to the associated JMS provider of JMS queues, for point-to-point messaging. Use queue connection factory administrative objects to manage JMS queue connection factories for the default messaging provider.
The name of the service integration bus to connect to.
A comma-separated list of preferred messaging engine names.
The name of the remote server to connect to if a suitable in-process messaging engine is not found.
The port of the remote server to connect to if a suitable in-process messaging engine is not found.
The JMS client identifier needed for durable topic subscriptions on all connections created using this connection factory.
The reliability applied to nonpersistent JMS messages sent using this connection factory.
Read ahead is an optimization that preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests.
The prefix used at the start of temporary queues created by applications using this connection factory.
The name of the WLM target group that refines where applications should be connected.
The type of target named in the Remote target group property.
The name of a target that identifies a group of messaging engines. Specify the type of target using the Target type property.
The type of target named in the Target property.
This property specifies the significance of the target group.
The name of the inbound transport chain that the application should target when connecting to a messaging engine in a 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 inbound transport chain. Refer to the InfoCenter for more information.
A comma-separated list of endpoint triplets, with the syntax hostName:portNumber:chainName, used to connect to a bootstrap server. For example Merlin:7276:BootstrapBasicMessaging,Gandalf:5557:BootstrapSecureMessaging. If hostName is not specified, the default is localhost. If portNumber is not specified, the default is 7276. If chainName is not specified, the default is BootstrapBasicMessaging. Refer to the InfoCenter for more information.
The proximity of messaging engines that can accept connection requests, in relation to the bootstrap messaging engine.
This alias specifies a user ID and password to be used to authenticate connections to the JMS provider for application-managed authentication.
The authentication mechanism to be used to authenticate connections to the JMS provider.
Whether or not the container logs that there is a missing transaction context when a connection is obtained.
Whether cached handles (handles held in instance variables in a bean) should be tracked by the container.
Allow sharing of connections between JMS and container-managed persistence (CMP) entity EJBs.
The authentication alias used during XA recovery processing.
The reliability applied to persistent JMS messages sent using this connection factory.
Controls whether or not durable subscriptions are shared across connections with members of a server cluster.
A JMS topic is used as a destination for publish/subscribe messaging. Use topic destination administrative objects to manage JMS topics for the default messaging provider.
The name of the topic that this JMS topic is assigned to, in the topic space defined by the Topic space property.
The name of the topic space that contains the topic, on the service integration bus defined by the Bus name property
The acceptable reliability of message delivery for nonpersistent JMS messages. Controls what happens to messages sent with a JMS delivery mode of NonPersistent if a delivery problem occurs.
The delivery mode for messages sent to this destination. This controls the persistence of messages on this destination.
The default length of time in milliseconds from its dispatch time that a message sent to this destination should be kept by the system.
The relative priority for messages sent to this destination, in the range 0 to 9, with 0 as the lowest priority and 9 as the highest priority.
Read ahead is an optimization that preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests.
Name of bus hosting topic.
A JMS topic connection factory is used to create connections to the associated JMS provider of JMS topics, for publish/subscribe messaging. Use topic connection factory administrative objects to manage JMS topic connection factories for the default messaging provider.
The name of the bus to connect to.
A comma-separated list of preferred messaging engine names.
The name of the remote server to connect to if a suitable in-process messaging engine is not found.
The port of the remote server to connect to if a suitable in-process messaging engine is not found.
The JMS client identifier needed for durable topic subscriptions on all connections created using this connection factory.
The reliability applied to nonpersistent JMS messages sent using this connection factory.
Read ahead is an optimization that preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests.
The prefix used at the start of temporary topics created by applications using this connection factory.
The name of the messaging engine used to store messages delivered to durable subscriptions for objects created from this JMS connection factory.
Controls whether or not durable subscriptions are shared across connections with members of a server cluster.
The name of the WLM target group that refines where applications should be connected.
The type of target named in the Remote target group property.
The name of a target that identifies a group of messaging engines. Specify the type of target using the Target type property.
The type of target named in the Target property.
This property specifies the significance of the target group.
The name of the inbound transport chain that the application should target when connecting to a messaging engine in a 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 inbound transport chain. Refer to the InfoCenter for more information.
A comma-separated list of endpoint triplets, with the syntax hostName:portNumber:chainName, used to connect to a bootstrap server. For example Merlin:7276:BootstrapBasicMessaging,Gandalf:5557:BootstrapSecureMessaging. If hostName is not specified, the default is localhost. If portNumber is not specified, the default is 7276. If chainName is not specified, the default is BootstrapBasicMessaging. Refer to the InfoCenter for more information.
The proximity of messaging engines that can accept connection requests, in relation to the bootstrap messaging engine.
This alias specifies a user ID and password to be used to authenticate connections to the JMS provider for application-managed authentication.
The authentication mechanism to be used to authenticate connections to the JMS provider.
Whether or not the container logs that there is a missing transaction context when a connection is obtained.
Whether cached handles (handles held in instance variables in a bean) should be tracked by the container.
Allow sharing of connections between JMS and container-managed persistence (CMP) entity EJBs.
The authentication alias used during XA recovery processing.
The reliability applied to persistent JMS messages sent using this connection factory.
A JMS provider enables messaging based on the Java Messaging Service (JMS).  It provides J2EE connection factories to create connections for JMS destinations. This panel is used to manage the default messaging provider and its JMS resources.
A JMS activation specification is associated with one or more message-driven beans and provides the configuration necessary for them to receive messages.
The name of the bus to connect to.
The JMS client identifier needed for durable topic subscriptions on all connections created using this activation specification.
The name of the messaging engine used to store messages delivered to durable subscriptions for objects created from this JMS activation specification. This is a required field when using a durable topic subscription.
JNDI Name of destination
The name of a J2C authentication alias used for component-managed authentication of connections to the service integration bus.
Whether the message-driven bean uses a queue or topic destination.
The JMS message selector used to determine which messages the message-driven bean receives. The value is a string that is used to select a subset of the available messages. The syntax is based on a subset of the SQL 92 conditional expression syntax, as described in the JMS specification. Refer to the InfoCenter for more information.
How the session acknowledges any messages it receives.
Whether a JMS topic subscription is durable or nondurable
Controls whether or not durable subscriptions are shared across connections with members of a server cluster.
The subscription name needed for durable topic subscriptions. Required field when using a durable topic subscription.
The maximum number of messages received from the messaging engine in a single batch.
The maximum number of endpoints to which messages are delivered concurrently.
The JMS functions on a V5 node are served by the JMS server on that node. Use this panel to view or change the configuration properties of the selected JMS server.
A JMS provider enables asynchronous messaging based on the Java Message Service (JMS).  It provides J2EE connection factories to create connections for specific JMS queue or topic destinations. V5 default messaging provider administrative objects are used to manage JMS resources for the internal V5 default messaging provider.
Queue destinations provided for point-to-point messaging by the internal V5 default messaging provider.  Use WebSphere queue destination administrative objects to manage queue destinations for the internal v5 default messaging provider.
Topic destinations provided for publish and subscribe messaging by the internal V5 default messaging provider. Use WebSphere topic destination administrative objects to manage topic destinations for the internal V5 default messaging provider.
A topic connection factory is used to create connections to the associated JMS provider of JMS topic destinations, for publish and subscribe messaging.  Use WebSphere topic connection factory administrative objects to manage topic connection factories for the internal V5 default messaging provider.
A queue connection factory is used to create connections to the associated JMS provider of JMS queue destinations, for point-to-point messaging.  Use WebSphere queue connection factory administrative objects to manage queue connection factories for the internal V5 default messaging provider.
A JMS provider enables asynchronous messaging based on the Java Message Service (JMS).  It provides J2EE connection factories to create connections for specific JMS queue or topic destinations. WebSphere MQ messaging provider administrative objects are used to manage JMS resources for WebSphere MQ as the JMS provider.
Queue destinations provided for point-to-point messaging by the WebSphere MQ messaging provider.  Use WebSphere MQ queue destination administrative objects to manage queue destinations for the WebSphere MQ messaging provider.
Topic destinations provided for publish/subscribe messaging by the WebSphere MQ messaging provider.  Use WebSphere MQ topic destination administrative objects to manage topic destinations for the WebSphere MQ messaging provider.
A queue connection factory is used to create connections to the associated JMS provider of JMS queue destinations, for point-to-point messaging. Use WebSphere MQ queue connection factory administrative objects to manage queue connection factories for the WebSphere MQ messaging provider.
A topic connection factory is used to create connections to the associated JMS provider of JMS topic destinations, for publish and subscribe messaging.  Use WebSphere MQ topic connection factory administrative objects to manage topic connection factories for the WebSphere MQ messaging provider.
A Generic JMS  destination defines the configuration properties of either a queue (for point-to-point messaging) or a topic (for Publish and subscribe messaging) provided by the selected generic messaging provider.
A JMS connection factory is used to create connections to the associated JMS provider for JMS destinations. Use this panel to view or change the configuration properties of a JMS connection factory for the selected generic messaging provider.
Allow sharing of connections between JMS and container-managed persistence (CMP) entity beans.
Read ahead is an optimization that preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests.
The name of a target that identifies a group of messaging engines. Specify the type of target using the Target type property.
The type of target named in the Target property.
This property specifies the significance of the target group.
The name of the inbound transport chain that the application should target when connecting to a messaging engine in a 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 inbound transport chain. Refer to the InfoCenter for more information.
A comma-separated list of endpoint triplets, with the syntax hostName:portNumber:chainName, used to connect to a bootstrap server. For example Merlin:7276:BootstrapBasicMessaging,Gandalf:5557:BootstrapSecureMessaging.

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 started as there is no runtime initialized for it yet, retry the operation once it has initialized. If dynamic configuration reload is not enabled for this bus then the server will need to be restarted.
The messaging engine {0} cannot be stopped.
The messaging engine {0} cannot be stopped as there is no runtime initialized for it. This means the messaging engine is stopped.
The messaging engine {0} is already started.
The messaging engine {0} is already stopped.
At least one WebSphere MQ server must be selected to perform this action.
To test the connection to a WebSphere MQ server at least one WebSphere MQ server must be selected.
Uninitialized
Initializing
Initialized
Joining
Joined
Autostarting
Starting
Started
Stopping
Stopping member
Stopped
Destroying
Destroyed
Unavailable
Unknown
WebSphere MQ server {1} connection test succeeded for WebSphere MQ queue manager {0}.
WebSphere MQ server {1} connection test succeeded for WebSphere MQ queue sharing group {0}.
WebSphere MQ server {0} configuration invalid.
Data store
UUID
Data source name
Schema name
Authentication alias
Create tables
Number of tables for permanent objects
Number of tables for temporary objects
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
The destination's default reliability can not be greater than the destination's maximum 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 strict message order
Reply destination
Reply destination bus
Default forward routing path
Select destination type
The destination name {0} is invalid as it starts with an '_'.
A destination with name {0} already exists.
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 attributes of the new WebSphere MQ queue point
WebSphere MQ queue name
Inbound nonpersistent message reliability  
Inbound persistent message reliability  
Include an RFH2 message 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 maximum length for a WebSphere MQ queue name is 48 characters.  The WebSphere MQ queue name specified is longer than this.
The value {0} for the WebSphere MQ queue name contains invalid characters.  The WebSphere MQ queue allowable characters range a-z, A-Z, 0-9, ., /, % and _.
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.
The WebSphere MQ queue name {0} has been used for both receiving messages into the mediation and the target destination for the outbound side of the mediation.
The maintain strict message order setting will override the receive exclusive setting.
The maintain strict message order setting has been set for a destination that is mediated by a mediation which allows concurrent mediations. The allow concurrent mediations setting will be overridden.
Message points
Identifier
UUID
Destination type
High message threshold
Send allowed
Receive allowed
Target UUID
Current message depth
Run-time ID
Queue
Mediation points
This destination has been configured with strict message ordering and has also been assigned to WebSphere MQ.  The maintenance of message ordering will also depend on the settings in WebSphere MQ.
Inbound persistent reliability
Inbound nonpersistent 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
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
Externally mediated
Buses
Bus
Custom properties
Custom property
The custom property "{0}" has already been configured on this service integration bus.
Messaging engines
Bus members
Destinations
Mediations
Name
UUID
Description
Enable bus security
Inter-engine authentication alias
Mediations authentication alias
Inter-engine transport chain
Discard messages
Configuration reload enabled
High message threshold
Bus Defaults
Bus
Add...
Bus members
Name
Node
Server
Cluster
Description
Add a new bus member
Select server, cluster or WebSphere MQ server
Choose the server, cluster or WebSphere MQ server to add to the bus
Selection
You must select a server, cluster or WebSphere MQ server 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.
Override WebSphere MQ Server properties
Connection settings
Override WebSphere MQ server connection settings
Transport chain name
Security
Messaging authentication alias
Trust user identifiers received in messages
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}" using a file store as the message store.
New bus member "{0}" will be added to bus "{1}" using a data store as the message store.
New bus member "{0}" will be added to bus "{1}".
The associated bus member could not be found.
A file store has been selected for a server cluster that contains members whose version is not at least WebSphere Application Server 6.1. The cluster policy must ensure that the messaging engines run on only the WebSphere Application Server version 6.1 or later nodes.
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
Messaging engines for {0}
Best effort nonpersistent
Express nonpersistent
Reliable nonpersistent
Reliable persistent
Assured persistent
Service integration
Buses
Bus Security
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
Current outbound messages
Messages sent
Messages received
Sender channel transmitter
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
A Foreign bus connection with routing type Direct, WebSphere MQ link, must be defined on the local Service Integration bus before a new WebSphere MQ Link can be created.
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.
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
Unable to delete subscription. You can only delete durable subscriptions that are not in use.
Foreign buses
Destination defaults
Default priority
Default reliability
Maximum reliability
Send allowed
Enable producers to override default reliability
Context properties
Foreign buses
Foreign bus connection
Name
UUID
Description
Send allowed
Destination defaults
Create a routing definition
A link has not been configured for this foreign bus connection. Select a messaging engine on this bus and from there configure a link.
The name of the foreign bus connection cannot be the same as the local bus "{0}" on which it is to be created.
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
Foreign messaging engine
Current outbound messages
Messages sent
Current inbound messages
Messages received
Target inbound transport chain
Bootstrap endpoints
host:port<:transport chain>
Authentication alias
Initial state
Status
You must select a service integration bus link
Start of Service integration bus link {0} has been successfully initiated
Service integration bus link {0} could not be started
Stop of Service integration bus link {0} has been successfully initiated
Service integration bus link {0} could not be stopped
Stopped
Started
Stopped
Started
Unknown
Activity
Inactive
Active
Unknown
A link with name {0} already exists.  Link names must be unique
A Foreign bus connection with routing type Direct, Service Integration Bus link, must be defined on the local Service Integration bus before a new Service integreation bus link can be created.
Click here for activity text
Service integration bus links
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
Exception destination timestamp
Exception destination reason
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
Deleting messages from this system destination is likely to lead to undefined behavior.
{0}.
An attempt has been made to delete a message from a temporary queue.  This is not supported.
The selected message could not be deleted due to the following error.  {0}.
Approximate total message size
bytes
Displayed message body size
Bytes
Please select the destinations to unmediate.
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 the messages for the mediation. When assigning the mediation to a server or cluster bus member, this will also be where the messages are processed. When the mediation is assigned to a WebSphere MQ server bus member, a server or cluster bus member which will process the messages, must be selected.
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 run
Select a bus member where the mediation will run.
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}".
Destination "{0}" on bus "{1}" will be mediated by an external application.
A mediation execution point 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 server name
Description
Server Type
Use bindings transport mode if available
WebSphere MQ host
WebSphere MQ port
Transport chain name
WebSphere MQ channel
Security
Messaging authentication alias
Trust user identifiers received in messages
Resource Discovery
Resource discovery authentication alias
Automatic discovery of resources
Reply-to queue
Queue manager
Queue sharing group
Connection properties
Security
Resource discovery
Test connection
Resource discovery has been enabled so a WebSphere MQ queue name must be supplied as a reply-to queue.
The secure transport chain has not been selected for use with one or more authentication aliases. This will allow passwords to be sent unencrypted. Please confirm this configuration is acceptable: Yes
WebSphere MQ servers
WebSphere MQ Servers
WebSphere MQ Server
Name
UUID
Override WebSphere MQ server connection properties
WebSphere MQ host
WebSphere MQ port
Transport chain name
WebSphere MQ channel
Messaging authentication alias
Trust user identifiers received in messages
Connection Properties
Security
WebSphere MQ mediation points
WebSphere MQ queue points
WebSphere MQ server
The transport chain {0} is not a permitted transport chain for the bus.  The transport chain must be added to the permitted transports for the bus to be able to connect to WebSphere MQ.
The transport chain {0} was not found in the administrative domain.  The transport chain must be defined to be able to connect to WebSphere MQ.
The messaging engine bus has been defined to only permit SSL enabled transports.  The transport chain {0} has not been defined as an SSL transport so the bus will not be able to connect to WebSphere MQ.
Create SIB destination
Unable to provide selection of WebSphere MQ queue names.  Please specify the WebSphere MQ queue name.
Unable to provide selection of WebSphere MQ queue names due to error\: {0}.
{0}
Unable to provide selection of WebSphere MQ queue names as the required outbound transport chain {0} is not defined on the admin console server: {1}. Please specify the WebSphere MQ queue name.
WebSphere MQ server {0} connection test failed for WebSphere MQ queue manager {1}.  {2}.
WebSphere MQ server {0} connection test failed for WebSphere MQ queue sharing group {1}.  {2}.
WebSphere MQ server {0} connection test failed for WebSphere MQ queue manager {1} with an exception: {2}.
WebSphere MQ server {0} connection test failed for WebSphere MQ queue sharing group {1} with an exception: {2}.
Unable to test connection to the WebSphere MQ server {0} as the required outbound transport chain {1} is not defined on the admin console server: {2}.
File store
Select the type of message store
Provide the message store properties
Provide the message store properties
Choose the type of message store for the persistence of message state
Provide properties for the file store
Select properties for the data store
File store
Data store
Data source
Create default data source with specified JNDI name
When selecting to create the default data source with specified JNDI name, a JNDI name must be provided.
Create default data source with generated JNDI name
Data source JNDI name
Use existing data source
When selecting to use an existing data source, an existing datasource name must be provided.
UUID
Log size
Log directory path
Default log directory path
Log
Store
Permanent and temporary stores
Same settings for permanent and temporary stores
Minimum permanent store size
Maximum permanent store size
Unlimited permanent store size
Permanent store directory path
Default permanent store directory path
Minimum temporary store size
Maximum temporary store size
Unlimited temporary store size
Temporary store directory path
Default temporary store directory path
Permanent store
Temporary store
MB
MB
The minimum value for the maximum permanent store size must be greater than 50.
The minimum value for the maximum temporary store size must be greater than 50.
The minimum value for the minimum temporary store size must be greater than 0.
The minimum permanent store size {0} can't be greater than the maximum permanent store size {1}.
The minimum temporary store size {0} can't be greater than the maximum temporary store size {1}.
Minimum permanent store size {0} can not be less than log size {1}.
Minimum temporary store size {0} can not be less than log size {1}.
Must select a message store type.
The log directory for a file store is required for a cluster bus member.
The permanent store directory for a file store is required for a cluster bus member.
The temporary store directory for a file store is required for a cluster bus member.
The log directory for a file store is required when the default log directory isn't selected.
The permanent store directory for a file store is required when the default permanent store directory isn't selected.
The temporary store directory for a file store is required when the default temporary store directory isn't selected.
The data source JNDI name is required for a cluster bus member.
bytes
Add a new messaging engine to a cluster
Configure
Message store type
Message store
Enabled
Disabled
Security
Security for bus {0}
Create a new bus
Confirm create of new bus
Create a new messaging engine bus
Bus name not specified.  The bus name must be set when creating a new bus.
Bus with name {0} already exists.  A bus name must be unique within the administrative domain.
Invalid bus name {0}.  Bus names cannot contain any of the following characters \\/,#$@:;\"*?<>|=+&%' or start with _ or . or contain ]]> .
The following is a summary of your selections. To complete the bus creation, click Finish.
If there are settings you wish to change, click Previous to review bus settings.
New bus "{0}" will be created with bus security setting "{1}".
Configure the attributes of your new bus
Bus name
Bus security
Add a user or group to the bus connector role.
Users and groups in the bus connector role
Users and groups in the bus connector role
Bus Connector Role
Give a user the bus connector role
User name
Give a group the bus connector role
Group name
Name
Type
Give a specific group the bus connector role
Server - Allow servers to connect to the bus
Everyone - Allow unauthenticated users to connect to the bus
All Authenticated - Allow all authenticated users to connect to the bus
User
Group
Failed to create the specified user or group due to error {0}.
Adding a user to the bus connector role has been selected, but a user has not been entered
Adding a Group to the bus connector role has been selected, but a group has not been entered
Permitted transports
Allow the use of all defined transport channel chains
Restrict the use of defined transport channel chains to those protected by SSL
Restrict the use of defined transport channel chains to the list of permitted transports
Security
Authorization
This bus was configured to enforce the associated security policy. In order to enforce this policy administrative security for the cell must be enabled. It is currently disabled as a result the bus will not enforce the security policy. Bus Security will be disabled by clicking Apply or OK on this page.
Secure Administration and Applications
Permitted transports
Permitted transports
Transport Name
Transport chain name
Add a transport to the list of permitted transport.
Failed to create the specified permitted transport due to error {0}.
Adding a permitted transport to a bus has failed as no permitted transport was selected.
Alias queue
Local queue
Remote queue
Cluster queue
Model queue
Not applicable
Queue manager
Copy
Live
Queue manager group
Private
Shared
Properties for WebSphere MQ queue
Put enabled
Get enabled
Shared
Description
Current depth
Maximum depth
Input process count
Output process count
Disposition
Queue type
None
Create a new instance?
Create another instance?
Yes
No
Summary
Summary
The summary of actions that have occurred during (or will have occur upon completion of) this wizard.
Summary of actions
Refresh
This configuration is not valid for a node that is not at least WebSphere Application Server version 6.1.
This configuration is not valid for a bus that contains members that are not at least WebSphere Application Server version 6.1.
Maintain strict message order is set for this destination which has message points on servers of a version earlier than WebSphere Application Server 6.1, which does not support this attribute. Strict message ordering will only be maintained on the message flows between the version 6.1 servers.
The version of the server being added to this bus does not support the bus security settings currently configured.
A member of this bus is of a version that does not support these bus security settings.
Security settings for bus "{0}" are not compatible with server "{1}" because it resides on pre-6.1 node "{2}".
Security settings for bus "{0}" are not compatible with cluster "{1}" because one or more of its member servers reside on a pre-6.1 node.
The value "{1}" for the permitted transport chains bus security attribute is not valid for bus "{0}" because the bus contains at least one pre-6.1 bus member.
Found group "Server" in the bus connector role for bus "{0}". This is not allowed because the bus contains at least one pre-6.1 bus member.
The group "Server" is not valid for bus "{0}" because bus security is enabled on that bus, and the bus contains at least one pre-6.1 bus member.
Link transmitters
Not supported
Foreign Bus Connection Wizard
Foreign Bus Connection
Foreign Bus Connections
Bus Connection Type
Summary
Indirect Foreign Bus Connection
Indirect Connection Details
Foreign Bus Connection Direct
Foreign Bus Type
Foreign Bus Connection Direct to SIB
Local Bus Details
Foreign Bus Details
Publish-Subscribe Details (optional)
Foreign Bus Connection Direct to WebSphere MQ
Local Bus Details
WebSphere MQ Details
Publish-Subscribe Details (optional)
Bus connection type
Direct connection
Indirect, using another bus
Will the foreign bus be connected directly to this bus or will it be reached using another foreign bus?
An Indirect foreign bus connection requires a 'next hop' attribute that must be a Direct foreign bus connection. No Direct foreign bus connections exist on the local bus.
The following is a summary of your selections. To complete creation of the Foreign Bus Connection, click Finish. If you want to change any selections, click Previous.
An indirect foreign bus definition will be created with the name:
The next hop bus attribute will be set to:
A direct foreign bus definition will be created with the name:
An MQ Link will be created with the name:
An MQ Link sender channel will be created with the name:
An MQ Link receiver channel will be created with the name:
A SIB Link will be created with the name:  
The following topic space mappings will be created:
Foreign bus type
Service Integration Bus
WebSphere MQ
What is the type of the foreign bus?
A Direct foreign bus connection requires a 'messaging engine' attribute to host the link. No messaging engines could be found.
Bus connection details
Target foreign bus name
Next hop foreign bus
The Target Foreign Bus name must be supplied.
Local bus details
Messaging Engine to host the connection
Inbound User ID
Foreign Bus Details
Security Details
Configure Publish-Subscribe Messaging for this connection
Name of Service Integration Bus to connect to (the foreign bus)
Gateway Messaging Engine in the foreign bus
Service Integration Bus Link Name
Configure a foreign bus in a remote cell
Configure a foreign bus in the local cell
Bootstrap Service Integration Bus Provider Endpoints
The name of Service Integration Bus to connect to must be supplied.
A Foreign Bus Connection cannot be created using the name supplied for the Service Integration Bus to connect to attribute as it is not unique among Foreign Bus Connections on the local Service Integration Bus.
The gateway messaging engine name must be supplied.
The service integration bus link name must be supplied.
The Service Integration Bus Link name supplied is already being used by an existing Service Integration Bus Link on the same Service Integration Bus. Please supply a unique Service Integration Bus Link name.
In order to configure Publish-Subscribe messaging for this link, at least one destination of type 'Topic Space' must exist on the local bus.
Secure Connection
Target Inbound Transport Chain
Authentication Alias
If the connection is to be secure, a value must be supplied for the Authentication Alias field.
If the connection is to be secure, a value must be supplied for the Target Inbound Transport Chain field.
The field Bootstrap Service Integration Bus Provider Endpoints must be supplied if a foreign bus is being configured in a remote cell.
Publish-Subscribe Topic Mappings
Topic Mappings
Select
Add
Remove
Topic Space on local bus
Topic Space on foreign bus
The foreign topic space field must be supplied with a value.
It is not valid to specify duplicate topic space mappings when configuring publish-subscribe messaging.
Local bus details
The Virtual Queue Manager name must be supplied.
Virtual Queue Manager name
WebSphere MQ Server details
Service Integration Bus to WebSphere MQ Message Flow Details
WebSphere MQ to Service Integration Bus Message Flow Details
WebSphere MQ Receiver Channel name
WebSphere MQ Sender Channel name
Host name
Port
Enable Service Integration Bus to WebSphere MQ message flow
Enable WebSphere MQ to Service Integration Bus message flow
Secure the WebSphere MQ Receiver Channel
SIB Inbound User ID
MQ Link name
Configure Publish-Subscribe Messaging for this connection
Foreign Bus name
The Foreign Bus name must be supplied.
A Foreign Bus Connection cannot be created using the name supplied for the Foreign Bus attribute as it is not unique among Foreign Bus Connections on the local Service Integration Bus.
The MQ Link name must be supplied.
The MQ Link name supplied is already being used by an existing MQ Link on the same Service Integration Bus. Please supply a unique MQ Link name.
A WebSphere MQ Host name must be supplied if SIB-WebSphere MQ message flow is enabled.
A WebSphere MQ port must be supplied if SIB-WebSphere MQ message flow is enabled.
A WebSphere MQ Receiver Channel name must be supplied if SIB-WebSphere MQ message flow is enabled.
A WebSphere MQ Sender Channel name must be supplied if WebSphere MQ-SIB message flow is enabled.
In order to configure Publish-Subscribe messaging for this link, at least one destination of type 'Topic Space' must exist on the local bus.
It is not possible to configure publish-subscribe messaging for this connection if neither SIB-WebSphere MQ or WebSphere MQ-SIB message flow has been enabled.
The maximum length for the WebSphere MQ Receiver Channel name is 20 characters.
The maximum length for the WebSphere MQ Sender Channel name is 20 characters.
The WebSphere MQ port must be a value between 0 and 2147483647.
Publish-Subscribe Topic Mappings
You must select at least one topic mapping to perform this action.
WebSphere MQ Broker Queue Manager
WebSphere MQ Broker Stream Queue
WebSphere MQ Subscription Point
Direction
Service Integration Bus Topic Space
Topic Name
The WebSphere MQ Broker Queue Manager name must be supplied.
The WebSphere MQ Broker Stream Queue name must be supplied if the direction is set to either 'Bi-Directional' or 'To WebSphere MQ'.
The WebSphere MQ Subscription Point must be supplied.
The Topic name must be supplied.
It is not valid to specify duplicate topic mappings when configuring publish-subscribe messaging. Ensure the pairing of topic name and WebSphere MQ Broker Queue Manager does not already exist as a mapping.
Test Connection
An Indirect Foreign Bus Connection cannot be tested, as it may not be possible to reach the target bus.
Please select a single Foreign Bus Connection to test.
It is not possible to test the chosen Foreign Bus Connection due to an inconsistent configuration. It is possible that no link object exists on the Foreign Bus, or that the link has not yet been started.
The Foreign Bus Connection test was successful, indicating that the link is started and ready for message transfer.
The Foreign Bus Connection test was unsuccessful. Possible reasons for failure include the SIB Link not being started, or the connection not being defined on the opposite side of the link.
The Foreign Bus Connection test was unsuccessful. Possible reasons for failure include an unknown WebSphere MQ host, an incorrect Websphere MQ port number, or the WebSphere MQ Queue Manager not running.
Link transmitters
Messaging engine
Status
Current outbound messages
Messages sent
Time since last message sent
Delete all messages
All messages deleted successfully from link transmitter {0}
Delete all messages failed for link transmitter {0}, exception: {1}
Move all messages
All messages moved successfully from link transmitter {0}
Move all messages failed for link transmitter {0}, exception: {1}
Re-route all messages
All messages re-routed successfully from link transmitter {0}
Re-route all messages failed for link transmitter {0}, exception: {1}
Confirm deletion of all messages from the selected link transmitters; Yes or No.
Confirm move of all messages to the exception destination from the selected link transmitters; Yes or No.
Confirm re-routing of all messages from the selected link transmitters; Yes or No.
Started
Stopped
Unhealthy
Unknown
Link transmitter streams
Priority
Reliability
Number of messages queued
Number of messages sent
Status
Messages
View messages
Best effort nonpersistent
Express nonpersistent
Reliable nonpersistent
Reliable persistent
Assured persistent
Started
Stopped
Unhealthy
Unknown
Infinite
ms
ms
seconds
minutes
hours
days
ms
second
minute
hour
day
Authorizations Policy
Manage destination access roles
Destinations
Destination
Type
Manage foreign bus access roles
Foreign buses
Foreign bus
Manage Access Roles
The "{0}" button has not been implemented.
The link for "{0}" has not been implemented.
Role type assignments
User
Group
Member
Sender
Receiver
Browser
Creator
Alias
Foreign destination
Port
Queue
Temporary destination prefix
Topicspace
Webservice
Select
Name
Type
Add
Remove
Inherit from default
Link receivers
Foreign messaging engine
Status
Current inbound messages
Messages received
Time since last message received
Started
Stopped
Unhealthy
Unknown
Link receiver streams
Priority
Reliability
Current inbound messages
Messages received
Last delivered message sequence ID
Status
Messages
View messages
Started
Stopped
Unhealthy
Unknown
Best effort nonpersistent
Express nonpersistent
Reliable nonpersistent
Reliable persistent
Assured persistent
Link receiver stream messages
Position
Identifier
Previous sequence identifier
State
Target bus
Target destination
Time on queue
Link transmitter stream messages
Position
Identifier
State
Transaction ID
Target bus
Target destination
Approximate message length (bytes)
Move
Delete
All selected messages successfully deleted.
Some messages failed to be deleted.
Message {0} could not be deleted, exception: {1}.
All selected messages successfully moved to the exception destination.
Some messages failed to be moved to the exception destination.
Message {0} could not be move to the exception destination, exception: {1}.
Confirm deletion of the selected {0} messages; Yes or No.
Confirm move of the selected {0} messages to the exception destination; Yes or No.
Maximum messages displayed
Add a new bus member
Select server, cluster or WebSphere MQ server
Summary
Configure WebSphere MQ server bus member
Specify connection details
Select message store type
Select message store type
Configure a data store
Specify data store properties
Server
Cluster
WebSphere MQ server
Select message store type
Select the type of message store
Specify file store properties
Configure file store
File store
Data store
Only a data message store is applicable for the version of server selected.
Clone existing membership?
Clone existing membership?
Messaging engine policy assistance settings
Messaging engine policy assistance settings
Clone the existing membership of bus:
Create new membership definitions.
Unfortuately the clone function was not ready for Iteration 3. Look out for this exciting new feature in Iteration 4 !!!
Select
Policy name
Policy description
Is further configuration required?
No pattern
No
To successfully utilise this policy the selected server cluster will need at least one server defined on another node added.
High availability
Scalability
Scalability with high availability
Custom
Enable messaging engine policy assistance?
Configure the messaging engine policy
Configure the messaging engine policy
Configure messaging engines
Configure messaging engines
Messaging engine name
The messaging engine should failover to other servers in the server cluster.
The messaging engine should fail back to a preferred server if one is available (as specified in the preferred servers list).
The messaging engine should only run on the servers in the preferred servers list.
Preferred server list
Available servers
Preferred servers
Add
Remove
Up
Down
Select one or more items to work with.
Message store configuration
Use the same attributes to define a message store as used by messaging engine:
Define message store attributes specific to this messaging engine.
At least one preferred server must be provided if a messaging engine should only failover to servers in the preferred server list.
A messaging engine must be specified if previously defined message store settings are to be re-used.
Messaging engine "{0}" could not be removed because its persistent message store settings are used by messaging engine "{1}".
Messaging engine "{0}" was successfully removed.
At least one messaging engine must be configured for a valid server cluster bus member topology.
Only one messaging engine should be selected for editing.
Messaging engines
Name
Failover?
Fail back?
Preferred order of servers to run on
Only run on preferred servers?
Is the message store configured?
Adding server "{0}" as member of bus "{1}".
Adding WebSphere MQ server "{0}" as member of bus "{1}".
Adding server cluster "{0}" as member of bus "{1}".
The cluster is being configured using messaging engine assistance for policy: "{0}".
The following messaging engines have been configured:
File store settings:
Data store settings:
WebSphere MQ server connection settings:
A message store type has not been selected!
The message store for messaging engine "{0}" has not been configured.
No
Using default value
Create default
Not applicable
Disabled
Enabled ({0})
Messaging engine policy assistance
The following is a summary of your selections. To complete the changes, click Finish. If you want to change any selections, click Previous.
SIB Security Resource Wizard
Search for Users or Groups
Select Users or Groups
Select Role Types
Summary
Resource
Users
Groups
Search pattern
Maximum number of search results to display
Please supply a value for the Search pattern.
Please supply a value for the Maximum number of search results to display.
Please select at least one row from the table.
Name
Sender
Receiver
Browser
Creator
The following security roles will be applied:
SIB Security Resource Wizard

Expand
Collapse
Set
Not set
Inherited
Not applicable
This panel shows the role type assignments for the selected destinations.
Specify to search for groups
Specify to search for users
The maximum number of results to display
The search pattern used to find users and groups
The resource on which user and group access permissions are being set
Use this step to confirm the choices made.
Use this step to select the role types granted to the users and groups.
Use this step to select the users and groups to grant access for.
Use this step to search for the users and groups to give access to for the specified resource.
SIB Security Resource Wizard
Manage the assignment of destination role types to users and groups
Manage the assignment of foreign bus role types to users and groups
A bus destination is defined on a service integration bus, and is hosted by one or more locations within the bus. Applications can attach to the destination as producers, consumers, or both to exchange messages.
A foreign bus is another bus with which this bus can exchange messages.
The persistent store for messages and other state managed by the messaging engine.
The universal unique identifier assigned by the system to this data store for administrative purposes.
The JNDI name of the data source that the messaging engine uses to access the relational database management system (RDBMS) for the data store.
The name of the database schema used to contain the tables for the data store.
The name of the authentication alias used to authenticate the messaging engine to the data source.
Select this option if the messaging engine creates the database tables for the data store. Otherwise, the database administrator must create the database tables.
Number of database tables to use for storage of permanent objects.
Number of database tables to use for storage of temporary objects.


The thread pool used to allocate threads for the execution of mediation handlers.
Minimum size of thread pool.
Maximum size of thread pool.
Specifies the number of milliseconds of inactivity that should elapse before a thread is reclaimed.
Specifies whether the number of threads can increase beyond the maximum number configured for the thread pool.
A bus destination is defined on a service integration bus, and is hosted by one or more locations within the bus. Applications can attach to the destination as producers, consumers, or both to exchange messages.
The identifier by which this destination is known for administrative purposes.
The universal unique identifier assigned by the system to this destination for administrative purposes.
Whether this bus destination is for a queue, topic space, or some other type of destination.
The messaging engine policy assistance settings for the bus member. A warning icon will be displayed if messaging engine policy assistance is enabled and the current cluster configuration does not meet the selected policy requirements.
An optional description for the bus destination, for administrative purposes.
Select this option to enable producers to override the default reliability that is set on the destination.
The default priority assigned to messages sent to this destination when a priority has not been set by the producer.
The maximum number of failed attempts to process a message. After this number of failed attempts, the message is forwarded from the intended destination to its exception destination.
The maximum reliability of messages accepted by this destination.
The destination to which a message is forwarded by the system when it cannot be delivered to this destination.
Clear this option (setting it to false) to stop producers from being able to send messages to this destination.
Clear this option (setting it to false) to prevent consumers from being able to receive messages from this destination.
Select this option (setting it to true) to indicate that the destination is quiescing. In quiesce mode, new messages for the destination cannot be added to the bus, but any messages already in the bus can still be sent to, and processed by, the destination.
The name of a destination to be appended to any non-empty reverse routing path of messages sent to this destination.
The bus on which the reply destination exists.
The value to which a message's forward routing path will be set if the message contains no forward routing path, in the format, bus:name or :name.
Select the type of destination to be created.
Create a new destination on this bus.
Create a new queue for point-to-point messaging.
The WebSphere MQ queue that will be used to store messages for the mediation point being defined.  As defined in WebSphere MQ.
The level of reliability to apply when a nonpersistent WebSphere MQ message is received.
The level of reliability to apply when a persistent WebSphere MQ message is received.
If selected messages sent to WebSphere MQ will include an RFH2 header.  The RFH2 header stores messaging information that does not have a corresponding WebSphere MQ message header field.  Enable this if messages being sent to WebSphere MQ might reenter the bus.
Create a new topic space for publish/subscribe messaging.
Queue points and publication points for the messaging engine.
The system-generated name by which this message point is known.
The universal unique identifier assigned by the system to this message point for administrative purposes.
Whether the message point is a queue or topic space.
A threshold above which the messaging system will take action to limit the addition of more messages to this message point.
Clear this option (setting it to false) to stop messages from being put onto this message point.
Clear this option (setting it to false) to stop messages from being retrieved from this message point.
The UUID of the bus destination for which this is a message point.
The number of messages on the message point.
The internal run-time identifier assigned to this message point.
A queue for point-to-point messaging.
A mediation point is a location in a messaging engine at which messages are mediated. A mediation point is created when a mediation is associated with a bus destination.
A WebSphere MQ mediation point is a location from which a mediation takes messages.




The message point for a queue, for point-to-point messaging.
The message point for a WebSphere queue.
Messages queued on the queue point.
A topic space is a location for publish/subscribe messaging.
Whether or not authorization checks are required for access to topics.
The mediation points for the topic space. The locations in the messaging engine at which messages on the topic space are mediated.
The message point for a topic space, for publish/subscribe messaging.
Bus member (server or cluster) where the mediations for the destination run.
Whether the mediation point is started or stopped when the hosting messaging engine is first started. Until started, the mediation point is unavailable.
The run-time status of the mediation point.

Messages queued on the mediation point.
A service integration bus supports applications using message-based and service-oriented architectures. A bus is a group of interconnected servers and clusters that have been added as members of the bus. Applications connect to a bus at one of the messaging engines associated with its bus members.
Arbitrary name-value pairs of data, where the name is a property key and the value is a string value that can be used to set internal system configuration properties. Defining a new property enables you to configure a setting beyond that which is available in the administrative console.
A messaging engine manages bus resources and provides a connection point for applications.
Bus members are the servers, WebSphere MQ servers and clusters that have been added to the bus.
A bus destination is a logical address within a service integration bus.
Mediations define the information needed by a messaging engine to perform the mediation processing for associated destinations.
The name of the service integration bus. Choose a unique name.
The universal unique identifier assigned by the system to this bus for administrative purposes.
An optional description for the bus, for administrative purposes.
Select this option to inherit the secure administration setting of the cell. Deselect this option if you always wish to disable bus security.
The name of the authentication alias used to authorize communication between messaging engines on the bus.
The name of the authentication alias used to authorize mediations to access the bus.
The transport chain used for communication between messaging engines in this bus.
Whether messages on a deleted message point should be retained at a system exception destination or can be discarded.
Select this option to enable certain changes to the bus configuration to be applied without requiring the messaging engines to be restarted.
A threshold above which the messaging system will take action to limit the addition of more messages to a message point.
Provide the default settings for these attributes on a new messaging engine.
Bus members are the servers, WebSphere MQ servers and clusters that have been added to the bus.
The name of the bus member.
The node on which the bus member is configured.
Select a server.
Select a cluster.
Use the connection settings preset on this form in preference to those entered for the WebSphere MQ server.
An optional description for the bus member, for administrative purposes.
Add a server, cluster or a WebSphere MQ server as a new member of the bus.
Displays a list of mediation execution points assigned to this bus member.
A messaging engine is a component, running inside a server, that manages messaging resources for a bus member. Applications are connected to a messaging engine when accessing a service integration bus.
The persistent store for messages and other state managed by the messaging engine.
The thread pool for allocating mediation handler threads.
The locations (queue points or publication points) at which messages are held in a messaging engine.
A queue point is created on each messaging engine to which a point-to-point destination is assigned. It is used to hold messages pending delivery to receiving applications.
A publication point is created on each messaging engine in the bus when a publish/subscribe destination is created. The publication point on a messaging engine is used to hold messages published by applications connected to that messaging engine until they are delivered to subscribers.
A mediation point is created on each messaging engine to which the mediation of a mediated destination is assigned. It is used to hold messages pending delivery to the mediation.
Arbitrary name-value pairs of data, where the name is a property key and the value is a string value that can be used to set internal system configuration properties. Defining a new property enables you to configure a setting beyond that which is available in the administrative console.
The name of the messaging engine.
The universal unique identifier assigned by the system to this messaging engine for administrative purposes.
An optional description for the messaging engine, for administrative purposes.
The initial state determines whether the messaging engine is started automatically.
The maximum total number of messages that the messaging engine can place on its message points.
A list of names of target groups with which the messaging engine will register.
The name of the service integration bus on which the messaging engine is configured.
The universal unique identifier of the service integration bus on which the messaging engine is configured.
Whether the messaging engine is currently started or stopped.
Links between the messaging engine and WebSphere MQ networks. Each WebSphere MQ link connects the messaging engine as a queue manager to WebSphere MQ, thereby providing a bridge between the bus and a WebSphere MQ network.
A WebSphere MQ client link enables JMS client applications to connect, via this messaging engine, to the service integration bus, as though it were a WebSphere MQ queue manager.
The bus member associated with this messaging engine.
The receiver channel that receives messages from the gateway WebSphere MQ queue manager. The receiver channel communicates with a WebSphere MQ sender channel on the gateway queue manager, and converts MQ format messages to service integration bus messages.
The name of the receiver channel for the WebSphere MQ link, used to receive messages from WebSphere MQ onto the bus.
The acceptable reliability of message delivery for nonpersistent message flows from WebSphere MQ through this WebSphere MQ link, from Best effort to Reliable, in order of increasing reliability.
The acceptable reliability of message delivery for inbound persistent message flows from WebSphere MQ through this WebSphere MQ link, from Reliable to Assured, in order of increasing reliability.
Whether the receiver channel is started or stopped when the associated WebSphere MQ link is first started. Until started, the channel is unavailable.
The sender channel that sends messages to the gateway queue manager. The sender channel communicates with a WebSphere MQ receiver channel on the gateway queue manager, and converts service integration bus messages to MQ format messages.

The name of the sender channel for the WebSphere MQ link, used to send messages from the bus to WebSphere MQ.
The hostname or TCP/IP IP address for the gateway queue manager that is used to connect into the WebSphere MQ network.
The TCP/IP port number on which the gateway queue manager is listening for the WebSphere MQ link.
The type of channel chain used for communication with the foreign bus.
The time in seconds for which the sender channel waits for new messages to arrive on the transmission queue after sending a batch of messages. The channel disconnects after this interval, and must be restarted manually or by triggering.
The maximum number of times that the sender channel tries to restart after a communication or partner failure. If the count of remaining retries reaches zero, and the channel has not restarted, then the long retry mechanism is invoked.
The number of seconds between attempts by the sender channel to restart after a communication or partner failure.
The maximum number of times that the sender channel tries to restart after the short retry mechanism did not recover from a communication or partner failure. If the count of remaining retries reaches zero, and the channel has not restarted, then an error is logged and the channel is stopped.
The number of seconds between attempts by the sender channel to restart after the short retry mechanism did not recover from a communication or partner failure.
Whether the sender channel is started or stopped when the associated WebSphere MQ link is first started. Until started, the channel is unavailable.
The name of the virtual queue manager associated with the messaging engine, and by which the messaging engine is known to a remote WebSphere MQ network.
The TCP/IP IP address of the host on which the target queue manager runs.
The run-time status of the sender channel.
The current logical unit-of-work identifier for the message on the channel.
The current sequence number for the message on the channel.
Whether or not the message on the channel is in-doubt.
The last logical unit-of-work identifier for a message on the channel.
The last sequence number for a message on the channel.
The number of messages in the current batch on the channel.
The number of batches that have been sent on the channel.
The maximum number of messages that a batch can contain.
The number of messages that have been sent on the channel.
The number of message buffers sent.
The number of message buffers received.
The number of bytes sent.
The number of bytes received.
The time at which the channel was last started.
The date on which the channel was last started.
The time at which the last message was sent on the channel.
The date on which the last message was sent on the channel.
The negotiated time, in seconds, between heartbeat flows passed from the sender channel across the WebSphere MQ link when there are no messages on the transmission queue.
The remaining number of long retry attempts that can be used to start the sender channel. If the count of remaining retries reaches zero, and the channel has not restarted, then an error is logged and the channel is stopped.
The remaining number of short retry attempts that can be used to start the sender channel. If the count of remaining retries reaches zero, and the channel has not restarted, then the long retry mechanism is invoked.
The maximum message length, in bytes, that can be transmitted on the channel. This is compared with the value for the partner and the actual maximum used is the lower of the two values.
The class of service for nonpersistent messages on the sender channel.
Whether or not a manual stop request has been made for the sender channel.
The run-time status of message batches for the sender channel of the WebSphere MQ link. You can choose to commit or roll back each batch.
A link between the messaging engine and a WebSphere MQ network. The WebSphere MQ link connects the messaging engine as a queue manager to WebSphere MQ, thereby providing a bridge between the bus and a WebSphere MQ network.
The sender channel that sends messages to the gateway queue manager. The sender channel communicates with a WebSphere MQ receiver channel on the gateway queue manager, and converts service integration bus messages to MQ format messages.
The receiver channel that receives messages from the gateway queue manager. The receiver channel communicates with a WebSphere MQ sender channel on the gateway queue manager, and converts MQ format messages to service integration bus messages.
Profiles used to define the topic mappings and transactionality for publishing and receiving (by subscription) topics across the publish/subscribe bridge between WebSphere Application Server and a WebSphere MQ network.
The name of the WebSphere MQ link, used for administrative purposes.
The universal unique identifier assigned by the system to this WebSphere MQ link for administrative purposes.
An optional description for the WebSphere MQ link, for administrative purposes.
The foreign bus to which this link connects.
The name of the virtual queue manager associated with the messaging engine, and by which the messaging engine is known to a remote WebSphere MQ network.
The maximum number of messages that can be sent through a channel before taking a checkpoint.
The maximum message length, in bytes, that can be transmitted on any channel for the WebSphere MQ link. This is compared with the value for the partner and the actual maximum used is the lower of the two values.
The time, in seconds, between heartbeat flows passed from the sender channel across the WebSphere MQ link when there are no messages on the transmission queue.
The value at which message sequence numbers wrap to start again at 1.
The class of service for nonpersistent messages on channels of this WebSphere MQ link.
Whether or not this WebSphere MQ link can be adopted by another messaging engine if the original hosting messaging engine is restarted or adopted on another machine.
Whether the WebSphere MQ link is started or stopped when the hosting messaging engine is first started. Until started, the WebSphere MQ link is unavailable.
The run-time status of the WebSphere MQ link.
Wizard to create a new WebSphere MQ link.
The associated foreign bus for this WebSphere MQ link.
The current total number of messages queued on the link transmitters to this Service integration bus link
The total number of messages sent since the start of the messaging engine on the link transmitters to this Service integration bus link
The total number of messages received since the start of the messaging engine on the link receivers for this Service integration bus link
The WebSphere MQ link sender channel transmitter queue for messages being queued across to the WebSphere MQ network.
A WebSphere MQ client link presents the messaging engine, and thereby the bus, as a WebSphere MQ queue manager to which WebSphere MQ clients can attach. This enables WebSphere Application Server Version 5 JMS clients to use messaging resources on the bus.
The name of the WebSphere MQ client link.
The universal unique identifier assigned by the system to this WebSphere MQ client link for administrative purposes.
An optional description for the WebSphere MQ client link, for administrative purposes.
The name of the channel for the WebSphere MQ client link, used to flow messages between WebSphere MQ clients and the bus.
The queue manager name used to represent the bus as a WebSphere MQ queue manager to WebSphere MQ clients.
Whether or not this is the default queue manager for the WebSphere MQ clients.
The maximum message length, in bytes, that can be transmitted on the channel for the WebSphere MQ client link.
The time, in seconds, to wait before checking that a client requesting an operation is still active.
Whether the WebSphere MQ client link is started or stopped when the associated messaging engine is first started. Until started, the MQ client link is unavailable.
The run-time status of the WebSphere MQ client link.
Advanced configurable properties, such as message reliability and broker queue names, for the WebSphere MQ client link.
The client connections that exist on the WebSphere MQ client link.
The connection between a WebSphere MQ client and the bus.
The TCP/IP IP address of the WebSphere MQ client.
The run-time status of the WebSphere MQ client connection.
The runtime status of the WebSphere MQ client.
The number of messages sent on the WebSphere MQ client link over the connection to a specific client.
The number of messages received on the WebSphere MQ client link over the connection from a specific client.
The number of message buffers sent on the WebSphere MQ client link over the connection to a specific client.
The number of message buffers received on the WebSphere MQ client link over the connection from a specific client.
The number of bytes sent on the WebSphere MQ client link over the connection to a specific client.
The number of bytes received on the WebSphere MQ client link over the connection from a specific client.
The time at which the client connection channel was started.
The date on which the client connection channel was started.
The time at which the last message was sent on the client connection channel.
The date on which the last message was sent on the client connection channel.
The time at which the last message was received on the client connection channel.
The date on which the last message was sent on the client connection channel.
The time, in seconds, between heartbeat flows passed across the WebSphere MQ client link when there are no messages on the transmission queue for the client connection.
The maximum message length, in bytes, that can be transmitted on the WebSphere MQ client link. This is compared with the value for the partner client and the actual maximum used is the lower of the two values.
Whether or not a manual stop request has been made for the WebSphere MQ client link connection.
The local address of the WebSphere MQ client connection.
The number of API calls serviced for the WebSphere MQ client connection.
Advanced configurable properties, such as message reliability and broker queue names, for the WebSphere MQ client link.
The acceptable reliability of message delivery for inbound persistent message flows from WebSphere MQ through this WebSphere MQ client link, from Reliable to Assured, in order of increasing reliability.
The acceptable reliability of message delivery for inbound nonpersistent message flows from WebSphere MQ through this WebSphere MQ link, from Reliable to Assured, in order of increasing reliability.
The name of the message broker control queue to which all command messages (except publications and requests to delete publications) are sent.
The name of the message broker publication queue to which all publication messages for the default stream are sent.
The name of the message broker subscription queue from which nondurable subscription messages are retrieved.
The name of the message broker durable subscription queue from which durable subscription messages are retrieved.
The name of the message broker connection consumer subscription queue from which nondurable subscription messages are retrieved for a connection consumer request.
The name of the message broker connection consumer durable subscription queue from which nondurable subscription messages are retrieved for a connection consumer request.
The name of the default topic space for the WebSphere MQ client link.
The saved status of message batches for the sender channel saved for transmission to WebSphere MQ. You can choose to commit or rollback each batch.
The name of the queue manager for the WebSphere MQ link sender channel.
The name of the channel used for the WebSphere MQ link sender channel.
Whether or not the saved batch is in doubt.
The current logical unit-of-work identifier for the saved batch.
The current sequence number for the saved batch.
The last logical unit-of-work identifier for the saved batch.
The last sequence number for the saved batch.
The runtime status of the receiver channel.
The connections that exist on the receiver channel of the WebSphere MQ link.
The runtime status of message batches for the receiver channel of the WebSphere MQ link.
The runtime status of message batches for the receiver channel of the WebSphere MQ link.
A connection that exists on the receiver channel of the WebSphere MQ link.
The name of the queue manager for the WebSphere MQ link receiver channel connection.
The IP address of the queue manager for the WebSphere MQ link receiver channel connection.
The runtime status of the WebSphere MQ link receiver channel connection.
The current logical unit-of-work identifier of the WebSphere MQ link receiver channel connection.
The current sequence number for the message on the channel.
The last logical unit-of-work identifier for a message on the channel.
The last sequence number for a message on the channel.
The number of messages in the current batch on the channel.
The number of batches received on the channel.
The maximum number of messages that a batch can contain.
The number of messages received on the channel.
The number of buffers sent on the channel.
The number of buffers received on the channel.
The number of bytes sent on the channel.
The number of bytes received on the channel.
The time at which the channel was last started.
The date on which the channel was last started.
The time at which the last message was received on the receiver channel connection.
The date on which the last message was received on the receiver channel connection.
The time, in seconds, between heartbeat flows passed from the receiver channel across the WebSphere MQ link when there are no messages on the transmission queue.
The maximum message length, in bytes, that can be transmitted on the channel. This is compared with the value for the partner and the actual maximum used is the lower of the two values.
The class of service for nonpersistent messages on the receiver channel.
Whether or not a manual stop request has been made for the receiver channel.
Profiles used to define the topic mappings and transactionality for publishing and receiving (by subscription) topics across the publish/subscribe bridge between WebSphere Application Server and a message broker in a WebSphere MQ network.
Topic mappings for publishing and receiving (by subscription) messages across the publish/subscribe bridge between WebSphere Application Server and a message broker in a WebSphere MQ network.
The transactional characteristics for publishing and receiving (by subscription) messages across the publish/subscribe bridge between WebSphere Application Server and a message broker in a WebSphere MQ network.
The name of the publish/subscribe broker profile.
An optional description for the publish/subscribe broker profile, for administrative purposes.
The name of the queue manager for the WebSphere MQ broker.
The mapping between a topic on the service integration bus and a stream queue and subscription point provided by a WebSphere MQ broker.
The transactional characteristics for publishing and receiving (by subscription) messages across the publish/subscribe bridge between WebSphere Application Server and a WebSphere MQ broker.
The name of the topic on the service integration bus.  The name must be the same as the topic name on the message broker in a WebSphere MQ network.
The name of the topic space that contains the topic.
Whether the mapping is for publishing message flows in both directions, or only to, or only from, WebSphere MQ.
The name of the stream queue at the message broker in a WebSphere MQ network.
The name of the WebSphere MQ broker subscription point that the topic consumes messages from.
The list of current broker subscriptions for this broker profile.
The current number of broker subscriptions for this broker profile.
The list of current broker subscriptions for this broker profile.
The topic name for this subscription.
The topic space for this subscription.
Whether the subscription is for message flows to or from WebSphere MQ.
The name of the WebSphere MQ broker stream queue that the topic publishes messages to.
The name of the WebSphere MQ broker subscription point that the topic consumes messages from.
The count of messages for this subscription.
The current status of this subscription.
The default transactional characteristics for publishing and receiving (by subscription) messages across the publish/subscribe bridge between WebSphere Application Server and a message broker in a WebSphere MQ network.
The type of messages that are received and then re-published by the publish/subscribe bridge within a transaction.
The maximum number of messages that can be sent across the publish/subscribe bridge before committing the transaction. If fewer messages are available, the commit action occurs when all messages have been received and re-published.
The transactional characteristics for publishing and receiving (by subscription) messages for the topic mapping across the publish/subscribe bridge.
Whether or not the messages for this topic are persistent, or inherit the type value defined for the publish/subscribe bridge.
The maximum number of messages that can be sent for this topic across the publish/subscribe bridge before taking a checkpoint.
A mediation that is associated with a bus destination to apply processing to messages on that destination.
Whether or not a global transaction is started for each message processed.
Select this option (setting it to true) to apply the mediation to multiple messages concurrently. Message ordering is not preserved. The default option is false.
Controls which messages are sent to the mediation. If a message matches the rule defined by the selector text string, then the mediation is applied to the message.
Controls which messages have the mediation applied to them. If the topic of a message matches the rule specified by the discriminator text string, then the mediation is applied to the message. If both the selector and discriminator are specified, the message must match both rules for the mediation to be applied to the message.
The universal unique identifier assigned by the system to this mediation for administrative purposes.
An optional description for the mediation, for administrative purposes.
The name by which this mediation is known for administrative purposes.
The name of the handler list that was defined when the mediation was deployed.
The active subscriptions for the topic space.
The name by which the active subscription is known for administrative purposes.

The name of the topic space that this subscription is for.

The text string that must be present in a message for the mediation to process the message.
The name of the topic that this subscription is for.
The user name by which the subscription is authenticated.
Messages being handled by this subscription.
A foreign bus is another bus with which this bus can exchange messages.
Properties to be applied when applications use destinations on this foreign bus when there is no explicit foreign destination definition.
The default priority assigned to messages sent to this destination when a priority has not been set by the producer.
The maximum reliability of messages accepted by this destination.
Clear this option (setting it to false) to stop producers from being able to send messages to destinations on this foreign bus.
Select this option to enable producers to override the default reliability that is set on the destination.
Context information passed to the mediation.
A foreign bus is another bus with which this bus can exchange messages.
The name of the bus with which this bus will exchange messages. This name must match exactly the name of the existing service integration bus that is defined as the foreign bus.
The universal unique identifier assigned by the system to this foreign bus for administrative purposes.
An optional description for the foreign bus, for administrative purposes.
Clear this option (setting it to false) to stop producers from being able to send messages to this foreign bus.
Properties to be applied when applications use destinations on this foreign bus when there is no explicit foreign destination definition.
Select this link to define the routing definition for this foreign bus.
The associated service integration bus links for this foreign bus.
The associated WebSphere MQ links for this foreign bus.
Create the routing definition for the foreign bus, to define the routing type and properties.
Routing type defines the type of link used to make the connection to the foreign bus. Use a service integration bus link for a connection to a foreign service integration bus, a WebSphere MQ link for a connection to a foreign WebSphere MQ network, or an indirect routing if the connection to the foreign bus is via another foreign bus.
The name by which the routing definition is known.
The user name used to authenticate inbound message flows from the foreign bus.
The user name used to authenticate outbound message flows to the foreign bus.
The name of the intermediate foreign bus in cases where the foreign bus you are configuring is not directly connected to the local bus.
The name by which the routing definition is known.
The universal unique identifier assigned by the system to the routing definition (virtual link) for administrative purposes.
The user ID applied to messages arriving from the foreign bus and used to authorize their access to destinations.
The user ID applied to messages sent to the foreign bus.
The routing properties for a service integration bus link to a foreign service integration bus.

The mapping between topic spaces in the local bus and topic spaces in the foreign bus.
The routing properties for a link to a foreign bus that represents a WebSphere MQ network.

The routing definition for the next service integration bus in a sequence of connected buses.
The name of the next service integration bus in the sequence of connected buses.



The mapping between topic spaces in the local bus and topic spaces in the foreign bus.
An optional description for the topic space mapping, for administrative purposes.
The mapping between topic spaces in the local bus and topic spaces in the foreign bus.
The mapping between a topic space in the local bus and a topic space in the foreign bus.
The name of the topic space on this (local) bus that is mapped to the remote topic space on the foreign bus.
The name of the topic space on the foreign bus that is mapped to the local topic space.
The current total number of messages queued on the link transmitters to this Service integration bus link
The total number of messages sent since the start of the messaging engine on the link transmitters to this Service integration bus link
The current total number of messages queued pending receit on the link receivers for this Service integration bus link
The total number of messages received since the start of the messaging engine on the link receivers for this Service integration bus link
Links between this messaging engine and messaging engines in foreign service integration buses.
The name of the service integration bus link. In order to work, the name must be the same as the name of the corresponding service integration bus link configured on the target foreign bus.
The universal unique identifier assigned by the system to the service integration bus link for administrative purposes.
An optional description for the service integration bus link, for administrative purposes.
The foreign bus to which this link connects.
The messaging engine on the foreign bus to which this link connects.
The type of transport chain used for communication with the foreign bus.
The comma-separated list of endpoints used to connect to a bootstrap server.
The name of the authentication alias, used to autnenticate access to the foreign bus.
Whether the link is started automatically when the messaging engine is started.
The run-time status of the service integration bus link.
Whether the service integration bus link is currently inactive, active, or its activity is unknown.
The associated foreign bus connection for this service integration bus link.
A communications link between this messaging engine and a messaging engine in a foreign service integration bus.
Context information used to enable correct processing of messages. This information adds to the context information derived from processing the message header.
The name of this context property. The mediation will retrieve the context property using this name.
The type of the context property, for example, Boolean, Byte, or Character.
The value of the context property.
Options that override the target destination.
An alias destination makes a destination available by another name and, optionally, overrides the parameters of the destination.
An alias destination makes a destination available by another name and, optionally, overrides the parameters of the destination.
An optional description for the alias destination, for administrative purposes.
The default priority assigned to messages sent to this destination when a priority has not been set by the producer.
Clear this option (setting it to false) to prevent consumers from being able to receive messages from this alias destination.
Clear this option (setting it to false) to stop producers from being able to send messages to this alias destination.
Select this option to enable producers to override the default reliability that is set on the destination.
The maximum reliability of messages accepted by this destination.
The name of the bus on which the destination for which this is an alias exists.
The name of the destination for which this is an alias.
The name of the bus on which this destination is known to applications.
The name of the destination as known to applications.
Indicates whether the authorization check is performed on the alias or the target destination.
The name by which this foreign destination is known for administrative purposes.
Create a new foreign destination (a destination on a foreign bus).
An optional description for the foreign destination, for administrative purposes.
The default priority assigned to messages sent to this destination when a priority has not been set by the producer.
Clear this option (setting it to false) to stop producers from being able to send messages to this destination.
Select this option to enable producers to override the default reliability that is set on the destination.
The maximum reliability of messages accepted by this destination.
The name of the foreign bus on which this destination is defined.
The identifier by which this destination is known for administrative purposes.
The messages on the message point.
The position of the message on the message point list.
The contents of the message body.
The identifier of the message.
Whether this message is currently locked or unlocked.
The local transaction identifier of the transaction that this message is currently part of.
The type of the message.
The approximate length of the message.
The time stamp of the message.
The time the message has been waiting to be consumed.
The time that the message arrived on the current messaging engine.
The number of times that the message has been redelivered.
The security user ID.
The producer type.
The timestamp at which the message was put to the exception destination.
The reason the message was put to the exception destination.
The API message ID.
The correlation ID.
The message ID.
The correlation ID.
The user ID.
The Format of the message.
The JMS delivery mode.
The JMS expiration.
The JMS destination.
The JMS reply to destination.
The JMS redelivered flag.
The JMS type field.
The JMSX delivery count.
The JMSX application ID.
The bus discriminator.
The bus priority.
The bus reliability.
The time to live of the message.
The reply discriminator value of the bus.
The reply priority value of the bus.
The reply reliability value of the bus.
The reply time to live value of the bus.
The short identifier of the bus.
The bus system message ID.
The approximate total length, in bytes, of the message including its header.
The amount in bytes of the message body data to be displayed.
Apply a mediation to a destination, to modify the destination handling of messages.
Transport channel service chains that lead to the messaging engine WebSphere MQ link.
Transport channel service chains that lead to the messaging engine.
A channel which can be used in combination with the TCP Channel - or other channels that support the same application interface to accept inbound connections to a WebSphere system integration bus messaging engine.
The amount of idle time, in seconds, before the channel attempts to solicit a response from its peer to check that the peer is still active. The sum of this value and the heartbeat timeout value determines the maximum amount of time that it can take to discover that some types of network failure have occurred.
The amount of time, in seconds, to wait for a response from a peer after deciding to check that the peer is still alive.
A channel that can be used in combination with the TCP Channel or other channels within the confines of WebSphere MQ support to facilitate communications between a WebSphere system integration bus and a WebSphere MQ client or queue manager.
Default system exception destination.
No exception destination is configured.
Specify a named destination.
The name of the mediation that mediates this destination.
The reliability assigned to a message produced to this destination when an explicit reliability has not been set by the producer.
The reliability assigned to a message produced to this destination when an explicit reliability has not been set by the producer.
The reliability assigned to a message produced to this destination when an explicit reliability has not been set by the producer.
The reliability assigned to a message produced to this destination when an explicit reliability has not been set by the producer.
Select this option to allow only one consumer to attach to each message point. If this option is not selected multiple consumers will be allowed to attach and receive messages from each message point.
Enabling this option will maintain the strict ordering of messages for this destination.
The remote queue points that are producing/consuming messages to/from queue points on remote messaging engines.
The remote publication points that are producing messages for publication points on remote messaging engines.
The remote queue points that are producing/consuming messages to/from queue points on remote messaging engines.
The remote queue point identifier.
The remote messaging engine where this queue point is localized.
The current number of outbound messages queued to the queue point.
The total number of messages sent to the queue point since the messaging engine started.
The current number of active message retrieval requests sent to the queue point from this remote queue point.
The total number of completed message retrieval requests sent to the queue point from this remote queue point since the messaging engine started.
The total number of active and completed message retrieval requests sent to the queue point from this remote queue point since the messaging engine started.
A snapshot of the current message retrieval requests from the message point.
The request identifier.
The time at which the message retrieval request will timeout.
The retrieval request message selection critieria.
The state of the message retrieval request.
The outbound message streams from this remote message point to the remote localized message point.
The stream priority.
The stream reliability.
The current number of messages on the stream.
The status of the stream.
View the messages on the selected stream.
A snapshot of the current outbound messages for the message point.
The message sequence identifier.
The API message identifier.
The time the message was produced.
The state of the queued message.
The remote mediation points that are producing messages for mediation points on remote messaging engines.
The remote mediation points that are producing messages to mediation points on remote messaging engines.
The remote mediation point identifier.
The remote messaging engine where this mediation point is localized.
The current number of outbound messages queued to the mediation point.
The total number of messages sent to the mediation point since the messaging engine started.
The remote publication points that are producing messages to publication points on remote messaging engines.
The remote publication point identifier.
The remote messaging engine where this publication point is localized.
The current number of outbound messages queued to the publication point.
The total number of messages sent to the publication point since the messaging engine started.
The messages queued outbound to the publication point on the remote messaging engine.
The topics that have been subscribed to from this remote messaging engine.
The subscriptions that have been made from this messaging engine to subscription homes on remote messaging engines.
The topics that have been subscribed to from this remote messaging engine.
The subscription that has been made from this messaging engine to a subscription home on a remote messaging engine.
The name of the remote subscription.
The current number of active message retrieval requests sent to the publication point from this remote subscription point.
The total number of completed message retrieval requests sent to the publication point from this remote subscription point since the messaging engine started.
The total number of active and completed message retrieval requests sent to the publication point from this remote subscription point since the messaging engine started.
The remote messaging engines that have remote producers or consumers connected to this queue point.
The remote messaging engines that have remote producers or consumers connected to this queue point.
The messaging engine where the remote queue point is located.
The current number of queued inbound messages for the queue point.
The total number of messages received on this queue point since the messaging engine started.
The current number of active message retrieval requests from the remote queue point.
The total number of completed message retrieval requests from the remote queue point since the messaging engine started.
The total number of active and completed message retrieval from the remote queue point since the messaging engine started.
The inbound message streams from the remote queue point.
The message retrieval requests from the remote queue point.
The remote messaging engines that have remote producers connected to this publication point.
The remote messaging engines that have remote producers connected to this publication point.
The messaging engine where the remote publication point is located.
The current number of queued inbound messages for the publication point.
The total number of messages received on this publication point since the messaging engine started.
The inbound message streams from the remote publication point.
The remote messaging engines that have remote consumers connected to this subscription point.
The remote messaging engines that have remote consumers connected to this subscription point.
The messaging engine where the remote subscription point is located.
The current number of active message retrieval requests from the remote subscription point.
The total number of completed message retrieval requests from the remote subscription point since the messaging engine started.
The total number of active and completed message retrieval from the remote subscription point since the messaging engine started.
The message retrieval requests from the remote subscription point.
The inbound message streams from the remote queue point.
The stream priority.
The stream reliability.
The current number of messages on the stream.
The sequence ID of the last message delivered.
The status of the stream.
View the messages on the stream.
A snapshot of the current inbound messages from the remote message point.
The sequence identifier of the message.
The sequence identifier of the message delivered before this message.
The API message identifier.
A snapshot of the current message retrieval requests from the remote message point.
The request identifier.
The time at which the message retrieval request will timeout.
The retrieval request message selection critieria.
The state of the message retrieval request.
A WebSphere MQ server represents either a WebSphere MQ v6 for z/OS queue manager or a WebSphere MQ v6 for z/OS queue sharing group. It is used by Service Integration Bus messaging to define properties used for connecting to WebSphere MQ.
The administrative name of the WebSphere MQ Server.
The universal unique identifier assigned by the system to this WebSphere MQ server for administrative purposes.
An optional description for the WebSphere MQ server, for administrative purposes.
A server can be either a queue manager or queue sharing group.  Select the appropriate type for the server you want to establish a connection to.
When selected, bindings transport mode will be used in preference to client transport mode when establishing connections to the WebSphere MQ server.  Otherwise client transport mode will always be used.
WebSphere MQ server host defined by either its symbolic host name or an IP address.
This is the port that will be used when attempting to establish client transport mode connections to WebSphere MQ.
The WebSphere MQ server connection channel, as defined in WebSphere MQ.
The transport chain used to establish an outbound network connection to the WebSphere MQ server.
If selected user identifiers received as part of WebSphere MQ messages will be used for security purposes within the bus.
WebSphere MQ server authentication alias name used when exchanging messages with WebSphere MQ.
WebSphere MQ server authentication alias used for WebSphere MQ resource discovery.
The name of the WebSphere MQ queue manager or queue sharing group, as defined in WebSphere MQ.
When selected this enables the discovery of WebSphere MQ queue names to assist the administrator.
WebSphere MQ queue name used by the system to obtain messages used in the resource discovery process.
Displays a list of mediation execution points assigned to this destination.
Displays a list of queue points used to hold messages pending delivery to receiving applications.
Displays a list of mediation points created when a mediation is associated with a bus destination.
Displays a list of WebSphere MQ mediation points assigned to this WebSphere MQ server bus member.
Choose the properties to override when adding this WebSphere MQ server to the bus.
Displays a list of WebSphere MQ queue points that have been defined for this destination.
Displays a list of WebSphere MQ mediation points that have been defined for this destination.
A WebSphere MQ server bus member is used as a bus member for assigning queue points and mediation points to WebSphere MQ queues.
Select a WebSphere MQ server.
The administrative name of the WebSphere MQ server bus member.
The universal unique identifier assigned by the system to this WebSphere MQ server for administrative purposes.
When selected the bus specific properties override the WebSphere MQ server connection properties.  Deselecting this option and applying the change will reset the connection settings to the WebSphere MQ server default values.
The override value for the WebSphere MQ server's host. This can either be a symbolic host name or an IP address.
The override value for the WebSphere MQ server's port.  This will be used when attempting to establish client transport mode connections to WebSphere MQ.
The override value for the WebSphere MQ server's transport chain name.  This is the transport chain used to establish an outbound network connection to the WebSphere MQ server.
The override value for the WebSphere MQ server's channel.  This value is the WebSphere MQ server connection channel, as defined in WebSphere MQ
The override value for the WebSphere MQ server's authentication alias name.  This is the authentication alias name used for exchanging messages with WebSphere MQ.
The override value for the WebSphere MQ server's trust user identifier setting.  If selected user identifiers received as part of WebSphere MQ messages will be used for security purposes within the bus.
Displays a list of WebSphere MQ queue points assigned to this WebSphere MQ server bus member.
The WebSphere MQ server which was used to create this bus member.
A WebSphere MQ queue point is used when sending messages to and receiving messages from a WebSphere MQ queue.
The list of users and groups in the bus connector role.
Users in the bus connector role are able to connect to the bus to perform messaging operations. Users can have this role either by specifically having that role, or because they are in a group with that role.
The name of the user or group in the bus connector role.
The type of the user or group in the bus connector role.
The name of the user to add to the bus connector role.
The name of the group to add to the bus connector role.
The bus connector role. Users in this role are able to connect to the bus to perform messaging operations.
The persistent store for messages and other state managed by the messaging engine.
Use a file store with this bus member.
A file store is only supported on servers whose WebSphere Application Server version is at least 6.1.
Use a data store with this bus member.
The messaging engine will create and use the default data source.
Size in megabytes of the log file.
When selected the same settings for the permanent store will be applied to the temporary store.
Name of the log files directory.
Name of the default log files directory.
Set log properties.
Set store properties.
The minimum number of megabytes reserved by each of the permanent store files. The permanent store files are never smaller than the log file.
The maximum size in megabytes for the permanent store files.
Indicates whether the permanent store files are unlimited in size.
Name of the permanent store files directory.
Name of the default permanent store files directory.
The minimum number of megabytes reserved by each of the temporary store files. The temporary store files are never smaller than the log file.
The maximum size in megabytes for the temporary store files.
Indicates whether the temporary store files are unlimited in size.
Name of the temporary store files directory.
Name of the default temporary store files directory.
File store.
Create a new data store for use with this bus member.
Supply the jndi name for an existing data store.
The universal unique identifier assigned by the system to this data store for administrative purposes.
Add a new messaging engine to a cluster.
Create a user or group in the bus connector role.
Add a group to the bus connector role.  This group can be a defined group or a selection of all authenticated users, all servers or everyone.
Add a user to the bus connector role by entering the name in the User name box.
Add a specific group from the configured user account repository to the bus connector role by entering the group name in the Group name box.
Select this to allow servers to connect to the bus.
Select this to allow all authenticated users to connect to the bus.
Select this to allow everyone, authenticated and unauthenticated users, to connect to the bus.
Configure the security settings for your service integration bus.
Link to configure WebSphere global security settings.
Select the type of allowed permitted transports.
Security of your service integration bus can be managed from here.
The list of permitted transports.
The name of the permitted transport.
A permitted transport is a transport mechanism that this bus will allow remote clients to use.
Select the transport name from the list of chain names.
Add a transport to the list of permitted transports.
Create a new Service Integration Bus.
Enter the name for your new bus.
Select whether you want to enable bus security.
The type of message store used. Either file store or data store. Once the messaging engine has been created this cannot be changed, only configured.
The properties for the message store in use by this messaging engine as determined by the message store type field.
Assign attributes to a WebSphere MQ mediation point.  A WebSphere MQ mediation point defines a WebSphere MQ queue which is used to hold messages before they are mediated.
Assign a bus member where the processing of messages, for this mediation, will take place.
The list of bus members where the processing of messages, for this mediation, will take place.
When a destination is assigned to WebSphere MQ an external application can be chosen to mediate the WebSphere MQ destination.
Support for maintaining the strict ordering of messages is only supported where the destination message points are all on WebSphere Application Server version 6.1 or later.
The foreign bus connection link transmitters for the queueing of messages on the local messaging engine for transmission across the link on the remote gateway messaging engine.
The name of the topic to be used in the publish-subscribe mapping.
The name of the topic space on the Service Integration Bus.
The direction of the publish-subscribe mapping.
The name of the WebSphere MQ broker subscription point that the topic consumes messages from.
The name of the stream queue at the message broker in a WebSphere MQ network.
The name of the queue manager for the WebSphere MQ broker.
The user ID applied to messages arriving from the foreign bus and used to authorize their access to destinations.
The name of the WebSphere MQ sender channel to send messages to. This value will be used as the name of the MQ Link receiver channel.
Specify whether to enable WebSphere MQ to Service Integration Bus message flow.
Specify whether to secure the WebSphere MQ receiver channel.
The WebSphere MQ port to be used in the connection.
The name of WebSphere MQ host to connect to.
The name of the WebSphere MQ receiver channel to send messages to. This value will be used as the name of the MQ Link sender channel.
Specify whether to enable Service Integration Bus to WebSphere MQ message flow.
Specify whether to configure Publish-Subscribe messaging on this MQ Link.
The name of the MQ Link to be created.
The name of the foreign bus definition to be created.
Specify to use the target queue manager name as the foreign bus name. If not selected, the Foreign Bus Name field must be supplied.
Specify to supply a different name for the foreign bus, and not use the queue manager name.
The name of the gateway queue manager in WebSphere MQ, which will by default act as the name of the foreign bus definition to be created.
The name of the virtual queue manager associated with the messaging engine, and by which the messaging engine is known to the remote WMQ network.
The name of the local messaging engine that will host the MQ link in the local bus.
The name of the topic space on the foreign bus that is mapped to the local topic space.
The name of the topic space on this (local) bus that is mapped to the remote topic space on the foreign bus.
Select this option when entering configuration details for a foreign bus in a remote cell.
Select this option when entering configuration details for a foreign bus in the local cell.
The name of the authentication alias, used to authenticate access to the foreign bus.
The type of transport chain used for communication with the foreign bus.
Specify whether to secure the connection being created.
A comma-separated list of endpoint triplets, with the syntax hostName: portNumber: chainName, used to connect to a bootstrap server. For example Merlin: 7276: BootstrapBasicMessaging,Gandalf: 5557: BootstrapSecureMessaging. This field is only required when configuring a foreign bus in a remote cell.
Specify whether to configure Publish-Subscribe messaging as part of this Service Integration bus link.
The name of the Service Integration bus link to be created as part of this connection.
The messaging engine on the foreign bus to which this link connects.
The name of the bus to create a connection to. This name must match exactly the name of the existing Service Integration bus that is defined as the foreign bus.
The user ID applied to messages arriving from the foreign bus and used to authorize their access to destinations.
The name of the local messaging engine that will host the Service Integration Bus link in the local bus.
The name of the existing, directly connected foreign bus to be used as the next-hop bus in this indirect connection.
The name of the target bus to indirectly connect to.
Specify the optional publish-subscribe details
Specify the WebSphere MQ details
Specify the local bus details
Foreign Bus Connection Direct to WebSphere MQ
Specify the optional publish-subscribe details
Specify the foreign bus details
Specify the local bus details
Foreign Bus Connection Direct to SIB
Specify the type of the foreign bus to connect to
Foreign Bus Connection Direct
Specify the target and next-hop bus connection details
Supply the bus connection details
A summary of the actions that will take place upon wizard completion
Select the type of bus connection
Foreign Bus Connection
A foreign bus connection allows communication with another bus. The foreign bus can represent another Service Integration Bus, an instance of WebSphere MQ, or an indirect connection to another foreign bus.
The transmission queues for applications producing messages to an inter-bus link.
The outbound message streams, by quality of service, for the link transmitter.
The inbound receiver queues for messaging applications on the foreign bus that are producing messages to this bus.
The inbound message streams from messaging applications on the foreign bus for the link receiver.
The current messages on the link receiver stream.
The outbound messages to the foreign bus link, on the link transmitter stream.
Limit the collection size to this maximum number.
The collection table shows the messaging engines that will be created when the server cluster is added as a bus member. At least one messaging engine must be created and message store settings must be configured for each messaging engine.
Configure the messaging engines for the to be created when the server cluster is added as a bus member.
Configure the policy for the messaging engine. The settings provided will be used to create a Core Group Policy for the messaging engine.
Configure the policy for the messaging engine.
Enabling messaging engine policy assistance enables a pre-defined or custom policy to be applied to the selected server cluster. Tooling will be enabled to assist in maintaining the policy if the server cluster changes in size. Restrictions will be placed on the changes that can be made to associated core group policies.
Select a pre-defined messaging engine policy to apply to the selected cluster when it is added as a bus member.
The selected cluster is already a member of another service integration bus. Select whether the existing membership settings should be cloned (so that the cluster is associated in the same way to the current bus as it is to that of the bus that the membership is cloned from) or if new membership settings should ne defined.
Should the selected clusters existing membership of another bus be used as the template for the membership of the current bus?
Specify the properties for the file store
Provide the properties for the file store
Choose the type of message store for the persistence of message state
Choose the type of message store for the persistence of message state
Specify the properties for the data store
Configure the properties for a data store
Choose the type of message store for the persistence of message state
Select the type of message store to use
Use the connection settings for the selected WebSphere MQ server or override them with new values.
Configure the connection settings for the WebSphere MQ server to be added as a member of the bus.
The actions that will be performed when selecting "Finish".
Choose the server, cluster or WebSphere MQ server to add to the bus
Add a server, cluster or a WebSphere MQ server as a new member of the bus.
No pattern will be applied to the server cluster. A single messaging engine will be created that can only be hosted on one server in the cluster.
The high availability pattern ensures that a single messaging engine is always available.
Selecting the scalability pattern will create a messaging engine for every server in the cluster. Each messaging engine will only ever be hosted by on the server it is assigned to.
Selecting the scalability with high availability pattern will create a messaging engine for every server in the cluster. Each messaging engine will be able to be hosted by one other server (as well as the one it is assigned to). Each server in the cluster will be able to host one other messaging engine.
Selecting the custom pattern will allow a unique pattern to be created for the server cluster. This is only recommended for advanced users.
An ordered list of servers that it would be preferable for the messaging engine to run on. The messaging engine will run on the first available server defined in the list.
Each messaging engine must have its own unique message store. However several message stores can be created within the same database or filesystem. Select either to use the same message store settings as a previously configured messaging engine or to configure an entirely new message store.

SIB service
Configuration reload enabled

The service that provides service integration functions.
Select this option to enable the dynamic reloading of the SIB configuration files for this server.

SI bus
Web services
URL
UDDI
Outbound Services
Ports
Custom Properties
Name
Description
Service destination name
WSDL location type
WSDL location
WSDL UDDI registry
WSDL service namespace
WSDL service name
Default port name
Port selection mediation
Bus member
Enable operation level security
New
View
Outbound Ports
Outbound service name
Reload WSDL
Service
New outbound service
Locate the target service WSDL
Select the location of the WSDL that describes the service provider
Select service
Select a service that is defined in the WSDL
Please select a service from the available options
The service you selected has no ports defined, please select a different service
Select Ports
Select the ports that are to be enabled for this service
Please select at least one port
Select
Port name
Binding
Port address
Name the outbound service and destinations
Optionally rename the outbound service and the service and port destinations from the default generated names if required, provide the name of the port selection mediation, if any, and identify the default port.
Default port
Port name
Port destination name
Select assigned bus members for port destinations and the port selection mediation, if required.
Each port destination needs to be assigned to a bus member
If you supplied a port selection mediation, this also needs to be assigned to a bus member
Please supply a service destination name.
Please supply a port destination name for every available port.
Please supply an outbound service name.
A service destination with the specified name already exists.
A port destination with the name {0} already exists.
The port destination {0} is the same as the service destination name.
You supplied a Port Selection Mediation, but have not specified a bus member to which it is assigned.
Port Name
Bus member
There was an inconsistent number of ports and related objects
{0}
Outbound Ports
Custom Properties
Name
Description
Port destination name
Port destination point
Binding namespace
Endpoint address
JAX-RPC handler list
Security request binding
Security response binding
Security configuration
Default port
New
Authenticating proxy host name
Authenticating proxy port number
Authenticating proxy user ID
Authenticating proxy password
Authenticating proxy Authorization Alias
Inbound Services
Ports
UDDI Publication
Publish WSDL files to ZIP file
Name
Description
Service destination name
Template WSDL location type
Template WSDL location
Template WSDL UDDI registry
Template WSDL service namespace
Template WSDL service name
Enable operation level security
Publish to UDDI
Unpublish from UDDI
Reload template WSDL
The inbound service name {0} could not be changed to {1} because it has been used to publish the service to a UDDI publication object {2}. Please remove all UDDI publications before attempting to change the inbound service name.
The WSDL was successfully reloaded
The WSDL could not be reloaded
When using a UDDI WSDL location type a valid WSDL UDDI registry must also be selected.
Service
Endpoint listeners
New Inbound service
New
Select the service destination and template WSDL location
Select the service destination that is to be enabled for Web service access, and the location of the WSDL that defines the portType of the service.
A destination must be selected.
Select service from template WSDL
Select the required service from the WSDL
Name the inbound service and select endpoint listeners
Select the endpoint listeners to receive requests from the destination and optionally rename the inbound service from the default generated name
Please select one or more endpoint listeners from the list. Only endpoint listeners that are connected to the bus that will be associated with this service are displayed. If there are no endpoint listeners available then create one on an application server or cluster and connect it to the appropriate bus before running this wizard.
Please supply an inbound service name
Inbound service name
Define UDDI publication properties
Describe the manner in which the WSDL describing the inbound service is published to a UDDI registry
A business key must be provided when selecting a UDDI Registry.
You have selected a WSDL location type of UDDI, but have not selected a UDDI registry.
You must select a WSDL location kind
You have supplied an unavailable WSDL Location
There are no services defined in the supplied WSDL location
You have not supplied a WSDL location
Could not retrieve available UDDI registries
Could not find selected UDDI registry
New
Inbound Ports
Custom Properties
Name
Description
Endpoint listener
JAX-RPC handler list
Security request binding
Security response binding
Security configuration
Template port name
Endpoint Listeners
Endpoint Listener
Connection Properties
Associated application
Name
Description
URL root
WSDL serving HTTP URL root
Custom HTTP URL for WSDL publication
The endpoint listener name is already being used.
The endpoint listener name {0} is already being used on {1}. Please use an alternative name. Please note that endpoint listener names are not case sensitive.
A SOAP/JMS endpoint listener cannot be created because there are no listener ports or activation specifications and queue connection factories configured for {0}. Either create the necessary JMS resources or select an alternative binding type.
The endpoint listener "{0}" could not be deleted because it is being used by the following inbound port(s): {1}
Inbound port "{0}" on inbound service "{1}" which is configured on service integration bus "{2}".
The endpoint listener "{0}" could not be deleted because it is being used by some inbound ports. However, there are too many inbound ports referenced to list them all. See SystmOut.log for further details.
The endpoint listener "{0}" could not be deleted because it is being used by the following inbound port(s):
Inbound port "{0}" on inbound service "{1}" which is configured on service integration bus "{2}".
It is not possible to modify the context root portion of the attribute, "{0}", after initial creation. The context root has been reset to its original value but the remaining changes have been retained.
Connection Properties
Name
Description
Value
Bus name
The service integration bus selected is already connected.
UDDI Publication
Name
Description
UDDI reference
Business key
Published service key
Inbound port for WSDL publication
Custom HTTP URL for WSDL publication
The combination of UDDI reference {0} and business key {1} is already being used by UDDI publication {2}. Please supply a different UDDI reference or business key.
Published
Yes
No
Partial
UDDI References
Name
Description
Publish URL
Inquiry URL
Authentication Alias
Password
JAX-RPC Handlers
Name
Class name
Description
JAX-RPC Handler Lists
Name
JAX-RPC Handlers
Description
This is a list of the available JAX-RPC handlers.
This is the list of JAX-RPC handlers currently assigned to this JAX-RPC handler list.
A JAX-RPC handler list must contain at least one JAX-RPC handler.
JAX-RPC Handlers
Name
Position
Description
Add    >>
<< Remove
Down
Up
Initialization Parameters
WSDL Location
WSDL Service Name
WSDL Service Namespace
WSDL Location
WSDL Location Type
WSDL UDDI Registry
SIBWSEndPointListenerReference
serverName
clusterName
endPointListenerName
cachedEndPointAddress
JAX-RPC Header
Namespace URI
Local part
SOAP Roles
Role
A SOAP role must be provided.
Unable to retrieve SIBWSInboundWizardForm from session
Unable to retrieve SIBWSOutboundWizardForm from session
Unable to retrieve WSDL services map from session
Unable to retrieve available port names from session
Unable to retrieve selected port names from session
Unable to retrieve parent service integration bus name from session
Unable to retrieve selected WSDL service name from session
Unable to retrieve selected WSDL service namespace from session
There was an error in the wizard step
There was an error finishing the wizard
Could not find the correct custom action to process
There was an error retrieving the list of configured servers
There was an error retrieving the total list of server configured objects in the cell
Could not save resource
There was an error setting the session data
There are no more outbound ports that can be added to this service
A resourceSet could not be obtained from the repositoryContext.
The endpoint listener "{0}" could not be deleted because it is being used by inbound port "{1}" on inbound service "{2}" which is configured on service integration bus "{3}".
A UDDI reference could not be deleted because it is still being used
Names cannot start or end with a white space, start with a period (.) or contain any of the following characters: \\/,#$@:;"*?<>|=+&%'
An object already exists with the specified identifier
An inbound service named {0} already exists.
An outbound service named {0} already exists.
{0} does not have a UDDI Publication configured so UDDI publishing actions cannot be performed.
There was an error when attempting to publish the WSDL files - see logs for details
There was an error when attempting to publish {0} to UDDI - see logs for details
The field, {0}, is required.
{0} could not be published.
{0} was successfully published.
{0} could not be unpublished.
{0} was successfully unpublished.
{0} is not published using UDDI publication {1}
The supplied service name and namespace do not occur in the WSDL
Could not reload the WSDL - see logs for details
The WSDL must contain ports that map to all configured outbound ports - the ports that have been configured for this service but do not occur in the specified WSDL are {0}. They must be deleted or a valid WSDL provided.
The WSDL must contain all the ports used as templates by the configured inbound ports - the template ports used that do not occur in the WSDL are {0}. They must be changed or a valid WSDL provided.
Default port name is required.
Invalid security configuration and binding specified. The version of the security configuration and binding attributes must match
At least one security binding must be specified if a security configuration is selected
A security configuration must be specified if a security binding is selected
New
Create a new endpoint listener
Select listener name and binding type.
Supply a name for the endpoint listener and select a binding type for it to use.
Select JMS resources (SOAP/JMS endpoint listeners only)
Select the resources to use to configure the endpoint listener URLs
Configure required URLs
Configure URLs for the application root and the WSDL serving root. Select pre-configured URLs based on the known virtual hosts or create a new values.
Endpoint listener name
Binding type
Install the endpoint listener application?
Please supply a name for the endpoint listener.
Use a listener port
Use an activation spec and queue connection factory
Listener port
Activation specification
Queue connection factory
Select a listener port to use to configure a URL root for the endpoint listener.
Select an activation specification to use in conjunction with the queue connection factory to configure a URL root for the endpoint listener.
Select a queue connection factory to use in conjunction with the activation specification to configure a URL root for the endpoint listener.
URL root
Pre-configured URL roots
Configure a new URL root
WSDL serving URL root
Pre-configured WSDL serving URL roots
Configure a new WSDL serving URL root
Please supply a new URL root or select one of the pre-configured options.
Please supply a new WSDL serving URL root or select one of the pre-configured options.
The URL root "{0}" is not a valid entry. Please supplied a valid URL.
The WSDL serving URL root "{0}" is not a valid entry. Please supplied a valid URL.
Connection properties
Select the service integration buses that the new Endpoint Listener should be connected to. Only buses that the application server or cluster is a member of are available for selection.
Available service integration buses
Service integration buses to connect to

An outbound service represents a WSDL-described service.
Manage the outbound services within this service integration bus.
Each port enabled within this outbound service has its own configuration.
Extra properties that customize the way that requests and responses are processed.
The outbound service name.
Description of the outbound service.
The name of the service destination for this outbound service.
The web service WSDL location type.
The URL location or the UDDI service key of the WSDL. When specifying a UDDI service key, provide only the last segment of the key. For example, for a service key of "uddi:cell01:node01:server1:default:6e3d106e-5394-44e3-be17-aca728ac1791", supply a value of "6e3d106e-5394-44e3-be17-aca728ac1791".
The UDDI registry containing the WSDL. Required if the location type is UDDI.
The namespace of the service within the WSDL. Required if there is more than one service in the WSDL.
The name of the service within the WSDL. Required if there is more than one service in the WSDL.
This port is used for all invocations unless it is overridden at runtime.
The name of the port selection mediation that may override the default port for each request.
The bus member to which the port selection mediation is assigned.
Selects whether the access control policy should be enforced.
Each port enabled within this service has its own configuration.
The administrative name of the outbound service.
The name of the service within the WSDL
An outbound port represents a single port for a WSDL-defined service provider. It provides the configuration of invocation of the Web service.
Extra properties that customize the way that requests and responses are processed.
The port name.
An optional description of the port.
The name of the port destination for this port.
The application server or cluster for the port destination.
The namespace of the binding for this point.
The endpoint address for this port.
This defines which list of JAX-RPC handlers is to be invoked for this port.
The security binding to be used with requests sent by this port.
The security binding to be used for responses received by this port.
Specifies the details of how security is applied to requests and responses.
Indicates whether this is the default port.
The host name of the authenticating proxy used for invoking requests for this port.
The port number of the authenticating proxy.
The user ID to be used in requests through the proxy.
The password to be used in requests through the proxy.
The name of the authorization alias that contains the user name and password to use with the authenticating proxy.
An inbound service describes the Web service enablement of a service destination. It provides the configuration of endpoint listeners within a port.
Manage the enablement of destinations as Web services within this service integration bus.
Each port associates this service with an endpoint listener with its own configuration.
Each entry describes the manner in which the WSDL describing this inbound service is published to a UDDI registry.
Publish the WSDL files for this service to a .zip file
The inbound service name. This name appears as the service name within WSDL published for this inbound service.
An optional description of the inbound service. This description appears in any published WSDL for this service.
The service destination to be enabled for Web service access.
The type of the template WSDL Location.
The URL location or UDDI service key of the template WSDL.
The UDDI registry containing the template WSDL. Required for UDDI location type.
The namespace of the service within the template WSDL. Only required if there is more than one service in the WSDL.
The name of the service within the template WSDL. Only required if there is more than one service in the WSDL.
Indicates whether the access control policy should be enforced.
The name of the service within the template WSDL
This defines the physical endpoint listener at which requests are received
The administrative name of the inbound service
An inbound port describes the Web service enablement of a service destination on a specific endpoint listener, with associated configuration.
Extra properties that may customize the way that requests and responses are processed.
The inbound port name. This name appears as the port name within the WSDL published for the inbound service.
An optional description of the inbound port. This description appears in any published WSDL for this port.
This defines the physical endpoint listener at which requests for this port are received.
This defines which list of JAX-RPC handlers is to be invoked for this port.
The security binding to be used for requests received by this port.
The security binding to be used for responses sent by this port.
Specifies the details of how security is applied to requests and responses.
Name of the port in the template WSDL to use as a basis for this port's binding
An endpoint listener receives requests from service requester applications within a specific application server or cluster.
Manage endpoint listeners for this gateway instance.
Configure endpoint listeners
Defines the manner in which an endpoint listener connects to the service integration bus.
The name of this endpoint listener.
An optional description of the endpoint listener.
The root of the URL that should be used to build the endpoint addresses within WSDL documents to direct requesters to this endpoint listener.
WSDL serving HTTP URL root
The HTTP URL root of the servlet that may be used to serve the WSDL that describes services that use this endpoint listener. Required if the URL root is not an HTTP URL.
The application that handles the requests for this endpoint listener.
Connection properties define the manner in which an endpoint listener connects to the service integration bus.
The name of this property.
An optional description of the property.
The value of the property.
The name of this property.
Describes the manner in which the WSDL describing an inbound service is published to a UDDI registry.
The name of this UDDI publication property.
An optional description of the UDDI publication properties.
The reference of the UDDI registry to which WSDL is to be published.
The key of the business within which this service is to be published.
The key of the service as published to the UDDI registry.
The inbound port that is to serve the WSDL that describes this service.
The HTTP URL root of the servlet that is to serve the WSDL that describes this service.
A UDDI reference describes the parameters necessary to connect to a particular UDDI registry.
The name of this UDDI reference.
An optional description of the UDDI Registry.
The URL that applications use to publish to the UDDI registry.
The URL that applications use to inquire on the UDDI registry.
The user ID for accessing the UDDI repository
The password for accessing the UDDI repository.
A JAX-RPC handler provides customization of Web service request or response handling.
The name of this JAX-RPC handler.
An optional description of the JAX-RPC handler.
The name of the class that implements the JAX-RPC handler.
A JAX-RPC handler list defines an ordered list of JAX-RPC handlers to be invoked against requests and responses.
The name of this JAX-RPC handler list.
The JAX-RPC handlers in this list.
An optional description of the JAX-RPC handler list.
A JAX-RPC handler list defines an ordered list of JAX-RPC handlers to be invoked against requests and responses.
The JAX-RPC handler to add.
The position in which the handler is to be added.
Defines the initialization parameters for this handler.

The name of the service within the WSDL. Only required if there is more than one service in the WSDL.
The namespace of the service within the WSDL.  Only required if there is more than one service in the WSDL.

The type of the location of the service providers WSDL document.
The UDDI registry containing the service provider's WSDL document. Required for UDDI Location Type.
Contains information about the endpoint listener which this InboundPort is associated with. See SIBWSEndpointListener in the sibwsepl package.




Defines the JAX-RPC headers against which this handler operates.
The namespace of the header that is processed by this handler
The local part of the name of the header that is processed by this handler
Defines the SOAP roles in which this handler acts
Defines the SOAP roles in which this handler acts
Use this wizard to create a new HTTP/HTTPS/JMS endpoint listener.
Enter a name for the endpoint listener.
Select a binding type for the endpoint listener.
If you choose not to install the standard application the endpoint listener will not work at runtime.
Select a queue connection factory
Select a pre-configured URL based on the available virtual hosts or configure a new value.
Select a pre-configured URL based on the available virtual hosts or configure a new value.

Web service gateway instances
Gateway services
Proxy services
Endpoint listeners
Name
Description
Gateway namespace
Default proxy WSDL URL
Endpoint listeners
Proxy services
Inbound web service enablement
Outbound web service enablement
Proxy service name
Description
Port destination point
Proxy request destination name
Request mediation
Request mediation bus member
Proxy response destination name
Response mediation
Response mediation bus member
Proxy WSDL override URL
New proxy service
Proxy port point
Endpoint listeners
Specify proxy service name, destinations and mediations
Provide the names of the objects that are to be used to support the gateway service in the runtime.
Select Endpoint listeners
Select the endpoint listeners to receive requests for the proxy service.
New
Gateway services
Target services
Inbound web service enablement
Gateway service name
Description
Gateway request destination name
Request mediation
Request mediation bus member
Gateway response destination name
Response mediation
Response mediation bus member
Default target service
New gateway service
Target service type
WSDL-defined web service provider
Service destination
Request destination
Select type of target service
Target services are either service destinations or WSDL-defined web service providers
Target destination name
Target bus name
Provide the names of the objects that are to be used to support the gateway service in the runtime.
New
Specify gateway service name, service destinations and mediations
Locate the target service WSDL
Select service
Select ports
Name the service and port destinations
Select points for service and port destinations
Select endpoint listeners
Define UDDI publication properties
Specify gateway service name, service destinations and mediations
Select template WSDL location
Select service
Select endpoint listeners
Define UDDI publication properties
Select the endpoint listeners to receive requests from the destination.
Target services
Outbound web service enablement
Name
Description
Bus name
Destination name
Identity information
Please specify a gateway service name
Please select a target destination.  If none are available to select, please create a destination before running this wizard
Please provide a name for the proxy service
A service named {0} already exists.
A service named {0} already exists.
An inbound service named {0} already exists. The service name will also be used to create an inbound service, please supply a new name.
An outbound service named {0} already exists. The service name will also be used to create an outbound service, please supply a new name.
A target service named {0} already exists.
A gateway instance named {0} already exists.
A destination already exists with the name chosen for the response destination.
A destination already exists with the name chosen for the request destination.
Creating a gateway service will attempt to create an inbound service of the same name. An inbound service already exists whose name has been chosen for the gateway service.
The proxy WSDL override URL supplied does not represent a valid WSDL: {0}
The default proxy WSDL URL supplied does not represent a valid WSDL: {0}
The proxy WSDL override URL supplied has multiple services defined in it: {0}
The default proxy WSDL URL supplied has multiple services defined in it: {0}
The default proxy WSDL URL supplied to the parent gateway instance is now invalid and does not represent a valid WSDL: {0}
The default proxy WSDL URL supplied to the parent gateway instance is now invalid and has multiple services defined in it: {0}
Default target service is required.
The destination named {0} does not exist within the bus named {1}.
The inbound service named {0} associated with this gateway service does not exist. Please recreate the inbound service using that name and this gateway service''s destination. Alternatively, delete and recreate this gateway service.
The outbound service named {0} associated with this target service does not exist. Please recreate the outbound service using that name and this target service''s destination. Alternatively, delete and recreate this target service.
The inbound service named {0} associated with this proxy service does not exist. Please delete and recreate this proxy service.
The outbound service named {0} associated with this proxy service does not exist. Please delete and recreate this proxy service.
Response mediation bus member is required
Request mediation bus member is required
The request destination and reply destination names must not match
The service name is not a valid entry
Unable to retrieve WSGWProxyServiceDetailForm from session
Unable to retrieve WSGWGatewayServiceWPMWizardForm from session
Unable to retrieve WSGWGatewayServiceWSDLWizardForm from session

A web services gateway allows you to configure specific endpoint listeners and deploy gateway and proxy services to those listeners.
List of web services gateways within the service integration bus.
Manage instances of the web services gateway within this service integration bus.
Manage gateway services
Manage proxy services
Manage endpoint listeners for this gateway instance.
The name of the web services gateway instance.
An optional description of the web services gateway instance.
The namespace assigned to this gateway for use in WSDL generation.
The URL of the default proxy WSDL description for use with proxy services.
Manage endpoint listeners for this gateway instance.
A proxy service provides the configuration of the web service enablement of a service destination that is able to act as a proxy for a variety of providers.
Proxy services deployed to the gateway instance.
Configure the enablement of the proxy service as a web service.
Configure the outbound invocation of web services from the proxy service.
The name of the proxy service
An optional description of the proxy service.
The service integration bus member that owns the resources for the proxy port destination.
The name of the service destination to be used to process request messages for this proxy service.
The optional name of the mediation that is run to process messages on the request destination.
The optional bus member to which the request mediation is assigned.
The name of the service destination to be used to process response messages for this proxy service.
The optional name of the mediation that is run to process messages at the response destination.
The optional bus member to which the response mediation is assigned.
The URL location of the WSDL used to override the default bindings.
The point where the proxy port destination is to be located.
The name of the service destination to be used to process request messages for this proxy service. You do not need to provide destination names. If you leave these fields blank they will be populated automatically, with values based upon the service name, at the end of the service creation process.
The name of the service destination to be used to process response messages for this proxy service. You do not need to provide destination names. If you leave these fields blank they will be populated automatically, with values based upon the service name, at the end of the service creation process.
This defines the physical endpoint listeners at which requests are received for the proxy service.
A gateway service provides the configuration of the web service enablement of a service destination, along with the information that maps to one or more target destinations.
Manage the set of target services for the gateway service.
Configure the enablement of the gateway service as a web service.
The name of the gateway service.
An optional description of the gateway service.
The name of the service destination to be used to process request messages for this gateway service.
The optional name of the mediation that is run to process messages on the request destination.
The optional bus member to which the request mediation is assigned.
The name of the service destination to be used to process response messages for this gateway service.
The optional name of the mediation that is run to process messages at the response destination.
The optional bus member to which the response mediation is assigned.
The default target service to be selected.
The type of the target service.
The name of the service destination to be used to process request messages for this gateway service. You do not need to provide destination names. If you leave these fields blank they will be populated automatically, with values based upon the service name, at the end of the service creation process.
The name of the service destination to be used to process response messages for this gateway service. You do not need to provide destination names. If you leave these fields blank they will be populated automatically, with values based upon the service name, at the end of the service creation process.
The name of the service destination that is the target for requests on this gateway service
The name of the service integration bus that owns the target destination
A target service is one of a set that may be routed to from a gateway service.
Configure the outbound invocation of web services from the target service.
The name of the target service.
An optional description of the target service.
The name of the service integration bus in which the target destination is configured.
The name of the destination.
Identity information used when routing to this target service.

Inbound WS-Security configuration
Name
Request consumer
Response generator
Outbound WS-Security configuration
Name
Response consumer
Request generator
WS-Security configurations
Name
Service type
Inbound
Outbound
Name
Name
New WS-Security configuration
Specify service type
Specify WS-Security configuration type.
Specify WS-Security configuration type.
Summary
The actor URI must be in absolute format. The relative URI format is not supported.
The actor URI "{0}" is invalid.
Request consumer binding
Name
Request generator binding.
Name
Response consumer binding
Name
Response generator binding configuration
Name
WS-Security bindings
Name
Binding Type
Request consumer
Request generator
Response consumer
Response generator
Name
Name
Name
Name
New WS-Security binding
Specify binding type
Specify WS-Security binding.
Specify WS-Security binding.
Specify WS-Security binding.
Specify WS-Security binding.
Summary
Actor URI
Properties
Actor URI
Properties
Required integrity
Message parts
Nonce
Time stamp
Name
Usage
Message Parts
Dialect
Name
Keyword
Nonce
Name
Dialect
Keyword
Time stamp
Name
Dialect
Keyword
Expires
Required confidentiality
Message parts
Nonce
Time stamp
Name
Usage
Required security token
Name
URI
Local name
Usage
Caller
Properties
Trust method
Local name
Name
Part
URI
Add time stamp
Properties
Expires
Enabled
Dialect
Keyword
Integrity
Message parts
Nonce
Time stamp
Name
Order
Confidentiality
Message parts
Nonce
Time stamp
Name
Order
Security Token
Name
URI
Local Name
Actor
Actor
Actor
Actor
Trust Method
Properties
Local Name
Name
Part
URI
Trust any
The request consumer binding configuration could not be found
The request generator binding configuration could not be found
The response consumer binding configuration could not be found
The response generator binding configuration could not be found
The inbound service configuration could not be found
The outbound service configuration could not be found
The name is already used by an existing Required Integrity or Required Confidentiality object
The value of Keyword must be one of {0}
A value of {0} has already been set by another integrity or confidentiality constraint.
The value of Order must be an integer between {0} and {1}
A WS-Security configuration with this name already exists
A WS-Security binding configuration with this name already exists
WS-Security version
Response sender
Response receiver
Request sender
Request receiver
Security version
Select security version
Select security version
Request receiver
Response sender
Request sender
Response receiver
Integrity
Required integrity
Body
Time stamp
Security token
Confidentiality
Required confidentiality
Body content
Username token
Login configuration
Basic authentication
Use Nonce
Nonce time stamp required
ID assertion
Signature
LTPA
Custom authentication methods
Name
{0} is a standard authentication method. To use {0} please select the appropriate checkbox under the Login configuration general properties.
Basic authentication Nonce settings
A custom authentication method has not been provided
Authentication method
Custom authentication method
Login configuration
ID assertion
Signature method
Trust mode
Add created time stamp
Add received time stamp
Enabled
Expires
Actor
Actor
{0} could not be deleted because it is referenced by {1} port: {2} on {1} service: {3}
inbound
outbound
Draft 13
1.0
(Draft 13)
(1.0)
Optional
Required
Rejected
Observed
Ignored

WS-Security configuration for an inbound request. This defines WS-Security requirements for the request consumed from the client and the response generated. The objects created may be applied to one or more inbound ports.
The name of the inbound WS-Security configuration.
WS-Security configuration for an outbound request. This defines WS-Security requirements for the request generated and response consumed from the target. The objects created may be applied to one or more outbound ports.
The name of the outbound WS-Security configuration.
WS-Security configurations for inbound and outbound services.
The name of the WS-Security configuration.
The type of service the WS-Security configuration applies to.
Name of the inbound WS-Security configuration.
Name of the outbound WS-Security configuration.
Use this wizard to create a new inbound or outbound WS-Security configuration.
WS-Security binding for the consumption of inbound requests from the caller.
The name of the binding.
WS-Security binding for the generation of outbound request to a target.
The name of the binding.
WS-Security binding for consumption of responses from outbound target.
The name of the binding.
WS-Security binding for generation of responses to caller.
The name of the binding.
WS-Security bindings for consumption and generation of requests and responses.
The name of the WS-Security binding.
The type of binding. This is one of request consumer, request generator, response consumer and response generator.
The type of binding. This is one of request receiver, request sender, response receiver and response sender.
Name of the request consumer binding.
Name of the binding.
Name of the response consumer binding.
Name of the response generator binding.
Use this wizard to configure a new WS-Security binding.
WS-Security headers within the consumed request message will only be processed if they have the specified Actor URI.
General properties for the inbound WS-Security configuration.
WS-Security headers within the consumed response message will only be processed if they have the specified actor URI.
General properties for the outbound WS-Security configuration.
Specifies the integrity constraints consumed messages must meet. This includes specifying which message parts within the incoming message must be digitally signed, and the message parts to which attached digitally signed Nonce and time stamp elements are expected.
Specifies parts of the message affected by this required integrity constraint.
Specifies the digitally signed Nonce elements which must be present in the consumed message, and what parts of the message they must be attached to. Nonce is a randomly generated value.
Specifies the digitally signed time stamp elements which must be present in the consumed message, and what parts of the message they must be attached to.
The name of the required integrity element.
Indicates the assertion of the required integrity constraint.
Identifies a specific message part according to the specified dialect and keyword.
The expression dialect to use.
The name of the message part definition.
Identifies the message part in a way defined by the chosen dialect.
Attaches a Nonce element to the message part specified by the dialect and keyword attributes. Nonce is a randomly generated value.
The name of the Nonce element.
The expression dialect to use.
The message part to attach the Nonce element to, specified in a way defined by the chosen dialect.
Attaches a time stamp element to the message part specified by the dialect and keyword attributes.
The name of the time stamp element.
The expression dialect to use.
The message part to attach the time stamp element to, specified in a way defined by the chosen dialect.
The expiration time of the time stamp, defined as an xsd:Duration type.
Specifies the confidentiality constraints consumed messages must meet. This includes specifying which message parts within the incoming message must be encrypted, and the message parts to which attached encrypted Nonce and time stamp elements are expected.
Specifies parts of the message affected by this required confidentiality constraint.
Specifies the encrypted Nonce elements which must be present in the consumed message, and what parts of the message they must be attached to. Nonce is a randomly generated value.
Specifies the encrypted time stamp elements which must be present in the consumed message, and what parts of the message they must be attached to.
The name of the required confidentiality element.
Indicates the assertion of the required confidentiality constraint.
Specifies accepted stand-alone security tokens within a consumed message. Stand-alone security tokens are those not already used for signature or encryption. Defining a required security token means that messages containing a token of that type will be processed according to the usage assertion. The security token will not be used for authentication unless it is also specified within a caller.
The name of the security token.
Specifies the namespace URI of the security token.
Specifies the local name of the security token.
Indicates the assertion of the required security token constraint.
Specifies the security token, signed part or encrypted part used for authentication. If a signed or encrypted part is used, the value of the part attribute must be the name of a defined required integrity or required confidentiality constraint. If a stand-alone security token is used for authentication, then the URI and local name attributes must define the type of security token used for authentication.
Properties associated with the caller.
The trust method associated with this caller if IDAssertion is in use for verifying an asserted ID from an intermediary.
Specifies the local name of the security token to be used for authentication.
The name of the caller.
Specifies the name of the required integrity or required confidentiality part within the message to be used for authentication.
Specifies the namespace URI of the security token to be used for authentication.
When add time stamp is specified for a consumer, a time stamp is added indicating when the message was consumed. For a generator, a time stamp is added indicating when the message was generated.
Properties associated with the added time stamp.
The expiration time of the time stamp, defined as an xsd:Duration type.
If selected, a time stamp will be added to the message.
The expression dialect to use.
The message part to attach the time stamp element to, specified in a way defined by the chosen dialect.
Specifies the integrity constraints applied to generated messages. This includes specifying which message parts within the generated message must be digitally signed, and the message parts to attach digitally signed Nonce and time stamp elements to.
Specifies parts of the message affected by this integrity constraint.
Specifies the digitally signed Nonce elements which must be inserted into the generated message, and what parts of the message they must be attached to. Nonce is a randomly generated value.
Specifies the digitally signed time stamp elements which must be inserted in the generated message, and what parts of the message they must be attached to.
The name of the integrity constraint.
Specifies the processing order of this integrity constraint.
Specifies the confidentiality constraints applied to generated messages. This includes specifying which message parts within the generated message must be encrypted, and the message parts to attach encrypted Nonce and time stamp elements to.
Specifies parts of the message affected by this confidentiality constraint.
Specifies the encrypted Nonce elements which must be inserted into the generated message, and what parts of the message they must be attached to. Nonce is a randomly generated value.
Specifies the encrypted time stamp elements which must be inserted in the generated message, and what parts of the message they must be attached to.
The name of the confidentiality constraint.
Specifies the processing order of this confidentiality element.
Specifies stand-alone security tokens to insert into the generated message. Stand-alone security tokens are those not already used for signature or encryption. Standard and custom security tokens may be defined by URI and local name.
The name of the security token
Specifies the namespace URI of the security token to insert.
Specifies the local name of the security token to insert.
Defines the Actor URI to be included in the WS-Security headers of a generated message.
Defines the Actor URI to be included in WS-Security headers of generated request.
Defines the Actor URI to be included in WS-Security headers of generated response.
Defines the Actor URI to be included in WS-Security headers of generated response.
Defines a trust method used to validate the identity of a trusted intermediary asserting an ID on a downstream message. When a trust method is configured, the security token defined by the caller is expected to contain an identity to be asserted.
Properties associated with the trust method.
Specifies the local name of the security token to use to validate the intermediary.
The name of the trust method.
Specifies the name of the required integrity or required confidentiality part within the message to be used to validate the intermediary.
Specifies the URI of the security token to use to validate the intermediary.
If trust any is selected then all upstream intermediaries will be trusted by this consumer. This should only be selected if you are certain that all upstream intermediaries are trusted. Selecting trust any will automatically override all other attributes of this trust method.
Identifies the version of the WS-Security specification this configuration uses.
Draft 13 WS-Security binding for generation of responses to a caller.
Draft 13 WS-Security binding for consumption of responses from a target.
Draft 13 WS-Security binding for the generation of requests to an outbound target.
Draft 13 WS-Security binding for the consumption of inbound requests from the caller.
Specifies the integrity constraints applied to sent messages. Indicates which parts of the message will be digitally signed.
Specifies the integrity constraints received messages must meet. Indicates which parts of the message must be digitally signed.
Specifies that the body of the message must be digitally signed.
Specifies that the time stamp header must be digitally signed.
Specifies that the security token header must be digitally signed.
Specifies the confidentiality constraints applied to sent messages. Indicates which parts of the message will be encrypted.
Specifies the confidentiality constraints applied to sent messages. Indicates which parts of the message will be encrypted.
Specifies that the body of the message must be encrypted.
Specifies that the username token header must be encrypted.
Specifies the authentication methods this service supports. Custom authentication methods can also be defined.
Specifies that a username and password is used as an authentication method.
Specifies that the username token should contain a Nonce element. Nonce is a randomly generated value.
Specifies that the username token should contain a Nonce time stamp element. Nonce is a randomly generated value.
Specifies that ID Assertion is used as an authentication method. An ID Assertion configuration must also be set.
Specifies that digital signature is used as an authentication method.
Specifies that Lightweight Third Party Authentication is used as an authentication method.
Specifies custom authentication methods this service will accept.
The name of the custom authentication method to accept.
Specifies Nonce settings for when Basic Authentication is used. Nonce is a randomly generated value.
Specifies the pre-defined authentication method to use.
Specifies the custom authentication method to use. If a custom authentication method is specified, no pre-defined method can be used.
Specifies the authentication method to use in the request. May be a pre-defined or custom authentication method.
Specifies the signature method and trust mode to use when ID Assertion is set as an authentication method.
Specifies the method by which the identity will be asserted.
Specifies the method by which the identity of the trusted party will be provided.
Specifies whether a time stamp will be added to any sent message. The time stamp may also contain an expires value.
Specifies whether a time stamp will be added to any received message.
When selected, a time stamp will be added to the message.
The expiration time of the time stamp, defined as an xsd:Duration type.
Defines the Actor URI to be included in the WS-Security headers of a generated message.
Defines the Actor URI to be included in the WS-Security headers of a generated message.

WS-Notification services
Name
Service integration bus name
Description
Enable dynamic topic namespaces?
JAX-RPC handler list
Outbound security response binding
Outbound security request binding
Outbound security configuration
Requires registration
Fixed topic set
Topic expression dialects
Dynamic topic space name
Delete service integration bus topic spaces?
Use an existing service integration bus
Create a new service integration bus called:
Select a bus member
Endpoint listener
Use an existing endpoint listener
Create a new endpoint listener using:
WS-Notification service points
Permanent topic namespaces
Notification broker inbound service settings
Subscription manager inbound service settings
Publisher registration manager inbound service settings
New WS-Notification service
Name and describe the WS-Notification service
Supply a name and description for the WS-Notification service
Select a service integration bus
Select an existing (or provide a name for a new) service integration bus
Select bus member
Select an existing member of the selected bus to associate with a service point
Select the service point endpoint listener
Select an existing endpoint listener that has been previously configured on the selected endpoint or create a new one
Configure a permanent topic namespace
Supply a namespace and select a service integration bus topic space to associate with this permanent topic namespace
New
_Bus
_Instance
_TopicNamespace
Please supply a name for the WS-Notification service
A WS-Notification service called "{0}" already exists on service integration bus "{1}"
There are no bus members available for use on service integration bus "{0}"
Please supply a namespace for the permanent topic namespace
Create a permanent topic namespace?
White spaces are not permitted in WS-Notification service names.
White spaces are not permitted in WS-Notification service names.
Permanent topic namespace
Namespace
Service integration bus topic space
Topic namespace documents
applied
Message reliability
Assured persistent
Reliable persistent
Reliable non-persistent
Express non-persistent
Best effort non-persistent
Create a new topic space (please specify name)
Please supply a topic space
Please supply a topic namespace
The associated service integration bus topic space "{0}" cannot be found and may have previously been deleted by some other action - this means that the configuration for this permanent topic namespace is corrupt.
Use an existing service integration bus topic space
Create a new service integration bus topic space called:
Delete service integration bus topic space(s)?
A permanent topic namespace "{0}" already exists on this WS-Notification service.
Topic namespace document
Document name
Description
URL of topic namespace document
Document contents
Associated permanent topic namespace
WS-Notification service points
Name
Associated bus member
Description
Bus member not defined
Channel
Channel 1
Channel 2
Binding type
SOAP/HTTP
SOAP/JMS
Host name
Host port
Notification broker inbound port settings
Subscription manager instance inbound port settings
Publisher registration manager inbound port settings
A WS-Notification service point called {0} already exists on WS-Notification service {1}.
A WS-Notification service called {0} already exists on service integration bus {1}.
Administered subscribers
External web service endpoint
Dialect
Topic
Topic namespace
Remote subscription timeout
Simple
Concrete
Full
The topic supplied is not compatible with the selected dialect. When using the SIMPLE dialect only root topics may be specified. When using the CONCRETE dialect wildcards may not be used.
Select a topic namespace defined on this WS-Notification service or specify a new value
Configure a topic namespace for this administered subscriber
Select a topic namespace configured on this WS-Notification service
Specify a new topic namespace
New WS-Notification service point
Name, describe and select a bus member for the WS-Notification service point
Supply a name and description and select a bus member for the WS-Notification service point
Select the service point endpoint listener
Select an existing endpoint listener that has been previously configured on the selected bus member or create a new one
New
Copy
Please supply a name for the WS-Notification service point
Please select one (and only one) WS-Notification service point to copy the advanced service integration bus inbound port settings from.
Publisher registrations
Publisher ID
Topic
Demand based
Creation time
Termination time
Producer EPR
"{0}" already exists
WS-Notification service point
At least one WS-Notification service point must be created.
Create WS-Notification service points
A WS-Notification must have at least one service point. Review the collection of WS-Notification service points and then select "Yes" to create a new instance or "No" once all the required instances have been created.
Create a new endpoint listener
Create a new permanent topic namespace
Configure name, description service integration bus and dynamic topic namespace settings
Configure JAX-RPC handler and web services security settings
Optionally choose a JAX-RPC handler list and security configuration and bindings
Create permanent topic namespaces
A WS-Notification may optionally have one or more permanent topic namespaces. Review the collection of permanent topic namespaces and then select "Yes" to create a new instance or "No" once all the required instances have been created.
Summary
Summary of actions
Configure name, description and select a bus member
Select or create an endpoint listener
Configure namespace and select service integration bus topic space
A WS-Notification service cannot be created because there are no service integration buses configured. Please create at least one service integration bus before attempting to create a WS-Notification service.
Proceeding to the next step will result in a new WS-Notification service being created (the configuration will be modified and subsequent cancellation actions will not delete it)
A new WS-Notification service was successfully created - further configuration of service points and namespaces are required to make it functional.
It will not be possible to update the bus and dynamic topic space settings now that the WS-Notification service has been created.
Please supply a dynamic topic space name for this WS-Notification service.
Please select an existing endpoint listener or use the button provided to create a new one.
The WS-Notification service called "{0}" was created on service integration bus "{1}".
The WS-Notification service point called "{0}" was created on bus member "{2}". Endpoint listener "{1}" on that bus member was selected to expose the service.
The permanent topic namespace "{0}" was created using service integration topic space "{1}".
Subscriptions
Subscription id
Topic(s)
Delivery state
Consumer EPR
Creation time
Termination time
Pull type
Service integration bus subscriptions
Service integration bus subscriptions
Topic namespace
Unable to locate publication point {0}.
Unable to locate subscription {0}.
Pull points
Pull point id
Creation time
Termination time
Subscription id
Producer EPR
Topic
Subscription reference
State

A WS-Notification service provides access to service integration bus resources for Web services publish and subscribe clients.
The name of the WS-Notification service.
The name of the service integration bus with which the WS-Notification service is associated.
An optional description of the WS-Notification service.
Indicates whether dynamic topic namespaces can be used within the WS-Notification service.
The JAX-RPC handler list that is applied to inbound service requests for the WS-Notification service.
The security binding to be used with remote publisher responses received by this WS-Notification service.
The security binding to be used with consumer notifications and remote publisher requests sent by this WS-Notification service.
Specifies the details of how security is applied to requests and responses.
Indicates whether publisher applications are required to register with the broker before they can publish notifications.
Indicates whether the list of topics supported by the notification broker is fixed or may vary at runtime.
List of topic dialects supported by this WS-Notification service.
The name of the service integration bus topic space to be used as the dynamic topic space for this WS-Notification servce.
The bus member associated with the WS-Notification service point.
An endpoint listener receives requests from service requester applications within a specific application server or cluster.
Select this link to configure the deployment of WS-Notification service points on one or more servers.
Select this link to configure permanent topic namespaces for the WS-Notification service.
The inbound service defined for the notification broker role of this WS-Notification service.
The inbound service defined for the subscription manager role of this WS-Notification service.
The inbound service defined for the publisher registration manager role of this WS-Notification service.
REQUIRED
Select this link to configure additional custom properties for this WS-Notification service.
Select this link to configure additional custom properties for this WS-Notification service point.
Select whether or not the service integration bus topic spaces associated with the WS-Notification service (including those associated with all the WS-Notification topic namespaces) should also be deleted.
A topic namespace is a grouping of topics that allows information to be shared between applications.
The URI string by which this topic namespace is known.
The service integration bus topic space with which this namespace is associated.
The collection of topic namespace documents that define the structure of the topic namespace.
The service integration bus reliability to apply to messages published to this topic namespace.
Choose an existing service integration bus topic space.
Create a new service integration bus topic space associated with this topic namespace.
Choose whether the service integration bus topic space associated with each WS-Notification topic namespace should also be deleted.
A topic namespace can optionally have topic namespace documents applied to it that define the structure of the topics that are permitted within the namespace.
The name of the file from which the topic namespace document was originally loaded.
An optional description of the topic namespace document.
The URL of the topic namespace document that should be loaded.
The contents of the topic namespace document.
The topic namespace to which this document is applied.
A WS-Notification service point defines access to a WS-Notification service on a given bus member through a specified Web service binding (for example SOAP over HTTP). Applications use the bus members associated with the WS-Notification service point to connect to the WS-Notification service.
The name of the WS-Notification service point. This appears as part of the address of the Web service that is exposed on the chosen server.
The name of the bus member on which this WS-Notification service point is deployed.
An optional description of the WS-Notification service point.
The inbound port defined for the notification broker role of this WS-Notification service point.
The inbound port defined for the subscription manager role of this WS-Notification service point.
The inbound port defined for the publisher registration manager role of this WS-Notification service point.
An administered subscriber provides a mechanism for the WS-Notification service point to subscribe to an external notification producer at server startup time.
The URL of the external Web service to which the service should subscribe.
The dialect in which the topic is expressed.
The topic on which the service should subscribe.
Create a new WS-Notification service point.
The set of applications that are currently registered as publishers with the notification broker.
The unique identifier of this publisher registration.
The topic on which the publisher is registered to publish.
Indicates whether this is a demand based publisher.
The time at which the registration will be deleted.
Additional publisher related data.
Configure a new permanent topic namespace for the current WS-Notification service.
This collection lists the subscriptions that have been created on the associated bus member or members by WS-Notification applications. Use this panel to view the information about a subscription, such as the topic on which the subscription is registered and the time at which it is currently set to expire. You can also delete a subscription using the button provided.
This collection lists the service integration bus subscriptions associated with the previously selected WS-Notification subscription.
This collection lists the pull points that have been created on the associated bus member or members by WS-Notification applications. Use this panel to view the information about a pull point, such as the subscription with which it is associated and the time at which it is currently set to expire. You can also delete a pull point using the button provided.
The URI that describes the topic namespace in which the specified topic is defined.
The length of time in hours after which the remote subscription will expire if not renewed by the server.
The endpoint reference of the remote Web service application from which event notifications are received.
The topic for which event notifications have been requested.
The current runtime state of the administered subscriber.
The time at which the registration was created.
The unique identifier of the pull point.
The time at which the pull point was created.
The time at which the pull point will be deleted.
The unique identifier of the subscription associated with the pull point.
The unique identifier of the subscription.
The current runtime state of the subscription.
The endpoint reference to which event notifications matching the subscription are sent.
Indicates whether the subscription is being used in pull mode.
The time at which the subscription was created.
The time at which the subscription will be deleted.
The service integration bus durable subscription or subscriptions that are associated with the WS-Notification subscription.


Reference topic

Terms of Use | Feedback

Last updated: 15 Mar 2007
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\share\auto_help_sib_entities.html

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