Before attempting to run a Java™ application or applet, you must deploy it on the Application Engine server.
Note: If you upgrade to a new FileNet® Workplace or Process Engine version, you must redeploy all existing custom applications and applets. Existing applications/applets, including all Java Step Processors and Launch Step Processors, should be recompiled and then redeployed. If you get compilation errors, check for applicable changes in the new version's sample Java Processors (see Java Step Processor Sample Files and Java Launch Step Processor Sample Files).
The steps to deploy a Java application/applet are as follows:
Copy the JAR file containing your custom Java application/applet to filenet_installation_directory\Workplace\download.
The Event page services Process Engine requests for a JSP page, redirecting control to the View (UI) JSP page. See the Web Application Toolkit's Framework Page for additional information.
In this procedure you modify the supplied Step or Launch Processor Event JSP file to create the new Event JSP page. The JSP file needs to be located in the directory you are deploying.
<%String jarVersionValues = com.filenet.wcm.toolkit.util.WcmBuildStamp.jarVersion + ", " + filenet.vw.toolkit.utils.VWBuildStamp.jarVersion;%>
<%String jarVersionValues = com.filenet.wcm.toolkit.util.WcmBuildStamp.jarVersion + ", " + filenet.vw.toolkit.utils.VWBuildStamp.jarVersion + ", " + "2.0.0"%>
where "2.0.0" is the JAR file version.
<jsp:setProperty name="plugInModule"property="appletClassName" value="filenet.vw.apps.steps.tabbed.VWTabbedStepApplet" />
Modify this line to reflect the name of the package you used when compiling your new Processor. For example, if your JAR file was created in the \newStep directory and the applet is named newStepApplet, your statement would be similar to:
<jsp:setProperty name="plugInModule"property="appletClassName" value="newstep.newStepApplet" />
<jsp:setProperty name="plugInModule"property="jarArchiveValues" value="wcm.jar, pe.jar" />
Modify this statement to add the name and location of the new JAR file. For example, if your custom jar file is named newSteps.jar, your statement would be:
<jsp:setProperty name="plugInModule"property="jarArchiveValues" value="wcm.jar, pe.jar, newSteps.jar" />
If you intend to use several JAR files, it is best to place all of the JAR files into a single JAR file and reference only this one JAR file. Alternatively, you can specify multiple JAR files using a comma delimiter. Not all browsers support multiple JAR files. Also note that each JAR file must be signed.
Create a View JSP page (see Framework Page) that corresponds to the JSP Event page you just created. The JSP page file needs to be located in the directory you are deploying.
WcmString topic = new WcmString("server.WcmStepProc_jsp.topic", "Java Step Processor");
WcmString topic = new WcmString("server.myCustomStepProcessor_jsp.topic", "My Custom Step Processor");
Before you can run your application or applet you need to configure the server for the Web application being used. To configure the server, use the Configuration Console to specify the Web application defined for VWService. See Managing VWServices in the Process Configuration Console documentation.
Specify the web application as a parameter when you run your application/applet, as follows:
To complete the deployment of your application: