Start or Stop the Enterprise Manager

After the installation, ensure that the Enterprise Manager starts and does so without any error messages.
apmdevops106
After the installation, ensure that the Enterprise Manager starts and does so without any error messages.
Start the Enterprise Manager Manually on Windows
You can start the Enterprise Manager manually in
one
of these ways:
  • Navigate to Start, Programs, CA APM, Administration, CA APM, Enterprise Manager.
  • Go to the
    <EM_Home>
    directory and run the
    IntroscopeEnterpriseManager.exe
    file.
  • Use a Windows Service. Use the standard controls in the Windows Services GUI.
The Enterprise Manager starts in accordance with the property settings in the
<EM_Home>/Introscope_Enterprise_Manager.lax
file.
If you are unable to start the Enterprise Manager, see these articles:
Configure the Enterprise Manager as a Windows Service
Using the Enterprise Manager as a Windows Service increases its availability. If you configure the Enterprise Manager as a Windows Service, the computer on which it runs starts automatically. The Enterprise Manager shuts down when the computer shuts down.
Introscope uses a public domain Java Service Wrapper from Tanuki Software to enable the Enterprise Manager to run as a Windows Service. For information about the Tanuki wrapper, see the Configuration Property Overview.
Follow these steps:
These instructions assume that you are familiar with configuring applications on Windows Services, and with using the Windows Services console.
  1. Verify that Enterprise Manager is installed and that it runs properly in Console mode.
  2. Stop the Enterprise Manager.
  3. Go to the
    <EM_Home>/
    directory and open the
    Introscope_Enterprise_Manager.lax
    file in a text editor.
  4. Set the
    lax.stdin.redirect
    property to blank and save the file.
  5. Go to the
    <EM_Home>/config
    directory and open the
    IntroscopeEnterpriseManager.properties
    file in a text editor.
  6. Set the
    introscope.enterprisemanager.disableInteractiveMode
    property to true and save the file.
  7. Assign a unique name to the Enterprise Manager service. By default, a service name is assigned in the
    EMService.conf
    file, in the
    <EM_Home>/bin
    directory. If no other services are configured on the computer, you can use the default service name. Otherwise, modify
    EMService.conf
    to specify a unique name and a display name for the service using these properties:
    • wrapper.name=<unique Enterprise Manager name>
    • wrapper.displayname=<Enterprise Manager display name>
    To change JVM memory allocation, edit the
    wrapper.java.initmemory
    and
    wrapper.java.maxmemory
    properties in the
    EMService.conf
    file.
  8. Save the file.
  9. To register the Enterprise Manager instance as a service, run the
    <EM_Home>/bin/EMCtrl64.bat
    register script.
    Step 9 applies to a single Enterprise Manager on a Windows computer that is running with the
    Introscope-default
    JVM system parameters.
    The Windows Services console shows that the Enterprise Manager is configured as a Windows Service.
  10. Repeat these steps for each Enterprise Manager you want to run as a service.
Unregister an Enterprise Manager Windows Service
Unregister the Enterprise Manager Service:
  • Before you change the
    EMService.conf
    properties file.
  • To return the Enterprise Manager instance to Console control.
  • Before you uninstall the Enterprise Manager instance.
Follow these steps:
  1. Stop the Enterprise Manager Service and shut down the Windows Services GUI.
  2. Run
    <EM_Home>/bin/EMCtrl32.bat
    unregister.
The service is only
marked
for a deletion if either the Enterprise Manager Service or Windows Services GUI is active. This behavior is standard for a Windows Service, occurring because the Windows Registry lock prevents the service from being removed. When you restart the computer, the service is deleted.
Start the Enterprise Manager Manually on UNIX
When running the Enterprise Manager in a UNIX environment, you can start the Enterprise Manager manually.
Follow these steps:
  1. Open a command prompt.
  2. Enter the following command:
    '
    ./Introscope_Enterprise_Manager'
    The Enterprise Manager starts in accordance with the property settings in
    <EM_Home>
    .
    Enterprise Manager output appears in the UNIX shell. Start the Enterprise Manager using the
    nohup
    command, which allows the shell to accept user input.
Run the Enterprise Manager in
nohup
Mode on UNIX
You can start the Enterprise Manager in
nohup
mode. The UNIX
nohup
command runs an action, but suppresses the action of the HUP (hang up) signal. The command continues running after the user who issued it logs out. Output that typically goes to the terminal goes to a file named nohup.out. The UNIX shell only accepts user input when you start up the Enterprise Manager in
nohup
mode.
Follow these steps:
  1. Go to the
    <EM_Home>/
    directory and open the
    Introscope_Enterprise_Manager.lax
    file in a text editor.
  2. Set the
    lax.stdin.redirect
    property to blank, and save the file.
  3. Go to the
    <EM_Home>/config
    directory and open the
    IntroscopeEnterpriseManager.properties
    file in a text editor.
  4. Set the
    introscope.enterprisemanager.disableInteractiveMode
    property to
    true
    and save the file.
  5. Start the Enterprise Manager with this command:
    nohup Introscope_Enterprise_Manager&
