Quickflow

Quickflow is a predefined workflow that doesn'texecute any actions on the document. It sends the document from oneperson to another. The Quickflow has been part of the Serverproduct since the first version of 4i. In previous versions ofServer it was not called Quickflow. The template name for theQuickflow is sendToDistributionList which resides in the Systemcabinet.

Here are some steps to identify the workflow that thedocument belongs to:
- Get the task name -- You can get the task name by lookingat the inbox or querying the dmi_queue_item table

- Once you have the task name, run the following queries:

select object_name from dm_process where r_object_id in(select process_id from dm_workflow where r_object_id in (selectr_object_id from dmi_package where r_package_name ='<name of thepackage>'));

The result will be the name of the workflow associated to thedocument. Nevertheless, the Quickflow will always use thesendToDistributionList workflow.

Captial Projects File -> new greyed out in Project Configuration area or unable create picklist and other config objects

There will be reason like

1.Permission issues

2.membership issues

3.Config types missed in Content Rules of the project config folder.

But in my case the I have seen funny and intresting issue with objectlist component which is hidden configuration.

You can not see any error messgae logs because it is not error.

In the object list component we have configured columns based on folder path for the projects like below

<scope

                                location="/PROJECTS/PTDR-ABC/04. Master Documents/01. PROJECT COMMUNICATION,

    /PROJECTS/PTDR-ABC/04. Master Documents/01. Forms,">

                                <component id="objectlist"

                                                extends="objectlist:eif/config/library/objectlist/objectlist_component.xml">

unfortunately  there was comma”,” before close scope tag <01. Forms,"> so we have remove it and system behaving as expected

How to set a repository as Global Registry

To enable a repository as a global registry after configuration, you must activate the 
dm_bof_registry user. 
To enable a repository as a global registry: 
1. Access Documentum Administrator in a browser and connect to the repository. 
2. Click Administration- User Management- Users. 
3. Locate the user named dm_bof_registry and click the Information icon. 
4. Verify that the user name attribute is set to dm_bof_registry. 
The value dm_bof_registry is required. 
5. Optionally, change the user login name to a new value. 
6. Change the user¿s password. 
7. Set the dm_bof_registry user¿s status to Active. 
8. Click Ok to save the user. 
9. During DFC installation on client machines, such as the Webtop or Documentum Administrator hosts, provide the user login name and password. 
This updates the dfc.properties file and enables that DFC installation to contact 
the global registry as required. 
10. To manually modify the dfc.properties file to designate a global registry repository 
and user credentials: 
a. On the DFC host, navigate to $DOCUMENTUM/config (UNIX or Linux) or 
%DOCUMENTUM%\config (Windows). 
b. From a command prompt, execute the following command to generate the 
encrypted form of the global registry user¿s password: 
java -cp dfc.jar com.documentum.fc.tools.RegistryPasswordUtils 
password_of_user 
where password_of_user is the global registry user¿s clear-text password. In 
step d below, you will need to enter the encrypted form of this password in 
the dfc.properties file. 
c. Open the dfc.properties file in a text editor. 
d. Modify the following attributes: 
dfc.bof.registry.repository=global_registry_repository_name 
dfc.bof.registry.username=user_login_name 
dfc.bof.registry.password=encryped_password_of_user 
where encryped_password_of_user is the encrypted password you generated in 
step b above. 
e. Save the dfc.properties file.

Documentum Cloning

Documentum cloning steps

First way
*****************************************************************
Copying a Docbase.
This approach does not use Documentum’s “dump” and “load” utilities, but rather standard file and database schema copies. Paraphrasing the installation guide’s notes, and using “source” to refer to the Docbase being copied, and “target” to refer to the Docbase that will receive the copy:

• NOTE: It is recommended that you use a clean, unused Content Server as the target. You will have to change the security keys to match the source Content Server, which would impact any existing Docbases on the target.

• NOTE: The same OS must be used for both the source and the target Content Servers.

• NOTE: On the target Content Server, the OS user that will own the copied Docbase must have the same username and password as the OS user on the source Content Server.

• Stop the source Docbase.

• Note the name and ID of the Docbase you will be copying. You can look at the Docbase’s server.ini file to determine its ID: $DOCUMENTUM/dba/config//server.ini à look for the “docbase_id” parameter.

• Copy the file $DOCUMENTUM/dba/secure/aek.key from the source Content Server to the same location on the target Content Server.

