Archive

Posts Tagged ‘dmcl.ini’

Documentum Traces

November 4, 2010 Comments off
Tracing is one of the easiest and excellent way to troubleshoot complex issues in Documentum.
There are 5 Types of Traces i can think of :
  • DMCl Trace
  • SQL Trace
  • Method Server Trace
  • DFC Trace
  • Authentication trace

1. DFC trace

Description:

This is to trace all the requests that use the Documentum foundation classes.

Steps:

To do this you need to add the following flags to the %DOCUMENTUM%\config\dfc.properties file:

#
# Specifies whether to combine the trace of dmcl along with other traces.

#
dfc.tracing.combineDMCL=true

#
# Specifies whether to enable or disable trace.
#
dfc.tracing.enabled=on

Once you save the file the tracing starts.
You don’t require restarting the Application Server but it can create extremely large logs. Because of this reason it is best if you enable the tracing just before you are ready to replicate the problem and disable it just after you finish replicating the problem.
To stop the tracing change the flag value to false:

#
# Specifies whether to enable or disable trace.
#
dfc.tracing.enabled=false

Remember you need to save the file for the change to take effect.

The information is saved in the %DOCUMENTUM%\logs\trace.log file unless you have modified the default configuration in the %DOCUMENTUM%\config\log4j.properties file if you are not sure you can check this flag:

log4j.appender.FILE_TRACE.File=C\:/Documentum/logs/trace. log

2. DMCL Trace

Description:

This is to trace all the requests that go from the Documentum clients to the content server.

Steps:

Go to the dmcl.ini file and add the following two lines

trace_file=<specify the location where you want the file to be created>

trace_level=<1-10>

3. SQL trace

Description:

This is to trace all the requests that go from the Content server to the database and it is logged automatically to the docbase log.

Steps:

This is done at the content server box

Go to the Documentum Server Manager and select the docbase on which you want to enable the trace.

Go to edit service and add the following line at the end

-osqltrace

Trace is generated on the docbase logs which can be found in

DM_HOME/dba/logs

 

4. Method server trace

Description:

This is to trace all the requests that go to the Method server.

This is done at the content server box

Go to the Documentum Server Manager and select the docbase on which you want to enable the trace.

Go to edit service and add the following line at the end

-otrace_method_server

Logs are in %DOCUMENTUM%\dba\log\<repository_id>\MethodServer\MethodServer\server_config_name.log

 

5 .Authentication Trace

Description:

This is to trace the all the authentication mechanisms in a docbase.

This is done at the content server box.

Go to the Documentum Server Manager and select the docbase on which you want to enable the trace.

Go to edit service and add the following line at the end

-oauthentication_trace

Trace is generated on the docbase logs which can be found in

DM_HOME/dba/logs

Appreciate any comments.

Configurational Tips for Documentum Webtop

March 30, 2010 Comments off

Below i tried to cover the scenario where multiple docbases are configured and provides a solution to various business requirements that may arise out of this kind of set up. It also illustrates the configurational change that makes webtop (till version 5.3 SP4) compatible with Internet Explorer 7.0.

1.   Accessing multiple docbases from single machine

Business Scenario: There are multiple environments (say Development, Test, Staging and Production). Each has its individual content server but the requirement is to connect to any one of these environment through a single application server.

Solution: Add the different docbrokers in dmcl.ini as backup. This allows the application server to connect to the docbase for which the login credentials are passed.

The content server requires user id, password and docbase name as the parameter for creating a session for the user. The request from application server first goes to the docbroker specified as primary. If the parameters passed in the request matches with that of the docbase listening on the primary docbroker, the session will be created otherwise the request will be forwarded to the backup docbroker specified in the dmcl.ini in the ascending order.

Configuration Text File

This solution works for the following scenarios:

  1. If the docbase name in the different environments is different (or even if the case is different i.e. docbase_name and DOCBASE_NAME are treated as different docbases).
  2. User id or login ticket is unique.

2.   Defaulting docbase on login screen in webtop

Business Scenario: Multiple content management applications are sharing the same set of content and application server. The docbase and webtop is separate for each of the application. The requirement is to default the docbase name in the webtop login screen for each of the application.

Solution: Add the following code snippet in the app.xml file located under webtop\custom folder.

<authentication>

        <!– Default domain and docbase to authenticate against –>

       <domain></domain>

       <docbase>docbase_name</docbase>

</authentication>

3.   I.E. 7 Compatibility

Add the following code snippet to app.xml file located under webtop\custom folder to make webtop (till version 5.3 SP4) compatible with Internet Explorer 7.0.

<browserrequirements>

     <windows>

          <ieversions>6.0,7.0</ieversions>

          <netscapeversions>7.2</netscapeversions>

          <firefoxversions>1.5</firefoxversions>

     </windows>

</browserrequirements>

%d bloggers like this: