EMC Smarts Application Connectivity Monitor 2.2

Transcription

1 EMC Smarts Application Connectivity Monitor 2.2 Installation Guide P/N REV A02 EMC Corporation Corporate Headquarters: Hopkinton, MA

2 Copyright EMC Corporation. All rights reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com All other trademarks used herein are the property of their respective owners. ii EMC Smarts Application Connectivity Monitor Installation Guide

3 Contents Preface... v Chapter 1 Chapter 2 Chapter 3 Application Connectivity Monitor Overview About Application Connectivity Monitor EMC Smarts product and version compatibility Installation tasks Upgrade tasks Uninstallation tasks Application Connectivity Monitor Requirements Operating system requirements Hardware requirements Installing Application Connectivity Monitor Before installation Installation requirements Determine the location of the EMC Smarts Broker Detect and stop EMC Smarts programs Install EMC Smarts Application Connectivity Monitor Mounting the CD-ROM Inserting the CD-ROM Performing the installation Using wizard mode Using CLI-Mode Using unattended (silent) mode EMC Smarts Application Connectivity Monitor Installation Guide iii

4 Contents Chapter 4 Chapter 5 Appendix A Appendix B Appendix C Appendix D Uninstalling Application Connectivity Monitor Before uninstallation Detect and stop EMC Smarts programs Uninstall Application Connectivity Monitor Uninstall using Wizard-Mode Uninstall using Unattended mode Uninstall from the Control Panel (Windows only) Verifying the Installation Obtain and install a temporary license file Start EMC Smarts products Start EMC Smarts services Starting services on UNIX Starting services on Windows Verify the EMC Smarts product status Where to go next Manually Installing Services Overview... A-2 Manually installing the Broker... A-3 Manually installing Application Connectivity Monitor... A-4 UNIX Procedures for CD-ROMs Mounting the CD-ROM... B-2 Manually Starting Products Start products in native mode (UNIX only)... C-2 Understanding the sm_edit Utility The sm_edit utility... D-2 iv EMC Smarts Application Connectivity Monitor Installation Guide

5 Preface This document provides instructions for installing the EMC Smarts Application Connectivity Monitor product. Audience for this guide This guide is intended for administrators and integrators responsible for installing the EMC Smarts Application Connectivity Monitor. EMC Smarts Application Connectivity Monitor installation directory In this document, the term BASEDIR represents the location where the Application Connectivity Monitor software is installed. For UNIX, this location is: /opt/incharge<n>/<productsuite>. For Windows, this location is: C:\InCharge<n>\<productsuite>. The <n> represents the software platform version number. The <productsuite> represents the EMC Smarts product suite to which this product belongs. This location is referred to as BASEDIR/smarts. On UNIX operating systems, Application Connectivity Monitor is, by default, installed to: /opt/incharge7/acm/smarts. On Windows operating systems, this product is, by default, installed to: C:\InCharge7\ACM\smarts. Optionally, you can specify the root of BASEDIR to be something other than: /opt/incharge7 (on UNIX) C:\InCharge 7 (on Windows) EMC Smarts Application Connectivity Monitor Installation Guide v

6 Preface However, you cannot change the <productsuite> location under the root directory. The EMC Smarts System Administration Guide describes the directory structure of Smarts software. EMC Smarts Application Connectivity Monitor products Application Connectivity Monitor includes the following products: Application Connectivity Monitor Related documentation In addition to this document, EMC Corporation provides a Help system for command line programs as well as product documentation. Help for command line programs Descriptions of command line programs are available as HTML pages. The index.html file, which provides an index to the various commands, is located in the BASEDIR/smarts/doc/html/usage directory. EMC Smarts documentation Readers of this guide may find the following related documentation helpful. It can be found in the BASEDIR/smarts/doc/pdf directory. Note: These documents are updated periodically. Electronic versions of the updated manuals are available on the Powerlink website: EMC Smarts Documentation Catalog EMC Smarts System Administration Guide EMC Smarts ICIM Reference EMC Smarts Common Information Model Infrastructure Models Chart EMC Smarts Common Information Model Application Business Models Chart EMC Smarts ASL Reference Guide EMC Smarts Perl Reference Guide EMC Smarts Dynamic Modeling Tutorial EMC Smarts MODEL Reference Guide vi EMC Smarts Application Connectivity Monitor Installation Guide

7 Preface EMC Smarts Application Connectivity Monitor documentation The following documents are relevant to users of Application Connectivity Monitor: EMC Smarts Application Connectivity Monitor Release Notes EMC Smarts Application Connectivity Monitor Installation Guide EMC Smarts Application Connectivity Monitor Configuration Guide EMC Smarts Application Connectivity Monitor User s Guide Suggestions for searching PDF files You may search across multiple PDF files using the Adobe Acrobat Reader software. 1. If the documentation is not accessible to all users of the EMC Smarts product suite, copy the contents of the BASEDIR/smarts/doc/pdf directory to a central location, such as a shared drive on your LAN, that operators and others may view. 2. To search throughout the documentation library, open the Acrobat Reader software. a. Choose Edit > Search, and enter a word or phrase. b. In the Where would you like to search option, select All PDF Documents in and type the pathname of the location where the PDF documents reside. If you have more than one EMC Smarts product suite installed, you can set up cross-product document searches by copying files from the BASEDIR/smarts/doc/pdf directory for each product suite into this common documentation directory path. Conventions used in this guide EMC uses the following conventions for notes and cautions. Note: A note presents information that is important, but not hazard-related.! IMPORTANT An important notice contains information essential to the operation of the software. EMC Smarts Application Connectivity Monitor Installation Guide vii

