Presets node in Webtop is greyed out

Cause

The presets mechanism requires a number of configuration conditions to be true in order for it to function. The troubleshooting steps in the Resolution section cover common issues that result in this problem, such as authentication problems, installation issues, etc.

Resolution

Troubleshooting Steps:

1. Make sure the repository is up and running during the wdk applications start up or deployment. 

2. Make sure the Webtop DocApp is installed in the repository. This will insure that the dmc_wdk_presets_owner user exists. 

3. Make sure presets are enabled (default setting) in /wdk/app.xml.

In wdk/app.xml, we have the following configurable elements for presets, check to see if this has been customized in other layers.

<presets>

         <!-- Presets -->

         <presets>

            <!-- Enable/Disable Presets -->

               <enabled>true</enabled>

            <!-- Version of preset package definitions (PresetVersion_x.x is r_version_label value of preset defs)-->

            <version>1.3</version>

            <!-- Repository folder containing preset package definitions and preset packages -->

            <repository_path>/Resources/Registry/Presets/Webtop</repository_path>

            <!-- If repository is blank, the dfc global registry repository will be assumed as the preset repository -->

            <repository></repository>

            <!-- Encrypted password for default preset user "dmc_wdk_presets_owner" -->

            <!-- If password is blank, default password will be used -->

            <!-- To create an encrypted password, execute the following command at a command-->

            <!-- prompt: -->

            <!--    java com.documentum.web.formext.session.TrustedAuthenticatorTool <password>-->

            <!-- The utility sends the encrypted password to the standard output-->

            <password></password>

            <!-- Interval to check for preset package changes in repository  -->

            <!-- Each execution is scheduled relative to the actual execution time of the previous execution -->

            <refresh_period_seconds>3600</refresh_period_seconds>

            <!-- Preset scope definition names may optionally be mapped to a different IQualifier scope name -->

            <scope_name_mappings>

               <scope_name_mapping>

                <preset_scope_definition_name>group</preset_scope_definition_name>

                <qualifier_scope_name>role</qualifier_scope_name>

               </scope_name_mapping>

            </scope_name_mappings>

         </presets>

4. Make sure the user who has the role dmc_wdk_presets_coordinator has WRITE permissions on the presets storage folder in the global repository (default storage folder is /Resources/Registry/Presets/Webtop).

5. Open the admin node and make sure the user shows up in the dmc_wdk_presets_coordinator role.

6. For presets, wdk applications uses a internal named user called, dmc_wdk_presets_owner, to access the preset data.  Check to see if this user is created in the global / designated presets repositories (you can verify this with IAPI). If this user is not available, then you may need to install the correct docapp. Installing the presets docapp as mentioned in Point 2 creates this user.

7. Check to see if the password for the dmc_wdk_presets_owner has been changed from the default "webtop".
If it has, then the wdk app.xml must be updated accordingly, by adding the encrypted password to the <presets><password> element. Use the TrustedAuthenticatorTool to encrypt the new password.

8. If the repository and / or password data is configured, check for the correctness of the values. The password must be a base64 encoded string, if specified.

9. To confirm the Business Object Framework (BOF) actually pulls down all the Webtop preset jar files and Webtop definition files from the global repository, check the BOF cache folder on app server. This is usually in c:\[tomcat install dir]\bin\documentum\cache\6.0.0.085\bof\[docbase], check the content.xml and confirm if all the preset jar has been downloaded.

To confirm the Webtop definition and properties also were pulled down by BOF, check

c:\<tomcat_install_dir>\bin\documentum\presets\<wdk_app> folder e.g. c:\<tomcat_install_dir>\bin\documentum\presets\Webtop, the number of files in this folder should equals the number of result that the following DQL return.

DQL>

select object_name, r_object_id, i_vstamp, r_version_label from dm_document (ALL)
where (object_name like '%.definition' or object_name like '%.properties')
and FOLDER('/Resources/Registry/Presets/Webtop')
and any r_version_label = 'PresetVersion_1.0'
union
select object_name, r_object_id, i_vstamp, r_version_label from dm_document
where (object_name like '%.definition' or object_name like '%.properties'
and FOLDER('/Resources/Registry/Presets/Webtop')
and (object_name not in (select object_name from dm_document (ALL)
where (object_name like '%.definition' or object_name like '%.properties')
and FOLDER('/Resources/Registry/Presets/Webtop')
and any r_version_label = 'PresetVersion_1.0')))

10. Check to make sure dm_world has at least READ permission on the /Resources cabinet.

Additional Information / FAQ: 

Q1. Is it obligatory that dmc_wdk_presets_owner must be a member of the dmc_wdk_presets_coordinator role " 

A1: dmc_wdk_presets_owner is an internal user used to read the preset data from the repository. If the logged in user is in dmc_wdk_presets_coordinator  role, then that user can edit the presets.

Q2. Is the dmc_wdk_presets_owner the only user who is responsible for connections with the "presets repository" " 

A2: Yes, it is the only user that talks to the presets repository.

Q3. What is the default password for the dmc_wdk_presets_owner user " 

A3: webtop

General Information on dmc_wdk_presets_owner: 

The PresetService uses this user name to establish a session to the preset repository when retrieving or creating Presets, via the Presets user interface in Webtop. Therefore, this user is the owner of all Preset Package objects. The user is created by a pre-processing script in the Webtop DocApp. The user has restricted folder access to only folders needed to manipulate preset packages.  The user name is hard coded in WDK and is not overridable. The default password is "webtop".  The password is hard coded in WDK but can be overridden by setting the <presets><password> element in wdk's app.xml.