Monday, September 29, 2008

Controlled documents are not getting Promoted

1. Set the Classpath for following:

C:\Program Files\Documentum\Shared\dcm.jar
C:\Program Files\Documentum\Shared\dcmSupport.jar
C:\Program Files\Documentum\Shared\dcmQueue.jar
C:\Program Files\Documentum\dctm.jar

2.Where are queue manager Logs

C:\Program Files\Documentum\dcmQueueManager\docbases\\config\logs

3. Login into Documentum Administrator (DA)

Go to locations and locate the files listed.
Cabinets/System/Media Server/Command Line Files
dcmCustomProfile.xml
ProfileSchema.dtd
Cabinets/System/Media Server/Profiles
ProfileSchema.dtd
Cabinets/System/Media Server/System Profile
dcmCustomProfile.xml
ProfileSchema.dtd
register.xml

If the Profiles are missing copy the xml files from Content Server from:

C:\Program Files\Documentum\dcmQueueManager\docbases\dcm53sp1_o9i\config\profiles

4. Queue manager needs to be installed for every instance of the Docbase in case there are mutilple Docbases

5. Stop the Queue manager service and execute the following Query for DCM 5.3 spx

DQL> select * from dmi_queue_item where name='dcm_custom_job'

If there is no result set, then the request is not being sent to the Queue manager, and there is no Docbase instance against the Queue manager

- Install DCM Queue manager Instance Add or Remove select the Docbase for the Installation ( Start - Programs - Documentum- DCM Queue Manager Instance Add or Remove)

6. User needs to have Write Permission to Promote the Controlled Document or Should be a Coordinator to Promote CD.

7. If the QM is installed on D:\ drive, need to check if dctm.jar is being set correctly in the classpath.

8. Check if the Queue items are visible by running the following Query.

For DCM 5.2.5 spx:

DQL> Select * from dmi_queue_item where name = 'dm_mediaserver' (DCM 5.2.5 SPx)

DQL> Delete dmi_queue_item objects where name='dm_mediaserver'

For DCM 5.3 spx:
DQL> Select * from dmi_queue_item where name = 'dcm_custom_job' (DCM 5.3 SPx)
DQL> Delete dmi_queue_item objects where name='dcm_custom_job'

No comments: