DFS Install + Content Server 5.3

Hello,

I am having trouble getting the DFS 6.5 setup correctly so that it can be called and access our content servers.

We are running:

Linux Content Servers off of tomcat with DFC 5.3 sp4

Linux App Servers running Oracle App Server 10.1.3.3

I got the DFS installed by dropping the EAR file and updating a jar file that was defined wrong in the ear file (jaxws-rt-2.0.jar)

<appserver>/services/core/ObjectService/ page comes up and shows all the links to the WSDL's for the services

I edited the TQueryServiceTest case that came with the dfs-sdk install, and i constantly get the error:

Exception in thread "main" java.lang.NoClassDefFoundError
     at com.emc.documentum.fs.datamodel.core.context.SsoIdentity.(SsoIdentity.java:63)
     at com.emc.documentum.fs.rt.impl.handler.ServerContextHandler.handleMessage(ServerContextHandler.java:70)
     at com.emc.documentum.fs.rt.impl.handler.ServerContextHandler.handleMessage(ServerContextHandler.java:1)
     at com.sun.xml.ws.handler.HandlerProcessor.callHandleMessage(HandlerProcessor.java:284)
     at com.sun.xml.ws.handler.HandlerProcessor.callHandlersRequest(HandlerProcessor.java:135)
     at com.sun.xml.ws.handler.ServerSOAPHandlerTube.callHandlersOnRequest(ServerSOAPHandlerTube.java:133)
     at com.sun.xml.ws.handler.HandlerTube.processRequest(HandlerTube.java:116)
     at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
     at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
     at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
     at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
     at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
     at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
     at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
     at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)
     at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doGet(WSServletDelegate.java:129)
     at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doPost(WSServletDelegate.java:160)
     at com.sun.xml.ws.transport.http.servlet.WSServlet.doPost(WSServlet.java:75)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)

Even though the previous line showed that SsoIdentity class was in the build path, and was returned by a Class.forName() call..

Any help would be greatly appreciated.

Find more posts tagged with

Comments

zhou_simonq

it seems that you haven't include the DFS client SDK when running the sample code.

i don't know whether there will be problems of your configuration. If possible, pls use DFS 6.5 for Content Server 6.5.

--simon

Jingzhi

It sounds like some version conflicts. Make sure DFS 6.5 support Oracle App Server 10.1.3.3 ?

And, you say "updating a jar file that was defined wrong in the ear file (jaxws-rt-2.0.jar)“, I don't know what's wrong about the jar?

Why you updating that?

DavidHaveman

There was a class file defined inside of the version of that jar file that came with the DFS install that when the installer ran, it through a NoSuchMethodError, and failed the install. It was a getter method that the program was expecting it to have no parameters but the version in the dfs install bundle had a String as a paramater. I searched for a while and found an updated jar file that had that same function in it with no parameters. Once i dropped that new jar file into the app servers library area, the install worked, and the wsdl's showed up properly.

Jingzhi

Pls post the whole exception stack.

1. Don't use the installed dfs, but try to deploy dfs.ear (without any modification) package on a tomcat server, and run your test against that; 2. Make sure all the dfs sdk libs set in the class path;

david.matheson

Quick note, Jingzhi probably means the DFS war, not the ear. The ear will not deploy on Tomcat.

DavidHaveman

Hey all,

So since posting this i went to EMC world 2010 and one of the EMC techs said we could deploy the DFS.ear file to our Application servers (or any other server really...) and you really shouldn't deploy (or have it still deployed) to the content server...

So.. im trying to figure out how to do this?

we have Oracle App Servers v 10.1.3.3 and Documentum 6.5 content servers..

Any ideas?

Thanks,