I got task to install and configure My Documentum for Outlook . .The most confusing part is to dig through all the documentation which is scattered all over place for different components in this installation.

MyD-Outlook_6_7 /Sp1/Sp2 supports all Content Server 6.5 version and later .

These are the steps i followed and it all worked out .

1- First thing first , make  an excel sheet and note down your current environment  specification for content server , web server . My environment settings are 6.5 SP3 , Tomcat 5.5.35

 

2- Download the matched version for My Documentum for Outlook , you have to download dar(MyD-Outlook_6_7.dar) file and My-Documentum-for-Microsoft-Outlook-6.7SP1.exe .

3- Download WAR/EAR file as per your applications server (WAR for Tomcat and EAR for IBM WAS)

4-  Install the DAR file using composer dar installer to all the repositories which you want to expose for MYD(My Documentum )- straight forward , no issues, it should be installed to global as well as other repositories you want to use in My Documentum.

5- Check out the following file dco_custom_settings.xml from given path /System/Applications/DCO and add all the repositories you want to enable for MYD. Empty login mode means normal mode , where user need to input user id and password to connect with repository.Repository name is case sensitive

<Repository name="TEST" LoginMode=""/>

6- Unzip the War file and add the dfc.properties file to following location My-Documentum-for-Microsoft-Outlook-WebService-6.7\WEB-INF\classes

7- Make war file again

8- Add the following tag to server.xml file in the Tomcat root folder/conf (example-C:\Tomcat\conf) and add the following tag. Here the tag provided in admin guide does'nt work with Tomcat so just make sure that you use this tag between <host>  </host>

<Context path="" docBase="My-Documentum-for-Microsoft-Outlook-WebService-6.7"
antiJARLocking="true" reloadable="true" />

9 Make sure you have enough memory for Tomcat  .

-Xms512m
-Xmx1024m
-XX:MaxPermSize=512m
-XX:MaxHeapFreeRatio=70

 

10 – Deploy the WAR file on tomcat which you created in step 7 and start the tomcat server .

11- Go to your DA installation and uncomment the following xml tags from it and restart the DA applications. This enables the administration node in DA for outlook profiles management.

Path for this file DA Installation folder\webtop\config\administration_component.xml

<node componentid=’dcoadmin’>
<icon>dcoadmin.gifdcoadmin.gif</icon>
<handlerclass>com.documentum.webtop.webcomponent.administration.
ConfigurationNavigationNodeConfigurationNavigationNode</handlerclass>
<label><nlsid>MSG_DCOADMIN</nlsid></label>
<node>—>

 

 

12- Install the My-Documentum-for-Microsoft-Outlook-6.7SP1.exe on your system ,its straight forward next –next.

13- Configure the My Documentum using Outlook and you will be able to see one extra Menu in Outlook and click on it , configure the repositories.  Two things to remember here.

URL of your deployed application

http://serverurl:portno/

You might get error saying, no repositories available, that means, your setting which you changed in DA step 5 are not working, restart DA , content server, try again. Once it is up and running, you can configure the profiles using DA outlook node as per your business requirement

 

Happy installing.

 

Please let me know if you face any problem by a comment .

There are two types of system , one is Windows based and other is Unix flavor.

 

For Windows based systems and we are considering dmadmin as installation user on the system.

(This works on WinXP/Win2000/Win2003/Win2008/Win7)

1- Go My Computer

2- Right click on icon

3- Click on manage

4- Go users

5- Right click on your installation user id –dmadmin -

6- Right click and change the password, restart your system

 

Unix based system – it will work on almost all but you can consult your specific Unix flavor for password changing command but it works on almost all.

1- Login to system

2- $passwd

3-$Changing password for dmadmin

4-$(current) UNIX password:

5-$Enter new UNIX password:

6-$Retype new UNIX password:

7-$passwd: password updated successfully

8-$ restart your docbase services.(docbroker/method server/repository services.)

 

Good Luck

Follow the steps -

Steps:

- Stop docbase
- change the password in database – go to Oracle/MS SQL Server/DB2/SyBase—whatever DB you are using.
- change the dbpasswd.txt

- Re-encrypt the dbpasswd.txt file do the following
cd $DM_HOME/bin
dm_encrypt_password -docbase <docbase name> -rdbms -encrypt <database password>
- Start the docbase

 

Good Luck

Include both the docbroker in the dfc.properties.

