OSB: Passing environment specific properties to JAR resource.

Question

Hi,
My scenario is as follows.
As part of our proxy service message processing, we make a LDAP lookup which is done via a java callout to a static method which does the ldap call.
Atm the ldap url & other properties are hard coded in the java class, but we need to make this configurable as these values differ in each environment.
What is the best way to solve the above problem? property files? some sort of XML config?
Our Environment: OSB 10.3, workshop 10.3, jdk 1.6.0_05.
P.S We release a single package containing the sbconfig.jar which is deployed on all environments and a environment specific package which contains the customization file for that environment.

Answer 1

atheek1 wrote:
How do I do this? I was not aware that we could modify the xquery references in message flow. Is this even possible?You are not modifying xquery resource. OSB provides a feature called Customisation file to modify values and references specific to that environment when you do a deployment to that environment. There are different customisation types within the customisation file and you need to use reference customisation so that the proxy service refers to the correct env specific property file.
Google 'customisation file' if you are new to this.Thanks, I figured that out.
But this means that in the first global build of the sbconfig.jar I have to include the xquery files for all environments. And in the customization process I change the reference in the proxy service to the proper environment specific xquery file.
This seems a bit clunky, as the xquery files for all environments would be deployed on the server. Ideally we should only ever include the xquery for that particular environment.
Is there any other way to accomplish this?
Can we define a JNDI provider that points to a ldap configuration?