Configuring the BMC AppSight Repository Server

A BMC AppSight Repository Server is used by both BMC AppSight for Java EE and BMC AppSight for Windows as a storage place for BMC AppSight recordings and as a proxy to send requests to, and gain control of, BMC AppSight servers. Through the BMC AppSight Repository server, BMC End User Experience Management can access detailed Application Diagnostics for slow and failed transactions.

This section presents instructions to configure the BMC AppSight Repository Server. To configure connections to the BMC AppSight components, add BMC AppSight Servers. Black Boxes that are connected to the integrated components are listed under their respective BMC AppSight servers, and the list is updated dynamically. If a server goes offline after you add it, only the server name is listed.

To configure the BMC AppSight Repository Server

1. Access the BMC AppSight Repository server at the following URL:
   AppSightReposServerHost:port/AppSightConsole/Administration/Administration.html
   where
   • AppSightReposServerHost is the computer name or IP address of the repository server
   • port is the port number that is used by the repository server on the computer. The default port is 7092.
2. To add an AppSight Server (Java EE or Windows), in the AppSight Server tab click the Add Server icon in the top left corner of the Repository screen. In the displayed screen, enter the following:
   • Host: The computer name or IP address of the AppSight Server.
   • Port: The port number that is used by the AppSight Server on the computer.

   • HTTPS: Select the checkbox if the AppSight Server supports HTTPS.
     

     Warning

     You can install any number of AppSight Servers, in accordance with your scalability requirements.

     
     

3. Click OK to add the AppSight Server.
   

To remove a BMC AppSight server from the BMC AppSight Repository server

In the AppSight Servers tab, select an AppSight Server from the displayed list and click the Remote Server icon (located in the top left corner of the Repository screen). In the confirmation message, click Yes.

To configure the retention of recordings (optional)

There are two levels of retention:

• In the BMC AppSight Repository the number.of.days.to.keep.problems property in the common.properties file (located in AppSightInstallDirectory\AppSight Repository\Server\properties) determines how many days data will be saved in the repository before being deleted (the default value is 7). When modifying this value, restart the BMC AppSight Repository service.
• In the BMC AppSight Server (only relevant when drilling down into recorded data using AppSight) recorded data is divided into two levels; the first level is displayed before clicking Drill down into BMC AppSight. The second level is displayed in the BMC AppSight Console, which is launched when clicking Drill down into BMC AppSight.
  Data from the both levels is transferred by the BMC AppSight Windows Server to the BMC AppSight Repository, so retention is controlled by the Repository, as described above. The difference between the two levels is that all recorded data for the first level is transferred, while only the recorded data for the second level is subject to throttling.
  By default throttling parameters are set at a maximum of 5MB every 5 minutes (both parameters are configurable, as described in the following procedure). The throttling parameters ensure that no output data will exceed the parameter values defined.

To modify the throttling parameters

1. In the command line utility, enter the regedit command and press Enter.
2. In the displayed Registry Editor window, locate the following keys (all keys are located in HKEY_LOCAL_MACHINE\SOFTWARE\Identify\AppSight Server and on 64-bit machines at HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node_
   Identify\AppSight Server) and modify them as required:
   • EUEMSlidingWindowTime: The default value is 5 (minutes). This value sets a maximum time period over which the data (ASL files) can be created.
   • EUEMSlidingWindowSize: The default value is 5 Mbytes. This value sets a maximum size limit for the amount of data (ASL files) that can be created.

Example:

In common testing scenarios, in order to generate as much output data as possible, you could increase the EUEMSlidingWindowTime value to 15 minutes and also increase the EUEMSlidingWindowSize value to 1GB. Note that once you have finished testing, BMC recommends you return the parameters to their default values to ensure you have enough disk space for future operations.