Essential Tips and Tricks for new or inexperienced APM users planning an Enterprise Manager install or upgrade

Document ID : KB000048560
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

This article contains a collection of essential tips and tricks to help make your first APM Enterprise Manager install or upgrade a successful experience.

Solution:

Licensing:

Licenses are tied to Enterprise Managers, or, more specifically, to the server(s) on which they reside. No license file is needed for Agents. For all machines where EMs will be installed, be prepared to provide the hostname and IP Address when requesting a license key from CA. If planning separate installations for Production and Pre-Production, then request separate licenses for each server.

Managing existing Agents during an EM upgrade:

There is no need to shutdown the application servers being monitoring to do an EM install or upgrade. All agents can continue to run while the EMs are down, though all metrics they report during that time will be lost.

When the new EM comes up, simply reconfigure the agents to connect to the new IP Address and port of the new MOM or standalone EM. If installing a cluster (multiple EMs), always point all agents to the MOM.

The MOM will redistribute them to the EM Collectors in the cluster.

In the IntroscopeAgent.profile file for each agent, if connecting to the EM via SSL, locate this line and follow the instructions in that

section:

# To connect to the Enterprise Manager using SSL,

Provide the EM's (MOM or standalone) IP Address and secure port number.

If the EM's IP Address and/or port number have changed, then bounce the app server JVM for the changes to take effect. By waiting to do this until the EM install or upgrade is complete, the amount of time the app server is down is minimized.

What is a TIM?

A TIM is like a network sniffer. In its configuration are defined the filters and Business

Services to monitor. Metrics are created from the data flowing across a specific port that meets the criteria established in the filters and Business Services. This data is correlated by the EM connected to the TIM (known as the TIM Collector) with Agent data and stored in the APMDB (Postgres or Oracle). This data is used to populate the AppMap tab in the Workstation Investigator, among other things.

What data should be backed up before an EM upgrade?

  • /config
  • /data
  • /traces
  • the existing license key
  • the Postgres or Oracle APMDB

If you have these folders backed up and the upgrade fails, you can reinstall the old version of the EM and restore these folders after the reinstall is complete. This will return you to the state you were in before attempting the upgrade.

Determining where the old Postgres or Oracle database is located:

The userid & encrypted password and the JDBC connection string for the database are stored in:

EM_HOME\config\tess-db-cfg.xml

How to convert SSL Private Keys to PEM Format:

You can use a 3rd party utility to do this. OpenSSL is recommended.
http://www.sslshopper.com/article-most-common-openssl-commands.html

How to turn off Socket, NIO, and FileSystem Tracing

Socket, Network I/O, and FileSystem Tracing are not recommended in Production systems due to the amount of metrics they may generate.
In earlier versions of APM/Wily, these metric types were off by default.

If you do not need these metrics, you can turn them off by commenting out "TurnOn" directives in Toggles files at the Agent.

Locate the toggles-typical.pbd or toggles-full.pbd specified in IntroscopeAgent.profile in the introscope.autoprobe.directivesFile= parameter.

The toggles file will contain entries like these. To turn off specific tracing, put a "#" character in front of the "TurnOn:" directive.
Arestart of the agent will be required for these changes to take effect .

Here is an example toggles-typical.pbd file where Socket, NIO, and FileSystem Tracing have been turned off:


     #######################
     # Network Configuration
     # ================
     #TurnOn: SocketTracing
     # NOTE: Only one of SocketTracing and ManagedSocketTracing should be 'on'.
     ManagedSocketTracing is provided to
     # enable pre 9.0 socket tracing.
     #TurnOn: ManagedSocketTracing
     #TurnOn: UDPTracing
     #######################
     # File System Configuration
     # ================
     # TurnOn: FileSystemTracing
     #######################
     # NIO Socket Tracer Group
     # ================
     #TurnOn: NIOSocketTracing
     #TurnOn: NIOSocketSummaryTracing
     #TurnOn: NIOSelectorTracing
     #######################
     # NIO Datagram Tracer Group
     # ================
     #TurnOn: NIODatagramTracing
     #TurnOn: NIODatagramSummaryTracing