ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » fmcojagt.jar version?

Post new topic  Reply to topic
 fmcojagt.jar version? « View previous topic :: View next topic » 
Author Message
MaheshPN
PostPosted: Wed Feb 09, 2005 11:55 am    Post subject: fmcojagt.jar version? Reply with quote

Master

Joined: 21 May 2003
Posts: 245
Location: Charlotte, NC

Hi Guys,
Our developers bought to my notice that, the fmcojagt.jar file have never changed since 3.4 SP4. Though IBM recommends to use/replace the old jar file with new one that comes with the every fixpack, for ex. /usr/lpp/fmc/bin/java3406 for fp6, the dates and size of the jar files under 3404 and 3406 are exactly same.
Does this means, we don't need to change or replace the jar file in the application and repackage it? or oldjar will pick up new updates automatically?

Let me know your thoughts.

thanks,
-Mahesh
Back to top
View user's profile Send private message
vennela
PostPosted: Wed Feb 09, 2005 2:06 pm    Post subject: Reply with quote

Jedi Knight

Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India

Quote:
Does this means, we don't need to change or replace the jar file in the application and repackage it?

I think so.
What I would do is download SP4 and SP6 again and verify the file sizes with what are existing on the box. After that if the size and date are same then you don't have to worry about repackaging.

Quote:
or oldjar will pick up new updates automatically?

It should not.

I don't have a 3.4 AIX box to verify.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
Ratan
PostPosted: Wed Feb 09, 2005 4:27 pm    Post subject: Reply with quote

Grand Master

Joined: 18 Jul 2002
Posts: 1245

Check the readme for SP4 and SP6 to see if there are any fixes for webclient that are in SP6 and not in SP4. If there are no changes then you probably need not worry about it.
_________________
-Ratan
Back to top
View user's profile Send private message Send e-mail
MaheshPN
PostPosted: Fri Feb 11, 2005 12:19 pm    Post subject: Reply with quote

Master

Joined: 21 May 2003
Posts: 245
Location: Charlotte, NC

Hi guys,
Thanks for the reply. The size and date of the fmcojagt.jar file on both the folders are exactly similar in AIX and Solaris.
I read the readme of fp6 and I don't see anything special other than deleting the old and creating a new webclient configuration.
But for windows, the readme says..
"1.1.5 No more automatic changes to the CLASSPATH environment variable

Before service pack 2, the installation of a service pack updated the
CLASSPATH variable to contain the latest version of the MQ Workflow
JAR file. Starting with service pack 2, you must update the CLASSPATH
manually to switch to the latest version. This is to prevent breaking
existing Java client configurations.

The latest JAR files can be found in
<workflow installation directory>\bin\java340<x>
where <x> is the number of the service pack.
"

I assumed that it is true for all environment. Now, I am not sure, does it means the changes has to be made only for windows and not for others?.
I have expressed my concern with IBM. I should hear back from them soon.

thanks,
-Mahesh
Back to top
View user's profile Send private message
hos
PostPosted: Mon Feb 14, 2005 7:31 am    Post subject: Reply with quote

Chevalier

Joined: 03 Feb 2002
Posts: 470

Mahesh,

1. The CLASSPATH was never updated on UNIX systems. So the statement in the readme is correct: Windows behaves now the same as UNIX. You have to update manually.
2. The need for updates results from the JNDI Java Agent (deprecated now). If you only use LOC locator you can safely use a former version of fmcojagt.jar if nothing has changed. fmcojagt.jar is the Java API and not the Web client (fmcohcli.jar) and it changes rarely.
3. For MQWF 3.5 users I recommend to use the native Java API (fmcjapi.jar) instead. It relieves you from keeping track of SP versions in separate directories and from setting/updating the CLASSPATH in WAS.
Back to top
View user's profile Send private message
MaheshPN
PostPosted: Mon Feb 14, 2005 8:15 am    Post subject: Reply with quote

Master

Joined: 21 May 2003
Posts: 245
Location: Charlotte, NC

Thanks Hos, Appreciated!!!

-Mahesh
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » fmcojagt.jar version?
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.