Topic
  • 4 replies
  • Latest Post - ‏2007-05-03T07:41:23Z by SystemAdmin
SystemAdmin
SystemAdmin
2340 Posts

Pinned topic Workflow API Error in WAS 6.0

‏2007-05-01T18:27:56Z |
Hi,
Our application(which uses a Workflow API) was working fine on WAS 5.0 server.But when i migrated it to WAS 6.0,the application is working fine,except that it cannot connect to Workflow API and is throwing out exception in Workflow.The error message that i am getting in the console when i try to login with a specific user id is as below:

MESSAGE UserId X017264 com.aetna.health.echs.servlet.ControllerServlet.handleRequest(), com/ibm/workflow/catalog/Properties
Exception java.lang.NoClassDefFoundError: com/ibm/workflow/catalog/Properties

When i tried to debug my application,the error message which i am getting is:

cause:UnsatisfiedLinkError (id=1535876)
detailMessage:"fmcojprf(Not found in java.library.path)"

Any help on this would be appreciated !!

Thanks
Updated on 2007-05-03T07:41:23Z at 2007-05-03T07:41:23Z by SystemAdmin
  • jmac_EmeriCon
    jmac_EmeriCon
    26 Posts

    Re: Workflow API Error in WAS 6.0

    ‏2007-05-02T02:02:56Z  
    Looks like a classpath problem to me. Do you have all the necessary workflow jars accessible?

    Regards

    John McDonald
    EmeriCon, LLC
  • SystemAdmin
    SystemAdmin
    2340 Posts

    Re: Workflow API Error in WAS 6.0

    ‏2007-05-02T07:28:56Z  
    Looks like a classpath problem to me. Do you have all the necessary workflow jars accessible?

    Regards

    John McDonald
    EmeriCon, LLC
    I hate it to contradict John, but UnsatisfiedLinkError messages have their
    root
    cause in wrong library path settings :-)

    Depending on the Operating System, make sure the the directory of the MQWF
    JNI libraries
    ( <MQWF install dir>/bin ) is in the

    • LIBPATH (AIX),
    • SHLIB_PATH(HP_UX)
    • LD_LIBRARY_PATH(Solaris)

    of the environment that starts up the Application Server.

    Volker Hoss
    IBM WebSphere Process Server Development
  • jmac_EmeriCon
    jmac_EmeriCon
    26 Posts

    Re: Workflow API Error in WAS 6.0

    ‏2007-05-02T13:22:19Z  
    I hate it to contradict John, but UnsatisfiedLinkError messages have their
    root
    cause in wrong library path settings :-)

    Depending on the Operating System, make sure the the directory of the MQWF
    JNI libraries
    ( <MQWF install dir>/bin ) is in the

    • LIBPATH (AIX),
    • SHLIB_PATH(HP_UX)
    • LD_LIBRARY_PATH(Solaris)

    of the environment that starts up the Application Server.

    Volker Hoss
    IBM WebSphere Process Server Development
    Volker:

    Of course you are right (Contradict any time, ;-) )

    One additional issue is that this is likely zOS, so if there are any additional hints let us know.
    Regards

    John McDonald
    EmeriCon, LLC
  • SystemAdmin
    SystemAdmin
    2340 Posts

    Re: Workflow API Error in WAS 6.0

    ‏2007-05-03T07:41:23Z  
    Volker:

    Of course you are right (Contradict any time, ;-) )

    One additional issue is that this is likely zOS, so if there are any additional hints let us know.
    Regards

    John McDonald
    EmeriCon, LLC
    Hi,

    this is described in detail in the z/OS WebClient documentation (HTML
    file) that comes with the product.
    In the customization chapter you find that you have to set the LIBPATH
    property of your Application Server
    to the proper directory.

    One side note: MQWF 3.5 is out of maintenance and you should upgrade to
    version 3.6.
    There you have the native Java API which, I highly recommend namely for
    z/OS! It is much
    more reliable in situations with resource limitations.

    Volker Hoss
    IBM WebSphere Process Server Development