Deployment planning
Planning is the key to a successful deployment. Be sure to read this entire document before you attempt to deploy to a destination environment.
At a very high level, the following topics describe the basic planning steps.
Review related documentation
The following auxiliary documentation provides additional information on FileNet P8 Platform and can assist you in preparing your systems. You can find all of the following PDFs on the IBM support page; some are also available in the online help system. To download documentation from the IBM support page, see Accessing IBM FileNet documentation.
Document or help topic name |
Refer to this document... |
Hardware and Software Requirements |
To confirm that the destination environment has at least the minimum supported levels of software from independent software providers. |
Installation and Upgrade Guide |
For information about the installation of FileNet P8 software. |
Release Notes |
To familiarize yourself with the new features and known issues associated with the FileNet P8 release. |
High Availability Technical Notice |
For information about how to set up FileNet P8 using clusters, farms and other high-availability software and hardware. |
Troubleshooting Guide |
For troubleshooting tips associated with a FileNet P8 Installation. |
Performance Tuning Guide |
For tuning tips that might affect a FileNet P8 installation. |
Users and Groups required by FileNet P8 Platform |
For a complete list of the user and group roles, accounts, and responsibilities required to install, configure, and maintain a FileNet P8 system. |
Review the source environment
Review your source environment for possible conflicts and make adjustments as needed.
As you implement your destination environment, try to avoid the following:
- Circular dependencies in the object store
The more independent you can keep the content, the easier it will be for you to move the content from the source to the destination environment. Circular dependencies are likely to cause the import of object store data to fail.
For example, assume that you have two documents, DocA and DocB.
DocA has a property that references DocB and DocB has a property that references DocA. This circular dependency causes the import of DocA and DocB to fail because each document requires the other to be available in the object store.
NOTE If circular dependencies exist, you must re-create the affected objects in the destination object store.
- Security migration
If possible, develop the FileNet P8 application in the destination LDAP domain. If this is not possible, try to replicate the destination LDAP domain in the source environment. By keeping your LDAP environments the same, or as similar as possible, you will reduce the amount of manual clean-up needed before you can transfer information between the source and destination systems.
- Modifying the system classes created as part of object store creation
If an access control list is the only environment-specific data for a system class, consider creating a subclass instead of modifying the system class. For example, consider creating subclasses for classes such as document, folder and custom object. Subclassing these system classes helps avoid initial migration issues and potential upgrade issues as you move from one FileNet P8 release to another.
NOTE Do not subclass system classes such as stored search, entry template, and workflow definition, which have a deployment module in FileNet Deployment Manager. The deployment modules provide processing for environment-specific data in the base classes that FileNet Deployment Manager cannot apply to any subclasses.
Consider using pilot projects
One way to simplify the development and deployment of a FileNet P8 application is to develop a pilot project in your destination environment and to expand its audience over time. By taking this approach (rather than working in a separate source environment) you can minimize:
- The equipment needed to support FileNet P8
- The time required to maintain and support two environments
- The time required to transfer information between the source and destination environments
Having adopted this approach, you might need to perform the following tasks as the project expands to a wider audience:
- Update the security rights on the object store, or add a new object store specifically for use by the new users.
- Add additional security policies.
- Add additional specialized files for the new users. For example, the new users might need special event actions or workflows.
- Add additional machines to compensate for the additional workload.
Acquire the appropriate rights
Acquire the appropriate access rights to deploy your application. At a minimum, you need the appropriate access rights to:
- Create databases and tablespaces as needed for the destination environment.
- Install software.
Review the LDAP settings
Review the LDAP settings on the destination system, and consider these questions:
- Does the destination environment use the same LDAP server as the source environment? If not, what are the differences between the two environments? After you import application data to the destination environment, what changes are needed to the access control lists for the objects?
- What users and groups will use the destination application?
Review the equipment available
Review the equipment available for the FileNet P8 destination system, and consider these questions:
- Do the source environment and destination environment use similar databases and tablespaces?
- How much space does your application and its associated data need?
- Can you access the destination environment from the development environment?
- Is there an overlap of resources between the two environments? For example, can you direct the development Application Engine to the destination Content Engine? Can you use a different isolated region on the destination Process Engine for your development work?