You can configure your upgraded Content Platform Engine instances with Configuration Manager into a new application server instance.
If you want to upgrade Content Platform Engine or Content Engine to a new application server version or a new machine while leaving the existing system untouched, it is useful to configure and deploy it into a new application server instance. You can configure and deploy into a new application server by creating a new configuration profile or by copying an existing profile and making modifications to that profile.
As an alternative, you can use migration or upgrade methods that are inherent to some application servers, such as IBM® WebSphere® Application Server. These methods allow you to copy and upgrade an existing configuration into a new application server instance. Use of these methods can allow you to retain configuration information for data source definitions, login modules, and LDAP settings that you would otherwise have to reapply for Content Platform Engine, as documented in this topic. If you do prefer to use such alternative methods, follow the procedures in the topic Configuring Content Platform Engine within an existing application server instance.
It is a best practice to retain the name of the virtual server if you migrate to a new application server instance during a Content Platform Engine or Content Engine upgrade, especially if the FileNet® P8 domain has more than one designated Content Engine site. How you set and retain the virtual server name depends on the application server.
It is a best practice to also retain the same port numbers as the existing instance in order to avoid the need to reconfigure other FileNet P8 applications.
You can use Configuration Manager to configure and deploy the Content Platform Engine software that you installed on an application server only if Configuration Manager is running on the same application server.