Archive for June, 2011

Presets in Documentum 6.5

June 9, 2011 1 comment

WDK (web development kit) customizations have been part and parcel of all custom Documentum WebTop applications. The customizations includes copying the WDK components (XMLs, JSPs, custom class etc) into the custom layer. Until version 5.3 SP6 there were no Documentum out of the box features that allowed developers to perform basic customization without having to customize the WDK components manually.

Documentum 6 and above version presented the idea of “Presets”. This versatile out of the box feature in Documentum enable Documentum developers to perform basic WDK customization/configuration with a few clicks of the mouse.

This Post  deals with the basics of Documentum presets and demonstrates a sample preset configuration.


Presets are out of the box feature in Documentum which enable Documentum developers to perform basic WDK customization/configuration with a few clicks of the mouse.Presets are easy to apply rules or configurations that can be created to bring in WDK configurations and setting without having to configure JSP’s pr XML’s manually. Though presets cannot completely replace WDK customizations, they certainly save time when used to make simple and common WDK changes in Documentum WebTop application.

Below an attempt is made to explain the various options available for presets and the way to configure them. Though all the options are being touched upon, for simplicity I am picking up an example preset which I will be using to disable the “FileàNewàDocument” option for all users except administrators.

 1. Presets option is available in Documentum WebTop once you have logged in as Documentum administrator. It can be seen in the left browser tree under Administration–>Presets

  1. When clicked on “Presets” the right panel will display the list of Presets if any exists.
  2. Use the menu bar option File–>New–>Preset to configure a new Preset

3. This will pull up a screen with the “Setup” tab pre selected. This screen offers the user with four options as shown below.

4. The four options are as follows

  1. Apply to User/Group/Role: This option enables us to configure a preset for a specific user/group or role. For example to configure a preset which would disable “Fileà NewàDocument” option for all users except the members of “admingroup” group, this would be the option to be selected.
  2. Apply to existing location: This option enables us to configure a preset for a specific location. For example if anyone wants to configure a preset that would enable /disable navigations or menu bar options for a particular folder or cabinet this would be the option to be selected.
  3. Apply to specific type: This option enables us to configure a preset for a specific object type. For example if anyone wants to configure a preset for dm_document( or any custom ) object type alone then this would be the best option.
  4. Apply to specific repository: This option enables us to configure a preset at the repository level. For example if anyone wants to configure a preset which would display only custom object types while creating a new document in WebTop for all users who are logged into a repository (docbase) then this would be the option they have to look into.

5. To continue with the steps, here we would be continuing by using option a mentioned above. Using this we would try to create a preset such that “FileàNewàDocument” option is disabled for all users who are members of “admingroup” group.

6. In the screen shown in step 4 click on “Select…” button for Apply to User/Group/Role: option. A screen as shown below will be pulled up to select the required group. In this example we will be selecting “admingroup”.Filter the required group and select it. Click OK

7. Once the group is selected, the next step would be to move to the “Rules” tab. Provide the “Preset name” and “Description” textbox and then click on Next button to move to “Rules” tab.

8. The “Rules” tab will present us with a screen which allows us to configure various entities with respect to the group we selected.

 Note : In this case these entities can be applied for group. As mentioned before (step 5) the same set of entities can be applied for other options,  that is the rules can be applied for type, docbase or location as well.

9. The above screen displays the following rules. For each rules there are configurations/actions that can be selected. Most of the options are self explanatory.

a. Permissions

b. Formats

c. Types

d. Groups

e. Workflows

f. Lifecycles

g. Templates

h. Actions

i. Navigation

j. Attributes

10 .Here since we are going to disable the menu item “File–>New–>Document” we will be selecting the option “Actions

11. When the option action is selected, an “Action Selector” drop down is presented to the user. We have the option to select a particular action and then add them to the “Excluded” list. Here we will be selecting the action “File–>New–>Document”.

12. Click “Finish” .The new preset is created and this will be visible in the Presets list. Refer image below.

13. The comparison between the screen shots taken for “File–>New–>Document” action before and after the preset is created.

Note: As mentioned in the steps above various kinds of Presets can be created. While planning to create presets, one thing to be borne in mind is that if a preset is applied to a group, location, docbase or type, it is not possible to create another preset for the same group, location, docbase or type.

More Details and Limitations of presets

Please refer Documentum WebTop release notes for more details and to know about limitations of presets.

  1. Presets are created as dmc_preset_package objects in Documentum
  2. WebTop presets reside in Documentum under the location given below    “Cabinets/Resources/Registry/Presets/Webtop/Preset Packages”
  3. A preset can be queried using the DQL select * from dmc_preset_package where object_name like ‘%<name of preset>%’

Any Points missed please mention it in the comments , will refresh the Post.

Configuring Documentum WebPublisher

June 7, 2011 Comments off

There has been a lot of Emails floating to me these days regarding  Documentum WebPublisher Configuration and Setup. I myself being newbie to WebPublisher could not reply back , so thought of coming back with a research and small Proof-Of-Concept at my end.

Before we start discussing about Documentum WebPublisher (WP) Configuration , here are few of the Pre-Requisites we need to take care:

The following Software / Components have to be installed before the actual services are installed:

  • Application server (e.g. Tomcat server) into Target Web Server
  • Database Server (e.g. MS SQL server)
  • Documentum Content Server
  • Web Publisher Server Files on Content Server
  • Web Publisher on target Web Server
  • Site Caching Service (SCS) Source on Content server
  • Site Caching Service (SCS) Target on target Web server

Documentum WP helps in Publishing the content from Documentum repositories.

Steps to create  &  publish the content:

 1.Create a workflow template using workflow manager.  User can either use the desktop version of workflow manager or web version that can be accessed from Web Publisher.

 To start creation of a workflow template using desktop version of workflow manager

 a) Open Workflow Manager.

b) Log in to Workflow Manager as Web Publisher administrator. A Web Publisher administrator should have super user permissions.

c) Choose File->Open. Browse to System->Applications->Web Publisher folder and select a Web Publisher default workflow. For example, Submit to Web site. This opens a default Web Publisher workflow on which to base custom workflow.

d) Choose File->Save As and save the workflow with a name that represents the workflow. All workflows must be saved in System->Applications->WebPublisher-><user_defined_workflow_folder>. Create a new folder or save workflows to the Web Publisher root folder.

e) Validate the template.

f) Install the new workflow template

g) Make it available through Web Publisher.

To access workflow manager from Web Publisher, log in to Web Publisher as a Web Publisher administrator.

Goto Administration – > Web Publisher Admin->Workflow templates and repeat the steps from c to g.

2.    Create a new category under Templates in Web Publisher. Goto Site Manager -> Templates and create.

3.    Import a template to the new category that is created. Template provides layout for content.

4.     Assign default life cycle and the newly created workflow to the template.

5.    Make the template available for use.

6.    Create a web cabinet in Web Publisher.

7.    Create a folder in web cabinet.

8.    Create content using the newly created template in Web Publisher.

9.    Create a site publishing configuration in documentum administrator

             i.        Start Documentum Administrator and connect to the docbase as a superuser.

            ii.         Click Site Publishing.

           iii.        Create a new site-publishing configuration.

      iv.        Set values in the site-publishing configuration:

a.    Click Active. In the Version field, type Active.

b.    Click Publishing Folder and browse the Docbase to the website folder (web cabinet).

c.    Type the target host name. This is the host where the SCS target software is installed.

d.    Type the target port for making connections to the target host. The port entered must match the port specified at the time of installation of SCS (DefaultPort , 2789)

e.    Type the target root directory to which user wants to publish the content. To publish web pages to Apache Tomcat, give this as target directory:

C:\Program Files\Apache Software Foundation\Tomcat 5.0\webapps\ROOT

f.     Choose the connection type.

g.    Click the Advanced tab. Select a new export directory or leave the default unchanged.

h.    Type the transfer user name, password, and domain. Enter the transfer authentication domain name that was provided during SCS target installation. Enter a valid username and password. Click Ok.

10. If the content that is created is not in a web-safe format, then convert it into web-ready format. This is done

a.    Login to WP as administrator and go to the Administration -> Web Publisher Admin -> Settings -> File Formats and define the file formats as “Web formats”, they will then be recognized as Web-safe formats.

b.    Set  a_special_app field of that content equal to “2” by update statement in DQL.

DQL query—

Update dm_document OBJECT SET a_special_app=’2’ where r_object_id=’<object id of the content which you want to publish>’

11. Log in to Web Publisher as Administrator.

12. Start the new workflow using Web Publisher.

13. Navigate to the content created.

14. Select the checkbox

15. Go to Tools

16. Select Workflow -> Start  

17. Assign a content author and web admin as administrator.

18.  Workflow tasks will appear in user’s inbox.

19. User can accept and forward the task to next user or reject it.

20. In Documentum Administrator, browse to the respective site configuration created. Select it and can then goto  tools tab ->Publish. Content is automatically published once it is approved.

Could not compress the article further , appreciate your patience, Hope the Post is useful and clarifies all the doubts as to How to Configure WP.

Awaiting Comments.

%d bloggers like this: