Install and Configure TIM for CA CEM

After you have installed Introscope or the Enterprise Manager, install a Transaction Impact Monitor (TIM) to complete the CA CEM installation. A TIM server is responsible for recording and observing HTTP packets, identifying user logins, and related transactions. TIM is also used to monitor and report defects and other statistics to CA CEM. There can be one or more TIMs in a CA CEM environment.
apmdevops106
After you have installed Introscope or the Enterprise Manager, install a Transaction Impact Monitor (TIM) to complete the CA CEM installation. A TIM server is responsible for recording and observing HTTP packets, identifying user logins, and related transactions. TIM is also used to monitor and report defects and other statistics to CA CEM. There can be one or more TIMs in a CA CEM environment.
TIM installation is available as software that can be installed on any hardware that complies with your organization security policies. You can hence maintain and control the underlying operating system according to your IT policies.
2
Verify Prerequisites
Verify that you meet the following prerequisites:
  • You have the answers to the following questions:
    • Is the network connection to the TIM physical or virtual? If the network connection is virtual, ensure that clock drift issues do not occur.
    • Is the network connection SPAN or Network Tap? The answer to this question helps you understand the type of load that can be monitored without packet loss.
      Note:
      The number of TIMs usually matches the number of connections.
  • The computer on which you want to install TIM meets the requirements that are specified in the Product Compatibility Matrix.
    Note:
    The TIM requires some packages that are part of the Red Hat/CentOS distribution.
  • You understand CA APM Time Settings.
Minimum Hardware Requirements
The TIM computer must meet the following minimum requirements:
Physical computer
  • Dual or quad core 2.93-GHz processor
  • 4-GB RAM memory
  • 146 GB or larger HD
  • 64-bit x86 CPU
Network adapters
  • Two onboard copper 10/100/1000 network adapters
    Note:
    If you upgrade your network to fiber, CA Technologies recommend that the TIM computer have the following resources:
  • RAID 1 Mirroring, for redundancy
  • 16-GB RAM
  • Two available PCI-e 8x slots, for fiber network adapters or hardware security modules
  • Redundant power supplies with failover, for redundancy
  • (optional) Two Intel Pro 1000 MF (1 GB) onboard network adapters for fiber networks
Virtual computer
For information about installation on a VM, see TIM on Virtual Machines.
Linux Packages and Installation Files
You require the following files to install TIM software:
  • timInstall.bin
  • ca-eula.txt
  • CA-APM-TIM-public_key.txt
    This public key verifies that the TIM installation package signature is not compromised.
You require the following Linux packages on the computer where you want to install TIM software:
  • mod_ssl
  • compat-libstdc++-33
  • pexpect
  • unzip
  • httpd
  • nspr
  • libpcap
For 5.x RHEL, install the following packages also:
  • pstack
  • mod_python
  • java-1.6.0-openjdk
For 6.x RHEL, install the following packages also:
  • gdb
  • mod_wsgi
  • java-1.7.0-openjdk
  • policycoreutils-python
  • lsof (list of files; lower case l)
  • pciutils
Run the installer using root user privileges.
Example: Use the following command to install the package that comes with the OS distribution:
yum -y install
Example: Use the
install mod_ssl
command as follows:
yum -y install mod_ssl
Download the TIM Software
As part of your preparation process, download the CA APM TIM software files that you need for your particular deployment.
Follow these steps:
  1. Download the TIM software files from the CA APM software download area on support.
    • CA-APM-TIM-public_key.txt
    • The TIM compressed tar file: tim-<
      version
      >.Linux.<
      Enterprise Linux version
      >.<
      arch
      >-install.tar.gz
      Example: tim-9.8xxxx.Linux.el6.x86_64-install.tar.gz
      This package includes the following files:
      • ca-eula.en.txt -- The CA End-User License Agreement file
      • timInstall.bin -- The TIM interactive installer
  2. Decompress the files somewhere on your network. Note the locations of these files because you provide the path to some of them during the installation process.
