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

Common help terms (text entities)

Ui strings not in plugin.nlsprops or fielddesc.dita files:

Security for bus {0}

General properties
General properties
Additional properties
General properties
General properties
Related Items

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.
Allows sharing of durable subscriptions when connections are made from within a server cluster.
Durable subscriptions can be shared across connections.
Durable subscriptions are never shared across connections.
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.
Click this button to cancel all subscriptions.
The mapping is used for publishing messages both from WebSphere Application Server to a WebSphere MQ network and from a WebSphere MQ network to WebSphere Application Server.
The mapping is used for publishing messages from WebSphere Application Server to a WebSphere MQ network.
The mapping is used for publishing messages from a WebSphere MQ network to WebSphere Application Server.
Inherit the value set on the Publish/subscribe broker profile.
Persistent messages are received and re-published.
Nonpersistent messages are received and re-published.

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.
Click this button to create a new endpoint listener.
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.
Click this button to create a new inbound service.
Click this button to reload the template WSDL for this inbound service.
Click this button to remove the inbound service from the UDDI registry.
New
Click this button to create a new outbound port.
Click this button to create a new outbound service.
Click this button to refresh the details displayed with data from the WSDL file.
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.
Clear all messages from this message 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

Extra button strings

Clicks this button to test the connection to WebSphere MQ.
Delete
Click this button to delete the selected items.
Click this button to delete the object displayed.
Click this button to delete all items in the list.
Click this button to refresh the list of items.

Add
Click this button to add a new member (a server or cluster) to the bus.
Remove
Click this button to remove a member (a server or cluster) from the bus.
New
Click this button to create a new administrative object of this type.
Start
Click this button to start selected items.
Stop
Click this button to stop selected items.
Click this button to commit the logical unit-of-work for the message batch.
Click this button to roll back the logical unit-of-work for the message batch.
Click this button to apply a mediation to a destination, to modify the destination handling of messages.
Click this button to remove a mediation from the destination, to remove the effect of the mediation from the destination handling of messages.
Reset
Click this button to reset a selected channel sequence number to 1. If the channel is running, the reset request will take effect only when the channel has been stopped and restarted.
Click this button to start mediating messages at this mediation point.
Click this button to stop mediating messages at this mediation point.
Click this button to add a new messaging engine to the server cluster.
Click this button to remove the selected messaging engines from the server cluster.
Click this button to stop selected WebSphere MQ links.
Delete all messages from the outbound message stream of the selected remote queue point. Messages in 'Pending Acknowledgment' state may already have been received at the remote queue point. You cannot delete messages in 'Committing' state; you must first commit their transactions.
Move all messages from the outbound message stream of the selected remote queue point to the exception destination configured for the destination. Messages in 'Pending Acknowledgment' state may already have been received at the remote queue point. Moving these messages to the exception destination results in two copies of the message in the bus. You cannot move messages in 'Committing' state; you must first commit their transactions.
Cancel the selected message retrieval request and make any message that is allocated to the request available to other application requests.
Cancel the selected message retrieval request and delete any message that is allocated to the request.Move
Move the selected outbound messages to the exception destination configured for the destination. Messages in 'Pending Acknowledgment' state may already have been accepted to the remote queue point. Moving these messages to the exception destination results in two copies of the message in the bus. You cannot move messages in 'Committing' state; you must first commit their transaction.
Delete
Delete the selected outbound messages from the stream. Messages in 'Pending Acknowledgment' state may already have been accepted to the remote queue point. You cannot delete messages in 'Committing' state; you must first commit their transaction.
Click this button to create a new gateway service.
Click this button to create a new proxy service.
Click this button to create a new service of this object type.
New
Click this button to create a new service of this object type.
View
Click this button to view the destination for this service.
New
Click this button to create a new service of this object type.
New
Click this button to create a new inbound port.
Add    >>
Click this button to add a new JAXRPC handler to the list.
<< Remove
Click this button to remove a selected JAXRPC handler from the list.
Down
Click this button to move the selected JAXRPC handler up the list.
Up
Click this button to move the selected JAXRPC handler down the list.Click this button to create a new WS-Notification service.
Click this button to copy the service point.
Click this button to create a new service point.

Common administrative console path strings (text entities)

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.

Panel tabs:

Configuration tab
Configuration properties for this object. These property values are preserved even if the runtime environment is stopped then restarted. See the information center task descriptions for information about how to apply configuration changes to the runtime environment.
Runtime tab
Runtime properties for this object. These properties directly affect the current runtime environment, but are not preserved when that environment is stopped. To preserve runtime property values, change the equivalent property values on the Configuration tab. See the information center task descriptions for information about how to apply configuration changes to the runtime environment.
Runtime properties for this object.
Topology tab
Topology properties for this object. These properties detail how this object relates to other objects in the system topology.
General properties
General properties
Additional properties
General properties
General properties

Paths to panels:

one of the paths shown in the table Paths to this panelServers > Application servers
Servers > Application servers > [Content Pane] server_name
Servers > Clusters
Servers > Clusters > [Content Pane] cluster_name
Servers > Application servers > [Content Pane] server_name > [Server messaging] SIB service
Servers > Clusters > [Content Pane] cluster_name > [Additional Properties] Servers > [Content Pane] server_name > [Additional Properties] Messaging engines
Servers > Clusters > [Content Pane] cluster_name > [Additional Properties] Servers > [Content Pane] server_name > [Additional Properties] Messaging engines > [Content Pane] bus_member_name
Service integration > Buses
Service integration > Buses > [Content Pane] New
Service integration > Buses > [Content Pane] bus_name
Service integration > Buses > [Content Pane] bus_name > [Additional Properties] Custom properties
Service integration > Buses > [Content Pane] bus_name > [Topology] Bus members
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations
Service integration > Buses > [Content Pane] bus_name > [Topology] Foreign Buses
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Mediations
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines
Service integration > Buses > [Content Pane] bus_name > [Additional Properties] Custom properties
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > engine_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > engine_name > [Message store type] Configure
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > engine_name > [Message store type] Configure
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > engine_name > [Additional Properties] Message points
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > engine_name > [Additional Properties] service integration bus links
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > engine_name > [Additional Properties] Mediation points
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > engine_name > [Additional Properties] WebSphere MQ links
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > engine_name > [Additional Properties] WebSphere MQ client links
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > engine_name > [Additional Properties] Next hop buses

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

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

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

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

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

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

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

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

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

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

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

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

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

Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > engine_name > [Additional Properties] Custom properties
Service integration > Buses > [Content Pane] bus_name > [Additional Properties] Custom properties > [Content Pane] property_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > engine_name > [Additional Properties] Custom properties > [Content Pane] property_name
Resources > JMS > JMS providers.  Then, in the Name column, click the link labelled "Default messaging provider" for the JMS provider that you want to work with.
Resources > JMS > JMS providers > [Content Pane] default_messaging provider > [Additional Properties] Connection factories
Resources > JMS > JMS providers > [Content Pane] default_messaging provider > [Additional Properties] Connection factories > factory_name
Resources > JMS > JMS providers > [Content Pane] default_messaging provider > [Additional Properties] Queue connection factories
Resources > JMS > JMS providers > [Content Pane] default_messaging provider > [Additional Properties] Queue connection factories > factory_name
Resources > JMS > JMS providers > [Content Pane] default_messaging provider > [Additional Properties] Queues
Resources > JMS > JMS providers > [Content Pane] default_messaging provider > [Additional Properties] Queues > queue_name
Resources > JMS > JMS providers > [Content Pane] default_messaging provider > [Additional Properties] Topic connection factories
Resources > JMS > JMS providers > [Content Pane] default_messaging provider > [Additional Properties] Topic connection factories > factory_name
Resources > JMS > JMS providers > [Content Pane] default_messaging provider > [Additional Properties] Topics
Resources > JMS > JMS providers > [Content Pane] default_messaging provider > [Additional Properties] Topics > topic_name
Resources > JMS > JMS providers > [Content Pane] default_messaging provider > [Additional Properties] Activation specifications
Resources > JMS > JMS providers > [Content Pane] default_messaging provider > [Additional Properties] Activation specifications > activation_specification_name
Servers > Application servers > [Content Pane] server_name > [Server messaging] WebSphere MQ link inbound transports > [Content Pane] chain_name > MQFAP inbound channel
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > engine_name > [Additional Properties] Message points
one of the paths shown in the table Paths to this panel
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] queue_name > [Additional Properties] Queue points > [Content Pane] queue_point_name > Runtime > Messages
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > engine_name > [Additional Properties] Mediation points > [Content Pane] mediation_point_name > Runtime > Messages
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] queue_name > [Additional Properties] Queue points > [Content Pane] queue_point_name > Runtime > Messages > [Content Pane] message_name
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] queue_name > [Additional Properties] Queue points > [Content Pane] queue_point_name > Runtime > Messages > [Content Pane] message_name > Message body
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] queue_name > [Additional Properties] Queue points > [Content Pane] queue_point_name > Runtime > Messages > [Content Pane] message_name
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] queue_name > [Additional Properties] Queue points > [Content Pane] queue_point_name > Runtime > Messages > [Content Pane] message_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Publish/subscribe broker profiles > [Content Pane] profile_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Publish/subscribe broker profiles > New
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name > [Additional Properties] Publish/subscribe broker profiles > [Content Pane] profile_name > Runtime > Subscriptions
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > engine_name > [Additional Properties] Message points > Runtime
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > engine_name > [Additional Properties] Mediation points > Runtime
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] queue_name > [Additional Properties] Queue points > Runtime
Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane]
topicspace_name
> [Additional Properties]  Publication points
> Runtime

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

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

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

Service integration > Buses > [Content Pane] bus_name > Security
Service integration > Buses > [Content Pane] bus_name > Security > [Additional Properties] Permitted Transports
Service integration > Buses > [Content Pane] bus_name > Security > [Additional Properties] Permitted Transports > [Content Pane] member_name
Service integration > Buses > [Content Pane] bus_name > Security > [Additional Properties] Users and Groups in the Bus Connector Role
Service integration > Buses > [Content Pane] bus_name > Security > [Additional Properties] Users and Groups in the Bus Connector Role > [Content Pane] member_name
Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > engine_name > [Additional Properties] Mediation thread pool

