Publishing Producer Details to ebXML Registry

Publishing a producer stores producer details in any one of the repositories, such as Sun Java System Service Registry Server or an ebXML Registry server. After a producer is published, you can search for the details of the producer using the application interface or using the command-line interface. For details on setting up Sun Java System Service Registry Server, see the Service Registry 3.1 Administration Guide.

You need to configure Sun Java System Portal Server for Registry to publish the producer details to the registry.

To Configure Sun Java System Portal Server for Registry

1. Create the directory, /soar/3.0/jaxr-ebxml/security, in the machine where Portal Server is installed.

2. Copy keystore.jks from Registry Server's /var/opt/SUNWsrvc-registry/3.0/data/security directory to /soar/3.0/jaxr-ebxml/security.

3. Log in to the Portal Server management console.

4. Select the Portals tab.

5. Select a portal server from Portals.

6. Click SSO Adapter from the submenu.

7. Click JES-REGISTRY-SERVER.

   The Edit Meta-adapter - JES-REGISTRY-SERVER screen appears.

8. Type the details.

   If you are accessing the registry server through a proxy:

   http.proxy.host

   Hostname of the proxy server.

   http.proxy.password

   Proxy password if proxy server required authentication.

   http.proxy.port

   Port on which proxy server is available.

   http.proxy.user

   Proxy username if proxy server required authentication.

   If you are not using a proxy server:

   registry.keypassword

   Password that is required to get the key from the keystore.

   registry.keystorealias

   The key alias that is present in the keystore that is to be used for authenticating with the registry server.

   registry.keystorelocation

   Location of the keystore relative to /soar/3.0/jaxr-ebxml/.

   registry.keystorepassword

   Password used to open the keystore.

   registry.publishurl

   URL of the registry server where publish request should be sent. This URL should accept SOAP requests.

   registry.queryurl

   URL of the registry server where search request should be sent. This URL should accept SOAP requests.

To Publish Producer Details to Registry

The following steps explain how to publish a producer to the Registry Server:

1. Create organization data and producer data files.

   Organization data file can contain the following entries:

   org.name=Sun Microsystems

   org.description=Description

   org.primarycontact.name=Henry

   org.primarycontact.phoneno=1234567

   org.primarycontact.email=someone@host.com

   ---

   Note –

   The org.name and org.description should be similar as that of the details in Identity Server unless the Registry is deployed internally.

   ---

   The producer data file should have the following entries:

   producer.name=Producer_name

   producer.description=Producer_Description

   producer.id=Producer_ID

   ---

   Note –

   It is not a must that you should create all the data files. But, for searching the details of producer, organization, or portlet, you should have created at least one file associated with that.

   ---

2. Stop and restart the common agent container:

   /usr/lib/cacao/bin/cacaoadm stop

   /usr/lib/cacao/bin/cacaoadm start

3. To publish the produce details, use the following command:

   ./psadmin publish-registry -u amadmin -f password_file -p portal1 -m producer -U producer_data_file -O organization_data_file -T portlet -L --debug

   ---

   Note –

   The portlet file specifies the portlets that are offered by WSRP producer. The portlets list is specified as a string within double quotes and elements separated by space. For example, "NotepadPortlet BookmarkPortlet WeatherPortlet."

   ---

   ---

   Note –

   You can check the log file by using the following command: more var/opt/SUNWportal/logs/admin/portal.admin.cli.0.0.log

   ---

Equivalent psadmin Command

psadmin publish-registry