A "new" FileNet® deployment
refers to any IBM® Connections
4.5 or 5.0 installation where you chose to create a new FileNet deployment when you installed IBM Connections Content Manager.
Follow this procedure only if you installed IBM Connections Manager for the first time and
are ready to set up the required data storage. The procedure does
not apply to a new FileNet deployment
that was migrated from an earlier version of IBM Connections, which already has the required
components nor does it apply to an existing FileNet deployment that was installed independently
of IBM Connections.
Before you begin
If you have set the value of login properties in your LDAP
configuration to be other than uid or if uid is
not the first value in the list of values, then the first <login>
attribute in the section of <loginAttributes> in profiles-config.xml needs
to match with the value that FileNet uses
to look up a user. Since by default, the uid value
is used and if the security principal for FileNet is not uid,
then you must modify the profiles-config.xml to
move the attribute that matches up with the principal to be the first
attribute in the <loginAttributes> section.
For example, if email is used as the principal,
then the <loginAttributes> section should
look like this:<loginAttributes>
<loginAttribute>email</loginAttribute>
<loginAttribute>uid</loginAttribute>
<loginAttribute>loginId</loginAttribute>
</loginAttributes>
Note: Make sure the CCM
shared file system is readable/writeable before running the tool.
If
you are unaware of the login properties settings, from the application
server's administrative console navigate to to find the settings
or contact your administrator. Find the JVM argument by navigating
to . The JVM argument needs to match the first value specified
in
<loginAttributes> as follows:
-Dcom.ibm.connections.directory.services.j2ee.security.principal={YOUR PROPERTY}
About this task
This procedure creates a new domain and object store for
the FileNet deployment.
Do not create a new domain or object store if you are migrating from
a previous version of Connections Content Manager.Procedure
- (Microsoft SQL
on Windows only) FileNet Collaboration Services
users need special permissions for the createGCD batch file to work.
Grant SQL Server permissions by adding the users to the SqlJDBCXAUser
role.
These are user accounts in Microsoft SQL Server. Whenever a SQL Server database is used, the
connection to that database is accomplished with a database user. A single database user needs to be
specified for each database; typically it's the same user for all databases. For more information,
see Understanding XA Transactions on the Microsoft Developer's Network.
- To create a P8 domain and Global Configuration Data (GCD),
perform the following steps:
- Locate the ccmDomainTool automation tool under the connections_root\addons\ccm\ccmDomainTool.
- Start the server where the Connections Content Manager
is deployed or start the Connections Content Manager cluster.
- (Non-Windows only) Set the executive permission by running
the command: chmod 755 *.
- Create the P8 domain and GCD as follows:
- For Windows platform,
run the command: createGCD.bat
- For non-Windows platforms, run the command: ./createGCD.sh
Click Y to regenerate a new dminfo.properties file.
Note: Optionally
specify a group name for administrative access.
- To create an Object Store and AddOns, perform the following
steps:
- Find the ccmDomainTool automation tool under the connections_root\addons\ccm\ccmDomainTool directory.
- Confirm you have created the domain and FileNet Global Configuration Database (GCD) either by
completing Step 2 or by creating them manually.
- Create the Object Store as follows:
- For Windows platform,
run the command: createObjectStore.bat
- For non-Windows platforms, run the command: ./createObjectStore.sh
Input the Connections administrator password (which is the FileNet Domain administrator).
Click Y to
regenerate a new dminfo.properties file.
- Be sure to restart the FileNet Engine
application from the WebSphere® Application
Server Integrated Solutions Console.
What to do next
Refer to Configuring collaborative features in FileNet to
learn about how to set up and maintain FileNet collaborative features.
Many
aspects of the FileNet configuration
are set up with defaults entered during your installation. You may
need to reconfigure some aspects of your FileNet deployment later, especially if user
information, authentication, or host names change after your initial
installation. Refer to Administering Libraries for additional information.