sibusresources and sibuswsgw, paths to panels


one of the paths shown in the table Paths to this panel
Servers > Application servers > [Content Pane] server_name > Endpoint listeners
Servers > Clusters > [Content Pane] cluster_name > Endpoint listeners
Servers > Application servers > [Content Pane] server_name > Endpoint listeners > [Content Pane] listener_name

Servers > Application servers > [Content Pane] server_name > Endpoint listeners > [Content Pane] listener_name > Connection Properties
Servers > Application servers > [Content Pane] server_name > Endpoint listeners > [Content Pane] listener_name > Connection Properties > [Content Pane] connection-property_name





Service integration > Web services

Service integration > Web services > JAX-RPC handlers
Service integration > Web services > JAX-RPC handler lists
Service integration > Web services > JAX-RPC handlers > [Content Pane] handler_name
Service integration > Web services > JAX-RPC handler lists > [Content Pane] handler-list_name

Service integration > Web services > JAX-RPC handlers > [Content Pane] handler_name > JAX-RPC headers
Service integration > Web services > JAX-RPC handlers > [Content Pane] handler_name > JAX-RPC headers > [Content Pane] header_name

Service integration > Web services > JAX-RPC handlers > [Content Pane] handler_name > SOAP roles
Service integration > Web services > JAX-RPC handlers > [Content Pane] handler_name > SOAP roles > [Content Pane] role_name


Service integration > Web services > UDDI references
Service integration > Web services > UDDI references > [Content Pane] UDDI-reference_name


Service integration > Buses > [Content Pane] bus_name > [Services] Inbound Services
Service integration > Buses > [Content Pane] bus_name > [Services] Inbound Services > [Content Pane] service_name

Service integration > Buses > [Content Pane] bus_name > [Services] Outbound Services
Service integration > Buses > [Content Pane] bus_name > [Services] Outbound Services > [Content Pane] service_name

Service integration > Buses > [Content Pane] bus_name > [Services] Web service gateway instances

Service integration > Buses > [Content Pane] bus_name > [Services] Web service gateway instances > [Content Pane] instance_name
Service integration > Buses > [Content Pane] bus_name > [Services] Web service gateway instances > [Content Pane] instance_name > Gateway Services
Service integration > Buses > [Content Pane] bus_name > [Services] Web service gateway instances > [Content Pane] instance_name > Gateway Services > [Content Pane] service_name
Service integration > Buses > [Content Pane] bus_name > [Services] Web service gateway instances > [Content Pane] instance_name > Proxy Services
Service integration > Buses > [Content Pane] bus_name > [Services] Web service gateway instances > [Content Pane] instance_name > Proxy Services > [Content Pane] service_name
Service integration > Buses > [Content Pane] bus_name > [Services] Web service gateway instances > [Content Pane] instance_name > Gateway Services > [Content Pane] service_name > Target Services
Service integration > Buses > [Content Pane] bus_name > [Services] Web service gateway instances > [Content Pane] instance_name > Gateway Services > [Content Pane] service_name > Target Services > [Content Pane] target-service_name

Service integration > Buses > [Content Pane] bus_name > [Services] Web service gateway instances > [Content Pane] instance_name > Endpoint listeners
Service integration > Buses > [Content Pane] bus_name > [Services] Web service gateway instances > [Content Pane] instance_name > Endpoint listeners > [Content Pane] listener_name
Service integration > Buses > [Content Pane] bus_name > [Services] Inbound Services > [Content Pane] service_name > [Additional Properties] Inbound Ports
Service integration > Buses > [Content Pane] bus_name > [Services] Inbound Services > [Content Pane] service_name > [Additional Properties] Inbound Ports > [Content Pane] port_name
Service integration > Buses > [Content Pane] bus_name > [Services] Web service gateway instances > [Content Pane] instance_name > Inbound Ports
Service integration > Buses > [Content Pane] bus_name > [Services] Web service gateway instances > [Content Pane] instance_name > Inbound Ports > [Content Pane] port_name

Service integration > Buses > [Content Pane] bus_name > [Services] Inbound Services > [Content Pane] service_name > [Additional Properties] Publish WSDL files to ZIP file
Service integration > Buses > [Content Pane] bus_name > [Services] Inbound Services > [Content Pane] service_name > [Additional Properties] UDDI publication
Service integration > Buses > [Content Pane] bus_name > [Services] Inbound Services > [Content Pane] service_name > [Additional Properties] UDDI publication > [Content Pane] publication_name

Service integration > Buses > [Content Pane] bus_name > [Services] Outbound Services > [Content Pane] service_name > Outbound Ports
Service integration > Buses > [Content Pane] bus_name > [Services] Outbound Services > [Content Pane] service_name > Outbound Ports > [Content Pane] port_name




