WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

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.

 View Only
  • 1.  Loooking for websphere.jar

    Posted 07/25/11 01:31 AM

    I have been assigned a job to compile an old Websphere(WAS4) project, so we can find out which parts of it need to be changed for the project upgrating( to WAS7).


    But when I trying to fix the jar errors, wesphere.jar is missing!! And WAS7 installation path never hava this jar anymore, searching google failed.


    please anybody can help with this, providing an WAS4 version webspere.jar???


    TKX in advance!



  • 2.  Loooking for websphere.jar

    Posted 07/27/11 04:25 PM

    You are doing it the hard way.  Download and install the free IBM toolkit to migrate your application. you can find it here:


    www.ibm.com/developerworks/websphere/dow...


    If you still need a jar, In WebSphere v7, under WAS_HOME\dev  there is a jar called was_public.jar which contains the public APIs for WebSphere V7.  you can use this jar to check for IBM removed APIs.  So, if your app uses removed APIs, they wont be here in this jar file, and you will need to update the code.


    But i do recommend that you download and install the free toolkit (its an eclipse/RAD) plugin.  There are other things you should look at when migrating an application.  removed APIs are just one item.


    I hope this helps!



  • 3.  Loooking for websphere.jar

    Posted 07/28/11 07:42 AM

    yeah, we surely going to change the code.


    I was on the step-in section of the whole migration project, and just want to find which parts of the source code have changed by compile it and find some complains. Maybe will use the migration toolkit when actually conducting the migration.


    Anyway, Thanks for your  help. 


     



  • 4.  Loooking for websphere.jar

    Posted 08/07/11 03:24 AM

    Sounds good and good luck...
    but remember that there are other things you should look at in addition to the removed APIs.  For example, JRE changes.  There were several JRE changes that went into effect in JRE 5. Your code might require updates there as well.  You wont find these changes in the websphere_api.jar file.  Other changes are things like behavoir changes, where the API stays the same, but there is small behavior difference.  example: the #{ becoming a reserved keyword in JSPs ... etc


    The Toolkit will catch all these for you and inform you about them.  Then you can evaluate each result and update the code as necessary.  In many cases, the kit can also make the change itself when you click  'Quick Fix".


    Good Luck.



  • 5.  Loooking for websphere.jar

    Posted 08/31/11 09:13 AM
    [quote author=88588591 post=504235989]

    Sounds good and good luck...
    but remember that there are other things you should look at in addition to the removed APIs.  For example, JRE changes.  There were several JRE changes that went into effect in JRE 5. Your code might require updates there as well.  You wont find these changes in the websphere_api.jar file.  Other changes are things like behavoir changes, where the API stays the same, but there is small behavior difference.  example: the #{ becoming a reserved keyword in JSPs ... etc


    The Toolkit will catch all these for you and inform you about them.  Then you can evaluate each result and update the code as necessary.  In many cases, the kit can also make the change itself when you click  'Quick Fix".


    Good Luck.

    [/quote]
    Further into the project, now I truelly understand what your reminding really means...

    The project is not that simple we assume at all...Even DB2CM & MQ Workflow related are not under change or not consideration...

    Anyway, we're walking through it.

    Tks anyway.