Changing App Visibility portal settings

You can change the App Visibility portal settings, such as the host name of computer or port numbers, in the portal.properties file located in the following directories:

• Windows
  installationDirectory\portal\properties

• Linux
  installationDirectory/portal/properties

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 configure SNMP events
  • Related topics

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 of 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 portal.
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

1. If you need to change the database port, replace the port number (8800, by default) with the value you require.

   database.url=jdbc:mysql://localhost:3301/adops_portal
2. Restart the App Visibility portal service.

To configure SNMP events

1. Set the interval in seconds between consecutive runs of the event trapping task (5 minutes by default):

   event.trapping.task.interval.sec=300

2. Set event reporting flags (to specify that the App Visibility portal reports, through SNMP, error violations, duration violations, and stale agents):

   event.trapping.should.collect.error=false
   event.trapping.should.collect.duration=false
   event.trapping.should.collect.agents=false

3. Set the host and port of the SNMP destination:

   event.trapping.snmp.destination.ip=localhost
   event.trapping.snmp.destination.port=162

4. Set the OIDs of the trap and the message when reporting on violations:

   event.trapping.snmp.oid.violation.trap=1.3.6.1.6.3.1.1.4.1.1.1
   event.trapping.snmp.oid.violation.message=1.3.6.1.6.3.1.1.4.1.1.0

5. Set the OIDs of the trap and the message when reporting on stale agents:

   event.trapping.snmp.oid.agents.trap=1.3.6.1.6.3.1.1.4.1.2
   event.trapping.snmp.oid.agents.message=1.3.6.1.6.3.1.1.4.1.2.0
6. Restart the App Visibility portal service.

Related topics

Changing-App-Visibility-collector-settings

Changing-App-Visibility-proxy-settings

Starting-and-stopping-the-App-Visibility-server-services

Changing-security-certificates-in-App-Visibility-components