one of the paths shown in the table Paths to this panel
Service integration > Web services > JAX-RPC handlers > [Content Pane] handler_name > Custom properties
Service integration > Buses > [Content Pane] bus_name > [Services] Inbound Services > [Content Pane] service_name > Custom properties
Service integration > Buses > [Content Pane] bus_name > [Services] Outbound Services > [Content Pane] service_name > Custom Properties
Service integration > Buses > [Content Pane] bus_name > [Services] Outbound Services > [Content Pane] service_name > Outbound Ports > [Content Pane] port_name > Custom Properties
Service integration > Buses > [Content Pane] bus_name > [Services] Inbound Services > [Content Pane] service_name > [Additional Properties] Inbound Ports > [Content Pane] port_name > Custom Properties
one of several paths; for example Service integration > Buses > [Content Pane] bus_name > [Services] Inbound Services > [Content Pane] service_name > Custom properties



sibuswssecurity, paths to panels

Service integration > Web services > WS-Security bindings
Service integration > Web services > WS-Security bindings > [Content Pane] request-consumer-binding_name
Service integration > Web services > WS-Security bindings > [Content Pane] request-generator-binding_name
Service integration > Web services > WS-Security bindings > [Content Pane] response-consumer-binding_name
Service integration > Web services > WS-Security bindings > [Content Pane] response-generator-binding_name
Service integration > Web services > WS-Security bindings > [Content Pane] request-receiver-binding_name
Service integration > Web services > WS-Security bindings > [Content Pane] request-sender-binding_name
Service integration > Web services > WS-Security bindings > [Content Pane] response-receiver-binding_name
Service integration > Web services > WS-Security bindings > [Content Pane] response-sender-binding_name



Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Required integrity
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Required integrity > [Content Pane] required-integrity_name

Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Required Confidentiality
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Required Confidentiality > [Content Pane] required-confidentiality_name

Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Required Security Token
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Required Security Token > [Content Pane] required-security-token_name

Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Caller
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Caller > [Content Pane] caller_name

Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Caller > [Content Pane] caller_name > [Additional Properties] Trust method

Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Add timestamp

Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Properties
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Properties > [Content Pane] property_name


Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Response generator] Actor

Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Response generator] Integrity
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Response generator] Integrity > [Content Pane] integrity_name

Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Response generator] Confidentiality
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Response generator] Confidentiality > [Content Pane] confidentiality_name

Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Response generator] Security Token
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Response generator] Security Token > [Content Pane] security-token_name

Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Response generator] Add timestamp

Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Response generator] Properties
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Response generator] Properties > [Content Pane] property_name


Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Request generator] Actor

Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Request generator] Integrity
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Request generator] Integrity > [Content Pane] integrity_name

Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Request generator] Confidentiality
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Request generator] Confidentiality > [Content Pane] confidentiality_name

Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Request generator] Security Token
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Request generator] Security Token > [Content Pane] security-token_name

Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Request generator] Add timestamp

Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Request generator] Properties
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Request generator] Properties > [Content Pane] property_name


Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Required integrity
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Required integrity > [Content Pane] integrity_name

Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Required Confidentiality
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Required Confidentiality > [Content Pane] confidentiality_name

Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer]  Required Security Token
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer]  Required Security Token > [Content Pane] security-token_name

Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Caller
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Caller > [Content Pane] caller_name

Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Caller > [Content Pane] caller_name > [Additional Properties] Trust method

Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Add timestamp

Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Properties
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Properties > [Content Pane] property_name



one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-inbound-config_name > [Request receiver] Required integrity
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-outbound-config_name > [Response receiver] Required integrity

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-inbound-config_name > [Request receiver] Required confidentiality
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-outbound-config_name > [Response receiver] Required confidentiality

Service integration > Web services > WS-Security configurations > [Content Pane] draft13-inbound-config_name > [Request receiver] Login configuration

Service integration > Web services > WS-Security configurations > [Content Pane] draft13-inbound-config_name > [Request receiver] Login configuration > [Additional properties] Custom authentication methods
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-inbound-config_name > [Request receiver] Login configuration > [Additional properties] Custom authentication methods > [Content Pane] method_name

Service integration > Web services > WS-Security configurations > [Content Pane] draft13-outbound-config_name > [Request sender]  Login configuration

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-inbound-config_name > [Request receiver] ID assertion
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-outbound-config_name > [Request sender] ID assertion

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-inbound-config_name > [Request receiver] Add received timestamp
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-outbound-config_name > [Response receiver] Add received timestamp

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-inbound-config_name > [Response sender] Actor
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-outbound-config_name > [Request sender] Actor

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-inbound-config_name > [Response sender] Integrity
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-outbound-config_name > [Request sender] Integrity

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-inbound-config_name > [Response sender] Confidentiality
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-outbound-config_name > [Request sender] Confidentiality

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-inbound-config_name > [Response sender] Add created timestamp
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-outbound-config_name > [Request sender] Add created timestamp

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-inbound-config_name > [Request receiver] Properties
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-inbound-config_name > [Response sender] Properties
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-outbound-config_name > [Response receiver] Properties
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-outbound-config_name > [Request sender] Properties
one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-inbound-config_name > [Request receiver] Properties > [Additional Properties]  Properties
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-inbound-config_name > [Response sender] Properties > [Additional Properties]  Properties
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-outbound-config_name > [Response receiver] Properties > [Additional Properties]  Properties
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-outbound-config_name > [Request sender] Properties > [Additional Properties]  Properties


Service integration > Web services > WS-Security configurations
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-inbound-config_name
Service integration > Web services > WS-Security configurations > [Content Pane] draft13-outbound-config_name





one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Required integrity > [Content Pane] required-integrity_name > [Additional Properties] Message parts
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Required integrity > [Content Pane] integrity_name > [Additional Properties] Message parts
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Required Confidentiality > [Content Pane] required-confidentiality_name > [Additional Properties] Message parts
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Required Confidentiality > [Content Pane] confidentiality_name > [Additional Properties] Message parts

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Required integrity > [Content Pane] required-integrity_name > [Additional Properties] Message parts > [Content Pane] message-part_name
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Required integrity > [Content Pane] integrity_name > [Additional Properties] Message parts > [Content Pane] message-part_name
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Required Confidentiality > [Content Pane] required-confidentiality_name > [Additional Properties] Message parts > [Content Pane] message-part_name
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Required Confidentiality > [Content Pane] confidentiality_name > [Additional Properties] Message parts > [Content Pane] message-part_name

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Required integrity > [Content Pane] required-integrity_name > [Additional Properties] Nonce
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Required integrity > [Content Pane] integrity_name > [Additional Properties] Nonce
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Required Confidentiality > [Content Pane] required-confidentiality_name > [Additional Properties] Nonce
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Required Confidentiality > [Content Pane] confidentiality_name > [Additional Properties] Nonce

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Required integrity > [Content Pane] required-integrity_name > [Additional Properties] Nonce > [Content Pane] nonce_name
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Required integrity > [Content Pane] integrity_name > [Additional Properties] Nonce > [Content Pane] nonce_name
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Required Confidentiality > [Content Pane] required-confidentiality_name > [Additional Properties] Nonce > [Content Pane] nonce_name
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Required Confidentiality > [Content Pane] confidentiality_name > [Additional Properties] Nonce > [Content Pane] nonce_name

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Required integrity > [Content Pane] required-integrity_name > [Additional Properties] Timestamp
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Required integrity > [Content Pane] integrity_name > [Additional Properties] Timestamp
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Required Confidentiality > [Content Pane] required-confidentiality_name > [Additional Properties] Timestamp
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Required Confidentiality > [Content Pane] confidentiality_name > [Additional Properties] Timestamp

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Required integrity > [Content Pane] required-integrity_name > [Additional Properties] Timestamp > [Content Pane] timestamp_name
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Required integrity > [Content Pane] integrity_name > [Additional Properties] Timestamp > [Content Pane] timestamp_name
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Required Confidentiality > [Content Pane] required-confidentiality_name > [Additional Properties] Timestamp > [Content Pane] timestamp_name
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Required Confidentiality > [Content Pane] confidentiality_name > [Additional Properties] Timestamp > [Content Pane] timestamp_name

one of several paths; for example Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Caller > [Content Pane] caller_name > [Additional Properties] Properties
one of several paths; for example Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Caller > [Content Pane] caller_name > [Additional Properties] Properties > [Content Pane] property_name

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Add timestamp > [Additional Properties]  Properties
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Request generator] Add timestamp > [Additional Properties]  Properties
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Add timestamp > [Additional Properties]  Properties
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Response generator] Add timestamp > [Additional Properties]  Properties
one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Request consumer] Add timestamp > [Additional Properties]  Properties > [Content Pane] property_name
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Request generator] Add timestamp > [Additional Properties]  Properties > [Content Pane] property_name
Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config_name > [Response consumer] Add timestamp > [Additional Properties]  Properties > [Content Pane] property_name
Service integration > Web services > WS-Security configurations > [Content Pane] v1-inbound-config_name > [Response generator] Add timestamp > [Additional Properties]  Properties > [Content Pane] property_name

