emc smarts solutionpack - dellemc.com · emc® smarts® solutionpack version 9.2 installation and...

EMC® Smarts® SolutionPackVersion 9.2

Installation and Configuration GuideP/N 300-999-916

REV 01

Copyright © 2013 EMC Corporation. All rights reserved. Published in the USA.

Published March, 2013

EMC believes the information in this publication is accurate as of its publication date. The information is subject to changewithout notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind withrespect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for aparticular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicablesoftware license.

EMC², EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and othercountries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com). Fordocumentation on EMC Data Domain products, go to the EMC Data Domain Support Portal (https://my.datadomain.com).

EMC CorporationHopkinton, Massachusetts 01748-91031-508-435-1000 In North America 1-866-464-7381www.EMC.com

2 EMC® Smarts® SolutionPack 9.2 Installation and Configuration Guide

7

Best Practices for Deployment 9

SolutionPack deployment scenarios..............................................................10Comparison of deployment scenarios............................................................10Comparison of classic SAM and Companion UI features................................11

System Requirements for Companion UI 13

Virtual platform requirements .......................................................................14Hardware requirements.................................................................................14Port and protocol requirements.....................................................................14Supported EMC Products...............................................................................14Browser requirements...................................................................................15Java requirements.........................................................................................16Tool requirement for Hyper-V implementation...............................................16

System Requirements for Watch4net 17

Operating system requirements for Watch4net..............................................18Browser requirements for Watch4net.............................................................18

EMC Smarts Console SolutionPack with SAM and Companion UI 19

Setup overview..............................................................................................20Product installation.......................................................................................20

Product installation files.........................................................................20Deploying an appliance..........................................................................21Starting the appliance ............................................................................23Deploying a Hyper-V virtual machine.......................................................23Checkpoint.............................................................................................25Verifying the appliance deployment .......................................................25Installing Service Assurance Manager.....................................................25Installing Service Assurance Manager Web Console................................26Installing Watch4net on a UNIX server.....................................................26Installing Watch4net on a Windows Server machine...............................27

Product licensing..........................................................................................27Configuring the license for the SAM server..............................................27Configuring the license for the Web Console server.................................28Obtaining a Watch4net license...............................................................28Watch4net licenses................................................................................29

Single sign-on configuration..........................................................................30Setting the properties for single sign-on authentication..........................30Setting up single sign-on for the Watch4net server.................................33Setting up single sign-on authentication for the SAM server....................35Replacing the authority identifier on non-SAM domain managers............36Setting up single sign-on authentication for the secondary SAM server(failover).................................................................................................36

Tables

Chapter 1

Chapter 2

Chapter 3

Chapter 4

CONTENTS

EMC® Smarts® SolutionPack 9.2 Installation and Configuration Guide 3

Setting up single sign-on authentication for the SAM Web Console server...............................................................................................................37Setting up single sign-on authentication for the Companion UI server.....38[Solaris only] Importing certificates to the Companion UI server..............39

Smarts Console SolutionPack setup with Companion UI................................40Connecting to the Watch4net server and Companion UI..........................40Configuring the Watch4net server for the first time..................................41Installing the EMC Smarts Console SolutionPack with Companion UI......41

SolutionPack software updates.....................................................................43Uninstalling a SolutionPack....................................................................43Updating SolutionPack files before installing the SolutionPack...............43Verifying the SolutionPack version number.............................................44Stopping Watch4net services on a UNIX server.......................................44Stopping Watch4net services on a Windows server.................................44Starting the Watch4net services..............................................................45

Installing the EMC Smarts Console SolutionPack with Companion UI.............45User synchronization.....................................................................................47

Setting the properties for user synchronization.......................................47Synchronizing users for first use.............................................................49Verifying setup of Smarts Console users.................................................50Checkpoint.............................................................................................50Testing single sign-on authentication.....................................................50Launching Smarts Console views with secure port..................................51

Data sources.................................................................................................52Configuring data sources .......................................................................52

EMC Smarts Console SolutionPack with SAM 57

Setup overview..............................................................................................58Installing Service Assurance Manager...........................................................58Installing Service Assurance Manager Web Console......................................58Installing Watch4net on a UNIX server...........................................................58Installing Watch4net on a Windows Server machine......................................59Obtaining a Watch4net license......................................................................59Watch4net licenses.......................................................................................60

Installing Watch4net licenses for the first time........................................60Adding or updating Watch4net licenses..................................................60Deleting Watch4net licenses...................................................................61

Starting the Watch4net services....................................................................61Connecting to the Watch4net server..............................................................61Configuring the Watch4net server for the first time........................................62Smarts Console SolutionPack setup without Companion UI...........................62

Installing the EMC Smarts Console SolutionPack without Companion UI...............................................................................................................62Launching Smarts Console views without Companion UI.........................64

SolutionPack software updates.....................................................................64Uninstalling a SolutionPack....................................................................65Updating SolutionPack files before installing the SolutionPack...............65Verifying the SolutionPack version number.............................................65Stopping Watch4net services on a UNIX server.......................................66Stopping Watch4net services on a Windows server.................................66Starting the Watch4net services..............................................................66

Installing the EMC Smarts Console SolutionPack without Companion UI........66

Uninstallation procedures 69

Chapter 5

Chapter 6

CONTENTS


Uninstalling Companion UI with vSphere client.............................................70Uninstalling Companion UI with Hyper-V Manager.........................................70Stopping Watch4net services on a UNIX server..............................................70Uninstalling Watch4net from a UNIX server....................................................70Stopping Watch4net services on a Windows server.......................................70Uninstalling Watch4net from a Windows server.............................................71Uninstalling a SolutionPack...........................................................................71

CONTENTS


CONTENTS


Comparison of features for deployment scenarios.........................................................11Comparison of classic SAM and Companion UI features.................................................11Minimum virtual platform requirements.........................................................................14Minimum virtual hardware requirements.......................................................................14Ports for communication protocols................................................................................14Interoperability chart for EMC Smarts Companion UI......................................................15Supported browsers......................................................................................................15Supported operating systems and relational database management systems................18Supported browsers......................................................................................................18Companion UI properties...............................................................................................32SAM Web Console properties.........................................................................................32Watch4net properties....................................................................................................32SAM Web Console keystore and truststore values..........................................................32Watch4net keystore and truststore values.....................................................................33

1234567891011121314

TABLES


TABLES


CHAPTER 1

Best Practices for Deployment

This chapter contains the following topics.

u SolutionPack deployment scenarios......................................................................10u Comparison of deployment scenarios....................................................................10u Comparison of classic SAM and Companion UI features........................................11

Best Practices for Deployment 9

SolutionPack deployment scenariosChoose the scenario that best matches your deployment requirements.

A SolutionPack is a component in the EMC® Watch4net® product family. A SolutionPackprovides the configuration needed to integrate and display data and reports for a giventechnology. For example, when EMC® Smarts® Console SolutionPack is installed withWatch4net, you can browse EMC Smarts Service Assurance Manager (SAM), SAM WebConsole, and Companion UI views in Watch4net.

The user interface for the Smarts products has been enhanced such that you have morechoices for viewing the notifications and network activity monitored by the domainmanagers. You may choose from the following deployment scenarios:

1. Service Assurance Manager (SAM) with both Companion UI and Watch4net views.

2. SAM consoles displayed inside a Watch4net outer frame.

3. Classic SAM console views.

Option 1 requires installation and configuration of Watch4net (including EMC SmartsConsole SolutionPack), SAM Web Console and a SAM server. Install the Companion UI asa virtual appliance in a VMware or Hyper-V environment. This option provides single sign-on capability. Use of an LDAP server is recommended.

Option 2 requires installation and configuration of Watch4net (including EMC SmartsConsole SolutionPack) and SAM Web Console and SAM server. This deployment optionrequires you to have separate login credentials for both SAM and Watch4net.

Option 3 provides management of the SAM server similar to earlier releases of theproduct.

The EMC Smarts Installation Guide for SAM, IP,ESM, MPLS, VoIP and NPM Managersprovides information for installing SAM and SAM Console.

Use of classic SAM console views are described in the EMC Smarts Service AssuranceManager Operator Guide and the EMC Smarts Service Assurance Manager DashboardConfiguration Guide.

The EMC Smarts SolutionPack Installation and Configuration Guide provides informationfor installing Watch4net and Companion UI and for configuring all of the componentsrequired to deploy Options 1 or 2 as an integrated solution.

Troubleshooting tips and additonal administration and user tasks are described in theEMC Smarts SolutionPack User and Administration Guide.

Within a Smarts Console workspace, you can access online help from the wrench icon thatdisplays in the banner of each view.

In the CUI Server Admin task menu, a Help icon displays in the upper right corner for eachtask.

Comparison of deployment scenariosCompare the features available for each deployment scenario.

When you configure Service Assurance Manager and Companion UI to work withWatch4net and EMC Smarts Console SolutionPack, you can obtain an integrated view ofyour network components. However, some environments may not support the use of allof these products.Use this list of features to determine which deployment scenario is right for yourbusiness.



If you implement options 1 or 2, all classic SAM features are available fromwithin Watch4net.

Table 1 Comparison of features for deployment scenarios

Feature Option1:Watch4net withSmarts ConsoleSolutionPack,SAM, SAMConsole,Companion UI

Option 2:Watch4net withSmarts ConsoleSolutionPack,SAM, SAMConsole

Option 3: ServiceAssurance Manager(Classic SAM, withoutWeb Console orWatch4net)

- - - -Virtual environmentrequired (forCompanion UI)

Yes No, Virtualenvironment is notrequired

No, Virtual environment isnot required

Single sign-on (SSO)available for usercredentials

Yes No, Maintainseparate logincredentials for SAMand Watch4net

No, Maintain separate logincredentials for SAM

Support for SmartsMobile app

Yes, Required for useof Smarts Mobileapp

No, Smarts Mobileapp not supported

No, Smarts Mobile app notsupported

Internet accessrequired

Yes Yes No

FIPS-mode No No Yes

Comparison of classic SAM and Companion UI featuresCompare the features available in classic Service Assurance Manager (SAM) withCompanion UI.

When trying to choose whether to install both Service Assurance Manager andCompanion UI, it is helpful to consider the features supported by each product.Use this list of features to determine which deployment scenario is right for yourbusiness.

Table 2 Comparison of classic SAM and Companion UI features

Feature Service Assurance Manager(classic Web Console views)

Service Assurance Managerwith Companion UI views

- - -Notification List Yes No, Uses Default notification

list only. Also cannot renamenotification columns

Role Based Access Control Yes (Profiles) No, All users see allnotifications/objects andfunctions.

Notification Log Yes Yes

Maps Yes No


Comparison of classic SAM and Companion UI features 11

Table 2 Comparison of classic SAM and Companion UI features (continued, page 2 of 2)

Feature Service Assurance Manager(classic Web Console views)

Service Assurance Managerwith Companion UI views

- - -Topology Tree Yes Partial. Limited to the

Watch4net inventory andsearch functionality. Not thefull Smarts Topology.

Server Tools Yes Yes, but no ability to filter thetools by user profile.

Client Tools Yes Yes, but no ability to filter thetools by user/profile.

CompanionUI Client Tools are separatefrom SAM Client Tools andrequire additionalconfiguration.

Group Health No Yes

Watch List No Yes

Domain Management Yes No

Domain Manager AdminConsole

Yes No

Configuration Changes View No. Yes

Audit Logs Yes Yes

Containment Yes Yes

Impact/CausedBy Yes Yes

BIM Views Yes No

Status Table Yes No

Summary View Yes No



CHAPTER 2

System Requirements for Companion UI


u Virtual platform requirements ...............................................................................14u Hardware requirements.........................................................................................14u Port and protocol requirements.............................................................................14u Supported EMC Products.......................................................................................14u Browser requirements...........................................................................................15u Java requirements.................................................................................................16u Tool requirement for Hyper-V implementation.......................................................16

System Requirements for Companion UI 13

Virtual platform requirementsThe Companion UI is an appliance that is bundled with the SUSE Linux Enterprise Server(SLES) 11 SP 2 operating system. The Companion UI must be deployed on a virtualmachine or VMware vCenter™ Server that supports Open Virtualization Format (OVF). TheCompanion UI requires the following minimum infrastructure before deployment.

Table 3 Minimum virtual platform requirements

Virtual platforms Versions- -vCenter Server/ESXi (64-bit) 4.1 or later

Microsoft Windows Server 2008 R2 or later

For a Hyper-V deployment, a valid Hyper-V license is also required.

Hardware requirementsThe Companion UI is distributed as a virtual appliance running on a server with thefollowing requirements.

Table 4 Minimum virtual hardware requirements

Item Description- -Processor 4 CPUs

Memory 16 GB

Disk space 100 GB for the virtual machine

Port and protocol requirementsThe appliance reserves specific ports for its communication protocols.

Table 5 Ports for communication protocols

Protocol Port- -Secure shell 22

http 80

https 443

Supported EMC ProductsThe Companion UI appliance runs on a platform that supports all EMC products offeringan EMC Data Access API (EDAA) interface.

Product and release compatibilityThe Companion UI is compatible with the versions of the following products.



Table 6 Interoperability chart for EMC Smarts Companion UI

Product Version Notes- - -EMC Smarts Service Assurance Manager 9.2 Refer to the EMC Smarts Installation

Guide for SAM, IP, ESM, MPLS, VoIP, andNPM Managers for interoperabilityinformation about underlying DomainManagers.

EMC Smarts Global Console, BusinessDashboard, and Web Console

9.2 Available for download as SAM Console.Only Business Dashboard and WebConsole are used in EMC Watch4net.

EMC Smarts Business Impact Manager 9.2 For Maintenance and Business ImpactManager Server.

EMC Smarts Network ConfigurationManager (NCM)

9.2

EMC Watch4net 6.2 Includes EMC Smarts ConsoleSolutionPack. Check EMC OnlineSupport for the latest updates of the 6.2EMC Watch4net product.

The Smarts Foundation EMC Data Access API (EDAA) Programmer Guideprovides information about the EDAA interface.

Browser requirementsBrowsers enable you to interact with the appliance.

All browsers must:u Accept cookies.

u Have pop-up blockers disabled.

u Have Adobe Flash Player (version 11 or higher) installed.

Table 7 Supported browsers

Browser Version Operatingsystem

Notes

- - - -Google Chrome 21 or

higherWindows None

Windows InternetExplorer

8 Windows Compatibility mode must be Off

Windows InternetExplorer

9 Windows Compatibility mode must be On

Mozilla Firefox 15 orhigher

Windows l Enable cookies and pop-ups.

l Disable all Add-ons.

l Enable JavaScript.


Browser requirements 15

Table 7 Supported browsers (continued, page 2 of 2)


Notes

- - - -Apple Safari 6 Mac OS X

and iOSNone

Security certificatesTo avoid security certificate errors, install digitally-signed certificates.

Java requirementsIf you are going to deploy Companion UI on a Hyper-V machine, Java JRE 1.6.0_37 orhigher is required.

Tool requirement for Hyper-V implementationYou need a specific tool for file extraction during the procedure to deploy Companion UIon a Hyper-V machine.

The 7-Zip file archiver from www.7-zip.org needs to be downloaded and installed.



http://www.7-zip.org

CHAPTER 3

System Requirements for Watch4net


u Operating system requirements for Watch4net......................................................18u Browser requirements for Watch4net.....................................................................18

System Requirements for Watch4net 17

Operating system requirements for Watch4netEMC® Watch4net® supports these operating systems and relational databasemanagement systems.

You can run Watch4net on a 32-bit system (for evaluation purposes) but a 64-bit systemis recommended for production. Watch4net must use Oracle 10.0 Enterprise Edition orlater. Watch4net ships with MySQL 5.5. Existing customers may continue to use MySQL5.0 in their Watch4net installations.

Table 8 Supported operating systems and relational database management systems

Operating system MySQL Oracle Watch4netdatastore

- - - -Sun Solaris 10 x86_64 X X X

Sun Solaris 10 SPARC X X

Linux RHEL 5 64 bit X X X

Linux RHEL 6 64 bit X X X

Linux CentOS 5 64 bit X X X

Linux CentOS 6 64 bit X X X

Linux SUSE Enterprise 11 64 bit X X X

Microsoft Windows 2008 64 bit X X X

Microsoft Windows 2012 64 bit X X X

Browser requirements for Watch4netYou can use any workstation to manage your Watch4net application and view reports.Watch4net is compatible with these web browsers.

Table 9 Supported browsers


Notes

- - - -Google Chrome Latest Windows, Linux Full support

Internet Explorer 6 and 7 Windows Browse mode only

Internet Explorer 8, 9, and 10 Windows Full support

Mozilla Firefox Latest Windows, Linux Full support

Apple Safari Latest Mac OS X and iOS Full support

Apple iPhone and iPad Latest Mac iOS Using APG iPhone/iPadclient from AppStore

System Requirements for Watch4net


CHAPTER 4

EMC Smarts Console SolutionPack with SAM andCompanion UI

This chapter contains the following sections.

u Setup overview......................................................................................................20u Product installation...............................................................................................20u Product licensing..................................................................................................27u Single sign-on configuration..................................................................................30u Smarts Console SolutionPack setup with Companion UI........................................40u SolutionPack software updates.............................................................................43u Installing the EMC Smarts Console SolutionPack with Companion UI.....................45u User synchronization.............................................................................................47u Data sources.........................................................................................................52

EMC Smarts Console SolutionPack with SAM and Companion UI 19

Setup overviewUse Watch4net and the EMC Smarts Console SolutionPack to display views of data fromService Assurance Manager (SAM), SAM Web Console, and Companion UI. This setuprequires installing each product, configuring the product licenses, setting single sign-onauthentication for each product host, installing the SolutionPack, synchronizing usersacross products, and configuring the data sources used by the products.

When setting up this SolutionPack, you must follow the installation and configurationprocedures in the order presented in these sections.u Product installation on page 20

u Product licensing on page 27

u Single sign-on configuration on page 30

u Smarts Console SolutionPack setup with Companion UI on page 40

u User synchronization on page 47

u Data sources on page 52

Product installationFollow the procedures in this section to deploy the Companion UI and install SAM, SAMWeb Console, and Watch4net.

You may deploy the appliance either using VMware or Hyper-V machines.

u Deploying an appliance on page 21

u Starting the appliance on page 23

u Deploying a Hyper-V virtual machine on page 23

u Checkpoint on page 25

u Verifying the appliance deployment on page 25

u Installing Service Assurance Manager on page 25

u Installing Service Assurance Manager Web Console on page 26

u Installing Watch4net on a UNIX server on page 26

u Installing Watch4net on a Windows Server machine on page 27

Product installation filesObtain installation files for SAM, SAM Web Console, Watch4net, and Companion UI fromthe Service Assurance Manager > Downloads link in the EMC Online Support website orfrom the media kit that ships with each product.

Companion UI installation filesYou may deploy Companion UI using either VMware vSphere Client or Microsoft Hyper-VManager. The installation files are usually compressed to speed up the downloadprocess. After you download and unzip the compressed files, the following componentsare available for use in deployment:

Files Used for- -.ovf and .vmdk files Deploying Companion UI virtual appliance with

VMware vSphere Client.

EMC Smarts Console SolutionPack with SAM and Companion UI


Files Used for- -

The .vmdk file is split intoseveral separate files on the supportwebsite to facilitate the download process.The .ovf file is included in the first .vmdkfile. There is only one .vmdk file in theCompanion UI media kit.

.ovf, .jar, .vhd files Deploying Companion UI virtual appliance withHyper-V Manager

configSSO folder with scripts such asconfigSSO.sh for UNIX and configSSO.bat forWindows and configSSO.conf properties file

Configuring single sign-on authentication for allproducts integrated with the Smarts ConsoleSolutionPack

Use Secure Copy (SCP) or ftpto move the configSSO folder to the /opt/emc/apps folder.

Deploying an applianceYou can deploy an appliance from an OVF file using a vSphere client.

You need this information to complete this procedure:u vCenter location where you are deploying the appliance

u Datastore you can use for deployment

u Static IP address to assign to your appliance

u Gateway

u Netmask

u DNS servers

1. Open vSphere Client and connect to the vCenter Server managing your VMwareenvironment.

2. From the File menu, select Deploy OVF Template.

3. In the Source step, browse to the location of the YourOVFfile.ovf file.

Example file path: /opt/ovf/YourOVFfile_OVFxx.ovfExample URL: http://myHost.emc.com/ovf/snapshot/92/YourOVFfile_OVFxx.ovf

4. Click Next.

To minimize deployment time, deploy the appliance from within the same local areanetwork (LAN) shared by your VMware ESX/ESXi servers. Deployment time shouldtake approximately 5 to 15 minutes. Deployment across a WAN could take 2 hours ormore.

5. In the OVF Template Details step, review the details of the loaded .ovf file and clickNext.

6. In the End User License Agreement step, review the End User License Agreement. ClickAccept and then Next to continue.


Deploying an appliance 21

7. In the Name and Location step:a. Type a Name for the appliance.

b. Specify an Inventory Location for the appliance within your VMwareenvironment.

c. Click Next.

8. In the Host/Cluster step, select a host or cluster where the appliance will run and clickNext.

9. In the Resource Pool step, select a resource pool associated with the host or clusterwhere the appliance will run and click Next.

This step is only necessary if a resource pool has been predefined.

10. In the Datastore step, select a datastore to hold the appliance images and click Next.

11. In the Disk Format step, select the storage space provisioning method and click Next.

Option Description

Thin provisioned format On-demand expansion of available storage, used fornewer datastore file systems

Thick provisioned format Appliance storage that is allocated immediately andreserved as a block

The Thin provisioned format option is recommended unless you are in ahigh performance environment.

12. In the Network Mapping step, select a destination network that has an IP Poolassociated with it and click Next.

13. In the Properties step:a. Set Appliance Fully Qualified Hostname to the fully qualified host name of the

appliance, such as myHost.emc.com.

You cannot change the hostname of the appliance after deployment. If you haveto change the hostname, EMC recommends that you delete the appliance andredeploy it with the new hostname. If you need to change the hostname for alonger-running appliance, the preferred method is to set up an alias in yourdomain name server (DNS) to resolve the appliance hostname.

b. Set Appliance IP Address to a static IP address for the appliance.

To change the IP address of the appliance after deployment, EMC recommendsthat you re-deploy the appliance.

c. Set Gateway IP Address to the gateway IP address for hosts in the network.

d. Set Netmask to the netmask applied to IP addresses in the network.

e. Set DNS Server(s) to a comma-separated list of domain name servers (DNS)available in the network. For example, 192.168.0.1, 192.168.0.2.

You must independently register the hostname for your appliance with yourdomain name servers (DNS). The appliance does not validate hostnames.Hostnames not registered with the corresponding DNS may prevent normaloperation.

f. (Optional) Set Search Domain(s) to a space-separated list of domains used in thenetwork. For example, emc.com myhostname.emc.com.



g. (Optional) Set Name or IP Address of NTP (time) server to the name or IP address of anNTP server to use for synchronizing the appliance date and time. For example,pool.ntp.org.

h. Set Timezone to the timezone of the appliance. For example, US/Eastern.

i. Click Next.

14. In the Ready to Complete step, review the list of properties for the appliance and clickFinish.A status bar is displayed in the vSphere Client, showing the deployment progress.

15. After deployment is complete, click Close in the Deployment Completed Successfullydialog box.

Starting the applianceUsing vSphere, you start the appliance after deployment.

1. In the vSphere Client, right-click the appliance name.

2. Select Power > Power On.The status displays in the Recent Tasks bar. The appliance may take up to 20 minutesto start the first time. You can monitor the progress on the vSphere console.

Deploying a Hyper-V virtual machineYou can deploy a virtual machine that includes the appliance by using .vhd, .ovf, .jar, .zipfiles, and Microsoft Hyper-V Manager.

You need this information to complete this procedure:u An administrator login with root privileges for the Windows 2008 R2 Server to create a

virtual machine.

u 7-Zip file archiver from www.7-zip.org, downloaded and installed.

u Static IP address to assign to your virtual machine if you are not going to use DynamicHost Configuration Protocol (DHCP)

u Gateway

u Netmask

u DNS servers

u Search Domains, a space-separated list of domains used in the network

After downloading and extracting files, specify Application and Networking propertiesusing the HyperV_Configuration.jar and SmartsUI-9.2.ovf files. Save theproperties to a .iso file. Then, using Hyper-V Manager and SmartsUI-9.2.vhd, deploy avirtual machine. Power on the virtual machine. When you mount the .iso file to the virtualmachine and start the appliance, the properties take effect.

If using the DVD to obtain installation files, there are three files available for use in Hyper-V deployment:u HyperV_Configuration.jaru SmartsUI-9.2.ovfu SmartsUI-9.2.zipIf you obtain the software from EMC Online Support website, you must first download andunzip SMARTS_CUI_V9200_HV.zip to extract these files.

1. Unzip or copy the files to the folder on the Microsoft 2008 R2 server where you wantto deploy the virtual machine. For example: C:\My Documents\Virtual Machine.


Starting the appliance 23

http://www.7-zip.org

2. Use 7-Zip to unzip files used in the Hyper-V deployment.a. Open 7-Zip.

b. If you downloaded SMARTS_CUI_V9200_HV.zip, unzip it first to obtain the threefiles.

c. Right-click the zip file and select 7Zip > Extract here.

Wait for the extraction to complete.

d. Right-click SmartsUI-9.2.zip and select Extract here.

Another new file, SmartsUI-9.2.vhd, appears in the folder.

3. Double-click the HyperV_Configuration.jar file to open the Ovf DeploymentProperty Editor.

4. In the Ovf Deployment Property Editor, from the File > Open menu, selectSmartsUI-9.2.ovf and edit the properties that will be needed by the virtualmachine.

In the menu, use arrow keys, the spacebar, and Enter or OK to select each setting andto complete the required fields.

a. Set Appliance Fully Qualified Hostname to the fully qualified host name of themachine, such asmyHost.emc.com.

You cannot change the hostname of the virtual machine after deployment. If youhave to change the hostname, EMC recommends that you delete the virtualmachine and re-deploy it with the new hostname. If you need to change thehostname for a longer-running virtual machine, the preferred method is to set upan alias in your domain name server (DNS) to resolve the hostname.

b. (Optional) Set Search Domain(s) to a space-separated list of domains used in thenetwork. For example, emc.com myhostname.emc.com.

c. (Optional) Set Name or IP Address of NTP (time) server to the name or IP address of anNTP server to use for synchronizing the date and time. For example,pool.ntp.org.

d. Set Timezone to the timezone of the virtual machine. For example, US/Eastern.

e. Set Default Gateway to the gateway IP address for hosts in the network.

f. Set DNS Server(s) to a comma-separated list of domain name servers (DNS)available in the network. For example, 192.168.0.1, 192.168.0.2.

You must independently register the hostname for your virtual machine with yourDNS. The virtual machine does not validate hostnames. Hostnames not registeredwith the corresponding DNS may prevent normal operation.

g. Set Network 1 IP Address to a static IP address for the virtual machine.

To change the IP address of the virtual machine after deployment, EMCrecommends that you re-deploy the virtual machine.

h. Set Network 1 Netmask to the netmask applied to IP addresses in the network.

5. Click ISO and save the file with the default name, ovf-env.iso, in the same folder asthe SmartsUI-9.2.vhd file.

6. Close the Ovf Deployment Property Editor.

7. Open Windows Server Manager.

8. Select Server Manager > Roles > Hyper-V > Hyper-V Manager > server Host name.

9. Select New > Virtual Machine and follow the prompts to create the new virtual machine.a. Type a name for the virtual machine. Click Next.

b. Type a memory size (16 GB is recommended). Click Next.



c. Assign a network connection. (The Local Area Connection will share the networkwith the Hyper-V server.) Click Next.

d. Select Use an existing virtual hard disk.

e. Click Browse and select the SmartsUI-9.2.vhd. Click Finish.

10. From Hyper-V Manager, right-click the new virtual machine in the Virtual Machines listand select Connect.

11. Mount ovf-env.iso to the virtual machine.a. Select Media > DVD Drive > Insert Disk and select ovf-env.iso.

12. Select Action > Start.

CheckpointCheck your progress using the following procedure(s).

Verifying the appliance deploymentAfter deploying the appliance, verify the properties and the network connectivity.

1. To verify VMware properties, navigate to VMs and Templates in vSphere client.

2. Expand the tree in the left panel and find the resource pool you selected for theappliance. The new appliance is listed under the resource pool.

3. To verify Hyper-V properties, review the values in the iso file that you generated as aresult of editing SmartsUI-9.2.ovf.

4. To confirm network configuration settings for either VMware or Hyper-V deployments,ssh into the appliance with the root credentials for the virtual machine (for example,using PuTTy, log in with root/password).

5. Verify that the values for hostname, /etc/resolv.conf, /etc/hosts, and ifconfigcorrectly reflect the settings specified during appliance deployment.

Installing Service Assurance ManagerInstall Service Assurance Manager (SAM) using the default installation paths.

1. Install Service Assurance Manager as described in the EMC Smarts Installation Guidefor SAM, IP, ESM, MPLS, VoIP, and NPM Managers.

2. If you changed the default installation path, for example opt/InCharge/SAM/smarts, record the path for use in other procedures.

Starting the Service Assurance Manager BrokerStart the Service Assurance Manager (SAM) Broker to allow cross-domain integration withWatch4net.

1. Start the Broker from the Service Assurance Manager (SAM) directory. For example:

./opt/InCharge/SAM/smarts/bin/brstart

Other command line options include:--port=426--output--restore=BASEDIR/smarts/local/repos/broker/broker.rps


Checkpoint 25

2. Record the name of the Broker and the port number for use in configuring the EMCSmarts Console SolutionPack.

Installing Service Assurance Manager Web ConsoleInstall the Service Assurance Manager (SAM) Web Console for integration withWatch4net.

1. Install Service Assurance Manager (SAM) Web Console as described in the EMCSmarts Installation Guide for SAM, IP, ESM, MPLS, VoIP, and NPM Managers.

2. If you changed the default installation path, for example opt/InCharge/CONSOLE/smarts, record the path for use in other procedures.

Installing Watch4net on a UNIX serverYou can install Watch4net on a UNIX server.

You need this information to complete this procedure:u A login with administrative privileges.

u The Watch4net installation package that you downloaded from EMC to a directory,such as /temp.

u Prior to starting Watch4net services, ensure the library search path is correct on theserver that hosts Watch4net. This requirement applies to "libstd" on Solaris and"libaio" on Linux.

1. Locate your installation package in your directory.

2. Change the permissions of the Watch4net installer so you can execute it. Forexample, for the Watch4net 6.2 Linux 64-bit executable, type:# chmod +x setup-linux-x86_64-v62.sh

3. Execute the installer from your directory:./setup-linux-x86_64-v62.sh

4. Read and accept the End User License Agreement. Use the space bar to scroll throughthe agreement. Press y to accept it.

5. Press Enter to accept the default installation directory (/opt/APG). Or, enter anotherlocation and press y.

6. Press Enter to accept the default user account name (apg) or enter another name.

7. Press Enter to accept the default location of service scripts (/etc/init.d) or enteranother location.

8. Press Enter to accept the default base directory (/etc) of runlevels scripts or enteranother location.

9. Press Enter to accept the default installation (recommended).

If you type m, only the Module Manager and Java will install. Then, you will have tomanually install other desired modules. Consult the Module Manager documentation,located in /opt/APG/Doc/APG-Module-Manager.pdf, for instructions aboutmanual module installation.

Ignore any yellow warning about a load balancer being configured asan arbiter.

You should see the message:Installation Complete!



10. For more information, read the Watch4net ReadMe.

Installing Watch4net on a Windows Server machineYou can install Watch4net on a Windows Server 2008 R2 (or later) machine.


u The Watch4net installation package that you downloaded from EMC to a directory,such as \temp.


2. Double-click the installer to execute it:setup-win64-v62.exe

3. Click Next in the Welcome screen.

4. Read and accept the End User License Agreement. Press I Agree.

5. Press Next to accept the default installation directory (C:\Program Files\APG). Or,browse to another directory and press OK.

6. Click Install to install the default modules (recommended).

If you clear the Recommended Modules checkbox, only the Module Manager and Javawill install. Then, you will have to manually install other desired modules. Consult theModule Manager documentation, located in C:\Program Files\APG\Doc\APG-Module-Manager.pdf.

7. Upon completion, click Next.


8. Click Finish to close the installer and to read the Watch4net Readme.

Product licensingFollow the procedures in this section to configure the product licensing for SAM, SAMWeb Console, and Watch4net.

u Configuring the license for the SAM server on page 27

u Configuring the license for the Web Console server on page 28

u Obtaining a Watch4net license on page 28

u Watch4net licenses on page 29

Configuring the license for the SAM serverA valid software license is required to start the SAM server.

Install Service Assurance Manager as described in the EMC Smarts Installation Guide forSAM, IP, ESM, MPLS, VoIP, and NPM Managers.

1. Copy the license file to BASEDIR/smarts/local/conf directory on the host systemwhere you installed the EMC Smarts software. For example, /opt/InCharge/SAM/smarts/local/conf.

2. Edit the SM_LICENSE variable in the runcmd_env.sh file on each host where EMCSmarts software is installed to specify the full path and file name of a single licensefile. When multiple products are installed on the same host, each product will include


Installing Watch4net on a Windows Server machine 27

a runcmd_env.sh in its BASEDIR/smarts/local/conf directory. Ensure that the nameand extension of the license file in the SM_LICENSE variable definition match thename and extension of the license file or point to the license server.

3. For example, based on your operating system and license name, add one of thefollowing lines to the runcmd_env.sh file.

Operating system Authority identifier for SSO

UNIX SM_LICENSE=/opt/InCharge/SAM/smarts/local/conf/smarts.lic

Microsoft Windows SM_LICENSE=C:\InCharge\SAM\smarts\local\conf\smarts.lic

Configuring the license for the Web Console serverA valid software license is required to start the Web Console.

Install Service Assurance Manager Web Console as described in the EMC SmartsInstallation Guide for SAM, IP, ESM, MPLS, VoIP, and NPM Managers.

1. Copy the license file to BASEDIR/smarts/local/conf directory on the host systemwhere you installed the EMC Smarts software. For example, /opt/InCharge/CONSOLE/smarts/local/conf.

2. Edit the SM_LICENSE variable in runcmd_env.sh on each host where EMC Smartssoftware is installed to specify the full path and file name of a single license file.When multiple products are installed on the same host, each product will include aruncmd_env.sh in its BASEDIR/smarts/local/conf directory. Ensure that the name andextension of the license file in the SM_LICENSE variable definition match the nameand extension of the license file or point to the license server.

3. For example, based on your operating system and license name, add one of thefollowing lines to the runcmd_env.sh file.


UNIX SM_LICENSE=/opt/InCharge/CONSOLE/smarts/local/conf/smarts.lic

Microsoft Windows SM_LICENSE=C:\InCharge\CONSOLE\smarts\local\conf\smarts.lic

Obtaining a Watch4net licenseIf you change the configuration of your machine, for example, by adding interfaces,removing them, or by changing the operating system, your Watch4net permanent licensemay no longer work. In that case, obtain the host ID and request a new permanentlicense.

1. Obtain the host ID. From the /bin directory (for example, /opt/APG/bin for UNIXand the C:\Program Files\APG\bin directory for Windows), type:

Operating System Command

UNIX ./manage-licenses.sh host-id

Windows manage-licenses.cmd host-id

2. Copy the host ID information to a clipboard or to a text file.

3. For product licenses, navigate to support.emc.com > Service Center > Product Registration &Licenses.



4. Paste the host ID information into the request for a new permanent license.

Watch4net licensesFor a new Watch4net installation, you need to install your Watch4net licenses for the firsttime using the manage-licenses.sh command. If you have an existing permanent ortemporary license and you need to update it, use the license upload feature in theWatch4net Centralized Management area.

Installing Watch4net licenses for the first timeAfter you install your Watch4net server, you need to install permanent or temporarylicenses on your Watch4net server.

You need this information to complete this procedure: Download the permanentlicense .zip file or the temporary .lic file that you received from EMC into a directory, suchas /opt/APG/licenses.

u From the installation /bin directory, type:


UNIX ./manage-licenses.sh install <download_path>/<license.zip>

Windows manage-licenses.cmd install <download_path>\<license.zip>

Permanent license example on Linux: From the /opt/APG/bin directory, type:

./manage-licenses.sh install /opt/APG/licenses/license.zip

The licenses in the .zip file are extracted and are applied to your Watch4net server.

Temporary license example on Windows: From the C:\Program Files\APG\bindirectory, type:

manage-licenses.cmd install C:\data\license.lic

The license is applied to your Watch4net server.

Adding or updating Watch4net licensesYou can add or update licenses on your Watch4net server.

You need this information to complete this procedure:u Download the permanent license .zip file or the temporary .lic file that you received

from EMC into a directory, such as /opt/APG/licenses.

1. Log into Watch4net.

2. Click Administration.

3. In the Centralized Management pane, select Licenses.

4. In the Physical Overview tree, select Licenses Management.

5. In the Licenses Listing pane, click Upload.

6. In the License Upload dialog box, browse to your license file. Click OK.

Licenses in a .zip file are extracted and appear in the Licenses Listing pane.


Watch4net licenses 29

Deleting Watch4net licensesYou can remove permanent or temporary licenses from your Watch4net server if youaccidently installed the wrong ones.





5. In the Licenses Listing pane, select one or more license checkboxes.

6. Click Delete.

Single sign-on configurationFollow the procedures in this section to create single sign-on (SSO) authentication forCompanion UI, SAM, SAM Web Console, and Watch4net. After the Smarts ConsoleSolutionPack setup is completed, users who log into Watch4net are automatically loggedinto the Companion UI and SAM views.

Certificate management among hostsThe sharing of digitally-signed certificates over an SSL connection among the producthosts and clients builds a trust relationship for SSO authentication. The servers hosting aproduct in this SolutionPack require a certificate to be shared among the hosts for CAS(Central Authentication Service) authentication. The Companion UI provides the CASauthentication for the SAM server. If a server is hosting SAM, SAM Web Console, andWatch4net, only one Companion UI certificate is required. By running SSO configurationscripts, certificates are created and copied to the appropriate hosts for SSOauthentication in this SolutionPack.

1. Setting the properties for single sign-on authentication on page 30

2. Setting up single sign-on for the Watch4net server on page 33

3. Setting up single sign-on authentication for the SAM server on page 35

4. Setting up single sign-on authentication for the secondary SAM server (failover) onpage 36

5. Setting up single sign-on authentication for the SAM Web Console server on page37

6. Setting up single sign-on authentication for the Companion UI server on page 38

If you have a secondary SAM server for a failover solution, copy theconfigureSSO folder with the edited configureSSO.conf file to the base directory pathof the secondary SAM server. Do not modify the values for the secondary SAM server.Then, run the procedure to create single sign-on authentication for the secondary SAMserver.

Setting the properties for single sign-on authenticationUse the configureSSO.conf file to define properties used in single sign-onauthentication for Watch4net, SAM Web Console, and Companion UI.

You must use the fully qualified domain names for Watch4net, SAM Web Console, andCompanion UI in the properties file. You may optionally replace the default Java keystore



values for the Watch4net and SAM Web Console products with your company's keystorevalues.

In a production environment, EMC recommends using a trusted certificate keystore ofyour choice.

1. Obtain the configureSSOZIP-9.2.0.<buildnumber>.zip file from the locationwhere you downloaded and unzipped your Companion UI installation files.

2. Unzip configureSSOZIP-9.2.0.<buildnumber>.zip and extract the configureSSOfolder.

3. Navigate to the configureSSO folder and edit configureSSO.conf with a texteditor.

4. Enter the values for Watch4net, SAM Web Console, and Companion UI.

5. Save the file.

6. Copy the configureSSO folder with the edited configureSSO.conf file to the basedirectory path for each product before running the configureSSO scripts.

Server Sample Base Directories

Watch4net /opt/APG

Companion UI /opt/emc/apps

SAM /opt/InCharge/SAM/smarts/local

SAM Web Console /opt/InCharge/CONSOLE/smarts/local

If you have a secondary SAM server for a failover solution, copy theconfigureSSO folder with the edited configureSSO.conf file to the base directorypath of the secondary SAM server. Do not modify the values for the secondary SAMserver.

configureSSO.conf properties fileBefore running any single sign-on configuration scripts, you must define the propertyvalues in the configureSSO.conf file.

Copy the configureSSO folder with the edited configureSSO.conf file to the basedirectory path for each product before running the configureSSO scripts.

Do not enter special characters except those required to be read by theoperating system. For example, for Windows, this is an acceptable filepath:W4N_KEYSTORE_FILEPATH= C:\\Program Files\\APG\\configureSSO\\cacerts.Do not add quotes or comments. For example, this value would cause errors:W4N_HOST_FQDN=wp-qa-147.lss.emc.com ##This is a wrong way to comment.


Setting the properties for single sign-on authentication 31

Table 10 Companion UI properties

Properties Description- -CUI_HOST_FQDN The fully qualified domain name of the

Companion UI host.

CUI_SSL_PORT The secure (SSL) port for the Companion UIhost. For example, 443

Table 11 SAM Web Console properties

Properties Description- -CONSOLE_HOST_FQDN The fully qualified domain name of the SAM

Web Console host.

CONSOLE_SSL_PORT The secure (SSL) port for the SAM WebConsole. For example, 8443.

Table 12 Watch4net properties

Properties Description- -W4N_HOST_FQDN The fully qualified domain name of the

Watch4net host.

W4N_SSL_PORT The secure (SSL) port for the Watch4net host.For example, 58443.

Advanced PropertiesDo not modify these properties unless you need to add your company's keystore values.All of the following configurations will be populated with default Java keystore values ifall of the fields are left empty.

Table 13 SAM Web Console keystore and truststore values

Properties Description Default values- - -CONSOLE_KEYSTORE_FILEPATH Path to the Web Console

keystore.

<ConsoleBaseDIR>/smarts/jre/lib/security/cacerts

CONSOLE_KEYSTORE_PASS Password for the WebConsole. keystore

changeit

CONSOLE_KEY_PASS The password for theencrypted Console key.

changeit

CONSOLE_TRUSTSTORE_FILEPATH

Path to the Web Consoletruststore. Leave thisfield blank to use thevalue inCONSOLE_KEYSTORE_FILEPATH as the value

IfCONSOLE_KEYSTORE_FILEPATHis empty, then<ConsoleBaseDIR>/smarts/jre/lib/security/cacerts



Table 13 SAM Web Console keystore and truststore values (continued, page 2 of 2)

Properties Description Default values- - -

for Web Consoletruststore filepath.

CONSOLE_TRUSTSTORE_PASS Web Console truststorepassword. Leave thisfield blank to use thevalue inCONSOLE_KEYSTORE_PASS as the Web Console

truststore password.

changeit

Table 14 Watch4net keystore and truststore values

Properties Description Default values- - -W4N_KEYSTORE_FILEPATH Path to the Watch4net

keystore

<W4NBaseDIR>/Java/Sun-JRE/6.0u37/lib/security/cacerts

W4N_KEYSTORE_PASS Password for theWatch4net keystore

changeit

W4N_KEY_PASS The password for theencrypted Watch4net key.

changeit

W4N_TRUSTSTORE_FILEPATH= Path to the Watch4nettruststore. Leave this fieldblank to use the value inW4N_KEYSTORE_FILEPATH as the value for

Watch4net truststorefilepath.

If W4N_KEYSTORE_FILEPATH isempty, then <W4NBaseDIR>/Java/Sun-JRE/6.0u37/lib/security/cacerts

W4N_TRUSTSTORE_PASS Watch4net truststorepassword. Leave this fieldblank to use the value inW4N_KEYSTORE_PASSas the Watch4nettruststore password.

changeit

Setting up single sign-on for the Watch4net serverUse the configureSSO.sh -w4n to create a certificate for the Watch4net server, importthe Companion UI certificate, add CAS information to the Tomcat context.xml file, createthe appadmin user and password, and back up the Tomcat server.xml and context.xmlfiles.

The following is required to perform this task:

u The Watch4net server is installed.u The Watch4net license is configured.u The Watch4net services are running.u The configureSSO folder has been copied to the Watch4net server.


Setting up single sign-on for the Watch4net server 33

u The configureSSO.conf file has been edited and the property values defined.

1. Login to the Watch4net server.

2. Navigate to the <W4NBaseDIR>/configureSSO folder. For example, /opt/APG/configureSSO.

3. For UNIX, change the permissions of the configureSSO.sh script so you can executeit:# chmod +x configureSSO.sh

4. Run the single sign-on configuration script.

The command must be run from the <W4NBaseDIR>/configureSSO folder.

Operating system Command

UNIX ./configureSSO.sh -w4n

Microsoft Windows configureSSO.bat -w4n

5. Check the <W4NBaseDIR>configureSSO/logs directory for success or error messagesin the log file for the configureSSO script.

6. Stop and start Watch4net services.

Stopping Watch4net services on a UNIX serverUse this procedure to stop a specific Watch4net service or to stop all of the Watch4netservices on your UNIX server.

u Type the following command from the /bin directory of the installation (for example,from the /opt/APG/bin directory):./manage-modules.sh service stop [all | <service_name>]

For example:./manage-modules.sh service stop all

Stopping Watch4net services on a Windows serverUse this procedure to stop Watch4net services from the Windows desktop.

1. From the application server's desktop, select Start > Administrative Tools > Services.

2. Right-click each service and click Stop, in this order:l APG MySQL

l APG Backend

l APG Alerting Backend

l APG Collector Manager

l APG Tomcat

l APG Task Scheduler

l APG Webservice Gateway

Starting the Watch4net servicesAfter you install Watch4net, start the Watch4net services.

u Type the following command from the /bin directory of the installation. For example,from the /<APG_DIR>/bin directory for UNIX and the <APG_DIR>/bin directory forWindows:




UNIX ./manage-modules.sh service start all

Windows manage-modules.cmd service start all

Watch4net service log filesThe Watch4net service log files provide detailed information about the status of theservice.

To determine why a service is not running, check the corresponding log file for theservice. For example:/opt/APG/Databases/MySQL/Default/data/[SERVER NAME].err/opt/APG/Backends/Alerting-Backend/Default/logs/alerting-0-0.log/opt/APG/Backends/APG-Backend/Default/logs/cache-0-0.log/opt/APG/Collecting/Collector-Manager/Default/logs/collecting-0-0.log/opt/APG/Web-Servers/Tomcat/Default/logs/service.log/opt/APG/Tools/Task-Scheduler/Default/logs/scheduler-0-0.log/opt/APG/Tools/Webservice-Gateway/Default/logs/gateway-0-0.log

Troubleshoot service startup problems on WindowsWhen services will not start, check the log files.

u Check these logs in the C:\Program Files\APG directory to troubleshoot startupproblems:Databases\MySQL\Default\data\[SERVER NAME].err.Backends\Alerting-Backend\Default\logs\alerting-0-0.logBackends\APG-Backend\Default\logs\cache-0-0.logCollecting\Collector-Manager\Default\logs\collecting-0-0.logWeb-Servers\Tomcat\Default\logs\service.logTools\Task-Scheduler\Default\logs\scheduler-0-0.logTools\Webservice-Gateway\Default\logs\gateway-0-0.log

Setting up single sign-on authentication for the SAM serverUse the configureSSO.sh -samserver to import the Companion UI certificate, replacethe authority identifier on the SAM server, set the fully qualified domain name for theCompanion UI and SAM Web Console, set the log file path, and back up the SSOconfiguration files.


u The SAM server host is installed.

u The SAM server license is configured.

u The SAM server is running.

u The configureSSO folder has been copied to the Watch4net server.

u The configureSSO.conf file resides on the SAM server and its property values aredefined.

1. Log into the SAM server host.

2. Go to the <SAMServerBaseDIR>/smarts/local/configureSSO folder.

<SAMServerBaseDIR>

indicates the base directory where SAM is installed, for example, /opt/InCharge/SAM



Setting up single sign-on authentication for the SAM server 35


The command must be run from the <SAMServerBaseDIR>/smarts/local/configureSSO folder.


UNIX ./configureSSO.sh -samserver

Microsoft Windows configureSSO.bat -samserver

5. Check the <SAMServerBaseDIR>/smarts/local/configureSSO/logs directory forthe log file for the configureSSO script.

6. Restart the SAM server by entering:<SAMServerBaseDIR>/smarts/bin/sm_service stop ic-sam-server<SAMServerBaseDIR>/smarts/bin/sm_service start ic-sam-server

7. If the Broker is running from the same installation as the SAM server, you also needto restart the Broker by entering:<SAMServerBaseDIR>/smarts/bin/sm_service stop ic-broker<SAMServerBaseDIR>/smarts/bin/sm_service start ic-broker

Replacing the authority identifier on non-SAM domain managersYou must set the authority identifier for non-SAM domains to "<STD>" when thosemanagers run on the server where SAM with single sign-on (SSO) is configured.

1. Verify you are working in the <SMARTS_HOME> directory in the non-SAM domainmanager.

2. Execute <BASEDIR>/smarts/bin/sm_edit local/conf/runcmd_env.sh.

3. Based on your operating system, add one of the following lines to runcmd_env.sh.


UNIX SM_AUTHORITY="<STD>"

Microsoft Windows SM_AUTHORITY="<STD>"

4. Save the runcmd_env.sh file.

Setting up single sign-on authentication for the secondary SAM server (failover)If you have a secondary SAM server for a failover solution, use the configureSSO.sh -samserver to import the Companion UI certificate, replace the authority identifier on thesecondary SAM server, set the fully qualified domain name for the Companion UI andSAM Web Console, set the log file path, and back up the SSO configuration files.


u The Failover Manager and the failover solution is deployed as described in the EMCSmarts Failover System User Guide.

u The secondary SAM server host is installed.

u The secondary SAM server license is configured.

u The secondary SAM server is running.





1. Log into the secondary SAM server host.

2. Go to the <SAMServerBaseDIR>/smarts/local/configureSSO folder.

<SAMServerBaseDIR>

indicates the base directory where SAM is installed, for example, /opt/InCharge/SAM



The command must be run from the <SAMServerBaseDIR>/smarts/local/configureSSO folder.


UNIX ./configureSSO.sh -samserver

Microsoft Windows configureSSO.bat -samserver

5. Check the <SAMServerBaseDIR>/smarts/local/configureSSO/logs directory forthe log file for the configureSSO script.

6. Restart the secondary SAM server by entering:<SAMServerBaseDIR>/smarts/bin/sm_service stop ic-sam-server<SAMServerBaseDIR>/smarts/bin/sm_service start ic-sam-server

7. If the Broker is running from the same installation as the secondary SAM server, youalso need to restart the Broker by entering:<SAMServerBaseDIR>/smarts/bin/sm_service stop ic-broker<SAMServerBaseDIR>/smarts/bin/sm_service start ic-broker

Setting up single sign-on authentication for the SAM Web Console serverUse the configureSSO.sh -samconsole to create a certificate for the SAM WebConsole server, import the Companion UI certificate, add CAS information to the Tomcatweb.xml file, and back up the Tomcat server.xml and web.xml files.


u The SAM Web Console is installed.

u The SAM Web Console license is configured.

u The Tomcat service is running.



1. Login to the SAM Web Console server.

2. Go to the <ConsoleBaseDIR>/smarts/local/configureSSO folder.<ConsoleBaseDIR> indicates the base directory where SAM Web Console is installed,for example, /opt/InCharge/CONSOLE.




Setting up single sign-on authentication for the SAM Web Console server 37

The command must be run from the <ConsoleBaseDIR>/smarts/local/configureSSO folder.


UNIX ./configureSSO.sh -samconsole

Microsoft Windows configureSSO.bat -samconsole

5. Check the <ConsoleBaseDIR>/smarts/local/configureSSO/logs directory for thelog file for the configureSSO script.

6. Restart the Tomcat service by entering:<ConsoleBaseDIR>/smarts/bin/sm_service stop ic-business-dashboard<ConsoleBaseDIR>/smarts/bin/sm_service start ic-business-dashboard

Setting up single sign-on authentication for the Companion UI serverUse the configureSSO.sh -cui script to import the Watch4net and SAM Web Consolecertificates from Windows or Linux hosts into the Companion UI server. For Solaris hosts,you must use the solaris_import_for_cui.sh script instead of configureSSO.sh.


u The configureSSO script has been run on Watch4net, SAM, and SAM Web Console.

u The Companion UI server is deployed.

u The Tomcat service is running.


u The configureSSO.conf file has been edited and the property values defined.

1. Login to the Companion UI server.

2. Change directory to the <CUIServerBaseDIR>/configureSSO folder. For example, /opt/emc/apps/configureSSO.



The command must be run from the <CUIServerBaseDIR>/configureSSO folder.

Operating system Command- -UNIX ./configureSSO.sh -cui

5. Check the <CUIServerBaseDIR>/configureSSO/logs directory for the log file forthe configureSSO script.

6. Restart the Tomcat service by entering service tomcat6 restart



[Solaris only] Importing certificates to the Companion UI serverWhen Watch4net or SAM Web Console are installed on Solaris hosts, you must manuallyimport their certificates into the Companion UI server's trusted keystore instead ofrunning the configureSSO -cui script.

In a production environment, EMC recommends using a trusted certificatekeystore of your choice.

Import certificates to the Companion UI trusted store by manually copying the certificatesto the Companion UI server and running the solaris_import_for_cui.sh script.

1. Confirm the host names specified in the W4N_HOST_FQDN, CONSOLE_HOST_FQDN, andCUI_HOST_FQDN fields in the configureSSO.conf file.

2. Log in to W4N_HOST_FQDN and CUI_HOST_FQDN.

3. Copy the certificate from W4N_HOST_FQDN to CUI_HOST_FQDN.

For example, from <W4NBaseDIR>/configureSSO/certs to <CUIServerBaseDIR>/configureSSO/certs.

4. Log in to CONSOLE_HOST_FQDN and CUI_HOST_FQDN.

5. Copy the certificate from CONSOLE_HOST_FQDN to CUI_HOST_FQDN.

For example, from <ConsoleBaseDIR>/smarts/local/configureSSO/certs to<CUIServerBaseDIR>/configureSSO/certs.

6. Change directory to <CUIServerBaseDIR>/configureSSO. For example, /opt/emc/apps/configureSSO.

7. Change the permissions of solaris_import_for_cui.sh so you can execute thescript:# chmod +x solaris_import_for_cui.sh

8. Run the solaris_import_for_cui.sh script.

Verifying if the Watch4net certificate exists in the Companion UI serverVerify the Watch4net certificate was successfully imported into the Companion UI server.

1. Check whether the Watch4net certificate exists in the Companion UI server byentering this command./opt/emc/apps/javaHome/bin/keytool -list -alias <w4n> -keystore /opt/emc/apps/javaHome/lib/security/cacerts

2. If the certificate exists, reboot the Companion UI server.

Verifying if the SAM Web Console certificate exists in the Companion UIVerify the SAM Web Console certificate was successfully imported into the Companion UIserver.

1. Check whether the SAM Web Console certificate exists in the Companion UI server byentering this command./opt/emc/apps/javaHome/bin/keytool -list -alias <console> -keystore /opt/emc/apps/javaHome/lib/security/cacerts

2. If the certificate exists, reboot the Companion UI.


[Solaris only] Importing certificates to the Companion UI server 39

Smarts Console SolutionPack setup with Companion UIFollow the procedures in this section to connect to the Centralized-Management webapplication in Watch4net where you can install the Smarts Console SolutionPack andenable Companion UI.

Installing Smarts Console SolutionPack1. Connecting to the Watch4net server and Companion UI on page 40

2. Configuring the Watch4net server for the first time on page 41

3. Installing the EMC Smarts Console SolutionPack with Companion UI on page 41

Updating a SolutionPackWhen software updates for a SolutionPack are available, follow these procedures toapply the updates:

1. Updating SolutionPack files before installing the SolutionPack on page 43

2. GUID-644686B5-012B-4CED-8841-C99A7B1D267B

3. Stopping Watch4net services on a UNIX server on page 34

4. Stopping Watch4net services on a Windows server on page 34

5. Starting the Watch4net services on page 34

6. Verifying the SolutionPack version number on page 44

Connecting to the Watch4net server and Companion UIAfter you start the Watch4net services, connect to the centralized-management webapplication in the Watch4net server and the Companion UI.

Centralized-management is one of the multiple web-applications available in theWatch4net product. The administrator should connect first to centralized-management toconfigure the product in a distributed environment. After everything is configured, theAPG web application should be used to browse reports, solutionpacks, and so forth.

1. Point your web browser to:http://[serverIP:port]/APG

Parameter Description

localhost The fully qualified hostname or IP address of the server whereWatch4net is running.

port The port number of the Watch4net server.

For example:

https://myHost.emc.com:58443/APG2. Log into Watch4net.

a. Type appadmin for the user name.

b. Type Changeme1! for the password.

c. Click Sign In.



Configuring the Watch4net server for the first timeAfter you log in with administrative privileges for the first time, you need to confirm theconfiguration settings for the Watch4net server.

u Click Save to accept the pre-defined values for the Watch4net server.

Fields that are blank should remain blank.

Installing the EMC Smarts Console SolutionPack with Companion UIYou can configure the EMC Smarts Business Dashboard, the Web Console, and theCompanion UI appliance for use in Watch4net by installing the EMC Smarts ConsoleSolutionPack.

You need this information to complete this procedure:

u The Web Console installed and running on a secure port, such as 8443 which is thedefault secure port.

u A virtual machine with Companion UI deployed and started, if you want single sign-oncapability.

u A login with administrative privileges.

1. Log into Watch4net.For example:

https://myHost.emc.com:58443/APG2. Navigate to Administration > Centralized Management > SolutionPacks.

3. Select SolutionPack Center.

4. Select the EMC Smarts Console SolutionPack in the Browse and Install SolutionPacksscreen. Expand the Infrastructure section if necessary to find the SolutionPack.

5. Read the summary information and click Install.

6. Select the components to install.a. Type emc-smarts-console in the Instance name field.

b. Select the server where Watch4net is installed in the Data collection list box.

c. Select the server where Watch4net is installed in the Reports list box.

d. Click Next.

7. Configure data collection.

If you are using broker or alternate authentication for your Smartsdomains, select the Do you want to configure advanced settings? checkbox and enter inyour specific domain details.

a. Accept the pre-defined values in the Data Collection pane.

b. Ensure the Enable alerting on data collected checkbox is selected.

c. Accept the pre-defined values in the Alerting on data collection pane.

d. Select the fully qualified name of the host where the EMC Smarts Broker residesand the TCP port (for example, localhost:426) in the Please select the Smartsbroker list box.


Configuring the Watch4net server for the first time 41

If your Broker is not listed, select Add new broker in the Please select the Smartsbroker list box. Then, provide the necessary Broker information. Do not specify anIP address.

For a secure Broker, you need to provide some additional information. (The Brokeris secure if it is running from the same directory as the Presentation SAM server.)

– If your Broker is secure, select the Are you using broker authentication checkboxand provide appadmin and Changeme1! for the Broker username and Brokerpassword.

– If the Broker is running from a different installation and you did not change thedefault username and password, then you can leave the Are you using brokerauthentication checkbox blank.

Click the Test Connection button in the upper right corner of the dialog box to verifyWatch4net can connect to the Broker. If the connection fails, recheck your Brokersettings.

e. Accept the default user value for the Domain default username field.

If the field is blank, type your administrator user name (for example, admin).

f. Accept the default password value for the Domain default password field.

If the field is blank, type your administrator password (for example, changeme).

g. Leave the Do you want to configure advanced settings checkbox blank.

h. Click Next.

8. Configure reports.a. Accept the pre-defined value in the Please select the Gateway list box.

b. Accept the pre-defined value in the Administration Web-Service instance field.

c. Type the fully qualified name of the host where the Web Console resides in theBusiness dashboard hostname or IP address field. Do not specify an IP address.

d. Type the secure port for the Web Console in the Business dashboard port field.

Port 8443 is the default secure port for the Web Console.

e. Type the name of the Presentation SAM server in the EMC Smarts SAM domain field,and specify IP domains for data collection.

f. Select the Enable CUI server checkbox (required) to use the Companion UIappliance and single sign-on capability.

g. Type the fully qualified domain name of the virtual machine where Companion UIis deployed for the CUI hostname or IP address field. Do not specify an IP address.

h. Ensure that the Enable HTTPS checkbox is selected.

i. Select the Broker in the Please select the Smarts broker list box.

j. Click Install.

The installation process begins.

9. Select the maximize arrow next to Data collection and Reports to view the installationprocess.

When the installation successfully completes, green checkmarks appear.

10. After installation is complete, select Centralized Management > SolutionPack to verify theinstalled SolutionPack.



SolutionPack software updatesWhen a new version of SolutionPack software is available, upload the latest files to theModule-Repository folder in Watch4net and then install the SolutionPack.

To update an installed SolutionPack with newer software, follow these procedures. Afterupdating the software, install the SolutionPack.1. Uninstalling a SolutionPack on page 43






To update SolutionPack files before installing the SolutionPack for the first time, followthese procedures. After updating the files, install the SolutionPack.1. Updating SolutionPack files before installing the SolutionPack on page 43





Uninstalling a SolutionPackYou can uninstall a SolutionPack from the Watch4net server.

You need a login with administrative privileges to complete this procedure.

1. Log into Watch4net and select Administration.

2. Select Centralized Management in the Administration tree.

3. Login with your administrator credentials (for example, admin for the User field andchangeme for Password field).

4. Select SolutionPacks in the tree.

5. Select the SolutionPack that you want to uninstall in the Installed SolutionPacksscreen.

6. In the Properties area, click the Trashcan icon next to the instance for eachSolutionPack block and click Remove.

Updating SolutionPack files before installing the SolutionPackUse this procedure to upload new SolutionPack files before installing the SolutionPackfor the first time.

You need this information to complete this procedure:u A Watch4net login with administrative privileges.

u The latest <solutionpack>.pkg file available from EMC Online Support.

After you update a SolutionPack, restart the Watch4net services and then check theSolutionPack version number to confirm the update.

1. Download the <solutionpack>.pkg from EMC Online Support to a directory, such as /temp.


SolutionPack software updates 43

2. Copy the <solutionpack>.pkg file to the following directory:

Operating System Description

UNIX ./opt/APG/Tools/Module-Repository

Windows C:\Program Files\APG\Tools\Module-Repository

3. Navigate to Administration > Centralized Management > Packages Management.

4. Click Upload.

5. Browse to the Module-Repository folder and upload <solutionpack>.pkg file.

6. Install the SolutionPack.

Verifying the SolutionPack version numberUse this command to verify the SolutionPack version number after an update or toconfirm that you have the latest version.

u Type the following command to verify your SolutionPack version number:


UNIX /opt/APG/bin/manage-modules.sh list installed

Windows C:\Program Files\APG\bin\manage-modules.cmd listinstalled







l APG Backend



l APG Tomcat










Installing the EMC Smarts Console SolutionPack with CompanionUI

You can configure the EMC Smarts Business Dashboard, the Web Console, and theCompanion UI appliance for use in Watch4net by installing the EMC Smarts ConsoleSolutionPack.


u The Web Console installed and running on a secure port, such as 8443 which is thedefault secure port.

u A virtual machine with Companion UI deployed and started, if you want single sign-oncapability.


1. Log into Watch4net.For example:

https://myHost.emc.com:58443/APG2. Navigate to Administration > Centralized Management > SolutionPacks.


4. Select the EMC Smarts Console SolutionPack in the Browse and Install SolutionPacksscreen. Expand the Infrastructure section if necessary to find the SolutionPack.





d. Click Next.







Starting the Watch4net services 45




– If your Broker is secure, select the Are you using broker authentication checkboxand provide appadmin and Changeme1! for the Broker username and Brokerpassword.








h. Click Next.




d. Type the secure port for the Web Console in the Business dashboard port field.

Port 8443 is the default secure port for the Web Console.

e. Type the name of the Presentation SAM server in the EMC Smarts SAM domain field,and specify IP domains for data collection.

f. Select the Enable CUI server checkbox (required) to use the Companion UIappliance and single sign-on capability.

g. Type the fully qualified domain name of the virtual machine where Companion UIis deployed for the CUI hostname or IP address field. Do not specify an IP address.

h. Ensure that the Enable HTTPS checkbox is selected.

i. Select the Broker in the Please select the Smarts broker list box.

j. Click Install.







User synchronizationFollow the tasks in this section to set the values in the UserSync properties file and runthe script that uses this file to synchronize users across Companion UI, SAM, andWatch4net for SSO authentication.

TasksFollow the tasks in this order to synchronize users across Companion UI, SAM, andWatch4net.

1. Setting the properties for user synchronization on page 47

2. Synchronizing users for first use on page 49

3. Checkpoint on page 25

4. Testing single sign-on authentication on page 50

5. Verifying setup of Smarts Console users on page 50

6. Launching Smarts Console views with secure port on page 51

Setting the properties for user synchronizationThe UserSync utility uses the values defined in the sso_usersync.properties file toassign default passwords and roles for Watch4net, SAM and Companion UI users, to setthe common properties for these products, to determine the authentication method forthe Companion UI, and to define how to run the UserSync utility.

1. Login into the Watch4net server.

2. Open sso_usersync.properties in <APG_Directory>/Collecting/Smarts-Collector/emc-smarts-console/contrib/user-sync.

3. Enter your values.

4. Save the file.

UserSync properties fileBefore running the UserSync utility, you must define the property values in thesso_usersync.properties file. This file is located in <APG_Directory>/Collecting/Smarts-Collector/emc-smarts-console/contrib/user-sync.

Common properties, such as default password for all new users in Companion UI, SAM,and Watch4net.

Property Description- -COMMON_ADMIN_USER User created with administrator rights in

Companion UI, SAM, and Watch4net by theUserSync utility. This value must match theSAM_ADMIN_USER. Example: admin

COMMON_ADMIN_PASSWORD Password for the administrator in CompanionUI, SAM, and Watch4net. This value mustmatch the SAM_ADMIN_PASSWORD. Example:changeme


User synchronization 47

Property Description- -NEW_USER_DEFAULT_PASSWORD Default password assigned to all new users in

Companion UI, SAM, and Watch4net by theUserSync utility. Example: changeme

Watch4net properties, such as user roles and profiles

Property Description- -W4N_WSDL_URL URL for the Watch4net administration tool module. Change

the IP address or hostname (watch4net.emc.com) to point tothe server containing the Watch4net installation. Example:https://admin:[email protected]:48443/Tools/Adminstration-Tool/Default.

W4N_DEFAULT_ROLE Role assigned to a new user created in Watch4net. Value canbe admin or user.

W4N_DEFAULT_PROFILE Profile assigned to a user created in Watch4net. Example:user

W4N_ADMIN_USERNAME User created with administrator rights in Watch4net. Defaultvalue: admin

W4N_ADMIN_PASSWORD Password for the administrator in Watch4net. Default value:changeme

Companion UI properties, such as authentication method for single sign-on

Property Description- -CUI_URL URL for the Companion UI. Change the IP address or host

name (cuiserver.emc.com) to point to the Companion UIserver. Example: https://cuiserver.emc.com/user-managment-service/users

CUI_DEFAULT_ROLE Default role assigned to new users created in theCompanion UI by the UserSync utility. Example: user

CUI_AUTHENTICATION_TYPE Method to authenticate users. This can be localauthentication or LDAP (Lightweight Directory AccessProtocol) authentication. If set to local authentication,you must manually maintain all user passwords for SSOin the Companion UI. If set to LDAP, this authenticationtype, handles all user passwords. Value is local or LDAP.

CUI_ADMIN_USERNAME Companion UI user name for the administrator. Defaultvalue: appadmin

CUI_ADMIN_PASSWORD Password for CUI_ADMIN_USERNAME. Default value:Changeme1!



SAM properties, such as SAM admin user and password

Property Description- -SAM_BROKER_NAME Host name or IP address of the SAM Broker. Example: sm-

Broker.emc.com

SAM_BROKER_PORT Port where the SAM Broker process is running. Example: 426

SAM_DOMAIN_NAME SAM domain name. Example: INCHARGE-SA

SAM_ADMIN_USER User name for the SAM administrator. Verify this user exists withadministrator rights in SAM.If the Broker is running from the Presentation SAM installation,the Broker is using CAS authentication. Specify appadmin for

SAM_ADMIN_USER.

If the Broker is not running from the Presentation SAMinstallation, specify admin for SAM_ADMIN_USER.

SAM_ADMIN_PASSWORD Password for the SAM administrator.If the Broker is running from the Presentation SAM installation,specify Changeme1! for SAM_ADMIN_PASSWORD.

If the Broker is not running from the Presentation SAMinstallation, specify changeme for SAM_ADMIN_PASSWORD.

SAM_DEFAULT_ROLE Default role assigned to new users created in SAM by theUserSync utility. Example: oper

SAM_RETRY_COUNT Number of times for the UserSync utility to retry connecting to theSAM Broker or the SAM server before reporting an error.

Other properties, such as steps to perform during first synchronization

Property Description- -BOOTSTRAP_STEPS Steps performed after Companion UI, SAM Web Console, SAM

server, and Watch4net are installed and configured. You runstart.bat -b (MIcrosoft Windows) or start.sh -b (UNIX)

to synchronize users. Example: ADD CUI W4N, ADD SAM W4N,ADD W4N CUI, ADD W4N SAM

ONDEMAND_STEPS Steps performed by the UserSync utility after an administratorhas added or deleted users in Watch4Net. You run start.bat(Microsoft Windows) or start.sh (UNIX) to synchronize users.

Example: ADD W4N CUI, ADD W4N SAM, DEL W4N CUI, DELW4N SAM

TEST_MODE Mode to run the UserSync utility (1=test mode, 0=non-testmode). Always set this value to 0.

Synchronizing users for first useThe first time you set up the Smarts Console SolutionPack with SAM and CUI, you mustuse the UserSync utility to synchronize users across Companion UI, SAM, and Watch4net.

Set the following to perform this procedure:


Synchronizing users for first use 49

u Set JAVA_HOME system properties on Microsoft Windows systems using setJAVA_HOME=<Watch4net_Dir>\Java\Sun-JRE\6.0u37. For example: set JAVA_HOME="C:\Program Files\APG\Java\Sun-JRE\6.0u37"

u Set JAVA_HOME on Linux systems using export JAVA_HOME=/<Watch4net_Dir>/Java/Sun-JRE/6.0u37. For example: export JAVA_HOME=/opt/APG/Java/Sun-JRE/6.0u37

1. Go to <APG_Directory>/Collecting/Smarts-Collector/emc-smarts-console/contrib/user-sync.

2. For UNIX, change the permissions of the start.sh command so you can execute it:# chmod +x start.sh

3. Fill out the properties in the sso_usersync.properties file.

Ensure that the SAM_ADMIN_USER and SAM_ADMIN_PASSWORDproperties are set appropriately for the Broker.

4. Depending on your operating system, use one of these commands to synchronizeusers.


UNIX ./start.sh -b

Microsoft Windows start.bat -b

Users are now the same in Companion UI, SAM, and Watch4net.

The original default values may not be the same. Instead, values forSAM_ADMIN_USER=admin and SAM_ADMIN_PASSWORD=changeme must be set in thesso_usersync.properties file.

Verifying setup of Smarts Console usersView a report of all users created in Watch4net for use in logging into the Smarts Consoleintegrated systems.

u To view the report, enter: <APG_DIR>/Collecting/Smarts-Collector/emc-smarts-console/contrib/user-sync/Report_-<date>.log

CheckpointCheck your progress using the following procedure(s).

Testing single sign-on authenticationTest the single sign-on authentication by logging into Watch4net after running theconfigureSSO scripts and the UserSync utility.

Log into Watch4net with any user name defined in SAM or Watch4net prior to configuringsingle sign-on authentication. Use the NEW_USER_DEFAULT_PASSWORD in thesso_usersync.properties file when testing login authentication.

After the UserSync utility runs, users are assigned either "user" or "admin" roles inWatch4net.



u "user" role gives limited access to Watch4net features, but it is sufficient to test thata SAM user can log into Watch4net successfully. To test this, log into Watch4net withoper and changeme (or the value in NEW_USER_DEFAULT_PASSWORD if different).With a successful login, you can view the Watch4net home page but you cannotnavigate to other views from the main window.

u "admin" role gives access to administrative functions in Watch4net such as access tothe Centralized-Management URL. A user with admin privileges in SAM or CompanionUI is assigned the "admin" role in Watch4net by the UserSync utility. To test this, loginto Watch4net with admin and changeme (or the value inNEW_USER_DEFAULT_PASSWORD if different). Navigate to SolutionPacks > SmartsConsole > SAM Console and access the SAM Global Console to test that your administratorlogin works in both Watch4net and SAM.

u After the UserSync utility runs, you can log into SolutionPacks > Smarts Console with theappadmin user name and Changeme1! password. (Administrator credentials areassociated with this login for both Companion UI and Watch4net as a result ofrunning the configureSSO scripts.) However, in the SAM views, the appadmin user isassigned "user" role privileges at first. If you want the appadmin user to haveadministrative privileges in the SAM views, you must first log in to Watch4net with auser name that already has SAM admin privileges and then manually assign theappadmin user to the admin profile in Smarts Console > SAM Console.

The EMC Smarts SolutionPack User and Administration Guide provides information aboutupdating permissions for each role.

Follow these steps to test login authentication for a user without administrator privileges:1. Point your web browser to https://[serverIP:port]/APG. An example URL with a

secure port is https://myHost.EMC.com:58443/APG.

2. On the login screen, enter the default authentication user name (oper) andpassword (changeme) and click Sign In.

Launching Smarts Console views with secure portTo display Smarts Console views when Companion UI is included in the Watch4netdeployment, you must log in with a secure port and navigate to EMC Smarts ConsoleSolutionPack in the Watch4net navigation pane.

1. Point your web browser to https://[serverIP:port]/APG. An example URL with asecure port is https://localhost:58443/APG.

2. On the login screen, enter your user name and password and click Sign In.

3. Select SolutionPacks > EMC Smarts Console from the navigation pane.The apps installed with Companion UI are available from CUI > Dashboard and CUI >Operations .

4. From Dashboard or Operations select workspaces such as Group Health, Watch List, orNotifications.

5. Within a workspace, you can access online help from the wrench icon that displays inthe banner of each view.

6. Access the Smarts Console Administration views by navigating to SolutionPacks > EMCSmarts Console > Administration > CUI Server Admin.

7. Access help for Smarts Console > Administration > CUI Server Admin views after you selecta task from the menu. The Help icon displays in the upper right corner for each task.

8. Access classic SAM views by selecting SolutionPacks > EMC Smarts Console > SAM GlobalConsole.


Launching Smarts Console views with secure port 51

9. Access Device Dashboards from SolutionPacks > EMC Smarts Console > Inventory.

Data sourcesFollow the procedures in this section to configure data sources (such as ServiceAssurance Manager or Network Configuration Manager) for display in the Smarts ConsoleSolutionPack in Watch4net.

1. Configuring data sources on page 52

Configuring data sourcesConfigure data sources to make data generated by EMC products available to yourapplications.

For a NCM data source, you need to import a certificate from the host first beforeconfiguration.


2. In the tree, select SolutionPacks > EMC Smarts Console > Administration > CUI Server Admin.

3. Log in with your Companion UI credentials if you are presented with a login screen.

4. In the System Configuration area, select Managed Data Sources.

5. Click Create.

6. Select the data source type.

7. Complete the configuration settings.

8. Click OK.

Presentation SAM data source configurationUse this information to complete the Create Configuration dialog box to specify apresentation SAM data source.

Field Description- -Broker Host Name The fully qualified hostname (preferred) or IP address of the host on

which the broker is running.

Broker Port The number of the port on which the broker is running.

DM Name The name of the instance of the SAM server to which you want toconnect.

DM User Name The user name to authenticate access to the Domain Manager.

DM Password The password to authenticate access to the Domain Manager.

Other EMC Smarts data source configurationUse this information to complete the Create Configuration dialog box to specify an EMCSmarts data source (for example, IP Availability Manager, MPLS Manager, EMC SmartsServer Manager (ESM), and Business Impact Manager). In order for data to be visible inthe app, the Domain Manager must first be added to the EMC Smarts Service AssuranceGlobal Manager that is configured as the Presentation SAM server.



Field Description- -Data Source Name A unique name for the data source. Only letters,

numbers, underscores, periods, and dashes areallowed. The first character must be a letter.

Broker Host Name The fully qualified hostname (preferred) or IPaddress of the host on which the broker isrunning.

Broker Port The number of the port on which the broker isrunning.

DM Name The name of the instance of the DomainManager to which you want to connect.

DM User Name The user name to authenticate access to theDomain Manager.

DM Password The password to authenticate access to theDomain Manager.

Watch4net Server data source configuration (Mobile app only)Use this information to complete the Create Configuration dialog box to specify aWatch4Net Server data source for only the EMC Smarts Mobile app.

Field Description- -APG WSDL URL The URL to access the Watch4net installation.

APG Username The user name to authenticate access to theWatch4net data source.

APG User Password The password to authenticate access to theWatch4net data source.

New or third-party data source configurationWhen configuring new or third-party data sources, use this information to complete theCreate Configuration dialog box.



Host Name The fully qualified hostname (preferred) or IPaddress of the host for the data source.

Port The number of the port used to connect to thedata source. Leave the field blank if you do notwant the port number to appear in theconnection URL. If omitted, your data sourcemust be available on port 443 for HTTPS andport 80 for HTTP on the host name instance.


Configuring data sources 53

Field Description- -Base Path The portion of the URI without the host name

and port needed to reach the instances. Forexample, if the URI is https://host:port/msa, the base path is msa.

The complete Base URI for the data source

appears in the Details view after you configure

the data source.

Identity Matcher Path The portion of the URI without the host nameand port needed to reach the identity matcherinstance. If the URI is https://host:port/msa_IM, the Identity Matcher Path is msa_IM.

The Identity Matcher URI for the data source

appears in the Details view after you configure

the data source.

Use HTTPS protocol Select to use HTTPS, otherwise HTTP is used.

Model Name The name of the model exposed by this datasource.

Model Version The version of the model exposed by this datasource.

Internal Description A description for the registry

Source Description A description of the data source

Verify Connection The connection to the regular and IdentityMatcher URIs at the host and port is verified ifselected. Clear the checkbox if you do not wantthe URIs verified.

Import a certificate from a remote NCM server into your truststoreThe Companion UI host requires a certificate from each remote server that it contacts overan SSL connection. The importRemoteCA.sh script imports these required certificatesfrom each remote service, such as a CAS server and data source, into its truststore.

DescriptionTypically, a CAS server runs on the same host as its remote protected data source butif it does not, you must import an SSL certificate from each host into the truststore.

If you redeploy your appliance, you must import a new certificate into your truststore.

The script is located in /opt/emc/apps/Common/bin on your appliance.

To get Help, enter importRemoteCA.sh --h.

SyntaximportRemoteCA.sh[ --hostname host | --port port_no | --tomcat | --fips ]



Options

--hostname host

Fully qualified domain name (FQDN) of the remote server whose certificate you want toimport.

--port port_no

Port number of the NCM EDAA (default 9443).

--tomcat

Restarts Tomcat after importing SSL certificates. When importing multiple certificates,wait until the last certificate is imported before restarting Tomcat. The Companion UI isunavailable during a restart, which takes a few minutes.

--fips

Imports FIPS certificate in PKCS12 format for appliances running in FIPS mode. If youchanged an appliance to run in FIPS mode after importing a non-FIPS certificate, youmust then import a FIPS certificate into your truststore.

Example # 1The following imports a FIPS certificate in PKCS12 format fromRemoteNCMhost.lss.emc.com with port 9443 into the truststore of your appliance andthen restarts Tomcat.

importRemoteCA.sh --hostname RemoteNCMhost.lss.emc.com --port 9443 --fips --tomcat

Example # 2The following imports a certificate from RemoteCAhost.lss.emc.com into the truststoreof your appliance and then restarts Tomcat.

importRemoteCA.sh --hostname RemoteCAhost.lss.emc.com --tomcat

Example # 3The following imports a FIPS certificate in PKCS12 format fromRemoteCAhost.lss.emc.com into the truststore of your appliance and then restartsTomcat.

importRemoteCA.sh --hostname RemoteCAhost.lss.emc.com --fips --tomcat

Example # 4The following enables you to validate and then update an existing certificate in thetruststore of your appliance.importRemoteCA.sh --hostname RemoteCAhost.lss.emc.comImporting the CA from RemoteCAhost.lss.emc.com:443.......Existing fingerprint in keystore 659547BB4DE500B60CEC5A83A1C48726Fingerprint for new certificate 2BC46B5CA530F5B1B1907C08F04E086ECertificate changed in remote host. Would you like to update new certificate [y|n]? yCertificate was added to truststore


Configuring data sources 55

NCM data source configurationUse this information to complete the Create Configuration dialog box to specify a NCM datasource. A valid NCM user name and password with system administrator privileges mustbe created in the NCM server before you can add NCM as a data source.



NCM Host The fully qualified host name of the host, suchas myHost.emc.com, on which NCM is running.Do not specify an IP address.

NCM Username The user name to authenticate access to theNCM server.

NCM User Password The password to authenticate access to theNCM server.



CHAPTER 5

EMC Smarts Console SolutionPack with SAM


u Setup overview......................................................................................................58u Installing Service Assurance Manager...................................................................58u Installing Service Assurance Manager Web Console..............................................58u Installing Watch4net on a UNIX server...................................................................58u Installing Watch4net on a Windows Server machine..............................................59u Obtaining a Watch4net license..............................................................................59u Watch4net licenses...............................................................................................60u Starting the Watch4net services............................................................................61u Connecting to the Watch4net server......................................................................61u Configuring the Watch4net server for the first time................................................62u Smarts Console SolutionPack setup without Companion UI...................................62u SolutionPack software updates.............................................................................64u Installing the EMC Smarts Console SolutionPack without Companion UI................66

EMC Smarts Console SolutionPack with SAM 57

Setup overviewUse Watch4net and the EMC Smarts Console SolutionPack to display views of data fromService Assurance Manager (SAM) and SAM Web Console. This scenario requiresconfiguration of Service Assurance Manager components (SAM Web Console and SAMserver) and Watch4net components (EMC Smarts Console SolutionPack). It does notinclude Companion UI with support for single sign-on (SSO). This deployment optionrequires you to have separate logins for each product.

If you have a secondary SAM server for a failover solution, deploy the secondary SAMserver as described in the EMC Smarts Failover System User Guide.

When setting up the Smarts Console SolutionPack without Companion UI, you mustfollow the installation and configuration procedures in the order presented in thischapter.

Installing Service Assurance ManagerInstall Service Assurance Manager (SAM) using the default installation paths.

1. Install Service Assurance Manager as described in the EMC Smarts Installation Guidefor SAM, IP, ESM, MPLS, VoIP, and NPM Managers.

2. If you changed the default installation path, for example opt/InCharge/SAM/smarts, record the path for use in other procedures.

Installing Service Assurance Manager Web ConsoleInstall the Service Assurance Manager (SAM) Web Console for integration withWatch4net.

1. Install Service Assurance Manager (SAM) Web Console as described in the EMCSmarts Installation Guide for SAM, IP, ESM, MPLS, VoIP, and NPM Managers.

2. If you changed the default installation path, for example opt/InCharge/CONSOLE/smarts, record the path for use in other procedures.

Installing Watch4net on a UNIX serverYou can install Watch4net on a UNIX server.


u The Watch4net installation package that you downloaded from EMC to a directory,such as /temp.

u Prior to starting Watch4net services, ensure the library search path is correct on theserver that hosts Watch4net. This requirement applies to "libstd" on Solaris and"libaio" on Linux.


2. Change the permissions of the Watch4net installer so you can execute it. Forexample, for the Watch4net 6.2 Linux 64-bit executable, type:# chmod +x setup-linux-x86_64-v62.sh

3. Execute the installer from your directory:./setup-linux-x86_64-v62.sh

4. Read and accept the End User License Agreement. Use the space bar to scroll throughthe agreement. Press y to accept it.

5. Press Enter to accept the default installation directory (/opt/APG). Or, enter anotherlocation and press y.



6. Press Enter to accept the default user account name (apg) or enter another name.

7. Press Enter to accept the default location of service scripts (/etc/init.d) or enteranother location.

8. Press Enter to accept the default base directory (/etc) of runlevels scripts or enteranother location.

9. Press Enter to accept the default installation (recommended).

If you type m, only the Module Manager and Java will install. Then, you will have tomanually install other desired modules. Consult the Module Manager documentation,located in /opt/APG/Doc/APG-Module-Manager.pdf, for instructions aboutmanual module installation.


You should see the message:Installation Complete!

10. For more information, read the Watch4net ReadMe.

Installing Watch4net on a Windows Server machineYou can install Watch4net on a Windows Server 2008 R2 (or later) machine.


u The Watch4net installation package that you downloaded from EMC to a directory,such as \temp.


2. Double-click the installer to execute it:setup-win64-v62.exe

3. Click Next in the Welcome screen.

4. Read and accept the End User License Agreement. Press I Agree.

5. Press Next to accept the default installation directory (C:\Program Files\APG). Or,browse to another directory and press OK.

6. Click Install to install the default modules (recommended).

If you clear the Recommended Modules checkbox, only the Module Manager and Javawill install. Then, you will have to manually install other desired modules. Consult theModule Manager documentation, located in C:\Program Files\APG\Doc\APG-Module-Manager.pdf.

7. Upon completion, click Next.


8. Click Finish to close the installer and to read the Watch4net Readme.

Obtaining a Watch4net licenseIf you change the configuration of your machine, for example, by adding interfaces,removing them, or by changing the operating system, your Watch4net permanent license


Installing Watch4net on a Windows Server machine 59

may no longer work. In that case, obtain the host ID and request a new permanentlicense.

1. Obtain the host ID. From the /bin directory (for example, /opt/APG/bin for UNIXand the C:\Program Files\APG\bin directory for Windows), type:


UNIX ./manage-licenses.sh host-id

Windows manage-licenses.cmd host-id

2. Copy the host ID information to a clipboard or to a text file.

3. For product licenses, navigate to support.emc.com > Service Center > Product Registration &Licenses.

4. Paste the host ID information into the request for a new permanent license.

Watch4net licensesFor a new Watch4net installation, you need to install your Watch4net licenses for the firsttime using the manage-licenses.sh command. If you have an existing permanent ortemporary license and you need to update it, use the license upload feature in theWatch4net Centralized Management area.

Installing Watch4net licenses for the first timeAfter you install your Watch4net server, you need to install permanent or temporarylicenses on your Watch4net server.

You need this information to complete this procedure: Download the permanentlicense .zip file or the temporary .lic file that you received from EMC into a directory, suchas /opt/APG/licenses.

u From the installation /bin directory, type:


UNIX ./manage-licenses.sh install <download_path>/<license.zip>

Windows manage-licenses.cmd install <download_path>\<license.zip>

Permanent license example on Linux: From the /opt/APG/bin directory, type:

./manage-licenses.sh install /opt/APG/licenses/license.zip

The licenses in the .zip file are extracted and are applied to your Watch4net server.

Temporary license example on Windows: From the C:\Program Files\APG\bindirectory, type:

manage-licenses.cmd install C:\data\license.lic

The license is applied to your Watch4net server.

Adding or updating Watch4net licensesYou can add or update licenses on your Watch4net server.




u Download the permanent license .zip file or the temporary .lic file that you receivedfrom EMC into a directory, such as /opt/APG/licenses.





5. In the Licenses Listing pane, click Upload.

6. In the License Upload dialog box, browse to your license file. Click OK.

Licenses in a .zip file are extracted and appear in the Licenses Listing pane.

Deleting Watch4net licensesYou can remove permanent or temporary licenses from your Watch4net server if youaccidently installed the wrong ones.





5. In the Licenses Listing pane, select one or more license checkboxes.

6. Click Delete.






Connecting to the Watch4net serverAfter you start the Watch4net services, connect to the centralized-management webapplication in the Watch4net server.

Centralized-management is one of the multiple web-applications available in theWatch4net product. The administrator should connect first to centralized-management toconfigure the product in a distributed environment. After everything is configured, theAPG web application should be used to browse reports, solutionpacks, and so forth.

1. Open your browser and type the following URL to connect to Watch4net:http://localhost:port/centralized-management


localhost The fully qualified hostname or IP address of the server whereWatch4net is running.


Deleting Watch4net licenses 61


port The port number of the Watch4net server.

For example:

http://myHost.emc.com:58080/centralized-management2. Log into Watch4net.

a. Type your user name. The default is admin.

b. Type your password. The default is changeme.

c. Click Sign In.

Configuring the Watch4net server for the first timeAfter you log in with administrative privileges for the first time, you need to confirm theconfiguration settings for the Watch4net server.

u Click Save to accept the pre-defined values for the Watch4net server.

Fields that are blank should remain blank.

Smarts Console SolutionPack setup without Companion UIFollow the procedures in this section to connect to the Centralized-Management webapplication in Watch4net where you can install the Smarts Console SolutionPack.

Installing Smarts Console SolutionPack without Companion UI1. Installing the EMC Smarts Console SolutionPack without Companion UI on page 62

2. Launching Smarts Console views without Companion UI on page 64

Updating a SolutionPackWhen changes to a SolutionPack are available, follow these procedures to update thesoftware:

1. GUID-644686B5-012B-4CED-8841-C99A7B1D267B





Installing the EMC Smarts Console SolutionPack without Companion UIYou can configure the EMC Smarts Business Dashboard and the Web Console for use inWatch4net by installing the EMC Smarts Console SolutionPack.


u The Web Console installed and running.








5. Select the EMC Smarts Console SolutionPack in the Browse and Install SolutionPacksscreen.





d. Click Next.









– If your Broker is secure, select the Are you using broker authentication checkboxand provide your Broker credentials for the Broker username and Brokerpassword.








h. Click Next.





Installing the EMC Smarts Console SolutionPack without Companion UI 63

d. Type the port for the Web Console in the Business dashboard port field.

Port 8080 is the default unsecure port for the Web Console.

e. Type the name of the Presentation SAM server in the EMC Smarts SAM domain field.

f. Leave the Enable CUI server checkbox blank.

g. Leave the CUI hostname or IP address field blank.

h. Select the Broker in the Please select the Smarts broker list box.

i. Click Install.





Launching Smarts Console views without Companion UITo display Smarts Console views when Service Assurance Manager (SAM) and the SAMWeb Console are included in the Watch4net deployment, you must log into Watch4netand navigate to EMC Smarts Console SolutionPack in the Watch4net navigation pane.

1. Point your web browser to http://[serverIP:port]/APG. An example default URLis http://localhost:58080/APG.

2. On the login screen, enter your Watch4net user name and password and click Sign In.

3. Select SolutionPacks > EMC Smarts Console from the navigation pane.

4. Log into EMC Smarts Console with a valid user name and password.

5. Access classic SAM views by selecting SolutionPacks > EMC Smarts Console > SAM GlobalConsole.

6. Access Device Dashboards from SolutionPacks > EMC Smarts Console > Inventory.

SolutionPack software updatesWhen a new version of SolutionPack software is available, upload the latest files to theModule-Repository folder in Watch4net and then install the SolutionPack.

To update an installed SolutionPack with newer software, follow these procedures. Afterupdating the software, install the SolutionPack.1. Uninstalling a SolutionPack on page 43






To update SolutionPack files before installing the SolutionPack for the first time, followthese procedures. After updating the files, install the SolutionPack.1. Updating SolutionPack files before installing the SolutionPack on page 43















Updating SolutionPack files before installing the SolutionPackUse this procedure to upload new SolutionPack files before installing the SolutionPackfor the first time.

You need this information to complete this procedure:u A Watch4net login with administrative privileges.

u The latest <solutionpack>.pkg file available from EMC Online Support.

After you update a SolutionPack, restart the Watch4net services and then check theSolutionPack version number to confirm the update.

1. Download the <solutionpack>.pkg from EMC Online Support to a directory, such as /temp.

2. Copy the <solutionpack>.pkg file to the following directory:


UNIX ./opt/APG/Tools/Module-Repository

Windows C:\Program Files\APG\Tools\Module-Repository

3. Navigate to Administration > Centralized Management > Packages Management.

4. Click Upload.

5. Browse to the Module-Repository folder and upload <solutionpack>.pkg file.

6. Install the SolutionPack.

Verifying the SolutionPack version numberUse this command to verify the SolutionPack version number after an update or toconfirm that you have the latest version.

u Type the following command to verify your SolutionPack version number:


Uninstalling a SolutionPack 65


UNIX /opt/APG/bin/manage-modules.sh list installed

Windows C:\Program Files\APG\bin\manage-modules.cmd listinstalled







l APG Backend



l APG Tomcat








Installing the EMC Smarts Console SolutionPack withoutCompanion UI

You can configure the EMC Smarts Business Dashboard and the Web Console for use inWatch4net by installing the EMC Smarts Console SolutionPack.


u The Web Console installed and running.








5. Select the EMC Smarts Console SolutionPack in the Browse and Install SolutionPacksscreen.





d. Click Next.








For a secure Broker, you need to provide some additional information. (The Brokeris secure if it is running from the same directory as the Presentation SAM server.)– If your Broker is secure, select the Are you using broker authentication checkbox

and provide your Broker credentials for the Broker username and Brokerpassword.








h. Click Next.


Installing the EMC Smarts Console SolutionPack without Companion UI 67




d. Type the port for the Web Console in the Business dashboard port field.

Port 8080 is the default unsecure port for the Web Console.

e. Type the name of the Presentation SAM server in the EMC Smarts SAM domain field.

f. Leave the Enable CUI server checkbox blank.

g. Leave the CUI hostname or IP address field blank.

h. Select the Broker in the Please select the Smarts broker list box.

i. Click Install.







CHAPTER 6

Uninstallation procedures


u Uninstalling Companion UI with vSphere client.....................................................70u Uninstalling Companion UI with Hyper-V Manager.................................................70u Stopping Watch4net services on a UNIX server......................................................70u Uninstalling Watch4net from a UNIX server............................................................70u Stopping Watch4net services on a Windows server...............................................70u Uninstalling Watch4net from a Windows server.....................................................71u Uninstalling a SolutionPack...................................................................................71

Uninstallation procedures 69

Uninstalling Companion UI with vSphere clientUsing your vSphere client, you can shut down and remove the appliance from yourVMware inventory.

1. Open the vSphere Client and connect to the vCenter server managing your appliance.

2. Right-click the appliance and select Power > Shut Down Guest.

3. Right-click the appliance and select Delete from Disk.

Uninstalling Companion UI with Hyper-V ManagerUsing your Hyper-V Manager, you can shut down the appliance and remove the virtualmachine from your inventory.

1. From Hyper-V Manager, select the virtual machine where the appliance resides.

2. Select Actions > Turn Off to stop the virtual machine.

3. Wait for the virtual machine to stop running.

4. Select Actions > Delete to uninstall the virtual machine.




Uninstalling Watch4net from a UNIX serverUninstall Watch4net by removing all of the Watch4net services and the installationdirectory.

1. From the /opt/APG/bin directory, type:./manage-modules.sh service remove all

2. Type the following command to remove the installation directory. For example:rm -rf /opt/APG




l APG Backend



l APG Tomcat





Uninstalling Watch4net from a Windows serverUninstall Watch4net from a Windows Server 2008 R2 (or later) machine by removing all ofthe Watch4net services and then the product.

1. From the C:\Program Files\APG\bin directory, type:manage-modules.cmd service remove all

2. Use the Windows Control Panel to uninstall Watch4net.a. Click Start > Control Panel > Programs.

b. Click Uninstall a program.

c. Select the Watch4net product and click Uninstall.










Uninstalling Watch4net from a Windows server 71