This article describes how to set up the Ping function in Protocol Gateway.
The Ping service (monitoring service) is used for system health checks and can be used by load balancers to detect issues in nodes. A Ping call engages all internal components in the CA system, including HSMs.
Prerequisites
| Expand |
|---|
|
The following prerequisites apply: - Protocol Gateway must be installed.
|
...
| Expand |
|---|
| title | Create certificate procedure for Ping |
|---|
|
- Create a certificate procedure for Ping, see Create certificate procedure in Certificate Manager.
- Set Procedure name to Ping Certificate Procedure.
- In Issuing CA, select Device Issuing CA.
- In Certificate format, select Ping.
|
| Expand |
|---|
| title | Create token procedure for Ping |
|---|
|
- Create a token procedure for Ping, see Create token procedure in Certificate Manager.
- Set Procedure name to Ping Procedure.
- In Certificate procedures, select the certificate procedure you just created, that is Ping Certificate Procedure.
- In Type, select pkcs10.
|
| Expand |
|---|
|
To set the properties for Ping: - Open \Nexus\cm-gateway\conf\Ping.properties for editing.
- Modify the following properties:
- Enable Ping by setting
start to true. Set default.tokenprocedure to Ping Procedure. - By default, the Ping service only checks the status of Protocol Gateway. It it shall also check the status of Certificate Factory (CF), then set
default.pingCF to true.
| Code Block |
|---|
| title | Example: Ping.properties |
|---|
| start = true
default.tokenprocedure = Ping Procedure |
|
| Expand |
|---|
|
- Restart the Tomcat service.
|
| Expand |
|---|
|
To verify Ping: Open a browser and go to: | Code Block |
|---|
| localhost:8080/pgwy/ping |
- Verify that the page shows
online.
|
Related information