wsnresources, paths to panels:

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Notification services
Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Notification services > [Content Pane] service_name
Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services > [Content Pane] 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 integration > Web services > WS-Notification services > [Content Pane] service_name > [Related Items] Notification broker inbound service settings > [Additional Properties] Publish WSDL files to ZIP file
Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services > [Content Pane] service_name > [Related Items] Notification broker inbound service settings > [Additional Properties] Publish WSDL files to ZIP file

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Notification services > [Content Pane] service_name > WS-Notification service points
Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services > [Content Pane] service_name > WS-Notification service points

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Notification services > [Content Pane] service_name > WS-Notification service points > [Content Pane] point_name
Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services > [Content Pane] service_name > WS-Notification service points > [Content Pane] point_name

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Notification services > [Content Pane] service_name > WS-Notification service points > [Content Pane] point_name > Administered subscribers
Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services > [Content Pane] service_name > WS-Notification service points > [Content Pane] point_name > Administered subscribers

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Notification services > [Content Pane] service_name > WS-Notification service points > [Content Pane] point_name > Administered subscribers > [Content Pane] subscriber_name
Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services > [Content Pane] service_name > WS-Notification service points > [Content Pane] point_name > Administered subscribers > [Content Pane] subscriber_name

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Notification services > [Content Pane] service_name > WS-Notification service points > [Content Pane] point_name > Runtime > Subscriptions
Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services > [Content Pane] service_name > WS-Notification service points > [Content Pane] point_name > Runtime > Subscriptions
Service integration > Web services > WS-Notification services > [Content Pane] service_name > Runtime > Subscriptions
Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services > [Content Pane] service_name > Runtime > Subscriptions

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 integration > Web services > WS-Notification services > [Content Pane] service_name > WS-Notification service points > [Content Pane] point_name > Runtime > Publisher registrations
Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services > [Content Pane] service_name > WS-Notification service points > [Content Pane] point_name > Runtime > Publisher registrations
Service integration > Web services > WS-Notification services > [Content Pane] service_name > Runtime > Publisher registrations
Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services > [Content Pane] service_name > Runtime > Publisher registrations

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Notification services > [Content Pane] service_name > WS-Notification service points > [Content Pane] point_name > Runtime > Pull points
Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services > [Content Pane] service_name > WS-Notification service points > [Content Pane] point_name > Runtime > Pull points
Service integration > Web services > WS-Notification services > [Content Pane] service_name > Runtime > Pull points
Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services > [Content Pane] service_name > Runtime > Pull points

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Notification services > [Content Pane] service_name > WS-Notification service points > [Content Pane] point_name > Runtime > Administered subscribers
Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services > [Content Pane] service_name > WS-Notification service points > [Content Pane] point_name > Runtime > Administered subscribers
one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Notification services > [Content Pane] service_name > Permanent topic namespaces
Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services > [Content Pane] service_name > Permanent topic namespaces

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Notification services > [Content Pane] service_name > Permanent topic namespaces > [Content Pane] namespace_name
Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services > [Content Pane] service_name > Permanent topic namespaces > [Content Pane] namespace_name

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Notification services > [Content Pane] service_name > Permanent topic namespaces > [Content Pane] namespace_name > Topic namespace documents
Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services > [Content Pane] service_name > Permanent topic namespaces > [Content Pane] namespace_name > Topic namespace documents

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Notification services > [Content Pane] service_name > Permanent topic namespaces > [Content Pane] namespace_name > Topic namespace documents name > Upload
Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services > [Content Pane] service_name > Permanent topic namespaces > [Content Pane] namespace_name > Topic namespace documents name > Upload

one of the paths shown in the table Paths to this panel
Service integration > Web services > WS-Notification services > [Content Pane] service_name > Permanent topic namespaces > [Content Pane] namespace_name > Topic namespace documents name > View
Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services > [Content Pane] service_name > Permanent topic namespaces > [Content Pane] namespace_name > Topic namespace documents name > View

Common administrative console button strings (text entities)

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

Other common ui strings

The scope displayed is for information only, and cannot be changed on this panel. If you want to browse or change this resource (or other resources) at a different scope, change the scope on the messaging provider settings panel, then click Apply, before clicking the link for the type of resource.

As a convention, use a JNDI name of the form jms/Name, where Name is the logical name of the resource. For more information about the use of JNDI and its syntax, see JNDI support in WebSphere Application Server 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.

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

The DefaultPrincipalMapping JAAS configuration is used by Java 2 Connectors to map users to principals that are defined in the J2C Authentication Data Entries. You can define and use other mapping configurations.

connectionProximity_more

The bus looks for a suitable messaging engine in the same application server as the bootstrap messaging engine. If a suitable messaging engine is found, it is used. If a suitable messaging engine is not found, the bus fails the connection request.

The bus performs the Server-based check. If a suitable messaging engine is not found, the bus looks for a suitable messaging engine on the same host as the bootstrap messaging engine. If a suitable messaging engine is found, it is used. If a suitable messaging engine is not found, the bus fails the connection request.

The bus performs the Host-based check. If a suitable messaging engine is not found, the bus looks for a suitable messaging engine in the same custom group as the bootstrap messaging engine. If a suitable messaging engine is found, it is used. If a suitable messaging engine is not found, the bus fails the connection request.

The bus performs the Group-based check. If a suitable messaging engine is not found, the bus looks for a suitable messaging engine anywhere on the bus. If a suitable messaging engine is found, it is used. If a suitable messaging engine is not found, the bus fails the connection request.

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

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

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

The preferred way to assign a client identifier is for it to be configured on the connection factory and transparently assigned to connections that the factory creates. Alternatively, an application can set the client identifier immediately after creating the connection.

For more information about the use of client identifiers, see the "Client identifiers" section of the JMS Specification.

