3.4. Add Custom JVM Properties

At this point, you need to add several custom properties to the JVM that is used to start IBM WebSphere 8. These custom properties take into consideration the configuration changes you have made so far.
  1. Click on Servers --> Server Types --> WebSphere Application Servers in your WebSphere administrative console.
  2. In the list of application servers, click on the server on which you are going to deploy Business Central. This will open up the configuration page for that server.
  3. Under Server Infrastructure, click on Java and Process Management and then Process Definition. This will open the JVM process definition page.
  4. Click on Java Virtual Machine under the Additional Properties heading. This will open up the configuration properties for the JVM that is used to start WebSphere.
  5. Click on Custom properties under Additional Properties.
  6. Create the following properties by pressing the New... button.
    • org.jbpm.designer.perspective=ruleflow - this argument on the command line forces the default perspective in the designer to RuleFlow instead of Full.
    • org.jboss.logging.provider=jdk - you only need to set this property if you have CA SiteMinder TAI (SMTAI) installed in your environment. By setting this property you are forcing Hibernate within Dashbuilder to use JDK instead of log4j for logging. CA SiteMinder TAI (SMTAI) contains an old version of log4j which causes conflicts.

    Note

    JBoss BRMS uses an embedded version of GIT for its artifact versioning. This version of GIT uses ports 9418 and 8003 for normal and SSH access, respectively.
    Make sure that these embedded GIT ports are not already in use in your version of IBM WebSphere.
    If these ports are being used and you need to change the default GIT ports, then change them by setting the org.uberfire.nio.git.daemon.port and org.uberfire.nio.git.ssh.port properties using the steps described here.
  7. You can choose to save these configuration settings to the master WebSphere configuration at this stage.
  8. Restart IBM WebSphere for these changes to take effect.