Supporting config file(s) host specific settings

[davesiracusa]

I added support for substitution properties in jboss-esb.xml.  At construction time I merge properties from a soa-p.properties file to support host specific changes(sample below).  I either look for this file in a directory or load the file from from an embedded .ESB resource in directory name that matches the hostname I'm running on.  In order to do this I created a wrapper class which constructs out-of-box actons via reflection.

Perosnally I'd like to refactor and extend this for all config files (jboss-esb.xml, deployment.xml, jbm-queue-service.xml, etc).  I think this feature would be helpful to other developers as many of us have development, user testing, staging and production environments where host names, thread settings, JCA retry periods vary from environment to environment.  I know I can do this at build time, however it's nicer to have only one .ESB file for all servers.

Can I override the existing loader/provider, or perhaps you can point me to a central point in the SOA-P source where I can make my changes?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

<service category="Business Profile Services"
    name="AddressHub SOAP Proxy"
    description="AddressHub SOAP WebService Proxy"
    invmScope="GLOBAL">
      <property name="maxThreads" value="@maxthreads-addresshub@"/>

   <listeners>
    <http-gateway name="Index-ahsoap" urlPattern="addresshub/soap/*" />
   </listeners>

   <actions mep="RequestResponse">
       <action name="proxy"
        class="com.siracusa.soa.esb.bus.bpesb.actions.WrapSoapProxyAction">
         <property name="guest-class" value="org.jboss.soa.esb.actions.soap.proxy.SOAPProxy" />
       <property name="guest-configuration-rethrow" value="false" />
      <property name="guest-wsdl" value="http://@addresshub-host@/addresshubWebServices/soap?wsdl" />
            <property name="guest-cacheDoc" value="file://@wsdl-cache-directory@/addresshub.html"/>
                <property name="guest-docXSL" value="/transforms/wsdl-viewer.xsl"/>

       <property name="exceptionMethod" value="exceptionHandler" />
               <property name="wsdl" value="file://@wsdl-cache-directory@/addresshub.wsdl">
       <http-client-property name="max-total-connections" value="100" />
       <http-client-property name="max-connections-per-host" value="50" />
      </property>
    </action>
   </actions>
  </service>

[kconner]

You can already do this through the system properties, does this not work for you?

For example

<property name="guest-wsdl" value="http://${addresshub-host}/addresshubWebServices/soap?wsdl"  />

And defining the property using the usual -D notation or through the system properties service.

Kev

[davesiracusa]

Hi Kevin

My bad...I should have looked a little deeper.

I'll likely use my mechanism for transient properties.

I poll for file changes and notify each action of any changes at runtime.

Thanks,

Dave

[mikefinnx]

We had a similar case - wanting to have config properties that vary by environment. We looked at system properties, but wanted something more dynamic, so chose to build something similar, but wired into the jndi binding service instead. The hot deploy mechanism is already there and the props are just bound into JNDI. Pretty slick, actually. Might be a good add for the product.

FWIW.

Mike

[davesiracusa]

Kevin

I switched to system properties.  The only one I had problem with is the SOAPProxy wsdl property, it doesn't appear to support file:// too well.

I use a relative path and it gets annoyed.  I suspect this is a known bug.

best,

Dave

[davesiracusa]

We started using system properties specified in properties-service.xml.
When deploying a new/updated .ESB things work just fine.
When restarting SOA-P the properties don't resolve when loading our .ESB.

We specify system properties in:

     jbm-queue-service.xml

     jboss-esb.xml

If we rename the .ESB to .tmp and back again, things are okay.