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 this procedure on the WebSphere Application Server administrative console.
On WebSphere Application Server version 8.0, the user interface for the WebSphere Application Server 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, click Applications > Application Types > Enterprise Applications.
  • After you select an application, set the context root.
Notes:
  • You do not see a check box for Create MBeans for resources.
  • To redeploy Build Forge® on WAS, delete the Build Forge® previously deployed.

Procedure

  1. Open the WebSphere Application Server administrative console. These are the URLs for the console:
    • http://<was_host>:<was_port>/ibm/console; the default port is 9060.
    • https://<was_host>:<was_port>/ibm/console; the default port is 9043. Use this URL if WebSphere Application Server administrative security is enabled.
  2. 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 WebSphere Application Server 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 WebSphere Application 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 indicated below for DB2.

      The following example is for a MySQL database driver:

      ${RBF_JDBC_DRIVER_PATH}\mysql-connector-java-5.0.5-bin.jar

      This example is for DB2:

      ${RBF_JDBC_DRIVER_PATH}\db2jcc.jar
      ${RBF_JDBC_DRIVER_PATH}\db2jcc_license_cu.jar

      With UNIX or Linux, in the examples above, use a forward slash (/) instead of a backslash (\).

    5. Save the change to the master configuration.
  3. If WebSphere Application Server is deployed on Solaris, it is necessary to update WAS application server JVM to use the DevPollSelectorProvider for IO process.

    Go to the WAS management console. Open Servers > Server Types > WebSphere application servers > server1 > Java and Process Management > Process definition > Java Virtual Machine > Generic JVM arguments

    The content of generic JVM arguments is as follows:
    -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.DevPollSelectorProvider 

    The default server name is server1. However, if your application server where Build Forge® is deployed has a different name, use it.

  4. Install the Build Forge® application WAR file.
    1. Open Applications > Enterprise Applications.
    2. Click Install.
    3. Browse to the jas.war file. Use /jas as the context root.
      • Windows systems:
        <bfinstall>\PrepForExternal\jas.war
      • UNIX and Linux systems:
        <bfinstall>/Platform/PrepForExternal/jas.war
    4. Click Next, and clear the Create MBeans for resources check box if it is selected.
    5. Click Next, and then click Finish.
    6. At the bottom of the installation text, click Save.
  5. Install the Build Forge® help WAR file.
    1. Click 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 Create MBeans for resources check box if it is selected:
    5. Click Next until you see the Finish button, and then click Finish.
    6. Click Save at the bottom of the installation text.
  6. Set RBF_JDBC_LIBRARY as a shared library reference.
    1. Click Applications > Enterprise Applications.
    2. Click the jas.war link.
    3. Click Shared library references.
    4. Select the jas.war box.
    5. Click Reference Shared Libraries.
    6. Add RBF_JDBC_LIBRARY to the list.
  7. Set the class loader order:
    1. Under Manage Modules, select jas.war and select Class loader order from the drop-down menu.
    2. Change that value to Classes loaded with local class loader first (parent last).
  8. Save the changes to the master configuration.
  9. Check the Build Forge® configuration file. Ensure that the services_url entry in the file points to the correct URL. If you are using WebSphere Application Server, the value for this property in buildforge.conf should look like https://<hostname>:9443/jas or https://<hostname>:9080/jas. The buildforge.conf file is in this location:
    • Windows systems
      <bfinstall>\
    • UNIX and Linux systems
      <bfinstall>/Platform/
  10. For UNIX and Linux systems, add execute permissions to all files in the bin directory for jas.

    In this example, the profile AppSrv01 is used. If your profile name is not AppSrv01, use your profile name.

    chmod -R 755 <WAS-install>/AppServer/profiles/AppSrv01/installedApps/<node>/jas_war.ear/jas.war/bin
  11. Update the library PATH variable to include the following directories:
    • Windows systems, PATH includes:
      <bfinstall>\token_libs
    • AIX systems, LIBPATH includes:
      <bfinstall>/Platform/token_libs
    • Linux/Solaris, LD_LIBRARY_PATH includes:
      <bfinstall>/Platform/token_libs
  12. If using 64-bit Linux or WebSphere Application Server, complete the following steps to copy the provided 64-bit libraries:
    1. Rename the 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