Use the command line tools to identify the open sessions and kill one of them. There are two tools, qwinsta and rwinsta. If you run "qwinsta /?" from a command shell, you will get the following:

qwinsta /?

Display information about Terminal Sessions.

QUERY SESSION [sessionname | username | sessionid]

              [/SERVER:servername] [/MODE] [/FLOW] [/CONNECT] [/COUNTER]

  sessionname         Identifies the session named sessionname.

  username            Identifies the session with user username.

  sessionid           Identifies the session with ID sessionid.

  /SERVER:servername  The server to be queried (default is current).

  /MODE               Display current line settings.

  /FLOW               Display current flow control settings.

  /CONNECT            Display current connect settings.

  /COUNTER            Display current Terminal Services counters information.



                                 

If you run "rwinsta /?", you get the following:

rwinsta /?

Reset the session subsytem hardware and software to known initial values.

RESET SESSION {sessionname | sessionid} [/SERVER:servername] [/V]

  sessionname         Identifies the session with name sessionname.

  sessionid           Identifies the session with ID sessionid.

  /SERVER:servername  The server containing the session (default is current).

  /V                  Display additional information.

For the sample server abc, you would run "qwinsta /server:abc"

Output

 SESSIONNAME       USERNAME                 ID  STATE   TYPE        DEVICE

console                                     0  Conn    wdcon

rdp-tcp                                 65536  Listen  rdpwd

                   abcd                    1  Disc    rdpwd

rdp-tcp#93        gates                    3  Active  rdpwd

From that output, we can take one of the IDs that was returned for the remote sessions and use rwinsta to kill that session. You would use something like:

rwinsta 1 /SERVER:abc

And that will terminate that session, allowing you to open a new session. You will need admin rights to run that command, but if you are using the admin terminal service connections to the server, then you would already have the necessary access rights to the server.

There is a third option, you can connect to the console session. This is the bonus option that I had referred to earlier. This is the session that you would get if you were physically in front of the server and were logging in on the server's mouse and keyboard. You can specify the console session as a command line parameter to the remote desktop client, mstsc.exe. The following syntax can be used to connect to the console session of a server:

mstsc /console

That feature will work with Server 2003 and later. On some machines, qwinsta and rwinsta may have been renamed to query.exe and reset.exe, respectively.

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.

The solutions for this problem deals with MS Windows 2008 server .



1. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DocumentumCTS\Parameters
AppParameters key

Make sure all the path to jre directory is complete and correct. If the path format is using complete path such as "C:\Program Files\Documentum\dctm.jar", try replacing it with short path like "C:\PROGRA~1\DOCUME~1\dctm.jar" in -Djava.class.path

Invoke Jave method from the WebTop UI using java code.

divyansh

Perquisite to run this code,


1-Use Eclipse and java 1.5 or later
2-Download JODConvertor from the URL
3-http://code.google.com/p/jodconverter/downloads/list
4-Add all the jar file in lib directory of JODconvertor to your project.
5-Download Openoffice 3.0 from URL http://download.openoffice.org/other.html#tested-full
5-Install the Openoffice 3.0

Limitation
A:- It cannot be multi-threaded.
B:- It cannot convernt MULTI-TIFF images to PDF but it can convert single page TIFF to PDF.

