| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Centralized configuration for Activation specifications? |
« View previous topic :: View next topic » |
| Author |
Message
|
| gs |
 Posted: Fri Jun 10, 2011 3:50 am Post subject: Centralized configuration for Activation specifications? |
 |
|
Master
Joined: 31 May 2007
Posts: 254
Location: Sweden
|
Since WAS v7 we're advised to use activation specifications instead of listener ports for MDB's.
However, what I find frustrating and confusing is why the connection details are configured directly in the activation specification.
With a listener port you reused a QCF, thus centralizing the configuration.
Is the current way to configure activation specifications defined by the JCA or by IBM and may there be a better way of configuring the activation specifications to centralize the config? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Jun 10, 2011 11:03 am Post subject: Re: Centralized configuration for Activation specifications? |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| gs wrote: |
Since WAS v7 we're advised to use activation specifications instead of listener ports for MDB's.
However, what I find frustrating and confusing is why the connection details are configured directly in the activation specification.
With a listener port you reused a QCF, thus centralizing the configuration.
Is the current way to configure activation specifications defined by the JCA or by IBM and may there be a better way of configuring the activation specifications to centralize the config? |
AFAIK the activation specification takes advantage of the deployment description and uses the jndi defined therein.
This is essentially no different from the listener port. You will still need to reference all the stuff that is needed somewhere in JNDI... That's your centralizer... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| gs |
| Posted: Tue Jun 14, 2011 6:53 am Post subject: |
|
|
Master
Joined: 31 May 2007
Posts: 254
Location: Sweden
|
But by using the deployment descriptor the developers would need to define the connection details during development.
Or what JNDI would be referenced in the DD? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jun 14, 2011 12:53 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| gs wrote: |
But by using the deployment descriptor the developers would need to define the connection details during development.
Or what JNDI would be referenced in the DD? |
The deployment descriptor essentially maps the JNDI as defined on the box to the JNDI calls used by the application.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
