Installation on Other Java EE Application Servers

This document provides instructions for installing Joget on various Java EE application servers, including WebLogic, WebSphere Liberty, and JBoss EAP. Each installation process involves specific steps tailored to the respective application server environments. Additionally, it includes guidance on configuring the logging file path for different application server types.

Installation on weblogic 14 (14.1.1)

1. Download the Quick Installer intended for Oracle WebLogic Server and Oracle Coherence development. Ensure to download it from the appropriate source, such as WebLogic Server 12c (12.2.1), WebLogic Server 11g (10.3.6), or Previous Releases.
2. To run the Quick Installer, use the following command:
   

   java -jar fmw_14.1.1.0.0_wls_lite_quick_generic.jar

   Note: The installer is not compatible with OpenJDK and requires Oracle Java Archive Downloads - Java SE 11 | Oracle Malaysia. Ensure you have Oracle Java installed before proceeding.

Create a new weblogic domain

After downloading and running the Quick Installer, proceed to create a new WebLogic domain.

3. Use the following command to change to the directory where the configuration script is located and then execute the script to start the domain configuration:
   

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

Run weblogic

After creating the WebLogic domain, set the required options in JAVA_OPTIONS and start WebLogic:

4. Run Weblogic and set the required options in JAVA_OPTIONS.
   

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

Start weblogic

5. Run the following command to start WebLogic server:
   

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

Deploy joget

Follow the steps below to deploy Joget on WebLogic server:

6. Copy the jw.war file to wls1411/user_projects/domains/base_domain/autodeploy/.
7. Access Joget at http://localhost:7001/jw.

Installation on webSphere liberty V20.0.0.1 with java EE 8 web profile

1. Open the terminal. 
2. Execute the following command to set the JVM_ARGS environment variable:
   

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

3. Deploy the jw.war file by copying it to the usr/servers/defaultServer/dropins directory.

Installation on webSphere liberty V19.0.0.8

1. Open the terminal.
2. Execute the following command to set the JVM_ARGS environment variable:
   

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

3. Enable WebSocket features by adding <feature>websocket-1.1</feature> in usr/servers/defaultServer/server.xml.
   

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

4. Deploy the jw.war file to the usr/servers/defaultServer/dropins directory.

Installation on JBoss EAP 7 (7.2.0)

1. Open the terminal.
2. Execute the following command to set the JAVA_OPTS environment variable:
   

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

3. Set up standalone/configuration/standalone.xml to prevent session locking by removing the locking and transaction tags. You can find more information at the following link: https://access.redhat.com/solutions/2776221.
   

   <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>

4. Deploy the jw.war file to the standalone/deployments directory.

Logging file path configuration

The logging file path is specified in the file WEB-INF/classes/log4j.properties. Specifically, these two tags control the location of the log files:

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

In other types of application servers besides Tomcat, the value for ${catalina.home} is empty, causing the path to become /logs/email.log.

To configure your preferred log file paths, Ensure to adjust the path in these tags according to your needs. You can also set the system property in the Java Virtual Machine (VM) startup script.

 For example:

• -Dcatalina.home=(preferred_path).