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 (\).
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
-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.
<bfinstall>\PrepForExternal\jas.war
<bfinstall>/Platform/PrepForExternal/jas.war
<bfinstall>\
<bfinstall>/Platform/
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
<bfinstall>\token_libs
<bfinstall>/Platform/token_libs
<bfinstall>/Platform/token_libs
copy <bfinstall>\token_libs_64\rcl_rational.dll
<bfinstall>\token_libs\rcl_rational.dll
cp <bfinstall>/Platform/token_libs_64/librcl_rational.so
<bfinstall>/Platform/token_libs/librcl_rational.so