| Author |
Message
|
| fmottais |
 Posted: Wed Jun 13, 2007 7:19 am Post subject: deploy big applicative jars best practice |
 |
|
Novice
Joined: 30 May 2007
Posts: 10
|
Hello,
i have two brokers WMB 6.0.3 in the same server (unix AIX).
I have put the jars which doesn't change in shared-classes (drivers,...).
But i have two application's versions (developpement and homologation) and i would like the two environments works together with their versions.
The applicative's jar are too big and when they are in the bar, i can't deploy it with the toolkit.
If i put all the jars in shared-classes, i can deploy my process flow without the jars but the two versions can't live together. How can i deploy my two versions without put it on shared-classes.
What are the best practices?
Thanks |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Jun 13, 2007 7:22 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I believe the best practices are not to share machines.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fmottais |
| Posted: Wed Jun 13, 2007 7:35 am Post subject: |
|
|
Novice
Joined: 30 May 2007
Posts: 10
|
Oups, i have just on machine!
Is there an workaround solution?
can i create two users wmb (one for each broker) and i put my jar in the classpath |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jun 13, 2007 7:46 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
This is at least the third time this pretty bad idea has come up, and been discussed.
Broker is not a general purpose Java application server. It should not be used to host general purpose Java applications, that need to be shoe-horned into the broker environment.
If I was convinced that there were very specific and good business reasons for doing this, and that it really was necessary to do this inside the broker runtime...
I would probably build a custom Java plugin that would interface with the application that was piled into such very large jar files that I couldn't deploy them. Then I would package this custom java plugin in a PAR file, so that it would have it's own class loader. Then I would create separate LIL directories on each broker, and put the different versions of the PAR file in those directories.
This would be regardless of whether I was running more than one broker on the same machine or not.
You, on the other hand, probably want to go back and revisit the other times that this has been discussed, and review the mistakes and problems that other people made. And reconsider doing this at all.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mlafleur |
| Posted: Wed Jun 13, 2007 8:55 am Post subject: |
|
|
Acolyte
Joined: 19 Feb 2004
Posts: 73
|
| You can change the workpath for the brokers so each has its own shared-classes directory. |
|
| Back to top |
|
|
| fmottais |
| Posted: Thu Jun 14, 2007 1:00 am Post subject: |
|
|
Novice
Joined: 30 May 2007
Posts: 10
|
i hava make an mqsiservice of my broker, and i see the variable working path.
qsiservice BKHOM01
BIPv600 fr FR
ucnv Console CCSID 819 dft ucnv CCSID 819
ICUW ISO-8859-1 ICUA ISO-8859-1
Install Path = /opt/IBM/mqsi/6.0
Working Path = /var/mqsi
Component UUID = 46f66113-0e01-0000-0080-dc65e75dfabb
process id = 696490
broker db name = DBHOM01
broker db userId = db2inst1
broker db password =
queue manager = QMBKHOM01
pubsub migration = no
fastpath Queue Manager = no
configuration timeout = 300
configuration delay timeout = 60
statistics major interval = 60
ComponentType = Broker
How can i change the variable working path ?
thanks |
|
| Back to top |
|
|
|
|
