After an application is migrated and deployed, additional system configuration steps
might be required.
When an application is deployed for the first time, additional steps that are not
part of the migration or deployment steps might be required to complete the
configuration within the new environment. Also, when an application is redeployed,
system configuration data might be overwritten during the redeployment process. The
system configuration data that is overwritten might need to be respecified.
You might need to complete system configuration tasks from several different
locations. Some configuration tasks are completed directly on the server for the
destination system by using system tools. Other configuration tasks are for objects
in the Content Platform Engine that are created as a part of
the application deployment. Configuration of these objects is done by using FileNet® P8 or IBM® Content Navigator administration tools.
During the deployment planning phase, assemble migration and deployment instructions,
including instructions about any additional configuration that is needed after the
migration and deployment steps. Include additional configuration steps that
encompass scenarios for a first-time deployment or a redeployment.
The
following examples show the types of server-level configuration tasks that might
need to be completed before an application can become operational in its deployed environment:
- Setup of printers. For example, printers might be provided for the use of
case workers in a production environment.
- Creation of file system folders that are used by structures such as IBM Case Manager custom widgets.
- Installation of external web services that the application was designed to
use.
- Installation of additional software components that are integrated with the
application, such as an email server, IBM Forms, Case Analyzer tools, or IBM Operational Decision Manager.
For objects managed in the
Content Platform Engine, most
configuration data is migrated through
FileNet Deployment Manager
when the object is deployed. However, some objects might need additional
configuration after deployment. The following examples show the types of objects
that might require additional configuration tasks:
- Component queue JAAS credentials. Export and import tools typically do not
manage passwords.
- Component Manager configuration and start processes for legacy component
queues.
- JMS JNDI specifications for a JMS queue.
- Supporting libraries that are not included in code modules that are migrated
with the application. Instead, these code modules are referenced by action
handlers or component queues that are used with the application.
If you created other files on the
Content Platform Engine
server as part of your
FileNet P8 application that
must be moved to the destination
Content Platform Engine
server, you must copy these files. The following examples show the types of files
that you might need to copy:
- Custom SQL queries and query scripts. You can save custom SQL queries and
custom Java™ (.js) and Visual Basic
(.vbs) scripts to a file that can be used in future query operations. You
specify the file name and location for these queries when you save
them.
- Java code for event actions that
reference Java classes on the class
path.
- Java code for libraries that are
referenced by code modules.