8 Preface! CAUTION A caution contains information essential to avoid data loss or damage to the system or equipment. The caution may apply to hardware or software. Normal font Bold Italic Typographical conventions EMC uses the following conventions in this guide: In running text: Interface elements (for example, button names, dialog box names) outside of procedures Items that the user selects outside of procedures Java classes and interface names Names of resources, attributes, pools, Boolean expressions, buttons, DQL statements, keywords, clauses, environment variables, filenames, functions, menu names, utilities Pathnames, URLs, filenames, directory names, computer names, links, groups, service keys, file systems, environment variables (for example, command line and text), notifications In procedures: Names of dialog boxes, buttons, icons, menus, fields, and maps Selections from the user interface, including menu items, and field entries Key names Window names Code examples Commands User interface tabs Used for: Full publications titles referenced in text In procedures: Directory paths Filenames Scripts Important/unique words URLs Utilities Variables Courier Used for: System output User entry < > Angle brackets used to enclose parameter or variable values supplied by the user. [ ] Square brackets used to indicate optional values. viii EMC Smarts Application Connectivity Monitor Installation Guide

9 Preface Vertical bar used to indicate alternate selections. The bar means or. { } Braces used to indicate content that you must specify (that is, x or y or z).... Ellipses used to indicate nonessential information omitted from the example. % Used to indicate a C shell prompt. # Used to indicate a C shell superuser prompt. Used to indicate a command is wrapped over one or more lines. The command must be typed as one line. Pathname conventions Directory pathnames are shown with forward slashes (/). Users of the Windows operating systems should substitute back slashes (\) for forward slashes. Graphical conventions If there are figures illustrating consoles in this document, they represent the consoles as they appear in Windows. Under UNIX, the consoles appear with slight differences. For example, in views that display items in a tree hierarchy such as the Topology Browser, a plus sign appears for Windows and an open circle displays for UNIX. Smarts Manager Unless otherwise specified, the term Smarts Manager is used to refer to EMC Smarts programs such as Domain Managers, Global Managers, and adapters. EMC Smarts Application Connectivity Monitor Installation Guide ix

10 Preface Where to get help EMC support, product, and licensing information can be obtained as follows. Product information For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at: Technical support For technical support, go to EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account. Sales and customer service contacts For the list of EMC sales locations, please access the EMC home page at: x EMC Smarts Application Connectivity Monitor Installation Guide

11 1 Application Connectivity Monitor Overview This chapter describes the EMC Smarts Application Connectivity Monitor product and its compatibility with other EMC Smarts products. In addition, this chapter provides checklists for installation and uninstallation tasks. EMC Smarts product and version compatibility Installation tasks Upgrade tasks Uninstallation tasks The product is distributed on a CD-ROM and is installed in the ACM subdirectory under the InCharge7 directory. Application Connectivity Monitor Overview 1-1

12 Application Connectivity Monitor Overview About Application Connectivity Monitor Application Connectivity Monitor (ACM) is a software package that automatically discovers TCP-based applications on the network, and monitors application connectivity to pinpoint the root cause of application availability problems. Application Connectivity Monitor operates in conjunction with: Availability Manager Availability Manager provides the network topology for Application Connectivity Monitor and identifies system outages (or impact of network outages) for Application Connectivity Monitor to correlate with application outages. Service Assurance Manager Service Assurance Manager collects the results of the deployment s root-cause analysis, and presents the results to network operations personnel through its Global Console. 1-2 EMC Smarts Application Connectivity Monitor Installation Guide

13 Application Connectivity Monitor Overview EMC Smarts product and version compatibility Table 1-1 Application Connectivity Monitor is compatible with the versions of the products listed in the EMC Smarts Application Connectivity Monitor 2.2 interoperability chart shown in Table 1-1. Interoperability chart EMC Smarts product suite EMC Smarts Service Assurance Management Suite EMC Smarts IP Management Suite and 7.0 EMC Smarts product and version compatibility 1-3

14 Application Connectivity Monitor Overview Installation tasks Tasks: Table 1-2 To install Application Connectivity Monitor, satisfy the requirements and perform the tasks listed in Table 1-2. EMC Smarts Application Connectivity Monitor installation requirements and tasks Go to: Before you install EMC Smarts Application Connectivity Monitor: Satisfy all requirements to install the suite. Check the Broker configuration. Detect and stop EMC Smarts programs. Choose an operating mode for the installation program. Application Connectivity Monitor Requirements on page 2-1 Before installation on page 3-2 Determine the location of the EMC Smarts Broker on page 3-3 Detect and stop EMC Smarts programs on page 3-3 Choose an operating mode for the installation program on page 3-6 Installation method: Insert the CD-ROM. Mounting the CD-ROM on page 3-9 Install using your chosen mode of operation: Wizard Mode CLI Mode Unattended (Silent) Mode Using wizard mode on page 3-10 Using CLI-Mode on page 3-13 Using unattended (silent) mode on page 3-14 After you install: Save your EMC Smarts evaluation license, smarts.lic, to the BASEDIR/smarts/local/conf directory. Edit the SM_LICENSE variable in the runcmd_env.sh file so that the variable specifies the full path name to the smarts.lic file. Manually Installing Services on page A-1 contains information on manually installing products as services. on page 5-3 Start Application Connectivity Monitor for the first time. Start EMC Smarts products on page 5-3 Verify the current state of the products and Broker. Verify the EMC Smarts product status on page 5-6 Install your permanent EMC Smarts license. EMC Smarts System Administration Guide 1-4 EMC Smarts Application Connectivity Monitor Installation Guide

15 Application Connectivity Monitor Overview Upgrade tasks You should run an Application Connectivity Monitor upgrade under the following conditions: You have an existing Application Connectivity Monitor installation You are installing the Application Connectivity Monitor 2.2 on the same physical machine The EMC Smarts Application Connectivity Monitor Release Notes contains additional information. Upgrade tasks 1-5

16 Application Connectivity Monitor Overview Uninstallation tasks To uninstall Application Connectivity Monitor, satisfy the requirements and perform the tasks listed in the Application Connectivity Monitor uninstallation requirements and tasks table shown in Table 1-3. Table 1-3 EMC Smarts Application Connectivity Monitor uninstallation requirements and tasks Tasks: Go to: Before you uninstall Application Connectivity Monitor: Detect and stop EMC Smarts programs Detect and stop EMC Smarts programs on page 4-3 Uninstallation method: Uninstall Application Connectivity Monitor using one of these methods or modes: Windows Control Panel method Wizard Mode CLI Mode Unattended (Silent) Mode Uninstall using Unattended mode on page 4-9 Uninstall using Wizard-Mode on page 4-8 Uninstall using Unattended mode on page 4-9 Uninstall using Unattended mode on page EMC Smarts Application Connectivity Monitor Installation Guide

17 2 Application Connectivity Monitor Requirements This chapter describes the operating system and hardware requirements for EMC Smarts Application Connectivity Monitor 2.2 and contains the following information: Operating system requirements Hardware requirements Application Connectivity Monitor Requirements 2-1

18 Application Connectivity Monitor Requirements Operating system requirements Table 2-1 summarizes the operating system platforms that are supported by the EMC Smarts Application Connectivity Monitor. Table 2-1 Support Platforms for Application Connectivity Monitor Operating system Version Solaris Versions 9 and 10 Windows Windows 2003 Enterprise Edition R1 and R3 Linux Red Hat Enterprise Linux AS 3, 4 VMWare ESX Server 2.5.x Windows 2003 Enterprise Edition R1 Red Hat Linux AS 3 Update EMC Smarts Application Connectivity Monitor Installation Guide

19 Application Connectivity Monitor Requirements Hardware requirements The minimum hardware requirements for installing Application Connectivity Monitor are summarized in the following tables. Table 2-2 lists the specific platform requirements for Application Connectivity Monitor. Table 2-2 Application Connectivity Monitor platform requirements Platform Platform hardware Solaris Sun Fire 280 Windows Red Hat Linux 2xPentium4, 2GHz 2XPentium4, 2GHz Table 2-3 lists disk space requirements for installing Application Connectivity Monitor. Table 2-3 Required disk space for Application Connectivity Monitor Platform Solaris Windows Linux Disk space 350 MB 350 MB 245 MB Table 2-4 lists minimum requirements for CPUs, memory, and data disk space used by the software for writeable files such as logs, repository files, and output files. Note: CPU means the number of physical CPU cores; not the number of CPU's displayed when hyperthreading is activated. If you are installing more than one product, then your system must meet the products total memory and data disk space requirements Hardware requirements 2-3

20 Application Connectivity Monitor Requirements (disk space (Table 2-3) plus RAM plus data disk space for a product (Table 2-4)). Table 2-4 CPU, memory, and data disk space requirements EMC Smarts product CPUs Memory (RAM) Data disk space Application Connectivity Monitor MB 100 MB each 2-4 EMC Smarts Application Connectivity Monitor Installation Guide

21 3 Installing Application Connectivity Monitor This chapter describes instructions if you are installing Application Connectivity Monitor for the first time and includes the following information: Before installation Install EMC Smarts Application Connectivity Monitor The basic installation steps are the same for all supported platforms. Installing Application Connectivity Monitor 3-1

22 Installing Application Connectivity Monitor Before installation This section explains the requirements that must be met before installing EMC Smarts Application Connectivity Monitor. See: Installation requirements on page 3-2 for an explanation of administrator access and JAVA JRE requirements. Determine the location of the EMC Smarts Broker on page 3-3. Detect and stop EMC Smarts programs on page 3-3. Choose an operating mode for the installation program on page 3-6. Installation requirements Before beginning, you must satisfy the following requirements: Access requirement: The user performing the installation must either be superuser (User ID 0) on UNIX platforms or have administrative privileges on Windows platforms. The installation program will halt if the user does not have the appropriate privileges. JRE requirement: Version 1.4.2_06 or later of the Java Runtime Environment (JRE) must be installed on the system to run the installation program. The installation program attempts to detect that a compatible JRE version has been installed on your system. If necessary, download the required J2SE JRE version: Solaris: Linux: Windows: If a compatible JRE version is installed and the installation program cannot locate it, you must specify the location when you execute the installation program. Based on the operating mode of the installation program that is used when installing or upgrading the suite, there may be additional requirements. These requirements are included in the procedures for the specific modes. 3-2 EMC Smarts Application Connectivity Monitor Installation Guide

