Archive

Posts Tagged ‘SQL’

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.

MORE ABOUT DQL

October 24, 2010 Comments off

DQL is used by administrators, developers, and applications to retrieve  information from the Content Server .DQL statements operate on objects and sometimes on tables/rows while SQL statements only operate on tables/rows.

Building blocks of a DQL statement  includes,

Ø  Literals, which describes the literal formats for the Documentum datatypes

Literals are values that are interpreted by the server exactly as they are entered. Content Server recognizes .Five types of literals:

§  Integer literals

§  Floating point literals

§  Character string literals

§  ID literals

§  Date literals

Ø  Special keywords which describes the special keywords that can be used in DQL

Special keywords have special meanings for Content Server when used in a DQL query. (They cannot be used in API methods.) Some  keywords are:

§  USER, which identifies the current user

§  TRUE and FALSE, which represent the Boolean true and false.

§  DM_SESSION_DD_LOCALE, which represents the data dictionary locale.

Ø  Functions which describes the functions that can be used in DQL queries

Source:www.scribd.com/doc/11468134/DQL-Reference-Manual-65

Functions are operations on values. DQL recognizes three groups of functions and two unique functions:

  • Scalar functions: Scalar functions operate on one value and return one value.
  • Aggregate functions: Aggregate functions operate on a set of values and return  one value.
  • Date functions:Date functions operate on date values.
  • The ID function:The ID function, a unique function recognized by DQL, is used in   the FOLDER and CABINET predicates and in the IN DOCUMENT and IN ASSEMBLY clauses.
  • The MFILE_URL function:The MFILE_URL function returns URLs to content files and   renditions in particular format

Ø  Predicates  which describes the predicates that can be used in expressions in queries

Predicates are used in WHERE clauses to restrict the objects returned by a query. The WHERE clause          defines criteria that each object must meet. Predicates are the verbs within the expression that define the        criteria.

DQL recognizes these predicates:

Arithmetic operators

Comparison operators

Column and attribute predicates

SysObject predicates

Ø  Logical operators describes the logical operators supported by DQL

Logical operators are used in WHERE clauses. DQL recognizes three logical operators:

  • AND
  • OR
  • NOT

Any number of expressions can be joined together with logical operators. Content Server imposes no limit. (Underlying RDBMS may impose a limit.) The  resulting complex expression is evaluated from left to right in the order of precedence of the operators. This order, from highest to lowest, is: NOT,AND,OR

Ø  DQL reserved words which is a  list of the words reserved in DQL

DQL reserved words should be enclosed in double quotes when using in a DQL query. some keywords are

  • ABORT
  • COMMIT
  • CHECK
  • ENABLE
  • ALL
Categories: DOCUMENTUM Tags: , ,

Sharepoint- Technical and Non-Technical Overview

May 31, 2010 Comments off

SharePoint at the Technical Front can be best described as :

A. Currently hosting multiple products:

1. Windows SharePoint Services 2003 and 2007(WSS)
2. SharePoint Portal Server 2003 (SPS)
3. Microsoft Office SharePoint Server 2007 (MOSS)

B. SQL Back-End servers of data feeding Web Front-End servers that render content.

C. Many complex technologies working together to create powerful, but easy to use tools.

Non-Technical Overview of SharePoint:

A. Web-based collaboration tool

B. SharePoint involves many complex technologies (SQL, IIS, and Office Client), it is designed to be easy-to-use and easy-to- understand.

C. Quick and easy way to create complex websites

D. Integrates with Office Applications

E. Flexible framework:

1. Short or long term data sharing
2. Private or public collaboration
3. Online or offline collaboration
4. Scalable

Some of the Common Uses and Solutions of SharePoint :

1. Team collaboration using several elements (Files, lists, surveys, discussions)

2. Publicly accessible presentation or “splash” page for information

3. Free form information sharing using Blog/Wikis

4. Access point for gathering data via survey or forms

5. Meeting Workspaces.

6. Personal Sites

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