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

wm.server.ws:wsHTTP service failure

  • 1.  wm.server.ws:wsHTTP service failure

    Posted 09/29/16 10:28 AM

    Getting bewlo error when trying to run wm.server.ws:wsHTTP service

    Could not run ‘wsHTTP’
    com.wm.app.b2b.server.ServiceException: [ISS.0088.9433] Access denied to Handler Service in the Handler Chain

    com.wm.app.b2b.server.ServiceException: [ISS.0088.9433] Access denied to Handler Service in the Handler Chain
    at wm.server.ws.wsHTTP(ws.java:4243)
    at sun.reflect.GeneratedMethodAccessor737.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:406)
    at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:649)
    at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:39)
    at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:49)
    at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:243)
    at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)
    at com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:171)
    at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:303)
    at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:34)
    at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:377)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:548)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:385)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:238)
    at com.wm.app.b2b.server.comm.DefaultServerRequestHandler.handleMessage(DefaultServerRequestHandler.java:119)
    at com.wm.app.b2b.server.HTTPMessageHandler.process(HTTPMessageHandler.java:156)
    at com.wm.app.b2b.server.HTTPDispatch.handleRequest(HTTPDispatch.java:179)
    at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:387)
    at com.wm.util.pool.PooledThread.run(PooledThread.java:127)
    at java.lang.Thread.run(Thread.java:745)


    #Integration-Server-and-ESB
    #webMethods
    #B2B-Integration


  • 2.  RE: wm.server.ws:wsHTTP service failure

    Posted 09/30/16 04:31 AM

    Can you share in which requirement you are using this service so that can share my thoughts.

    Thanks,


    #B2B-Integration
    #Integration-Server-and-ESB
    #webMethods


  • 3.  RE: wm.server.ws:wsHTTP service failure

    Posted 09/30/16 04:56 AM

    We have to do an POC around generic webservice provider which will act as a getaway and which does not require WSD for consumer to be created in designer.
    Even if end point input/output signature changes, will not have any code changes in webMethods.

    This is my requirement


    #Integration-Server-and-ESB
    #webMethods
    #B2B-Integration


  • 4.  RE: wm.server.ws:wsHTTP service failure

    Posted 09/30/16 05:11 AM

    If wm.server.ws:wsHTTP service is used to hit some system, can you try to make use of pub.client:http ? Can you check is it works for your need ?

    Thanks,


    #B2B-Integration
    #Integration-Server-and-ESB
    #webMethods


  • 5.  RE: wm.server.ws:wsHTTP service failure

    Posted 09/30/16 05:11 AM

    Also, could share wM version along with fix levels.

    Thanks,


    #Integration-Server-and-ESB
    #B2B-Integration
    #webMethods


  • 6.  RE: wm.server.ws:wsHTTP service failure

    Posted 09/30/16 05:15 AM

    Yes this works but this service is deprecated.


    #B2B-Integration
    #Integration-Server-and-ESB
    #webMethods


  • 7.  RE: wm.server.ws:wsHTTP service failure

    Posted 09/30/16 05:20 AM

    Can you share wM version with fix levels ?

    Thanks,


    #Integration-Server-and-ESB
    #webMethods
    #B2B-Integration


  • 8.  RE: wm.server.ws:wsHTTP service failure

    Posted 09/30/16 05:27 AM

    Can you try to make use of client:soapClient service. Update me how it goes.

    Thanks,


    #Integration-Server-and-ESB
    #webMethods
    #B2B-Integration


  • 9.  RE: wm.server.ws:wsHTTP service failure

    Posted 09/30/16 05:46 AM

    WM version 9.10
    Fixes: TNS_9.10_Fix1
    IS_9.10_Core_Fix1


    #webMethods
    #B2B-Integration
    #Integration-Server-and-ESB


  • 10.  RE: wm.server.ws:wsHTTP service failure

    Posted 09/30/16 05:47 AM

    client:soapClient: requires WSD to be created and does not match our requirements because WSD need to be recreated every time we change input/output signature at the provider.


    #webMethods
    #Integration-Server-and-ESB
    #B2B-Integration


  • 11.  RE: wm.server.ws:wsHTTP service failure

    Posted 09/30/16 05:50 AM

    Making sense, let me think how to proceed.

    Thanks,


    #B2B-Integration
    #Integration-Server-and-ESB
    #webMethods


  • 12.  RE: wm.server.ws:wsHTTP service failure

    Posted 09/30/16 06:12 AM

    Not sure alternatives, can you increase logging and see more details for more details.

    Thanks,


    #Integration-Server-and-ESB
    #B2B-Integration
    #webMethods


  • 13.  RE: wm.server.ws:wsHTTP service failure

    Posted 10/01/16 01:15 AM

    Very interesting idea, but hard to implement. Even you could handle the dynamic service inputs/outputs, how would you handle the WS policy? SOAP-based WS is too heavy to meet your flexible requirements, how about using RESTful WS?


    #Integration-Server-and-ESB
    #webMethods
    #B2B-Integration