23 Installing Application Connectivity Monitor Determine the location of the EMC Smarts Broker You must specify the location of the EMC Smarts Broker during installation of the EMC Smarts software. Typically, this location is chosen during the design of the EMC Smarts software deployment and before any installation begins. Consult with your deployment planner or check the build guide that documents your deployment to determine the name of the host where the Broker was installed and the port that the Broker uses. If the location is the same host where you are installing this suite, then the installation program will automatically install the Broker if it is not already on the host. Detect and stop EMC Smarts programs Before installing or uninstalling your suite, you must stop all EMC Smarts services, EMC Smarts scheduled jobs, and any other process that uses programs or libraries in any EMC Smarts installation area. On UNIX systems, this also includes the Smarts service daemon process, sm_serviced. WARNING When you install a Service Pack or Hot Fix, all Smarts product suites on the same host must be show down. If the Broker is no the host, it too must be shut down. This will prevent Smarts applications from starting and new connections from being established while the Broker is down. Inform any users who may be affected and, if necessary, schedule the installation or uninstallation for a period of low utilization. Detecting EMC Smarts programs The sm_plist utility identifies all Smarts programs that are running for any product suite on your machine. You can use the sm_plist utility whenever you need to identify Smarts programs that are running (for example, before an installation or uninstallation, or applying another Service Pack or Hot Fix). To use the utility, invoke it from the BASEDIR/smarts/script directory. The utility displays active programs in a window: 1. Go to the BASEDIR/smarts/script directory. Before installation 3-3

24 Installing Application Connectivity Monitor 2. Start the sm_plist utility: For UNIX, enter #./sm_plist.sh BASEDIR2 For Windows, enter cscript sm_plist.vbs BASEDIR2 where BASEDIR is the directory where the sm_plist utility is installed and BASEDIR2 represents the location of any EMC Smarts product suite. Stopping active EMC Smarts programs (UNIX) 1. Stop active EMC Smarts services using the sm_service utility from BASEDIR/smarts/bin: #./sm_service stop --all Note: sm_serviced waits 30 minutes after sending a shutdown request to a process. If the process is still running after 30 minutes, sm_serviced terminates it. 2. Determine if any EMC Smarts services are still running by using the brcontrol utility from BASEDIR/smarts/bin: #./brcontrol -b <host>:<port> Based on the location of the Broker, go to the appropriate step, as indicated in Table 3-1. Table 3-1 Next steps for detecting and stopping programs The Broker is on the And this displays. Do this Same host Different host Error attaching to Broker message List of servers registered with the Broker List of servers registered with the Broker The EMC Smarts Broker is not running. Go to Step 4. The Broker or service daemon did not shut down. If any servers are still running on the host, these did not shut down. Go to Step 3. If any servers are still running on the host where you will install the EMC Smarts software, these did not shut down. Go to Step Stop any EMC Smarts manager that is still running. If the Broker is on the host, stop the local Broker: 3-4 EMC Smarts Application Connectivity Monitor Installation Guide

25 Installing Application Connectivity Monitor To stop any manager that is still running, use the dmquit utility from BASEDIR/smarts/bin: #./dmquit --server=<servername> To stop the local Broker from BASEDIR/smarts/bin: #./brquit --broker=localhost:<port> 4. Determine if any other EMC Smarts processes are still running and shut the processes down: Detect the processes using the following command: # ps -ef grep sm_ If a list is displayed, note the process ID (pid) of these active EMC Smarts processes. WARNING Do not stop or kill the EMC Smarts service daemon process, sm_serviced. Shut down these EMC Smarts processes (except sm_serviced) using the following command: # kill <pid> Stopping active EMC Smarts programs (Windows) To stop a service from the Windows desktop using the Microsoft Management Console: 1. Select Settings > Control Panel. 2. At the Control Panel, select Administrative Tools. 3. At the Administrative Tools folder, select Services. 4. At the Services window, locate any running Smarts services. These services start with the words EMC Smarts, InCharge, or Smarts. For each of these services, right-click the service and then select Stop. Note: Do not stop the Broker service. 5. Repeat Step 4 until all Smarts services are stopped. Before installation 3-5

26 Installing Application Connectivity Monitor 6. Open a command prompt and determine if any Smarts Managers are running by using the brcontrol utility from BASEDIR\smarts\bin: brcontrol -b <host>:<port> 7. Stop any Smarts Manager that is still running using the dmquit utility from BASEDIR/smarts/bin: dmquit --server=<servername> 8. If the Broker is installed on the same host, use the brquit utility from BASEDIR/smarts/bin to stop it: brquit --broker=localhost:<port> 9. Press Ctrl+Alt+Delete. The Windows Security dialog box appears. 10. Click Task Manager. The Windows Task Manager appears. 11. Select the Processes tab.! CAUTION Allow up to 30 minutes before performing Step 12. Smarts Managers with large topologies can take considerable time to stop while saving the topology to the repository. Stopping processes prematurely may corrupt your repository file. 12. In the Processes tab, look in the column labeled Image Name for sm_server. For each sm_server, right-click it and then select End Process. 13. In the Processes tab, look for other Image Names that start with sm_, for example, sm_notify, sm_adapter, sm_beacon, etc. For each instance, right-click it and then select End Process. Note: Do not shutdown any sm_authority or sm_logger processes. The sm_authority and sm_logger processes are child processes of a Smarts server. The child processes will stop when the parent process stops. Choose an operating mode for the installation program Use one of the following modes supported by the installation program: Wizard mode is a Java-based Graphical User Interface (GUI). 3-6 EMC Smarts Application Connectivity Monitor Installation Guide

