Updgrade jvm 1.3.1 to 1.4.2 for IS 4.6

[kaovei]

Following this alert from WM :

‘webMethods has identified an issue that may cause your webMethods
implementation to cease functioning on May 18, 2006. A thorough analysis of
the webMethods software suite has been conducted and you are being notified
as one of our customers who may be subject to this problem. Please log into
webMethods Advantage [url]http://advantage.webmethods.com/critical[/url] for more
information on the issue, effected webMethods components and most
importantly, how you can keep this issue from effecting you.’

We may consider to upgrade the IBM jvm 1.3.1 currently running for IS 4.6 to 1.4.2.
However, reading the installation instruction for IS4.6, I have no clues to predict if IS 4.6 is comptatible with jvm 1.4.2 although it says that it supports jre 1.2.2 and later.

Does someone has experience of running IS 4.6 on IBM jre 1.4.2 to share.

(As we are running on IS 4.6 I am not even sure that we are affected by this issue, but as we are running IBM JVM 1.3.1, I started this thread in case of).

Big thanks in advance.

[ns_wmc]

I am working on the same issue…
Any help?

BTW, should not this be posted under forum –
Managing webMethods Integration Server ?

• NS

[ns_wmc]

Hi All,

I am facing a problem, while looking for this issue.

We have many different environments for webMethods. For some of them, I could not even locate for the ibmjcefw.jar file under lib!

For some instances, I could locate that lib (6.1) and when I looked into that jar and found the manifest file, there is no entry for “ibmjcefw.jar”!!

If anybody has worked on this, Please help in locating the problem.

Thanks,
NS.

[wMusers.Com1 (wMusers.Com)]

Critical Software Update - JCE Certificate Expiration Problem

   [B]Quick Links[/b]

• IBM Alert Notification
• Susceptible webMethods Components
• Prevent the Failure from Occurring
• Contact Customer Care

This is a critical information announcement about an IBM software problem that could cause a failure in your webMethods installation after May 18, 2006. This notice describes the problem in the IBM software, lists the susceptible webMethods components, and explains how to prevent the failure from occurring.
Description of the IBM Software Problem

IBM has recently announced that a security certificate contained in certain versions of their Java Virtual Machine (JVM) will expire on May 18, 2006. This problem only occurs on V1.2 and 1.3 IBM JVMs in which the ibmjcefw.jar is dated prior to 040219 in the manifest file. If you have an ibmjcefw.jar that is dated 040219 or later in V1.2 or 1.3 IBM JVMs, or your JVM is V1.4 or greater, you will be unaffected by the certificate expiration issue.
See the following link on IBM’s Support Website for more information: http://www-1.ibm.com/support/docview.wss?uid=swg21212932
Susceptible webMethods Components

webMethods has thoroughly examined the entire webMethods software suite and has determined that the webMethods components listed below are susceptible to the expired security certificate failure.

• Version 6.1 webMethods Integration Servers that have been configured to run against IBM JVM 1.2 and 1.3 and in which the ibmjcefw.jar is dated prior to 040219 in the manifest file.
  
  Note that Integration Server version 6.1 was the first version to make use of JCE and also the first time that webMethods distributed IBM JVM 1.3.1 containing the expiring certificate. Integration Server version 6.5 ships with JVM version 1.4 which does not contain the expiring certificate; therefore, Integration Server 6.1 is the only version susceptible to the certificate expiration problem.
• Enterprise components listed below that are configured to run against IBM JVM 1.2 and 1.3 in which the ibmjcefw.jar is dated prior to 040219 in the manifest file. Note that webMethods Enterprise components did ship with the IBM JVM 1.3 containing the expiring certificates.
  [LIST]
• Enterprise Adapter Runtime
• Custom adapters created using Enterprise Adapter Runtime
• Enterprise Adapter Manager
• Any of the following webMethods Enterprise Adapters:
  [LIST]
