Home› Documentum

EMC 6.0 - webservice consuming applications not working on deployment server

Respond
rvalenzuelarvalenzuela Ruben Valenzuela
edited December 25, 2008 in Documentum
Good morning,

I am writing to comment on a situation with our applications we have developed and tested in a development environment but have problems when passing to production.

We have the following configuration:
ProductionDevelopment
Dades: Administrator 6.0DAPRD Document: Document Manager 6.0
CSDES: Content Server 6.0 SP1CSPRD: Content Server 6.0 SP1
BDDES: Oracle 10.2.0.1BDPRD: Oracle 10.2.0.1
WebLoader: Application in Windows. NET 3.5
WebQuery: Web Application. NET 3.5

As I commented the applications in the development environment function properly allowing the massive load of documents - the first - and then view them from the web application. all the settings concerning the server are defined in the config files of weach application. Included is part of the file below

<configuration>
       <appSettings>
             <add key="mapfre.documentum.web.service.context.root" value="http://scl002001-007vp:9080/services"/>
             <add key="mapfre.documentum.web.service.module" value="core"/>
             <add key="mapfre.documentum.repository.name" value="RCL001"/>
             <add key="mapfre.documentum.repository.user.name" value="user"/>
             <add key="mapfre.documentum.repository.user.password" value="password"/>
       </ appSettings>
<connectionStrings/>

The production environment has been implemented by copying from development to a virtual image of CSDES to create CSPRD. Then we deleted the broker and docbase in CSPRD to point to the database BDPRD.

After all the tests we have doubts about the possibility that the virtual image of CDPRD could still have a "pointer" to the original machine CSDES.

For example the web application gives us the following error:
Server Error in '/ WebQuery.
________________________________________
Problem with the content server:
Service method "Execute" invocation failed.
Description: An unhandled exception when you run the current web request. Review the stack trace for more information about the error and where it originated in the code.

Exception Details: cl.mapfre.paperless.store.StoreException: Problem with the content server:
Service method "Execute" invocation failed.


Also, the load application gives us an error:
invocation failed.
Error storing file 00000017.tif: Service method "CreatePath" invocation failed.

What we seek:
• We would appreciate any hints or advice that will allows us to identify the cause of this problem.
• How can we administer DFS Server (WAS?), Configuration, permissions, logs, etc..

Sincerely,
Ruben Valenzuela

Answers

  • rvalenzuelarvalenzuela Ruben Valenzuela
    edited December 24, 2008

    I'd like to add further information.

    Checking up in services.msc I found that the "Documentum Java Method Server" is enabled but stoped. So I stoped all documentum related services and restarded. All went up and I thought it was OK, but my query still fails to respond.

    Then I did a search over documentum folder for all .log files and here I found this file DmMethodServerService.log:

    STATUS | wrapper  | 2008/12/24 10:20:47 | --> Wrapper Started as Service
    STATUS | wrapper  | 2008/12/24 10:20:48 | Launching a JVM...
    INFO   | jvm 1    | 2008/12/24 10:20:53 | Wrapper (Version 3.2.0) http://wrapper.tanukisoftware.org
    INFO   | jvm 1    | 2008/12/24 10:20:53 |
    INFO   | jvm 1    | 2008/12/24 10:21:16 | Starting Documentum Java Method Server Service components...
    INFO   | jvm 1    | 2008/12/24 10:21:23 | Starting Admin Server...
    INFO   | jvm 1    | 2008/12/24 10:21:23 | Admin Server started.
    INFO   | jvm 1    | 2008/12/24 10:21:23 | Testing Admin Server...
    INFO   | jvm 1    | 2008/12/24 10:23:48 | Admin Server test complete.
    INFO   | jvm 1    | 2008/12/24 10:23:54 | Starting Managed Server...
    INFO   | jvm 1    | 2008/12/24 10:23:54 | Managed Server started.
    INFO   | jvm 1    | 2008/12/24 10:23:54 | Testing Managed Server...
    INFO   | jvm 1    | 2008/12/24 10:33:58 | java.lang.Exception: Managed Server test failed.
    INFO   | jvm 1    | 2008/12/24 10:33:58 |  at com.documentum.install.servicewrapper.impl.Service.startComponent(Service.java:175)
    INFO   | jvm 1    | 2008/12/24 10:33:58 |  at com.documentum.install.servicewrapper.impl.Service.startAll(Service.java:240)
    INFO   | jvm 1    | 2008/12/24 10:33:58 |  at com.documentum.install.servicewrapper.impl.JavaServiceWrapperType3$StartupApplication.run(JavaServiceWrapperType3.java:183)
    INFO   | jvm 1    | 2008/12/24 10:33:59 | Stopping all service components.
    INFO   | jvm 1    | 2008/12/24 10:34:05 | Managed Server is already stopped
    INFO   | jvm 1    | 2008/12/24 10:34:11 | Stopping Admin Server...
    INFO   | jvm 1    | 2008/12/24 10:34:13 | Admin Server stopped.
    INFO   | jvm 1    | 2008/12/24 10:34:13 | All components stopped.
    STATUS | wrapper  | 2008/12/24 10:34:14 | <-- Wrapper Stopped

    it took the service 13 minutes to fail and stop.

    How can I troubleshoot this?

  • rvalenzuelarvalenzuela Ruben Valenzuela
    edited December 25, 2008

    Problem Solved!!

    Thought you might want to know that I solved the problem.

    As I mentioned in my first post the production server was an image of our development server - using VMWare -, what I  found on this "Documentum Java Method Server" service that there where some references hidden in some of the command files - .cmd - referencing the old installation. All I did was change it to the proper CS Server and it was solved.

    Hope this helps someone in the future.

Sign In or Register to comment.