Health Checks

All health checks described in the APIO Core Deployment Guide apply to both the database and the APIO Core application. Additional checks are outlined in this chapter to ensure the proper functioning of the BWGW.

Login Test

From the container's host, run the following curl command to verify authentication with the BroadWorks Application Server:

# curl --insecure -H "Content-Type: application/json" --data '{"username": "<username>", "password": "<password>"}' https://<bwgw>/api/v1/login/
{"ids":{"tenant_id":"UAT_ent1","group_id":"UAT_ent1_g3220"},"profile":{"user_level":8,"broadsoft_type":"Group","username":"<username>","is_first_login":false,"first_name":"Bruce","last_name":"Wayne","emailAddress":"","language":"English","access_type":0,"read_only":false,"language_code":"en","is_expired":false,"is_enterprise":true},"_record_internal_id":"67c43c5b-a824-4e17-a2ed-d1751277ec33-1747043255.10587549209594726562"}

This operation should also generate log entries in the following files:

• /var/log/apio_gtw/apio_gateway_proq.log
• /var/log/apio_gtw/apio_gtw-<instance>-stdout.log
• /var/log/apio_gtw/caddy-stdout.log

You can also test the login API via APIO Core by executing the following curl command. This will trigger the hunting mechanism configured in APIO Core to locate the appropriate gateway and application server:

# curl -v --insecure -H "Content-Type: application/json" --data '{"username": "<username>", "password": "<password>"}' https://<core>/api/v01/auth/login

Alternatively, you can specify the proxy name to directly target a specific gateway.

# curl -v --insecure -H "Content-Type: application/json" --data '{"username": "<username>", "password": "<password>", "proxy": "<proxy-name>"}' https://<core>/api/v01/auth/login