Adapter Up No Calls Are Working

Issue Statement

Everything looks good but none of the adapter calls seem to work.

What You Can Do

In some cases healthcheck has been set to “none” by default. If that is the case, enable healthcheck and then make sure the healthcheck call works. If not, please review the Adapter Status is Red. If the healthcheck call is working, then connectivity and authentication should not be the issue.

Here are some things that you can do to try to resolve the issue:

• Recheck the base_path and version
  • It is possible the healthcheck has a different path set up than the rest of the calls, or local changes were made to get it working. It may be necessary to make changes so that all calls are set up similarly.
• Put the adapter into debug level logging. This is critical to determine what the adapter is doing and be able to compare it to what it is supposed to do.
  • See article on Why Debug Logs Are Important.
  • It might be easier to run integration testing from the adapter with debug logs turned on to test the healthcheck. You need to set up the integration test to just run the healthcheck and to for proper connectivity to the actual system in the sampleProperties.json. Then you will need to set the log level in the package.jsonto see what is happening.
• Run one of the commands in Postman or Curl to provide a comparison on what works.
• You may need to make changes to the configuration for the call you are trying to make, namely:
  • Changes to IAP Service Instance Configuration for the adapter. If you change these values make sure you do not break getToken or healthcheck.
  • Changes to the healthcheck action defined in the Endpoint Configuration .system entity (/adapter-home-dir/entities/specific-entity). The action.json includes things like path, method, data types, schemas, etc.

If you are unable to determine the issue by looking at the log, follow the Support process to create a ticket with the log information and the Itential Adapters Team will be happy to assist.