Using SSL with the UDDI JAXR provider

You can use Secure Sockets Layer (SSL) to encrypt HTTP traffic between the Java API for XML Registries (JAXR) provider for UDDI and the UDDI registry.

About this task

Deprecated feature Deprecated feature: From WebSphere® Application Server Version 8.0, Java API for XML Registries (JAX-R) APIs are deprecated. The Java Platform, Enterprise Edition (Java EE) 6 platform began the deprecation process for JAX-R because it is based on Universal Description, Discovery and Integration (UDDI) 2 technology, which is no longer relevant. If your applications use JAX-R, then you might consider using UDDI 3.depfeat
To use SSL, set the JAXR client program as follows.

Procedure

  1. For the javax.xml.registry.queryManagerURL and javax.xml.registry.lifeCycleManagerURL connection properties, specify a URL with the protocol https and the appropriate port to use SSL to access the UDDI registry. The default port of the UDDI registry for HTTPS is 9443. Often, only the lifeCycleManager URL, that is, the UDDI Publish API URL, requires SSL.
  2. Add a new security provider to the java.security.Security object, according to the Java Secure Sockets Extension (JSSE) implementation that is used. If running under the JVM provided in WebSphere Application Server, the JSSE that is provided by IBM® is on the classpath automatically. Use the following code to add the IBM security provider:
    java.security.Security.addProvider(new com.ibm.jsse.JSSEProvider());
  3. Set the javax.net.ssl.trustStore system property to the file name of the client trust store file. The client trust store file is a Java key store (.jks) file and must contain the server certificate of the UDDI registry. To manage key store files, you can use the iKeyman tool.
  4. Set the javax.net.ssl.trustStorePassword system property. This property is the password used to open the client trust store file.
  5. Optional: If you use a JVM version that is earlier than the version that is provided with WebSphere Application Server, you might need to set the java.protocol.handler.pkgs system property to com.ibm.net.ssl.internal.www.protocol.

What to do next

For more information about SSL and the iKeyman tool, see the topic about secure communications using SSL.

Task topic    

Terms and conditions for information centers | Feedback

Last updated: April 20, 2014 08:46 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=twsu_jaxr_sec
File name: twsu_jaxr_sec.html