• BroadVision Edition
• Broker Package (AKA Broker Bridge)
• CICS Edition
• Clarify Edition
• CORBA Edition
• Database Edition
• Email Edition
• Enterprise Integrator Logger Adapter
• Enterprise JavaBeans Edition
• File I/O Edition
• Informix Edition
• Integration Logic Agent Edition
• J.D. Edwards OneWorld Edition
• JDBC Edition
• JMS Edition
• Kenan Arbor Edition
• LDAP Edition
  [/LIST]
  [LIST]
• Metasolv Edition
• Microsoft SQL Edition
• MQSeries Edition
• MSMQ Edition
• ODBC Edition
• Oracle Edition
• PeopleSoft Edition
• PeopleSoft PIA Edition 4.6 Plug-in
• PeopleSoft PIA Edition
• Portal Edition
• SAP Edition
• Siebel Edition
• Sybase Edition
• Tuxedo Edition
• Vantive Edition
• XML Edition
  [/LIST]
  
  [/LIST]
  

Prevent the Failure from Occurring

To prevent the expired security certificate failure from occurring for the Enterprise components listed above, take these steps:

• For non-AIX platforms, customers should move to Sun JVM 1.3.1 available from the Sun Website. However, in order to make this version of the Sun JVM compliant with webMethods, you must also install a previously released Sun JCE Patch available from the webMethods Advantage Web site. The switch to the Sun JVM is required because IBM no longer distributes their JVM for non-IBM platforms. Version 1.3.1 of the JVM is required because the webMethods Enterprise components do not support newer versions of the JVM.
• For AIX platforms, customers should move to the IBM JVM 1.4.1 available from IBM http://www-128.ibm.com/developerworks/java/jdk/aix/service.html
• Special note for customers running Enterprise EJB Adapter or Enterprise JMS Adapter versions 4.2 on AIX platforms. Our testing has shown that upgrading to the IBM JVM 1.4.1 does resolve the JCE expiration problem but causes compatibility issues between the Enterprise Adapters and WebSphere Application Server. For these customers, we recommend that you contact IBM directly for assistance or consider migrating to a later version of webMethods EJB and/or JMS solutions that do not exhibit the problem. Additionally, webMethods has contacted IBM to see if they have a separate fix for the WebSphere issue. We will acquire this fix if and when available, test it in our labs and update our customers as we discover additional information.

To prevent the failure from occurring for Integration Server users we recommend moving to the Sun 1.4.2 JVM.

For Windows, Sun and HP users, this version of the JVM ships with Integration Server and should already be installed in the webMethods directory. In order to configure the Integration Server to use the Sun JVM, follow these instructions

1. Navigate to the <webMethods_install_dir>\IntegrationServer\bin directory and open the server.bat (windows) or server.sh (Unix) file in a text editor.
2. Edit the JAVA_DIR parameter and point it to the JRE shipped with webMethods, located in <webMethods_install_dir>\jvm\win142\jre, then save and close the file.

For AIX users, download the appropriate patch from the IBM website for your current version of the JVM.

Finally, though we have performed extensive testing internally, customers are free to configure their systems using a variety of supported JVMs. Therefore, even though we have identified the webMethods components that are susceptible to the problem and the versions in which we explicitly shipped the JVM containing the expiring certificate, there is always a possibility that a customer may have reconfigured their environment to use a version of the IBM JVM that exhibits the problem. Therefore we encourage all customers using IBM JVMs to perform “time shift testing” on their environments by setting the system date time on their servers to May 19, 2006 or later and then restarting and testing their webMethods integrations.

[jeevanrego]

Hi Marks

Thats really very informtive, thanks.

Cheers
Jeevan

[gupta_r.17495]

Hi,

We are getting this error during IS6.1 on windows2000 startup on May18th 11:34PM…So i guess this error related to above mentioned JVM issue???

Both our QA,PROD servers are down at this moment.

java.lang.NoClassDefFoundError: javax/crypto/f
at javax.crypto.Cipher.getInstance(Unknown Source)
at com.entrust.toolkit.security.provider.X917Random1.<
ce)
at com.entrust.toolkit.security.provider.X917Random.<i
e)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:262)
at iaik.security.random.SecRandom.a(Unknown Source)
at iaik.security.random.SecRandom.getDefault(Unknown S
at com.wm.app.b2b.server.StateManager.init(StateManage
at com.wm.app.b2b.server.Server.run(Server.java:248)

Please advice.

TIA,
RMG

[wMusers.Com1 (wMusers.Com)]

Yes, I think it is.

[gupta_r.17495]

Thanks Mark,

All right we solved the problem,here is what we did reference from advantage.

We edited the server.bat and changed this line
SET JAVA_DIR=C:\webMethods6\IntegrationServer\jvm
to
SET JAVA_DIR=C:\webMethods6\jvm\win142

Save it and restart the server.It worked great…

HTH,
RMG

[Greatwhite]

hi, i m running wM 6.1 on windows XP pro sp2…it used to work fine…but yesterday when i started IS, it does not…the error msg is as posted in similar threads…

java.lang.NoClassDefFoundError: javax/crypto/f
at javax.crypto.Cipher.getInstance(Unknown Source)
at com.entrust.toolkit.security.provider.X917Random1.(Unknown Sour
ce)
at com.entrust.toolkit.security.provider.X917Random.(Unknown Sourc
e)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java(Compiled Code))
at iaik.security.random.SecRandom.a(Unknown Source)
at iaik.security.random.SecRandom.getDefault(Unknown Source)
at com.wm.app.b2b.server.StateManager.init(StateManager.java:63)
at com.wm.app.b2b.server.Server.run(Server.java:248)
so…this z what i did…

1. changed system date to one year previous date(05/26/2005) and rebooted the system and started IS without making any changes in my server.bat.
   result:did not work…
   2.i changed the system date back to the original…then edited server.bat
   entry to this
   SET JAVA_DIR=C:\webMethods6\jvm\win142\jre
   alternatively(or)
   SET JAVA_DIR=C:\webMethods6\jvm\win142
   saved the file and started IS 6.1 from Command console…
   Result:this time it partially loads packages and after a while aborts…
   the IS could not start…
   Now what should i do?

A.should i go to SUN website and download JRE 1.4.2 …where do i keep the downloaded file(Path)…
can someone give me detailed steps…installation etc…any class_path settings or Path settings to make along with this…

B.should i download JRE 1.3.X(sun) along with another patch mentioned therein and follow the same procedure as in step A above…

C.i m not downloading from IBM site since i understand they are not supplying patches for NON-IBM OS…anymore.
Correct me if i m wrong…

Any help with this is highly appreciated.

Thanks

[wMusers.Com1 (wMusers.Com)]

Since this server is using XP Pro, I’m guessing that it is a development environment. If so, why not just reinstall the latest version of IS 6.1 from scratch into a new folder and copy over your custom packages.

You did not say what errors were occuring when you attempted to use the webMethods-supplied Sun 1.4.2 JRE. Understanding those messages might lead you in different directions.

Mark

[Greatwhite]

Dear Mark,

Thank you for your immediate tip.Actually, i observed those errors i mentioned when i pointed to java JRE 1.4.2 were instance abort messages when i aborted the running server.bat instance.
what actually happenned is, afer loading packages, the instance never finishes…i mean the IS never starts…
i observer these…
1.previously when it was alright, the server.bat was consuming(MEm usage) around 300MB Ram(ctrl+alt+del).but now after i pointed
java_dir in server.bat to \jvm\win142, the server.bat process
consumes only 170MB Memory…The IS never starts…
and i wait more to see what happens…i find this…
Now the server.bat process is only using close to 30+MB mem and nothing
happens…i m at my wits end…

Any help is greatly appreciated…btw do u think SUN jre 1.3.1 will help?

Thanks again

[wMusers.Com1 (wMusers.Com)]

Crank up the logging verbosity by starting from the command line with server.bat -log none -debug=6. See what errors are shown.

Mark

[Greatwhite]

Dear Mark,

Thanks a lot again.u guided me in the right direction.i just got jitters with this JCE EXPIRY issue for no good reason and pointed to wrong port(IS).
SET JAVA_DIR=\jvm\win142\jre…works fine.
my IS is up now…i m sorry to have wasted ur time for all the wrong reasons…