Secrets of DFC tracing

EPFM : When selecting two or more folders for content rules sub-folder types are Showing ecs ids instead of types

"Error 0 loading DMCL32.DLL. Make sure the DLL and supporting files are in your path"

issue we have index plus on the client computer and we forgot install the dfc.
solution:
Make sure the DFC installed on the client computer where you have installed index plus client.

How to get the repository log: (on CONTENT SERVER MACHINE)

It is <repository_name>.log you can find in <DOCUMENTUM_INSTALL_FOLDER>\dba\log  . 

How to get WDK logs: (on APP SERVER MACHINE)

By default, the log4j.properties (….found in <webtop_home>\WEB-INF\classes) will contain..

log4j.rootCategory=WARN, file, stdout
log4j.category.MUTE=OFF

log4j.appender.stdout.threshold=ERROR
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%d{ABSOLUTE} %5p [%t] %c - %m%n


log4j.appender.file.File=${user.dir}/documentum/logs/documentum.log
log4j.appender.file.MaxFileSize=10MB
log4j.appender.file.MaxBackupIndex=10
log4j.appender.file.Append=false
log4j.appender.file=org.apache.log4j.RollingFileAppender
log4j.appender.file.layout=org.apache.log4j.PatternLayout
log4j.appender.file.layout.ConversionPattern=%d{ABSOLUTE} %5p [%t] %c - %m%n

…we can leave it as such. The WDK log is the documentum.log.

Note: This will need an app server restart.

How to get DFC trace: (on APP SERVER MACHINE)

The "dfc.properties" file to use would be the one that Webtop uses. This should be found in the <webapp deployment directory>/webtop/WEB-INF/classes folder.  For instance if you were using tomcat on windows you might find the file in the following location
<webtop_home>\WEB-INF\classes.  

Can you try the following settings in your dfc.properties for capturing the DFC trace

dfc.tracing.enable=true
dfc.tracing.include_rpcs=true
dfc.tracing.verbose=true
dfc.tracing.mode=standard
dfc.tracing.log.level = DEBUG
dfc.tracing.timing_style=date
dfc.tracing.date_column_width=12
dfc.tracing.date_format=yyyy-MM-dd hh:mm:ss.SSS
dfc.tracing.max_stack_depth=10
dfc.tracing.include_session_id=true
dfc.tracing.dir=${user.dir}/documentum/logs/

and then send us on the resultant trace file from <$TOMCAT_HOME>\documentum\logs.

You can reset dfc.tracing.enable=false when you have captured the trace

How to make repository global repository manually? -- "No Global Registry Docbase found for host: xxxx"

Symptom

How to make repository global repository manually? and Install xPlore and configure a new index agent against any repository either Global or Non-Global. You may get an error: No global registry docbase found. However all apps are working fine.

The user has upgraded content server from 5.x to 6.x. Now they are trying to configure IA (xPlore), and has manually activated the global registry. This manual update process had missed to update object dm_docabse_config attribute docbase_roles[0] with value Global Registry. Though it's an internal attribute which is taken care automatically at the time of global registry configuration during docbase upgrade.

In case, it was updated manually then this issue is expected as when one configure IA (xPlore) against a repository regardless of Global or Non- Global, installer going to check global repository's dm_docabse_config attribute  docbase_roles[0] value if it's a Global Registry or not. If it won't find it, it going to fail with "No Global Registry Docbase found for host: xxxx"

Resolution

Follow solution ID esg106683 (listed below) to resolve the issue.

To enable a repository as a global registry after configuration, you must activate the dm_bof_registry user.

1.     Access Documentum Administrator in a browser and connect to the repository.

2.     Navigate to Administration > User Management > Users.

3.     Locate the user named dm_bof_registry and select View > Properties > Info to access the User Properties - Info page.

4.     Verify that the username attribute is set to dm_bof_registry. The value dm_bof_registry is required.

5.     Optionally, change the user login name to a new value.

6.     Change the user's password.

7.     Set the dm_bof_registry user's status to Active.

8.     Click OK to save the user.

9.     During DFC installation on client machines, such as the Webtop or Documentum Administrator hosts, provide the user login name and password. This updates the dfc.properties file and enables that DFC installation to contact the global registry as required.

10.   To manually modify the dfc.properties file to designate a global registry repository and user credentials:

1.     On the DFC host, navigate to $DOCUMENTUM/config (UNIX or Linux) or %DOCUMENTUM%\config (Windows).

2.     From a command prompt, execute the following command to generate the encrypted form of the global registry user's password: java -cp dfc.jar com.documentum.fc.tools.RegistryPasswordUtils password_of_user where password_of_user is the global registry user's clear-text password. In step d, enter the encrypted form of this password in the dfc.properties file.

3.     Open the dfc.properties file in a text editor.

4.     Modify the following attributes:
dfc.globalregistry.repository=global_registry_repository_name
dfc.globalregistry.username=user_login_name
dfc.globalregistry.password=encryped_password_of_user
where encryped_password_of_user is the encrypted password you generated in step b.

5.     Save the dfc.properties file.

In addition to the above instructions, one need to update dm_docabse_config attribute  docbase_roles[0] with value Global Registry in  order to avoid below xPlore index Agent configuration issue against the global repository.

"No Global Registry Docbase found for host: xxxx"

iapi>retreive,c,dm_docbase_config
iapi>set,c,l,docbase_roles[0]
data>Global Registry
iapi>save,c,l
iapi>reinit,c