Validate Installation

To validate successful installation of the application - and for validating accessibility of the application throughout - the application exposes a health check endpoint. This is a simple endpoint that can be accessed without authentication, which responds with a simple diagnostic message (that is, HTTP 200 'OK'). Below is an example of how this is done through cURL.

curl -v http://<<hostname>>
*   Trying 10.252.13.175:27052...
* TCP_NODELAY set
* Connected to <<hostname>> (IP) port <<port>> (#0)
> GET /health HTTP/1.1
> Host: hostname:portnumber
> User-Agent: curl/7.65.3
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Date: Wed, 11 Mar 2020 08:34:22 GMT
< Transfer-Encoding: chunked
< Content-Type: text/plain; charset=UTF-8
< X-ORACLE-DMS-ECID: b4dcc298-1fbe-4599-ac09-011d1f33e9cf-00002cd6
< X-ORACLE-DMS-RID: 0
<
* Connection #0 to host <<hostname>> left intact
OK

Another way of validating the installation is by checking if the HTTP API services endpoint can be accessed; URL format is:

http://machine.domain:port/api

The default context-roots like "/api" may have been overridden when a deployment plan was used to deploy the application. Also, the URIs for accessing application end points may only be accessible via a load balancer.