This is the followup to my previous blog entry on WSRP and ebXML.

The Sun Java System Service Registry (Registry Server) can be installed on the same node as that of the Sun  Java System Portal Server or on a separate node using the JES installer. While installing the Portal Server the only Registry Server component that is required by the Portal Server is the Registry Server SDK. The SDK is the SPI for the JAXR API.  The SDK is automatically installed by the JES installer when installing the Portal Server.

Now in order to publish or discover WSRP artifacts, you'd need a Registry Server installed somewhere. Upon successful installation and configuration of the registry server, you should configure the Portal server so that it can authenticate to the Registry server to perform its tasks. Here are some highlevel configuration tasks.

Obtaining the Credentials :

    Registry Server uses certificates for authenticating the incoming request. The client of the Registry Server (which in our case is the Portal Server) should have a client certificates to authenticate itself to Registry Server. Follow the instructions here for creating an user and obtaining the certificate from the Registry Server.

Creating the keystores:

    Once the client certificate is available, We need to create a keystore some where in the /soar/3.0/jaxr-ebxml/security directory and import the certificate into the keystore. Use the standard java "keytool" command line interface to create the keystore and import the certificate into the keystore.

Configuring the Portal Server:    

    The Portal Server provides the SSOAdapter Service which allows services/users within the portal server to authenticate with an external service. There is an SSOAdapter named JES-REGISTRY-SERVER at the top level .

• Populate the values that are required in this SSOAdapter service.
• Make sure that the "amadmin" user has SSOAdapter service assigned.
• Finally restart  the cacao server.
  

Note on Configuration:

The JES-REGISTRY-SERVER has a property called "registry.keystorelocation" which is the location of the keystore relative to /soar/3.0/jaxr-ebxml/. So do not provide fullpath to the keystore

Publish and Search :

The psadmin command that portal provides has the following 2 subcommands

1. search-registry
2. publish-registry

these commands allows the administrator to publish/search for WSRP artifacts from the registry.

Note on Organizations:

In the previous blog, I did talk about Organizations, For those of you who were familiar with the Sun Java System Portal Server you may tend to think an Organization as an "org" as defined in the  Access Manager product. This does not necessarily map to this. For eg: If you are publishing the WSRP artifacts onto to a internet facing registry then it would make sense to put the actual organization name like "Sun Microsystems" , else if you are publishing to an intranet registry you may want to map it to Access Manager "Org".