Home > DOCUMENTUM > D2 Plugins and Customization…

D2 Plugins and Customization…

August 19, 2019

Customizing D2- What is Possible?1-e1566236184837.jpg

2.jpgHow does Content Check-in Service work in D2?

The content checkin process uses IDownloadService.getCheckinUrls() service to perform the checkin operation as a single and/or atomic operation. We first cease the usage of the checkin() and getUploadUrls() services and use the getCheckinUrls() service.

D2-Specs Plugin

 Automatically design technical specifications of D2 product

  • Generate a document that compares two different configurations.
  • Using Module Description, we can describe the various elements of our configuration matrix.
  • Once modules are described, we can generate application specifications.
  • We can include dictionaries and taxonomies in the technical document.
  • All the configurations differences are listed into a PDF document
  • All the differences between the two configurations are listed into tables organized by types and modules.


BOCS sits on a separated host, nearer to customer needs. A server machine with only an OS installed, so this machine does not need Documentum or DB to be installed. The host will be used only to install BOCS and DFS. On the content server, it is required to have a DMS installed and running.


D2 is integrated with Documentum Retention Policy Services. RPS policies and markup that apply to a selected document can be displayed, and operations on documents will conform to retention policies.

If we install D2-RPS-CONNECTOR, this will add a set of PDF control capabilities to D2-Client along with a set of configuration modules and dedicated screens to D2-Config.

D2-RPS-CONNECTOR involves two components:

  1. D2-RPS-CONNECTOR docapp or dar
  2. D2-RPS-CONNECTOR-Install.jar library

The D2-RPS-CONNECTOR library has to be installed on the Content Server & the application server.

Copy D2-RPS-CONNECTOR-API.jar in the Jboss lib folder:

Copy Policy engine and services jars in the RPSA webapp lib folder.


Lockbox is a component of the RSA Common Security Toolkit (CST) which securely stores passwords for Documentum D2 in an encrypted file. The stored passwords are put as <key, value> pairs. Lockbox uses keys to store and retrieve the passwords. Documentum D2 uses Lockbox that were earlier present as clear text in the various properties files, such as D2FS.properties, d2fs-trust.properties, D2-JMS.properties, and D2-Config.properties.

The Lockbox configuration for D2 can be done in either of the following ways:

  • Using the new D2 Configurator Utility – Configure the lockbox through the configurator: D2-Configurator-4.5.0.jar file.
  • Manual configuration of D2 Lockbox


  • Copy LB.jar and LBJNI.jar that are extracted from the D2 installer into <Documentum install path>\<Jboss version>\server\DctmServer_MethodServer\lib folder
  • set PATH=C:\Documentum\D2\Lockbox\win_vc80_x64;%PATH%
  • set CLASSPATH=<D2 install path>\C6-Common-<version>.jar;<lockbox install path>\LB.jar;<lockbox install path>\LBJNI.jar;%CLASSPATH%
  • Generate lockbox file and set D2.passphrase

java.exe –cp “C:\Program Files\EMC\D2\C6-Common-4.5.0.jar;C:\Documentum\D2\Lockbox\LB.jar;C:\Documentum\D2\Lockbox\LBJNI.jar” com.emc.common.java.crypto.SetLockboxProperty C:\Lockbox D2Method.passphrase #1Password

  • We can create a passphrase using java PassphraseGenerator:

java com.emc.common.java.crypto.PassphraseGenerator <length>


  • Copy the D2.lockbox file generated in <Documentum-root>/<JBoss-version>/server/DctmServer_MethodServer/deployments/ServerApps.ear/APP-INF/classes/
  • Create emc/d2/lockbox/main folder under <Documentum install path>/<JBoss version>/modules/ & Copy LB.jar and LBJNI.jar files that are extracted by the D2 installer to the main/ folder
  • Create module.xml for these 2 jar entries.
  • Add dependencies in jboss deployment xml file.


Need to configure the lockboxPath entry both in D2-Config and D2 client applications:

D2 Config

  • In D2-Config application, D2-Config.properties file contains lockboxPath properties entry. The file path of this properties file is located at :

<webapp root>\webapps\D2-Config\WEB-INF\classes\D2-Config.properties

  • Open the above file in a text editor and search for the string “lockboxPath”. By default, this entry would be commented. Uncomment and specify the fully qualified folder path of D2.lockbox file.

D2 Client

  • In D2 application, D2FS.properties file contains lockboxPath properties entry. The file path of this properties file is as under:

<webapp root>\webapps\D2\WEB-INF\classes\D2FS.properties

  • Open the above file in a text editor and search for the string “lockboxPath”. By default, this entry would be commented. Uncomment and specify the fully qualified folder path of D2.lockbox file
  • Lastly Copy lockbox librariesjar and LBJNI.jar into AS webapps.

 Restart Environment

The system hostname key is missing from the Lockbox – Regenerate the lockbox file again by running the installer through admin command line pointing to the supported java.

Deployed LB onto the JMS (D2 Lockbox on Content Server), Set the dll path:


java Dclb.library.path=C:\Documentum\D2\Lockbox\win_vc80_x64 com.emc.common.java.crypto.SetLockboxProperty C:\Progra~1\EMC\D2\lockbox D2Method.passphrase $Pass123

%d bloggers like this: