An action handler implemented as a JavaScript script can
fail in some WebLogic configurations.
Symptoms
An action handler implemented in JavaScript for an event
action, a document classification action, a lifecycle action, or a
change preprocessor action might fail on some versions of WebLogic-based
application servers.
Causes
The js.jar file supplied with some versions of WebLogic
is older than the js.jar file supplied in the Content Platform Engine EAR
file, and the WebLogic-supplied file takes precedence over the Content Platform Engine file.
The js.jar file is the JAR file that contains
the JavaScript implementation.
Resolving the problem
To resolve this problem, complete the following steps:
- Extract the js.jar file from the Engine-wl.ear file
using the jar command:
jar -fvx Engine-wl.ear
APP-INF/lib/js.jar
- Copy the extracted js.jar file to any location
on the WebLogic server. As an example, create a /opt/JavaScript directory
and copy the extracted js.jar file to this new
directory.
- Add the path to the js.jar file to the beginning
of the classpath used to start the WebLogic server. For example, edit
the setDomainEnv.sh script with the following
entry:
EXT_PRE_CLASSPATH=/opt/JavaScript/js.jar
- Start the WebLogic server and verify in the log file (AdminServer.log)
that the first entry in the java.class.path contains the path set
in step 3 above. For example, the entry should look similar to the
following:
java.class.path = /opt/JavaScript/js.jar:...