Topic
  • 3 replies
  • Latest Post - ‏2010-05-06T08:22:21Z by SvetlanaD
SvetlanaD
SvetlanaD
3 Posts

Pinned topic inbound adapter doesn work on production process server

‏2010-05-04T09:35:41Z |
Hello to everybody!
I have a problem.
My JDBC inbound adapter works perfect on test process server in WID 6.2.
But it doesn’t on production Process Server 6.2.
Adapter connects to DB2 Universal.

Please help me!
  • Jens.Engelke
    Jens.Engelke
    5 Posts

    Re: inbound adapter doesn work on production process server

    ‏2010-05-04T15:00:11Z  
    Hi,

    if you have an urgent production problem, the best approach is to contact IBM support by opening a PMR.

    I think you need to somehow elaborate on "is not working".
    Is there anything in the log
    - when starting the server
    - when starting the application
    - when triggering an action from which you'd expect an event in WPS.

    With your current description, there are thousands of possible causes
    - connected to the wrong DB
    - not connected to a DB (maybe incorrect user credentials)
    - different JNDI names
    - firewalls

    Regards,
    Jens
  • SystemAdmin
    SystemAdmin
    67 Posts

    Re: inbound adapter doesn work on production process server

    ‏2010-05-04T15:38:01Z  
    Hello,

    I agree with Jens, you need to open a PMR with IBM Support if this issue is impacting a production environment.

    Once you open the pmr, please take a look at the following TechNote. It outlines a problem in the core WAS were a manual JVM property must be enabled before an inbound JCA Adapter will start polling.

    Technote: WebSphere Adapters do not poll for events on WebSphere Process Server 6.1/6.2 with WebSphere Application Server 6.1.0.23/6.1.0.25
    http://www-01.ibm.com/support/docview.wss?uid=swg21394864

    Regards,
    -David
  • SvetlanaD
    SvetlanaD
    3 Posts

    Re: inbound adapter doesn work on production process server

    ‏2010-05-06T08:22:21Z  
    Thanx Jens and David.

    about log files there are no mistakes...

    May be it cause of integrated Process server and Portal? it works on cluster...

    Thanx again