FileNet P8 Content Platform

Engine Documentation with

Installation Screenshots
Documentation and Installation of CPE

Datum Solutions
Ketan D Mehta
4/25/2016
 Contents

I. FileNet Conte Platform Engine Introduction

II. Pre-Requisites and Components for the Installation of FileNet Content Platform Engine

III. FileNet Content Platform Engine Operating System & Hardware Requirements

IV. Overview of Java V1.6 and above

V. Overview of Java Development Kit (JDK)

VI. Overview of Java Runtime Environment (JRE)

VII. Overview of Active Directory

VIII. Database DB2 V10.5.5

IX. Installation Manager 1.7.0

X. Data Studio V4. 1.0.1

XI. GCD

XII. Object Store

XIII. WebSphere V8.5.5

XIV. Content Platform Engine V5.2.1

XV. Case Foundation

XVI. Domain Creation in ACCE

XVII. Workplace XT

XVIII. CE Client

XIX. Content Navigator

XX. Case Manager

2|Page
I. FileNet Content Platform Engine Installation Documentation with Screen
Shots

Overview of FileNet Content Platform Engine

FileNet is an Enterprise Content Management (ECM) solution product suite from IBM. Enterprises use
FileNet content platform engine to manage their content and business processes. FileNet P8 platform
(CPE 5.2.1) is the latest version of FileNet system. It offers out of the box functionality and capable of
being customize to manage a specific business Process.

II. Pre-Requisites and Components for the Installation of FileNet Content Platform Engine
1. Java latest version (Compatible version i.e. 1.6 and above)
2. JRE
3. Browser (Internet Explorer Version should 9 or above)
4. Directory Services (Active Directory, Tivoli and Oracle)
1. Database (DB2, Sql and Oracle)
2. Data base Client (Data Studio or Toad)
3. Application Server (WebSphere Application Server, Jboss or Weblogic)
4. Case Foundation
5. Workplace XT
6. CE Client
7. Content Navigator
8. Case Manager

First few things will be by default in the system. If not we could download and install it. However, main
installation starts from the Directory Services. Here we use Microsoft Active Directory for LDAP.

Page |3
III. FileNet Content Platform Engine Operating System & Hardware
Requirements

Operating System Hardware Bitness Tolerate Disk Space Memory

AIX 7.1 Power System TL1 SP2 Power System - Big Endian 64 50gb 4gb
Red Hat Enterprise Linux (RHEL)
Server 7 x86-64 64 50gb 4gb
SUSE Linux Enterprise Server
(SLES) 10 IBM z Systems 64 50gb 4gb
Windows Server 2008 R2
Enterprise Edition x86-64 64 50gb 4gb

IV. Overview of Java

Java is a programming language and computing platform first released by Sun Microsystems in 1995.
There are lots of applications and websites that will not work unless you have Java installed, and more
are created every day. Java is fast, secure, and reliable. From laptops to datacenters, game consoles to
scientific supercomputers, cell phones to the Internet, Java is everywhere.

V. Overview of Java Development Kit (JDK)

Jdk is a software development environment used for developing Java applications and applets. It
includes the Java Runtime Environment (JRE), an interpreter/loader (java), a compiler (javac), an
archiver (jar), a documentation generator (javadoc) and other tools needed in Java development.

4|Page
VI. Overview of Java Runtime Environment (JRE)
The Java Runtime Environment (JRE) is a set of software tools for development of Java applications. It
combines the Java Virtual Machine (JVM), platform core classes and supporting libraries. JRE is part of
the Java Development Kit (JDK), but can be downloaded separately.

Page |5
 Java Successfully Installed

VII. Overview of Active Directory

AD has information about all the objects-users, computers, resources like printers, shared Files/Folders-
in an organization/Network. Basically it used for the LDAP Authentication. In order to create a domain,
DC Promo must be used to complete the task. The process will install the AD DS (Active Directory
Domain Services) on the Windows Server, joins the machine to the domain and replicate all partitions
from the existing domain controller.

Steps to create a Domain

Click on Start>Run>DC PROMO

DC Promo starts by checking if the binaries for Active Directory Domain Services have been installed.
This should be done when the AD DS role is added through Server Manager.

Note: It’s recommended to have a Static TCP/IP Address

Active Directory Installation Started.

6|Page
Database

Page |7
Click on Create a new Domain in order to create a New Domain.

Enter the Domain name of your choice as seen below.

8|Page
Select Forest functional level For Example: Server 2003 or 2008 r2

Ensure DNS Server is checked

Page |9
Click on Yes to create a Domain

Click Next

10 | P a g e
Enable reboot on Completion.

P a g e | 11
Your System will reboot. After the reboot Go to Administrative tools>Right Click
on Users>create new users and groups as shown below, give them
administrator privileges. P8admin user and P8admns Groups are standard users
and Groups.

By default we create P8admin user and P8admns Groups.

as shown in the below Screen Shots.

12 | P a g e
Enable Password never expires is recommended.

Click on Next and then click on Finish.

P a g e | 13
Below is the Screen shot of the user which we created.

Installation of Active Directory Successfully Completed

14 | P a g e
VIII. Overview of IBM DB2 V10.5 Installation & Configuration
Database is a collection of data that is related to a particular topic or purpose. Databases are basically
containers for data. A public library stores books, we could also say that a library is a database of books
but strictly defined, databases are computer structures that save, organize, protect, and deliver data. A
system that contains databases is called a database management system, or DBM. As an example,
employee records in a filing cabinet, a collection of sales leads in a notebook, are examples of collections
of data or databases or collection of Documents. We Use DB2 which is RDBMS (relational database
management system) where in applications store data in a tabular form, while DBMS applications store
data as files. RDBMS has a relation between tables.

Autonomics

Automate tasks such as memory allocation, storage management, health monitoring and business policy
maintenance to improve IT productivity. DB2 helps lower the cost of managing data by automating
administration, increasing storage efficiency, improving performance and simplifying the deployment of
virtual appliances. By automating tasks such as memory allocation, storage management and business
policy maintenance, DB2 is able to perform many management tasks itself, freeing up DBAs to focus on
new projects.

Features of DB2 are:-

1. Automatic Maintenance
2. Automatic storage
3. Self-Tuning Memory
4. Health Monitoring
5. Self-Configuration

P a g e | 15
16 | P a g e
Here we need to select the below information and have to assign the Password

P a g e | 17
Click on Create the default DB2 instance which is an environment to store data.

Select Single Partition instance which will reside only on this computer

18 | P a g e
 Click on Finish and please remember the Port Number.

Installation of Db2 Database Successfully Completed.

P a g e | 19
IX. Overview and Screenshots of Installation Manager V1.7.0
Installation Manager is a tool that you can use to install and maintain your IBM software packages.
Wizards guide you through the steps that you must take to install, modify, update, roll back, or uninstall
your IBM products. Use Installation Manager to install individual software packages on your local
machine, or in conjunction with the IBM Packaging Utility to perform software installations for an
enterprise. In File Net p8v Installation Manager Plays a Vital role in installing software’s such as DB2,
Data Studio and Web Sphere.

X. Overview of Data Studio V4.1.0.1

Data Studio is a client for DB2. It provides database management and maintenance support, including
object, change, and authorization management, scripting, basic health and availability monitoring, and
job scheduling to automate changes to the database. The Data Studio client is built on Eclipse
technology and provides an integrated development environment for database and instance
administration, routine and Java application development, and query tuning.

The IBM Data Studio client is one of two Data Studio components: the client and the web console. Data
Studio helps developers and database administrators develop, debug, and deploy database applications
and database routines (SQL or Java stored procedures and user-defined functions).

With the Data Studio client, you can format SQL statements so that they are easier to read, generate
visual representations of access plans, and get recommendations for collecting statistics on the objects
that a statement reference. The Version of Data Studio is 4.1

We typically install the product package using the installation Launchpad and the Installation Manager
Install wizard.

Role, Creation and Operations of Data Studio in FileNet p8

After the Installation of Data Studio, You have to login and create four databases (DB) i.e. GCD, OS,
CMTOS, CMDOS AND ICN. Here, while installing FileNet p8 we use a Standard Naming Convention for
the databases i.e. GCD for GCD and CMTOS for Object Store(OS) remaining are same as mentioned
below.

20 | P a g e
 1. GCD stand for Global Configuration Database
2. CMTOS stands for Case Manager target object store
3. CMDOS stands for Case Manager design object store and
4. ICN stands for IBM Content Navigator.
XI. Overview of Global Configuration Database
The Global Configuration Database (GCD) contains definitions of the common set of attributes that
control functional characteristics of the collection of resources and services for the FileNet P8 domain it
represents. The GCD provides hierarchical object storage and contains bootstrap data and global
configuration information for the FileNet P8 domain. The GCD defines domain resources such as object
store databases, full-text index areas, fixed content storage areas, content cache areas, feature add-ons,
and marking sets. The GCD can contain sensitive information. Only specified users or groups (typically an
administrator) have read and write access to the data contained within it.

After Creating GCD, we don’t touch it nor disturb it unless required.

XII. Overview of Object Store

The IBM FileNet P8 domain can have one or more object stores. An object store represents a location
within an IBM FileNet P8 domain on the Content Engine server in which objects are stored, accessed,
and managed. An object store is used to store a related set of data, which can be grouped by type. For
example, one object store could contain email messages, and another could contain home loan
information. The important distinction is that different object stores can contain data for different
applications, with different metadata. In our example, the object store for email could have an "email"
class of documents that contains "subject", "from", and "to" properties. The object store for home loans
could have a "loan" class of documents that has "total amount" and "interest rate" properties. Another
alternative is to use object stores to group data chronologically. For example, a new email object store
could be created every year. Then to delete emails older than seven years, entire object stores older
than seven years could be deleted. The benefit of chronological grouping is that deleting an entire
object store is much faster than deleting all of the individual objects in an object store.

An Object Store object provides access to metadata and to collections of objects (such as documents,
folders, and class descriptions) that are saved in the object store. As with most other types of objects,
you can use static methods on the Factory inner classes to create instances of object Store

However after creating CMTOS we create three Large Table Spaces i.e. DATA, INDEX and BLOB. Default
buffer pool and table space page size should be 32kb for all the table Spaces including GCD Database.
Default buffer pool and table space page size is 4kb.

After the creation of CMTOS Database. Expand CMTOS>Table Spaces>Right click>Create Large Table
Space Size and Create three individual new tables i.e. DATA, INDEX and BLOB by generating DDL and
then run Sql Query. Default tables are three.

P a g e | 21
Now go back to GCD Database>Expand>right click on tables>refresh>you see 3 additional tables for
Data, Index and Blob i.e. from 144 it will be 147. These additional tables are reflected in GCD after
creating in CMTOS.

Select 1.7.0 and Click next

Click on Install in order to install the Installation Manager

22 | P a g e
Installation Manager is being installed.

Click on restart Installation Manger to launch the Installation Manager and to

start installation of other Packages.

P a g e | 23
After the installation of Installation Manager you will see the below window.
Click on Install in order to install Data Studio or you can launch installation
Manager from the Start button.

Click on I accept the license and then clicks on next to complete the Installation.

24 | P a g e
Enable version 4.1.0.1 and click on next

P a g e | 25
Click on Access help from the web instead of Access help from a server on your
intranet and click on Next.

26 | P a g e
Installation of Data Studio successfully completed.

Click on Start>Data Studio >create a new database as shown below.

Once you click on new Database you will see the below screen shot

Enter the below details to create a new Database

P a g e | 27
After the above step you will see the below screen where you need to type GCD to create a
GCD Database, Default buffer pool and table space page size is 4kb. However we need to
select buffer pool and table space page size as 32kb then click on Run and execute the query
to create a DB. After the creation of GCD, right click on GCD>Connect.

After the above step we need to create a new Database for CMTOS by clicking on create a
new Database and enter the information as shown in the below screenshot.

28 | P a g e
Here we need to create a Database for Object Store as we created earlier for GCD by typing
CMTOS in the Database name. Default buffer pool and table space page size is 4kb. However
we need to select buffer pool and table space page size as 32kb then click on Run and execute
the query to create a DB. After the creation of CMTOS, right click on GCD>Connect.

After the creation of CMTOS Database, Expand CMTOS>Table Spaces>Right click>Create Large
Table Space Size and Create three individual new tables i.e. DATA, INDEX and BLOB by
generating DDL or by running a SQL Query. Default tables are three.

P a g e | 29
Below is the screenshot before creating table spaces.

30 | P a g e
You could see the table spaces successfully created in the above the screen
shot.

Installation of Data Studio Successfully Completed.

P a g e | 31
XIII. Overview and installation of WebSphere
WebSphere (Version 8.5.5 is the latest release)

WebSphere offers a fast, flexible and secure Java application server runtime environment. WebSphere
Application Server supports environments from single server and midsize configurations to large
deployments requiring web tier clustering over multiple application server instances

WebSphere Application Server (WAS) is a software product that performs the role of a web application
server. More specifically, it is a software framework and middleware that hosts Java based web
applications. It helps you build, deploy and run applications with flexible, secure and Java EE-certified
runtime environments—from lightweight production environments to large enterprise deployments.
Application server is used to serve web based applications and enterprise based applications (i.e.
servlets, jsps and ejbs). Application server contains web server internally. It’s a service that handles
requests for business operations, and performs business logic. It provides the infrastructure for
executing applications that run your business.

Typically used for complex transaction-based applications. To support high-end needs, an application
server has to have built-in redundancy, monitor for high-availability, high-performance distributed
application services and support for complex database access

Acts as middleware between back-end systems and clients. It provides a programming model, an
infrastructure framework, and a set of standards for a consistent designed link between them.

WebSphere Consists of

1. Cell
2. Node
3. Application Server
4. Node Agent
5. Deployment Manager

Cell:

A cell is a logical grouping of nodes that enables common administrative activities in a WebSphere
Application Server distributed environment. A cell can have one or many clusters.

Node:

A node is a logical group of one or more application servers on a physical computer. The node name is
unique within the cell. A node name usually is identical to the host name of the computer.

32 | P a g e
Application Server:

The application server is the primary component of WebSphere. The server runs a Java virtual machine,
providing the runtime environment for the application's code. The application server provides
containers that specialize in enabling the execution of specific Java application components.

Node Agent:

A node agent manages all managed processes on a WebSphere Application Server on a node by
communicating with the Network Deployment Manager to coordinate and synchronize the
configuration. A node agent performs management operations on behalf of the Network Deployment
Manager. The node agent represents the node in the management cell. Node agents are installed with
WebSphere Application Server base, but are not required until the node is added to a cell in a Network
Deployment environment.

Deployment Manager:

The administrative process used to provide a centralized management view and control for all elements
in a WebSphere Application Server distributed cell, including the management of clusters. The Network
Deployment Manager is responsible for the contents of the repositories on each of the nodes. The
Network Deployment Manager manages this through communication with node agent processes on
each node of the cell.

Types of Profiles in Was:

1. Application Server: An application server profile runs our enterprise applications and makes
them available to the internet or intranet. It contains a standalone application server.
2. Cell: This environment has 2 profiles. A management profile with a deployment manager & an
application server added (federated) to the management profile.
3. Management: A management profile provides components for managing multiple application
server environments. They are 1) Deployment Manager 2) Administrative Agent 3) Job Manager.
4. Custom: A custom profile contains an empty node with no servers. However a server can be
added after the profile in created.
5. Secure Proxy: A secure proxy (configuration-only) profile is for use with a Demilitarized Zone
(DMZ) secure proxy server. This configuration-only profile is intended only to be used to
configure the profile using the integrated solutions console. After you configure the profile, you
can export the profile configuration and then import it into the secure proxy profile in your DMZ
secure proxy profile in your administrative component.

P a g e | 33
To install WAS, Click on Start button>Right click on Installation Manager>Run as Admin

Select WebSphere Application Server

34 | P a g e
P a g e | 35
Here removing Program 86 and installing in C:\IBM is recommended

At the end of the WAS Installation customization toolbox will launch which is used to create a
Profile.

36 | P a g e
Click on create for Profile Creation, Here select the path of disktag from WAS installation
folder.

Select Application Server and click next

P a g e | 37
Ensure that you uncheck Enable admin security as we would be configuring it later in CPE to
authenticate through LDAP.

Click next

38 | P a g e
Below you could see the details such as Profile name, Node name, Application server name
and port numbers. Please remember the port number. Port numbers can also be seen in WAS
Console. Click on create to create a profile.

Click on Installation Verification to verify or on Start the Server. A verification window will
open up where you could see the details.

WebSphere Successfully Installed

P a g e | 39
After the Installation of WAS, three changes should be done i.e.

1. Heap Size

2. Transaction time out

3. Jar files.

i. Overview of Heap Size

When a Java program starts, Java Virtual Machine gets some memory from Operating System. Java
Virtual Machine or JVM uses this memory for all its need and part of this memory is call java heap
memory. Whenever we create object using new operator or by any another means object is allocated
memory from Heap and When object dies or garbage collected, memory goes back to Heap space in
Java.

How to change the Heap Size

Open WebSphere Application Server Console

http://fnserver.ecm.com:9060/ibm/console or http://localhost:9060/ibm/console or
http://localhost:9060/admin

To Set the Heap Size follow below steps

1. Navigate to the Java virtual machine settings.

2. Expand Servers > Server Types and select WebSphere application servers.
3. Click the name of your server. For example: server1.
4. Under the Server Infrastructure group, click to expand Java and Process Management.
5. Click Process Definition.
6. Under the Additional Properties group, click Java Virtual Machine.
7. Use the following settings (for a single server instance, 3 GB host):
8. Initial Heap Size: 512
9. Maximum Heap Size: 1024
10. Click OK.
11. In the messages box, click Save.
12. Click OK.
13. In the messages box, click Save.
14. Click Save to save your changes to the master configuration.
15. Restart the WebSphere Application Server.

40 | P a g e
 ii. Overview of Transaction time out

The transaction service is a server runtime component that can coordinate updates to multiple resource
managers to ensure automatic updates of data. Transactions are started and ended by applications or
the container in which the applications are deployed.

WebSphere automatically rolls back transactions that don’t complete in a certain number of seconds.
The default setting is 120 seconds, which may be too short for compiling certain complex pages,
especially pages that embed many page fragments.

To set the transaction timeout follow below Steps:

1. Go to WebSphere Console, expand Servers, and then click Application Servers.

2. Click the link for the server you want to edit.
3. Under Container Settings, expand Container Services.
4. Click Transaction Service.
5. Change the Total transaction lifetime timeout to a large value, for example, 500000.
6. Change the Maximum transaction timeout to a large value, for example, 500000.
7. Click OK.
8. Click Save to save your changes to the master configuration.

iii. Overview of Jar Files

A JAR (Java Archive) file is a file that contains the class, image, and sound files for a Java application or
applet gathered into a single file and possibly compressed. When a programmer gets a Java program
development kit, a small program or utility called "jar" is included. The jar utility lets the programmer
create, list, or extract the individual files from a JAR file. In an enterprise, a Java application can be
started with a set of JAR files for use during execution. An off-the-shelf open source package can be
delivered as a JAR file and run with XML data.

To Set the Jar Files follow the below Path

Navigate to Environment under Welcome Page.

1. Expand Environment > WebSphere Variables

2. Click the name of your server. For example: server1.
3. Drop down and select Node
4. Click on DB2UNIVERSAL_JDBC_DRIVER_PATH and enter the Value of the Jar files i.e.
C:\Program Files\IBM\SQLLIB\java
5. Click OK DB2_JCC_DRIVER_PATH and enter the Value of the Jar files i.e. C:\Program
Files\IBM\SQLLIB\java
6. Click OK
7. Click Apply

P a g e | 41
 8. Click Save to save your changes to the master configuration.

XIV. Overview and Installation of Content Platform Engine

Content Platform Engine is a FileNet P8 component that is designed to handle the heavy demands of a
large enterprise. It can manage enterprise-wide workflow objects, custom objects, and documents by
offering powerful and easy-to-use administration tools. Using these tools, an administrator can create and
manage the classes, properties, storage, and metadata that form the foundation of an enterprise content
management (ECM) system. Content Platform Engine is the content and workflow-management
component of the FileNet P8 platform to set up Content Platform Engine and get full workflow
functionality.

P.S. the below screen shots for the installation and Configuration of CPE

42 | P a g e
Accept the License to install Content Platform Engine

Select Installation Set as Custom

P a g e | 43
44 | P a g e
Please ensure that you select the installation directory as C:\IBM\FileNet\Content Engine instead of
Program files as its recommended.

Editing CCL Server URL

Editing of CCL SERVER URL Remove port and enter 9080 as shown below

P a g e | 45
Configuration and editing of MTOM URL

Pre Installation Summary. While Installing CPE it executes Script/Batch file: Executing Ant
Scrip, Builds the CPE Ear file starting from (1 of 5 ) then it starts Merging the Workflow system
EAR files into the CPE (1 of 5 )then it checks the compatibility and Configures .Net API and does
the Installation.

46 | P a g e
Click on Install

Installation Started

P a g e | 47
48 | P a g e
P a g e | 49
Complete the CPE installation of by hitting on done.

You can open the configuration by clicking on Start Configuration Manager from
Installation Complete Window as shown above or you could open it from the desktop and
Start button if you plan to configure later.

Content Platform Engine Successfully Installed.

50 | P a g e
 Configuration of Content Platform Engine
We can configure and deploy all of your Content Platform Engine instances with Configuration Manager.
Configuration Manager prepares the Content Platform Engine application for deployment on the
application server. Configuration is a multiple step process. You must provide information about your
Content Platform Engine application environment, apply the settings by running the configuration tasks,
and deploy the application. You can configure multiple instances before you deploy any of them, or you
can configure and deploy one instance at a time.

Profile Creation in CPE

Open FileNet Configuration Manager to create a profile and to set the Application Server Properties. P.S.
the below steps.

1. Click on Workbench
2. Click on File
3. Click on New Installation Profile
4. Give Profile Name =Ex:(CPE)
5. Click Next
6. Select Application Server = WebSphere
7. It will Navigate to Set Properties for WAS
8. Select the Version of WAS from Dropdown
9. Select Application Server Installation Directory
10. Select Server profile directory
11. Application Server user name and PW
12. Soap Port number = 8880
13. Application server host = localhost
14. Application Server cell = Select from dropdown
15. Application server transaction timeout =600
16. Security domain = default
17. Test Connection and
18. Click on FINISH

After the creation of Profile we open the Profile from Configuration Manager for Content
Platform Engine and perform the below tasks.

1. Accept or Choose License

2. Java Database Connectivity (JDBC) data source properties for the global configuration database
(GCD) database
3. Java Database Connectivity (JDBC) data source properties for each object store database
4. Directory service (LDAP) provider properties
5. Content Platform Engine application login modules
6. Content Platform Engine bootstrap properties
7. Deploy Application

P a g e | 51
 i. Overview and Configuration screenshot of GCD JDBC Data Sources
The JDBC data source information is used by Content Platform Engine to connect to the global
configuration database (GCD) and the object store databases. Configuration Manager provides two tasks
for configuring the JDBC data sources: Configure GCD JDBC Data Sources and Configure Object Store
JDBC Data Sources.

The procedures for editing the Configure GCD JDBC Data Sources task and the Configure Object Store
JDBC Data Sources task are the same. To complete the Content Platform Engine configuration, you must
configure the GCD data sources and the data sources for each object store.

To edit the Configure GCD JDBC Data Sources task:

Choose License will be by default

Open first GCD data source task and then object store data source task for editing:

1. Double-click Configure GCD JDBC Data Sources or right click and edit task
2. Double-click Configure Object Store JDBC Data Sources or right click and edit task

Provide the property values for your database. Place your mouse on a ? (Question Mark Icon to view
the property description. P.S. the below screen shot of GCD JDBC Data Sources)

52 | P a g e
 ii. Overview and Configuration screenshot of OBJECT STORE JDBC
data sources
Each object store in our site requires its own JDBC data sources. We can configure the data sources by
using the Configuration Manager.

We created the JDBC data source for the Global Configuration Data (GCD) earlier in the configuration
process so, now we must add the data sources for at least one object store. We can create additional object
store data sources as needed either immediately or later while configuring Case Manager.

Please see the below screen shots.

P a g e | 53
After entering the below values click on Run task and ensure it’s successfully Finished.
Please see the below screenshots for details.

54 | P a g e
iii. Overview and Configuration screenshot of Login Modules
Login Modules are basically for Authorization and Authentication .All logins to FileNet P8 are done
through the Java Authentication and Authorization Service (JAAS). Authorization takes place by means
of a direct connection between Content Platform Engine and one of the supported directory services i.e.
Active Directory.

P a g e | 55
iv. Overview and Configuration screen shot of LDAP
We must configure the LDAP (Lightweight Directory Access Protocol) settings. The directory service
provider (LDAP) settings define the directory service and the users and groups that Content Platform
Engine uses for authentication. Every user has to be a part of LDAP. Here we need to enter the details of
Directory Services.

For example: Select the Directory Services which you are using for ex: AD or Tivoli. Here I selected
Active Directory as I am using directory services from Microsoft We need to specify the repository type,
server name, directory service port number, bind and base username and password for Authentication and
configuration of LDAP and then run the task.

Test Connection before running the task to ensure connection is successful.

56 | P a g e
 v. Overview and Configuration screenshot of Bootstrap and Text
Extraction
The bootstrap settings are for creating the global configuration database (GCD) and for starting Content
Platform Engine. The text extraction setting is used to install the IBM Content Search Services text
extraction and API modules into the CPE EAR file. Configuration Manager configures the bootstrap file
with information supplied by the user. Here we need to enter the details of GCD Data Sources, bootstrap
Username and Password and then run the task.

When you click on View Bootstrap EAR and Text Extraction info you will see the below
information

P a g e | 57
vi. Over view and configuration of Deploy Application
Deploying an application means putting it on a Web server so that it can be used either through the
Internet or an intranet. Right click on Deploy Application>enable the task select Deployment type
weather standard or Network. I chose Standard as it’s a Standalone. Select the Application Server Name,
Node and virtual host and then run the task.

Select Deployment type and rest of the information will automatically pop up. After selecting the
required fields run task and ensure it is finished successfully.

Content Platform Engine is successfully Installed and configured by executing

the above the tasks.

58 | P a g e
 After the completion of the above task we need to install Case Foundation.

XV. Overview and Installation of Case Foundation

Case foundation earlier known as BPM (Business Process Management) The IBM Case Foundation
installation is required for licensing of full workflow functionality and to install several tools that are
required for Case Analyzer.

P a g e | 59
60 | P a g e
 Specify the Directory Path

Specify the Destination folder

P a g e | 61
Select Installation type as custom so that it can enable Case Analyzer Components.

This detected a valid installation of CPE

62 | P a g e
It reviews the information So go through the product features and Click on Install

Installing Java Runtime Environment

P a g e | 63
Enable to Case Analyzer

Click on Done

Case Foundation Installation Successfully Completed

64 | P a g e
 After installing Case Foundation, Go to WebSphere Console > Expand Application types and follow the
below Steps to access FileNet Engine.

1. Click on WebSphere enterprise Applications

2. Select FileNet Application and click start
3. Once Application is started Go to Browser and access the FileNet by putting the below address
4. http://localhost:9080/acce/
5. You will see the Administration Console for Content Platform Engine (ACCE )

Login to ACCE to create a Domain with the user name and Password to create a Domain.

P.S. the below screen shot

XVI. Overview and Domain Creation in ACCE

FileNet P8 domain is a logical grouping of resources like object store databases, full text index area, file
storage areas, and content cache areas. A FileNet p8 server provides access to the resources which are
mentioned above. Each resource and each FileNet p8 server belongs to only one domain. A FileNet p8
server can access any resource in its domain, but cannot access any resource that lies outside of its
domain. The FileNet P8 domain is associated with one or more Java 2 Enterprise Edition (J2EE) security
policy domains. The J2EE domain is used to authenticate users and establish their group memberships.
The identity and group membership of the user determine which FileNet P8 domain objects the user can
access.

P a g e | 65
After the completion of the above task we need to create a FileNet P8 domain which contains the entities
that represent the Content Platform Engine physical resources (such as object stores) as well as the
Content Platform Engine servers that provide access to the applications like WorkplaceXT.

i. Domain Creation in ACCE

To create a domain we need to give a Display Name, specify the Directory Service Provider which we
used for example Microsoft Active Directory.

After the above step we need to configure the user access information by providing the below information

1. Display Name
2. Directory service Provider Name
3. Hostname
4. Directory service port number
5. Bind user name and password i.e. cn=administrator, cn=users,dc=ecm, dc=com
6. User base DN and password i.e cn=users,dc=ecm,dc=com ,
7. Group Base DN
8. Add Users and Groups

Now the domain is successfully created. P.S. the below Screen shots

66 | P a g e
Select the Directory Service.

P a g e | 67
Enter the group base DN

68 | P a g e
Adding of users and group to P8 Domain

Click on Finish

P8 Domain Successfully Created

P a g e | 69
After Domain Creation we need to create Connection Point, Object Stores, Workflow and Isolated
Region. Below is the theory and screenshots of the mentioned components.

Overview and Creation of Connection Point in ACCE

Before creating an Object Store it’s recommended to create a Database connection Point. You could also
create a connection point while creating Object Store. To create a connection point P.S. the below steps

1. Expand Administration under Domain

2. Right Click on Database Connections and select New DB connection
3. Give the Display Name
4. Enter JNDI and JNDI XA data source (The name of the JNDI data source through which a
connection can be made to the database)
5. To check the data source go to WAS Console >Resources>JDBC>Data sources.
6. Finish.

Overview of Object Store

An Object Store object provides access to metadata and to collections of objects (such as documents,
folders, and class descriptions) that are saved in the object store. As with most other types of objects,
you can use static methods on the Factory inner classes to create instances of object Store.

P.S the below steps to create object Store.

1. Enter the Display Name

2. Under Define the DB > Select Connection Point from the drop down which you created
3. Under the Type of Storage Area for Content >Select Storage Area i.e. DB or File Storage
4. Under Grant Admin Access>Add Users
5. Under Select Add on>Select Workplace XT and other Add on
6. Click Finish

P.S below for more details of Storage Areas

Storage areas

Storage areas represent the physical location where content is stored in P8. There are four types of
storage areas. They are as follows

1. Database
2. File
3. Fixed
4. Advanced

70 | P a g e
 i. Database storage

Content in a database storage area is stored within a table in the P8 object store database. Each P8
object store has one, and only one, database storage area. Database storage areas are useful when the
size of your object store is not very large in terms of number of documents and the sizes of those
documents. Smaller documents of about 10MB or less do have performance advantages in a database
storage area when compared to other storage area types. You should not store any document that is
over 100MB in a database storage area.

ii. File Storage

A file storage area is an area that contains document content in a directory tree on a local or shared
network drive. The disk drive can be a Windows NTFS volume, a UNIX file system.

iii. Fixed storage

A fixed storage area consists of two storage repositories: a staging area on the FileNet P8 system and a
separate content device. The content device can be a fixed content device or a federated content
system. Content devices have distinct operating software that runs independently of the storage that it
manages. Initially Content Platform Engine writes the object content to the staging area. While in the
staging area, the object content element list can be freely modified. The object content is later migrated
from the staging area to the fixed device. Annotation content is never migrated to the content device.
FileNet P8 can set and modify the retention setting for object content that is stored on the fixed content
device. The object content retention is synchronized between FileNet P8 and the fixed content device.

Retention on object content stored in the fixed content device is applied when the object is checked in
to the fixed content device. When you check out an object, you can change the retention setting for that
object. When you check the object back in to the fixed content device, the new retention setting is
applied to the object content.

Below are the few fixed storage companies

1. Centera
2. Nas and
3. San

P a g e | 71
 iv. Advanced Storage Area

An advanced storage area provides high availability content storage and disaster recovery through use
of replication and replica repair. This capability is accomplished without relying on any special features
of the underlying storage devices, so advanced storage areas can be applied to commodity storage. An
advanced storage area supports different storage devices. A single advanced storage area can have
multiple advanced storage devices that are connected to it. For example, you can have an OpenStack
storage device and two file system storage devices that are connected to an advanced storage area.
Each one of these devices is a replica in the advanced storage area. In addition, a single storage device
can be used by multiple advanced storage areas within the same object store. So the same OpenStack
storage device can be connected to two advanced storage areas.

v. Creation of Workflow System

A workflow system is a collection of isolated regions. Each isolated region contains the queues, rosters,
and event logs that are necessary to create and process workflows.

vi. Connection Point

A connection point identifies and provides access to an isolated region of the workflow system database.
Client applications use the connection point to access an isolated region for workflow process
functionality such as work items, queues, rosters, and event logs. An isolated region can have multiple
connection points. While creating a new Workflow system enter the table space of the Data which was
created in Data Studio. We need to create an Isolated Region.

vii. Isolated region

An isolated region is a logical subdivision of the workflow database that is identified by a database
connection and an isolated region number. You can use an isolated region for a production environment
and a separate isolated region for a development environment. You can create custom table spaces to
store workflow data such as queues, rosters, event logs, indexes, region object tables, or identity tables.
Segmenting workflow data to separate table spaces can improve performance or enable the backup and
recovery of data for a specific isolated region.

P.S the below Steps for the creation of Workflow

1. Open the Object Store (CMTOS)

2. Click on Administration>Workflow System
3. Right Click on Workflow System>New Work flow system
4. Enter table space for DATA which you gave in the Data Studio
5. Give name for the Connection Point
6. Give Name for the Isolated region
7. Give a random number for Isolated region
8. Finish

72 | P a g e
Creation of Object Store in ACCE

Give the Display for the Object Store, Standard Naming Convention is CMTOS. However
here I Chose OS instead of CMTOS because OS is already created in Database.

P a g e | 73
Please enter the Data Source name which we configured in the OS JDBC Data Sources.

74 | P a g e
P a g e | 75
Select the Storage Area

Add Admin user and Groups to have the Administrative access the Object Store.

76 | P a g e
Select the users and Groups to give the Authorization. P.S the below ScreenShot.

Click next and select the Add on Extensions. This acts as a Plug in.

P.S. the below screen shot.

P a g e | 77
After the above Step Click next to complete the Domain Creation.

Object Store Successfully Created

78 | P a g e
While creating a new Workflow system enter the table space of the Data which was created in Data
Studio. We need to create a Connection point and Isolated Region

Creation of Isolated Region

P a g e | 79
 Object Store Successfully Created.

80 | P a g e
XVII. Overview and Configuration Workplace XT Version: 1.5
Workplace XT is an Application Engine An end-user web application that provides access to the
document management capabilities and is tightly integrated with the business process management
capabilities of FileNet P8. Workplace XT also supports extended FileNet P8 capabilities such as forms
management, records management, and portals. Workplace XT runs in a J2EE web container. Workplace
XT is faster, user friendly and has features like drag and drop to add documents. Most of the features
provided in Workplace XT are zero-download HTML that runs under many browsers on any platform.
Advanced capabilities that are graphic-intensive are provided as Java applets, including Process Designer,
Process Configuration Console, Process Administrator, Scenario Designer, Scenario Console, and Search
Designer. Application Engine protects user credentials passed between Workplace and Content Platform
Engine and, if configured, provides SSL security.

P.S. the below steps for the installation of Workplace XT

1. Click on Workplace XT software and run it as run as a administrator and click Next
2. Accept the terms and license agreement
3. Click Next
4. Specify the installation path>Click Next
5. It will check the connection>Click Next

6. Client will be configured >Click Next

7. Workplace XT Product will be automatically detected by the CPE Installation Program>Click
Next
8. Now it will update, an if required, it will overwrite the existing CPE client files found at this
location
9. Now Specify the type of the Application Server on which CPE is deployed i.e. WebSphere
10. CPE Url' will be automatically there. So need to specify. It is used for CPE server connections
11. cemp:iiop://localhost:2809/FileNet/Engine >Click Next
12. Component Manager CPE url will be there by default. This URL is used to connect to the XT
Component Manager i.e. cemp:http://localhost:9080/wsi/FNCEWS40MTOM/> Click Nexet
13. Uncheck add rest services> Click next
14. Enable Create the deployment file now in order to create a deployment file
15. Click Next
16. Select the destination folder>Click Next
17. Case foundation will be detected
18. Click Next
19. Now the IBM CPE Client will be configured> Click next
20. It will update Workplace XT>Click Next
21. Case Analyzer and Workplace XT Service manager Component will be enable by default
22. Click Next
23. DONE

After the Installation of Workplace XT we need to do the below changes and they are as follows

P a g e | 81
 1. Login to WebSphere: https://fnserver.ecm.com:9043/ibm/console/login.do?action=secure
2. Under Applications >Click on Applications
3. Click on New Enterprise Applications
4. select New application and it redirects to new local file path , there we need to give
web_client.ear file and click next .
5. There it asks the installation options :
6. Fast path or detailed, need to select which one we like to prefer and click Next
7. Once it deployed, click on Applications - > Application types -> click on WebSphere enterprise
applications , there we need to click on Workplace XT and need to do three changes. They are as
follows
8. Click on
9. Workplace XT - > Class loading and Update detection Classes loaded with local class loader first
(parent last).
10. Enterprise Applications -> Workplace XT > Manage Modules ->web_client.ear - > Class loader
order -> Classes loaded with local class loader first (parent last).
11. Enterprise Applications - >Workplace XT -> Security role to user/group mapping -> All
Authenticated by mapping special subjects to All Authenticated in Application's Realm ,
Everyone by mapping special subjects to Everyone.
12. Once changes are done start and stop the WebSphere server.

Below are the Screen shots of Workplace XT

82 | P a g e
Select the Installation Path as C:\IBM\FileNet\WebClient or remove 86 if you are installing in
Program file as shown below

P a g e | 83
Below we need to select WebSphere Application Server and it’s version as it’s our Middleware
Application.

84 | P a g e
Below we need to set the EJB transport Method by giving the hostname i.e. localhost

Generate an EAR file should be enable in order to deploy the Workplace XT in WebSphere

Click on Next

P a g e | 85
Select the Configuration Path. For Ex: If you want to install in C:\IBM\FileNet\Config remove
program files

86 | P a g e
Specify the directory Path for Ex: If you want to install in C:\IBM\FileNet\Webclient\upload
remove program files. XT uses this directory path to store temp copies of files uploaded to the
application.

Please specify the Log file directory path

P a g e | 87
Below is the screen shot for the Configuration of user token security settings so that it can be used
to pass and accept the credentials from the FileNet Applications, Click next to complete the
Installation

Below are the final installation screenshots of Workplace XT

88 | P a g e
 Workplace XT Successfully Installed.

P a g e | 89
XVIII. Overview of Content Platform Engine Client
After the Installation of Workplace XT we have to install Content Platform Engine Client software in
order to enable the communication between the Application Engine and Content Platform Engine.

XIX. Overview of Content Navigator

IBM Content Navigator is a user interface for Enterprise Content Management (ECM) solutions.Content
Navigator enables users to create custom views of the content on the web client by creating team spaces,
which provide a focused view of the relevant documents, folders, and searches that a team needs to
complete their tasks. IBM Content Navigator also includes a powerful API toolkit that you can use to
extend the web client and build custom applications. Content Navigator enables users to search and work
with documents that are stored in content servers that are located around the world from a web browser.
IBM Content Navigator is accessible from Mobile Phone. Content Navigator can be used to access
multiple content management repositories.In Navigator we have Favorites, Browse, Document
Information, saved search list, search builder, text search etc.

With IBM Content Navigator, users can do the below activities

 Search for content that is stored on the repository

 Preview documents
 View documents side-by-side
 Edit document properties
 Add annotations to documents
 Send documents and links to documents through email
 Print documents
 Download documents

In addition, if you use IBM Content Navigator with IBM Content Manager or IBM FileNet Content
Manager which we are using we can do the below activities.

 Browse for content that is stored on the repository

 Search for content that is stored on the repository by running a text search
 Save document, folders, and other content as favorites
 Edit documents
 Add documents to content servers
 Organize documents by creating folders and adding content to the folders
 Use workflows to:
 Review and approve documents
 Assign work to users
 Use the version control rules that are set on the repository\

Below are the Installation screen shots of IBM Content Navigator

90 | P a g e
Before installing Content Navigator, we need to create a Database for Navigator. Name the Database
as ICN. P.S. the below screen shots.

Enter the username, Password, Instance name and Port

P a g e | 91
Name the Database as ICN as its Standard naming Convention

After naming, select the buffer pool and table space page size to 32kb and click on Run in order to run
the query.

92 | P a g e
After the Creation of ICN Database we need to install ICN. P.S. the below steps for ICN Installation.

Right Click on the ICN Application or double click to install.

Installation is being prepared

P a g e | 93
After the above step you will see the below screen where you need to click ok and accept the License
Agreement

Installation Directory

94 | P a g e
Below is the Pre installation Summary where you could review the information and click Install to
continue or previous to make changes.

It will unzip the Script for the Installation.

The following client connector files were also installed as part of the IBM Content Navigator
installation

P a g e | 95
After the above screen Workbench will be loading for ICN Configuration and Deployment tool

Click on Workbench to Create a Profile for ICN

After seeing the above screen follow the below steps and Installation Screen Shots

1. Click on Workbench and Create Profile

2. Give the Profile Name
3. Select Application Server i.e. WebSphere
4. Enter the information about your environment to enable the tool to connect to the web
application server i.e. WebSphere
5. Application Server Version
6. Installation directory
7. Profile
8. Admin user name and password
9. Soap Port Number
10. Host Name
11. Cell an deployment session timeout
12. After enabling the above tool a connection to the Application server is formed...
13. Select the Application to Configure

96 | P a g e
Click on File and create a new Profile for ICN

Provide a standard name for the Profile

See the below screen shot for Naming Convention and Profile Directory

P a g e | 97
We need to select Web Sphere Application Server as we already Installed it in order to deploy ICN.

Below is the screen shot to specify the installation Directory path.

98 | P a g e
I removed Program files as I installed WebSphere Application Server in the below mentioned path.

After enter the above details we need to test the connection and ensure that it’s Successful.

We need to Select IBM FileNet p8 to Deploy and Configure.

P a g e | 99
Here we need to click on Next to Configure and deploy the Web Application.

Update the FileNet P8 Client Connector files by giving the Protocol, hostname and Port Number. This
will install the Content engine client connector files to the Navigator server.

After the entering the details, when you click on test Content Engine Connection you will see the
below message

100 | P a g e
After testing the connection when you click on next you will see the below Screen shot which tells you
that the FileNet p8 Connector files are updating.

1. Configure Process Engine for IBM Content Navigator

This task registers the application and creates the IBM Content Navigator step processor in the
isolated region. Here you need to select the protocol, hostname, port number, admin username,
password and Process Engine Connection Point. P.S the below screen shot for more details.Enter the
below values and run task and ensure its Finished Successfully without an Error.

P a g e | 101
 2. Configuration of LDAP Server
ICN uses the content Engine LDAP repository to log into p8. We must configure the web application
server to use the Content Engine LDAP repository by entering values like Directory service provider,
LDAP repository type, hostname, port number. Enter the below values and run task and ensure its
Finished Successfully without an Error.