You can change the delivery reliability option for the destination of a message that is sent by a JMS application as Nonpersistent. The default is Express nonpersistent but you have a range of other options, including those with persistent characteristics, with Assured persistent being the most reliable. For more information refer to Message reliability levels.
You can change the delivery reliability option for the destination of a message that is sent by a JMS application as Persistent. The default is Reliable persistent but you have a range of other options including those with nonpersistent characteristics, with Best effort nonpersistent being the least reliable. For more information refer to Message reliability levels
Important: If you change the delivery reliability options of a message sent by a JMS application from one of the Persistent message reliability options (Assured persistent and Reliable persistent) to one of the Nonpersistent message reliability options (Best effort nonpersistent, Express nonpersistent, and Reliable nonpersistent), you risk losing messages in certain circumstances. For example, at server restart, or when there is heavy workload.
Messages that are assigned to a consumer are locked on the server and cannot be consumed by any other consumers for that destination. Messages that are assigned to a consumer, but not consumed before that consumer is closed, are subsequently unlocked on the server and then available for receipt by other consumers.

You can override this property for individual JMS destinations by setting the Read ahead property on the JMS destination.

You may not want to select this option if you have multiple clients attempting to receive from the same destination, because it can adversely affect message processing. For example, you allocate five messages to client A, but client A takes a long time processing the first of those messages. Meanwhile client B is available, but doing nothing, and could have been helping out with the other four messages. So, the "Default" behavior is to only have it on when there can only be one client (that is, for nondurable subscriptions and durable subscriptions in a non-clustered environment). However, if you are using a queue but you know that there is only ever one client attached to that queue at any one time, you could override the default behavior by selecting this option.

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

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

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

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

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

If the topic is to be used with WebSphere MQ, the topic prefix value should be a maximum of 12 characters.

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

This indicates the name of 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.

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

If the selected messaging engine is in the same server as the application, a direct in-process connection is made and this transport chain property is ignored.

The transport chains represent network protocol stacks operating within a server. The name you specify must be one of the transport chains available in the server that hosts the messaging engine, as listed on the Servers > Application servers > [Content Pane] server_name > Messaging engine inbound transports panel. The following transport chains are provided, but you can define your own transport chains on that panel.

InboundBasicMessaging
This is a connection-oriented protocol, using a standard TCP/IP connection (JFAP-TCP/IP). It includes support for two-phase transactional (remote XA) flows, so that a message producer or consumer, running on a client or server system, can participate in a global transaction managed on that client or server system. The specific use for the XA flows is to support access from an application running in one server to a messaging engine on second server, perhaps because the first server does not have a suitable messaging engine. If the remote XA flows are used, a transaction coordinator must be available local to the application.
InboundSecureMessaging
This is the InboundBasicMessaging protocol wrapped in SSL.

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.

This option is used as part of the task to enable container-managed persistence (CMP) entity beans to share the database connections used by the data store of a messaging engine. This has been estimated as a potential performance improvement of 15% for overall message throughput, but can only be used for entity beans connected to the application server that contains the messaging engine.

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

When a client issues a client connect request, the processing attaches to the required bus according to the following logic:
  • If a target group is specified, connect to the first messaging engine that satisfies the following conditions for the target type:
    • Server Look for a messaging engine in the same server.
    • Cluster Look for a messaging engine in the same server, then on other servers in the same cluster.
    • Host Look for a messaging engine in the same server, then on other servers in the same cluster, then on other servers in the same host.
    • Bus Look for a messaging engine in the same server, then on other servers in the same cluster, then on other servers in same host, then any other messaging engine on the same bus.
  • If a target group is not specified, or a target group is specified but no suitable messaging engine is found and target significance is Preferred, connect to the first messaging engine that satisfies the following conditions for the target type:
    • Server Look for a messaging engine in the same server.
    • Cluster Connection fails.
    • Host Look for a messaging engine in the same server, then on other servers in the same host.
    • Bus Look for a messaging engine in the target group in same server, then on other servers in same host, then any other messaging engine on the same bus.

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.

You only need to specify provider endpoints if the connection factory is used by client applications running outside of a server environment or is used by an application running on a server in one cell to connect to a target bus in another cell.
In these scenarios, the clients (or servers in another bus) cannot locate directly a suitable messaging engine to connect to in the target bus. The client must locate a suitable messaging engine by first using a bootstrap server running a SIB Service (see Servers > Application servers > server_name > SIB Service). The bootstrap server locates a suitable messaging engine on behalf of the client then tells the client how to connect to the selected messaging engine. When using a bootstrap server, one of the predefined bootstrap transport chains must be specified. The predefined bootstrap transport chains are:
BootstrapBasicMessaging
This corresponds to the server transport chain InboundBasicMessaging (JFAP-TCP/IP)
BootstrapSecureMessaging
This corresponds to the server transport chain InboundSecureMessaging (JFAP-SSL-TCP/IP)
BootstrapTunneledMessaging
Before you can use this bootstrap transport chain, you must define a corresponding server transport chain on the bootstrap server. (See Servers > Application servers > server_name > Messaging engine inbound transports.) This transport chain tunnels JFAP using HTTP wrappers.
BootstrapTunneledSecureMessaging
Before you can use this bootstrap transport chain, you must define a corresponding server transport chain on the bootstrap server. (See Servers > Application servers > server_name > Messaging engine inbound transports.) This transport chain tunnels JFAP using HTTP wrappers.

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

