You can install custom code to use on the Application Engine.
You must deploy custom code from the source
Application Engine to the destination
Application Engine. Custom code might include
the following examples:
- Custom Java™ or HTML launch and step processors. For more
information, see Deploying Legacy Process
Applications.
- Code that is built by using the Content Java API.
- Code for existing custom components.
To deploy custom code to the destination Application Engine server
- Generate an EAR, WAR, or JAR file that contains the custom
code.
- Optional: Include copies of the JAR files that
are provided with the FileNet® P8 software
such as the P8toolkit.jar and javaapi.jar files.
For more information about these JAR files, see JAR File Dependencies.
- Copy the EAR, WAR, or JAR file to the appropriate location
in the destination environment.
- Update references in the code to the following items for
the destination environment:
- Specific names of object stores
- Specific user names
- Specific server names, IP addresses, or ports
- Specific router name and port
- GUIDs for the objects that are created by your application
- Ensure that any absolute folder paths referenced in the
code are available in the destination environment.
- Ensure that files that you copied to the destination environment
are included in the correct class path statements that are used by
the application.