This documentation supports the 18.08 version of Remedy IT Service Management Suite.

To view the latest version, select the version from the Product version menu.

Using application servers to support BMC SLM Collector installations

Starting with the version 9.1.04, BMC will no longer provide support for the SLM Collector and all BMC provided integrations making use of the SLM Collector.

The following topics describe how to use application servers or servlet engines with the Collector:

To use performance or SIM-based service targets, you must install the Collector.

The Collector is an optional component and can be omitted if you do not need to create performance or SIM-based service targets.

Using the Collector requires a supported application server or servlet engines, for example, Apache Tomcat. The application server or servlet engine implements the Java servlets and allows for the execution of a Java web server environment.

For more information on supported servers, see the BMC Service Level Management Collector Information on the planning spreadsheet  in the BMC Remedy ITSM Suite Deployment online documentation.

For information on how the Collector functions in a server group environment, see Installing in the BMC Remedy ITSM Suite Deployment online documentation.

To add the Collector to an existing BMC SLM installation

  1. Install one of the supported application servers or servlet engines.
  2. Run the BMC SLM installer with only the Collector component selected.
  3. If the Collector server is not the same server as the AR Server, or the HTTP port number is not 8080, then you must edit and import the file WSFilters.xml found under the BMC SLM installation directory by completing the following steps:
    1. Open the file, SLM_APP_INSTALL_HOME>\ar\slm\workflow\en\WSFilters.xml
    2. Search for the pattern http://<COLLECTOR_SERVER>:<PORT_NUMBER>/daytona. (The default is http://<localhost:8080>/daytona).
      AND
      Replace every instance of<COLLECTOR_SERVER>:<PORT_NUMBER>with<COLLECTOR_SERVER>:<NEW_PORT_NUMBER>where<NEW_PORT_NUMBER>is the http port of the application server or servlet engine in which the Collector is running, and<COLLECTOR_SERVER>is the server that hosts the application server or servlet engine.
    3. Using DevStudio, import the edited WSFilters.xml file as a definition file into the BMC Remedy AR Server.
    4. Choose to import all and click the check box to overwrite existing objects.

To move a previously installed Collector to a new application server

The Collector can share an application server or servlet engine with other BMC platforms. Although, due to performance and memory requirements for various web applications, you might want to move the Collector to its own application server or servlet engine. To move an installed version of Collector to a new application server, complete the following steps:

  1. Stop the existing application server or servlet engine.
  2. Uninstall the Collector.
    This removes the Collector web application.
  3. Start that existing instance again.
  4. Install the Collector to a new application server/servlet engine.
  5. Open the file: SLM_APP_INSTALL_HOME>\ar\slm\workflow\en\WSFilters.xml
  6. Search for the pattern Search for the pattern http://<COLLECTOR_SERVER>:<PORT_NUMBER>/daytona. (The default is http://<localhost:8080>/daytona).
    AND
    Replace every instanceof<COLLECTOR_SERVER>:<PORT_NUMBER>with<COLLECTOR_SERVER>:<NEW_PORT_NUMBER>where<NEW_PORT_NUMBER>is the http port of the application server or servlet engine in which the Collector is running, and<COLLECTOR_SERVER>is the server that hosts the application server or servlet engine.
  7. Using DevStudio, import the edited WSFilters.xml file as a definition file into the BMC Remedy AR Server.
  8. Choose to import all and click the check box to overwrite existing objects.

Was this page helpful? Yes No Submitting... Thank you

Comments