Use the IBM® FileNet® Collaboration Services
(FNCS) Configuration Manager to re-configure FNCS 2.0.0.1 to support
changes to IBM Connections Content
Manager; for instance, when a host or port that is used to connect
to Connections Content Manager is changed.
Before you begin
Set any relevant properties and respective values in the <FNCS_Install_Location>/configmanager/profiles/fncs-sitePrefs.properties as
described in Site preference parameters of the IBM FileNet P8 Information Center. In particular,
set anonymousAccessEnabled=true and enablePropertySheetTemplateMinMax=true.Important: Set the properties fncsServerURL and fncsServerURLSecure to
the base URL used to address FileNet Collaboration
Services, for example, http://example.com and https://example.com.
Set the icURI property to the base URL used
to address IBM Connections,
for example, http://example.com. These values
might need to be changed if you have configured a security proxy such
as Tivoli® Access Manager,
which changes the URL or hostname that end users use to access your
deployment compared to your HTTP server.
About this task
The following procedure explains how to re-configure FileNet Collaboration Services
that are embedded with a new installation of FileNet from Connections Content Manager.For
an existing FileNet installation,
refer to the FileNet Collaboration
Services Information Center for a complete list of
configuration options available. For IBM
i, CCM configuration with an existing FileNet installation is
only supported.
With Connections Content Manager and a new FileNet deployment, these configuration
options are available in <connections_install_root>/addons/ccm/FNCS/configmanager/profiles,
for example: /opt/IBM/Connections/addons/ccm/FNCS/configmanager/profiles
on Linux
Procedure
- Run one of the following commands depending upon your operating
system:
- Click OK to use the configuration
manager.
- Ensure that the following prerequisites are satisfied and
then click Next:
- Content Platform Engine is installed and running
- Application servers are configured.
- Single signon is enabled.
- Installation and configuration sheet for FileNet Collaboration Services is available
and populated with values for your environment.
- Enter the Content Platform Engine (CPE) information as
follows:
- Determine the port number for the CPE iiop:// URL by
opening the IBM WebSphere® Application Server's administrative
console that manages the server where the CPE application is running.
- Navigate to where <server_name> is
the name of the server hosting the CPE.
- Under the Communications area, expand the Ports list
and make note of the port for BOOTSTRAP_ADDRESS,
the port to be used for the CPE iiop:// URL.
- Enter the name of the object store the FileNet Collaboration Services application
references that to be used or already is being used for IBM Connections.
- Clear Test the connection to the Content Platform Engine and
then click Next.
Note: The iiop URL is used during installation and configuration
but is not used during program execution. When you use the Connections
installation program to install FileNet,
an instruction is added as a JVM: -DFileNet.EJB.ContextProperties=java.naming.provider.url=! This
instruction directs FileNet to
use a local EJB always instead of using a remote EJB located through
iiop when you connect between FileNet Collaboration
Services and the FileNet Content
Engine. If you deploy FileNet Collaboration
Services to a cluster, make sure that this JVM argument exists on
all cluster members.
- Select None for the Web
client application or select the web client application
that you want to use to view your documents and supply the appropriate
details, and then click Next.
- Enter the IBM Connections
HTTP URL and then click Next. If
you the HTTP server is configured tto handle web requests for IBM Connections, then enter its
URL here.
- Select the version and location of WebSphere Application Server where you
want to deploy the FileNet Collaboration
Services application, and then click Next.
- Specify the WebSphere Application
Server profile information that you use to deploy the FileNet Collaboration Services application
and supply the administrator credentials and then click Next. If you are redeploying the FileNet Collaboration
Services application, then choose the same profile that the application
is already deployed on.
Note: If your FileNet is deployed by Connections, choose
the profile of Deployment Manager.
- Select whether to deploy the FileNet Collaboration Services application
on a single application server or in a cluster. If you are redeploying
the application, choose the same option that the application is already
been deployed on, and then click Next.
Note: The cluster or single server must already be created.
- Select the cluster name (or server name, if you chose the
single application server option in the previous step) where you want
to deploy IBM FileNet Collaboration Services application.
Choose the same cluster name (or server name) where the application
is already deployed to if you are redeploying the application. Click Next.
- If you already changed the name of the IBM FileNet Collaboration
Services application, then change it now to that same name. If Filenet
is already installed by Connections, the default application name
is FNCS (If you update it to fix pack 1, make
sure the application's name appears as FNCS in
UPPERCASE). Click Next.
- Review the information that you entered to ensure its accuracy
and then click Next.
- When the Deployed successfully summary
panel displays, click Done to complete the
configuration of the FileNet Collaboration
Services.
- Log in to the WebSphere Application
Server Integrated Solutions Console for the Deployment Manager, and
click .
- Select the check boxes for the nodes and click Full
Resynchronize.
- Install the authentication filter code as follows. The
authentication filter must be reinstalled every time FNCS is re-configured.
- In WebSphere Application
Server administrative console, navigate to WebSphere Enterprise Applications.
- Select the FileNet Collaboration Services option.
- Click Update.
- For Application update options, select
the Replace, add, or delete multiple files option.
- Select local file system if you are running
the browser on the Deployment Manager node, and then locate the auth_filter_patch.zip file
in the connections_root/ccm/ccm/ccm/auth_filter_patch/auth_filter_patch.zip directory.
Note: If
the browser is not running on the Deployment Manager (DM) node, then
select remote file system and choose the DM
file system, locating the auth_filter_patch.zip file
in the directory previously stated.
- Click Next and OK to
update the application.
- Reset the OAuthClient security role to user/group mapping
as follows:
Note: You must reset the OAuthClient mapping
every time FNCS is re-configured.
- In the WebSphere Application
Server administrative console, navigate to WebSphere Enterprise Applications.
- Click the FileNet Collaboration
Services application (fncs).
- Under Detail Properties, click Security
role to user/group mapping.
- Select the OAuthClient option.
- Under Map Special Subjects, click All
Authenticated in Application's Realm and click OK to
save changes.
- Click Save to save directly to
the master configuration
- Restart the FileNet Collaboration
Services (FNCS) application
Results
A summary supplies suggestions of how to confirm that the
service is up and running.