27 Installing Application Connectivity Monitor Command Line Interface (CLI) mode (UNIX only) is a text-based method intended to support systems with non-graphics consoles. Unattended (Silent) mode reads the selections and settings for the installation from a user-modifiable file, which enables users to easily duplicate the installation on many computer systems. Use the following decision tree to choose the appropriate mode for the installation program. Start Will the deployment require multiple installations? Yes Use Unattended (Silent) mode No What is the operating system? Windows Use the Wizard mode UNIX Are all of these available? X Windows display Fixed ports for communication through firewalls Special access to production systems No Yes to all Use any mode: Wizard mode is recommended Use CLI mode (recommended) or Unattended (Silent) mode Figure 3-1 Choose an operating mode for the installation program Before installation 3-7

28 Installing Application Connectivity Monitor Note: On UNIX systems, Wizard mode uses the X Window System to display the installation wizard. The host on which you install the EMC Smarts software and the host where you log on must be configured to run the X Windows System. Before starting the installation program using the Wizard mode, verify that the X Window System is running. 3-8 EMC Smarts Application Connectivity Monitor Installation Guide

29 Installing Application Connectivity Monitor Install EMC Smarts Application Connectivity Monitor This section describes how to install EMC Smarts Application Connectivity Monitor 2.2 into a new directory structure. Note: On the Windows 2003 (Enterprise Edition) platforms, EMC Smarts products do not install properly and EMC Smarts services do not start properly when installed to a directory path containing spaces. Therefore, the directory names used in BASEDIR cannot contain spaces. Mounting the CD-ROM UNIX Mount the CD-ROM and change to the CD-ROM directory using established procedures for your environment. The procedure for mounting the CD-ROM differs based on the operating system. If necessary, see Appendix B for typical commands and examples. Inserting the CD-ROM 1. Insert the CD-ROM into the CD-ROM drive. If autoplay is enabled, the installation program starts automatically using the Wizard mode. 2. If necessary, change the directory to the CD-ROM. Use Windows Explorer to access the CD-ROM drive and locate the /suite directory. Performing the installation To perform the installation, use the procedure for the installation program mode that you selected: For Wizard mode, go to Using wizard mode on page For CLI mode, go to Using CLI-Mode on page For Unattended (Silent) mode, go to Using unattended (silent) mode on page Install EMC Smarts Application Connectivity Monitor 3-9

30 Installing Application Connectivity Monitor Using wizard mode The text below provides detailed information on using the Wizard mode to install Application Connectivity Monitor to a Windows or Unix operating system. Satisfy wizard mode requirements (UNIX Only) On UNIX systems, wizard mode uses the X Window System to display the installation wizard. The host on which you install the EMC Smarts software and the host where you log on must be configured to run the X Window System. Before starting the installation program using the wizard mode, verify that the X Window System is running. Running wizard mode! 1. Execute the Setup command from Table 3-2 on page The InstallShield wizard dialog box displays and closes. The Shutdown Programs dialog box and the Welcome screen then display. IMPORTANT When you insert the installation CD, there may be a delay of several minutes between the InstallShield preparation screen and the EMC Smarts splash screen/installation dialogs. During this time, the java.exe process is running. Please be patient. Do not eject/reinsert the CD to start a second install process. Table 3-2 Setup command syntax for wizard-mode Operating system Solaris Linux Windows Execute: #./setup-acm-2_2_0_0-solaris.bin #./setup-acm-2_2_0_0-linux.bin setup-acm-2_2_0_0-win.exe If the installation program cannot find a suitable JVM (Java Virtual Machine), use the option -is:javahome <local_java_dir> to specify the path to where Java is installed. For example, <local_java_dir> can be: Windows: C:\Program Files\Java\j2re1.5 UNIX: /opt/java/j2re EMC Smarts Application Connectivity Monitor Installation Guide

