| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Upgrading a Solaris JAVA MQ Client application |
« View previous topic :: View next topic » |
| Author |
Message
|
| PeterPotkay |
 Posted: Thu Jul 24, 2003 10:32 am Post subject: Upgrading a Solaris JAVA MQ Client application |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
A Solaris server is running a JAVA application that was released to
production a couple of years ago. There is no Queue Manager on this server.
The app client connects to a Windows server that has the queue manager.
Now, they wish to be at the latest level of MQClient for this Solaris
server, 5.3 CSD04. The only app running on this server using MQ is the JAVA
one.
How do I go about this? Are the following five assumptions correct?
1.)When the app was written 2 years ago, they used the jar files found in
MA88. MQClient or MA88 did not need to be installed on the Solaris server,
just MA88 needed to be made available to the application at compile time
wherever they compiled it.
2.)The MQClient for Solaris for 5.3 CSD04 (#MACY
http://www-3.ibm.com/software/integration/support/supportpacs/individual/mac
y.html) does not NEED to be installed on their Solaris server.
3.)I do need to get the application area the latest jar files somehow. So, I
should download and install the MACY support pac to some Solaris server
(maybe even the one in question), and just point them to the jar files
called com.ibm.mq.jar and con.ibm.mqbind.jar, which according to the docs
are found in /opt/mqm/java.
4)They need to recompile their app with the latest MQ JAVA jar files.
5.)By simply recompiling their Java app with the MQ jar files found in
Support Pack #MACY, their app will be running at 5.3 CSD04.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Jul 24, 2003 10:49 am Post subject: Re: Upgrading a Solaris JAVA MQ Client application |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
A lot of your assumptions depend heavily on how the application group is packing up their application into a deployment jar file.
It sounds as if they are including the MQ jar files in their jar as well. While this makes the application look a lot more like a C application, in that everything is all in the same package, it's not necessarily the standard Java deployment methodology. Java jar files are like any other shared library - there are reasons for static linking and reasons for dynamic linking, and problems caused by both as well.
However, if they are packaging the MQ jars into their jar file, then your assumptions are probably correct.
But you'll want to upgrade the Windows server as well. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Jul 24, 2003 11:40 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
The windows server has been upgraded already.
I haven't talked with the app group in depth yet. I wanted to be better informed.
I think what you are saying though is that they are in some fashion referring to the MQ java jar files, and as long as I provide them with the new verions available in support pack MACY, and they rebuild their app to use the new ones, they will be at 5.3 CSD04. There is really nothing for me to do on the Solaris server that will be hosting this java client app. Is this correct?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