3. Configure the JDBC Driver for your Database.

This task adds the DB JDBC driver to the web application server environment variables so that the
web application can access information that is stored in a DB. This will configure the JDBC drivers for
the database where we store the navigator configuration data.

102 | P a g e
Enter the below values and run task and ensure its Finished Successfully without an Error.

Completion of JDBC Driver for your Database

P a g e | 103
 4. Configure Database and Data Source
ICN requires a DB. This task creates a data source connection that enables the web client to connect to
your DB. This task also creates a script that is used to create tables for each component that requires
access to the DB.

Test Connection Was Successful for Database and Data Source.

104 | P a g e
Completion of Configure your Database and Data Source.

5. Configure JAAS Authentication on your web application server.

This task updates the java authentication and authorization service (JAAS) settings on web
application server to enable the web client to authenticate user's login credentials.

P a g e | 105
6. Completion of Configure JAAS Authentication on your Web Application
Server.

7. Configure the Task Manager Component.

This task is configured to use task manager APIs to create and run asynchronous tasks from the web
client. This task is also required to delete team spaces. Below is the Screen shot of Starting and and
ending the Configuration of Task Manager Component.

106 | P a g e
8. Configure the IBM Content Navigator Web Application.
This creates the web application by using Configuration and deployment tool. Below is the screen shot
of Starting and Ending of ICN Web Application

9. Build the Web Application

P a g e | 107
It verifies and ensures that the EAR file do not contain any errors.

10.Deploy Web Application.

After performing the above tasks we need to deploy the EAR file and Script

Below is the Screenshot after the Web Application Deployment.

108 | P a g e
 IBM Content Navigator is successfully installed.

After configuring the above tasks in Content Navigator Task View, We need to go to Browser and login
to Content Navigator with the following URL i.e. http://localhost:9080/navigator and perform the

P a g e | 109
below tasks.

We need to connect to the repository before we configure parameters, folder, system properties an
so on.

110 | P a g e
After Connecting to the Repository we need to click on Configuration Parameters to select the
Workflow Connection point then save and close. We can override the default behavior of this
repository by setting the configuration parameters.

XX. Overview of Case Manager

Case Manager provides a way to quickly design, build and deploy a solution that is flexible enough to
handle Case Management Work.

Case Manager uses content Navigator as platform for the Content Manager and Case Managr Clients.

IBM Case Manager is a platform for designing and deploying solutions that help people gather the right
content, apply analytics for faster, more accurate decisions, and take action to assure better business
outcomes.

Please see the below steps for the installation of IBM Case Manager

P a g e | 111
Click Ok

112 | P a g e
P a g e | 113
Accept License in order to continue the Installation

114 | P a g e
In Below Screenshot you will see Workplace XT Detected why installing Case Manager

In Below Screenshot you will see Content Navigator detected while installing Case
Manager

P a g e | 115
Please specify the Installation Directory Path

In the below screen shot you could see the Disk Space required , product name an
Installation Directory Path

116 | P a g e
In the Below Screenshots you could see it extracts duplicates, installs cm_unistallter.exe
and installs JDK

P a g e | 117
Installing Add on

Expanding Case Builder, acmrest.war and Case Builder

118 | P a g e
P a g e | 119
120 | P a g e
Click Next and the Click on done to complete the Installation

Case Manager Successfully Installed

P a g e | 121
After the Installation Click on Start>Case Manager Configuration tool>Workbench and Create a
Profile. P.S. the below screen shots for Profile Creation.

Click on File>Create Profile

Click Next

122 | P a g e
Select WAS development environment profile and Give the Profile name

Set properties for WAS by entering the below installation path and user credentials

Test the connection and ensure its Successful

P a g e | 123
Set properties for WAS by entering the below installation path and user credentials.

Test the connection and ensure its Successful

124 | P a g e
Set properties for WAS by entering the below installation path, user credentials and Object Store

P a g e | 125
Select the tasks required for this Profile. You could ignore last three tasks as well i.e.

Configure Business Rules

Register the External Data Service

Deploy and Register Extensions package

After the above step you have to run task in the IBM Case Manager Configuration tool

126 | P a g e
 1. Update the Content Platform Engine Client Connector files
A Version of the Content Platform Engine Client connector files are installed on the IBM Case
Manager Server.

We need to run the task and ensure it is successfully finished.

P a g e | 127
 2. Configure the Case Management Object Stores
This task installs the Case Manager add-ons for the case management design and target object stores.

We need to run the task and ensure it is successfully finished.

128 | P a g e
 3. Define the Default Project Area
A project area groups solutions in the design object store so that the entire object store is not affected
when we reset the test environment. It's used for the development environment.

4. Create Case Manager Applications

This task adds the Content Platform Engine EJB URL value to the IBM Case Manager API WAR file,
adds the Case Manager Design object store name, adds Workplace XT context root to the Case Manager
Builder EAR file. We need to run the task and ensure it is successfully finished.

P a g e | 129
 5. Deploy the Case Manager API
This task deploys the IBM Case Manager Application file to application server. Case Builder and Case
Manager Client use the Case Manager API application to interact with CPE.

130 | P a g e
 6. Register the IBM Case Manager Services Plug-in
By running this task it registers the Plug-in for Content Navigator that contains the Case Manager
services that are used by other components.

7. Deploy Workplace XT
This is required for using Processor Designer from Case Manager Builder and is also required by Content
Navigator for displaying form policy documents in Case Manager Client.

P a g e | 131
 8. Deploy Case Manager Builder
This task deploys the Case Manager Builder EAR file to application server. This task makes the Case
Manager Builder application available for users.

132 | P a g e
 9. Deploy the Forms Application
This task is required to integrate forms into your case management configuration.

10.Register the IBM Case Manager Administration Client Plug-in

This task registers the plug-in for IBM Content Navigator that contains the admin client for Case Manager

P a g e | 133
 11.Register Project Area
This task registers a project area with a Content Navigator desktop, it creates default case manager
desktops, configure repositories for the case management design and target object stores and adds case
manager features to the desktop. Please see the second screen shot for details

Case Manager successfully installed and configured.

Hence FileNet Installation with Screen shots completed.

134 | P a g e
P a g e | 135
136 | P a g e
P a g e | 137