Symptoms
Need to troubleshoot
the BOF user setup to allow connecting to a Global Repository/ Global Registry.
Cause
Troubles using BOF
(TBOs/SBOs) or using version 6 web clients and be caused due to incomplete or
incorrect configuration.
Resolution
To use BOF (TBO/SBO)
requires that at least one of your Repositories be designated as the BOF Global
Registry. Each Application Server must identify the BOF Global Registry it will
use via the dfc.properties file.
There are two parts to
setting up the BOF Global Registry:
1) making sure the
dm_bof_registry Repository user is active.
2) making sure that
the dfc.properties file on your Application Server(s) are correctly referencing
the Repository that is acting as the BOF Global Registry and has the listed the
correct user information for the dm_bof_registry user.
1. Verifying that a
Repository is the BOF Global Registry:
===================================
-Using Documentum
Administrator (DA), log into the Repository that should be the BOF Global Registry,
using an administrator account.
-In Classic view, in
the left navigation tree, click on the Administration node. In the page that
appears, under the heading "User Management", click on "Search
for Users".
-Search for the
following user: 'dm_bof_registry" (enter this value next to the User Name
label, and click Search).
-View the properties
of this user dm_bof_registry" (click the (i) icon).
-Make note of the
user's 'State' and 'User Login Name'.
If the user State is
'Inactive', then this Repository is not the BOF Global Registry. To make this
Repository the BOF Global Registry, follow Steps 2-4.
If the BOF Global
Registry user is 'Active', you need to verify some information in your
dfc.properties file on your Application Server(s).
From the Application
Server machine, locate the dfc.properties file.
Open this file in any
text editor. Ensure the following three attributes are set in the
dfc.properties file:
dfc.bof.registry.repository =
dfc.bof.registry.username =
dfc.bof.registry.password =
Without the above
three entries, the BOF Global Registry will not be set.
If these entries are
missing or values are not complete, you will need to add and populate these
values. See the following steps for more details.
2. Enabling the BOF
Global Registry
===================================
The following section
outlines the steps required to enable the BOF Global Registry using the
Documentum Administrator (DA) application.
-Log into Documentum
Administrator (DA) as an Administrator in the Repository where you want to
enable TBO/SBO functionality.
-In Classic view, in
the tree, click on the Administration node. In the page that appears, under the
heading "User Management", click on "Search for Users".
-Search for the
following user: 'dm_bof_registry" (enter this value next to the User Name
label, and click Search).
-View the properties
of this user 'dm_bof_registry" (click the (i) icon).
- The properties page
will appear. From the properties page, ensure the following options and values
are set to the following:
User State:
Active
User Source:
Inline Password
Restrict Folder
Access: System
- For security
purposes, change the default password (make a note of the new password).
- Click OK on the
'dm_bof_registry' user 'Properties' page.
3. Verifying the
dfc.properties file
====================================
On each Application
Server, locate the dfc.properties file. Open this file in any text editor.
Ensure the following three attributes are set in the dfc.properties file:
dfc.bof.registry.repository =
dfc.bof.registry.username =
dfc.bof.registry.password =
Without the above
three entries, the BOF Global Registry will not be set.
Note: The password
supplied in the entry 'dfc.bof.registry.password' must be consistent with the
password provided when setting the 'dm_bof_registry' password via Documentum
Administrator (DA). The password must also be encrypted. For information on how
to encrypt the password, see the next section in this document, entitled
'Encrypting Passwords for the dfc.properties file'.
4. Encrypting
Passwords for the dfc.properties file
===================================================
The password provided
in the 'dfc.properties' file must be encrypted. A utility is provided to
encrypt this password. The following section outlines the steps required to
invoke the password utility program to encrypt a password.
From a command prompt,
go to the $DOCUMENTUM_SHARED/config folder and execute the following:
java com.documentum.fc.tools.RegistryPasswordUtils <password>
Note- If you are using
java methods that use the TBOs/SBOs then you will need the following entries on
the %DM_Home/config/dfc.properties file as well
dfc.bof.registry.repository =
dfc.bof.registry.username
=
dfc.bof.registry.password =
===================================================
No comments:
Post a Comment