Home  Administration > Data Collector Administration > SiteScope Administration > External Integrations and Functionality > Integration with Mercury Business Availability Center > Changing the Core Server to Which SiteScope Sends Data



Changing the Core Server to Which SiteScope Sends Data

Beginning in SiteScope 8.0.0.1, you can change the Core Server to which a SiteScope agent reports its data. Generally, this is only applicable if you are working with a Mercury Business Availability Center deployment with components installed on more than one server.

Note: You must use the SiteScope Classic interface to make this change.

Limitations

The following are limitations for using this feature:

Changing the Core Server to Which SiteScope Sends Data (Version 8.0.0.1 and Later)

To change the Core Server to which SiteScope sends data:

  1. Access the SiteScope Classic interface. You do this by opening a Web browser to the SiteScope server address. By default, the address will have the form of http://<SiteScope server>:8888.
  2. Click the Preferences button on the SiteScope main navigation bar. The General Preferences page opens.
  3. Select the Mercury BAC link from the Preferences submenu. The Mercury Business Availability Center Server Registration page opens.
  4. Click the Edit Core Server button
  5. In the Business Availability Center server machine name/IP address box, enter the required Core Server name or IP address
  6. Click Update to save the changes.
  7. Restart SiteScope

Changing Core Server for Other SiteScope Versions

Prior to the 8.0.0.1 version of SiteScope, changing the Core Server to which a SiteScope reports its data requires that you execute a command line procedure on the SiteScope server. As part of each procedure, you specify a name of a file which is created during the process and used to modify SiteScope configuration information. The following describe the steps you use for earlier versions of SiteScope.

To change the Core Server to which SiteScope 7.8.1.2 or 7.8.1.0 sends data:

  1. Make a note of the name of the currently configured Core Server to which the SiteScope is sending its data. Also note the name of the other Core Server to which you want to redirect the SiteScope reporting.
  2. Access the server where the subject SiteScope is running.
  3. Open a command line window on the SiteScope server and change the working directory to the <SiteScope_install_path>\SiteScope\classes directory.
  4. Execute the following command line to export the relevant SiteScope configuration data to a text file. Substitute a valid filename for the <filename> parameter (for example, sitescope2bca.txt):
  5. ..\java\bin\java -cp COM.freshtech.TopazIntegration.TopazServerSettings export <filename>

  6. Open the exported text file with a text editor. Replace all occurrences of the original Core Server name with the name of the new Core Server.
  7. Save the changes to the text file.
  8. Stop the SiteScope service.
  9. In the command line window, execute the following command line to import the relevant SiteScope configuration data to SiteScope. Substitute the name of the text file for the <filename> parameter as indicated:
  10. ..\java\bin\java -cp COM.freshtech.TopazIntegration.TopazServerSettings import <filename>

  11. Restart the SiteScope service.

To change the Core Server to which SiteScope 7.9.1.0 or 7.9.5 sends data:

  1. Make a note of the name of the currently configured Core Server to which the SiteScope is sending its data. Also note the name of the other Core Server to which you want to redirect the SiteScope reporting.
  2. Access the server where the subject SiteScope is running.
  3. Open a command line window on the SiteScope server and change the working directory to the <SiteScope_install_path>\SiteScope\classes directory.
  4. Execute the following command line to export the relevant SiteScope configuration data to a text file. Substitute a valid filename for the <filename> parameter (for example, sitescope2bca.txt):
  5. ..\java\bin\java -cp COM.freshtech.TopazIntegration.AMSettingsManager export <filename>

  6. Open the exported text file with a text editor. Replace all occurrences of the original Core Server name with the name of the new Core Server.
  7. Save the changes to the text file.
  8. Stop the SiteScope service.
  9. In the command line window, execute the following command line to import the relevant SiteScope configuration data to SiteScope. Substitute the name of the text file for the <filename> parameter as indicated:
  10. ..\java\bin\java -cp COM.freshtech.TopazIntegration.AMSettingsManager import <filename>

  11. Restart the SiteScope service.

To change the Core Server to which SiteScope 8.0.0.0 sends data:

  1. Make a note of the name of the currently configured Core Server to which the SiteScope is sending its data. Also note the name of the other Core Server to which you want to redirect the SiteScope reporting.
  2. Access the server where the subject SiteScope is running.
  3. Open a command line window on the SiteScope server and change the working directory to the <SiteScope_install_path>\SiteScope\classes directory.
  4. Execute the following command line to export the relevant SiteScope configuration data to a text file. Substitute a valid filename for the <filename> parameter (for example, sitescope2bca.txt):
  5. ..\..\java\bin\java.exe -Dtopaz.home=..\..\\conf\ems\tools -classpath ..\..\WEB-INF\classes;..\..\WEB-INF\lib\jgl.jar;..\..\WEB-INF\lib\xdr.jar;..\..\WEB-INF\lib\tmc_ex_data.jar;..\..\WEB-INF\lib\xdr_utils.jar;..\..\WEB-INF\lib\jms.jar; COM.freshtech.TopazIntegration.AMSettingsManager export <filename>

  6. Open the exported text file with a text editor. Replace all occurrences of the original Core Server name with the name of the new Core Server.
  7. Save the changes to the text file.
  8. Stop the SiteScope service.
  9. In the command line window, execute the following command line to import the relevant SiteScope configuration data to SiteScope. Substitute the name of the text file for the <filename> parameter as indicated:
  10. ..\..\java\bin\java.exe -Dtopaz.home=..\..\\conf\ems\tools -classpath ..\..\WEB-INF\classes;..\..\WEB-INF\lib\jgl.jar;..\..\WEB-INF\lib\xdr.jar;..\..\WEB-INF\lib\tmc_ex_data.jar;..\..\WEB-INF\lib\xdr_utils.jar;..\..\WEB-INF\lib\jms.jar; COM.freshtech.TopazIntegration.AMSettingsManager import <filename>

  11. Restart the SiteScope service.



Copyright 2006 Mercury Interactive Corporation