nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Documentum Time Zone Arithmetics??

vfr400

We load documets into documentum by batch jobs. These documents have date attributes.
If the import file contains a date: 3/15/2010 00:00:00, this date is stored in the database (its a orcale, check done via sqlplus)

as 14-mar-2010 23:00:00. Formatting is not a problem. The problem is, it is an hour earlier.

When displaying that date in webtop / properties of the document, it is displayed as 3/15/2010 00:00:00.

Here takes (I strongly assume this) some time zone arithmetics place.

The problem now is: We have a dfc application embedded in webtop, which does a search. You can enter a date in a datetime action control, the associated java code creates a dql statement , runs it on the server and the resultset is returned.

If we select 15-mar-2010 in this search application, we get all documents from 16-mar-2010 as result. Time Zone arithmetics does not take place here.

So now I am a bit in trouble as searches do not work correctly. Two solutions come into my mind:

1) Get documentation how this timezone artithmetics is handled by content server or dfc or any involved product and do it right.

2) Disable time zone arithmetics in cs or any other component. Take any date as it is, documentum!! HAH! (thats the one I'd prefer)

Any clues how I cat achieve one of these goals?

Find more posts tagged with

Comments

DCTM_Guru

1) Read the Content Server Admin Guide for more info on time zone

2) Are all you servers located in the same time zone? If so, then you should be able to do this (read documentation for #1). The time zone offset was created to support distributed location of the various servers.

vfr400

I found out, that documentum assumes that all date values entered are meant to be in the local timezone. Then the datevalue is converted to UTC and stored in a db. The only thing I came about that does not convert to UTC is the datetime control. (dfc 6.5 that is). You have to do the conversion by yourself.

Thats how I did it:

    private static final String DOCUMENTUM_DATETIME_FORMAT    = "MM/dd/yyyy hh:mm:ss";


    public static String convertLocalTimeToUTC(Date localDateTime)
    {

        SimpleDateFormat     doc_formatter;

        try
        {
            doc_formatter = new SimpleDateFormat(DOCUMENTUM_DATETIME_FORMAT);
            doc_formatter.setTimeZone(TimeZone.getTimeZone("UTC"));
            return doc_formatter.format(localDateTime);
        }
        catch (Exception e)
        {
            System.out.println("convertLocalTimeToUTC: converting " + localDateTime + " throws " + e);
            return "";
        }
    }

GhostMile

Is there CS Administration Guide version 6.6?

The handling of the dates is changed as of version 6.6 and the latest Admin Guide is 6.5.

How to deal with this?

DCTM_Guru

Yes, it should be in the same place as the rest of 6.6 content server download.

GhostMile

Well, it maybe should be there, but it's not, or I can't find it.

It is also not listed in the release notes.

DCTM_Guru

I stand corrected. I just checked powerlink as well and I dont see 6.6 CS Admin Guide. This typically means that there's nothing new and using 6.5 should suffice.

Where did you see that handling of dates has been changed in 6.6?

msroth

I wrote a blog post that explored a similar issue as yours last May. Perhaps it contains some insights for you.

http://msroth.wordpress.com/2011/05/15/the-content-server-and-time-zones/