31 Installing Application Connectivity Monitor 2. If you have not already done so, find and stop the active EMC Smarts services. For installations or uninstallations, do not stop the EMC Smarts service daemon process, sm_serviced. However, when adding additional products to an existing installation, you must stop sm_serviced. Click OK in the Warning dialog box when you have stopped all EMC Smarts services. 3. Click Next in the Welcome screen to continue. Next is disabled if: You do not have administrative privileges for the products you are attempting to install. An error message also displays. Your system failed the requirements check. If this occurs, review the check results by clicking Get System Information. Then, cancel the installation setup program, and upgrade your system. 4. Read and accept the EMC Corporation end user license agreement and click Next. 5. If the installation program detects an existing installation of the same suite, the Installation Type screen displays. Select Install the product to a new directory. Note: This screen does not display if you are installing the suite for the first time on the system. 6. Click Next to accept the default installation directory or type your preferred directory and click Next. The default installation directory is /opt/incharge7 (on UNIX) or C:\InCharge7 (on Windows). If you specify a directory, be sure to use forward slashes ( / ) for both UNIX and Windows directories. If the specified directory does not exist, it will be created. If you do not have write privileges, an error message displays. Note: On the Windows 2003 (Enterprise Edition) platform, EMC Smarts products do not install properly and EMC Smarts services do not start properly when installed to a directory path containing spaces. Therefore, the directory names used in BASEDIR cannot contain spaces. 7. In the Setup screen, select one of the options, then click Next: Complete to install the entire suite. Install EMC Smarts Application Connectivity Monitor 3-11

32 Installing Application Connectivity Monitor Custom to install a specific product. In the Product Selection screen that follows afterwards, deselect products that you do not wish to install (by default, all products are selected). Click Next. 8. If you selected Complete or Custom in Step 7, select the type of Global Console installation. You can select the Global Console or the Global Console, Web Console, and Business Dashboard. 9. The Services Selection screen displays. Select the products that you wish to install as services and click Next. If a product is not selectable (displays as gray text), click Back to return to the Product Selection screen and select the product. Note: When installed as services, EMC Smarts products run when the system is running. If the system is stopped and restarted, the EMC Smarts products restart automatically. EMC Corporation recommends that EMC Smarts products be installed as services whenever possible. If any of the products being installed can be started as services, these products are displayed in the services selection screen. 10. Choose a location to install an EMC Smarts Broker or specify the location of an existing broker. Click Next to continue. 11. If you are installing the Perl API, read and accept the EMC Corporation Perl API license agreement and click Next. 12. Review the list of products that will be installed and the target installation directory. At the bottom of the list, the total amount of disk space required for the selected products is provided so that you can verify that adequate disk space is available. To install the products, click Next. Note: A screen will display for a short period of time, letting you know that a runtime patch is being installed. This requires no user intervention and will only take a few seconds. 13. The Installation Progress screen is displayed. 14. Upon completion, the Installation Summary displays informational messages such as successful confirmations, error messages, and warnings. Click Finish to exit the installation. It is not necessary to restart the system after installation EMC Smarts Application Connectivity Monitor Installation Guide

33 Installing Application Connectivity Monitor Investigate any errors or warnings. The log file is a text file with the naming convention Install.<suite>.<productversionNumber>.log. It is located in the BASEDIR/smarts/setup/logs directory. If the installation process fails, the log files are located in the /tmp directory. 15. Remove the CD-ROM after completing the installation. Be sure that no processes are currently accessing the drive. Where to go next For all other post-installation steps, see Verifying the Installation on page 5-1. Using CLI-Mode CLI mode installation is the text-based method of executing the Installation program. This mode is intended for UNIX platforms with non-graphics consoles. The CLI mode follows the same process as the wizard mode but uses text rather than graphics. Running CLI mode Table 3-3 To start the CLI mode, execute the Setup command with the -console option as shown in Table 3-3 on page The setup command syntax for CLI-mode Operating system Solaris Linux Executable #./setup-acm-2_2_0_0-solaris.bin -console #./setup-acm-2_2_0_0-linux.bin -console If the installation program cannot find a suitable JVM (Java Virtual Machine), use the option -is:javahome <local_java_dir> to indicate the path to the Java home directory. For example, <local_java_dir> can be /opt/java/j2re1.5 User selections and navigation in CLI mode During the installation and uninstallation processes, you are prompted with a series of steps and menus: For prompts, accept the default value or select another choice. The default values are indicated in brackets. To accept the default value, press Enter. To reply yes, enter y or Y; to reply no, enter n or N. Do not press Delete; this causes the process to terminate with an error message. Install EMC Smarts Application Connectivity Monitor 3-13

34 Installing Application Connectivity Monitor For selections in menus, accept the default selections or type the number of the item and press Enter. The default values are indicated in brackets or as pre-defined selections in menus. An X is used to indicate the selected item. When you are finished making selections, type zero (0) and press Enter. If you incorrectly type an entry, press 4 to repeat the prompt and select the correct value. Arrow keys and the Backspace key are not supported. To navigate between each step, use the keys listed in Table 3-4 on page Table 3-4 Navigation keys Key Operation 1 Next, continue to the next step 2 Previous, go back to the previous step 3 Cancel, terminate the program 4 Redisplay, repeat the step 0 Accept the marked ([X]} menu choice Where to go next For the post-installation steps, see Verifying the Installation on page 5-1. Using unattended (silent) mode Unattended mode reads the commands and settings from a user-modifiable file that you create prior to beginning the process. Manual intervention is not necessary after you execute the setup command. Modifying the response file Each suite has a response file located on the CD-ROM in the utils directory. Its naming convention is <suite>-response.txt. The response file provides instructions and examples of command line options that are passed to the program in unattended mode. The command line options are organized by process flow. The process flow is almost identical to that of the Wizard mode EMC Smarts Application Connectivity Monitor Installation Guide

