The following are the steps and issues when installing Joget DX on other Java EE application servers. Please do contribute to this article with your experiences.


Log file path is specified in WEB-INF/classes/log4j.properties .

Specifically, these 2 tags:

  • log4j.appender.R.File=${catalina.home}/logs/joget.log
  • log4j.appender.R2.File=${catalina.home}/logs/email.log

In other app server types other than tomcat, the value for ${catalina.home} is empty, so the path becomes /logs/email.log .

Do change the path for these tags to set your preferred log paths.
Another alternative is also to set the system property in the Java VM startup script, e.g.: -Dcatalina.home=(your_preferred_log_path)

Installation on Weblogic 14c (14.1.1)

  1. Download the Quick Installer intended for Oracle WebLogic Server and Oracle Coherence development only from (WebLogic Server 14c (14.1.1), WebLogic Server 11g (10.3.6) and Previous Releases.

  2. Run the Quick Installer (NOTE: The installer does not support OpenJDK, and requires Oracle Java Java Archive Downloads - Java SE 11 | Oracle Malaysia):

java -jar fmw_14.1.1.0.0_wls_lite_quick_generic.jar

  1. Create a new Weblogic domain (Installing and Configuring Oracle WebLogic Server and Coherence):

cd wls1411/oracle_common/common/bin
./config.sh

Run Weblogic

  1. Set the required options in JAVA_OPTIONS

export JAVA_OPTIONS="-javaagent:/path/to/wflow-cluster.jar -javaagent:/path/to/aspectjweaver-1.9.22.jar -javaagent:/path/to/glowroot.jar"

Start Weblogic

./user_projects/domains/base_domain/bin/startWebLogic.sh

Deploy Joget

  1. Copy jw.war to wls1411/user_projects/domains/base_domain/autodeploy/
  2. Access Joget at http://localhost:7001/jw

Installation on WebSphere Liberty V24.0.0.5 with Java EE 8 Web Profile:


  1. Set the JVM_ARGS environment variable:

    export JVM_ARGS="-javaagent:path_to/wflow/wflow-cluster.jar -javaagent:path_to/aspectjweaver-1.9.22.jar -javaagent:path_to/wflow/glowroot/glowroot.jar"

  2. Deploy the jw.war file in the usr/servers/defaultServer/dropins directory

Installation on WebSphere Liberty V20.0.0.1 with Java EE 8 Web Profile:

  1. Set the JVM_ARGS environment variable:

    export JVM_ARGS="-javaagent:path_to/wflow/wflow-cluster.jar -javaagent:path_to/aspectjweaver-1.9.22.jar -javaagent:path_to/wflow/glowroot/glowroot.jar"

  2. Deploy the jw.war file in the usr/servers/defaultServer/dropins directory

Installation on WebSphere Liberty V19.0.0.8

  1. Set the JVM_ARGS environment variable:

    export JVM_ARGS="-javaagent:path_to/wflow/wflow-cluster.jar -javaagent:path_to/aspectjweaver-1.9.22.jar -javaagent:path_to/wflow/glowroot/glowroot.jar"

  2. Enable websocket features (disabled by default) by adding <feature>websocket-1.1</feature> in usr/servers/defaultServer/server.xml e.g. 



    <!-- Enable features -->
<featureManager>
    <feature>jsp-2.3</feature>
    <feature>websocket-1.1</feature>
</featureManager>

  3. Deploy the jw.war file in the usr/servers/defaultServer/dropins directory

Installation on JBoss EAP 7 (7.4.0)

  1. Set the JAVA_OPTS environment variable:

    export JAVA_OPTS="$JAVA_OPTS -javaagent:path_to/wflow/wflow-cluster.jar -javaagent:path_to/aspectjweaver-1.9.22.jar -javaagent:path_to/wflow/glowroot/glowroot.jar -Dorg.aspectj.tracing.enabled=false -Dorg.aspectj.tracing.factory=default"

  2. Deploy the jw.war file in the standalone/deployments directory


Installation on JBoss EAP 7 (7.2.0)

  1. Set the JAVA_OPTS environment variable:

    export JAVA_OPTS="$JAVA_OPTS -javaagent:path_to/wflow/wflow-cluster.jar -javaagent:path_to/aspectjweaver-1.9.22.jar -javaagent:path_to/wflow/glowroot/glowroot.jar -Dorg.aspectj.tracing.enabled=false -Dorg.aspectj.tracing.factory=default"

  2. Configure standalone/configuration/standalone.xml to prevent session locking (https://access.redhat.com/solutions/2776221) by removing the locking and transaction tags:

    <cache-container name="web" default-cache="passivation" module="org.wildfly.clustering.web.infinispan">
    <local-cache name="passivation">
        <!-- DELETE OR COMMENT THESE 2 LINES
        <locking isolation="REPEATABLE_READ"/>
        <transaction mode="BATCH"/> 
        -->
        <file-store passivation="true" purge="false"/>
    </local-cache>
</cache-container>

  3. Deploy the jw.war file in the standalone/deployments directory