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

Invoking Java Service from Adapter Service returns supplied service doesn't exists

  • 1.  Invoking Java Service from Adapter Service returns supplied service doesn't exists

    Posted Mon October 05, 2020 08:48 AM

    Hi All,

    The requirement is to insert the data from Java Service to Employee Table. I tried below steps but getting error that the supplied service doesn’t exists. Could someone help me to find out the issue?
    To invoke Java Service:

    1. Created employeeService as Java Service
    2. Invoked Java Service (employeeService) from Adapter Service

    Thanks


    #Flow-and-Java-services
    #webMethods-io-Integration
    #Adapters-and-E-Standards
    #webMethods
    #Integration-Server-and-ESB


  • 2.  RE: Invoking Java Service from Adapter Service returns supplied service doesn't exists

    Posted Mon October 05, 2020 09:08 AM

    Hi,

    service name in the adapter template should be FirstService.services:employeeService
    Alternatively you can copy the service namespace using ctrl+c on the java service and paste it in the adapter template.

    Regards,
    Mansooor


    #webMethods-io-Integration
    #Adapters-and-E-Standards
    #Flow-and-Java-services
    #Integration-Server-and-ESB
    #webMethods


  • 3.  RE: Invoking Java Service from Adapter Service returns supplied service doesn't exists

    Posted Mon October 05, 2020 09:29 AM

    (post withdrawn by author, will be automatically deleted in 24 hours unless flagged)


    #Flow-and-Java-services
    #Integration-Server-and-ESB
    #webMethods-io-Integration
    #Adapters-and-E-Standards
    #webMethods


  • 4.  RE: Invoking Java Service from Adapter Service returns supplied service doesn't exists

    Posted Mon October 05, 2020 12:00 PM

    Hi Harleen,
    Yes the invoking service namespace (fully qualified path) should be -
    FirstService.services:employeeService

    Please try it out and see if it helps!

    HTH,
    RMG


    #Adapters-and-E-Standards
    #Integration-Server-and-ESB
    #webMethods
    #webMethods-io-Integration
    #Flow-and-Java-services