CA APM Time Settings
Here are some important notes about time settings in CA APM:
  • The Collector running the TIM Collection Service communicates with the TIMs in Greenwich Mean Time. The time zone of the TIM affects only the timestamp of the log files of the TIM.
  • Set up your clusters to ensure that computers running Enterprise Managers synchronize their system clocks with a time server. An example is an NTP server. All computers must use the same NTP server or must use NTP servers that are synchronized with each other. The NTP servers can be synchronized directly or using some other time server.
  • Keep the TIM synchronized with the Enterprise Manager instances. Use caution while changing the system clock when in these situations:
    • Using a standalone Enterprise Manager
    • The installation has not been configured to synchronize with a time server.
  • Changing this time on the Enterprise Manager can affect CA CEM system functions as follows:
    • Setting the time forward (manually or DST change) results in gaps in the aggregation statistics.
    • Setting the time backward (manually or DST change) results in corruption, duplicate aggregation statistics, or both.
    • Changing the time in the middle of an aggregation process results in corrupted aggregation statistics.
  • Statistics and aggregation are based on the Enterprise Manager time zone
  • Ensure that the time on TIM matches with the time on the MOM or the collector. If the time is not synchronized, BT Stats and recordings are lost. The CEM console displays a TIM Time Not Synchronized event. Manually synchronize the TIM time in this situation.
  • The most important clock in CA APM is on the computer that hosts the Enterprise Manager or the MOM. The time setting in this clock is the time that all Collectors, agents, and TIMs must be synchronized with.
  • The Collector sends a request for TIM Collection Service every 15 minutes and at the Enterprise Manager startup.
  • CA APM requires that all hosts in a cluster are synchronized to within 3 seconds of each other. On virtual machine deployments, a time synchronization protocol is required because clocks drift and high CPU usage causes faster drift.
    More information
    : www.vmware.com
  • During the change from Daylight Saving Time (DST) to Standard Time, data for the “repeated” hour is overwritten. Data is lost from regular reports. The data is preserved in historical data, in transaction traces, error snapshots, and ChangeDetector data. On Linux, the system clock does not change when DST starts or stops. DST affects only I/O.
  • The MOM, database, and all Collectors must be in the same time zone.
Configure the TIM Network Management Settings
By default, the TIM software is configured to use DHCP assignment of IP addresses on the management port (eth0). You can use dynamically assigned IP addressing in short term or testing environments.
In a production environment, set a static IP address.
To configure the TIM Network Management Settings, edit the network configuration file.  Set the eth0 port to include a static IP Address, Subnet mask, and Gateway addresses as shown in this example:
/etc/sysconfig/network-scripts/ifcfg-eth0
Network management interface is configured.
Install the TIM Software
You install the TIM software and then access the TIM Setup Page to verify that the installation is successful. You can install the software in one of the following ways:
  • Memory-based file system
  • Disk-based file system
The TIM can handle more traffic using the memory-based file system than the disk-based file system. The memory-based file system can increase performance significantly.
Note:
The TIM uses a component named
apmpacket
to read packets from network interfaces and write the packets to files.
Follow these steps (memory-based file system):
  1. Navigate to the directory where you extracted the TIM compressed tar file.
  2. Accept the ca-eula.en.txt file:
    1. Open the ca-eula.en.txt file.
    2. Read the agreement.
    3. If you agree to the terms and conditions of the agreement, edit the CA-EULA property to: CA-EULA=accept
    4. Save and close the file.
  3. Mount /opt/CA/APM/apmpacket/data/pcap on a
    tmpfs
    file:
    mount -t tmpfs -o size=<fs_size>,mode=0744 tmpfs /opt/CA/APM/apmpacket/data/pcap
    -o size=number
    Specifies the size limit of the TMPFS file system
    Note:
    We recommend 5 GB or more for
    tmpfs
    for good performance.
  4. Specify the file path and file name of the CA EULA file and press Enter.
    Default:
    <
    Current Working Directory
    >/ca-eula.en.txt
    Specify any directory other than /tmp or /var/tmp.
  5. Specify the installation directory and press Enter.
    Default:
    /opt
    Specify any directory other than /tmp and /var/tmp.
  6. (Optional) Specify if you want to create a private HTTPD for TIM.
    1. Type
      Y
      if you want to specify a port other than the default HTTP port of 8080.
    2. Specify a valid port number for HTTP and press Enter.
    3. Specify a valid HTTPS port.
      Default:
      8443
    4. Specify if you want to modify the firewall to open the TIM HTTP server ports.
      Values:
      1 for Yes and 2 for No
      The firewall configuration file at /etc/sysconfig/iptables specifies open or blocked ports. To open the HTTPD port, type 1. The installer edits the firewall configuration file to add the port you specified.
  7. Specify the TIM internal port. TIM uses this internal port for communication with CEM.
    Default:
    81
  8. Confirm your specified ports.
    The installer commences TIM installation. By default, logs are written to the console. Verify that the logs do not contain any errors about libraries that are required for TIM.
  9. (Optional) Restart the HTTPD service using the
    service httpd restart
    command when the installation is successful.
  10. Verify that you can access the TIM Setup Page using the following URL:
    http://<TIM_Computer_Name or IP_Address>:<Port_Number>/cgi-bin/ca/apm/tim/index
    For the Tim Setup page, default user name is admin and password is quality. <Port_Number> refers to the httpd server port. If private httpd server instance is created for TIM, specify the corresponding httpd server port.
