Page Comparison

It may happen that the production environment may go down due to some disaster. In that case, you need to monitor the following applications to detect a failure in the production environment: 

You need to monitor the following applications to detect a failure in the production environment, in case of disaster. 

Adeptia Connect UI Health Check

To set up the health checkup, you need to configure the Load Balancer for all nodes to process the request. To do so, configure your Load Balancer Health Checkup and type the URL in the below format: 

<protocol_name>://<ip_address>:<port_number>/index.html

where,

        <protocol_name> is the name of the protocol you are using. It could be HTTP or HTTPS.

        <ip_address> is the IP address of Tomcat.

        <port_number> is the port number hosting Tomcat. By default, it is 8080 for HTTP and 8443 for HTTPS.

For example, https://192.168.1.14:8443/index.html

The configuration settings of Load Balancer may vary depending upon the Load Balancer you are using.

Following are the steps to configure Load Balancer on Amazon Web Services:

1. Login to Amazon Web Services.
2. Under Compute group, click EC2.
   
   Image Added
   
   
3. Under Resources, click Load Balancers.
4. Select the load balancer to configure the health check.
5. Under Health Check tab, click Edit Health Check.

6. Type /index.html in the Ping Path text box. 

   Image Added

Adeptia Suite UI Health Check

Once you have configured WebRunner for all nodes, you need to configure Load Balancer for all nodes to process the request. To do so, configure your Load Balancer Health Checkup and type the URL in the below format:

<protocol_name>://<ip_address>:<port_number>/adeptia/healthcheck/kernel

where,

          <protocol_name> is the name of the protocol you are using. It could be HTTP or HTTPS.

          <ip_address> is the IP address of the WebRunner.

          <port_number> is the port number at which WebRunner is running. By default, it is 8080 for HTTP and 8443 for HTTPS.

For example, https://192.168.1.1:8443/adeptia/healthcheck/kernel

The configuration settings of Load Balancer may vary depending upon the Load Balancer you are using.

Following are the steps to configure Load Balancer on Amazon Web Services:

1. Login to Amazon Web Services.
2. Under Compute group, click EC2.
   
   Image Added
   
   
3. Under Resources, click Load Balancers.
4. Select the load balancer to configure the health check.
5. Under Health Check tab, click Edit Health Check.

6. Type /adeptia/healthcheck/kernel in the Ping Path text box.

   Image Added

External and Internal

...

Load Balancer Status

Monitor the running status of the internal and external load balancer

...

.

Shared

...

• Storage availability
• Read/write permissions

• Database
  • Database connectivity
  • Read/write permissions

...

Storage

• Ensure that there is sufficient storage available on the shared drive.
• Shared drive is performing read/write operations.

Database

• Check the database connection with Adeptia Suite and Adeptia Connect.
• Database is performing read/write operations.

System Health Status

• CPU usage
• RAM RAM
• Hard disk failure
• Network conectivityconnectivity