OpenText Documentum D2 FAQ

To rename the application URL to launch, stop the D2 service, change the
D:tomcatwebappsD2 folder name, change any reference to this URL in
D:tomcat… (such as
D:tomcatwebappsd2WEB-INFclassessettings.properties), and start the D2 service.

Most changes you make in D2-Config can be immediately applied by doing the following after making the change:
- Refresh the D2 Cache
  - In D2-Config, click Tools > Refresh cache then go to D2 and reset the workspace the change applies to. In some instances, you need to logout and log back in.
- Some changes require an application restart.
  - Stop the D2 webservice, clear the D2 cache and start the D2 webservice.

The number of results returned in search results is controlled by the maxResultSetSize parameter in D:tomcatwebappsd2WEB-INFclassesD2FS.properties

To remove the annoying, disruptive “Open DCMApp.exe?” dialog when logging into D2, refer to the KB located at Copy This Link To Browser After Logging Into OT My Support Portal Then Launch

To capture detailed console logs when debugging D2 applications, add ?logLevel=FINEST to the end of the application URL, such as: https://lmcge1ppdocwa01.cpnpp.net:11015/d2?logLevel=FINEST

The creation profile process if content is not allowed to be inherited/copied (properties only will be inherited/copied), the “Block inheritance modification” checkbox needs to be checked in the related Extended Creation Profile.

Dependent attributes on Property pages that are being filled from the data dictionary based on the entry of another attribute can have a timing issue. The attribute that is being returned from the dictionary cannot be in that object’s Properties Inheritance. The inheritance is applied at creation/import time and results in an error because the dictionary lookup has yet to finish. The data dictionary lookup only happens once the page has been loaded.

Be aware that when upgrading/migrating applications that used Java 7 or earlier, the date formats provided in future versions contain a comma between the date and time. To be able to use these older formats that do not have the comma, the following must be included on the content servers:
Update the Catalina.bat file (for the JMS) to include the JAVA option which provides backward Java compatibility:
-set “JAVA_OPTS=%JAVA_OPTS%
-Djava.protocol.handler.pkgs=org.apache.catalina.webresources
-Djava.locale.providers=COMPAT,CLDR”
Update the dfc.properties file to contain: dfc.date_format=MM/dd/yyyy hh:mm:ss a

To remove cabinets and folders where documents and records are stored due the following. On the DocListWidget in the Parameters section select Content type “DQL” and enter a DQL query that won’t return anything like “select * from dm_sysobject where r_object_id = ‘0000000000000000’;”
This will return an empty DocListWidget with default columns (object name, title, status, modified, modified by, etc…)

In the 22.2 version of D2 an attribute that has a Type of “ID” will not be available in the “Set property”, ‘Set properties” or “Set repeating property” drop downs in lifecycles. The attribute must be changed to a different Type.

Java methods in lifecycles and Actions in the lifecycles have a propensity to act on the same object at the same time.
- Example: A Java method was going through a process to update content and the lifecycle had an “Action type” of “Mark”.
- When these processes were running at the same time a “version mismatch” error was returned.
- The issue can be resolved by either adding a doc.save() to the Java method or moving the “Mark” to the Java method depending on the situation.
Java method actions run on the content server and actions run locally,
- Therefore they have different sessions and are apart of the same lifecycle.
- They run parallel.
- Therefore you can only modify the object from one or the other not both.

A bug has been found in the Admin widget when updating user information. This occurs when you are attempting to update a user that has an empty “User source” or is “None”. In this instance, if the User login domain field is added or changed, the update will not be applied. For some reason OpenText will only apply this update for users that have a User source of “LDAP”. The work around is to enter the needed User login domain update and enter “LDAP” in the User source. This causes the User login domain update to be applied. Then you go back in and put “LDAP” back to what it is supposed to be in the User source field.