Follow these steps (disk-based file system):
  1. Navigate to the directory where you extracted the TIM compressed tar file.
  2. Accept the ca-eula.en.txt file:
    1. Open the ca-eula.en.txt file.
    2. Read the agreement.
    3. If you agree to the terms and conditions of the agreement, edit the CA-EULA property to:
      CA-EULA=accept
    4. Save and close the file.
  3. Start the interactive installer. Type:
    ./timInstall.bin
  4. Specify the file path and file name of the CA EULA file and press Enter.
    Default:
    <
    Current Working Directory
    >/ca-eula.en.txt
    Specify any directory other than /tmp or /var/tmp.
  5. Specify the installation directory and press Enter.
    Default:
    /opt
    Specify any directory other than /tmp and /var/tmp.
  6. (Optional) Specify if you want to create a private HTTPD for TIM.
    1. Type
      Y
      if you want to specify a port other than the default HTTP port of 8080.
    2. Specify a valid port number for HTTP and press Enter.
    3. Specify a valid HTTPS port.
      Default:
      8443
    4. Specify if you want to modify the firewall to open the TIM HTTP server ports.
      Values:
      1 for Yes and 2 for No
      The firewall configuration file at /etc/sysconfig/iptables specifies the open or blocked ports. To open the HTTPD port, type
      1
      . The installer edits the firewall configuration file to add the port you specified.
  7. Specify the TIM internal port. TIM uses this internal port for communication with CEM.
    Default:
    81
  8. Confirm your specified ports.
    The installer commences TIM installation. By default, logs are written to console. Verify that the logs do not contain any errors about libraries that are required for TIM.
  9. (Optional) Restart the HTTPD service using the following command when the installation is successful:
    service httpd restart
  10. Verify that you can access the TIM Setup Page using the following URL:
    http://<TIM_Computer_Name or IP_Address>:<Port_Number>/cgi-bin/ca/apm/tim/index
    For the Tim Setup page, default user name is admin and password is quality. <Port_Number> refers to the httpd server port. If private httpd server instance is created for TIM, specify the corresponding httpd server port.
Cannot Access the TIM Setup Page
Symptom:
I cannot access the TIM Setup Page using the following URL:
http://<TIM_Computer_Name or IP_Address>:<Port_Number>/cgi-bin/ca/apm/tim/index
A "page not found" error appears.
Solution:
A "page not found" error occurs when the TIM is not installed.
Verify that the TIM
rpm
package is installed successfully using the following command:
rpm -q tim
The TIM
rpm
package is listed.
Note:
One of the
rpm
packages is
apmpacket
, which reads network packets and writes them to files.
If the TIM
rpm
package is not listed, reinstall the TIM and look for error messages.
Error During TIM Installation
Symptom:
I see the following error during TIM installation:
<
TIM_Installation_Location
>/CA/APM/tim/bin/tim: error while loading shared libraries: libjvm.so: cannot open shared object file: No such file or directory
Solution:
  • Verify that <
    TIM_Installation_Location
    >/CA/APM/tim/jre contains the correct JVM. This JVM depends upon the RHEL version.
  • Verify that the location <
    TIM_Installation_Location
    >/CA/APM/tim/jre is not empty. If it is empty, uninstall and reinstall the correct version of the
    openjdk rpm
    .
