Configuring Websphere Application Server to run Build Forge applications

Configure WebSphere Application Server to run the services application and the help application.

About this task

Perform the steps in the following procedure in the WebSphere Admin Console.

Starting the WebSphere version 8.0, the user interface for the WebSphere Administrative Console has changed slightly. The instructions below are for version 7 and earlier. The following differences in version 8.0 affect this procedure:

To access an application, use Applications > Application Types > Enterprise Applications.
The place where you set the context root has moved to after you select the application.
You do not see a checkbox for Create MBeans for resources.

Procedure

Open the WebSphere administrative console. These are the URLs for the console:
- http://<was_host>:<was_port>/ibm/console; 9060 is the default port
- https://<was_host>:<was_port>/ibm/console; the default port is 9043. Use this URL if WebSphere Administrative Security is enabled.
Configure support for your JDBC driver.
1. Create a new variable, RBF_JDBC_DRIVER_PATH. Create the variable in Environment > WebSphere Variables. Its scope should be the WAS node and server. Set the value to the directory that contains your database driver JAR files.
2. Save the change to the master configuration.
3. Stop and restart the WebSphere server to make the new variable available.
4. Create a new shared library, RBF_JDBC_LIBRARY.
  Create the library in Environment > Shared Libraries. Add the JAR file names for your JDBC device driver, using the RBF_JDBC_DRIVER_PATH that you just created. If you have more than one jar file to list, place each jar file in its own line (as is the case with DB2).
  
  The following example is for a MySQL database driver:
```
${RBF_JDBC_DRIVER_PATH}\mysql-connector-java-5.0.5-bin.jar
```
  The next example is for DB2:
```
${RBF_JDBC_DRIVER_PATH}\db2jcc.jar
${RBF_JDBC_DRIVER_PATH}\db2jcc_license_cu.jar
```
  With Unix or Linux, in these examples, use the forward slash (/) instead of backslash (\).
5. Save the change to the master configuration.
Install the Build Forge application WAR file.
1. Open Applications > Enterprise Applications.
2. Click Install.
3. Browse to the rbf-services.war file. Use rbf-services as the context root.
  - Windows systems:
```
<bfinstall>\PrepForExternal\rbf-services.war
```
  - UNIX and Linux systems:
```
<bfinstall>/Platform/PrepForExternal/rbf-services.war
```
4. Click Next, and clear the following check box if it is selected:
  - Create MBeans for resources
5. Click Next until you see a Finish button, then click Finish.
6. Click Save at the bottom of the installation text.
Install the Build Forge Help WAR file.
1. Open Applications > Enterprise Applications.
2. Click Install.
3. Browse to the BuildForgeHelp.war file in the Build Forge installation directory. Use /BuildForgeHelp as the context root.
4. Click Next, and clear the following check box if it is selected:
  - Create MBeans for resources
5. Click Next until you see a Finish button, then click Finish.
6. Click Save at the bottom of the installation text.
Set RBF_JDBC_LIBRARY as a shared library reference.
1. Open Applications > Enterprise Applications.
2. Click the rbf-services.war link.
3. Click Shared library references.
4. Select the A Services Layer Login Servlet box.
5. Click Reference Shared Libraries.
6. Add RBF_JDBC_LIBRARY to the list.
Set the class loader order. Under Manage Modules, select A Services Layer Login Servlet and locate Class loader order in the drop down box. Change that value to Classes loaded with local class loader first (parent last).
Save the changes to the master configuration.
Check the Build Forge configuration file. Ensure that the services_url entry in the file points to the correct URL. If you are using WAS, the value for this property in buildforge.conf should look like https://<hostname>:9443/rbf-services or https://<hostname>:9080/rbf-services. The buildforge.conf file is in this location:
- Windows systems
```
<bfinstall>\
```
- UNIX and Linux systems
```
<bfinstall>/Platform/
```
Add execute permissions to all files in bin directory for rbf-services. (UNIX and Linux systems). In this example, the profile AppSrv01 is used. Use your profile name if it is not AppSrv01.
```
chmod -R 755 <WAS-install>/AppServer/profiles/AppSrv01/installedApps/<node>/rbf-services_war.ear/rbf-services.war/bin
```
Update the PATH variable to include the token libraries directory.
- Windows systems
```
<bfinstall>\token_libs
```
- UNIX and Linux systems
```
<bfinstall>/Platform/token_libs
```
If a 64-bit Linux or WAS is in use, you need to copy the provided 64-bit libraries.
1. Rename the 32-bit library file.
  - Windows systems: rename <bfinstall>\token_libs\rcl_rational.dll to <bfinstall>\token_libs\rcl_rational.dll.old.
  - UNIX and Linux systems: rename <bfinstall>/Platform/token_libs/librcl_rational.so to <bfinstall>/Platform/token_libs/librcl_rational.so.old.
2. Copy the 64-bit library files from token_libs_64 to token_libs. Do not use line breaks in the commands. They are used here for readability.
  - Windows systems
```
copy <bfinstall>\token_libs_64\rcl_rational.dll 
     <bfinstall>\token_libs\rcl_rational.dll
```
  - UNIX and Linux systems
```
cp <bfinstall>/Platform/token_libs_64/librcl_rational.so 
   <bfinstall>/Platform/token_libs/librcl_rational.so
```

Feedback