Changing Diagnostics Portal settings


You can change the BMC Application Diagnostics Portal settings in the portal.properties file located in the following directories:

  • Windows
    <InstallationDirectory>\portal\properties
  • Linux
    <InstallationDirectory>/portal/properties

Note

After making changes directly to the the portal.properties file, restart the Portal service.

This topic presents the following procedures:

To access through a load balancing or reverse proxy server

By default, the Diagnostics Portal automatically and randomly assigns a Diagnostics Collector to a Diagnostics Agent. Load balancing servers control which Diagnostics Collector is assigned to a particular Diagnostics Agent, while a reverse proxy server adds a layer of security for the Diagnostics Server.

You must configure the load balancing or reverse proxy server to forward requests to the assigned Collectors.

Perform the following procedure to change the host name of the Diagnostics Portal to that of the load balancing server or revers 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 BMC Application Diagnostics Portal HTTP listening port. The default port is 8100.

    tomcat.http.listening.port=8100
  2. Set the BMC Application Diagnostics Portal HTTPS listening port. The default port is 8143.

    tomcat.https.listening.port=8143
  3. Restart the Portal service.

To set security properties

  1. Set the security level of http connection:

    connection.security.level=not_secured

    The following options are valid:

    • not_secured
    • encrypted_authenticated
  2. Restart the Portal service.

To modify database settings

  1. Set the database location:

    database.url=jdbc:mysql://localhost:3306/adops_portal
  2. database.password.enc=ABCD9876
  3. Restart the 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 BMC Application Diagnostics 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 Portal service.

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*