Security for bus {0}
General properties
General properties
Additional properties
General properties
General properties
A WebSphere MQ queue manager on the WebSphere MQ network with which WebSphere Application Server applications perform messaging.
A WebSphere MQ queue sharing group on the WebSphere MQ network with which WebSphere Application Server applications perform messaging.
Messages flow in both directions between the bus and WebSphere MQ.
Messages flow only from the bus to WebSphere MQ.
Messages flow only to the bus from WebSphere MQ.
The state of the message is unknown.
The acceptable reliability of message delivery for inbound persistent message flows from WebSphere MQ, from Reliable to Assured, in order of increasing reliability.
The acceptable reliability of message delivery for inbound nonpersistent message flows from WebSphere MQ, from Reliable to Assured, in order of increasing reliability.
Transmission of the message has been completed.
The message transmission is being committed.
The message is waiting to be sent.
The transmit message request is waiting for an acknowledgement that the message has been transmitted.
JNDI name
Additional custom properties for this runtime component. Some components may make use of custom configuration properties which can be defined here.
The name of a bus member. This option retrieves the active messaging engines that are hosted by the named bus member (an application server or server cluster).
The name of a custom group of messaging engines (that form a self-declaring cluster). This option retrieves the active messaging engines that have registered with the named custom group.
The name of a messaging engine. This option retrieves the available endpoints that can be used to reach the named messaging engine.
It is preferred that a messaging engine be selected from the target group. A messaging engine in the target group is selected if one is available. If a messaging engine is not available in the target group, a messaging engine outside the target group is selected if available in the same service integration bus.
It is required that a messaging engine be selected from the target group. A messaging engine in the target group is selected if one is available. If a messaging engine is not available in the target group, the connection process fails.
JFAP inbound channel
MQFAP inbound channel
Messaging engine
Runtime service integration properties of the message.
Application Programming Interface properties of the message.
Java Message Service properties of the message.
Service integration bus properties of the message.
Controls the reliability delivery option for message flows between producers and the destination. Select this option to use the reliability defined for the destination instead of the reliability specified by producers.
The message-driven bean uses a JMS queue. The JNDI name of the JMS queue is specified on the Destination JNDI name property.
The message-driven bean uses a JMS topic. The JNDI name of the JMS topic is specified on the Destination JNDI name property.
Messages can be lost if a messaging engine fails, but are not lost under normal operating conditions.
The message provider preemptively assigns messages to consumers on nondurable subscriptions and unshared durable subscriptions. That is, read ahead optimization is turned on only when there can only be a single consumer.
The messaging provider preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests.
The messaging provider does not preemptively assign messages to consumers.
The messaging provider preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests for this destination.
The messaging provider does not preemptively assign messages to consumers for this destination.
Read ahead optimization is defined on the connection.
Retrieves the active messaging engines that are hosted by the named bus member.
Retrieves the active messaging engines that provide message points for the named destination.
Retrieves the active messaging engines that have registered with the named custom group.
Retrieves the available endpoints that can be used to reach the named messaging engine.
Retrieves the available endpoints that can be used to reach the messaging engine identified by this UUID value.
Connections can be made to messaging engines in the same application server.
Connections can be made to messaging engines in the same host.
Connections can be made to messaging engines in the same server cluster.
Connections can be made to messaging engines in the same bus.
The persistence of messages on this topic is defined by the producing application.
The bus destination uses the default exception destination.
The bus destination has no exception destination.
The bus destination uses the exception destination specified in this field.
The message request has been made, but has not yet been acknowledged.
The message request is now waiting for acknowledgment.
The message request has been acknowledged.
The message request is being removed.
The message request has been rejected.
All messages sent to this topic are treated as nonpersistent.
All messages sent to this topic are treated as persistent.
The session automatically acknowledges the delivery of a message.
The session lazily acknowledges the delivery of messages, which can improve performance, but can lead to a message-driven bean receiving a message more than once.
The messaging provider stores messages while the message-driven bean is not available, and delivers the messages when the message-driven bean becomes available again.
The messaging provider does not store and redeliver messages if a message-driven bean is not available.
Clones are supported.
Clones are not supported.
The alias destination uses (inherits) the value of the corresponding property on the target destination.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable.
Messages are discarded when a messaging engine stops or fails.
Messages may be discarded when a messaging engine fails.
Messages are not discarded.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable.
Messages are discarded when a messaging engine stops or fails.
Messages may be discarded when a messaging engine fails.
Messages are not discarded.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable.
Messages are discarded when a messaging engine stops or fails.
Messages may be discarded when a messaging engine fails.
Messages are not discarded.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable.
Messages are discarded when a messaging engine stops or fails.
Messages may be discarded when a messaging engine fails.
Messages are not discarded.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable.
Messages are discarded when a messaging engine stops or fails.
Messages may be discarded when a messaging engine fails.
Messages are not discarded.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable.
Messages are discarded when a messaging engine stops or fails.
Messages may be discarded when a messaging engine fails.
Messages are not discarded.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable.
Messages are discarded when a messaging engine stops or fails.
Messages may be discarded when a messaging engine fails.
Messages are not discarded.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable.
Messages are discarded when a messaging engine stops or fails.
Messages may be discarded when a messaging engine fails.
Messages are not discarded.
If a message cannot be delivered, it is discarded.
Use the delivery option configured for the bus destination.
Use the delivery option configured for the bus destination.
This context has a boolean information type.
This context has a byte information type.
This context has a character information type.
This context has a double information type.
This context has a floating point information type.
This context has an integer information type.
This context has a long information type.
This context has a short information type.
This context has a string information type.
The alias destination uses (inherits) the value of the corresponding property on the target destination.
The alias destination uses the delivery option value specified by producers.
The alias destination uses the delivery option value specified by the Reliability property of the destination.
Producers can send messages to this destination.
Producers cannot send messages to this destination.
Consumers can get messages from this destination.
Consumers cannot get messages from this destination.
When the associated messaging engine is started, the gateway link is in a stopped state and cannot process any new requests for connections.
When the associated messaging engine is started, the gateway link is in a started state and can process any new requests for connections.
The gateway link is in a stopped state and cannot process any new requests for connections.
The gateway link is ready and enabled for connections.
The gateway link is not active.
The gateway link is active, processing messages for connections.
When the associated messaging engine is started, the WebSphere MQ client link is in a stopped state and cannot process any new requests for inbound connections from clients.
When the associated messaging engine is started, the WebSphere MQ client link is ready and enabled to receive inbound connections.
The WebSphere MQ client link is ready and enabled to receive inbound connections from clients, but no client connections have yet been established.
The WebSphere MQ client link is in a stopped state and cannot process any new requests for inbound connections from clients.
The WebSphere MQ client link has received an inbound connection from a client, and is in the process of starting this connection.
The WebSphere MQ client link is performing channel negotiation and is not yet ready to transfer messages.
The WebSphere MQ client link has an active session with a client, and data can be flowing between the client and the WebSphere MQ client link.
The WebSphere MQ client link, or a connection with that link, is in the process of being stopped.
The WebSphere MQ client link has established sessions with several clients, and the sessions can be in different states: Starting, Running Stopping, or Stopped.
The WebSphere MQ link is ready and enabled to create connections, but no connections have yet been established.
The WebSphere MQ link has received a connection request, and is in the process of starting this connection.
The WebSphere MQ link is performing channel negotiation and is not yet ready to transfer messages.
The WebSphere MQ link is initializing the session for a connection and is not yet ready to transfer messages.
The WebSphere MQ link is retrying a failed connection.
The channel is being used for standby purposes. Messages can be transferred only when the channel is active.
The WebSphere MQ link has an active session with WebSphere MQ, and data can be flowing between WebSphere MQ and the WebSphere MQ link.
The WebSphere MQ link, or a connection with that link, is in the process of being stopped.
The channel is waiting for the message-retry interval to finish.
The WebSphere MQ link is in a stopped state and cannot process any new requests for connections.
The WebSphere MQ link has established several sessions with WebSphere MQ, and the sessions can be in different states: Starting, Running, Stopping, or Stopped.
Nonpersistent messages can be lost if there is a transmission failure or if the channel stops when the messages are in transit.
Nonpersistent messages are not lost if there is a transmission failure or if the channel stops when the messages are in transit.
When the associated messaging engine is started, the WebSphere MQ link is started automatically and is enabled for communication with the WebSphere MQ network.
When the associated messaging engine is started, the WebSphere MQ link is in a stopped state and cannot communicate with the WebSphere MQ network.
The channel is in doubt about which messages have been committed by WebSphere MQ for the unit
of work that it has sent.
The channel is not in doubt about which messages have been committed by WebSphere MQ.
The name of the WebSphere MQ queue manager from which the message batch was received.
The name of the WebSphere MQ sender channel from which the message batch was received.
The last unit of work identifier for the message batch.
The last sequence number for the message batch.
When the associated messaging engine is started, the mediation is started and is available to process messages.
When the associated messaging engine is started, the mediation is stopped and is not available to process messages.
The mediation is waiting to start. This could be because the application server is not yet open for e-business, or because a previous instance of the mediation has not yet been deleted.
The mediation is started and is available to process messages.
The mediation is in the process of stopping.
The mediation is stopped. The reason why the mediation is stopped is shown in the Reason attribute.
The mediation is in the process of being deleted.
The message is locked.
The message is unlocked.
The message state is in doubt.
The message is waiting to be consumed.
When the associated application server is started, the messaging engine is started and is available to process messages.
When the associated application server is started, the messaging engine is stopped and is not available to process messages.
Persistent messages are received and re-published.
The mapping is used for publishing messages both from WebSphere Application Server to a WebSphere MQ network and from a WebSphere MQ network to WebSphere Application Server.
The mapping is used for publishing messages from WebSphere Application Server to a WebSphere MQ network.
The mapping is used for publishing messages from a WebSphere MQ network to WebSphere Application Server.
Inherit the value set on the Publish/subscribe broker profile.
Persistent messages are received and re-published.
Nonpersistent messages are received and re-published.
Collection certificate store
Encryption information
Key information
Key locators
Login binding
Login mappings
Description
Property
Name
Required
Validation Expression
Value
Web services security namespace
Web services security namespace
Custom properties
Signing information
Token consumers
Token generators
Trust anchors
Trusted ID evaluators
Export WSDL
Use defaults
Properties
Specifies a list of untrusted, intermediate certificate files. This collection certificate store is used for certificate path validation of incoming X.509-formatted security tokens. The root trusted certificates are specified in the Trust anchors panel.
Specifies the configuration for the XML encryption and decryption parameters. If the data and key encryption algorithms are specified, the application server only accepts elements encrypted with those algorithms.
Specifies the parameters for the token consumer. The information is used on the consumer side only to process the security token. Because you can plug-in a custom token consumer, you must specify a Java class name.
Specifies a list of key locator configurations that retrieve the key for signature and encryption. You can customize a key locator class to retrieve keys from other types of repositories. The default implementation retrieves keys from a key store.
Specifies the configuration that is used for sending the security tokens within the messages.
Specifies a list of configurations for validating security tokens within incoming messages.
Custom properties for the type of service integration resource. Type the name and value of any custom properties that you need.
An optional description of the custom property.
The name of the custom property.
Whether or not the custom property is required for processing to continue.
An expression that is used to validate the value specified for the custom property.
The value of the custom property.
Specifies the namespace used by Web services security to send a request. However, this field configures the namespace value only and does not enforce the semantics of the specification related to the namespace. Web services security uses the processing semantic only in draft 13 of the OASIS specification.
Specifies the namespace used by Web services security to send a request. However, this field configures the namespace value only and does not enforce the semantics of the specification related to the namespace. Web services security uses the processing semantic only in draft 13 of the OASIS specification.
Extra properties of the service.
The status of the WSDL published to a UDDI registry.
Specifies the configuration for the signing parameters.
Specifies the parameters for the token consumer. The information is used on the consumer side only to process the security token. Because you can plug-in a custom token consumer, you must specify a Java class name.
Specifies the parameters for the token generator. The information is used on the generator side only to generate the security token. Because you can plug-in a custom token generator, you must specify a Java class name.
Specifies a list of key store configurations that contain root-trusted certificates. These configurations are used for certificate path validation of the incoming X.509-formatted security tokens. You must create the key store using the key tool utility. Do not use the key management utility because it does not create a key store with the expected format.
Specifies a list of trusted identity (ID) evaluators that determine whether the identity-asserting authority is trusted. You can use trusted ID evaluators for backward compatibility with Version 5 applications. However, it is recommended that you use a login module instead.
The integrity constraint is ignored.
The required integrity constraint is observed, but both messages that meet or do not meet the required integrity constraint are accepted.
Both messages that meet or do not meet the required integrity constraint are accepted.
Both messages that meet or do not meet the required integrity constraint are rejected.
The required integrity constraint must be met by the incoming message.
Select this option to export WSDL.
Specifies whether to use the default binding information. When this option is enabled, Web services security uses the default binding information instead of the custom binding information defined here.
Specifies additional properties for the configuration.
REQUIRED
REQUIRED
REQUIRED
The topics on which the subscription is registered.
Messages are not discarded.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable.
Messages are discarded when a messaging engine stops or fails.
Messages may be discarded when a messaging engine fails.
Link to configure WebSphere Application Server global security settings.
Record all trace levels.
View the outbound topics for this publication point.
[Collection]
[Settings]
Buttons
Text
Check box
Check box
Radio button
Text area
Text
Text
Selection list
Selection list
Custom
Custom
Range
Required
Data type
Default
Yes
No
Integer
Password
Check for updates to this topic
online
Links marked (online) require access to the Internet. Each link launches a search for the topic in the online information center. When search results are listed, select the topic that corresponds best to your configuration.
Extra button strings
Delete
Add
Remove
New
Start
Stop
Reset
Cancel the selected message retrieval request and make any message that is allocated to the request available to other application requests.
Cancel the selected message retrieval request and delete any message that is allocated to the request.Move
Delete
New
View
New
New
Add >>
<< Remove
Down
Up
To view this pane in the administrative console, click
To browse the properties of a listed item, select its name in the list.
To browse or change the properties of a listed item, select its name in the list.
To act on one or more of the listed items, select the check boxes next to the names of the items that you want to act on, then use the buttons provided.
To change what entries are listed, or to change what information is shown for entries in the list, use the Filter settings.
To create a new item, click New.
To add a server or cluster as a new member of the bus, click Add.
Configuration tab
Configuration properties for this object. These property values are preserved even if the runtime environment is stopped then restarted. See the information center task descriptions for information about how to apply configuration changes to the runtime environment.
Runtime tab
Runtime properties for this object. These properties directly affect the current runtime environment, but are not preserved when that environment is stopped. To preserve runtime property values, change the equivalent property values on the Configuration tab. See the information center task descriptions for information about how to apply configuration changes to the runtime environment.
Runtime properties for this object.
Topology tab
Topology properties for this object. These properties detail how this object relates to other objects in the system topology.
General properties
General properties
Additional properties
General properties
General properties
one of the paths shown in the table Paths to this panel
server_name
cluster_name
server_name
cluster_name server_name
cluster_name server_name bus_member_name
bus_name
bus_name
bus_name
bus_name
bus_name
bus_name
bus_name
bus_name
bus_name
bus_name
bus_name
bus_name
bus_name
bus_name
bus_name
bus_name
bus_name
bus_name destination_name bus_name destination_name
bus_name destination_name bus_name destination_name
bus_name destination_name message_point_name
bus_name queue_name
bus_name queue_name
bus_name queue_name queue_point_name
bus_name
topicspace_name
bus_name
topicspace_name
bus_name
topicspace_name publication_point_name
bus_name
topicspace_name publication_point_name
bus_name mediation_name
bus_name mediation_point_name
bus_name
bus_name port_name
bus_name webservice_name
bus_name link_name
bus_name link_name
bus_name link_name channel_name
bus_name link_name channel_name bus_name link_name
bus_name link_name channel_name
bus_name link_name channel_name
bus_name link_name channel_name channel_name
bus_name link_name channel_name bus_name link_name
bus_name link_name profile_name
bus_name link_name
bus_name link_name profile_name
bus_name link_name profile_name
bus_name link_name profile_name mapping_name
bus_name link_name profile_name mapping_name
bus_name link_name
bus_name
bus_name bus_name
bus_name member_name
bus_name link_name
bus_name link_name property_name
bus_name link_name
bus_name link_name connection_name
bus_name bus_name
bus_name bus_name
bus_name bus_name
bus_name bus_name
bus_name bus_name
bus_name bus_name
bus_name bus_name
one of the paths shown in the table Paths to this panel
bus_name bus_name
bus_name mediation_name
bus_name destination_name
one of the paths shown in the table Paths to this panel
bus_name
bus_name property_name
bus_name property_name
. Then, in the Name column, click the link labelled "Default messaging provider" for the JMS provider that you want to work with.
server_name chain_name
bus_name
one of the paths shown in the table Paths to this panel
bus_name queue_name queue_point_name
bus_name mediation_point_name
bus_name queue_name queue_point_name message_name
bus_name queue_name queue_point_name message_name
bus_name queue_name queue_point_name message_name
bus_name queue_name queue_point_name message_name
bus_name link_name profile_name
bus_name link_name
bus_name link_name profile_name
bus_name
bus_name
bus_name queue_name
bus_name
topicspace_name
bus_name
topicspace_name publication_point_name
bus_name
topicspace_name publication_point_name subscription_name
bus_name link_name profile_name
bus_name link_name profile_name
bus_name link_name profile_name map_entry_name
bus_name bus_name link_name
bus_name bus_name link_name
server_name chain_name
General properties
bus_name
bus_name identifier_name
bus_name identifier_name messaging_engine bus_name identifier_name
bus_name identifier_name subscription_name
bus_name identifier_name
bus_name identifier_name messaging_engine_name bus_name
bus_name identifier_name
bus_name
bus_name identifier_name bus_name identifier_name bus_name identifier_name
bus_name identifier_name messaging_engine
bus_name identifier_name
bus_name identifier_name
bus_name identifier_name
bus_name link_name
bus_name
bus_name identifier_name
bus_name identifier_name
bus_name identifier_name subscription_name
bus_name identifier_name
bus_name identifier_name
bus_name
bus_name mediation_name
bus_name
bus_name mediation_name
bus_name
bus_name
bus_name
bus_name
bus_name
bus_name
bus_name
bus_name
bus_name
bus_name
one of the paths shown in the table Paths to this panel
server_name
cluster_name
server_name listener_name
server_name listener_name
server_name listener_name connection-property_name
handler_name
handler-list_name
handler_name
handler_name header_name
handler_name
handler_name role_name
UDDI-reference_name
bus_name
bus_name service_name
bus_name
bus_name service_name
bus_name
bus_name instance_name
bus_name instance_name
bus_name instance_name service_name
bus_name instance_name
bus_name instance_name service_name
bus_name instance_name service_name
bus_name instance_name service_name target-service_name
bus_name instance_name
bus_name instance_name listener_name
bus_name service_name
bus_name service_name port_name
bus_name instance_name
bus_name instance_name port_name
bus_name service_name
bus_name service_name
bus_name service_name publication_name
bus_name service_name
bus_name service_name port_name
one of the paths shown in the table Paths to this panel
handler_name
bus_name service_name
bus_name service_name
bus_name service_name port_name
bus_name service_name port_name
one of several paths; for example bus_name service_name
request-consumer-binding_name
request-generator-binding_name
response-consumer-binding_name
response-generator-binding_name
request-receiver-binding_name
request-sender-binding_name
response-receiver-binding_name
response-sender-binding_name
v1-inbound-config_name
v1-inbound-config_name required-integrity_name
v1-inbound-config_name
v1-inbound-config_name required-confidentiality_name
v1-inbound-config_name
v1-inbound-config_name required-security-token_name
v1-inbound-config_name
v1-inbound-config_name caller_name
v1-inbound-config_name caller_name
v1-inbound-config_name
v1-inbound-config_name
v1-inbound-config_name property_name
v1-inbound-config_name
v1-inbound-config_name
v1-inbound-config_name integrity_name
v1-inbound-config_name
v1-inbound-config_name confidentiality_name
v1-inbound-config_name
v1-inbound-config_name security-token_name
v1-inbound-config_name
v1-inbound-config_name
v1-inbound-config_name property_name
v1-outbound-config_name
v1-outbound-config_name
v1-outbound-config_name integrity_name
v1-outbound-config_name
v1-outbound-config_name confidentiality_name
v1-outbound-config_name
v1-outbound-config_name security-token_name
v1-outbound-config_name
v1-outbound-config_name
v1-outbound-config_name property_name
v1-outbound-config_name
v1-outbound-config_name integrity_name
v1-outbound-config_name
v1-outbound-config_name confidentiality_name
v1-outbound-config_name
v1-outbound-config_name security-token_name
v1-outbound-config_name
v1-outbound-config_name caller_name
v1-outbound-config_name caller_name
v1-outbound-config_name
v1-outbound-config_name
v1-outbound-config_name property_name
one of the paths shown in the table Paths to this panel
draft13-inbound-config_name
draft13-outbound-config_name
one of the paths shown in the table Paths to this panel
draft13-inbound-config_name
draft13-outbound-config_name
draft13-inbound-config_name
draft13-inbound-config_name
draft13-inbound-config_name method_name
draft13-outbound-config_name
one of the paths shown in the table Paths to this panel
draft13-inbound-config_name
draft13-outbound-config_name
one of the paths shown in the table Paths to this panel
draft13-inbound-config_name
draft13-outbound-config_name
one of the paths shown in the table Paths to this panel
draft13-inbound-config_name
draft13-outbound-config_name
one of the paths shown in the table Paths to this panel
draft13-inbound-config_name
draft13-outbound-config_name
one of the paths shown in the table Paths to this panel
draft13-inbound-config_name
draft13-outbound-config_name
one of the paths shown in the table Paths to this panel
draft13-inbound-config_name
draft13-outbound-config_name
one of the paths shown in the table Paths to this panel
draft13-inbound-config_name
draft13-inbound-config_name
draft13-outbound-config_name
draft13-outbound-config_name
one of the paths shown in the table Paths to this panel
draft13-inbound-config_name
draft13-inbound-config_name
draft13-outbound-config_name
draft13-outbound-config_name
v1-inbound-config_name
v1-outbound-config_name
draft13-inbound-config_name
draft13-outbound-config_name
one of the paths shown in the table Paths to this panel
v1-inbound-config_name required-integrity_name
v1-outbound-config_name integrity_name
v1-inbound-config_name required-confidentiality_name
v1-outbound-config_name confidentiality_name
one of the paths shown in the table Paths to this panel
v1-inbound-config_name required-integrity_name message-part_name
v1-outbound-config_name integrity_name message-part_name
v1-inbound-config_name required-confidentiality_name message-part_name
v1-outbound-config_name confidentiality_name message-part_name
one of the paths shown in the table Paths to this panel
v1-inbound-config_name required-integrity_name
v1-outbound-config_name integrity_name
v1-inbound-config_name required-confidentiality_name
v1-outbound-config_name confidentiality_name
one of the paths shown in the table Paths to this panel
v1-inbound-config_name required-integrity_name nonce_name
v1-outbound-config_name integrity_name nonce_name
v1-inbound-config_name required-confidentiality_name nonce_name
v1-outbound-config_name confidentiality_name nonce_name
one of the paths shown in the table Paths to this panel
v1-inbound-config_name required-integrity_name
v1-outbound-config_name integrity_name
v1-inbound-config_name required-confidentiality_name
v1-outbound-config_name confidentiality_name
one of the paths shown in the table Paths to this panel
v1-inbound-config_name required-integrity_name timestamp_name
v1-outbound-config_name integrity_name timestamp_name
v1-inbound-config_name required-confidentiality_name timestamp_name
v1-outbound-config_name confidentiality_name timestamp_name
one of several paths; for example v1-outbound-config_name caller_name
one of several paths; for example v1-outbound-config_name caller_name property_name
one of the paths shown in the table Paths to this panel
v1-inbound-config_name
v1-outbound-config_name
v1-outbound-config_name
v1-inbound-config_name
one of the paths shown in the table Paths to this panel
v1-inbound-config_name property_name
v1-outbound-config_name property_name
v1-outbound-config_name property_name
v1-inbound-config_name property_name
one of the paths shown in the table Paths to this panel
bus_name
one of the paths shown in the table Paths to this panel
service_name
bus_name service_name
one of the paths shown in the table Paths to this panel
one of the paths shown in the table Paths to this panel
service_name
bus_name service_name
one of the paths shown in the table Paths to this panel
service_name
bus_name service_name
one of the paths shown in the table Paths to this panel
service_name point_name
bus_name service_name point_name
one of the paths shown in the table Paths to this panel
service_name point_name
bus_name service_name point_name
one of the paths shown in the table Paths to this panel
service_name point_name subscriber_name
bus_name service_name point_name subscriber_name
one of the paths shown in the table Paths to this panel
service_name point_name
bus_name service_name point_name
service_name
bus_name service_name
one of the paths shown in the table Paths to this panel
one of the paths shown in the table Paths to this panel
service_name point_name
bus_name service_name point_name
service_name
bus_name service_name
one of the paths shown in the table Paths to this panel
service_name point_name
bus_name service_name point_name
service_name
bus_name service_name
one of the paths shown in the table Paths to this panel
service_name point_name
bus_name service_name point_name
one of the paths shown in the table Paths to this panel
service_name
bus_name service_name
one of the paths shown in the table Paths to this panel
service_name namespace_name
bus_name service_name namespace_name
one of the paths shown in the table Paths to this panel
service_name namespace_name
bus_name service_name namespace_name
one of the paths shown in the table Paths to this panel
service_name namespace_name name
bus_name service_name namespace_name name
one of the paths shown in the table Paths to this panel
service_name namespace_name name
bus_name service_name namespace_name name
The scope displayed is for information only, and cannot be changed on this panel. If you want to browse or change this resource (or other resources) at a different scope, change the scope on the messaging provider settings panel, then click Apply, before clicking the link for the type of resource.
As a convention, use a JNDI name of the form jms/Name, where Name is the logical name of the resource. For more information about the use of JNDI and its syntax, see JNDI support in WebSphere Application Server in the WebSphere Application Server information center.
This property provides a list of the J2C authentication data entry aliases that have been defined to WebSphere Application Server. You can select a data entry alias to be used to authenticate the creation of a new connection to the JMS provider.
If you have enabled WebSphere Application Server global security, select the alias that specifies the user ID and password used to authenticate the creation of a new connection to the JMS provider. The use of this alias depends on the resource authentication (res-auth) setting declared in the connection factory resource reference of an application component's deployment descriptors.
The DefaultPrincipalMapping JAAS configuration is used by Java 2 Connectors to map users to principals that are defined in the J2C Authentication Data Entries. You can define and use other mapping configurations.
The bus looks for a suitable messaging engine in the same application server as the bootstrap messaging engine. If a suitable messaging engine is found, it is used. If a suitable messaging engine is not found, the bus fails the connection request.
The bus performs the Server-based check. If a suitable messaging engine is not found, the bus looks for a suitable messaging engine on the same host as the bootstrap messaging engine. If a suitable messaging engine is found, it is used. If a suitable messaging engine is not found, the bus fails the connection request.
The bus performs the Host-based check. If a suitable messaging engine is not found, the bus looks for a suitable messaging engine in the same custom group as the bootstrap messaging engine. If a suitable messaging engine is found, it is used. If a suitable messaging engine is not found, the bus fails the connection request.
The bus performs the Group-based check. If a suitable messaging engine is not found, the bus looks for a suitable messaging engine anywhere on the bus. If a suitable messaging engine is found, it is used. If a suitable messaging engine is not found, the bus fails the connection request.
Select this property to log connections being created without a transaction context.
The preferred way to assign a client identifier is for it to be configured on the connection factory and transparently assigned to connections that the factory creates. Alternatively, an application can set the client identifier immediately after creating the connection.
For more information about the use of client identifiers, see the "Client identifiers" section of the JMS Specification.
You can override this property for individual JMS destinations by setting the Read ahead property on the JMS destination.
You may not want to select this option if you have multiple clients attempting to receive from the same destination, because it can adversely affect message processing. For example, you allocate five messages to client A, but client A takes a long time processing the first of those messages. Meanwhile client B is available, but doing nothing, and could have been helping out with the other four messages. So, the "Default" behavior is to only have it on when there can only be one client (that is, for nondurable subscriptions and durable subscriptions in a non-clustered environment). However, if you are using a queue but you know that there is only ever one client attached to that queue at any one time, you could override the default behavior by selecting this option.
This property overrides the value set by the Read ahead property on the JMS connection factory.
The default for this property is null, which causes temporary queues to be named without any prefix.
_T<topic_prefix>_<messaging_engine_id><destination_id>
If the topic is to be used with WebSphere MQ, the topic prefix value should be a maximum of 12 characters.
The default for this property is null, which causes temporary topics to be named without any prefix.
This indicates the name of a target that is to be used to determine one or messaging engines to handle work. The type of target is indicated by the Target type property
Connections are load balanced across the available messaging engines that satisfy the selection criteria.
If want applications to be able to connect to any messaging engine in the bus, do not set this property.
For more information about using this property with other connection factory properties for workload management of connections, see Administrative properties for JMS connections to a bus.
If the selected messaging engine is in the same server as the application, a direct in-process connection is made and this transport chain property is ignored.
The transport chains represent network protocol stacks operating within a server. The name you specify must be one of the transport chains available in the server that hosts the messaging engine, as listed on the server_name panel. The following transport chains are provided, but you can define your own transport chains on that panel.
For more information about using this property with other connection factory properties for workload management of connections, see Administrative properties for JMS connections to a bus.
For more information about using this property with other connection factory properties for workload management of connections, see Administrative properties for JMS connections to a bus.
To specify endpoint addresses, type a comma-separated list of endpoint triplets, each of the form host_name:port_number:chain_name where:
[2002:914:fc12:179:9:20:141:42]:7276:BootstrapBasicMessagingIf host_name is not specified, the default is localhost.
localhost:7276:BootstrapBasicMessaging
[ [host_name] [ ":" [ port_number] [ ":" chain_name] ] ]Specifying host_name : chain_name instead of host_name : : chain_name (with two colons) is incorrect. It is valid to enter nothing, or to enter any of the following: "a, "a:", ":7276", "::chain", and so on. The default value applies if you do not specify a value, but you must separate the fields with ":"s.
You can create other transport chains and specify them as part of the provider endpoints.
For an application running in an application server, this property defines how close messaging engines must be to the application server. For an application running outside an application server, this property defines how close messaging engines must be to the bootstrap server.
When searching for the most suitable messaging engine a closer messaging engine is always selected ahead of a more remote messaging engine.
Use this property to define what happens to any messages that cannot be delivered to this destination. By default, such messages are routed to the system default exception destination of the messaging engine that discovers the problem; _SYSTEM.Exception.Destination.engine_name.
If you want to messages to be sent to another exception destination, select Specify then type its name on this property. The exception destination must be a queue, on the same bus or a foreign bus, and must exist when the destination is created.
If you do not want undeliverable messages to be routed to an exception destination, select None.
If the message contains the discriminator text string, then the message is not processed by the mediation.
You should base the content of the discriminator text string on an understanding of which messages the mediation should process.
The format of the discriminator matches the topic discriminator specification.
If the message does not match the rule defined by the selector text string, then the message is not mediated.
You should base the content of the selector text string on an understanding of which messages the mediation should process.
The format of the selector string is the same as for JMS selector strings.
For non-transactional JMS message-driven beans and MessageListeners that use a JMS destination configured on the default messaging provider, best-effort nonpersistent messages are not recoverable. In this case, if a message is unlocked because the message-driven bean or MessageListener threw an exception, then the message is not redelivered or sent to the exception destination because it was deleted from the message store when it was passed to the listener. If you require higher message reliability for non-transactional JMS message-driven beans and MessageListeners, configure a different option for the Maximum reliability property of the bus destination.
You only need to modify this property if you have client applications running outside of an application server, or applications on a server in another cell, that want to use this connection factory to connect to the target service integration bus specified on the connection factory.
To use JMS destinations of the default messaging provider, an application connects to a messaging engine on the target service integration bus to which the destinations are assigned. For example, a JMS queue is assigned to a queue destination on a service integration bus.
Client applications running outside of an application server - for example, running in a client container or outside the WebSphere Application Server environment - cannot locate directly a suitable messaging engine to connect to in the target bus. Similarly, an application running on a server in one cell to connect to a target bus in another cell cannot locate directly a suitable messaging engine to connect to in the target bus.
In these scenarios, the clients (or servers in another bus) must complete a bootstrap process through a bootstrap server that is a member of the target bus. A bootstrap server is an application server running the SIB Service, but does not need to be running any messaging engines. The bootstrap server selects a messaging engine that is running in an application server that supports the desired target transport chain. For the bootstrap process to be possible, you must configure one or more provider end points in the connection factory used by the client.
A bootstrap server uses a specific port and bootstrap transport chain. The port is the SIB_ENDPOINT_ADDRESS (or SIB_ENDPOINT_SECURE_ADDRESS if security is enabled), of the messaging engine hosting the remote end of the link. Together with host name, these form the endpoint address of the bootstrap server.
The properties of a JMS connection factory used by an application control the selection of a suitable messaging engine and how the application connects to the selected messaging engine. By default, a connection factory tries to use a bootstrap server that has an endpoint address of localhost:7276:BootstrapBasicMessaging. That is, by default, applications try to use a bootstrap server on the same host as the client, and using port 7276 and the predefined bootstrap transport chain called BootstrapBasicMessaging.
If you want an application to use a bootstrap server with a different endpoint address, you need to specify the required endpoint address on the Provider endpoints property of the JMS connection factories that the client application uses. You can specify one or more endpoint addresses of bootstrap servers.
The endpoint addresses for bootstrap servers must be specified in every JMS connection factory that is used by applications outside of an application server. To avoid having to specify a long list of bootstrap servers, you can provide a few highly-available servers as dedicated bootstrap servers. Then you only need to specify a short list of bootstrap servers on each connection factory.
boothost1:7278:BootstrapBasicMessaging or boothost1:7278and for a server assigned secure port 7289, on host boothost2, and using the predefined transport chain BootstrapTunneledSecureMessaging:
boothost2:7289:BootstrapTunneledSecureMessaging
[ [host_name] [ ":" [port_number] [ ":" chain_name] ] ]where:
[2002:914:fc12:179:9:20:141:42]:7276:BootstrapBasicMessaging. If a value is not specified, the default is localhost.
If port_number is not specified, the default is 7276.
The following predefined bootstrap transport chains are provided:
Specifying host_name : chain_name instead of host_name : : chain_name (with two colons) is incorrect. It is valid to enter nothing, or to enter any of the following: "a, "a:", ":7276", "::chain", and so on. The default value applies if you do not specify a value, but you must separate the fields with ":"s.
boothost1:7278:BootstrapBasicMessaging, boothost2:7289:BootstrapTunneledSecureMessaging, [2002:914:fc12:179:9:20:141:42]:7276:BootstrapBasicMessaging