35 Installing Application Connectivity Monitor By default, the response file includes settings that support the installation of all products from the CD-ROM and configure the Broker location as localhost at port 426. You must edit the response file to change any of these settings: for example, to support Windows operating systems or specify a different Broker location For unattended operation, modify a response file: 1. Copy the response file from the CD-ROM /utils directory to a directory on your system, for example, the /tmp directory. 2. Using any editor, modify the values for the command line options in the response file: Specify the target directory. Select a directory for the process log file. Select the products to install. Ensure that the property value for the product is set to true. Select the products to start as services. Ensure that the property value for the product is set to true. Specify the location of the Broker. 3. Save the file. Running unattended mode Execute the Setup command from a command-line shell using the syntax in Table 3-5 on page Table 3-5 Operating system Solaris Linux Windows The Setup command syntax for unattended mode Executable #./setup-acm-2_2_0_0-solaris.bin -options <path>/<suite>-response.txt #./setup-acm-2_2_0_0-linux.bin -options <path>/<suite>-response.txt setup-acm-2_2_0_0-win.exe -options <path>\<suite>-response.txt Where: <path> is the fully qualified path to the response file and <suite> is the product suite, for example, NPM, IP, MPLS, or SAM. If the installation program cannot find a suitable JVM (Java Virtual Machine), use the option -is:javahome <local_java_dir> to indicate the path to the Java home directory. For example, <local_java_dir> can be: Windows: C:\Program Files\Java\j2re1.5 UNIX: /opt/java/j2re1.5 Install EMC Smarts Application Connectivity Monitor 3-15

36 Installing Application Connectivity Monitor For example, to start the unattended installation on Solaris for the EMC Smarts Application Connectivity Monitor when the response file is located in /opt/home, execute: #./setup-solaris.bin -options /opt/home/acm-response.txt Note: Indicates that this command must be typed as one line. Separate each option with a space when typing the command. Where to go next For post-installation steps, see Verifying the Installation on page EMC Smarts Application Connectivity Monitor Installation Guide

37 4 Uninstalling Application Connectivity Monitor This chapter describes uninstalling Application Connectivity Monitor and includes the following information: Before uninstallation Uninstall Application Connectivity Monitor Note: After uninstalling Application Connectivity Monitor, your customized files remain saved in the BASEDIR/smarts/local directory. WARNING For UNIX only, when uninstalling EMC Smarts suites from the same server, the EMC Smarts suite that was installed first must be uninstalled last. During the installation of the first EMC Smarts suite, the EMC Smarts Service Database is also installed and the other suites subsequently access it. Uninstalling the suite installed first will also uninstall the Service Database which will disable the sm_service command for those products, prevent their proper operation and uninstallation, and interrupt products running as services. Perform this check by looking at the value of the SMHOME variable in /etc/init.d/ic-serviced (or /sbin/init.d/ic-serviced for HP-UX). The suite listed in SMHOME is the suite that should be uninstalled last. Uninstalling Application Connectivity Monitor 4-1

38 Uninstalling Application Connectivity Monitor WARNING EMC Smarts product suites use standard installation software to install and uninstall product suites. You must use the uninstaller command for UNIX. For Windows, you must use the Add/Remove Programs to uninstall EMC Smarts software. Failure to use the appropriate method will result in an unstable system and/or inconsistent product directories. Do not manually delete the installed product directories. The uninstall process is not a rollback! It removes all product suite files, not simply files that changed as a result of a new product installation. If you need a full rollback procedure, contact EMC Smarts technical support. WARNING If you install additional services manually by selecting Custom from the Installation Type screen, you can only uninstall those services manually. They do not uninstall when you perform a standard uninstallation. 4-2 EMC Smarts Application Connectivity Monitor Installation Guide

39 Uninstalling Application Connectivity Monitor Before uninstallation The following section covers the preparation for the uninstallation process and includes the following topics: Detect and stop EMC Smarts programs on page 4-3 Stopping active EMC Smarts programs (UNIX) on page 4-4 Stopping active EMC Smarts programs (Windows) on page 4-5 Uninstall the FLEXnet License Server on page 4-6 Detect and stop EMC Smarts programs Before installing or uninstalling your suite, you must stop all EMC Smarts services, EMC Smarts scheduled jobs, and any other process that uses programs or libraries in any EMC Smarts installation area. On UNIX systems, this also includes the Smarts service daemon process, sm_serviced. WARNING When you install a Service Pack or Hot Fix, all Smarts product suites on the same host must be show down. If the Broker is no the host, it too must be shut down. This will prevent Smarts applications from starting and new connections from being established while the Broker is down. Inform any users who may be affected and, if necessary, schedule the installation or uninstallation for a period of low utilizaiton. Detecting EMC Smarts programs The sm_plist utility identifies all Smarts programs that are running for any product suite on your machine. You can use the sm_plist utility whenever you need to identify Smarts programs that are running (for example, before an installation or uninstallation, or applying another Service Pack or Hot Fix). To use the utility, invoke it from the BASEDIR/smarts/script directory. The utility displays active programs in a window: 1. Go to the BASEDIR/smarts/script directory. 2. Start the sm_plist utility: For UNIX, enter Before uninstallation 4-3