public static IDfSession connectToDocbase1(String docbaseName,
String username, String passwd, String domain,
String docBrokerHost, String docBrokerPort) throws DfException {
try {
IDfSession session = null;
IDfClientX clientX = new DfClientX();
IDfClient client = clientX.getLocalClient();
IDfLoginInfo loginInfo = new DfLoginInfo();
loginInfo.setUser(username);
loginInfo.setPassword(passwd);
loginInfo.setDomain(domain);
if (docBrokerHost != null && docBrokerHost.length() > 0) {
IDfTypedObject apiconfig = client.getClientConfig();
String primaryHost = apiconfig.getString("primary_host");
String primaryPort = apiconfig.getString("primary_port");
apiconfig.setString("primary_host", docBrokerHost);
apiconfig.setString("primary_port", docBrokerPort);
try {
IDfTypedObject serverMap = client.getServerMapEx(
docbaseName, null, docBrokerHost, docBrokerPort);

session = client.newSession(docbaseName + "@"
+ serverMap.getString("i_host_name"), loginInfo);
} catch (DfException e) {
if (primaryHost != null) {
apiconfig.setString("primary_host", primaryHost);
}
if (primaryPort != null) {
apiconfig.setString("primary_port", primaryPort);
}
throw e;
}
apiconfig.setString("primary_host", primaryHost);
apiconfig.setString("primary_port", primaryPort);
} else {
session = client.newSession(docbaseName, loginInfo);
}
return session;
} catch (DfException ex) {
System.out.println("failed to connect " + ex.getMessage());
throw ex;
}
}

Following up on the webex, please try the steps below to clean up your

1. Unconfigure the docbase using MTS configuration program.
2. Uninstall MTS
3. Remove the remaining Documentum products from Add/Remove Programs.
4. Delete the following folders and all contents:
C:\Documentum
C:\Program Files\Documentum
5. Delete the Documentum entries from registry.
6. Reboot the MTS machine to make sure everything is clean.
7. Back up your custom profiles
8. Log in to DA as an admin user.
9. Delete the Media Server folder, located in: \System (select all children and all versions when prompted during delete)
10. Navigate to \System\Applications
11. Delete the CTSTransformRequest, MediaProfile, and Transformation folders if present
(including all versions and sub folders).
12. Navigate to the System\Modules\TBO folder
13. Delete all of the following folders (if present):
• dm_cts_response
• dm_media_profile
• dm_transform_request
• dmc_cts_reporting_config
• dmc_cts_request_archiving
14. Navigate to the System\Modules\SBO folder and:
• Delete all of the folders that start with "com.documentum.services.cts...";
• Delete all of the folders that start with "com.documentum.services.dam...".
15. Run the following two DQL statements against the docbase, in this order:
DQL> delete cts_instance_info object
DQL> drop type cts_instance_info

Restart docbase. Install MTS 6.5 SP3, install 2 DAR files, and then configure MTS against this docbase again to see if it fix your issue.

Perl Script to automate starting and stopping applications for Documentum Suite on All Unix based platforms.

How to drop all the tables , views from the Oracle DB schema for recreating the repository?

1-

Create one sql file and name it -createdroptables.sql and write below given queries into this file


SET SERVEROUTPUT ON;

SPOOL C:\droptables.LOG;

SELECT * FROM (SELECT 'DROP TABLE '||table_name||' CASCADE CONSTRAINTS;' FROM user_tables UNION
SELECT 'DROP VIEW '||VIEW_NAME||';' FROM user_views UNION
SELECT 'DROP SEQUENCE '|| SEQUENCE_NAME||';' FROM user_sequences UNION
SELECT 'DROP SYNONYM ' || SYNONYM_NAME ||';' FROM user_synonyms UNION
SELECT 'DROP FUNCTION ' || OBJECT_NAME ||';' FROM user_procedures UNION
SELECT 'PURGE RECYCLEBIN;' FROM dual) ORDER BY 1 ASC;

SPOOL OFF

2 Run this sql file on sqlplus console

SQL> @C:\createdroptables.sql

3 Rename the droptables.log file to droptables.sql which is created in c:\ drive

4 Run this sql file on sqlplus console

SQL> @C:\createdroptables.sql

5 Check the tables in schema by running below given query

select table_name from user_tables;

6 You should get no table name ie its now empty schema.

Good Luck recreating repository.

How to manage the User cabinet’s visibility to users in Documentum Server?

Scenario1: Only owners will be able to see their cabinets , not even super users and System administrator will be able to see their cabinets.


1: Make is_private = 1 which is by default


Scenario 2: Some group (admin users or some other group of users) wants to see the cabinet of all users