import java.io.*;
import org.artofsolving.jodconverter.OfficeDocumentConverter;
import org.artofsolving.jodconverter.OfficeDocumentConverter.*;
import org.artofsolving.jodconverter.office.*;
import org.artofsolving.*;
import org.artofsolving.jodconverter.document.*;
import org.artofsolving.jodconverter.process.*;
import org.artofsolving.jodconverter.util.*;
public class Main {
public static void main(String[] args) throws Exception {
conversion();
}
public static void conversion(){
OfficeManager officeManager = new DefaultOfficeManagerConfiguration().buildOfficeManager();
officeManager.start();
OfficeDocumentConverter converter = new OfficeDocumentConverter(officeManager);
converter.convert(new File("C:/Temp/first.doc"), new File("C:/Temp/Doctest.pdf"));
officeManager.stop();
System.out.println("Hellow WOrld , its done");
}

Ask me if you are not able to run it.

Happy Conversion.

Manually uninstalling the Oracle from WinOS platform .

I had to do it for the Documentum installation and it sucks to do all these steps if you really mesh up the oracle installation. I did this to try some latest Documentum product testing and i noted down these steps if i need them in future or these can be of any help to anybody.No guarantee for any damage to system because these steps involve registry modifications and can really cause harm to your server if you try them on production environments(BE AWARE ). It was all hit and trial to re-install the oracle as oracle un-installer doesn't clean-up the system if you need to reinstall and it will be nightmare unless you really clean up the previous installations of oracle from the system.

A. Removing Components on Windows OS.
To remove all Oracle components from a computer on Windows OS:

1. Check privileges:
1.a. Ensure you are logged in as a user with Administrator privileges.

2. Stop all Oracle services (if any are running):
2.a. Right click My Computer > Manage > Services and Applications > Services

2.b. If any Oracle services (their names begin with Oracle) exist and have
the status Started, select the service and click Stop.

2.c. Click Close to exit the Services window.

2.d. Close the Control Panel/Computer Management window.

3. Remove the entries in the Windows registry:
3.a. Start the registry editor:
Choose Start > Run > regedt32

3.b. Go to HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE
Note the value of the key INST_LOC, this is the location of the Oracle Universal
Installer. The default location is Installation Drive(C:or D:):\Program Files\Oracle\Inventory. If this value is different, make note of it, so we can delete these files later.
Delete this ORACLE key.

3.c. Go to HKEY_LOCAL_MACHINE\SOFTWARE\ODBC and expand all subkeys and
remove all keys under here which are related with the
"Oracle ODBC Driver"

3.d. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and remove
all keys under here that begin with ORACLE or ORAWEB.

3.e. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\...
\Application and remove all keys under here that begin with ORACLE.

3.f. Go to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall
and remove any entries related to Oracle.

3.g. Go to HKEY_CLASSES_ROOT, remove all keys that begin with Oracle, OraPerf or
OraOLEDB

3.h. Close the registry.

4. Clean up the environment settings:
4.a. NT: Choose Start > Settings > Control Panel > System > Environment tab
2000: Choose Start > Settings > Control Panel > System > Advanced tab >
Environment variables.

4.b. At "System Variables" click on the variable PATH in order to modify
the value. For example, you may see a path similar to this one:
C:\ORACLE\ORA81\BIN;C:\PROGRAM FILES\ORACLE\JRE\1.1.7\BIN

4.c. If an %ORACLE_HOME% was installed, remove this %ORACLE_HOME%\BIN path.

4.d. If JRE was installed by Oracle, remove the JRE path.

4.e. If there is a CLASSPATH variable under "System Variables", first make note
of the path defined, then delete it. This variable can be added back at
a later date if needed.

4.f. Check if there are any other Oracle variables set in "System Variables",
ORACLE_HOME, ORACLE_SID or TNS_ADMIN. If these exist, delete them also.

4.g. Click on APPLY and OK.

4.h. Close the Control Panel window.

5. Delete the software and icons:
5.a.Choose Start > Programs > Accessories > Windows NT Explorer.

5.b. Go to SYSTEM_DRIVE:\WINNT\PROFILES\ALL USERS\START MENU\PROGRAMS
OR Go to SYSTEM_DRIVE:\DOCUMENTS AND SETTINGS\ALL USERS\START MENU\PROGRAMS


and delete the following icons:
- Oracle - HOME_NAME
where HOME_NAME is the previous Oracle home name.
- Oracle Installation Products

5.c. Go to SYSTEM_DRIVE:\Program Files\Oracle or the location of INST_LOC as
noted earlier in step 3.b and delete this directory.

5.d Go to SYSTEM_DRIVE:\Temp and delete all files and directories in here.

5.e. Go to the drive where the Oracle software is installed on your machine
and delete all ORACLE_BASE directories on your hard drive.

5.f. Close the Windows Explorer.

6. Finish the removal

7 Reboot your computer.

In a multiple Content Server environment, sometimes ACS/JMS may fail with an Exception since it tries to connect to the remote Content Server projected to Docbroker.

Cause
ACS/JMS connects to Content Server with a trusted login, but it only works locally. If it tries to connect to remote Content Server, it fails.

Resolution
The user can configure additional docbrokers used only internally. Below is a sample configuration with two Content Server and two Docbrokers each.

Suppose on each Content Server, Docbroker 1 is using port 1489 and Docbroker 2 is using port 1491 (port 1490 is used for secure communication by first Docbroker and port 1492 by second Docbroker, since each Docbroker should be assigned with two consecutive ports).

Content Server 1

server.ini
[DOCBROKER_PROJECTION_TARGET]
host = host1
port = 1489
proximity = 5
[DOCBROKER_PROJECTION_TARGET_1]
host = host2
port = 1489
proximity = 5
[DOCBROKER_PROJECTION_TARGET_2]
host = host1
port = 1491
proximity = 1
[DOCBROKER_PROJECTION_TARGET_3]
host = host2
port = 1491
proximity = 10

dfc.properties
#only put the docbroker on port 1491
host = host1
port = 1491

Content Server 2
server.ini
[DOCBROKER_PROJECTION_TARGET]
host = host2
port = 1489
proximity = 5
[DOCBROKER_PROJECTION_TARGET_1]
host = host1
port = 1489
proximity = 5
[DOCBROKER_PROJECTION_TARGET_2]
host = host2
port = 1491
proximity = 1
[DOCBROKER_PROJECTION_TARGET_3]
host = host1
port = 1491
proximity = 10

dfc.properties
#only put the docbroker on port 1491
host = host2
port = 1491

Application server
dfc.docbroker.host[0]= host1
dfc.docbroker.port[0]=1489
dfc.docbroker.host[1]= host2
dfc.docbroker.port[1]=1489

On each machine, the second docbroker is used internally by the clients installed on the CS (ACS, JMS, IDQL, etc). In this way, it prevents the system to try to connect to remote CS with trusted login when it actually is unable to.

Introduction
In Documentum applications, the speed at which users can retrieve or add content to the system plays a big part in the overall end user experience. Network latency and bandwidth restrictions, physical architecture and client configuration all have an impact on the time it takes between initiating a content transfer, performing the upload or download, and returning control back to the user.

This document will discuss various tuning options available to achieve the best possible performance for UCF content transfer in your network environment.

Overview of UCF
UCF (Unified Client Facilities) is the EMC Documentum framework for performing content transfer between the client and content servers over HTTP. It provides many features that extend beyond simple file transfer protocol, such as:
Content compression to optimize transfers of larger files over the network
Support for complex documents, such as XML files
Support for compound document types, such as OLE objects inside a Microsoft Office document
Awareness of locally downloaded files, and the ability to avoid downloading the same content twice
Registry support, to allow checkout from one application and check in from another
Recoverability in the case of a brief network interruption
Location aware, to allow users to transfer content from the closest ACS or BOCS server
High-Level UCF Operations
When a content transfer is initiated, the UCF client running on the end user machine is initiated if it is not already running. The applet loads the UCF client jars and initiates contact with the UCF server, running on the application server.

The UCF client and server pass information back and forth about the environment and requested action before content is transferred between the two machines. Depending on the architecture and configuration, content may be transferred through the application server, directly to or from an ACS server on the content server, or a BOCS server located near the user.

After the content transfer is complete, there will be some additional communication from server to client to provide instructions on registry entries to be added or modified, directions on how to launch the appropriate application for view or edit operations, or instructions on how to delete the local file on check in.

Optimizing UCF for Best Performance

Tip #1 - Use ACS and BOCS for Content Transfer Whenever Possible

The introduction of ACS and BOCS servers in 5.3 SP1 have allowed content transfer to be performed directly from the content server, rather than requiring that the content always pass through the application server. This not only removes the double-hop that is required (which is very costly for small files) but also reduces the load on the application server.

In the 5.3 timeframe, ACS and BOCS could only be used for download operations such as checkout, export and view. All upload operations still passed through the application server.

From D6 onward, ACS and BOCS servers can also be used for upload operations.

Note that not all applications are network location aware and able to take advantage of remote ACS and BOCS servers.

Tip #2 - Optimize UCF Client Initialization

In 5.3 SP1 through SP5, D6 and D6SP1, the UCF client engine will time out after one minute of inactivity, and the javaw.exe process would be terminated. This means that if a user initiates another content transfer request after the timeout has occurred, the browser must re-initialize the UCF client and restart javaw.exe.

This value can be increased in the ucf.client.config.xml file as follows:

Edit the ucf.client.config.xml file (located at C:\Documents and Settings\\Documentum\ucf\\shared\config\ucf.client.config.xml) and add the following option to extend the UCF Client Timeout.
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true"
socketBuffer="64000"/>
If you are using 5.3 ACS and BOCS the application server is Tomcat 5.0.28. In versions 5.3 SP1 or SP2, you will need to add the socketBuffer parameter. In 5.3 SP3 through SP6, this parameter should already have been added by the installer.

In 6.5 and beyond, Jboss is the container for ACS and BOCS. In 6.5 SP1, enhancements were added to the embedded Jboss server to enable it to recognize and use the socketBuffer parameter.

BEA Weblogic
If you are using BEA Weblogic as your application server and you are not using ACS, be sure to add the -Dweblogic.ChunkSize parameter. By default, the ChunkSize is 4k which is much too small.

It can be set in the config.xml for the domain:

server1

false

localhost
17001



-Dweblogic.Chunksize=64000
weblogic
{3DES}wmzrpHOymvTy3q8TOeF1qQ==


It can also be defined in the set_domain_env batch file with the other JAVA_PROPERTIES values:
set JAVA_PROPERTIES=-Dplatform.home=%WL_HOME% \
-Dwls.home=%WLS_HOME% -Dwli.home=%WLI_HOME% \
-Dweblogic.Chunksize=64000
In D6 and D6 SP1, the application server that hosts ACS and BOCS is BEA Weblogic, and the installer has automatically added those options to the script that starts the embedded Weblogic server (startMethodServer.cmd for example).

IBM Websphere
If you are not using ACS and content is being transferred through WAS, then you may see improvements in content download performance for large files by modifying the ResponseChunkSize configuration parameter in the plugin-cfg.xml.

where N equal the chunk size in kilobytes. The default value is 64 (kilobytes).

Tip #6 - Improve Upload Performance in D6 and Above

In D6, a parameter was added to the ucf.client.config.xml file that allowed the users to specify a chunk size to be used when uploading content.

Internal testing showed that a value of 49152 worked best with ACS on BEA when simulating various WAN conditions. However, in environments where customers are not using ACS write, or whose network conditions are different from that which was tested, this value may not be optimal. Increasing or decreasing the optimal.chunk.size parameter based on your specific network conditions can be beneficial.

49152

Note that this setting is ignored if the client is using Sun Java version 1.6 due to a Java bug (http://bugs.sun.com/bugdatabase/view_bug.do"bug_id=6631048).

Tip #7 - Use Adaptive Parallel Content Transfer to Consume More Available Bandwidth

By default in most versions of UCF, content download operations will be done in a single thread. If sufficient network bandwidth is available, the download operations could perform significantly faster if the file was broken up into smaller pieces and transferred by multiple concurrent threads.

In 5.3 SP6 and D6.5 the UCF client can be configured to use multiple threads when downloading files. This is controlled in the ucf.client.config.xml file using the following parameters:

5


131072


300


131072

The "max.parallel.download.streams" parameter limits the number of threads that can be run concurrently when performing a parallel download. In this example, 5 separate streams could potentially be initialized. If one of the streams finishes their assigned task ahead of the others, it is then free to request a new range of bytes to be downloaded.

The "min.parallel.segment.size" parameter specifies that if the remaining portion of a document after a byte range is assigned is smaller than a specified value, it should not be assigned to a new thread. Rather the original thread's byte range should be extended to include those additional bytes. For example, if a thread is supposed to download 500Kb of a 600Kb file, as the remaining number of bytes is less than 128k, no new thread will be started and the original thread will assume ownership of those additional bytes.

The "Adaptive" part of parallel content transfer is controlled by the remaining two parameters. As tests have shown that disk I/O actually becomes a bottleneck and degrades performance if the content is transferred in parallel over LAN conditions, it is important to be able to control when the parallel content transfer is actually turned on. In this case, the UCF client will measure how many bytes were transferred initially by a single thread within a specified timeframe. If the number of bytes is less than what it expected, parallel content transfer will be turned on. If it is more than was expected, then it is assumed that bandwidth and latency are sufficient for a single thread to transfer the content most efficiently.

In the example above, the UCF client will measure the number of bytes that have been downloaded in the first 300ms of transfer (or as close to that time as possible). It will enable parallel content transfer if less than 131072 bytes (128k) have been downloaded, and disable it if more than 128k has been downloaded.

If your remote users have very high latency, it is likely that you will want to increase the "measurement.time.interval" to match the round trip time plus time to download a small portion of the file. For example, if you have 200ms round-trip latency, you might consider increasing the measurement.time.interval to 500ms to compensate for the time it takes for the request to reach the ACS server and start the content transfer.

In order to permanently disable parallel content transfer, all that must be done is changing the "max.parallel.download.streams" to 1, or decreasing the "single.thread.throughput" to a very small number, such as 1. In this case, regardless of the actual throughput, parallel content transfer will not be used. This is especially important in load testing scenarios, where many clients are being simulated from the same client machine.

Tip #8 - Tuning Content Download when Documentum User Directory is on a Network Drive

If the location of the Viewed and Checkout directories are on a network drive, or users regularly export content to a network drive, performance can be improved by setting the value of "ucf.file.buffer.size" to a larger number. The default value is 32768.

To set it for a single user, simply add the following to the ucf.client.config.xml on the client machine:

61440

To set the default for all users, add the same option to the ucf.installer.config.xml file on the application server and force a new version of UCF on the server side using the steps in Appendix B.

Tip #9 - Use UCF Client Logging to Measure performance

UCF Client logs are extremely useful when diagnosing UCF performance.

UCF client logging is enabled on the end user's machine.

Edit the ucf.client.logging.properties file, located at:
C:\Documents and Settings\\Documentum\ucf\\shared\config

For best results, set the log level to FINEST, as shown below:
handlers=java.util.logging.FileHandler, java.util.logging.ConsoleHandler
.level=FINEST
#-------------------
java.util.logging.FileHandler.pattern=C:/Documentum/logs/ucf.client%u.log
java.util.logging.FileHandler.limit=10485760
java.util.logging.FileHandler.count=10
java.util.logging.FileHandler.formatter=java.util.logging.SimpleFormatter
java.util.logging.FileHandler.encoding=UTF-8
#-------------------
java.util.logging.ConsoleHandler.level=OFF
java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter
In addition, to prevent the UCF client log from overwriting itself each time, change the value of java.util.logging.FileHandler.count to a number greater than 1. As each new client initializes, the old logs will be renamed and preserved for further analysis.

In the UCF client logs you will see entries such as "Logging request: getFile" and "Handled request: getFile" with timestamps. This can be used to better measure the time taken in the UCF pre-processing, content transfer and post-processing phases.

Appendix A:

Reduce the Effect of On-Access Scanning on UCF Initialization and Other Java Applets After Reboot
Right-click on the VirusScan icon in the system tray and choose "On Access Scan Properties.
Click on All Processes.
Click on Advanced.
Ensure "Scan inside archives" is NOT selected.
Click on the Detection tab.
Click on the Exclusions button.
Click on Add.
Add C:\Documents and Settings\s38737\Documentum\ucf , with "Also exclude subfolders", "On Read" and "On Write".
Click on OK to save.
Click Add to add another path.
Add C:\Program Files\Java with "Also exclude subfolders" and "On Read".
Click OK to save.
Appendix B:

Changing UCF Client Settings for All Users

1. Edit the \webtop\wdk\contentXfer\ucf.installer.config.xml file.
2. In this file, you will find the following line,
<"xml version="1.0" encoding="UTF-8"">
<"dctm fileVersion="5.3.0.1" compatibilityVersion="5.3.0.1"">


3. Change the highlighted text above from 5.3.0.XXX to 5.3.0.XXXa
4. Under the configurations tag, change or add the desired option.

value

The next time the UCF client engine is initialized on the client side, the new UCF settings will be downloaded and added to the ucf.client.config.xml file.

There may be cases where the "default" values in the ucf.installer.config.xml should not be applied to the client side. In this case, the "persistent" attribute can be added to the option on the client side. This will prevent any changes on the server side from being applied to that particular client.

value

If not specified, then persistent is set to false.

The persistent property can be specified on the ucf.installer.config.xml and in the ucf.client.config.xml. The following chart outlines the expected behavior:

Server Client Description
false false Server value will override client value.
true true Server value will override client value.
true true Server value will override client value.
false true Client value will not be overridden.

Commonly used DQLs for Documentum Admins. I update this blog whenever i get some good DQL to write , its for my personal reference as well as for other user if it helps anybody. Please use it at your own risk.

1- To see the audit trail for the particular user's login attempt to troubleshoot login related issues.

SELECT * FROM dm_audittrail
WHERE event_name='dm_connect'
AND user_name='user_name'

2- Group by clause by date to calcuate the number of documents create each day in the repository. Modify it accordingly as per your need.

select (DATEFLOOR(DAY, r_creation_date)) as r_MONTH , count(*)as cnt from amtrak_invoice where r_creation_date >= date('06/06/2011') GROUP BY (DATEFLOOR(DAY, r_creation_date))order by 1

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