• On the target Content Server, login as the same OS user that owns the Docbase in the source Content Server. Go through the standard process to create a new Docbase. You must use the same Docbase name and ID as the source Docbase. If you are manually creating the Docbase DB schema, it would be a good idea to use the same data and index tablespace names as used by the source Docbase DB schema, to facilitate import (later step).

• Stop the target Docbase.

• On the source Content Server, zip or tar the entire Docbase directory: $DOCUMENTUM/data//

• Export the Docbase schema from the source database.

• Connect as SYSTEM to the target database, and drop the newly-created target Docbase schema.

• Re-create an empty target schema of the same name/password:
SQL> create user 
2 identified by 
3 default tablespace 
4 temporary tablespace 
5 quota unlimited on 
6 quota unlimited on 
7 quota unlimited on ;
SQL> grant connect to ;
SQL> grant create session to ;
SQL> grant create sequence to ;
SQL> grant create table to ;
SQL> grant create view to ;

• Import the source Docbase schema export file into your new target schema that you just re-created.

• Connect to the new target Docbase DB schema, check the following, and make updates to refer to the 

new target Docbase location rather than the original source location:

o select r_install_domain, web_server_loc from dm_server_config_s;
o select host_name from dm_mount_point_s
o select target_server from dm_job_s;
o select projection_targets in dm_server_config_r;

• Run the following SQL statement in the target DB schema so that all views get rebuilt:
update dm_type_s set views_valid=0;

• Update the directory path information in Docbase DB schema

Below sql statements are examples of updating drive letter from E to C. 

update DM_LOCATION_S
set FILE_SYSTEM_PATH=replace(FILE_SYSTEM_PATH, 'E:\', 'C:\')
where FILE_SYSTEM_PATH like '%E:\%'

update DM_MOUNT_POINT_S
set FILE_SYSTEM_PATH=replace(FILE_SYSTEM_PATH, 'E:\', 'C:\')
where FILE_SYSTEM_PATH like '%E:\%'

• Copy the zip or tar of the source Docbase filesystem over to the target Content Server, and unzip or untar it into the corresponding target folder $DOCUMENTUM/data//.

• Edit the target server.ini file ($DOCUMENTUM/dba/config//server.ini), and ensure that the preserve_existing_types key in the SERVER_STARTUP section is set to TRUE:

preserve_existing_types=T
• Save server.ini
• Start the target Docbase

**********************************************************************
Same steps in other language

Cloning a Documentum Server

Part I – Preparing the Target Environment
Create same users & groups on target machine
Create /etc/services entries on target identical to source (Unix only)
Install Oracle with different sid 
Create Oracle user same as source 
Create tablespaces, etc. for docbase owner same as source
Verify server.ini settings if tablespace names change
Transfer .profile for dmadmin and docbase owner from source and modify Oracle sid and home settings. (Unix only)
Install Documentum Server on target – same version and patch level as source
Create a local Docbroker on target
Create target Docbase with same properties as source
Docbase name
Docbase ID
Docbase owner
During installation, modify the server.ini to reflect changes in index_store tablespace and add: preserve_existing_types = T
Ensure target Docbase projects only to target Docbroker
Shutdown target Docbase
Apply appropriate server patch
Start target docbase to ensure patch applied successfully
Shutdown target Docbase
Drop all tables in target database schema (Have dba do this)
Sample script:
Connect oracleowner/password@sid
Spool drop_schema.sql
Select ‘drop table’||table_name||’;’ from user_tables;
Spool off
@drop_schema
Verify schema objects no longer exist in target database

Part II – Transfer the database and content
Run LogPurge, DM_Clean and DM_Filescan on source Docbase
Run State of Docbase on source Docbase
Inactivate all jobs on source Docbase if any are scheduled to run during cloning
Shutdown the source Docbase
Export all objects owned by database owner from source database (dba)
(exp oracleowner/password@sid owner=docbaseowner file=docbasename.exp compress=y)
Import data into target database (dba)
(imp oracleowner/password@sid file=docbasename.exp)
Through Oracle, update hostname in target database (login as docbase owner)
Update dm_mount_point_s 
set host_name = ‘newhost’;
Update dm_server_config_s
set r_host_name = ‘newhost’;
Update dm_server_config_r
Set projection_targets = ‘newhost’ where projection_targets = ‘oldhost’;
Update dm_type_s set views_valid = 0;
Update dm_job_s
Set target_server = ‘docbasename.docbasename@newhost’ 
Where target_server = ‘docbasename.docbasename@oldhost’

On source, navigate to $Documentum/data/docbasename/content_store_01. Issue a ls –R | wc –l to get file count. (Unix method, do something similar on Windows)
Tar and transfer everything in $Documentum/data/docbasename/content_store_01. This will include all content beginning with hex-docbase id folder and full text indexes in verity folder. (Unix method, do something similar on Windows)
Untar content on target server.
Navigate to $Documentum/data/docbasename/content_store_01. Issue a ls –R | wc –l to get file count and compare to file count from source. Make sure they match! (Unix method, do something similar on Windows)
Tar and/or transfer the following files/directories: (Unix method, do something similar on Windows)
$Documentum/dba/config/docbasename/checkpass.cfg
$Documentum/dba/config/docbasename/dm_check_audit_pws. chown to root and chmod to 6777.
Re-start source docbase and re-activate jobs

Part III – Activate the Clone
Startup the clone server!
Verify connectivity through iapi and idql
Edit dmcl.ini on local client or application server to point to clone host machine
Log into clone through DTC or Webtop.
**********************************************************

Please note that checkout objects will not get cloned .Make sure you execute api for unlocking the objects: unlock,c,r_object_ id

Run all the 3 jobs 1) dm_filescan 2) dm_clean and 3) dm_consistency checker and start clonning of docbase

