<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<body link="#355491" alink="#4262a1" vlink="#355491" style="background: #e2e2e2; margin: 0; padding: 20px;">
<div>
<table cellpadding="0" bgcolor="#FFFFFF" border="0" cellspacing="0" style="border: 1px solid #dadada; margin-bottom: 30px; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td>
<table border="0" cellpadding="0" cellspacing="0" bgcolor="#FFFFFF" style="border: solid 2px #ccc; background: #dadada; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td bgcolor="#000000" valign="middle" height="58px" style="border-bottom: 1px solid #ccc; padding: 20px; -moz-border-radius-topleft: 3px; -moz-border-radius-topright: 3px; -webkit-border-top-right-radius: 5px; -webkit-border-top-left-radius: 5px;">
<h1 style="color: #333333; font: bold 22px Arial, Helvetica, sans-serif; margin: 0; display: block !important;">
<!-- To have a header image/logo replace the name below with your img tag -->
<!-- Email clients will render the images when the message is read so any image -->
<!-- must be made available on a public server, so that all recipients can load the image. -->
<a href="http://community.jboss.org/index.jspa" style="text-decoration: none; color: #E1E1E1">JBoss Community</a></h1>
</td>
</tr>
<tr>
<td bgcolor="#FFFFFF" style="font: normal 12px Arial, Helvetica, sans-serif; color:#333333; padding: 20px; -moz-border-radius-bottomleft: 4px; -moz-border-radius-bottomright: 4px; -webkit-border-bottom-right-radius: 5px; -webkit-border-bottom-left-radius: 5px;"><h3 style="margin: 10px 0 5px; font-size: 17px; font-weight: normal;">
Integrate JBoss SOA-P and SOA Software registry
</h3>
<span style="margin-bottom: 10px;">
created by <a href="http://community.jboss.org/people/ScottDawson">Scott Dawson</a> in <i>JBoss ESB Development</i> - <a href="http://community.jboss.org/message/579527#579527">View the full discussion</a>
</span>
<hr style="margin: 20px 0; border: none; background-color: #dadada; height: 1px;">
<div class="jive-rendered-content"><p>I just modified a JBoss SOA Platform instance to use the SOA Software registry. I noticed that there is a JIRA issue (<a class="jive-link-external-small" href="https://issues.jboss.org/browse/SOA-1478">https://issues.jboss.org/browse/SOA-1478</a>) regarding updating the JBoss-SOA Software integration documentation for SOA-P 5.x and I think I can give you most of the required updates based on my experience.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>My software versions are:</p><p>JBoss SOA Platform 5.0.2.GA</p><p>SOA Software Service Manager 5.2 + updates through sm52-update-3.44</p><p>Linux (RHEL 5.5)</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>I used the SOASoftwareIntegration.pdf that ships with JBoss ESB 4.7. The list that follows are the points where I had to do something different from what is shown in that document.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>1. The example URLs in the document are based on UDDI v2. I chose to make everything UDDI v3 compatible so the  SOA Software URLs specified in jbossesb-properties don't need the "_v2" suffix as shown in the document. SOA Software's UDDI v3 URLs don't have the version number appended. Also, I had to specify the securityManagerURI in addition to the queryManagerURI and lifeCycleManagerURI shown in the document. Without the securityManagerURI, Scout errors occur.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>2 I had to specify 2 registry interceptors in jbossesb-properties, again, to eliminate Scout errors. Fortunately, this configuration appears commented out in the file, so I only had to uncomment it:</p><p> <property name="org.jboss.soa.esb.registry.interceptors"</p><p>                value="org.jboss.internal.soa.esb.services.registry.InVMRegistryInterceptor, org.jboss.internal.soa.esb.services.registry.CachingRegistryInterceptor"/></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>With these changes, here is the resulting 'registry' section in the jbossesb-properties file, which is located in the server/<profile>/deployers/esb.deployer directory:</p><p><code> </p><p>    <properties name="registry"></p><p>        <property name="org.jboss.soa.esb.registry.uddi.maxRows" value="100"/></p><p><span>        <property name="org.jboss.soa.esb.registry.queryManagerURI" value="</span><a class="jive-link-external-small" href="http://soa01:9901/uddi/inquiry" target="_blank">http://soa01:9901/uddi/inquiry</a><span>"/></span></p><p><span>        <property name="org.jboss.soa.esb.registry.lifeCycleManagerURI" value="</span><a class="jive-link-external-small" href="http://soa01:9901/uddi/publish" target="_blank">http://soa01:9901/uddi/publish</a><span>"/></span></p><p><span>        <property name="org.jboss.soa.esb.registry.securityManagerURI" value="</span><a class="jive-link-external-small" href="http://soa01:9901/uddi/security" target="_blank">http://soa01:9901/uddi/security</a><span>"/></span></p><p>        <property name="org.jboss.soa.esb.registry.implementationClass" value="org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl"/></p><p>        <property name="org.jboss.soa.esb.registry.factoryClass" value="org.apache.ws.scout.registry.ConnectionFactoryImpl"/></p><p>        <property name="org.jboss.soa.esb.registry.user" value="administrator"/></p><p>        <property name="org.jboss.soa.esb.registry.password" value="password"/></p><p>        <!-- the following parameter is scout specific to set the type of communication between scout and the UDDI (embedded, rmi, soap) --></p><p>        <property name="org.jboss.soa.esb.scout.proxy.transportClass" value="org.apache.ws.scout.transport.AxisTransport"/></p><p>        <property name="org.jboss.soa.esb.scout.proxy.uddiVersion" value="3.0"/></p><p>        <property name="org.jboss.soa.esb.scout.proxy.uddiNameSpace" value="urn:uddi-org:api_v3"/></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>        <property name="org.jboss.soa.esb.registry.interceptors"</p><p>                value="org.jboss.internal.soa.esb.services.registry.InVMRegistryInterceptor, org.jboss.internal.soa.esb.services.registry.CachingRegistryInterceptor"/></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>        <!-- The following properties modify the cache interceptor behaviour --></p><p>        <property name="org.jboss.soa.esb.registry.cache.maxSize" value="100"/></p><p>        <property name="org.jboss.soa.esb.registry.cache.validityPeriod" value="600000"/></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>        <!-- Organization Category to be used by this deployment. --></p><p>        <property name="org.jboss.soa.esb.registry.orgCategory" value="org.jboss.soa.esb.:category"/></p><p>    </properties></p><p></code></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>It appears that everything is working correctly. The app server comes up without errors and I see a couple of services in the 'Red Hat/JBossESB' organization in Service Manager. Based on past experience with the community version ESB (and the screenshots in the document), I expected to see more JBoss internal services but only 2 currently appear in the registry: DeadLetterService and JBpmCallbackService.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>I hope this is helpful.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Regards,</p><p>Scott Dawson</p><p>Unisys</p></div>
<div style="background-color: #f4f4f4; padding: 10px; margin-top: 20px;">
<p style="margin: 0;">Reply to this message by <a href="http://community.jboss.org/message/579527#579527">going to Community</a></p>
<p style="margin: 0;">Start a new discussion in JBoss ESB Development at <a href="http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2032">Community</a></p>
</div></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>