Planning is the key to a successful deployment. Deployment
planning describes, at a high level, the basic planning steps for
deploying a FileNet® P8 system.
Review related documentation
The following
auxiliary documentation provides information about FileNet P8 components and can assist
you in deploying your application.
Review FileNet P8 environments
Review
your source and destination FileNet P8 environments.
See Assets preparation to
identify potential asset issues and to make adjustments as needed.
Consider the use of 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 these issues:
- The equipment that is required to support FileNet P8
- The time that is required to maintain and support two environments
- The time that is required to transfer information between the
source and destination environments
If you adopt this approach, you might need to complete
the following tasks as the project expands to a wider audience:
- Update the security rights on the object store, or add an object
store specifically for use by the new users.
- Add security policies.
- Add specialized files for the new users. For example, the new
users might need special event actions or workflows.
- Add equipment to compensate for the additional workload.
Acquire the appropriate access rights
Acquire
the appropriate access rights to deploy your application. At a minimum,
you need the appropriate access rights to the following tasks:
- Create databases and table spaces, 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 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 table spaces?
- 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 use a different isolated region on the destination
system for your development work?