I was told you might be able to help with the following problem. Thanks for any suggestions and let me know if you need any more detail to help identify the source of this problem.
When using the CMIS Workbench to connect to one of our repositories, I am getting the following certificate error: On the same machine I am able to connect to the same repository through Java code running on a local Websphere server. For that, I added the appropriate certificate from our repository server to the WebSphere server environment and I get no errors. Thinking that a similar type of action could solve the Workbench issue I have tried the following things: Adding this to the Java control panel "exception site list" on my machine, but that also did not help. I added it to this row in the workbench.sh file which also did not make any difference: JAVA_OPTS="-Dcmis.workbench.url=http://localhost:8081/inmemory/atom -Dcmis.workbench.user=test -Dcmis.workbench.binding=atompub -Dcmis.workbench.acceptSelfSignedCertificates=true -Djava.net.useSystemProxies=true " As far as the JVM that is being used, the code that runs successfully does run under a different JVM than the Workbench uses: for the workbench I see this: com.ibm.system.agent.path = c:\Program Files\IBM\SDP\jdk\jre\bin com.ibm.vm.bitmode = 64 For my code, which is running in my local websphere environment I have this: C:\Program Files\IBM\SDP\runtimes\base_v7 So that tells me they are not the same which is what I would have expected. Regards, David L. (Dave) Walling C F 0 1 0 1 3 0 - Senior Application Programmer, Global Automation and Productivity Phone: 1-720-395-9755 | Mobile: 1-301-573-3943 E-mail: dlwa...@us.ibm.com 6710 Rockledge Dr Bethesda, MD 20817-1827 United States
