IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.



#Automation


#Applicationintegration
#webMethods
#Integration
 View Only
  • 1.  Changing the JVM Version

    Posted 07/15/08 10:48 AM

    I have a question regarding JRE versions of the Integration server. Our 7.1 installation runs on Java 1.5. Now we have a thirdparty jar which has been compiled with Java 1.6. So when we try to use this jar, webMethods complains about the different versions. So we downloaded jdk1.6 and copied as “linux160” directory (under /opt/webMethods/jvm). Then we changed the extended settings in integration server accordingly. But this also doesn’t solve the problem. Is there a workaround?

    Thanks,
    Ram


    #Integration-Server-and-ESB
    #webMethods-Archive
    #webMethods


  • 2.  RE: Changing the JVM Version

    Posted 07/15/08 11:31 AM

    Please update your extended setting changes.


    #Integration-Server-and-ESB
    #webMethods-Archive
    #webMethods


  • 3.  RE: Changing the JVM Version

    Posted 07/15/08 12:06 PM

    actually we did the change in extended setting. but it still doesn’t solve the problem.


    #Integration-Server-and-ESB
    #webMethods
    #webMethods-Archive


  • 4.  RE: Changing the JVM Version

    Posted 07/15/08 03:42 PM

    Try updating the server.sh file in IS_Directory/IntegrationServer/bin to update the JVM version of IS.


    #webMethods-Archive
    #webMethods
    #Integration-Server-and-ESB


  • 5.  RE: Changing the JVM Version

    Posted 07/16/08 03:08 PM

    I think, in this case You must force IntegrationServer to run on Java 1.6.
    You may do it by changing $WM_HOME/IntegrationServer/bin/server.sh (bat)

    Here is more:
    [URL]wmusers.com

    Very important ! Using JDK 6 remember to add also in:
    server.sh:

    JAVA6_ISSUE=-Dsun.lang.ClassLoader.allowArraySyntax=true
    ...
    $JAVA_RUN $JAVA6_ISSUE ...

    or server.bat:

    set JAVA6_ISSUE=-Dsun.lang.ClassLoader.allowArraySyntax=true
    ...
    %JAVA_RUN% %JAVA6_ISSUE% ...

    #Integration-Server-and-ESB
    #webMethods
    #webMethods-Archive


  • 6.  RE: Changing the JVM Version

    Posted 10/27/09 10:20 AM

    Hi,

    Has anyone upgraded their IS instances to use JVM 1.6?
    Are there any tools/packages used to test such a JVM upgrade to version 1.6?

    Thanks
    Dev


    #webMethods
    #Integration-Server-and-ESB
    #webMethods-Archive


  • 7.  RE: Changing the JVM Version

    Posted 11/08/09 02:44 AM

    update server.sh and jcode.sh to point the java home directory…


    #webMethods
    #webMethods-Archive
    #Integration-Server-and-ESB


  • 8.  RE: Changing the JVM Version

    Posted 11/08/09 03:58 PM

    I do, but not in production environment (lack of support of JVM 1.6 from SoftwareAG).
    I don’t know about any build-in self-test in IS, but You must somehow test Your integration code anyway - maybe You alone have sufficient test set, to be sure it working.

    Of course, in bin/server.sh / bin\server.bat JAVA_DIR must be set:
    JAVA_DIR=/jre
    or
    JAVA_DIR=

    If You using jcode, bin/jcode.sh / bin\jcode.bat should also be modify in that way.

    There may be a need for additional change - in file: config/server.cnf.
    Two lines should look like this:
    watt.server.compile=/bin/javac -classpath {0} -d {1} {2}
    watt.server.compile.unicode=/bin/javac -encoding Unicode -classpath {0} -d {1} {2}
    This file is editable from from WWW console (WmRoot) also.


    #Integration-Server-and-ESB
    #webMethods
    #webMethods-Archive