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
Expand all | Collapse all

connecting to IS as external client from within IS java service

  • 1.  connecting to IS as external client from within IS java service

    Posted 11/16/15 12:56 PM

    hi all,

    we are using wm9.6 (without any fixes).

    from within java thread (which is not running in the context of IS), i would like to invoke a service on IS.

    i’m failing to connect to the IS.

    my program
    new context()
    context.connect (server, username, passwd)

    this connect fails with two exceptions

    jvm 1 | Cannot connect to server “localhost:5555”
    jvm 1 | com.wm.net.NetException: [ISC.0064.9324] Server Error: 502 internal e
    rror - server connection terminated
    jvm 1 | at com.wm.app.b2b.client.Context.invoke(Context.java:1038)
    jvm 1 | at com.wm.app.b2b.client.Context.invoke(Context.java:851)
    jvm 1 | at com.wm.app.b2b.client.Context.connect(Context.java:570)
    jvm 1 | at com.wm.app.b2b.client.Context.connect(Context.java:521)
    jvm 1 | at CustomerUpdates.MsgHandling$1.handleCUMessage(MsgHandling.jav
    a:447)
    jvm 1 | at CustomerUpdates.MsgHandling$1.handleDelivery(MsgHandling.java
    :386)
    jvm 1 | at com.rabbitmq.client.impl.ConsumerDispatcher$5.run(ConsumerDis
    patcher.java:144)
    jvm 1 | at com.rabbitmq.client.impl.ConsumerWorkService$WorkPoolRunnable
    .run(ConsumerWorkService.java:99)
    jvm 1 | at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolE
    xecutor.java:1145)
    jvm 1 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPool
    Executor.java:615)
    jvm 1 | at java.lang.Thread.run(Thread.java:744)
    jvm 1 | Caused by: com.wm.net.NetException: [ISC.0064.9324] Server Error: 502
    internal error - server connection terminated
    jvm 1 | at com.wm.net.NetURLConnection._getInputStream(NetURLConnection.
    java:700)
    jvm 1 | at com.wm.net.NetURLConnection.getInputStream(NetURLConnection.j
    ava:333)
    jvm 1 | at com.wm.app.b2b.client.Context.invoke(Context.java:943)
    jvm 1 | … 10 more
    jvm 1 | com.wm.app.b2b.client.ServiceException: [ISC.0036.9101] Not connected
    to server
    jvm 1 | at com.wm.app.b2b.client.BaseContext.checkConnection(BaseContext
    .java:342)
    jvm 1 | at com.wm.app.b2b.client.Context.invoke(Context.java:862)
    jvm 1 | at com.wm.app.b2b.client.Context.invoke(Context.java:387)
    jvm 1 | at CustomerUpdates.MsgHandling$1.handleCUMessage(MsgHandling.jav
    a:463)
    jvm 1 | at CustomerUpdates.MsgHandling$1.handleDelivery(MsgHandling.java
    :386)
    jvm 1 | at com.rabbitmq.client.impl.ConsumerDispatcher$5.run(ConsumerDis
    patcher.java:144)
    jvm 1 | at com.rabbitmq.client.impl.ConsumerWorkService$WorkPoolRunnable
    .run(ConsumerWorkService.java:99)
    jvm 1 | at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolE
    xecutor.java:1145)
    jvm 1 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPool
    Executor.java:615)

    any help is appreciated

    thanks and regards
    ajay kumar kasam


    #webMethods
    #Flow-and-Java-services
    #Integration-Server-and-ESB


  • 2.  RE: connecting to IS as external client from within IS java service

    Posted 11/16/15 03:00 PM

    jvm 1 | com.wm.app.b2b.client.ServiceException: [ISC.0036.9107] Transport err
    or encountered
    jvm 1 | at com.wm.app.b2b.client.Context.connect(Context.java:573)
    jvm 1 | at com.wm.app.b2b.client.Context.connect(Context.java:521)
    jvm 1 | at MsgHandling$1.handleOUMessage(MsgHandling.java:301)
    jvm 1 | at MsgHandling$1.handleDelivery(MsgHandling.java:253)
    jvm 1 | at com.rabbitmq.client.impl.ConsumerDispatcher$5.run(ConsumerDis
    patcher.java:144)
    jvm 1 | at com.rabbitmq.client.impl.ConsumerWorkService$WorkPoolRunnable
    .run(ConsumerWorkService.java:99)
    jvm 1 | at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolE
    xecutor.java:1145)
    jvm 1 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPool
    Executor.java:615)
    jvm 1 | at java.lang.Thread.run(Thread.java:744)


    #Flow-and-Java-services
    #Integration-Server-and-ESB
    #webMethods


  • 3.  RE: connecting to IS as external client from within IS java service

    Posted 11/17/15 05:56 AM

    misconfiguration from my side. issue resolved


    #Flow-and-Java-services
    #webMethods
    #Integration-Server-and-ESB


  • 4.  RE: connecting to IS as external client from within IS java service

    Posted 07/14/17 11:38 AM

    Hi All,

    Could anyone please help me with this error, faced while deploying the Model build:

    com.wm.deployer.common.DeployerException: com.wm.deployer.common.DeployerException: [ISC.0036.9101] Not connected to server

    Version : 8.2.

    Regards
    Priya


    #Flow-and-Java-services
    #Integration-Server-and-ESB
    #webMethods


  • 5.  RE: connecting to IS as external client from within IS java service

    Posted 07/14/17 11:39 AM

    I have checked with the server for which this error is encountered. The server is up and test connection is successful.

    Regards
    Priya


    #webMethods
    #Integration-Server-and-ESB
    #Flow-and-Java-services


  • 6.  RE: connecting to IS as external client from within IS java service

    Posted 07/17/17 08:04 AM

    Hi Priya,

    please check that the remote server definition on the target is pointing to itself and is working correctly.
    Additionally check that the WmDesigner has a logicial server configured to point to this (local) remote server entry.

    Deployer uses this informations indirectly for BPM deployments by using the logical server alias on the target server to resolve the conncections.

    Regards,
    Holger


    #Integration-Server-and-ESB
    #webMethods
    #Flow-and-Java-services


  • 7.  RE: connecting to IS as external client from within IS java service

    Posted 07/18/17 04:43 PM

    Thank you Holger. That worked :slight_smile:

    Thanks a lot.

    Regards
    Priya


    #Integration-Server-and-ESB
    #Flow-and-Java-services
    #webMethods


  • 8.  RE: connecting to IS as external client from within IS java service

    Posted 07/21/17 04:41 PM

    Hi Holger,

    Many thanks for responding and helping me on my previous query.

    I got another hurdle where when deploying Model Build, while simulating I am getting ‘No Deployment History’.

    Could you please provide some idea in this as when this situation is encountered.

    Regards
    Priya


    #Flow-and-Java-services
    #Integration-Server-and-ESB
    #webMethods


  • 9.  RE: connecting to IS as external client from within IS java service

    Posted 07/24/17 06:09 AM

    Hi Priya,

    is this before you simulate of after you simulate the candidate?

    A fresh new candidate does not have a deployment history, after the simulation there should be a simulation report listed.
    If not this is considered a bug and needs to be investigated.

    Regards,
    Holger


    #Integration-Server-and-ESB
    #Flow-and-Java-services
    #webMethods


  • 10.  RE: connecting to IS as external client from within IS java service

    Posted 07/24/17 05:48 PM

    Hi Holger,

    It was a fresh deployment only. But after clicking on Simulation, no report was getting generated. It was a server issue. I were able to deploy the build successfully.

    Anways, as always thank you so much for your response.

    Whenever I get stuck at any point I feel this forum to be the best place where I can expect to get solution to my queries.

    Its been 3 months for me in webMethods and really thankful to all the help and guidance I have been reciving in this forum. :slight_smile:

    Having said that, I am right now stuck in testing phase where after deployment of the BPO, I need to create one instance in MWS of that BPO(be it completed/failed) does not matter.

    But I am not able to do so. I am entering data in interface and debugging the service, even thoguh it is successful in Interface, nothing is gtting logged on in implementation/MWS.

    Could you please help me with this. I ahve around 20 BPO’s to perform testing :frowning:

    Regards
    Priya


    #Flow-and-Java-services
    #Integration-Server-and-ESB
    #webMethods


  • 11.  RE: connecting to IS as external client from within IS java service

    Posted 07/25/17 09:07 AM

    Hi Priya,

    please check if the BPOs are enabled for execution and if the logging settings of the BPOs are correct.

    Regards,
    Holger


    #webMethods
    #Integration-Server-and-ESB
    #Flow-and-Java-services


  • 12.  RE: connecting to IS as external client from within IS java service

    Posted 07/25/17 10:51 AM

    Hi Holger,

    I have checked for the following:

    BPO’s - enabled
    log file path - correct(in log4j properties file)
    Broker - connected(in IS page)
    extended settings - correct(in IS page wsel etc. files)
    webservice - configured (in IS page)
    remote servers - connected and configured (in IS page)
    PRT - present and enabled (in IS page)
    jdbc pools - connected(in IS page)

    Please let me know, where could be the problem. When the request is getting triggered successfully in interface server, why it is not reaching implementation server and in MWS process instance is not getting created.

    Is there any possibility of issue lying with the broker.

    Please let me know for broker settings what are all the things I need to check in the server, IS , MWS.

    Providing success log sample from Interface server:

    2017:07:24 20:30:25:365,INFO ,deployer,INFO,null,wm.server.flow:stepFlow,START - WSEL TrackingId: %soapHeaders/HDRDOC1:trackingHeader[0]/requestId% - Request ID: JT - MSISDN: 447528055123 - UserId: pay_dd - Use Case: SubscribeEvent - Channel Code: JT - Enduser Code: JT - ddBundleId: JT_DD_005 - PaymentsMessageType: DD_PAYMENT_SUCCESSFUL - BacsReference: 129597742-2017179
    2017:07:24 20:31:18:185,INFO ,deployer,INFO,null,wm.server.flow:stepFlow,START - WSEL Request ID: %soapHeaders/HDRDOC1:trackingHeader[0]/requestId% - Request ID: JT - BusinessProcessState Id: NOT_AVAILABLE - BusinessProcessState UpdateStatus: SUBMITTED - ChannelCode: JT EnduserCode: JT - UsecaseName: SubscribeEvent Key: 447528055123
    2017:07:24 20:32:41:240,INFO ,deployer,INFO,null,wm.server.flow:stepFlow,FINISH - WSEL Request ID: %soapHeaders/HDRDOC1:trackingHeader[0]/requestId% - Request ID: JT - BusinessProcessState Id: NOT_AVAILABLE - BusinessProcessState UpdateStatus: SUBMITTED - ChannelCode: JT EnduserCode: JT - UsecaseName: SubscribeEvent Key: 447528055123
    2017:07:24 20:32:56:237,INFO ,deployer,INFO,null,wm.server.flow:stepFlow,FINISH - WSEL TrackingId: %soapHeaders/HDRDOC1:trackingHeader[0]/requestId% - Request ID: JT - MSISDN: 447528055123 - UserId: pay_dd - Use Case: SubscribeEvent - Channel Code: JT - Enduser Code: JT - ddBundleId: JT_DD_005 - PaymentsMessageType: DD_PAYMENT_SUCCESSFUL - BacsReference: 129597742-2017179

    Regards
    Priya


    #Integration-Server-and-ESB
    #webMethods
    #Flow-and-Java-services