Only run the Enterprise Manager in
nohup
mode after you configure it. Otherwise, the Enterprise Manager might not start, or can start and consume excessive system resources.
Manage the Enterprise Manager Using Control Scripts on UNIX
You can manage the Enterprise Manager by running control scripts on UNIX. These scripts let you start, stop, and view the server application status. You can use the
EMCtrl.sh
startup script to start and stop the Enterprise Manager instead of using the
./Introscope_Enterprise_Manager
command.
Follow these steps:
  1. Open a command prompt.
  2. Use any of the following commands at the bin directory:
    • ./EMCtrl.sh
      start
      Starts the Enterprise Manager
    • ./EMCtrl.sh
      stop
      Stops the Enterprise Manager
    • ./EMCtrl.sh
      status
      Displays the status of the Enterprise Manager
    • ./EMCtrl.sh
      help
      Displays the supported options for the script
If you are unable to start the Enterprise Manager manually, see TEC1679792.
Configure the Enterprise Manager to Use a Different JVM
By default, an Introscope component uses the JVM it is bundled with. You can configure the Enterprise Manager to use a different JVM. Use one of the following options:
  • To start the Enterprise Manager with
    Introscope Enterprise Manager.exe
    , edit the
    lax.nl.current.vm
    property to point to the desired JVM executable. Find this property in the
    Introscope_Enterprise_Manager.lax
    file.
    • You can use an absolute or relative path to the executable.
    • On Windows, escape backslashes, and include the JVM executable file extension:
      java.exe
      instead of java.
  • If you run the Enterprise Manager as a Windows service, edit the
    wrapper.java.command
    property to point to the desired JVM executable. Find this property in the
    EMService.conf
    file.
    • You can use absolute paths; backslashes must be escaped.
    • You can also use relative paths. We recommend that you use UNIX forward slashes and start with dot-slash (./).
    • The executable is java not
      java.exe
      .
  • If you start the Enterprise Manager with the
    runem.sh
    script on AS/400, edit the
    JAVA_HOME
    variable to point to the desired JVM root directory. Find this variable in the
    runem.sh
    file.
    • Use an absolute to the executable, not a relative path.
Create a config Directory for Each Enterprise Manager
You can have multiple Enterprise Managers that run using a single instance of Introscope. You create a separate configuration directory for each Enterprise Manager. This setup lets you:
  • Keep all the directories within one instance of Introscope.
  • Maintain separate configuration, logs, data, and traces directories for each Enterprise Manager.
Follow these steps:
  1. For each Enterprise Manager, make a copy of the config, logs, data, and traces directories.
  2. Open the
    IntroscopeEnterpriseManager.properties
    file in each copy of the config directory and modify the following property:
    introscope.enterprisemanager.directory.config=config
    The default directory is
    config
    . This directory is created when Introscope was first installed.
  3. Change the location of this directory using either:
    • An absolute path, for example,
      introscope.enterprisemanager.directory.config=C:\\Introscope\\em1\\config
    • A path relative to the Introscope installation directory, for example,
      config2
    In a Windows environment, backslashes must be escaped (doubled) for the path to function.
  4. Save and close the file.
  5. Open the
    Introscope_Enterprise_Manager.lax
    file and modify the following property:
    lax.nl.java.option.additional
    This property modifies the Java command line and can contain multiple properties. Use the location of the
    config
    file that you selected.
    This property can point either to a directory containing an Enterprise Manager properties file, or directly to an
    IntroscopeEnterpriseManager.properties
    file.
    Examples:
    -Dcom.wily.introscope.em.properties=C:\Introscope\em1\config
    -Dcom.wily.introscope.em.properties=C:\Introscope\em1\config\IntroscopeEnterpriseManager.properties
  6. Save and close the file.
  7. Restart the Enterprise Manager.
Use Enterprise Manager Shell and Terminal Window Commands
When the Enterprise Manager is running, you can use shell and terminal window commands.
Follow these steps:
  1. Set
    introscope.enterprisemanager.disableInteractiveMode
    to
    false
    in the Enterprise Manager properties file.
  2. Set
    lax.stdin.redirect
    to console.
  3. Enter any of the following commands in the Enterprise Manager terminal window or shell:
Command
Result
iscopehelp
Displays the help screen.
iscopeshutdown
Shuts down the Enterprise Manager.
The Enterprise Manager Log File
The
IntroscopeEnterpriseManager.log
file is located in the
<EM_Home>/logs
directory. The file records information about how Introscope, CA CEM, and the APM database are running and error conditions, for example:
  • Messages about start up and shut down
  • Certain types of exceeded overhead
  • Third-party libraries
  • CA CEM communications with the Enterprise Manager
  • Data about specific Introscope and CA CEM properties
You can configure the Enterprise Manager logging properties.
Roll Enterprise Manager Logs by Date or Size
You can roll Enterprise Manager logs based on date or size. Rolling the logs retains a specified number of days of information and purges the rest.
Follow these steps:
  1. Open the
    IntroscopeEnterpriseManager.properties
    file in the
    <EM_Home>\config
    directory.
  2. Locate the Logging Configuration section.
  3. Set the following properties to accomplish the log rolling you want.
    • To roll log files daily or by date, modify these properties:
      log4j.appender.logfile=com.wily.org.apache.log4j.DailyRollingFileAppender
      log4j.appender.logfile.DatePattern
      These properties work together to roll Enterprise Manager log files according to the date. The
      log4j.appender.logfile.DatePattern
      property defines the log rolling time period that the
      log4j.appender.logfile=com.wily.org.apache.log4j.DailyRollingFileAppender
      property carries out.
      Example:
      This configuration rolls the log files every day:
      log4j.appender.logfile=com.wily.org.apache.log4j.DailyRollingFileAppender
      log4j.appender.logfile.DatePattern='.'yyyy-MM-dd
    • To roll log files by time interval, modify the
      property log4j.appender.logfile.DatePattern
      . This Enterprise Manager property configures the time of day when the Enterprise Manager rolls log files.
      Examples:
      This configuration rolls the log files every hour:
      log4j.appender.logfile.DatePattern='.'yyyy-MM-dd-hh
      This configuration rolls the log file rolls every day at midnight:
      log4j.appender.logfile=com.wily.org.apache.log4j.DailyRollingFileAppender
      log4j.appender.logfile.DatePattern='.'yyyy-MM-dd
    • To roll log files by log size and quantity, modify the properties:
      log4j.appender.logfile.MaxBackupIndex
      This property determines how many backup log files the Enterprise Manager keeps.
      log4j.appender.logfile.MaxFileSize
      This property determines the maximum size of the log file.
      Example:
      This configuration keeps up to three backup/rolled Enterprise Manager logs, and each log is up to 2 KB:
      log4j.appender.logfile.MaxBackupIndex=3
      log4j.appender.logfile.MaxFileSize=2KB
  4. Save and close the
    IntroscopeEnterpriseManager.properties
    file.
Stop the Enterprise Manager
When you stop the Enterprise Manager:
  • Agents stop reporting data.
  • SmartStor does not save data.
  • You are logged out of the Workstation.
  • All users that are connected to the Enterprise Manager are disconnected.
If the Enterprise Manager detects errors writing to disk, indicating a shortage of disk space, it automatically shuts down. If failover is configured, agents can failover to another Enterprise Manager. For more information, see Java Agent
or Microsoft .NET Agent.
Follow these steps:
  1. Verify that you have shutdown privileges for the Enterprise Manager.
  2. Use one of the following methods:
    • From the terminal window:
      1. Set
        introscope.enterprisemanager.disableInteractiveMode
        to
        false
        in the Enterprise Manager properties files.
      2. From the terminal window, enter:
        iscopeshutdown
    • From the Workstation in a
      Management Module Editor
      window, select
      Manager
      ,
      Shut Down Enterprise Manager
      .
Restart After an Unplanned Shutdown
This information only applies to CA APM. This information does not apply to a standalone CA Introscope (without TIMs).
In most circumstances, restarting the Enterprise Manager is the same as starting it. However, if the Enterprise Manager has stopped in an error state instead of a planned shutdown, you might need to delete some files before restarting.
A shutdown can occur because of a heavy load or a file processing error. If an Enterprise Manager shuts itself down (crashes), unprocessed files can remain in the
<EM_Home>/cem/tess/badfiles
directory. When you restart the Enterprise Manager with these files present, the files are processed on restart. If these files caused the shutdown, another crash can occur immediately on restart when the Enterprise Manager begins to process these files. The solution is to delete the files from the directory before restarting the Enterprise Manager.
Follow these steps:
Deleting these files can result in some data loss. You can lose recent defect details, customer experience metrics, and statistics.
  1. On the Enterprise Manager that is running the TIM Collection Service, delete the files in the
    <EM_Home>/cem/tess/badfiles
    directory.
    The files are XML files and have names such as
    btstats-2010-01-05-23_26_13-172.16.252.20.xml
    and
    defect-12627339680000057712-172.16.252.20.xml
    .
  2. Start the Enterprise Manager.