Location of Service Binding Manager bindings.xml file

[pilhuhn]

I may miss something very obvious here:

configurations are selected on the command line with -c and the selected configuration would also select the port mappings from the service binding managers bindings.xml file.
Now when I want to run 2 configs on the same machine / IPs with different port bindings, I normally need to duplicate e.g. the 'default' directory (or at least data/, tmp/ and work/ ) per configuration.
If I duplicate the whole default/ directory, each instance 'ports-01', 'ports-02'
would have its own conf/bootstrap/bindings.xml file.
This seems odd to me, as it means that bindings.xml could completely different in all of the different instances. Bindings.xml should only exist in one instance at e.g. the jbossas/server/ level. This is how it effectively was in AS4, as users just commented in the MBean which was pointing to the single instance in docs/examples/

[jaikiran]

I agree that the default location of the bindingservice.beans (that's the name in 5.1.0.GA) doesn't actually need to be per server configuration. Instead i guess it could be moved out to a shared location.

However, even now the location of bindingsURI is configurable in server/servername/conf/bootstrap/profile.xml:

<property name="bindingsURI">${jboss.server.home.url}conf/bindingservice.beans</property>

I moved the bindingservice.beans to JBOSS_HOME/docs/examples and changed this property to

<property name="bindingsURI">${jboss.home.url}docs/examples/bindingservice.beans</property>

Worked fine.

[pilhuhn]

This needs to be the default in the future (perhaps not in docs/examples as those are no longer just examples ) as users are likely to forget to copy over the file and will then get strange results. Also the admin-console will need a definitive source of information.

[alrubinger]

If you'd like to change the default, recommend you propose the change w/ reasoning to jboss-development:

https://lists.jboss.org/mailman/listinfo/jboss-development

After some feedback we can look at opening a JIRA and making the change in trunk if there's consensus.

S,
ALR

[alrubinger]

Ah Heiko, didn't note you're "pilhuhn", sorry for the newbie instructions. :)

S,
ALR

[pilhuhn]

Well .. mail is sent anyway :-)

[emuckenhuber]

Yes the bindingserver configuration will move to a common location in AS6, but will remain as it is now for 5_x.

[pilhuhn]

Emanuel
I think this should go into 5.1.1

Heiko

[emuckenhuber]

"pilhuhn" wrote:
Emanuel
I think this should go into 5.1.1

Hmm well we can talk about moving that, but it seems quite confusing - as there are no other deployments coming from a common location.
For AS6 we are planning to move 'duplicate' deployments to a common location anyway - so i guess it would make more sense then.

But what exactly is the problem for the console, having the bindingservice there?

[brian.stansberry]

Back from vacation; plowed through the emails.

Thanks Jaikiran for the post on how the location can be moved.

Re: changing this for 5.1.1, I want to echo Emanuel's question: what's the issue for the console here? The SBM exposes an interface via the ProfileService ManagementView; that's the way a console should deal with this, which I would think would make the location of the file irrelevant.

BTW, Emanuel, Scott and I got a SBM management interface working right before I went on vacation and I had no time to document it for you Heiko. That is now corrected:

http://www.jboss.org/community/wiki/ServiceBindingManagerManagementInterface

I certainly agree that having this file be in a central location is the right thing to do for AS 6, but for 5.1.1 it becomes a kludge. It's been this way since 5.0.0 and I haven't heard any complaints about it from the community. Perhaps that just means people don't change this much.

Hmm, one issue is if the SBM content is changed via the PS ManagementView, the changes are stored in the target server's data/attachments dir. So they don't apply to all nodes that might be using a given SBM config.