You can use WebSphere Application Server to be the application
server instead of the provided Apache Tomcat application server. You
configure it to run the Build Forge services and Build Forge Help
applications .
There are three areas of configuration in Websphere Application
Server:
- Configure it to run the Build Forge services and help applications.
This is required.
- Configure Java 2 security for the Build Forge services application.
This is required if you are running Java 2 security on WebSphere Application
Server.
- Configure support for SSL and password encryption in Build Forge.
This is required if you have configured those features in Build Forge.
Prerequisites
- Check the detailed system requirements for a specific product site.
Run a query for your Rational Build Forge edition and version to see
which versions of WebSphere Application Server are supported.
- Due to restrictions in the license server, the Build Forge console
and WAS must be running on the same operating system and hardware
platform.
- Be sure that you have applied the latest fix pack to WebSphere
Application Server before you attempt to deploy the Build Forge services
layer.
Important: When you use this configuration, you must
start the Build Forge services and Build Forge Help applications in
WebSphere Application Server before you start Build Forge.
They are not started automatically.