Set the TIM Host Name and Domain Name
Setting the host name and domain name for each TIM is a best practice. The host name is required for some integrations, to use SMTP and SNMP protocols, and in some security environments.
Follow these steps:
  1. Connect to the TIM with the username
    root
    and the administrator password.
  2. Edit the host name in the /etc/sysconfig/network file or the host name and domain name in the /etc/hosts file. To set the host name parameter, use the host name command as shown in the following example:
    hostname myapmhost.mycompany.com
  3. Restart the TIM using
    one
    of the following procedures:
    • Click Start or Stop Tim in the Tim Setup page.
    • Execute the following command:
      service tim restart
    TIM host name and the domain name are configured.
Configure the TIM Network Monitor Interface
After the TIM software is installed, configure the TIM to monitor the network traffic and communicate with the Enterprise Manager.
Follow these steps:
  1. Access the TIM Setup page from a Web browser on any network computer.
  2. Select Configure TIM Network Interfaces
    option.
  3. Select the interface to monitor. The following interfaces are a few examples:
    • A copper cable that is connected to a switch to monitor the TIM traffic
    • A fiber cable that is connected to a network tap to monitor the TIM traffic
    • A tap that supports only half-duplex and you require dual fiber cards to achieve full-duplex
      Note:
      Select monitoring ports only for those ports on which the TIM is to receive a network monitoring feed. Do not use the management port for monitoring.
  4. Click Set.
    TIM is configured to monitor the network traffic.
Add and Enable TIMs
Enable TIMs so that they can monitor transactions and can send the data to the Enterprise Manager. If you have clustered Enterprise Managers, then enable the TIMs from the MOM.
The following scenarios are examples of when you enable TIMs:
  • When setting up a TIM and associating it with an Enterprise Manager
  • After upgrading the TIMs and Enterprise Manager
  • After upgrading the TIMs or Enterprise Manager
  • After a configuration is imported.
Follow these steps:
  1. Start a Web browser and input the address of the server that hosts the Enterprise Manager. <IP_Address> is the IP address or DNS name for the MOM or a standalone Enterprise Manager, as shown in the example. Use the DNS name that your DNS administrator configured.
    http://<IP_Address>:8081/wily
  2. Enter the user name and password.
  3. Select Setup, Monitors in the CEM console.
  4. Add a TIM if it does not appear in the list:
    1. Click
      New
      .
    2. Enter the name and IP address of the TIM.
    3. Enter HTTP port value on which TIM is installed. If TIM is installed using
      private httpd
      , the port value is the value that is specified during installation.
      Note:
      If https is enabled for CEM, specify the https port instead of the http port.
    4. Click
      Save
      .
  5. Select the check box next to each required TIM and click Enable.
    You have enabled communication between the Enterprise Manager and the TIMs. The CEM console displays the new
    Tools
    and
    CEM
    tabs.
Configure TIM Monitoring
You can configure each TIM to monitor specific network traffic and load balance the traffic among the TIMs.
If TIMs are incorrectly configured, then the network packet monitoring can be affected. If you do not configure the TIM web server filters, then the TIM monitors all IP addresses. If a TIM gets overloaded, recording can be affected. If you have more than one TIM monitoring the same servers, then transactions are monitored twice. This situation can also lead to false positive defects such as missing or partial responses.
Assign each TIM to the portion of the network that it must monitor.
Follow these steps:
  1. Select
    Setup
    ,
    Web Server Filters
    .
  2. Click
    New
    .
  3. Type a Name that describes the network portion for TIM monitoring. For example, WebFarmCorp1.
  4. In the Monitor list, select the TIM to assign to monitor this portion of the network.
  5. Select how you want to monitor by clicking one of the following options in the Address Type field:
    • IP Address
      Specifies the IP address of the device you want to monitor.
      Note:
      If there is only one server to monitor, type the specific IP address.
    • MAC Address
      Specifies the MAC address of the device you want to monitor.
  6. Complete the fields in the Web Server Filter Settings section.
    Note:
    In most cases, TIMs must monitor specific servers in the network rather than overlapping servers.To configure more than one monitor for an IP address or range, select Save without checking for overlapping IP Addresses.
  7. Click Save.
    TIM is configured to monitor the specified network.
Verify Communication Between the TIM and Enterprise Manager
Verify that the connection between the TIM and the Enterprise Manager is set up correctly. You can then view CA CEM reports and statistics.
Follow these steps:
  1. Open the CEM console.
  2. Select Setup, Monitors, and ensure that the TIMs are enabled.
  3. The Monitors page shows the following columns:
    • Domain Configuration Status
    • Monitor Configuration Status
    Both columns must show successful states for all enabled Monitors.
    If there is an error, the columns display a failure or an HTTP error code. To see details, click on the link of the monitor that failed.
The Enterprise Manager is running (refresh the browser).
  • All TIMs have the correct IP addresses.
  • All TIMs are running and are accessible.
  • All cables providing physical connections between the computers are securely in place.
Configure RTTM for User Groups
Real-time transaction metrics (RTTM) about the end-user experience by user group help you address issues before that experience degrades to incident creation. The RTTM metrics provide information about the user groups for all enabled TIMs in your implementation.
Follow these steps:
  1. In the administrator console, select
    Setup
    ,
    Services
    .
  2. Click
    TIM Collection Service
    .
    The TIM Collection Services pane appears.
  3. Verify that the RTTM Collection Service is running and the TIMs are enabled.
  4. Select
    Setup
    ,
    RTTM Configuration
    .
  5. Complete the settings:
    Enable grouping by User Group
    Reports the transactions that match a user group alias when it is defined. For no matching transactions, the TIM reports an actual identified user group. If no identification is defined for the parent business application, the behavior is similar to this option being disabled.
    If the user group is identified and also matches one of the alias matcher definitions in RTTM, the TIM reports the alias. For example, you configure a user group to match
    apm*
    . The alias is
    apm
    . Two different transactions have user groups that are identified as apm1 and apm2. Both user groups match
    apm*
    , so the alias
    apm
    identifies the user group. If a match exists and an alias is not present, the first transaction is identified as apm1 and second transaction is identified apm2 as user groups.
    Maximum Business Transaction group instances to report per TIM
    Specifies the maximum number of metrics that the TIM reports per interval (the default interval is 7 seconds).
    Note:
    Increasing this number beyond the default value can impact performance. Increasing this number beyond the default value can impact performance. Combinations of user group transactions can occur over time. Some combinations can occur once but can remain in the RTTM agent, reporting zero values until a restart. This behavior hinders new metrics appearing over time, because this number counts against the live metric count in the Enterprise Manager per agent limit. To overcome this behavior, use the age-out property for new business transaction group metrics. This property removes metrics that do not appear for over an hour (default). You can configure this option using the
    cem.btstats.ageOutAfter
    property in the
    tess-default.properties
    file. The value cannot be lower than 900 seconds. However, switching TCS, restarting RTTM service, and disabling monitor can cause immediate metric age-out.
  6. Create an RTTM matcher for collecting enhanced metrics. Click New or Update.
    The RTTM matcher page appears. You can add a new match setting for mapping patterns to an alias at the TIM. Grouping both wanted or unwanted metrics allows fewer metrics, which helps collect more metrics from the TIM per business transaction before reaching the maximum clamp. Changes propagate to TIMs immediately.
  7. Complete the following fields and click Save:
    Matcher
    Specifies a user group name for reporting transactions that match a user group alias. For no matching transactions, the TIM reports an actual user group.
    In WebView, transactions matching the alias are grouped under one metric. Other nonmatching user groups have individual metrics.
    Alias
    Specifies an alias name.
    Pattern
    Specifies the string pattern to match against identified values for grouping.
    Type
    Specifies the type of match performed for a pattern:
    – Exact Match—no wildcards (*) are allowed.
    – Simple Pattern Match—one wildcard is allowed.
    – Regular Expression Match
View APM Geo-Location Metrics
You can track the geographic locations of the business transactions, and can view the performance metrics for a location. Enable the geo-location feature under the CEM/TESS
RTTM
Configuration
tab to locate the business transactions geologically. The Collector that hosts CEM publishes the following metrics as part of RTTM metrics by Business transaction.
  • Count (number of times a given client IP access the business transaction)
  • Defect Count
  • Average response time
  • Performance defect count
  • Availability defect count
The Geo-location service that runs on MOM is exposed to all the connected collectors over the internal APM communication protocol. The internal APM communication protocol suits for internal APM clients that run on any collector. REST service is open to all the clients that provides a valid access token for every request.
You can access the REST service using the
/apm/appmap/private/geo
URI over a secure connection. You provide the access token that is generated using WebView to access the REST service. The access token is then sent to the REST client to access the
GeoLookup
REST API.
The
GeoUpdateService
uses a CSV file to upload the geo-location information to the APM database. GeoLookupService constructs the
GeoCache
using the geo-location information. The
GeoCache
processes every
Geolookup
request, and returns the respective geo-location information to the client. The CSV file contains the IP range and country information to tracks the business transactions for a specified location. Use the default CSV file that is available in the
deployGeo
folder. You can also create CSV file, or download it from a geo-location provider. If you create or download the CSV file, import it to a CA APM database. After you decide on the CSV file, enable the geo-location grouping to generate the location metrics.
To enable and disable
GeoUpdate
service, configure the following property in the IntroscopeEnterpriseManger.properties file:
i
ntroscope.enterprisemanager.hotGeoDeploy.enabled
By default, the property value is set to TRUE.
The
GeoUpdate
service uploads CSV file from
deployGeo
folder to CA APM database.
Import the CSV File to CA APM Database
You can use the
GeoUpdate
service to import the CSV file to the CA APM database when you are not using the default CA APM CSV file.
Follow these steps:
  1. Create a CSV file in a text editor, and save it, or download the CSV file from your geo-location provider.
    Note:
    The CSV file must contain the coma separated values including valid IP range (start IP and end IP) and Country. The Province and City are optional values.
  2. Ensure that the CSV file content that you created or downloaded over Internet meets the following criteria:
    • The CSV file extension must be
      .csv
      to avoid import failure.
    • Comma is the delimiter. The file must have at least three columns (IP range (start IP and end IP), country).
    • Supports only
      IPV4
      format and range for column one and two. Otherwise, the row is rejected and printed to a separate file.
    • (Optional) The value of the fourth column must be a State or Province, and the fifth column must be City.
    • No additional validation is done for country, state, province, and city.
    • Data is ignored if the file contains extra columns (more than five columns).
    • Do not overlap the subnets (from and to IP range). Otherwise, the last IP range (higher value from the sorted IPs) is considered.
    • Start IP must be unique. Otherwise, the duplicate Start IP is rejected.
    • Invalid data is logged in the separate CSV file.
    • A maximum of three sets of processed CSV files are archived in the
      deployGEO
      folder. Each set of processed file contains:
      • The original CSV file
      • A file that includes the invalid lines that are not logged on the Enterprise Manager logs form the original file. Configure the following property to specify the number of CSV files to archive:
        introscope.enterprisemanager.hotGeoDeploy.numberOfSetsOfFilesToKeep=3
  3. Place the CSV file in the default
    deployGEO
    folder.
    Alternatively, update the following property to provide the folder location from where the CSV file is imported.
    introscope.enterprisemanager.hotGeoDeploy.directory=deployGEO
Enable Geo-Location Grouping
You can enable or disable the geo-location grouping feature from the TESS
RTTM
Configuration
tab.
Follow these steps:
  1. In the Administrator console, select
    Setup
    ,
    RTTM Configuration
    .
  2. Select the
    Enable grouping by Geo location
    check box.
  3. (Optional) Select country, state, or city to specify, or view the metrics that are based on the selection. The city granularity option is the default value, when you enable the geo-location grouping option.
    The business transactions that are done from a location are tracked. The metrics for a geo-location are available in the
    ByGeo
    node under the existing Business Transaction node path of the
    RTTM
    metrics.
    For example, if you select a city in the Geo Location Granularity option, the metrics path is as follows:
    *SuperDomain* > Server_Name > CEM > CEM_Application (*SuperDomain*)>Busniess Services>BT1>ByGeo>US>California|Santa Clara: Average Response Time (ms)
    Note:
    If no location is identified, a
    Not Determined
    node appears in the ByGeo node. To analyze whey certain location is unidentified, disable and enable the geo-location grouping to view the latest logs in the EM log file. The logs help you troubleshoot the issue.
