Collect data about your servers before creating the bus links.
About this task
To create bus links between servers, you first need to record information about the servers.
To prepare to create bus links, complete the following steps:
- Record the user ID and password that is used in the connectionsAdmin authentication alias for bus communication. You selected this ID and password during the installation process.
- Collect the details of the server and the bus that host the News repository (you will need this information later when you are creating the bus links):
Table 1. Server and bus data
|Server||Name of the WebSphere® Application Server hosting the application; for example, for the News repository: NewsServer; for other applications: ActivitiesServer||You can find this name in the WebSphere Application Server Integrated Solutions Console under Servers -> Application Servers.|
|Host name||The fully qualified host name of the system that hosts the server; for example: server.example.com||To obtain the host name, run an IP checking utility on your system.|
|Bus name||The name of the Service Integration Bus created for this server by the IBM® Connections installation wizard; for example: Connections_NewsServer_Bus.||You can find this name in the WebSphere Application Server Integrated Solutions Console under Service Integration -> Buses.|
|SIB secure endpoint port||The port number on which the SIB service listens for secure connection requests; for example: 7286.||You can find this name in the WebSphere Application Server Integrated Solutions Console under Servers -> Application Servers; from there, navigate to <server_name> -> Communications -> Ports -> SIB_ENDPOINT_SECURE_ADDRESS|
|Messaging engine||The name of the messaging engine for this server; for example: home1Node01.NewsServer-Connections_NewsServer_Bus||You can find this name in the WebSphere Application Server Integrated Solutions Console under Service Integration -> Buses -> <bus_name> -> Messaging engines. You should see only one engine defined here.|
- Using the above table as a reference, collect the details of the server and the bus that host the other applications. You will need this information later when you are creating the bus links.
- Exchange SSL certificates between each server.
Note: If the servers are managed by different WebSphere Application Server profiles, on the same machine or different machines, then you must exchange SSL certificates between each server and the server hosting the News Repository. You do not need to do this for servers that are managed by the same WebSphere Application Server profile because they share the same SSL settings.