Injecting JavaScript through browser plugins

You can inject JavaScript into your web applications to monitor their performance and availability. For SaaS-based web applications, you can use browser plugins to manage the JavaScript injection in the browsers of the users in your enterprise, without having to modify the web applications. 

Plugins for the following browsers are available:

• Chrome
• Firefox

Do the following to inject JavaScript through browser plugins.

1. Distribute the plugins to the browsers in your enterprise.
2. Configure the plugins.
3. Configure the applications to be monitored.

The following sections describe each step in detail.

Distributing the plugins

Distribute the plugins within your enterprise in any suitable way, such as the BMC Client Management application, or the Windows group policy. The plugins are located here:

• Plugin for the Chrome browser
• Plugin for the Firefox browser

For more information, use the following links:

• Documentation for the Chrome browser
• Documentation for the Firefox browser

Configuring the plugins

This section provides information about configuring the Chrome and Firefox browser plugins.

Configuring the Chrome browser plugin

Do the following on Windows:

1. Ensure that you have administrator privileges.
2. Create a registry key at the following location:
   <host_computer>\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\<extension_id>\Policy
3. Create a string key for each of the following mandatory settings and insert the correct values:
   • BeaconReceiverHost—The fully qualified server name for the beacon receiver
   • BeaconReceiverPort—The port for the beacon receiver server
   • Version—The version of the beacon receiver server, for example 11.3
4. Save your changes.

For more information, see the  Chrome documentation .

Configuring the Firefox browser plugin

Do the following on Windows:

1. Ensure that you have administrator privileges.

2. Create a .json schema file with the following content:

   {
"name": "active_eue_enteprise@bmc.com",
"description": "ignored",
"type": "storage",
"data": {
"BeaconReceiverHost": "<Beacon receiver host>",
"BeaconReceiverPort": <Beacon receiver port>,
"Version" : <Version>
}
}

3. Create a registry key at the following location:
   <host_computer>\HKEY_LOCAL_MACHINE\SOFTWARE\Mozilla\ManagedStorage\active_eue_enteprise@bmc.com
4. Change the Default key value to contain the full path to the .json schema file that you created.
5. Save your changes.

For more information, see the  Mozilla documentation .

Configuring the monitored web applications

You must configure the monitored web applications so that the browser plugins can monitor them.

Do the following:

1. On an App Visibility proxy server, open the following file:
   %AppVisibilityRoot%/apm-proxy/webapps/static-resources/plugin_settings.json

2. Insert the following content in the file:

   {
"DomainsWhitelist" : ["www.bmc.com”],
"ConfigRefreshIntervalMinutes": 1
}

    Information about the DomainsWhitelist parameter

   This parameter contains the list of monitored applications. You can change this list at any time to add or remove the applications to be monitored by the plugins. To add multiple applications, use a comma-spearated list. For example:
   
   

   {
"DomainsWhitelist" : ["www.app1.com”, "*.www.app2.com”, "www.app3.com”],
"ConfigRefreshIntervalMinutes": 1
}

   In this example, the plugins monitor any page under the www.app1.com, *.www.app2.com, and "www.app3.com applications.

   Ensure that you use a wild card only at the beginning of a URL.

    Information about the ConfigRefreshIntervalMinutes parameter

   This parameter controls the frequency in minutes at which the plugins are updated. For example, if the value of this parameter is 1, the plugins are updated every 1 minute.

   BMC recommends to use the default value of 1.

3. Save your changes.

4. Repeat the steps on each App Visibility proxy server.