A cache (
GeoCache
) is created when the MOM starts, or the first RTTM data is processed after you enable the geo-location feature. The cache stores the start IP, end IP, and location triplet arrays. Each location triplet object contains the information about country, state province, and city. There can be multiple IP ranges that refer to the single location.
To enable or disable the in-memory IP-mapping when EM starts, configure the following property in the IntroscopeEnterpriseManger.properties file:
introscope.enterprisemanager.geolocation.initializeGeoMap
  • If the property value is set to TRUE, the IP mapping is built when EM starts.
  • If the property value is set to FALSE, then mapping is built on first request for the Geo-location data.
By default, the property value is set to TRUE.
Note:
The
cem.btstats.geolocation.initializeGeoMap
property is renamed to
introscope.enterprisemanager.geolocation.initializeGeoMap
property. The new property is now available in the
IntroscopeEnterpriseManager.properties
file, and not in the
tess-default.properties
file.
Verify the RTTM Configuration
After the RTTM Collection Service communicates with the TIM, verify that WebView displays the customer experience metrics as expected. If RTTM is configured for groups, metrics appear by report group under each business transaction.
Follow these steps:
  1. In WebView, open the Investigator and click the Metric Browser tab.
  2. Look for these nodes and metrics under *SuperDomain* > S
    erver_Name
    > CEM >
    CEM_Application
    (*SuperDomain*):
    • Business Service -- aggregated metrics from all the TIM monitors.
    • TIM -- one entry for each active TIM monitor you have.
      Note
      : If Enable grouping by User Group is selected, each TIM has user group nodes and metrics corresponding to that group for each monitored business transaction.
  3. Deploy the CEMBTStats Management Module using the following command:
    cp <EM_HOME>/examples/CEMBTStats/config/modules/BtStats_ManagementModule.jar <EM_HOME>/deploy/
  4. Select the New Console option in the Workstation menu.
  5. Select RTTM - CA CEM Overview from the Dashboard drop-down list.
    The RTTM - CA CEM Overview appears.
  6. Verify that real-time transaction data appears in the dashboard.
Change TIM Setup Page Password
Change the default password that allows access to the Setup Page on the TIM. Changing this password involves using the
htpasswd
command on the Linux computer.
Follow these steps:
  1. On the TIM, run the following command:
    htpasswd <TIM_Installation_Location>/httpd.passwd admin
    Note:
    Default location is
    /opt/CA/APM/tim
  2. At the prompt, input the new password.
    The password is changed.
Stop or Start a TIM
You stop a TIM in these situations:
  • You want to stop monitoring an application that the TIM is monitoring.
  • You notice that the TIM has excessive memory usage from an incorrectly written plug-in that makes the TIM unresponsive. After you resolve the problem, you can restart the TIM.
Follow these steps:
  1. Log in to the TIM as
    root
    using a console or
    ssh
    .
  2. Execute the command that corresponds to the action you want:
    service tim stop service tim start
(Optional) Uninstall TIM
You can uninstall the TIM software. Before you uninstall, ensure that no other computer is accessing the TIM.
Follow these steps:
  1. Open the CEM console and select Setup, Monitors.
    1. Select the enabled TIMs.
    2. Click Disable.
    3. Log out.
  2. Access the TIM Setup page using the following URL:
    http://<TIM_Computer_Name or IP_Address>:<Port_Number>/cgi-bin/ca/apm/tim/index
    The Tim Setup page appears.
  3. Click Configure Tim Settings and then click Start or Stop Tim. Close the page. The TIM stops.
    If the TIM does not stop, check the TIM logs. Or run the
    service tim stop
    command from the command line and monitor the results.
  4. Navigate to <
    TIM_Installation_Directory
    >/CA/APM/tim/uninstall and run timUninstall.sh.
  5. Restart the httpd service using the following command:
    service httpd restart
  6. (Optional) Delete
    all
    the TIM files, logs, and configurations by using the following command:
    rm -rf <TIM_Installation_Directory>
    Use this command with caution because it removes all the TIM directories and their contents.
    The TIM is uninstalled.
TIM on Virtual Machines
Installing a TIM on a virtual machine is supported for VMWare ESX and vSphere 4.x. The virtual machine (VM) must meet or exceed the following minimum requirements:
  • VMWare ESX
  • 2 vCPUs (3.2 GHz or faster)
  • 30-GB disk storage
  • 6-GB RAM
  • 2 vNICs
Note:
If you install TIM on a VMWare virtual machine, ensure that you configure the deployment to correct clock drift issues.
For the installation, follow the instructions in this CA Communities article.