There are many ways to implement FileNet P8 in an environment. Small organizations might have a simple implementation consisting of the Content Platform Engine (CPE), and Content Navigator. Large organizations may have multiple CPEs in a single cluster performing many different functions. Some of those functions are basic, such as end-users simply uploading or retrieving content. Others are more complex, such as implementing workflows, or bulk uploads/imports. In the more complex environments, questions often arise asking how to keep behind the scenes tasks, such as bulk uploads, from interfering with overall performance.
One way to avoid impacting performance is to separate servers into different functional areas that all point to the same P8 Domain. For instance, FileNet could be deployed to a server, or group of servers that are accessed strictly by end-users. Another instance could be deployed to a server, or group of servers that are used solely for bulk uploads/imports. An additional instance can even be spun up that is specifically used for administrative tasks. In the video below, I go through how to create such an environment.
Application modernization is a growing area of focus for enterprises. If you’re considering this path to cloud adoption, this guide explores considerations for the best approach – cloud native or legacy migration – and more.
As always, feel free to leave comments below. Enjoy!
For more information on Perficient and to learn what we can do for your business, please visit perficient.com.