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.

 View Only
  • 1.  Universal Name

    Posted Sun October 26, 2008 04:17 PM

    Dear All,

    I have created a service nesma.receive.paynotifyrq:prnq

    I want give this service to my client as below URL please note without invoke prefix after port,
    [URL=“http://nesmaprod:8976/nesma.receive.paynotifyrq”][COLOR=#22229c]http://nesmaprod:8976/nesma.receive.paynotifyrq[/color][/URL][URL=“http://nesmaprod:8976/nesma.receive.paynotifyrq/pnrq.jsp”]/pnrq.jsp[/URL]

    [/u]

    [URL=“http://nesmaprod:8976/nesma.receive.paynotifyrq”]In order to accomplish this, I did following

    1. Added a port 8976, allow by default
    2. Added Universal namespace to [URL]http://nesmaprod:8976/nesma.receive.paynotifyrq[/URL]
    3. local name to pnrq.jsp

    but I call the service i get following error,
    No such object: nesma.receive.paynotifyrq/pnrq.jsp

    Any suggestions please how to acheive it.

    Regards,
    Faisal


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


  • 2.  RE: Universal Name

    Posted Mon October 27, 2008 01:21 AM

    I don’t think what you are trying to do will work. You can only serve JSPs using the “web” folder in a package. Read about that in the Web Applications Developer’s Guide 7.1.1 available on Advantage.

    Page 36 of that document includes the following:


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


  • 3.  RE: Universal Name

    Posted Mon October 27, 2008 06:31 AM

    Thanks for your reply.

    but requirement is to client call the service without web prefix.

    Regards,
    Faisal


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


  • 4.  RE: Universal Name

    Posted Mon October 27, 2008 08:30 PM

    You can not meet that requirement using only Integration Server’s embedded Tomcat. The requirement appears to be to submit an XML document over HTTP. As the provided of the capability to do so, you control the URL but can only do so within the limits of the tool you are using.

    Now, you could setup a standalone Tomcat server and create a JSP with the required URL that simply redirects traffic to the Integration Server URL, but that seems to be non-value-added and would introduce additional components that are unnecessary and would represent new points of failure.

    My suggestion is to push back on this “requirement” explaining the realities of the underlying tools.

    Mark


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