host_name
is the name of the host on which the bootstrap server runs. It can be an IP address. In the case of an IPv6 address, put square braces ([]) around host_name as shown in the example below:
[2002:914:fc12:179:9:20:141:42]:7276:BootstrapBasicMessaging
If host_name is not specified, the default is localhost.
port_number
is the number of the port on which the bootstrap server listens. If not specified, the default is 7276.
chain_name
is the name of a predefined bootstrap transport chain used to connect to the bootstrap server. If not specified, the default is BootstrapBasicMessaging.
If you do not specify any endpoint value, the connection factory uses the default endpoint address:
localhost:7276:BootstrapBasicMessaging
Note: When configuring a connection to a non-default bootstrap server, specify the required values using colons as separators. The syntax is as follows:
[ [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.

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

For an application running in an application server, this property defines how close messaging engines must be to the application server. For an application running outside an application server, this property defines how close messaging engines must be to the bootstrap server.

When searching for the most suitable messaging engine a closer messaging engine is always selected ahead of a more remote messaging engine.

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

Use this property to define what happens to any messages that cannot be delivered to this destination. By default, such messages are routed to the system default exception destination of the messaging engine that discovers the problem; _SYSTEM.Exception.Destination.engine_name.

If you want to messages to be sent to another exception destination, select Specify then type its name on this property. The exception destination must be a queue, on the same bus or a foreign bus, and must exist when the destination is created.

If you do not want undeliverable messages to be routed to an exception destination, select None.

If the message contains the discriminator text string, then the message is not processed by the mediation.

You should base the content of the discriminator text string on an understanding of which messages the mediation should process.

The format of the discriminator matches the topic discriminator specification.

If the message does not match the rule defined by the selector text string, then the message is not mediated.

You should base the content of the selector text string on an understanding of which messages the mediation should process.

The format of the selector string is the same as for JMS selector strings.

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

For non-transactional JMS message-driven beans and MessageListeners that use a JMS destination configured on the default messaging provider, best-effort nonpersistent messages are not recoverable. In this case, if a message is unlocked because the message-driven bean or MessageListener threw an exception, then the message is not redelivered or sent to the exception destination because it was deleted from the message store when it was passed to the listener. If you require higher message reliability for non-transactional JMS message-driven beans and MessageListeners, configure a different option for the Maximum reliability property of the bus destination.

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.

Note: When configuring a connection to a non-default bootstrap server, specify the required values for the endpoint address using colons as separators.
For example: for a server assigned non-secure port 7278, on host boothost1, and using the default transport chain BootstrapBasicMessaging:
boothost1:7278:BootstrapBasicMessaging
or 
boothost1:7278
and for a server assigned secure port 7289, on host boothost2, and using the predefined transport chain BootstrapTunneledSecureMessaging:
boothost2:7289:BootstrapTunneledSecureMessaging
The syntax for an endpoint address is as follows:
[ [host_name] [ ":" [port_number] [ ":" chain_name] ] ]
where:
host_name
is the name of the host on which the server runs. It can be an IP address. In the case of an IPv6 address, put square braces ([]) around host_name as shown in the example below:
[2002:914:fc12:179:9:20:141:42]:7276:BootstrapBasicMessaging
. If a value is not specified, the default is localhost.
port_number
where specified, is one of the following addresses of the messaging engine hosting the remote end of the link:
  • SIB_ENDPOINT_ADDRESS if security is not enabled
  • For secure connections, SIB_ENDPOINT_SECURE_ADDRESS if security is enabled.

If port_number is not specified, the default is 7276.

To find either of these values using the WebSphere Application Server administrative console, complete the following steps:
  1. In the navigation pane, click Servers > Application servers > [Content Pane] server_name.
  2. Under Communications, click Ports
chain_name
is the name of a predefined bootstrap transport chain used to connect to the bootstrap server. If not specified, the default is BootstrapBasicMessaging.

The following predefined bootstrap transport chains are provided:

BootstrapBasicMessaging
This corresponds to the server transport chain InboundBasicMessaging (JFAP-TCP/IP)
BootstrapSecureMessaging
This corresponds to the server transport chain InboundSecureMessaging (JFAP-SSL-TCP/IP)
BootstrapTunneledMessaging
Before you can use this bootstrap transport chain, you must define a corresponding server transport chain on the bootstrap server. (See Servers > Application servers > server_name > Messaging engine inbound transports.) This transport chain tunnels JFAP using HTTP wrappers.
BootstrapTunneledSecureMessaging
Before you can use this bootstrap transport chain, you must define a corresponding server transport chain on the bootstrap server. (See Servers > Application servers > server_name > Messaging engine inbound transports.) This transport chain tunnels JFAP using HTTP wrappers.

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.

If you want to provide more than one bootstrap server, identify all the required endpoint addresses. Separate each endpoint address by a comma character. For example, to use the servers from the earlier example:
boothost1:7278:BootstrapBasicMessaging, boothost2:7289:BootstrapTunneledSecureMessaging, [2002:914:fc12:179:9:20:141:42]:7276:BootstrapBasicMessaging

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\manual_help_sib_entities.html

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