Lastly, I apologize for the horribly formatted post!
The editor kept erasing my content and giving me a "you cannot post a blank message" error.... so I had to post in pieces in order to get around that error.
Hey there ecmdeveloper:
Wow. You really covered all bases with this posting which is quite impressive. We appreciate that you sent us an explanation as to why we received 5 email postings from your question! Thank you.
I don't think there is any other clarifications that will be necessary in regards to your inquiry.
The Documentum Community is more suited for the business/product big picture inquiries. Therefore, I have moved your posting over to the Developer Community where these type of detailed technical questions are best suited and addressed.
Developer Community - can you reach out on this posting?? Many thanks.
Best regards,Kelly
Hello!
Try to clean-up java cache (while browser with webtop is working in tray call context menu on java icon, select Java Control Panel -> tab General -> Settings -> Delete Files)
Try to clean-up Documentum folder in user's profile.
Thanks for the reply, but that didn't seem to help.
I didn't mention, but I have tried to be diligent in my cache cleanup. I have cleared the java applet cache, as you suggested. I also deleted the ucf and ucf-java folders from the user's documentum directory on the client machines. This time, I deleted the entire Documentum directory under c:\users\user1\documentum.
I also have been clearing the browser cache and restarting the browser between attempts.
Is there a specific DNS name that must be used in order for the UCF applets to work? I've tried a number of urls (mapped via hosts file), each one prompts me to trust content, so I would assume that the dns name isn't restricting the applet's access. Also, when I navigate to the DA app, the java icon appears in the taskbar. So, it appears that the applet is launching.
thanks again.
Did you fill dfc.globalregistry.password, dfc.globalregistry.repository, dfc.globalregistry.username options in dfc.properties file for war?
Does export work well?
I did set the dfc.properties, but I just now noticed that there are two copies created in the content server installation.
One had my password as MmKZP8KOlvrE6ndUolyl6Q\=\= and the other had MmKZP8KOlvrE6ndUolyl6Q==
(it's the word "password" encoded)
I coped the version with the back-slashes. I just ran the command line encoder and it didn't have the back-slashes, so I switched the string in the dfc.properties located in the WAR file's WEB-INF/classes directory.
I deleted the client's documentum directory, including the ucf directories, but it didn't appear to make a difference with my issue. I did verify that the dfc.properties created in the client's Documentum\config directory was the non-back-slash version, so it does appear to be pushing the new version out.
#dfc.docbroker.host[0]=
#dfc.globalregistry.repository=#dfc.globalregistry.username=#dfc.globalregistry.password=
dfc.docbroker.host[0]=dctm65.testserver.netdfc.globalregistry.repository=dmdevdfc.globalregistry.username=dm_bof_registrydfc.globalregistry.password=MmKZP8KOlvrE6ndUolyl6Q==
When I attempted to export, I received the below error:
16:32:32,836 WARN [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] com.documentum.ucf.server.transport.impl.InitGAIRConnectorServlet - com.documentum.ucf.server.transport.impl.UnrecoverableTransportException: HTTP session is not properly initialized at com.documentum.ucf.server.transport.impl.InitGAIRConnectorServlet.doPost(InitGAIRConnectorServlet.java:48) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at com.documentum.web.servlet.ResponseHeaderControlFilter.doFilter(ResponseHeaderControlFilter.java:317) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at com.documentum.web.servlet.CompressionFilter.doFilter(CompressionFilter.java:108) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at com.documentum.web.env.WDKController.doFilter(WDKController.java:76) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Initially, there was no error in the client's browser, but I received the attached error message once I started my subsequent export action.
I also have installed an Apache HTTP Server v2.2 with the WL module so I could try to communicate directly with that instead of directly with the WebLogic server. This made no difference.
Could there be an issue with my version of WebLogic? The compatibiltity matrix says Oracle WebLogic 10.3 is acceptable, but I'm on 10.3.2... Perhaps that's the snag? I'll attempt to see if I can install on Tomat 6.0.18.
Is there a simple way to verify if the global registry is enabled successfully for a repository? I know that I configured it during the configuration process, but I'd like to double check at this point...
Thanks again for your help!
A quick update:
I deployed my same WAR to Tomcat 6.0.18 (using jdk 1.5_06) and I was able to successfully import & export a doc via UCF.
I will have to do some more testing to verify that all's well on this app server, but it appears to be working out better that the WebLogic 10.3.2 Server.
Thanks again for your help & I hope that this thread helps others.
Hello,
There are a few bugs in the UCF functionality in Documentum 6.5
Kindly refer this thread
https://community.emc.com/message/185909#185909
Also the Bug Issue No:167102
Turning of ACS in the wdk/app.xml fixed the issue for me.
Hope this piece of info helped you.
Thanks,
Vijay
Yeah, I remember that "try it a second time" issue with ACS back from the 5.3 days. I assumed they would have it fleshed out by now.
It's a different error, but good information none-the-less.
I'll try to enable UCF, but disable ACS, on my weblogic instance when I get a chance in the next few days. I'm currently away from that server.
Thanks for the lead!
Hello, ecmdeveloper!.
> I'll attempt to see if I can install on Tomat 6.0.18.
This simple app server will show the propriety of war file.
> Is there a simple way to verify if the global registry is enabled successfully for a repository?
You can use any Documentum client (e.g idql32, your sample java class) to connect to repository with dm_bof_registry account.
I've tried to access with IE 6 & 7 as well as firefox 3.0 & 3.5
From ucf.client0.log
Dec 4, 2009 10:40:27 PM com.documentum.ucf.client.logging.impl.UCFLogger fatalSEVERE: Unrecoverable stream error: HTTP session is not properly initializedcom.documentum.ucf.common.transport.TransportStreamException: Unrecoverable stream error: HTTP session is not properly initialized at com.documentum.ucf.client.transport.impl.ClientReceiver.getRequests(ClientReceiver.java:53) at com.documentum.ucf.client.transport.impl.ClientSession.handshake(ClientSession.java:622) at com.documentum.ucf.client.transport.impl.ClientSession.handshake(ClientSession.java:601) at com.documentum.ucf.client.transport.impl.ClientSession.run(ClientSession.java:215)
Alexey, good point on verifying if the default bof user exists. But, is there a flag on the dm_server_config object or anything like that that undoubtedly signifies a repo as the "global repo"? I'll admit that I haven't done much digging on this myself, so no worries if you don't know off-hand. I'm thinking there might be some info in the Object Reference document.
Thanks all.
Has anyone figured this issue out? We have just upgraded from WP 5.3 SP4 on Weblogic 8.1 to WP 6.5 SP1 on Weblogic 10.3, and now we are unable to import or export due to this problem.
On which version of java is your weblogic domain running? I believe that my instance was running on 1.6, which was bundled with the weblogic install, but documentum wants 1.5_06 (i believe).
I can't remember if I verified this, but it did work when I switched jre versions on tomcat.
Let me know if that works for you!
-ryan
Hi Jason,
Try disabling acs in the app.xml and then try the Import. It should work.
Post back ur findings.
Did this issue solved? We have a exact same issue.
hi
i am facing the same issue when import we have 6.6 can any one help me plz. depolying the same war on tomcate works fine.
fadi
Hey have you got a solution to the bug.Even I am facing the same problem but while importing and viewing documents.My webtop 6.6 has become totally useless and I am not able to work on it.Its webtop 6.6 with weblogic as the app server.
yes pleas do the follwoign it shall fix your issue
Add the following descriptor to web-inf\weblogic.xml and re-deploy:
<session-descriptor> <cookie-http-only>false</cookie-http-only> </session-descriptor>
Hi mo7eb,
I made the changes suggested by you but they did not seem to work.
I redeployed my application after making those changes in the weblogic.xml file.
Still I am getting this error:
Jun 13, 2011 8:12:49 PM com.documentum.ucf.client.logging.impl.UCFLogger fatalSEVERE: stdOutErrType 2; msg = Exception in thread "Thread-15" com.documentum.ucf.common.transport.TransportError: com.documentum.ucf.common.transport.TransportStreamException: Unrecoverable stream error: HTTP session is not properly initialized at com.documentum.ucf.client.transport.impl.ClientSession.run(ClientSession.java:449)Caused by: com.documentum.ucf.common.transport.TransportStreamException: Unrecoverable stream error: HTTP session is not properly initialized at com.documentum.ucf.client.transport.impl.ClientReceiver.getRequests(ClientReceiver.java:53) at com.documentum.ucf.client.transport.impl.ClientSession.handshake(ClientSession.java:655) at com.documentum.ucf.client.transport.impl.ClientSession.handshake(ClientSession.java:634) at com.documentum.ucf.client.transport.impl.ClientSession.run(ClientSession.java:248)
My weblogic is weblogic 11g
Webtop 6.6
Please Help.