Archive

Posts Tagged ‘dmcl’

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.

DBOF Configurations

May 5, 2010 Comments off

We Know DBOF lives wherever DFC lives, either on the Content Server or Application Server, or on any of the other clients. The following Steps need to be tracked when we are trying to configure DBOF :

1) Configure DMCL.ini to both access DocBase and enable session pooling. Add the following entry to the [DMAPI_CONFIGURATION] section :

connect_pooling_enabled = T

When installing Documentum, a file with the name DMCL.ini is created in the folder

‘:/SYSROOT\system32’.

Example: C:/SYSROOT/system32.

2) Make sure dfc.jar is referenced by the CLASSPATH environment variable of your JVM running the application, dfc.jar is in ‘Shared’ folder under Documentum installation folder.

Example: C:/Program Files/Documentum/Shared

3) Make sure dmcl40.dll is in a directory referenced by the PATH variable. By default the file is placed in folder C:/Program Files/Documentum/Shared.

4) The DFC_DATA system variable must refer to the directory containing Documentum configuration information, usually C:\Documentum. This needs to be a directory that has an immediate subdirectory called C:\Documentum\config. This is where the dbor.properties file is also located.

5) Make sure TBO classes and SBO classes are configured in dbor.properties file on
Application Server.

6) The dbor.properties is editable file. As part of best practices the file should be edited by a program using IDfDbor and IDfDborEntry interfaces provided in DFC classes.The entries in dbor.properties file will
look like:

doc_request=type, com.bp.customObj.DocumentRequestTBO, 1.0
com.bp.customObj.ICreateFolderSBO=service,com.bp.customObj.CreateFolderSBO,1.0

DocumentRequestTBO, ICreateFolderSBO and CreateFolderSBO are the java classes
created for providing our own business logic.doc_request is the custom object type defined in DocBase. One can create custom object types using Documentum DA. ‘type’ represents Type Based Object followed by full class name, 1.0 represents the version number of the class to be used.

The second line represents the mapping of SBO, as the identifier ‘service’ mentions.

7) Make sure TBO and SBO compiled classes are accessible from class path variable on
Application server.

I will try to bring in how to implement the concept of BOF in Documentum in my coming Posts.

Appreciate your comments.

Categories: DOCUMENTUM Tags: , , , , , , ,
%d bloggers like this: