Global JMS provider settings modification

waclaw
centeractive people
Posts: 44
Joined: 11 Sep 2012, 20:27

Global JMS provider settings modification

Postby waclaw » 13 Nov 2012, 16:01

Hi

Location of my ActiveMQ server has changed, and I wanted to update its configuration in Opensphere. I changed the global JNDI hostname and port properties in Tool -> Tool options... -> JMS Provider for ActiveMQ, but these modifications were not reflected in components connecting to ActiveMQ. I guess they should be, am I right?

thank you
waclaw
urs.minder
centeractive people
Posts: 68
Joined: 06 Jun 2012, 16:45
Contact:

Re: Global JMS provider settings modification

Postby urs.minder » 23 Nov 2012, 08:30

This is actually not a bug but it works as designed. In the early phases of Opensphere project work, you may define local resources such as JMS providers and JDBC connections within the tool options dialog. Tool options are often specific to your working environment, hence cannot easily be shared with other users. Projects on the other hand are supposed to be used by different users and will typically transit between distinct types of environments (POC, development, test etc.). Project resources (i.e. WSDL files) contained in the project file structure and the powerful concept of substitution variables allow for easy shift and adaptation on different platforms.

To prevent you from having to change the JNDI hostname and port in all your JMS messaging components, you should use substitution variables straight from the beginning when creating a new Opensphere projects.
waclaw
centeractive people
Posts: 44
Joined: 11 Sep 2012, 20:27

Re: Global JMS provider settings modification

Postby waclaw » 24 Nov 2012, 11:53

But for similar Tibco Rendezvous settings it is possible to alter them globally, and there's no need to touch RV components.
urs.minder
centeractive people
Posts: 68
Joined: 06 Jun 2012, 16:45
Contact:

Re: Global JMS provider settings modification

Postby urs.minder » 28 Nov 2012, 20:31

waclaw wrote:But for similar Tibco Rendezvous settings it is possible to alter them globally, and there's no need to touch RV components.

This can indeed be confusing. Different versions of Tibco Rendezvous (RV) cannot easily coexist on your computer, the reference to the valid installed RV installation is made when Opensphere is installed. The RV settings that can be change in the project properties dialog do not affect the reference to RV but the way Opensphere interacts with it. This project specific configuration remains valid if the project is ported to another computers provided RV is also installed there.
waclaw
centeractive people
Posts: 44
Joined: 11 Sep 2012, 20:27

Re: Global JMS provider settings modification

Postby waclaw » 30 Nov 2012, 17:40

urs.minder wrote:This is actually not a bug but it works as designed. In the early phases of Opensphere project work, you may define local resources such as JMS providers and JDBC connections within the tool options dialog. Tool options are often specific to your working environment, hence cannot easily be shared with other users. Projects on the other hand are supposed to be used by different users and will typically transit between distinct types of environments (POC, development, test etc.). Project resources (i.e. WSDL files) contained in the project file structure and the powerful concept of substitution variables allow for easy shift and adaptation on different platforms.

To prevent you from having to change the JNDI hostname and port in all your JMS messaging components, you should use substitution variables straight from the beginning when creating a new Opensphere projects.


I understand that substitution variables can help, but what if the user wasn't predictive enough at the very beginning of the work on a project?

Your argument is ability to move a project between various environments, but I think, that global resource definition fits into it. Let's say I have a project testing some JMS stuff, and my components are using "ActiveMQ" JMS resource. If JMS service's location changes (e.g. I move it from one server to another one, or change the port), I can easily modify global "ActiveMQ" configuration, so that all JMS components utilizing "ActiveMQ" resource are impacted. No need for substitution variables. Now, my colleague wants to use the project too. She clones it, and sees that the components require a JMS resource with "ActiveMQ" name. So she defines it in Opensphere global setting according to her own environment, and everything should work fine.

I find the above way more intuitive and less error prone, but it's just my opinion.

thanks
waclaw
urs.minder
centeractive people
Posts: 68
Joined: 06 Jun 2012, 16:45
Contact:

Re: Global JMS provider settings modification

Postby urs.minder » 01 Dec 2012, 13:30

Thanks for sharing your ideas on how you expect to use Opensphere. We agree that in the future the user should be able to switch to a different version of Tibco Rendezvous (RV) without having to reinstall Opensphere. Working with different versions of RV must be at least as flexible as working with different implementations and versions of JMS. The today distinction between RV and JMS properties should possibly be removed in a way that it's looks obvious to the user how they work. Therefore I created bug #1767 in or internal bug tracking system to be analyzed by our specialists.
malik378
Posts: 2
Joined: 20 Jan 2014, 11:08

Re: Global JMS provider settings modification

Postby malik378 » 20 Jan 2014, 11:10

To prevent you from having to change the JNDI hostname and port in all your JMS messaging components, you should use substitution variables straight from the beginning when creating a new Opensphere projects.
cisco ccna training cisco ccna training
pass4sure 70-646 pass4sure 70-646
bomber-jacket.org.uk http://bomber-jacket.org.uk
testking ccna testking ccna

Return to “Bug Reports”

Who is online

Users browsing this forum: No registered users and 1 guest