1: Make is_private = 0 attribute of the dm_cabinet objects.
2: Create a default_user_cabinet_acl
Where
Dm_world = none
Admingroup = read
Owner = delete

3: apply above ACL on all the cabinets
4: you can apply above created ACL on the dm_cabinet type so that whenever a new cabinet is created, this ACL is applied automatically, One advantage of this approach is , you can change this ACL at anytime and all the cabinets will be affected by this change for example, you want to add one more group of users who wants to see all the cabinets in your organization like managers than you can add that group to this acl and assign them access.

Scenario 3: When you are integrating LDAP authentication and wants to create default cabinets for users.

1: you can create cabinet by mapping users
2: you can create cabinet by passing one more attribute to the
ldapjobSyn method
-create_default_cabinet true
Insert this before –full_sync =false/true parameter

This creates cabinet with the user’s last name, first name example Singh, Kulveer but in this case, the ACL which you created in Scenario2 was not applied to the cabinet even though you applied the ACL on dm_cabinet
type itself, this is strange behaviour, I don’t know why Documentum does so.

OR
You can create cabinet by mapping LDAP attribute in LDAP config object

Goto DA->Basic Configuration->LDAP Servers->Mappting tab->property Mapping table-> Add new property

Where you can map dm_user objects default_folder attribute to the LDAP attribute for example

Default_folder = {$sn}

Refer Documentum Administrator guide for more detail regarding this LDAP mapping.

3: Step 2 will create cabinets only for the new users which are being pulled by the LDAP in both the cases but if you want to create cabinets for all the users which are already pulled into the Documentum than
A: Create users by script for existing users and make is_private = 0
OR
B: Delete all the users in Documentum and run the LDAPSync job and all the users will be created with their default cabinets. Note: you may loose some group and other ACL information which may be lost when you delete the users but it all again depends on your LDAP configuration.

4: in step 3 user’s cabinets are created but you have to run the script to make the is_private=0 and apply the ACL created in Scenario 2. This task can be done by creating job or changing the existing LDAPSync job to change the is_private=0 and apply the ACL . This totally depends on the complexity of your systems user base.

You can use any of the approaches based on your requirement and complexity of the system.

I would like to hear the comments for the above approaches. Let’s make it better by sharing our knowledge.

How to configure LDAP Object in Documentum

To setup an LDAPConfig Object and import the users you may follow the steps documented in the eContent Server Administrator Guide, Appendix C, "Using an LDAP Directory Server". However, please note the following three items that are not detailed in the documentation.

1. You must provide an email address in the LDAP server and LDAP Configuration object in Documentum Administrator (DA).

2. Use groupofuniqueNAMES instead of groupofuniquemembers. The groupofuniquenames is defined in the schema, where as the groupofuniquemembers is not.





STEPS FOR TESTING LDAP FUNCTIONALITY:

Below is the procedure for testing the LDAP functionality briefly without checking in detail.

1. Install Netscape Directory Server on NT or Unix. A schema is made automatically when you install LDAP server.


2. Add a user and group into LDAP Directory Server, by Netscape LDAP Directory Server, and PLEASE PROVIDE EMAIL ADDRESS.


3. Make an LDAP Configuration object in a Docbase, using DA. Below is a sample of the setting:



Hostname : your computer name or IP address where LDAP server runs,

Port : default 3891 Note but it depends on your LDAP Server so
consult the LDAP team for this.

Person Object Class : person

Group Object Class : groupofuniquenames [NOT groupofuniquemembers]

Person Search Base : o=xyz.com (This is the domain name of the computer where LDAP server is installed.)

Group Search Base : o=xyz.com (Same as Person Search Base)


Enabling LDAP Changelog Information : uncheck


Name : uid

OS Name : uid

Email Address : mail


4. Restart Docbase


5. Run LDAPSynchornize job


6. Check whether users and groups defined in LDAP server are imported into the Docbase in DA.


7. Try to connect to the Docbase with Intranet Client (IC) or Desktop Client (DTC) as the user defined in LDAP Server.



Again, the following items are correction or clarification to the documentation:

1. Provide an email address in the LDAP server and LDAP Configuration object in Documentum Administrator (DA).

2. Use groupofuniqueNAMES instead of groupofuniquemembers. The groupofuniquenames is defined in the schema, where as the groupofuniquemembers is not.

3. Restart Docbase once you have created a LDAP Configuration object.

Please feel free to given feedback/comments/suggestions/improvements.

When a document is deleted from Documentum, only the document's metadata is deleted. The content itself (i.e. the object pointed to by the dmr_content object) remains in the content storage area until the IAPI script generated by the dmclean utility is run. If the dmclean utility has not been run, it is still possible to recover the object's content file.

Note: The document's attributes cannot be recovered without going back to a database backup. Below is an outline of a strategy which can be used to do this recovery.


Recovering the Information of the deleted Object

1. The Following DQL will retrieve the object_ids that correspond to the content objects that have been deleted

select r_object_id from dmr_content where any parent_id is null

If you want to retrieve data for a particular client, you can extract the following information to create your DQL:-

a) What was the name of the object? This is the object_name attribute.

b) What format was the document? This is the full_format attribute.

c) What was the date/time of the last checkin? This is the set_time attribute.

d) What was the name of the client machine where the file was last checked in? This is the set_client attribute.


The DQL that will be created in this case according to your search criteria is as follows:-

select r_object_id from dmr_content where any parent_id is null and
set_client = and full_format = and set_time > DATE('')


2. Using the Object Ids recovered the following IAPI needs to be executed to pick up the path and relevant information of the Object under consideration :-

API> apply,c,,GET_PATH
API> next,c,q0
API> get,c,q0,result

This returns the file system path to the object. For example:

/disk2/dm20/data/solar20o/content_storage_01/00000065/80/00/14/07


How to restore the Document

To be able to restore the document back to its original location, you will need to firstly create a document object of the deleted type using the IAPI :

Creating a new dm_document object using IAPI
API> create,c,dm_document
0900006580005a65.


Setting the name of the Deleted object
API> set,c,,object_name
SET> Restored Document
OK

Linking the deleted file to the newly created object
API> setfile,c,,/disk2/dm20/data/solar20o/content_storage_01/000000
65/80/00/14/07,
OK

Linking the object to a directory in the Cabinets where the file will be restored
API> link,c,,/Temp
OK

Saving the file
API> save,c,

This will restore the deleted document at the location /Temp with the name Restored Document

Deleting bulk number of objects is a daily task in administrating the Documentum Server and its not possible to delete more than couple of thousands objects using DA or even iDQL because it takes lot of time or sometimes it hangs the server. So best way to do it is through create a text file of API commands for those objects which need to be deleted and i have compiled some steps to do that in easy way . It can be automated by using writting some job but if you need to delete instantenously by running script . Here is the solution.

1:- Create a dql file to extract object_ids of the objects which you want to delete

example

Name this file something like "extract_objectIds.dql"
---------------------------------------
select 'destroy,c,'as destroy,r_object_id from dm_document
go
quit

---------------------------------------
2:- Create a batch file to run this dql command created in above file named like

extract_objectId.bat

----------------------------------------
@echo off
setlocal & pushd


rem -=-=-=-=-=-=-=-=-=--
rem - Set these values -
rem -=-=-=-=-=-=-=-=-=--
set DOCBASE_NAME=xxxx
set DCMT_SUPERUSER=yyyy
set DCMT_SUPERUSER_PW=zzzzz

echo
"%DM_HOME%\bin\idql32" %DOCBASE_NAME% -U%DCMT_SUPERUSER% -P%DCMT_SUPERUSER_PW% -Rextract_objectIds.dql >object_Ids.log
:EOF
endlocal & popd

-----------------------------------

3:- Extract all the API commands from the log you got in previous step in your objectid.log into a new file called "destroy_objects.api"
for example , your object_Ids.log must be containing data like

destroy,c, 09xxxxxxxxxxxxxx
destroy,c, 09xxxxxxxxxxxxxx
destroy,c, 09xxxxxxxxxxxxxx
destroy,c, 09xxxxxxxxxxxxxx

4: Create a new batch file or update the above batch file and run iapi command file using the batch file.

New Batch file example (destroy_objects.bat)

----------------------------------------------
@echo off
setlocal & pushd

rem // $Id$
rem -=-=-=-=-=-=-=-=-=--
rem - Set these values -
rem -=-=-=-=-=-=-=-=-=--
set DOCBASE_NAME=xxxx
set DCMT_SUPERUSER=yyyy
set DCMT_SUPERUSER_PW=zzzzz


rem Destroying Objects
echo
echo.
""%DM_HOME%\bin\iapi32" %DOCBASE_NAME% -U%DCMT_SUPERUSER% -P%DCMT_SUPERUSER_PW% -Rdestroy_objects.api -lobjectsDeleted.log

:EOF
endlocal & popd
------------------------------------------------

Run this batch file by setting your Docbase Name , UserId, Password.

Thats it.

Happy Destroying Objects.

Note: