Professional Documents
Culture Documents
Article - Deploying With FDM PDF
Article - Deploying With FDM PDF
Deployment Manager to
move P8 assets across
different environments in
isolated networks
Abstract: The FileNet Deployment Manager product is an essential tool for any enterprise wide P8
solution. Most organizations have at least 3-4 environments starting from development to production.
All P8 assets need to be efficiently and effectively moved across these different environments. This
article describes the steps to achieve a successful P8 application deployment. It overcomes the product
limitation of P8 asset dependency by providing a standardized pattern on how to extract the objects in
sequential manner and how to perform the deployment when the environments are in different networks.
The article provides steps for content engine, process engine, forms and workplace XT assets; it also
considers the scenario where environment specific data is different across the isolated environments.
About the author: Manoj Khilnani is a Senior Managing Consultant working with IBM Software
Services for Federal (ISSF). He is a certified IT Specialist and FileNet Consultant. He has 16 years of
software development life-cycle experience. In the last few years, he has extensively worked on ECM
products such as DB2 Content Manager and FileNet P8. Reach out to him at mkhilnan@us.ibm.com
Table of Contents
Introduction ........................................................................................................................... 3
FileNet Deployment Manager Concepts ............................................................................... 4
Figure 1. P8 Information Center Deployment Tasks .................................................... 4
Figure 2. Referenced list of P8 deployable objects....................................................... 5
Exporting Content Engine Configuration ............................................................................. 5
Figure 3. Add assets to the export manifest .................................................................. 6
Figure 4. Add Assets Selection List .............................................................................. 7
Figure 5. Edit Include Options ...................................................................................... 7
Figure 6. Include Options List ...................................................................................... 8
Table 1. Sequential export objects and configuration ................................................... 8
Exporting Process Engine Configuration............................................................................ 11
Figure 7. Process Engine Export Configuration ......................................................... 12
Figure 8. Select Export Components .......................................................................... 13
Retrieve Source Environment Specific Data for Mapping ................................................. 13
Copy Exported Configuration across Networks ................................................................. 14
Creating Destination Environment & Source Pair .............................................................. 14
Converting and Importing Process Engine Configuration .................................................. 15
Converting and Importing Content Engine Configuration ................................................. 16
Configuring Imported P8 Objects ....................................................................................... 17
Conclusion .......................................................................................................................... 17
Acknowledgements ............................................................................................................. 17
Resources ............................................................................................................................ 17
Implementing FileNet Deployment Manager to move P8 assets across different environments in isolated networks:
Deploying P8 Application using FileNet Deployment Manager
Introduction
Deployment plays an important role in the FileNet P8 architecture. The P8 product
consists of many different components which have their objects and configurations
defined in separate databases. The content engine and workplace XT components share
the object store database whereas process engine has its own database to store the
workflow related configurations. Different tools such as XT application, FileNet
Enterprise Manager, Process Configuration Console and Process Designer allows the user
to create and store different objects and configurations.
The File P8 application is normally developed in one environment and then copied over to
one or more environments for testing, QA and production. The FileNet Deployment
Manager is used for moving all assets from the source environment to the target
environment. This tool allows most of the objects to be exported except some, such as
cache stores, GCD markings etc. It has a limitation that if the objects have dependency on
another object, then the referenced object must exist before (or be imported when) the
object that references it is imported.
This article focuses on creating the structured sequential export files in the source
environment for content and process assets which can be imported in any remote P8
environment with different environment specific data such as object store and LDAP
principals. The scenario on which we will be focusing is performing the export/import
from development to UAT environment.
Note: This article applies to FileNet Deployment Manager Version 5.1
The above figure shows the high level steps to achieve the application deployment across
environments that can be accessed using single deployment manager.
1.
2.
3.
4.
5.
6.
7.
8.
9.
These steps will change if the environments are in separate networks and cannot be
accessed by single deployment manager instance. In order to achieve the deployment
across isolated environments, the above figure needs to be separated in two different
sequential processes (Source and Destination steps).
Implementing FileNet Deployment Manager to move P8 assets across different environments in isolated networks:
Deploying P8 Application using FileNet Deployment Manager
The above figure shows the list of objects types that are deployable. This list does not
cover all the objects types but only those that are referenced in this article.
1. Select All Programs > IBM FileNet P8 Platform > FileNet Deployment
Manager to open the Deployment Manager
2. Click File > New Environment
3. Enter the environment name, Development in this example. Click Finish
4. Double-click and open the development environment
5. Switch to CE Connection tab and enter the CE information. Click Test
Connection to verify
6. Switch to Overview tab
7. Click Retrieve Data for Object Store Data and select the mode Merge. Click
OK
8. On the left panel, right click Export Manifests. Click New > Export Manifest
9. Enter a name for the export manifest, such as 1_Choicelist. Click Finish
10. Double-click and open the export manifest 1_ChoiceList.xml
11. Click Add assets to the export manifest (Ctrl + Shift + A)
12. Drill down to the Choice Lists option on the left panel
13. Select all application related choice list objects and Click Add
14. Click Close to close the selection window
Implementing FileNet Deployment Manager to move P8 assets across different environments in isolated networks:
Deploying P8 Application using FileNet Deployment Manager
16. Modify the options for the choice list objects as required and Save the changes
(Ctrl + S)
17. Repeat the above steps to export the below objects and configurations
Objects
1_ChoiceList
Options
Implementing FileNet Deployment Manager to move P8 assets across different environments in isolated networks:
Deploying P8 Application using FileNet Deployment Manager
2_PropertyTemplates
3_SearchTemplates
6_Classes
Uncheck Include
content of folders.
Note: Include
subfolders depending
on the data.
Uncheck Include
immediate user defined
object value
properties.
Uncheck Include
immediate user defined
object value
properties.
Uncheck Include
immediate user defined
object value
properties.
Implementing FileNet Deployment Manager to move P8 assets across different environments in isolated networks:
Deploying P8 Application using FileNet Deployment Manager
definitions, form
templates and entry
templates.
11_Workflows
11
2. Click Next
3. Select all applicable process engine components.
Note: If the version of P8 is similar then one can select all the process engine
components.
Implementing FileNet Deployment Manager to move P8 assets across different environments in isolated networks:
Deploying P8 Application using FileNet Deployment Manager
Note: One can retrieve data for all the users/groups from the content engine LDAP
source. The above procedure limits the number of users/groups to only those used
by the P8 system and not retrieves all users/groups in the LDAP system.
4. Retrieve data for the security principal half map from process engine.
a. Click 'Retrieve Data' for the Security Principal Data
b. Select Source as 'Process Engine Configuration Export File' and click 'Next'.
c. Select Deploy Dataset as 'C:\Backup\PEDevExport.xml', mode as Merge
and click 'Finish'.
5. Retrieve data for the service data
a. Click 'Retrieve Data' for the Service Data
b. Select Source as 'From CE Deploy Dataset' and click 'Next'.
c. Select Deploy Dataset as 1_ChoiceList, mode as Merge and click 'Finish'.
d. Repeat the above retrieve service data steps for all the export manifest files
Implementing FileNet Deployment Manager to move P8 assets across different environments in isolated networks:
Deploying P8 Application using FileNet Deployment Manager
Implementing FileNet Deployment Manager to move P8 assets across different environments in isolated networks:
Deploying P8 Application using FileNet Deployment Manager
Modify the entry templates: Make sure the folder path is correct for all the entry
templates. If the form entry templates are modified then modify the form policies
referencing the entry templates.
Transfer the Workflows: The workflows are imported but not transferred. Transfer
all the application workflows. If the workflow references another workflow then
transfer the referenced workflow first.
Conclusion
This article described how to deploy applications using FileNet Deployment manager and
Process Configuration Console. It provided steps on how to export and import most of the
P8 assets across isolated environments. The article also discussed the conversion of
process engine asset for the environment specific data. Though the article referenced most
of the P8 objects, any additional objects can follow the similar deployment path.
Acknowledgements
Thanks to Dave Keen (Advisory Software Engineer ECM Software Development) who
spent valuable time reviewing and giving his suggestions and comments on all aspects of
this article.
Resources
17