Links between this messaging engine and messaging engines in foreign service integration buses.
To view this pane in the console, click the following path:
bus_name link_name.
A service integration bus link is a link between a messaging engine in the local bus and a messaging engine in a foreign bus. The messaging engine in the foreign bus must also have a service integration bus link to the local bus. For a connection to be active, the service integration bus links at both ends must be started.
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.
The name of the service integration bus link. In order to work, the name must be the same as the name of the corresponding service integration bus link configured on the target foreign bus.
Required | Yes |
Data type | Text |
The universal unique identifier assigned by the system to the service integration bus link for administrative purposes.
Required | No |
Data type | Text |
An optional description for the service integration bus link, for administrative purposes.
Required | No |
Data type | Text area |
The messaging engine on the foreign bus to which this link connects.
Required | Yes |
Data type | Text |
The type of transport chain used for communication with the foreign bus.
Required | No |
Data type | Text |
The comma-separated list of endpoints used to connect to a bootstrap server.
The port for the bootstrap endpoint is the port defined on the SIB endpoint address that is configured on the target application server on the foreign bus.
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.
If you want an application to use a bootstrap server with a different endpoint address, you need to specify the required endpoint address on the Provider endpoints property of the JMS connection factories that the client application uses. You can specify one or more endpoint addresses of bootstrap servers.
The endpoint addresses for bootstrap servers must be specified in every JMS connection factory that is used by applications outside of an application server. To avoid having to specify a long list of bootstrap servers, you can provide a few highly-available servers as dedicated bootstrap servers. Then you only need to specify a short list of bootstrap servers on each connection factory.
boothost1:7278:BootstrapBasicMessaging or boothost1:7278and for a server assigned secure port 7289, on host boothost2, and using the predefined transport chain BootstrapTunneledSecureMessaging:
boothost2:7289:BootstrapTunneledSecureMessaging
[ [host_name] [ ":" [port_number] [ ":" chain_name] ] ]where:
[2002:914:fc12:179:9:20:141:42]:7276:BootstrapBasicMessaging. If a value is not specified, the default is localhost.
If port_number is not specified, the default is 7276.
The following predefined bootstrap transport chains are provided:
Specifying host_name : chain_name instead of host_name : : chain_name (with two colons) is incorrect. It is valid to enter nothing, or to enter any of the following: "a, "a:", ":7276", "::chain", and so on. The default value applies if you do not specify a value, but you must separate the fields with ":"s.
boothost1:7278:BootstrapBasicMessaging, boothost2:7289:BootstrapTunneledSecureMessaging, [2002:914:fc12:179:9:20:141:42]:7276:BootstrapBasicMessaging
Required | No |
Data type | Text |
The name of the authentication alias, used to authenticate access to the foreign bus.
Required | No |
Data type | drop-down list |
Whether the link is started automatically when the messaging engine is started.
Required | No |
Data type | drop-down list |
Range |
|
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.
The run-time status of the service integration bus link.
Status | Activity | Meaning |
---|---|---|
started | inactive | The service integration bus link is started on the local messaging engine but has no connection to the foreign bus. Theservice integration bus link is attempting to activate a connection to the foreign bus. The service integration bus link on the foreign bus must also be started to enable the successful activation of a connection between the buses. |
started | active | The service integration bus link is started on the local messaging engine and has an active connection to the foreign bus. |
stopped | inactive | The service integration bus link is stopped on the local messaging engine and there is no connection to the foreign bus. |
unknown | inactive | The administrative console cannot contact the server to determine the status. |
Required | No |
Data type | drop-down list |
Range |
|