The Sun Portal Server 7 is integrated out-of-the-box with Sun Service Registry which allows WSRP artifacts to be published and discovered from the Service Registry. The integration implements some of the usecase mentioned in the ebXML-WSRP integration technote from OASIS

Sun Service Registry is a ebXML based implementation of an webservices registry server. In short Registry Server its a repository of metadata of contents. The registry also offers

1. Validation, Cataloging, Versioning & Lifecycle Management Service
2. Notification Service
3. Discovery & adhoc Query Service
4. Federated and inter registry links
5. Access Control Digital Signature etc.
6. Taxonomies, Classification etc.

A webservice is represented in an ebXML Registry through what is known as a Registry Information Model (ebRIM). Think of the ebRIM as a schema which describes how a service can be represented inside the ebXML registry.

The WSRP - ebXML Registry Technical note is the one which maps the WSRP artifacts to the ebRIM, It also defines some of the usecase on how these WSRP artifacts can be manipulated on the registry server.

To be more specific about WSRP artifacts representation with ebXML registry. The integration/technote allows publishing and discovery of the following WSRP artifacts

1. A WSRP Producer
2. A WSRP Portlet
   

Both the above artifacts are defined as "Services" using the ebRIM.

Apart from the above defined WSRP artifacts the specification allows binding or creating association with the following ebXML artifacts

1. An Organization
2. An Administrator/User

The relationship between the objects is as follows

• An Organization can have 'n' number of Producers (offers Producer Service)
• A Producer can offer 'n' number of Portlets
• An Organization can have 'n' number of administrators/users associated with it
  

The WSRP-ebXML tech note does not mandate that a Producer service should publish all the portlets that are available within the Producer. This is attributed to the fact that given a Producer service a Consumer can discover all the Portlets that are available in other words the WSRP Protocol itself provides discovery of Portlets published by an Producer.

Despite the above discovery mechanism supported by the Producer, there may be a need publish a portlet apart from the Producer that offers the portlets. This is mainly to facilitate finer search criteria's for a Consumer, while searching for portlets.

With the above defined bindings to the registry. A WSRP Producer Portal would have ability to

• Publish for a WSRP Producer
• Optionally publish or associate an Organization that offers this Producers
• Optionally publish the Portlets that this Producer Offers
• Optionally publish a user/administrator who is associated with the Organization
  

Alongside an WSRP Consumer Portal would have the ability to

• Search for a WSRP Producer
• Search for the WSRP Portlet
• Search for an Organization that offers WSRP Services
  

That wraps up short summary of the technote. Will try to post something on Sun Portal specific configuration and steps for doing the above sometime later.