JCA Connector 8 hosts, 165 users

[earnest.dyke]

Greetings all,

I have a need to create a JCA connector that will allow us to pool connections to our legacy ERP (running in UniData). Our topology is 8 servers each having any number of "accounts" (165 total across the 8 servers). These are NOT 165 unique user ids rather accounts. I need to be able to create a pool for each host/"account" combination but I really don't want to have to create 165 *-ds.xml files. Any one have any other ideas on how I might accomplish this?

Thanks in advance for any and all relevant responses.

Earnie!

[sfcoy]

You will probably get more focused attention for this kind of question over at IronJacamar.

My understanding is that the app server manages the pooling. JCA includes a matching mechanism so that you match connections by server/account if you need to do that.

[earnest.dyke]

Thanks Stephen, moved to IronJacamar.

Earnie!

[jesper.pedersen]

This is a job for JCA for sure, and you don't need a setup with 165 deployments - that is wrong

It should be modelled using a ConnectionRequestInfo object with the account information, one resource adapter for the whole thing.

Take a look at our code generator - http://docs.jboss.org/ironjacamar/userguide/1.0/en-US/html/codegenerator.html - to get started; "Use CCI" should be N ! And of course <security><application/></security>.

[earnest.dyke]

Thanks Jesper, I will look into this.

Earnie!

[earnest.dyke]

Jesper,

Another question comes to mind. You recommand using a single resource adapter and I can see that but I have 8 servers to which this will connect. If I use a single datasource all connections will be intermingled and in the same pool. I have a requirement to limit connections to each of the 8 servers separated so I was thinking one resource adapter implemented in 8 datasource defniitions that way I could control connects to each server. Is this the best way to do this?

Thanks!

Earnie!

[jesper.pedersen]

First of all - a resource adapter isn't a datasource.

If you want to limit account access per server, and you know the account names up-front, just do a <config-property> on the ManagedConnectionFactory with the account names in a "," separated String. Then verify the CRI information against that. And the pool will be divided based on the equallity of the CRI, so there is no "same pool".

Read http://docs.jboss.org/ironjacamar/userguide/1.0/en-US/html/introduction.html#overview_outbound - and look at http://docs.jboss.org/ironjacamar/userguide/1.0/en-US/html/samples.html#sample_helloworld

[jesper.pedersen]

It would probably be best to do an AdminObject where you can update the account names. So move the <config-property> to the ResourceAdapter instance, and enable ResourceAdapterAssociation for all your components.