DCO deploy on jboss

Any one deployed the dco.ear on jboss? If yes, can you send me some notes.

The instructions {Documentum Client for Outlook 6.5 SP1 Administration Guide.pdf}, do not mention it but as it is an ear it might just be possible.

Ideally I would like to deploy it on the JMS of the Content Server (D65sp2) for demo to client. Later can put it on better place....

Find more posts tagged with

Documentum

Comments

K.Chandru

You have to copy the dco ear file to the jboss server (JMS) to this location C:\Documentum\jboss4.2.0\server\DctmServer_MethodServer.

Restart the JMS will deploy the EAR file.

lastnitescurry

Thanks but already tried that and it does not work for the DCO war from D65sp1

K.Chandru

try extracting dco.ear file to dco.ear folder and restart jms

lastnitescurry

Thanks for you response but have you actually done what you said on the versions I am using?

For a finish I used dco.war from D65sp2 release and that will deploy on JBOSS or Tomcat.

kumarsan123

Hi Brian,

We didn't provide dco.war for 6.5SP1. if you are trying to deploy dco.war(extracted from .ear) then you must be having good amount of issue. so if you are deploying 6.5 SP1 then please deploy Documentum-Client-for-Outlook-WebService-6.5-SP1.ear on application server.

The dco.war was introduced from 6.5SP2 onwards. I would recommend tomcat for dco.war deployment Even you can use other application server. Prior to dco.war deployment you must have to deploy emc-dfs.war .

And If you are using 6.6 then there is good news for you. You will have one My-Documentum-for-Microsoft-Outlook-WebService-6.6.war. This war file include dfs services as well as dco services.

Thanks

lastnitescurry

I used the war from D65sp2 release.

Packaging the DFS and DCO into one war file may help some folks... But it is of no value if the DCO install documentation continues to be rubbish. I have been working with Documentum software since january 1999 and attempting to DCO working, wasted a weekend of my life.... even when I had a dco.war!!!

kumarsan123

If you have dco admin guide then you can find the deployment steps easily.

Just For information :

The emc-dfs.war and dco.war are two different archive files. you need to place it separately . Don't mix up into single war file. The dco.war has been customized based on the dco context path and services.

lastnitescurry

finding the install instructions for D65sp2 was not a problem... following them to get a working DCO system was...

* no mention of having to customised DA to display the Outlook configuration node

* no mention of having to include the 2 XML configuraiton files into the war

* no mention of having to edit file "/Cabinets/System/Applications/DCO/dco_custom_settings.xml", to add the repository to the list of repositories for clients... The client side message is really help full.... ACTUALLY NO IT WAS NOT!!!!

* no mention of the setting for DFS host..... It was however stated that you must have DFS installed on the same app server.... which is not necessary.

For now I do not have to worry about dco/mdo... and for that I am very glad.... From what I can see ye have done a lot of work but as always stopped short of the finish line.... poor deployment documentation... no client side SDK.... and lets not forget no way to create and configure a light weight sysobject type in D6.5+ so one is stuck with dm_messagearchived...

unfortunately my moment of not having to worry about dco/mdo will expiry around next October when the client will finally want the software they paid for two years ago, to work