Referencing Action Handlers in the Classpath

For testing action handlers, it is easier to reference them in the class path of your application server rather than store them as CodeModule objects in the Content Engine.

There are various ways of setting a class path. For more information about setting class paths, see the documentation for your application server.

For WebLogic, reference an action handler or supporting library in the CLASSPATH variable in the Content Engine launch script, startWebLogic.sh or startWebLogic.cmd. The Content Engine launch script is in the WebLogic domain where you installed the Content Engine, such as FNCEDomain.

For WebSphere® , you can reference an action handler or supporting library in the CLASSPATH in any of the following ways:

Using the WebSphere Administrative Console, add it as a shared library on the Java™ page, for example, Application servers > server1 > Process Definition > Java Virtual Machine.
In the bin directory of the profile where you installed the Content Engine, reference it in the WAS_CLASSPATH variable in setupCmdLine.sh or setupCmdLine.bat. For example, if you installed in the default profile, modify the setupCmdLine script in the Windows directory WebSphere\AppServer\profiles\default\bin, or the non-Windows directory WebSphere/AppServer/profiles/default/bin.

Restart the application server after you update the class path.

Note: The Windows environment has a command-line size limit, which can be exceeded by a CLASSPATH variable set to a long string. For Windows 2000 and NT 4.0, the limit is 2,047 characters. For Windows XP and newer operating systems, the limit is 8,191 characters.