z/OS Connect to DB2 service ending with a 500
A customer is attempting to call a DB2 service (that lives in DB2) from an API created in z/OS Connect. He took the steps use zconbt tool to create the .sar file and two .json files. He has deployed his API and he provided me the info to define in the server.xml. We've defined the API name and location, the service name and service ref, and the id, host, port, and httpmethod, and URI.
Why would he be getting a 500? It doesn't seem like he's reaching the service. Please advise.
Hello @A.Calixto
Please can you check the messages.log file for the z/OS Connect EE server, and also any DB2 log file for messages relating to the 500 error?
The IBM White paper z/OS Connect EE V3 Getting Started Guide (from page 121) shows a working example of using z/OS Connect EE V3 with DB2 which you might find useful.
Kind regards, Alan Hollingshead
IBM z/OS Connect EE Test & Performance
I have looked at your link and coded the auth and username/password parms.
I am now getting the following:
BAQR0429W: API getname encountered an error while processing a request under URL http://*host*/getname/deptno/AAA.
in z/OS Connect EE I see the service is coming up as unknown. Does the service need to be deployed to z/OS Connect? The documentation does not specify this and I was under the impression it would need to be since this is a DB2 service in DB2. I coded the connection parms in order for z/OS Connect to know where to find the service (host, port, etc). I used the zconbt tool to create the .json files used for the API.
Please advise ...
Hello @A.Calixto
The services and APIs need to be deployed to your z/OS Connect EE server. There is a screenshot on page 148 of the whitepaper discussed in my previous post which shows how to deploy an API. Do the same for your service.
In your server.xml make sure you have configured:
<zosconnect_services>
</zosconnect_services>
to ensure that z/OS Connect EE server will load your deployed services from the default location. An equivalent setting for APIs is not required. Your server will automatically load APIs from the default location.
Check your messages.log file during initialization of your server to ensure your services and APIs have been installed successfully.
Kind regards, Alan Hollingshead
IBM z/OS Connect EE