40 Uninstalling Application Connectivity Monitor #./sm_plist.sh BASEDIR2 For Windows, enter cscript sm_plist.vbs BASEDIR2 where BASEDIR is the directory where the sm_plist utility is installed and BASEDIR2 represents the location of any EMC Smarts product suite. Stopping active EMC Smarts programs (UNIX) 1. Stop active EMC Smarts services using the sm_service utility from BASEDIR/smarts/bin: #./sm_service stop --all Note: sm_serviced waits 30 minutes after sending a shutdown request to a process. If the process is still running after 30 minutes, sm_serviced terminates it. 2. Determine if any EMC Smarts services are still running by using the brcontrol utility from BASEDIR/smarts/bin: #./brcontrol -b <host>:<port> Based on the location of the Broker, go to the appropriate step, as indicated in Table 4-1. Table 4-1 Next steps for detecting and stopping programs The Broker is on the And this displays Do this Same host Different host Error attaching to Broker message List of servers registered with the Broker List of servers registered with the Broker The EMC Smarts Broker is not running. Go to Step 4. The Broker or service daemon did not shut down. If any servers are still running on the host, these did not shut down. Go to Step 3. If any servers are still running on the host where you will install the EMC Smarts software, these did not shut down. Go to Step Stop any EMC Smarts manager that is still running. If the Broker is on the host, stop the local Broker: To stop any manager that is still running, use the dmquit utility from BASEDIR/smarts/bin: 4-4 EMC Smarts Application Connectivity Monitor Installation Guide

41 Uninstalling Application Connectivity Monitor #./dmquit --server=<servername> To stop the local Broker from BASEDIR/smarts/bin: #./brquit --broker=localhost:<port> 4. Determine if any other EMC Smarts processes are still running and shut the processes down: Detect the processes using the following command: # ps -ef grep sm_ If a list is displayed, note the process ID (pid) of these active EMC Smarts processes. WARNING Do not stop or kill the EMC Smarts service daemon process, sm_serviced. Shut down these EMC Smarts processes (except sm_serviced) using the following command: # kill <pid> Stopping active EMC Smarts programs (Windows) To stop a service from the Windows desktop using the Microsoft Management Console: 1. Select Settings > Control Panel. 2. At the Control Panel, select Administrative Tools. 3. At the Administrative Tools folder, select Services. 4. At the Services window, locate any running Smarts services. These services start with the words EMC Smarts, InCharge, or Smarts. For each of these services, right-click the service and then select Stop. Note: Do not stop the Broker service. 5. Repeat Step 4 until all Smarts services are stopped. 6. Open a command prompt and determine if any Smarts Managers are running by using the brcontrol utility from BASEDIR\smarts\bin: Before uninstallation 4-5

42 Uninstalling Application Connectivity Monitor brcontrol -b <host>:<port> 7. Stop any Smarts Manager that is still running using the dmquit utility from BASEDIR/smarts/bin: dmquit --server=<servername> 8. If the Broker is installed on the same host, use the brquit utility from BASEDIR/smarts/bin to stop it: brquit --broker=localhost:<port> 9. Press Ctrl+Alt+Delete. The Windows Security dialog box appears. 10. Click Task Manager. The Windows Task Manager appears. 11. Select the Processes tab.! CAUTION Allow up to 30 minutes before performing Step 12. Smarts Managers with large topologies can take considerable time to stop while saving the topology to the repository. Stopping processes prematurely may corrupt your repository file. 12. In the Processes tab, look in the column labeled Image Name for sm_server. For each sm_server, right-click it and then select End Process. 13. In the Processes tab, look for other Image Names that start with sm_, for example, sm_notify, sm_adapter, sm_beacon, etc. For each instance, right-click it and then select End Process. Note: Do not shutdown any sm_authority or sm_logger processes. The sm_authority and sm_logger processes are child processes of a Smarts server. The child processes will stop when the parent process stops. Uninstall the FLEXnet License Server The FLEXnet License Server is used by EMC Smarts products for license management. The FLEXnet software is provided as part of any EMC Smarts software distribution. To install a FLEXnet License Server and set up permanent licenses for your EMC Smarts products, see the EMC Smarts System Administration Guide. 4-6 EMC Smarts Application Connectivity Monitor Installation Guide

43 Uninstalling Application Connectivity Monitor When uninstalling all of your EMC Smarts products and suites that use a specific FLEXnet License Server, you must also uninstall the FLEXnet License Server. Note: If any EMC Smarts products will remain in your network and use the FLEXnet License Server, do not uninstall either the license server or the EMC Smarts product suite where the permanent license file resides. If you uninstall EMC Smarts products without uninstalling the FLEXnet License Server, a message displays that the FLEXnet (lmgrd) service is still running. Keep in mind that an EMC Smarts application will not start if it is unable to contact the license server. To stop and uninstall the FLEXnet license server, perform these steps: 1. Stop the FLEXnet license server. Solaris # /etc/init.d/smarts-license stop Linux # /etc/init.d/smarts-license stop Windows To manually start the license server on Windows, do the following as administrator: Select Start > Settings > Control Panel > Administrative Tools. Select Services. Select the FLEXnet License Server service. Right-click and choose Stop. 2. Execute the install_license script with the uninstall command from the BASEDIR/smarts/script directory. UNIX # BASEDIR/smarts/script>install_license.sh uninstall Windows BASEDIR\smarts\script>install_license.cmd uninstall Before uninstallation 4-7