The following are issues encountered and steps to resolve them when installing Joget Workflow Enterprise Edition v4 (4.0.8 onwards) on other Java EE application servers. Please do contribute to this article with your experiences.
Installation on Weblogic 12c (12.1.3.0.0)
1. Add the attached Weblogic deployment descriptor weblogic.xml to jw/WEB-INF
2. Deploy the updated jw.war and jwdesigner.war
Installation on Websphere 8.5 Liberty Profile (8.5.5.2) and Full Profile (8.5.5.0)
1. There is an issue with JSP parsing for certain functions https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014934503. This causes a JSP parsing issue in jw/WEB-INF/jsp/console/app/processView.jsp.
| Code Block |
|---|
Caused by: javax.el.ELException: Function 'fn:escapeXml' not found at org.apache.el.lang.ExpressionBuilder.visit(ExpressionBuilder.java:197) at org.apache.el.parser.SimpleNode.accept(SimpleNode.java:151) at org.apache.el.lang.ExpressionBuilder.prepare(ExpressionBuilder.java:155) at org.apache.el.lang.ExpressionBuilder.build(ExpressionBuilder.java:173) at org.apache.el.lang.ExpressionBuilder.createValueExpression(ExpressionBuilder.java:216) at org.apache.el.ExpressionFactoryImpl.createValueExpression(ExpressionFactoryImpl.java:67) at org.apache.jasper.runtime.PageContextImpl.proprietaryEvaluate(PageContextImpl.java:777) at com.ibm._jsp._processView._jspx_meth_c_forEach_0(_processView.java:4001) at com.ibm._jsp._processView._jspService(_processView.java:404) |
In jw.war, replace that file with the updated one attached here. This change will be included in 4.0.12 onwards.
2. Deploy the updated jw.war and jwdesigner.war
Installation on Glassfish 4.1
1. There is an exception when deploying jw.war due to invalid content in jw/WEB-INF/web.xml
| Code Block |
|---|
Exception while deploying the app [jw] : org.xml.sax.SAXParseException; lineNumber: 112; columnNumber: 24; Deployment descriptor file WEB-INF/web.xml in archive [jw]. cvc-complex-type.2.4.a: Invalid content was found starting with element 'tracking-mode'. One of '{"http://java.sun.com/xml/ns/j2ee":session-timeout}' is expected. org.xml.sax.SAXParseException; lineNumber: 112; columnNumber: 24; Deployment descriptor file WEB-INF/web.xml in archive [jw]. cvc-complex-type.2.4.a: Invalid content was found starting with element 'tracking-mode'. One of '{"http://java.sun.com/xml/ns/j2ee":session-timeout}' is expected. at com.sun.enterprise.deployment.io.DeploymentDescriptorFile.read(DeploymentDescriptorFile.java:324)
at com.sun.enterprise.deployment.io.DeploymentDescriptorFile.read(DeploymentDescriptorFile.java:245)
at com.sun.enterprise.deployment.archivist.Archivist.readStandardDeploymentDescriptor(Archivist.java:665)
|
Modify the web.xml to comment or remove the tracking-mode tag i.e.
| Code Block |
|---|
<!--
<session-config>
<tracking-mode>COOKIE</tracking-mode>
</session-config>
-->
|
2. Deploy the updated jw.war and jwdesigner.war
Installation on JBoss EAP 6.3
1. There is an issue in the spring-modules-validation JAR http://stackoverflow.com/questions/8226916/tld-parse-error-on-deploying-ear-to-jboss-as7. Remove the existing spring-modules-validation-0.8.jar and replace with the patched spring-modules-validation-0.8.patched.jar
2. Spring 2.5 component scanning does not work by default in JBoss https://jira.springsource.org/browse/SPR-5120, so add snowdrop-vfs-2.1.1.Final.jar and replace web.xml with the updated web.xml
3. Deploy the updated jw.war and jwdesigner.war