Configuration for UCF Timeout error

Verify Java settings

Close ALL open browsers and applications.

Stop Java

• Start the Task Manager.
• Make sure that javaw.exe is not in the list of running processes.
• If it is in the Processes list, select it and click End Process. Make sure all your applications are closed so that nothing unrelated gets killed in the process. You must repeat this step for each javaw.exe process in the list.

Open the Java Control Panel

Clear the Java cache:

• On the General tab, in Temporary Internet Files section, click Settings.
• In the Temporary Files Settings popup, click Delete Files, then click OK.
• Clear EMC Java Certificates:
• • On the Security tab, click Certificates.
  • Select and Remove all certificates issued to "EMC Corporation".
  • When finished, click Close.

Make sure one version of Java is enabled:

• On the Java tab, click View.
• Make sure only one Java version has the Enabled checkbox selected. Click OK.
• Remark: the used JRE for our configuration is 1.7.0_65.

Disable next generation Java plug-in:

• On the Advanced tab, expand the Java Plug-in list. Uncheck Enable the next-generation Java Plug-in and click Apply.

Click OK to close to Java Control

Verify your browser settings

Clear browser cache and restore browser defaults for Internet Explorer 9

• In your browser, choose Tools > Internet Options.
• On the General tab, “Browsing history” section, click Delete. In the popup, select all checkboxes and click Delete, which closes the popup.
• On the Advanced tab, click the Restore advanced settings button, and Apply.

Enable "Automatic prompting"

• On the Security tab, select Trusted Sites. In the Security level for this zone section, click the Custom level button.
• In the Security Settings popup, scroll to Downloads, enable Automatic prompting for file downloads, and click OK.
• If prompted, confirm that you want to accept changes.
• Close the Internet Options window and close the browser.

Clear the Documentum cache

Important: Before performing the following steps, don't forget to check in any document that you have checked out in WebPublisher (wcm3). Otherwise, you will lose all your changes to the document!

We assume here that the client machines runs with Windows XP or 7 as an Operating System.

• Double-click on the My Computer icon on your desktop, or choose Start > Computer.
• On Windows XP: Navigate to the C:\Document and Settings\\Documentum folder.
• On Windows 7: Navigate to the C:\Users\\Documentum folder.
• Delete all content in the ucf folder and close the window.

Validate the results

• Possibly restart your PC.
• Open an Internet Explorer browser and open the web application wcm3.
• If you get either of the following popups, do the following:
• • "This is the first you have visited the [http://intragate.ec.europa.eu/wcm3] site. Do you want to trust content from this site?" Click Yes.
  • "Java has discovered application components that could indicate a security concern: ResidentUcfInvoker_LaunchRuntimeApplet_0." Click Run.
• Wait 2 to 3 minutes before continuing to the next step.
• Try to do the file operation that originally gave you the error message.

Export Content and corresponding metadata to the local machine using dfc

try
{
IDfSessionManager sessionMgr = null;
IDfClientX clientx = new DfClientX();
IDfClient client = clientx.getLocalClient();
sessionMgr = client.newSessionManager();
IDfLoginInfo loginInfoObj = clientx.getLoginInfo();
loginInfoObj.setUser("asdadad");
loginInfoObj.setPassword("dsadasdsa");
sessionMgr.setIdentity("XXX", loginInfoObj);
IDfSessionManager sesMgr = sessionMgr;
IDfSession session = sesMgr.getSession("XXX");
System.out.println("Session Created");

IDfExportOperation eo = clientx.getExportOperation();    
IDfQuery query=clientx.getQuery();          
IDfXmlQuery xmlQuery=clientx.getXmlQuery();          

query.setDQL("SELECT * FROM doc_type where r_object_id='XXXXXXXXXX'");            
IDfCollection collection=query.execute(session,IDfQuery.DF_READ_QUERY);          
while(collection.next())            
{

String docId=collection.getString("r_object_id");              
IDfId idObj = clientx.getId(docId);              
IDfDocument myObj = (IDfDocument)session.getObject(idObj);      
IDfExportNode node = (IDfExportNode)eo.add(myObj);              
node.setFilePath("D:/XXX/"+ myObj.getObjectName() + "."+myObj.getContentType());                                          
if (eo.execute()) {
System.out
.println("Export operation successful.");
} else {
System.out.println("Export operation failed.");
}
xmlQuery.includeMetaData(true);              
xmlQuery.setDql("select * from doc_type where r_object_id='"+docId+"'");            
xmlQuery.includeContent(false);              
xmlQuery.execute(IDfQuery.DF_READ_QUERY,session);            
FileOutputStream fos = new FileOutputStream("D:/XXX/"+myObj.getObjectName()+".xml");

xmlQuery.getXMLString(fos);
fos.flush();
fos.close();



}
}catch(DfException e)
{
e.printStackTrace();


} catch (IOException e) {
// TODO Auto-generated catch block
e.printStackTrace();
} 

JBOSS 6.3 error on Webtop 6.8 deploy: java.lang.SecurityException: Toolkit not encapsulated by a jar

After deploying Webtop 6.8 in JBoss 6.3 the services are available, but any request from Java clients fail with authentication errors that include this issue in the stack:

Caused by: java.lang.SecurityException: Toolkit not encapsulated by a jar.
    at com.rsa.jcm.f.hz.a(Unknown Source) [jcmFIPS.jar:6.1]
    at com.rsa.jcm.f.js.b(Unknown Source) [jcmFIPS.jar:6.1]
    at com.rsa.crypto.jcm.ModuleLoader.a(Unknown Source) [jcmFIPS.jar:6.1]
    at com.rsa.crypto.jcm.ModuleLoader.load(Unknown Source) [jcmFIPS.jar:6.1]

Cause

This issue happens only with deployments in JBoss-eap 6.3 when Webtop 6.8 is deployed as an ear file.

Resolution

1.     Delete the existing deployment of Webtop from JBoss, if any.

2.     Stop JBoss

3.     Change the webtop.war file extension to .zip

4.     Unzip the content in a folder with name "webtop.war" and place it in the JBoss deployment folder.

5.     Create an empty file "webtop.war.dodeploy" in same location.

6.     Start JBoss

7.     JBoss will deploy Webtop 6.8 and then change "webtop.war.dodeploy" file to "webtop.war.deployed". Once this happens, the deployment is complete.

8.     At this point, the error will not happen again.