Identify objects to be deployed
The first step in preparing to deploy your application is to identify the assets that must be moved to the destination environment. It is recommended that you create a checklist that identifies all the assets to be moved.
The following list provides an example of the assets that you should include in your checklist. For more detailed lists of the deployable assets you should consider, see FileNet P8 asset deployment maps.
As you make your checklist, limit the selections to the application-specific classes and objects. In addition, include only the assets that are required in the destination environment. Do not include any assets that are unrelated to the source environment.
- Object store content, which can include:
- Documents (including unfiled documents), stored searches, search templates, workflow
definitions, external objects, and other customer-generated content
- Folders or folder hierarchies created for the application.
Best practice: Ensure that you export the complete folder hierarchy for your application. Errors can occur if you export a single folder that is then imported into a different folder hierarchy in the destination environment.
- Custom objects
- Class definitions — ones that you created and, if you changed them, the system class definitions that
were created for each object store
- Custom properties and property templates
- Choice lists
- Event actions, subscriptions, and associated scripts
NOTE When you create a code module for an event action, you can either use Enterprise Manager to attach the associated Java™ class to the code module or you can specify the Java class, which then must exist in the class path on the server. If you use the first approach, the Java class is included in the export files. If you use the second approach, you must ensure that the Java class is transferred to the destination environment.
- Document classification actions
- Security policies
- Document lifecycles actions and policies
- Storage policies
NOTE When importing an object that references another object, ensure that the referenced object
exists in the source object store before you import the referencing object. For example, to
successfully import a property template that references a choice list, ensure that the choice list
exists in the destination object store before you import the property template. If the referenced object
does not exist in the source object store but is included in the export manifest, then during
the import process select Retry Failed Imports in the Import Helper. Selecting this option causes
the import operation to attempt to re-import any referencing objects that previously failed to
import. The successive import operation imports the referencing objects because the referenced objects
were imported during a previous import.
- Application Engine preference files including user and site preference information
and customized configuration files on Application Engine
- Any customizations of or additions to the FileNet P8 applications that you have created, including
applications and Enterprise Java Beans (EJB) components that use one of the Java APIs, application code built using the
Workplace toolkit, JAR files that implement workflow adaptors, and so on.