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.
Installation on Weblogic 12c (12.2.1.4)
Set the JAVA_OPTIONS environment variable:
export JAVA_OPTIONS="-javaagent:path_to/wflow/wflow-cluster.jar -javaagent:path_to/aspectjweaver-1.8.5.jar -javaagent:path_to/wflow/glowroot/glowroot.jar"
- Deploy the jw.war file in the domains/base_domain/deploy/autodeploy directory
Installation on Websphere Liberty 19 (19.0.0.8)
Set the JAVA_OPTIONS 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"
- 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>
- Deploy the jw.war file in the usr/servers/defaultServer/dropins directory
Installation on JBoss EAP 7 (7.2.0)
Set the JAVA_OPTIONS environment variable:
export JAVA_OPTIONS="-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"
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>
- Deploy the jw.war file in the standalone/deployments directory