How to set Date defualt time

This feature is not supported in Composer as it is designed in that way .Feature request CMPSR-3839 was created to request adding this feature for future releases of composer. It is supported from Data Dictionary perspective.

The steps mentioned on the Feature request are as following :

Below are the steps:

1. Create custom type (set dm_document as super type) in Composer.

2. Create custom_attr with type as time.

3. Set the default value for the attr created in step 2.

you will not be able to set the default value for time

 try the following DQL:

ALTER TYPE your_type MODIFY (your_attr (SET default=NULL))  

When requesting a PDF rendition from a word file, the following error appears on the CTS logs: No Media Plug-in of type AdvancedPDF available to handle a 'document_to_pdf' transformation 14:12:00,722 DEBUG [ Thread-29] CTSPluginHandlerImpl - No Media Plug-in of type AdvancedPDF available to handle a 'document_to_pdf' transformation

And in the PDFAdvanced log, the process received a time out error as the files remained in Pending status.

Cause

This could be because the name of the CTS host is not the correct one on the Adlib Configuration.

Resolution

Check to see if the file is able to be proccessed directly through ADLIB.

If unable to process the file directly, even with ADLIB, and if the JOB status is still PENDING, then we should check the following.

In the CTS host:

1. In Program Files/Documentum/CTS/Adlib/Express, open the adexps.exe. 
2. In Configuration, check to see that the Default Option is selected.

In Program Files/Documentum/CTS/Adlib:

1. Open the Exponent Connector and click in Options.

  - Tab Processing : Check that the Exp Confg is the default.

  - Tab Exp Manager: Check that the host name is the correct one.

2. Open the Exponent Manager and click in Options.

  - Tab Processing: Check that the default option is selected.

  - Tab Exp Connector: Check that the host name is the correct one.

Add new format object

The icons that display for documents of various formats are located in the directory: /webtop/wdk/theme/documentum/icons/format/

Each format has 2 icons; a 16 pixel by 16 pixels GIF formatted image file and a 32 pixel by 32 pixels GIF formatted image file. You can edit / create these files in any image editing application which supports the export of these icons images as "Graphics Interchange Format" (GIF).

The file naming convention is as follows:

f_<format name>_16.gif

f_<format name>_32.gif

Where <format name> is the "name" attribute for the dm_format object that represents the format you are creating or modifying. In the folder contents view the 16x16 icon is displayed and in the properties page the larger 32x32 icon is displayed.

Example 1:

Create a custom icon for a format name "mp3", which is not already included in Webtop:

I started f_zip_16.gif and f_zip_32.gif are generic blank document icons.

I edited them in Microsoft Paint and saved them in the above icons/format directory, as:

f_mp3_16.gif and f_mp3_32.gif

Starting Webtop I imported an mp3 file and when viewing the folder contents the document displayed the newly created icon. Viewing properties on the new format should show your new large icon.

Example 2:

Create a new format in DA fir WinRAR archives.

Name: winrar

Default File Extension: rar

Windows Application: WinRAR.exe

Follow the same procedure above to create two custom icon image files and save them in the /webtop/wdk/theme/documentum/icons/format/ directory as:

f_winrar_16.gif

f_winrar_32.gif

Import a document with a .rar file extension and save it as a WinRAR format in the Docbase. View the folder contents and Properties of this document.

Restart the application server and you should see the custom icons you created for this format.

Let me know if you have any questions.