UCF – Java 1.7.u45 Conflict

EMC just released ETA: UCF content transfer and file operations may experience operational issues for JRE version 1.7.u45.  There has been a change in the Java security model that can cause problems with the UCF if client and server are not using the same version of the JRE you are using a JRE earlier than 1.7u25.  The bottom line is that client and server should be upgraded to JRE 1.7.u45, or all should remain at JRE 1.7.u25 or earlier.  All WDK-based clients are affected.  Follow the link (and discussion in the comments section) for more details.


About Scott
I have been implementing Documentum solutions since 1997. In 2005, I published a book about developing Documentum solutions for the Documentum Desktop Client (ISBN 0595339689). In 2010, I began this blog as a record of interesting and (hopefully) helpful bits of information related to Documentum, and as a creative outlet.

6 Responses to UCF – Java 1.7.u45 Conflict

  1. David Lloyd says:

    Scott… I think you might have mischaracterized this a bit – it has nothing to do with the JRE version on the *server*, as far as I can see. The ETA only addresses the client JRE, as the issue is purely client-side. It does not mention anything about what JRE should be used on the server.


    • Scott says:

      I wondered about that a bit, the ETA is not completely clear. I don’t have any first-hand experience with it yet, but the ETA discusses issues with UCF and JRE 1.7.u25 talking to JRE 1.7.u45. That comment (in the ETA issue section), only made sense to me if the server was running a different version of the JRE than the client. You think different?


      • David Lloyd says:

        Yes; the issue affected us, and no action on the server side was necessary. I can see where the wording is confusing and might have suggested interaction between JREs, but what actually happened here is that 1.7 u45 raised the security baseline, and what this means is that even if you’re running 1.7 u25, the new security baseline WILL affect you since the JRE is “aware” that it is now outdated, by virtue of the Javascript LiveConnect interaction. More at https://blogs.oracle.com/java-platform-group/entry/updated_security_baseline_7u45_impacts.

        It’s a little difficult to grok, but when they’re talking about “LiveConnect changes in 1.7u45 that block UCF applet calls in Documentum WDK-based clients running on JRE version 1.7u25.” they’re still only talking about purely client-side JRE applet activity – nothing on the app server side.


      • Scott says:

        Thanks everyone for the clarification. Like I said, I have no first-hand experience with this problem yet. I have been out of the office all day and wanted to get this out quick so, forgive any inaccuracies. I have edited the post to reflect the discussion here (I hope).


  2. Andrey B. Panfilov says:

    There is no conflict at all. Oracle introduced new security model in u45, that is “incompatible” with previous u21 (see warning dialog matrix at https://blogs.oracle.com/java-platform-group/entry/7u45_caller_allowable_codebase_and – there is no win/win row for different JRE versions), latest WDK patches “support” (in meaning of “applet does not prompt warning dialog”) u45 but not u21. If you users still use u21 you should install these fixes: ftp://ftp2.lss.emc.com/Hotfixes/KnowledgeWorker/Webtop/6.7SP2/P08/hotfix%20for%20JRE%201.7%20update%2021%20-%206.7SP2%20P08/ or ftp://ftp2.lss.emc.com/Hotfixes/KnowledgeWorker/Webtop/6.7SP1/P22/hotfix%20for%20JRE%201.7%20update%2021%20-%206.7SP1%20P22/


  3. Pingback: Another Tech Advisory for Java and UCF | dm_misc: Miscellaneous Documentum Information

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: