STEPS FOR CHANGING THE INSTALL OWNER PASSWORD

1. Login into the appropriate Content Server box using telnet.

NOTE: since our Application is Load Balancer we need to change for all the three content servers.

2. Stop all the process and services (follow the start/stop document).
3. Stop the Index Server & Index Agents.

NOTE: Stop all the server side Documentum related process/services. E.g.:
Docbrokers, docbases, method servers, thumb nail server etc... If 2DAM docbase resides in the same content server its safe that we stop DTS/MTS Boxes).

4. On the /lapps/docadm location, type the command “passwd”.
5. It will ask for the current password, give it and press enter.
6. It will ask for the new password, type the new password and click enter.
7. Repeat the steps 1 to 6 for the other content servers.
8. Restart all the Documentum server side process as per the start/stop document in all the three content servers.
9. Edit the DSCredentials.xml in the location cabinets/gdm/customizations folder by login in through DA.
10. Modify with the new installation owner password

NOTE: New GDM Env (GDM Clean & GDM_PT docbases does not require to update the DSCredentials.xml since the installation owner account credentials was not hard coded. But safer sides please check when this particular Operation is being performed).

11. update the business.xml using DA in the location cabinets/gdm/ (if available)

NOTE: New GDM Env (GDM Clean & GDM_PT docbases does not require to update the business.xml since the installation owner account credentials was not hard coded. But safer sides please check when this particular Operation is being performed).


12. Repeat the steps 8 and 9 for all the 3 applications.

NOTE: login to each docbase using DA and perform the operations (if applicable).

13. Do complete healths check of all the 4 Applications.
14. Select any of the default jobs and check its status by running it manually.

Note: Consistency Checker Job is the safe option to check the status of the password change as it won’t create/modify/ update/delete any objects.

NOTE: As we are unable to test the LDAP job in PSIC, we need to make sure that it is running in production when we perform this operation.

Stop and Restart Application process

Sequence of Events to Stop the System
1. Log into Windows hosts to stop all of the rendition agent services (MTS/DTS)
2. Log into Index Agent host, to the Admin console for each agent, and Stop the indexing process for each agent in the console
http://:9081/IndexAgent1/login.jsp
Click on the Agent Status action link named “Stop”.
3. From the command line of the primary Index Server host, stop the Index Agent
a. $ cd $DOCUMENTUM/share/IndexAgents
b. $ ./shutdownAllIndexAgents.sh
4. From the command line of the secondary Index Server, stop the FAST index server a. $ cd $DOCUMENTUM/fulltext/IndexServer/bin
b. $ ./shutdown.sh
c. To verify the shutdown, you can run the “nctrl systatus” command.
d. To clear the DMCL cache navigate to “/tmp/dmcl” and perform
the “rm –rf *” command
5. From the command line of the primary Index Server, stop the FAST index server
a. $ cd $DOCUMENTUM/fulltext/IndexServer/bin
b. $ ./shutdown.sh
c. To verify the shutdown, you can run the “nctrl systatus” command.
d. To clear the DMCL cache navigate to “/tmp/dmcl” and perform
the “rm –rf *” command
6. From the WebLogic management console, stop all of the running applications
a. WebDAV
b. DA
c. DAM
d. Webtop
e. To clear the DMCL cache navigate to “/tmp/dmcl” and perform
the “rm -rf *” command
7. On each of the 3 content servers, stop the following IN THIS ORDER:
a. Java Method server
i. $ cd $DM_HOME/tomcat/bin/
ii. $ ./shutdown.sh
b. Thumbnail server
i. $ cd $DM_HOME/thumbsrv/bin
ii. $ ./dm_thumbsrv_stop.csh
c. Repository
i. $ cd $DOCUMENTUM/dba
ii. $ ./dm_shutdown_<2DAM>.sh
iii. $ ./dm_shutdown_.sh
d. The last thing to stop on each of the 3 content servers are the 3 Docbrokers
i. $ cd $DOCUMENTUM/dba
ii. $ ./dm_stop_Docbroker
1. This stops the Docbroker on port 1489
iii. $ ./dm_stop_DocbrokerP1
1. This stops the Docbroker on port 1490
e. To clear the DMCL cache navigate to “/tmp/dmcl” and perform
the “rm –rf *” command
8. Log into the SunOne web servers and stop the services for your applications
9. With all repository services stopped, the servers and database services can be safely stopped/restarted if necessary.

Sequence of Events to Start the System
The process for starting the application is basically to execute the steps above in reverse order
1. Ensure database services and all hosts have been restarted and are running
a. Try to connect to the database with sqlplus as the repository owner
2. Log into the SunOne Web servers and start the services for
3. On each of the 3 content servers, start the following IN THIS ORDER
a. Docbrokers
i. $ cd $DOCUMENTUM/dba
ii. $ ./dm_launch_Docbroker
1. This starts the Docbroker on port 1489
iii. $ ./dm_launch_DocbrokerP1
1. This starts the Docbroker on port 1490
b. Repositories
i. $ cd $DOCUMENTUM/dba
ii. $ ./dm_start_.sh
c. Method Server
i. $ cd $DM_HOME/tomcat/bin
ii. ./startup.sh
iii. Verify this by hitting the method server URL at http://:9080/DmMethods/servlet/DoMethod
d. Thumbnail Server
i. $ cd $DM_HOME/thumbsrv/bin
ii. $ nohup ./dm_thumbsrv_start.csh &
iii. Verify this by hitting the URL for the Thumbnail server at https://:8443/thumbsrv/getThumbnail?format=msw8
1. You can substitute other format values here, such as jpeg or bmp
4. On the 3 WebLogic application server hosts, log in and start all of the applications from the command line. (NOTE: If the server itself has been restarted, you will need to log and start the WebLogic admin console as well.)
a. $ wls
b. $ ./startda.sh
c. $ ./start.sh
f. You can verify that all applications have started up correctly on each WLS by logging into the WLS admin console.
g. Within the WLS admin console, do first time Garbage Collection on all the managed servers by navigating into “Monitoring” > “Performance” tabs and click on “Force Garbage Collection” button.
5. From the command line of the primary Index Server, start the FAST index server
a. $ cd $DOCUMENTUM/fulltext/IndexServer/bin
b. $ ./startup.sh
c. To verify the start, you can run the “nctrl systatus” command and see that all processes are “running”
6. From the command line of the secondary Index Server, start the FAST index server a. $ cd $DOCUMENTUM/fulltext/IndexServer/bin
b. $ ./startup.sh
c. To verify the startup, you can run the “nctrl systatus” command.
7. From the command line of the primary Index Server host, start the Index Agent a. $ cd $DOCUMENTUM/share/IndexAgents
b. $ ./startupAllIndexAgents.sh
8. Log into Index Agent host, to the Admin console for each agent, and Start the indexing process for each agent in the console
i. http://:9081/IndexAgent1/login.jsp
Click on the Agent Status action link named “Start”.
9. Log into Windows hosts to start all of the rendition agent services (MTS/DTS)
10. From within DA or applications themselves, verify complete environment functionality with the test cases provided.

Failed to load preferences, Cannot locate file - dfc.properties

Failed to load preferences, Cannot locate file - dfc.properties

ID: esg82728

SOLUTION

Symptoms

While uninstalling the existing Index Agent on Solaris machine, an error dialog box is displayed:

"Failed to load preferences: java.io.FileNotFoundException: Cannot locate file - dfc.properties"

Cause

Environment variable DFC_DATA set in dmadmin's profile seems to cause this problem. All the other environment variables seemed to be correct.

Resolution

When DFC_DATA was commented out in the dmadmin's profile, the problem disappeared.

Component 'MSCOMCTL.OCX'

Component 'MSCOMCTL.OCX' or one of its dependencies not correctly registered: a file is missing or invalid
MSCOMCTL.OCX error screenshot:

How to Correct or fix this dependency error:
1. First search your local drive for MSCOMCTL.OCX to see if it is missing. The path to the file is typically: C:\WINDOWS\system32 if you are running Windows XP
2. If the file is missing you can download it HERE
3. Once downloaded, click the MSCOMCTL.exe and extract the file to your C:\WINDOWS\system32 directory

Resolution : Install Microsoft ActiveX Control Pad Installation

( setuppad.exe )

How can I change the docbase (repository) owner password?

You will need to do the following steps:

- Stop the Docbase (repository)
- Backup file dbpasswd.txt under /Documentum/dba/config//
- Modify dbpasswd.txt file with the new database password in plain text (without encrytion just like abraxis1234)
- Re-encrypt the dbpasswd.txt file:

cd $DM_HOME/bin means --> C:\Documentum\product\5.3\bin

dm_encrypt_password -docbase -rdbms -encrypt

- Start the Docbase (repository).

Login Page is not displaying

Installed DCM and DA on APP Server machine but login page is not displayed but DOne message at status bar
Sol: Update the class path in weblogic.cmd and restart weblogic

Unable to instantiate WordPerfect MPI: Can't get object clsid from progid

Symptoms

When running Document Transformation Services, the following message can be observed in the CTS log file located under Program Files\Documentum\CTS\logs:

INFO [ main] CTSPluginHandlerImpl - Unable to instantiate the following MP: com.documentum.cts.plugin.wordperfect.WordPerfectPlugin
com.documentum.cts.plugin.common.CTSPluginException: Can't get object clsid from progid
Cause Exception was: Unable to instantiate WordPerfect MPI: Can't get object clsid from progid
com.jacob.com.ComFailException: Can't get object clsid from progid
at com.jacob.com.Dispatch.createInstanceNative(Native Method)
at com.jacob.com.Dispatch.(Dispatch.java:160)
at com.jacob.activeX.ActiveXComponent.(ActiveXComponent.java:54)



Cause

This issue will appear if WordPerfect is not installed on the DTS server. By default, the plugin for WordPerfect is included in the CTSPluginService.xml file located under Program Files\Documentum\CTS\config.



Resolution
- Take a back up for CTSPluginService.xml
Navigate to Program Files\Documentum\CTS\config and open the CTSPluginService.xml with a text editor. Locate the following line:





Comment out this line using the following syntax:





Restart the CTS services and restart. The issue should be resolved.