Changing App Visibility portal settings

This topic presents the following procedures:

• • To access through a load balancing or reverse proxy server
  • To change the port numbers
  • To modify database settings

To access through a load balancing or reverse proxy server

By default, the App Visibility portal automatically and randomly assigns an App Visibility collector to an App Visibility agent. Load balancing servers control which App Visibility collector is assigned to a particular App Visibility agent, while a reverse proxy server adds a layer of security for the App Visibility server.

The collectors.load.balancer.address property value directs the App Visibility agent communication through the load balancing or reverse proxy server and forwards requests to the assigned App Visibility collectors.

Perform the following procedure to change the host name on the App Visibility portal to that of the load balancing server or reverse proxy server:

1. Open the portal.properties file.
2. Change the collectors.load.balancer.address value to the host name or IP address that you want the components to use when connecting to the collectors.
3. Restart the portal service.

To change the port numbers

1. Set the App Visibility portal HTTPS listening port.

   The default port is 8100.

   tomcat.http.listening.port=8100

2. Modify the App Visibility portal supportability port.

   The default port is 8101.

   tomcat.supportablity.port=8101
3. Restart the App Visibility portal service.

To modify database settings

Use this procedure to modify the database location, data retention time, and maximum database size. To change the database password, see Changing-the-App-Visibility-database-password.

1. If you change the location of the database, or if you need to change database port, modify the database location:

   database.url=jdbc:postgresql\://localhost\:8800/avdb?currentSchema\=portal

2. Modify the period to retain data in the database on the App Visibility portal (retention.time).

   The retention time is in days.

   retention.time=35

3. Modify the percentage of used database space at which the system issues an event, and the percentage at which the system closes the event.

   The events indicate that the database growth might require your attention.

   db.cleanup.start.threshold=90
   db.cleanup.stop.threshold=85
4. Restart the App Visibility portal service.