c

************************************************************************************

PROBLEM RESOLUTION:

After configuring the DATA sources at CM Navigated to WAS-> Global security-> uncheck the -> JAVA
security option.

Configure the Federated repositories- and apply.

After creating Directory configuration wizard, I am able to see the domain permission window and by
default display administrator in wizard.

I did following things before running FEM

1. In Ldap I provided "administrator" as administrative console user.

re- run the ldap, bootstrap & deploy application.

2. After configuring the DATA sources at CM Navigated to WAS-> Global security-> uncheck the -> JAVA
security option.

- uncheck the java security settings on "Global security" home page.

- Configure the Federated repositories- check the administrative primary username as "administrator &
provided password. and apply
3. Restart the app server.

Now Click to FEM-> Add-> provided username as "administrator" and in baseDN & Group DN I provided
" dc=domain,dc=com" value. Earlier i provided "cn=users,dc=domain,dc=com" in both.

After completion of Directory wizard-> Domain permission wizard opens...

Set Statement Cache Size property
(WebSphere) Navigate to the WebSphere Administrative Console page containing the field Statement
Cache Size property. For example, in WebSphere 6.0.x, navigate to Resources > JDBC
> JDBC_provider > Data sources > GCD DATA SOURCE (all one by one) > WebSphere Application
Server data source properties.
Now adjust the WebSphere transaction timeout value

 Log on to the WebSphere Administrative Console.

 Navigate to Servers > Application Servers > server_instance > Container Services > Transaction
 Service, where server_instance is the name of the WebSphere server instance you created for
 Content Engine.
 Change the value of the Total transaction lifetime timeout parameter to 600 (seconds) or more.

CAUTION A large enough timeout value is critical if you are upgrading Content Engine from
version 3.5.x; otherwise, the upgrade may fail.
To enable the Log4j logging API
To allow Log4j logging by FileNet P8 client applications, the log4j.properties.client file is in the
FileNet/ContentEngine/config/samples directory. Before you can use Log4J logging in a FileNet
P8 client application, you need to move and rename this file as follows:
 Navigate to the directory FileNet/ContentEngine/config/samples, which contains the log4j files.
 Copy the file to the FileNet/ContentEngine/config directory.
 Rename the file you moved, log4j.properties.client, to log4j.properties.

Configure Content Engine ApplicationServer Database

Connectivity (WebSphere 7.0)
Now go to-> 1. Start the WebSphere administrative console (if it isn’t already running).

2. Navigate to Security > JAAS Configuration > J2C Authentication Data. In the right-hand pane,
note the alias created for the GCD database user, as you will use this alias for data source
connectivity.
Go to JDBC providers-> select JDBC providers for non XA:
From additional properties on right side-> click Data sources->Click new and enter details like:

 Data source Name: NONXANEW

 JNDI: NONXANEW
 Data source helper class: com.ibm.websphere.rsadapter.MicrosoftSQLServerDataStoreHelper
 Component-managed authentication alias: (JDBC provider ->Alias, means
,mypcNode01Cell/administrator
 Mapping-configuration- alias-: None
 Container- Managed authentication alias
 FINISH it

NOW under additional properties:

select ->Connection pool-> add value to maximum number of connection like: 1 to 120 (max 150)

Now->additional properties->Custom properties:

Name Value Type
1.databaseName ->ostore1-> java.lang.String
2.serverName-> <mypc> ->java.lang.String
3.portNumber ->1433 ->java.lang.Integer
4.selectMethod-> direct ->java.lang.String
5.enable2Phase ->false (for XA)->java.lang.Boolean
FOR NON-XA:
Now->additional properties->Custom properties:
Name Value Type
1.databaseName ->ostore1-> java.lang.String
2.serverName-> <mypc> ->java.lang.String
3.portNumber ->1433 ->java.lang.Integer
4.selectMethod-> direct ->java.lang.String
5.enable2Phase ->true (for XA)->java.lang.Boolean

Screen shot for XA datasource

Note: Now we have created these two CE datasources for XA & Non-XA (non distributed). Which
will helpful for us while creating Object store in FEM.

Next task is to create Object store in FEM:

Login to FEM-> Object store-> right click create new object store.

Please note that I have selected the File storage area and specified the path for shared directory.

Fill out the require details in wizard and finally finish that.

Verify Content Engine:

Before installing Process Engine, I am creating Process Engine ODBC data source and test the
connection(SQL Server only)

1. Start Program > Administrator Tools > Data Source (ODBC).

2. Click Add on the System DSN tab.
3. Select SQL Server as the driver to use for the new data source and click Finish.
Click OK to finish

Then ran the following .sql :

Select the vwdb database & then execute the following commands:
1. CreatePEinstallSP_3.sql
2.CreatePEinstallSP_2.sql
3.CreatePEinstallSP_1.sql

1. osql -E -D PEDS -d vwdb -i CreatePEinstallSP_3.sql -n -o output3.log

2. osql -E -D PEDS -d master -i CreatePEinstallSP_2.sql -n -o output2.log
3. osql -E -D PEDS -d vwdb -i CreatePEinstallSP_1.sql -n -o output1.log

PE_createDbUsers 'f_sw', 'f_maint', 'vwdb'

osql -E -D PEDS -d vwdb -i input.txt