API Enablement

  • 1.  try it out works when it should not

    IBM Champion
    Posted Mon September 14, 2020 03:22 PM
    Ive got the swagger up for stocknanager
    item-d 999999

    clock try it out give shows curl string..


    response body no content
    response code 0
    response header { "error": no response from serer}


    This request should fail, as I did not define a queue manager.   There were no diagnostics or trace entries
    even with

    traceFormat="BASIC"  traceSpecification="*=info:zosConnectServiceMq=all:zosConnectApiRequester=fine"
    ___________________________


    try it from curl and I get

    {"action":"Contact the administrator of the service to resolve the problem.","message":"BAQM0006E: An unexpected JMSException occurred while processing a request for service 'stockQuery'. The exception message was 'MQJCA1011: Failed to allocate a JMS connection.'.","explanation":"An unexpected JMSException occurred while processing a request."}

    and lots of records in the trace.log file


    ___________________________________


    so something is wrong with the try-it

    _____________________________________________________



  • 2.  RE: try it out works when it should not

    Posted Tue September 15, 2020 12:21 PM
    Hi Colin.  It's misleading, but the following response is what Swagger UI displays when a request fails due to a security issue such as an untrusted self-signed cert, invalid cert, or bad username:password.
    response body no content
    response code 0
    response header { "error": no response from serer}
    -Ted

    ------------------------------
    Ted Cipresso
    ------------------------------