Page History
The Bridgehead is an interface application for WebSphere that transfers IBM Connections statistics directly to ConnectionsExpert.
Follow these steps to deploy the Bridgehead application on your WebSphere server.
...
| Note |
|---|
In the Bridgehead installation described here, the EAR will be installed in the AppsCluster, so all scopes are set to AppsCluster. If you want to deploy the EAR to a different Cluster, please adjust the scope. |
...
1. Download and copy Files
In the ConnectionsExpert web interface, navigate to the Configuration view by clicking on the cogwheel icon (top-right corner). In the Configuration view you can download the ConnectionsExpert_Bridgehead.zip. This archive includes EAR and configuration files for the installation of the so called Bridgehead:
- bridgehead.ear
- pbh/
- adminclient.props
- jyscripts
- jython-standalone-2.5.3.jar
- queries
Please copy the folder "pbh" into the Connections customization directory.
...
...
2. Configure the adminclient.props settings:
| Code Block |
|---|
host=<dmgr_fqdn> (default: localhost) port=<dmgr_soap_port> (default: 8879) type=SOAP |
...
securityEnabled=true username=<username> password=<password> |
...
autoAcceptSignerForThisConnectionOnly=true |
...
| Note |
|---|
localhost only works in non-clustered environments. Please use the hostname (FQDN) in clustered environments. |
Enter your username and password and configure the other settings according to your WebSphere environment.
You need to add a WebSphere Administrator Account here, no special Connections access roles are needed.
So you can use an already existing account (local or LDAP), or you create a local WebSphere Administrator Account.
Create a local user Users and Groups > Manage Users > Add… and add this user to
Users and Groups > Administrative user roles:
Figure 4: User Roles
Optional: To encrypt the password in the adminclient.props you can use the following command:
...
<customer-specific>\WebSphere\AppServer\bin\PropFilePassword Encoder.<sh|bat> <path_to_pbh_dir>\adminclient.props password
- Create WebSphere Cluster
In the WebSphere Integrated Solution Console (ICS) go to Clusters > WebSphere Application Clusters. Create a cluster with one or optionally more nodes.
Figure 5: Create Cluster 1
Figure 6: Create Cluster 2
Figure 7: Create Cluster 3
In clustered Connections environments you can select more than one node to install the panagenda Bridgehead on.
...
In the ICS go to Resources > URL select the scope on which your Bridgehead should run (CustomAppsCluster) from URLs and click on the New... button. Use as specification like file:///$\{CONNECTIONS_CUSTOMIZATION_PATH}/pbh/...
panagenda Bridgehead Admin Client Properties
Name:
panagenda Bridgehead Admin Client Properties
JNDI Name: url/bridgeheadAdminClientProps Specification:
file:///$\{CONNECTIONS_CUSTOMIZATION_PATH}/pbh/adminclient.props
Figure 11: Create URL Resources - Example
panagenda Bridgehead SQL Queries
Name:
panagenda Bridgehead SQL Queries
JNDI Name: url/bridgeheadQueries Specification: file:///$\{CONNECTIONS_CUSTOMIZATION_PATH}/pbh/queries
panagenda Bridgehead jyscripts
...
Please assign the pbh_admin role to the user which you use on the ConnectionsExpert Configuration page (see "User Accounts:" on page 6):
Figure 19: Security Roles
- Restart Cluster
Please restart the newly created Cluster or Application Server (which is used for the Bridgehead application) in order to get everything initialized.
10Populate Web Server Plugins
...
In the ICS go to Servers > Server Types > Web servers
Figure 20: Populate Web Server Plugins
If you have a firewall between your HTTP and application server, please note that the panagenda Bridgehead ports need to be opened. Otherwise your HTTP server will not be able to access the Bridgehead cluster.
...
Figure 21: SPNEGO Configuration Adjustment 1
- Add
;request-url!=/bridgehead
to the end of the Filter criteria, as shown on the screenshot:
Figure 22: SPNEGO Configuration Adjustment 2
- Confirm by clicking OK
Store your adjustments with Save:
Figure 23: SPNEGO Configuration Adjustment 3
If Dynamically update SPNEGO is deactivated, you have restart your entire environment
Figure 24: SPNEGO Configuration Adjustment 4
12Check Bridgehead Access and Version
Open https://<your connections url>/bridgehead. Login with the user you assigned the
pbh_admin role to, see step 8 "Change Security Role" on page 22.
You should see a line similar to the following:
{"status":"OK","ts":1476867238257,"version":"3.0.0"}
If the status is OK ("status":"OK"), the Bridgehead installation has been successful.