Page History
...
| 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:
...
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 |
...
- Windows:
<customer-specific>\WebSphere\AppServer\bin\PropFilePassword
Encoder.<sh|bat> <path_to_pbh_dir>\adminclient.props password
3. 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.
...
After creating the application servers, please change the JVM maximum heapsize setting to a value of 2048.
4. Create Shared Library
Go to Environment > Shared Libraries, select the scope on which your Bridgehead should run (CustomAppsCluster) and click on the New... button:
...
Click on OK when you are done:
5. Create URL Resources
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
...
Specification:
file:///$\{CONNECTIONS_CUSTOMIZATION_PATH}/pbh/adminclient.props
panagenda Bridgehead SQL Queries
Name:
panagenda Bridgehead SQL Queries
...
file:///$\{CONNECTIONS_CUSTOMIZATION_PATH}/pbh/queries
panagenda Bridgehead jyscripts
Name:
panagenda Bridgehead jyscripts
...
Specification:
file:///$\{CONNECTIONS_CUSTOMIZATION_PATH}/pbh/jyscripts
6. Deploy EAR
In the ICS go to Applications > Application Types > WebSphere Enterprise Applications, click the Install button and select the path to the file bridgehead.ear:
...
Wait until you see the message "Application panagenda Bridgehead installed successfully" and click on Save:
7. Map Shared Library Reference
In the ICS go to Applications > Application Types > WebSphere Enterprise Applications, select panagenda Bridgehead and set Shared library references to "pbhJython"
...
Add "pbhJython" to the right box and click OK:
Your shared library reference should look like on this screenshot:
Close with OK and save to master configuration.
8. Change Security Role
Please assign the pbh_admin role to the user which you use on the ConnectionsExpert Configuration page (see "User Accounts:" in the ConnectionsExpert Setup Guide):
9. Restart Cluster
Please restart the newly created Cluster or Application Server (which is used for the Bridgehead application) in order to get everything initialized.
10. Populate Web Server Plugins
| Note |
|---|
For licensing reasons, the Bridgehead application has to be accessible via the Connections HTTP server. If this is not possible in your environment, please contact support@panagenda.com. |
...
| Note |
|---|
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. |
11. OPTIONAL: Adjust SPNEGO Configuration
| Note |
|---|
If SPNEGO is used, the panagenda Bridghead has to be added to its exceptions! |
...
- Select your SPNEGO filter
- Add
;request-url!=/bridgehead
to the end of the Filter criteria, as shown on the screenshot: - Confirm by clicking OK
- Store your adjustments with Save:
- If Dynamically update SPNEGO is deactivated, you have restart your entire environment
12. Check 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" in the ConnectionsExpert Setup Guide.
...