Page History
...
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:
Enter "pbhJython" in the Name field and use a Classpath based on the Connections Customization directory, such as
${CONNECTIONS_CUSTOMIZATION_PATH}/pbh/jython-standalone-2.5.3.jar
(WebSphere Variable: CONNECTIONS_CUSTOMIZATION_PATH.)
Click on OK when you are done:
5. Create URL Resources
...
Specification:
file:///$\{CONNECTIONS_CUSTOMIZATION_PATH}/pbh/adminclient.props
panagenda Bridgehead SQL Queries
...
In the ICS go to Applications > Application Types > WebSphere Enterprise Applications, click the Install button and select the path to the file bridgehead.ear:
Select Fast Path and click Next.
...
| 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. |
In the next step, map JNDI names for URLs and all DataSources:
Continue the steps and click on Finish.
Wait until you see the message "Application panagenda Bridgehead installed successfully" and click on Save:
7. Map Shared Library Reference
...
Select the second entry and click Reference shared libraries
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.
...
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
...
In the ICS go to Servers > Server Types > Web servers
| 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. |
...
- 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
...