OL-27753-06 COP Files for Cisco Videoscape Control Suite 3.5.0 Services Installation Guide Please Read Important Read this entire guide. If this guide provides installation or operation instructions, give particular attention to all safety statements included in this guide. Notices Trademark Acknowledgments Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) Publication Disclaimer Cisco Systems, Inc. assumes no responsibility for errors or omissions that may appear in this publication. We reserve the right to change this publication at any time without notice. This document is not to be construed as conferring by implication, estoppel, or otherwise any license or right under any copyright or patent, whether or not the use of any information in this document employs an invention claimed in any existing or later issued patent. Copyright © 2014 Cisco and/or its affiliates. All rights reserved. Information in this publication is subject to change without notice. No part of this publication may be reproduced or transmitted in any form, by photocopy, microfilm, xerography, or any other means, or incorporated into any information retrieval system, electronic or mechanical, for any purpose, without the express permission of Cisco Systems, Inc. Contents About This Guide Chapter 1 Installing Videoscape Control Suite Services: Preparation vii 1 Before You Begin ...................................................................................................................... 2 Install the Videoscape Control Suite Management Console.............................................. 5 Log in to the Management Console....................................................................................... 8 Create the SFTP User ............................................................................................................... 9 Configure the Virtual Service Namespace and Service Instance .................................... 10 Verify the PubSub .................................................................................................................. 14 Download the COP File Template and COP File .............................................................. 17 Chapter 2 Install the NOSQLCB COP File 19 Install the NOSQLCB COP File............................................................................................ 20 Chapter 3 Install HornetQ 23 Install HornetQ....................................................................................................................... 24 Chapter 4 Install the OMS COP File 27 Install the OMS COP File ...................................................................................................... 28 Chapter 5 Install the UPM COP File 31 Install the User Profile Manager COP File ......................................................................... 32 Chapter 6 Install the UPMCDA COP File 35 Install the UPMCDA COP File ............................................................................................. 36 Chapter 7 Install the JBoss COP Files 49 Installing the EPM Filer COP File........................................................................................ 50 Install the EPM COP File ...................................................................................................... 52 Install the AlertManager COP File ...................................................................................... 54 Install the ECS COP Files ...................................................................................................... 57 Install the BillingAdaptor (BOA) COP File ........................................................................ 64 OL-27753-06 iii Contents Chapter 8 Install the SRM COP File 69 Install the SRM COP File ...................................................................................................... 70 Chapter 9 Install the WFE COP File 73 Install the WFE COP File ...................................................................................................... 74 Chapter 10 Install the Targeting Message Service (TMS) COP File 77 Install the TMS COP File ....................................................................................................... 78 Chapter 11 Install the Headend Purchase (HEP) COP File 81 Install the HEP COP File ....................................................................................................... 82 Chapter 12 Install the Personal Planner Server (PPS) COP File 83 Install the PPS COP File ........................................................................................................ 84 Chapter 13 Install the Unified Notification Gateway COP File 87 Installing the Unified Notification Gateway COP File ..................................................... 88 Chapter 14 Install the Location Service Data COP File 89 Installing the Location Service Data COP File ................................................................... 90 Install the Location Service COP File .................................................................................. 91 Chapter 15 Install the Conductorapps Manager COP File 93 Installing the Conductorapps Manager COP File ............................................................. 94 Chapter 16 Install the PortProxy COP File 95 Installing the PortProxy COP File ....................................................................................... 96 Chapter 17 Install the Data Analytics 97 Data Analytics Overview ...................................................................................................... 98 Installation and Configuration of Data Analytics ............................................................. 99 Analytics Quick Start........................................................................................................... 104 Known Issues and Limitations........................................................................................... 108 iv OL-27753-06 Contents Chapter 18 Install EPM Analytics 111 Installing EPM Analytics .................................................................................................... 112 Chapter 19 Install USRM Analytics 115 Requirements for Installing USRM Analytics .................................................................. 116 Installing USRM Analytics ................................................................................................. 117 Chapter 20 Upgrade COP Files 119 Upgrade COP Files .............................................................................................................. 121 NOSQLCB Server Upgrade COP R2.1 to R3.0 GA .......................................................... 123 Upgrade UPM from Version 2.5 to Version 3.0 ............................................................... 128 Upgrade HornetQ from Version 2.5 to Version 3.0......................................................... 129 Upgrade UPM Adaptor (UPMCDA) from Version 2.5 to Version 3.0 ......................... 130 Upgrade OMS from Version 2.5 to Version 3.0 ............................................................... 131 Upgrade OMS from Version 3.0 to Version 3.1 ............................................................... 132 Upgrade the UI Component of COP Files ........................................................................ 133 Chapter 21 Uninstall COP Files 135 Uninstall COP Files.............................................................................................................. 136 Chapter 22 Troubleshooting 139 Troubleshoot COP File Installation ................................................................................... 140 Chapter 23 Customer Information 143 Appendix A NOSQLCB COP File Installation for Videoscape Control Suite 2.1 145 Install the NOSQLCB COP File (2.1) ................................................................................. 146 Configure the NOSQLCB Server ....................................................................................... 149 OL-27753-06 v About This Guide About This Guide Purpose This document provides the instructions needed to install and configure the Cisco Options Package (COP) files for the Cisco Videoscape Control Suite. Separate files must be installed for each COP file. COP Files Overview Cisco uses COP files to deliver software updates to customers. Some COP files are needed for all customers, but in most cases, Cisco prepares COP files for individual customers. For authentication purposes, COP files for individual customers are digitally signed. A COP file is a compressed file that has a .cop file extension. The software installer unpacks the .cop file and looks for a copstart.sh script inside of it. This script contains all the logic to install the accompanying files. The script is run with root privileges. When the COP file has been digitally signed, the COP file will have an .sgn extension in addition to the .cop extension. Audience The audience for this document includes system administrators, operators, and installation engineers who deploy Cisco Videoscape Control Suite systems. Document Version This is the sixth formal release of this document, which was updated for Videoscape Control Suite 3.5.0. OL-27753-06 vii 1 Chapter 1 Installing Videoscape Control Suite Services: Preparation This chapter provides instructions for installing the service that is required before you can install the Cisco Videoscape Control Suite COP files. In This Chapter OL-27753-06 Before You Begin..................................................................................... 2 Install the Videoscape Control Suite Management Console............. 5 Log in to the Management Console ..................................................... 8 Create the SFTP User .............................................................................. 9 Configure the Virtual Service Namespace and Service Instance ... 10 Verify the PubSub ................................................................................. 14 Download the COP File Template and COP File ............................. 17 1 Chapter 1 Installing Videoscape Control Suite Services: Preparation Before You Begin Software Requirements Be certain that you have installed the Cisco Videoscape Control Suite software. See the Videoscape Control Suite Installation and Upgrade Guide (part number OL29939) for details. COP files will be installed on one of the Videoscape Control Suite Service instances installed using the Videoscape Control Suite Installation and Upgrade Guide (part number OL-29939). NOSQLCB instances require three blades. Each blade contains a NOSQLCB server instance. A possible VM configuration to support Services and NOSQLCB VM consists of the following: UCS blade 1 2 - VM-1 — Cisco Videoscape Control Suite (Msginfra node) - VM-2 — Cisco Videoscape Control Suite with Cisco Videoscape Control Suite Management Console COP file installation - VM-3 — Cisco Videoscape Control Suite Services — Endpoint Manager (EPM) Services — Alert Manager (AM) Services — Session Resource Manager (SRM) Services — Work Flow Engine (WFE) Services — HornetQ (CD) Services — User Profile Manager (UPM) Services — User Profile Manager Adaptor (UPMCDA) OL-27753-06 Before You Begin NOSQLCB VM - - - Small Configuration M2: 4vCPU / 16GB RAM / 80GB HDD M3: 5vCPU / 20GB RAM / 80GB HDD Medium Configuration M2: 6vCPU / 24GB RAM / 160GB HDD M3: 8vCPU / 32GB RAM / 160GB HDD Large Configuration M2: 12vCPU / 48GB RAM / 80 GB HDD M3: 16vCPU / 64GB RAM / 80 GB HDD or M2: 24vCPU / 96GB RAM / 160GB HDD M3: 32vCPU / 128GB RAM / 160GB HDD UCS blade 2 — VM-4 (NOSQLCB server 1) UCS blade 3 — VM-5 (NOSQLCB server 2) UCS blade 4 — VM-6 (NOSQLCB server 3) COP File Requirements In general, COP files end with .cop.sgn. For example: cisco.conductor-xxxxxxx.x.x-x-x.cop.sgn Note: COP files cannot be downloaded from the desktop. Template File Requirements cisco.conductor-xxxxxx.x.x-x-x.tmp.xml Note: The template file can be downloaded from the desktop or through the SSH File Transfer Protocol (SFTP). Browser Requirements - Videoscape Control Suite 3.1 and 3.5 Internet Explorer 9 Mozilla Firefox 17, 18, 19, 20 Google Chrome 23, 24, 25, 26 OL-27753-06 3 Chapter 1 Installing Videoscape Control Suite Services: Preparation Browser Requirements - Videoscape Control Suite 2.1, 2.5, and 3.0 Internet Explorer 9 Mozilla Firefox 5 Browser Requirements - Videoscape Control Suite 2.0 Internet Explorer 8 Internet Explorer 9 Mozilla Firefox 5 4 OL-27753-06 Install the Videoscape Control Suite Management Console Install the Videoscape Control Suite Management Console The Videoscape Control Suite management console (CMC) is the GUI infrastructure that is used to perform all other COP file installations and upgrades and to manage the Videoscape Control Suite (VCS) system. The management console .cop.sgn file must be installed before installing any other COP files. This section describes the procedure for installing the management console. Install the Videoscape Control Suite Management Console Complete the following steps: 1 Log in to the management node as the admin user. For example: ssh [email protected] Note: If the file platformconfig.xml alone was used, the cluster user and password were defined when platformconfig.xml was created. 2 3 OL-27753-06 If this is a manual installation, the user and password were defined during the installation. At the prompt, enter the following command to download the management console COP file to your management node: admin:file transfer secure-import [email protected]:Rel_2.5/Release17/cisco.conductor-cmc2.5-0-1122.cop.sgn The system should respond as shown in the following example: Valid entry Warning: Permanently added '209.165.201.0' (RSA) to the list of known hosts. [email protected]'s password: cisco.conductor-cmc-2.5-0-1122.cop .sgn 100% 3530MB 20.6MB/s 02:51 admin: After the file transfer has completed, enter the following to load the management console COP file: admin:file load cop cisco.conductor-cmc-2.5-0-1122.cop.sgn This operation takes 20-25 minutes to complete, during which time the system should respond as shown in the following example: admin:file load cop cisco.conductor-cmc-2.5-0-1152.cop.sgn Copying COP for Authentication Authenticating COP 5 Chapter 1 Installing Videoscape Control Suite Services: Preparation WARNING: Authenticate file cisco.conductor-cmc-2.5-0-1152.cop failed but overridden Extracting the file ... COP extraction completed, starting Install Tue Feb 12 12:07:59 EST 2013 - Installing CMC COP. Please wait ... Copying all rpms ... rpms copy done. host_name: csvm185177 Management Node. Stoping management service Stop if any mhm, linux_ha, cmc, mcc, mc, snmpd are running Loading CMC Libraries ... Firewall configuration verified. Cleanup cop and oracle Deploying database ... Database deployed. Creating database schema ... Database configuration completed. Start Lumos installation ... Installing CMC Application packages ... wcsadmin.sh found CMC Application installation completed. Patching IFM files ... CMC Application installing HA Support. CMC Application HA Support installed. Done patching IFM files. WCSAdmin class extracted and found adding oradb to servM service and start oradb adding cmc to servM service and start cmc adding cmc to servM service and start cmc done XMPDbUpdate start..!! XMPDbUpdate end..!! adding mc/mcc/snmpd to servM service restart servM to start all services No HA bulk sync indication Executed command: mkdir -p /var/log/active/installed_options/cisco.conductor-cmc-2.5-01152.cop. ret_val: 0 Tue Feb 12 12:40:16 EST 2013 - CMC COP Install Complete. WARNING: cisco.conductor-cmc-2.5-0-1152.cop Uninstall file does not exist admin: Note: If you are performing the Easy Install from the Videoscape Control Suite Installation and Upgrade Guide (part number OL-29939), complete the CMC installation and return to "Deploy the Videoscape Control Suite on Service Nodes" in that guide before continuing with these instructions. 6 OL-27753-06 Install the Videoscape Control Suite Management Console 4 OL-27753-06 After the installation has completed, go to https://<hostname>: Example: https://209.165.202.128, username: root, password: Public123 The home page displays the status of all nodes. 7 Chapter 1 Installing Videoscape Control Suite Services: Preparation Log in to the Management Console Important: If already logged in to management console, skip these steps and go to Create the SFTP User (on page 9). 1 Open a supported browser and enter the URL (https: <hostname of the Videoscape Control Suite Management host> or <hostname of the Videoscape Control Suite Management host>:8080) of the management console server. The login page of the management console appears. 2 8 In the CMC login page, enter your Username and Password. Then, click Login. The management console main page, showing the Videoscape Control Suite nodes, appears. OL-27753-06 Create the SFTP User Create the SFTP User The SFTP user is needed to install COP or ISO files on other nodes within the Videoscape Control Suite cluster. This is the user account used to transfer files to the other nodes and perform the installation. This user only has to be created once. This section describes the procedure for creating the SFTP User. Create the SFTP User Important: This procedure is only required if you have not already set up an SFTP account for Videoscape Control Suite. If you already have an SFTP account set up, you can skip this procedure. Note: Although the SFTP User field is blank after upgrading the CMC, if you try to create the same user, you will receive an error that the user already exists. If this occurs, create a new user with a different name. 1 In the management console main page, choose Administration > Users, Roles & AAA. The Change Password window opens. 2 Click SFTP User Account. 3 Enter the User Name and Password for the SFTP user. Note: Do not use "sftpuser" as the SFTP user name. 4 Click Submit. A message appears indicating that the SFTP user was created successfully. OL-27753-06 9 Chapter 1 Installing Videoscape Control Suite Services: Preparation Configure the Virtual Service Namespace and Service Instance A Virtual Service Namespace and Server Instance only have to be created for the ECS COP files prior to installation. The Service Virtual Namespace format is: cisco.dbds.ecs.<siteid>.<servicename> Example: cisco.dbds.ecs.cluster1.RegisterService Note: A Virtual Service Namespace and Service Instance do not need to be created for any COP files. They have been automated for all COP files. Configure the Virtual Service Namespace (Dynamic) 1 10 Choose Message Infrastructure > Service Infrastructure > Virtual Service > Create Dynamic VS. OL-27753-06 Configure the Virtual Service Namespace and Service Instance 2 Enter the necessary information, as follows: Category – Choose the appropriate option (XMPP, HTTP, RMI, HTTPS). Namespace – This field is automatically completed with the entry entered in the Name field. Admin JID – This field is automatically completed once the Service Instance (SI) entry has been created, or during install of the Service. Name – Enter the Name for the Virtual Service. For the ECS COP file, enter a name such as: cisco.dbds.ecs.cluster1.<service>. AccessPoint – If the Service has an access point, this field will be completed during installation of that Service. An example of a completed Virtual Service entry is shown below. 3 OL-27753-06 Click Save to save your entries. 11 Chapter 1 Installing Videoscape Control Suite Services: Preparation Configure the Virtual Service Namespace (Static) 1 Choose Message Infrastructure > Service Infrastructure > Virtual Service > Create Static VS. 2 Provide values for the following required fields: Note: Click the help icon (?) by each field to see the current rules for that parameter. Name – Enter a unique value. Admin JID – Enter a value if you want the client to be able to discover that status of the selected instances for this virtual service. Namespace – Enter a unique value. Admin State – Choose Enable or Disable. KeepAlive Interval – Enter a value from 1 through 30. Algorithm – Choose hash_from, roundrobin, or consistent_hash_from. Also enter information, if desired, into the following optional fields: 3 4 Access Point – Enter a unique value that begins with a character or digit. Click Save to complete the add operation for the new virtual service, or, click Reset to clear the fields. Click Back to return to the Virtual Service Management page. The virtual service will appear in the Virtual Service List in the Virtual Service Management page. Configure the Service Instance 1 2 12 Choose Message Infrastructure > Service Infrastructure > Service Instance > Create SI. Complete the necessary fields, as follows: Managed – This field is selected automatically. If this is not a Managed service, deselect this entry. Virtual Service’s Namespace – Choose the Virtual Namespace in the dropdown list of the Service for which the JID is added. Instance JID Name – Enter the JID for the Service Instance. HostName – Choose the Service Directory Name Space (SDNS) entry in the drop-down list. OL-27753-06 Configure the Virtual Service Namespace and Service Instance OL-27753-06 Password – Enter the Password for the Service Instance JID. Confirm Password – Re-enter the password for the Service Instance JID. Auto Binding JSM – This entry is selected automatically. Binding JSM – This entry is selected automatically. Auto Binding CM – This entry is selected automatically. Binding CM – This entry is selected automatically. Backup Binding CM – This entry is completed automatically. Accesspoint – Complete this entry if needed. 3 Version – This entry is completed automatically. Click Save to save your entries. The following pop-up message is displayed: 4 Click OK to proceed and save the entry. 13 Chapter 1 Installing Videoscape Control Suite Services: Preparation Verify the PubSub A service or feature (EPM or AM) publishes to a publish-subscribed (PubSub) node. An entity publishes information to a node at a PubSub service. The PubSub service pushes an event notification to all entities that are authorized to learn about the published information. This section describes the procedure for creating a PubSub entry if it was not created when you installed Videoscape Control Suite. Note: PubSub entry can be defined for creation in the cluster.xml file. For example: <component hostname="pubsub.features" name="ps-1" type="PS"/> 1 In the management console main page, choose Message Infrastructure > PubSub Subscribe. Is there a PubSub entry listed in the PubSub Service List that can be used for Services? If yes, go to Download the COP File Template and COP File (on page 17). If no, go to Add a PubSub (on page 14). Add a PubSub 1 2 3 4 5 6 7 14 In the management console page, choose Message Infrastructure > Message Fabric > Node/Router/Component. Choose the Msginfra node in the Node List on which the PubSub node belongs. The Router List appears. Choose the appropriate router in the Router List. Click XCP Web Controller. The Jabber XCP Controller window opens. Click Enter the XCP Controller Now. Enter the Username and Password (from the cluster file). Locate the Components area at the bottom of the window. OL-27753-06 Verify the PubSub 8 In the Add a new area, click PubSub. 9 Click Go to open the PubSub Configuration window. 10 Change the Configuration view to Advanced. Note: Locate this in the right side of the window. 11 Scroll down the page until you see Hostnames for this Component. 12 Place your cursor in the box at the end of the current entry, and press Enter to open a new line. 13 In the new line, enter pubsub.features. 14 Scroll to the bottom of the page and click Submit. The system returns you to the management console page. OL-27753-06 15 Chapter 1 Installing Videoscape Control Suite Services: Preparation 15 Scroll to the bottom of the page and click Restart the system. At the confirmation message, click OK. 16 After the system restarts, verify that the Status of all components is Running. 17 At the bottom of the page, click Log off and then close the window. 16 OL-27753-06 Download the COP File Template and COP File Download the COP File Template and COP File COP files are installed using COP file template (.tmp.xml) files and COP (.cop.sgn) files. These files must be downloaded from a central repository. This section describes the procedures for downloading the COP file template and COP file to your management console node. Download the COP File Template The COP file template can be downloaded two ways: from the desktop or through SFTP. This section provides instructions for both options. Template File Download From the Desktop 1 At the management console main page, choose Operate > Download. The Image Repository window opens. 2 Click Import. The Import Images window opens. 3 Click Desktop (provided you have downloaded the file to your desktop) and then Browse. Browse to the location of your COP file template. 4 Highlight (on your laptop) the COP file template and click Open. 5 Click Submit. A confirmation message appears. 6 Click OK in the confirmation message. Template File Download through SFTP 1 At the management console main page, choose Operate > Download. The Image Repository window opens. 2 Click Import. The Import Images window opens. 3 Click SFTP. The window expands to show Collection Options. 4 Enter the following information: 5 6 OL-27753-06 Server – This is the IP address of the server which holds the image repository. User Name – This is the user name associated with the server containing the image repository. User Password – This is the password associated with the server containing the image repository. Directory (full path) – This is the full directory path to the COP file. Image Name – This is the actual name of the COP file you want to download. Click Submit. A confirmation message appears. Click OK in the confirmation message. 17 Chapter 1 Installing Videoscape Control Suite Services: Preparation Download the COP File Note: A COP file can only be downloaded using SFTP. 1 In the management console main page, choose Operate > Download. The Image Repository window opens. 2 Click Import. The Import Images window opens. 3 Click SFTP. The window expands to show Collection Options. 4 Enter the following information: 5 6 18 Server – This is the IP address of the server which holds the image repository. User Name – This is the user name associated with the server containing the image repository. User Password – This is the password associated with the server containing the image repository. Directory (full path) – This is the full directory path to the COP file. Image Name – This is the actual name of the COP file you want to download. Click Submit. A confirmation message appears. Click OK in the confirmation message. OL-27753-06 2 Chapter 2 Install the NOSQLCB COP File This chapter provides you with the information you need to install the NOSQLCB COP file. The database of the NOSQLCB server is used by the following services or features: End Point Manager Operator Message Service Session Resource Manager ECS DBAccessService or Oracle/Postgres Note: The ECS DBAccessService can use the Oracle, NOSQLCB, or Postgres database. For configuration of the NOSQLCB server, see the configuration guide for the service or feature involved. In This Chapter OL-27753-06 Install the NOSQLCB COP File........................................................... 20 19 Chapter 2 Install the NOSQLCB COP File Install the NOSQLCB COP File 1 2 3 4 5 6 7 8 Download the NOSQLCB COP file as described in Download the COP File Template and COP File (on page 17). Choose Operate > COP Install to begin the COP file installation. Select the Nodes on which to install the COP file, then select the NOSQLCB file. Note: You can select all of the nodes you want to install the COP file on in this step. Click New Config Generation. Choose the node(s) on which to install the COP file on from the list of nodes in the COP Configuration Attributes, then click Generate Config. Note: If this is the first installation, you can install on multiple nodes at the same time. Result: A confirmation message appears. Click OK in the confirmation message to generate the configuration file. Click OK to return to the COP Install page. Choose the node(s) on which to install the COP file and the COP file that you would like to install. Then click COP Install from the COP Images To Install area. Note: If this is the first installation: You can install on multiple nodes at the same time. After the Service Account is created, you only install one node at a time. 9 You do not need to select the Config file. Result: A confirmation message appears. Click OK to start the COP installation. The status under COP install will change for the nodes selected for install. Notes: When the install completes, the status changes to SUCCESS. For first-time installations, install all NOSQLCB COP files before proceeding to the next step. 10 Choose Administration > Users, Roles & AAA > Service Account. 20 OL-27753-06 Install the NOSQLCB COP File 11 Select the nosqlcb Service Name, then click Modify. UserName – Enter the username for the NOSQLCB server. An example is Administrator. Password – Enter the password for the NOSQLCB servers. An example is Public123. Confirm Password – Re-enter the NOSQLCB password. Key – Enter the key to encrypt the NOSQLCB username and password. Confirm Key – Re-enter the NOSQLCB key. The following illustration shows an example of a completed Service Account entry: 12 After all entries have been created, click Create. OL-27753-06 21 Chapter 2 Install the NOSQLCB COP File 13 After the NOSQLCB has been configured, the Service Account Manager window appears as follows. The NOSQLCB COP file has been successfully installed. Install NOSQLCB UI Components Install the NOSQLCB UI components as follows: 1 Choose Operate > COP Install. 2 Choose the management node on which you will install the UI component. 3 Select the NOSQLCB COP file. 4 Click Install UI Components. A confirmation message appears. 5 Click OK. 6 Click OK. The CMC stops and takes you to the CMC login window. 7 Log in with root/Public123 and verify that the NOSQLCB Database menu item has been added under Services. Note: For NOSQLCB configuration procedures, see the Videoscape Control Suite Database User Guide (OL-28290). 22 OL-27753-06 3 Chapter 3 Install HornetQ This chapter provides instructions for installing the HornetQ messaging system. In This Chapter OL-27753-06 Install HornetQ...................................................................................... 24 23 Chapter 3 Install HornetQ Install HornetQ HornetQ is an open source asynchronous messaging system that is used for delivering messages between UHE components. HornetQ is currently packaged as a COP file. This section describes the procedure for installing HornetQ. Install HornetQ Note: See Notes Regarding the HornetQ COP File (on page 25), which follows this procedure, for information that may affect your HornetQ COP file installation. 1 Log in to the CMC user interface. 2 Download the COP and Template files for HornetQ. 3 Choose Operate > COP Install. A list of nodes is displayed. 4 Choose the node on which to install the HornetQ COP file. The COP images To Install screen becomes available. 5 Select the HornetQ COP file to install. The COP Image Config Files window becomes available. 6 Click New Config Generation to access the template required to generate the configuration information needed to install the HornetQ COP file. The COP Config window becomes available. Note: HornetQ COP Configuration includes the following: 7 Data Folder – The HornetQ data storage folder. Is Backup Server – Set only if Redundancy Enabled is set to "true." Set to true for backup HornetQ server instance, or false for master instance. Redundancy Enabled – If true, the backup/master hornetq server must be configured. Otherwise, enter false. In the COP Configuration Attributes section, choose the node on which to install HornetQ, then click Edit. Additional configuration parameters become available. 8 9 10 11 12 13 24 Redundancy Server – Set only if Redundancy Enabled is set to "true." Set to define the Host Alias / IP Address of master/backup HornetQ instance. Complete the fields if needed, then click Save to save your entries, or Cancel to ignore. Click Generate Config to generate the HornetQ configuration file. A confirmation message appears. Click OK. Click OK to return to the COP Install page. In the COP Install page, choose the node on which to install the HornetQ COP file. The COP Images to Install screen becomes available. Choose the HornetQ COP file you would like to install. The COP Image Config Files window becomes available. OL-27753-06 Install HornetQ 14 In the COP Images to Install page, click COP Install to initiate the COP installation process. A confirmation message appears. 15 Click OK. Another confirmation message appears. 16 Click OK. 17 Click OK to acknowledge the initiation. The HornetQ COP Install shows SUCCESS when it is completed. 18 Confirm that the HornetQ COP Install completes successfully. Notes Regarding the HornetQ COP File If the customer expects to deploy the HornetQ service in a separate environment between management traffic and service traffic, as root user, modify the modiservice.hornetq.host=<local ip address> parameter in the /opt/hornetq/hornetq/etc/config.properties file after the reboot. OL-27753-06 25 4 Chapter 4 Install the OMS COP File This chapter provides you with the information that you need to install the Operator Messaging Service (OMS) COP file. Prerequisites You must complete the following tasks before installing the OMS COP file: Install the NOSQLCB COP File (on page 19) Install HornetQ (on page 23) Install the UPM COP File (on page 31) Install the UPMCDA COP File (on page 35) Install the Message server, if needed (requires the IP address and ftpuser/password) In This Chapter OL-27753-06 Install the OMS COP File ..................................................................... 28 27 Chapter 4 Install the OMS COP File Install the OMS COP File Log on to the CMC 1 2 Open a supported browser and enter the URL of the management console server. The URL has the general form: https: <hostname of the Videoscape Control Suite Management host> or http: <hostname of the Videoscape Control Suite Management host> Result: The management console login page appears. Enter your Username and Password, and then click Login. The management console main page, showing the Videoscape Control Suite nodes, appears. Install the OMS COP File 1 2 3 4 5 6 In the management console main page, click Operate and then click COP Install. Choose the service node on which you want to install the COP file. The window updates to show a list of COP images to install. Note: If you are installing on multiple nodes, choose all of the nodes on which you want to install, or you can install them one node at a time. Choose the COP image you want to install. The window updates to allow for the configuration of the new image. Click New Config Generation. The COP Configuration page appears. Choose the service node on which you want to install the COP file. Enter the following information: PubSub Host Name – This is the host name of the PubSub component used by the Client Directory. OMS must use the same PubSub component in order to listen for the event from the Client Directory. TMS Server IP — This is the IP address of the TMS server node (optional). The service node on which you want to install the COP file TMS Server Port — This is the TMS server Port number (optional). 7 Click Save, and then click Generate Config. 8 Click OK to generate the configuration file. A pop-up confirmation message is displayed. 9 Click OK to return to the COP install page. 10 In the COP install page, choose the following: The OMS COP file to be installed The Node Configuration file that was just generated 11 Click COP Install. A confirmation message appears. 12 Click OK. A pop-up confirmation message is displayed. 13 Wait a few seconds for the COP Install Status column to display SUCCESS or IN_PROGRESS. 28 OL-27753-06 Install the OMS COP File 14 Wait for the installation to complete. A success message is displayed when the installation is complete. 15 If you did not select all nodes for the installation, repeat these steps for any remaining nodes. Note: Make sure that the OMS configuration files are the same for all nodes. Verify the OMS installation 1 2 3 4 Use SSH client to connect to the service node on which you have installed OMS already. Log in to the system by using the platform user name and password. The platform CLI appears. Enter utils service list, and then press Enter. The following screen is displayed: Verify that the OMS service is started. Note: If the OMS service has not started, reboot the node, or contact Cisco Services for further assistance. Notes Regarding the OMS COP File Installation If OMS over TMS is deployed and if the IP address of the TMS service node has changed from what it originally was, or is expected to change, use the root account to modify the tmsIP variable in the /opt/cisco/oms/conf/oms.xml file with the new IP address. Then, restart the OMS service. OL-27753-06 29 5 Chapter 5 Install the UPM COP File This chapter provides instructions for installing the COP file for the User Profile Manager (UPM). Prerequisites You must complete the following tasks before installing the UPM COP file: Install HornetQ (on page 23) Install the Oracle database and configure it to support UPM. See the Videoscape Control Suite Database User Guide (OL-28290) for details. In This Chapter OL-27753-06 Install the User Profile Manager COP File ........................................ 32 31 Chapter 5 Install the UPM COP File Install the User Profile Manager COP File Install the User Profile Manager COP File Note: See Notes Regarding the UPM COP File (on page 33), which follows this procedure, for information that may affect your UPM COP file installation. 1 Log in to the CMC user interface. 2 Download the COP and Template files for User Profile Manager (UPM). See Download the COP File Template and COP File (on page 17). 3 Choose Operate > COP Install. A list of nodes is displayed. 4 Choose the node on which to install the UPM COP file. The COP Images to Install area becomes available. 5 Choose the UPM COP file you would like to install. The COP Image Config Files window becomes available. Note: Choose the UPM Data COP file. 6 Click New Config Generation to access the template needed to generate the configuration information needed to install the UPM COP file. The COP Config screen becomes available. 7 Complete the fields in this window as follows: HornetQ Host – Enter the IP address of the node where HornetQ is installed. DB Port – Enter the Oracle database listening port for the Oracle database service. DB Service Name – Enter the Oracle database Service Name. DB User Password – Enter the password for the UPM user created in the Oracle database. Tablespace Name – Enter the name of the tablespace created to support UPM. DB Host – Enter the IP address or hostname of the Oracle database server that UPM will use for its database repository. UPM DB User – Enter the UPM database user created to support the UPM installation. JSM Topic — Enter the topic that UPM will use to support this installation. Examples are ‘UPM-SHAW’, ‘UPM-VOO’, and so on. 8 In the COP Configuration Attributes list of nodes, choose the node on which to install the UPM COP file, then click Generate Config. A confirmation message appears. 9 Click OK in the confirmation message. 10 Click OK to return to the COP Install page. 11 In the COP Install page, choose the node on which to install the UPM COP file. The COP Images to Install area becomes available. 32 OL-27753-06 Install the User Profile Manager COP File 12 Choose the UPM COP file that you would like to install. The COP Image Config Files window becomes available. 13 In the COP Images to Install area, click COP Install to initiate the COP installation process. A confirmation message appears. 14 Click OK. Another confirmation message appears. 15 Click OK. Another confirmation message seeking acknowledgment of the initiation appears. 16 Click OK to acknowledge the initiation. Note: The UPM COP Install shows SUCCESS when it is completed. 17 Confirm that the UPM COP Install has completed successfully. Notes Regarding the UPM COP File If the IP address of the UPM-related service node has changed or needs to be changed from how it was originally configured, execute the following commands from the admin command line interface (CLI). Follow whatever prompts result from the commands. a Enter set network ip eth0 <new IP address> <netmask> and press Enter. Note: The service node restarts after you make the change. b Wait for the node to restart. Then, enter show network eth0 and press Enter to verify the new IP address. OL-27753-06 33 Chapter 5 Install the UPM COP File c Enter set network hostname <same hostname> and press Enter to configure the hostname. If the IP address of the UPM-related service node has changed or needs to be changed from how it was originally configured, as root user, modify the service.queue.connections.1.host=<new hornetq address> variable in the /opt/nds/upm/etc/config.properties file. If the customer expects to deploy the UPM service in a separate environment between management traffic and service traffic, as root user, modify the expected Ethernet interface of the HornetQ service in the service.upm.http.host file. Then, manually restart the UPM service. Optimize UPM Performance After the UPM COP has been installed, optimize its performance by modifying ( as the root user) some parameters in the /opt/nds/upm/etc/config.properties file : # the minimal count of listening threads service.upm.http.minThreads=100 # the maximal count of listening threads service.upm.http.maxThreads=1500 database.connectionPool.maxLimit=400 database.connectionPool.maxStatementsLimit=400 34 OL-27753-06 6 Chapter 6 Install the UPMCDA COP File This chapter provides instructions for installing the COP file for the User Profile Manager Adaptor (UPMCDA), including the necessary preliminary steps. Prerequisites You must complete the following tasks before installing the UPMCDA COP file: Install HornetQ (on page 23) Install the UPM COP File (on page 31) In This Chapter OL-27753-06 Install the UPMCDA COP File............................................................ 36 35 Chapter 6 Install the UPMCDA COP File Install the UPMCDA COP File Install the UPMCDA COP File Installing the UPMCDA COP File involves first installing the COP file itself, and then configuring the UPM adaptor. This section provides instructions for both procedures. Install the COP File 1 Choose Operate > Download to download the UPMCDA COP file. 2 Choose Operate > COP Install. 3 Choose the node(s) upon which to install the UPMCDA COP file. The COP Images to Install area is displayed. 4 Choose the UPMCDA COP file to be installed, and then click New Config Generation. Result: The COP Config window for UPMCDA is displayed. 5 Configure these fields: 6 7 8 36 UPM Host – Enter the IP address of the host where UPM is installed. HornetQ Host – Enter the IP address of the host where HornetQ is installed. Pubsub Service – Enter the PubSub service for UPMCDA. Note: All services that interact with UPMCDA must use the same PubSub service that UPMCDA uses. Choose the node upon which to install the UPMCDA COP file in the list of nodes, and then click Generate Config. Result: A confirmation message appears. Click OK to generate the configuration file. A pop-up confirmation message is displayed. Click OK to return to the COP Install page. OL-27753-06 Install the UPMCDA COP File 9 Choose the node upon which to install the UPMCDA COP file, and then choose the COP file to install. 10 Click COP Install. Result: A confirmation message appears. 11 Click OK to start the COP installation. The status under COP install will change for the node selected for install. Note: Once the install has completed, the status changes to SUCCESS. 12 Choose Message Infrastructure > Service Instance and verify that the ClientDirectory and UPMAdaptorAdmin instances are IS. Configure the UPM Adaptor Configure the UPM Adaptor as follows: 1 Choose Services > UPM Adaptor Settings. 2 Select the UPM adaptor admin, then click Edit. The UPM Adaptor Instance Configuration is displayed. 3 Update the following fields on this page: 4 OL-27753-06 Component Mode – Set this to True for components (EPM, OSM, and so on) to use User Profile Manager Adaptor. Component Name – The Open Port jidmap router defined in the Open Port Configuration step above. Component Password – The password for the component defined in Component Mode. Component Open Port IP – IP address of the Connection Manager configuration. Component Port – Port of the Connection Manager configuration. Pubsub Enable – Enable the PubSub (Data changed notify) function. Debug flag – The debug flag, set to true to enable, false to disable; the log file is under /opt/cisco/cd/log. WFE Mode – Enables or disables the WFE function, default is false. Auto Provision – Set this to True for the components (EPM, OSM, and so on) you want to use. Pubsub JID – The PubSub host name that the client uses to subscribe to the data change notification. WFE IP – WorkFlow engine service IP address. WFE Create User URL – URL for createUser. WFE Create Account URL – URL for createAccount. WFE Create Device URL – URL for createDevice. WFE Delete User URL – URL for deleteUser. WFE Delete Account URL – URL for deleteAccount. WFE Delete Device URL – URL for deleteDevice. Click Save, then confirm that OpenPort changes to a green (running) state. 37 Chapter 6 Install the UPMCDA COP File Preparation for UPMCDA Configure the XCP Controller This procedure prepares the UPMCDA service for communications with the XCP controller. 1 Log in to the XCP Controller at https://<ip CMC>:7301. 2 Log in to the CMC user interface. 3 Choose Message Infrastructure > Node/Router/Component. Then, choose the following: 4 5 38 The Active Management node The Active Router The XCP Web Controller Click Enter the XCP Controller now. A message is displayed prompting you to log in. Enter admin as the User Name, as well as the admin user’s Password, as defined in the cluster or platform file. Then, click OK to log in. OL-27753-06 Install the UPMCDA COP File Configure Connection Manager (CM) Configure the CM as follows: 1 Change the Configuration View in the upper-right corner of the window from Basic to Advanced. 2 In the Components section of the UI, locate Connection Manager in the Description column. In the Actions column for this item, click Edit. 3 OL-27753-06 The CM opens for editing. Configure the Adaptor for port 5223. Note: If this port does not exist, you will need to add an additional XMPP Director. 39 Chapter 6 Install the UPMCDA COP File 4 Scroll down and locate JSM Command Processor. Under Actions for this item, click Details. The JSM Command Processor Configuration for this item opens. 5 6 7 8 9 40 If only one XMPP Director is listed, create a second XMPP Director. Then click Go next to the second XMPP Director. The XMPP Director Configuration window opens. Change the Port to 5223, and then click Submit. Click SSL Settings, and then change the SSL Mode from tls to tls-required. Click Require valid Client side certificates, and then copy the entry in Full path to SSL cert file or directory and paste it into the field for Full Path to root of CA cert file. Change the last part of the path from tls to host-key.pem, as shown below. OL-27753-06 Install the UPMCDA COP File 10 Scroll down and set Use X509 Certificate Authentication and Use logical JidMapping to Yes. 11 Scroll to the bottom and click Submit to save the changes. The system returns you to the JSM Command Processor Configuration window. 12 Write down the JSMCP Configuration Component IP, Port, and Password. 13 Scroll down and click Submit. The system returns you to the XCP Controller main window. 14 Scroll to the bottom and click Submit. 15 Click Restart the system in the XCP Controller main window to commit your changes. A confirmation message appears. 16 Click OK. All components will stop and then start, and will all be in a running state. OL-27753-06 41 Chapter 6 Install the UPMCDA COP File Configure Jabber Session Manager Configure Jabber Session Manager to support UPMCDA as follows: 1 In the Router section at the top of the XCP Controller main window, click Edit. The JSM Configuration window opens. 2 3 42 Click to place a check-mark in the mod_presence_mirror and mod_presence_bcc fields. Scroll down to Automatically provision new users and set this field to Yes. OL-27753-06 Install the UPMCDA COP File 4 Scroll down to Mirroring Presence, select it, and then enter jidmap.msginfra in the Copy (BCC) packets text box. 5 Scroll down and click Submit. The system returns you to the XCP Controller main window. Scroll to the bottom of the window and click Submit. Click Restart the system in the XCP Controller main window to commit your changes. A confirmation message appears. Click OK. All components will stop and then start, and will all be in a running state. 6 7 8 Create the Open Port Create the Open Port to support UPMCDA as follows: 1 Choose Components > Add a New. 2 Click OpenPort, and then click Go. A pop-up entry field for the OpenPort Component is displayed. 3 4 OL-27753-06 Enter jidmap as the OpenPort Component, and then click OK. The OpenPort Configuration window opens. Scroll down and click XDB; then, enter http://www.jabber.com/protocol/jidmapping in the Namespace Filters field. 43 Chapter 6 Install the UPMCDA COP File 5 Enter an asterisk (*) in the Host(s) field. 6 Scroll down and click Submit. The system returns you to the XCP Controller main window. Scroll to the bottom of the window and click Submit. Click Restart the system to commit your changes. A confirmation message appears. Click OK. All components will stop and then start, and will all be in a running state. 7 8 9 Add the UPMCDA JID to Admin User of JSM For user and roster provisioning, it is necessary to add the UPM Adaptor Service JID as an admin user of the client JSM. Complete the following steps to add the UPMCDA JID: 1 Log in to the CMC with the root user ID and password. 2 Choose Message Infrastructure > Node/Router/Component. 44 OL-27753-06 Install the UPMCDA COP File OL-27753-06 3 Choose one of the client JSM Nodes (JUSM with "inforsvc=0" in the cluster.xml file). 4 Choose the node, and then choose the Router. 45 Chapter 6 Install the UPMCDA COP File 46 5 Click XCP Web Controller to open the Jabber XCP window. 6 7 Log in using the admin User Name and Password. Check the configuration mode and, if necessary, set it to Advanced by selecting in the drop-down list of the Configuration View menu items at right. 8 9 Click Edit in the Router section, at the top of the page. Scroll down to JSM Configuration, click Jabber Administrators, and add the UPM Adaptor JID. OL-27753-06 Install the UPMCDA COP File 10 Scroll to the bottom of the page and click Submit to save your entry. You are returned to the main page. 11 Click Restart the System to make your changes permanent. A confirmation message appears. 12 Click OK to confirm. 13 Click Logoff to log out of the Jabber XCP Controller. Configure the UPMCDA JID 1 Log in to the CMC. 2 Choose Message Infrastructure > Client Facing Configuration. 3 Click Session Manager. The Session Manager window appears. 4 In the Admin JID field, input the JID of the client directory that was created during UPMCDA installation. 5 OL-27753-06 Click Save. 47 Chapter 6 Install the UPMCDA COP File Notes Regarding the UPMCDA COP File If you have changed the HornetQ and UPM IP addresses, the following parameters also need to be changed: The service.queue.connections.1.host=<new HornetQ IP address> The cdir.upm.service.1.host=<new UPM IP address> These parameters are in the /opt/cisco/upmcda/META-INF/config.properties file. UPMCDA Post-Installation Considerations These steps are necessary for communication with the following services: EPM, AM, BOA, and OMS Configure the XCP Controller, a Web-based interface that lets you configure and view the current state of your XCP server Configure the Connection Manager to support UPMCDA Configure Jabber Session Manager to support UPMCDA Create the Open Port needed to support UPMCDA 48 OL-27753-06 7 Chapter 7 Install the JBoss COP Files Introduction The JBoss COP files consist of the following COP files. Endpoint Manager Filer (EPM Filer) Endpoint Manager Alert Manager ECS COP files BillingAdaptor These files all run under the JBoss umbrella, which means that JBoss has to be stopped and restarted if any of these services are be started, stopped or restarted. In This Chapter OL-27753-06 Installing the EPM Filer COP File....................................................... 50 Install the EPM COP File ..................................................................... 52 Install the AlertManager COP File ..................................................... 54 Install the ECS COP Files ..................................................................... 57 Install the BillingAdaptor (BOA) COP File ....................................... 64 49 Chapter 7 Install the JBoss COP Files Installing the EPM Filer COP File The following COP file installation prerequisites must be met before you can install the Endpoint Manager (EPM) Filer COP file: Install HornetQ (on page 23) Install the UPM COP File (on page 31) Note: The HornetQ and UPM COP files can be the standalone versions that are part of the UHE suite of software. Install the UPMCDA Cop File (on page 35) Follow these instructions to install the EPM Filer COP file: 1 Once downloaded, in the CMC UI Main Menu, choose Software > Operate > COP Install. 2 From COP Install > Videoscape Control Suite Nodes, choose the node upon which to install the EPM Filer COP file. 3 From COP Install > COP Images to Install, choose the COP file to install (cisco.conductor-epmfiler-3.5-x-x.cop.sgn) 4 From COP Install > COP Images Config Files, click New Config Generation to configure the EPM Filer COP file for installation. Result: The COP Config page is displayed for the EPM Filer COP file. 5 Complete the entry: 6 7 8 9 10 11 12 13 14 50 Svc PubSub: Enter the PubSub for EPM, such as pubsub.features. Note: This PubSub must be already created. From COP Config > COP Configuration Attributes, choose the node(s) upon which to install the EPM Filer file. Click Edit. Enter the FILE STORE PATH and click Save. From COP Config > COP Configuration Attributes, click Generate Config to generate the configuration files for the EPM Filer install. Result: A message is displayed, asking Do you really want to generate selected configuration file(s)?. Click OK to generate the configuration files. Result: A message is displayed: Node Configuration file(s) generated successfully. Do you want to go back to COP Install page? Click OK to generate the config file and return to the COP Install page. In the COP Install page, choose the node upon which to install the EPM COP file from the Videoscape Control Suite nodes. From COP Install > COP Images to Install, choose the COP file to install. From COP Install > COP Image Config Files (bottom UI), choose the Config file generated for EPM for that node. From COP Install > COP Images to Install (middle UI), click COP Install. OL-27753-06 Installing the EPM Filer COP File 15 Click OK to confirm. Result: A message is displayed: COP Install initiation is successful. 16 Click OK. Result: In the COP Install UI, under COP Install Status, you will see the status change to IN_PROGRESS, while the install is going on. This will change to SUCCESS once the install is complete. 17 (Optional) To install EPM Filer for High Availability, install the same version of EPM Filer on another Service node. The EPM Filer will be installed in an activeactive HA scenario. OL-27753-06 51 Chapter 7 Install the JBoss COP Files Install the EPM COP File You must complete the following tasks before installing the EPM service: Install HornetQ (on page 23) Install the UPM COP File (on page 31) Note: The HornetQ and UPM COP files can be the standalone versions that are part of the UHE suite of software. Install the UPMCDA COP File (on page 35) Install the EPM Filer COP File (on page 50) Follow these instructions to install the EPM COP file. 1 Once downloaded, in the CMC UI Main Menu, choose Software > Operate > COP Install. 2 From COP Install > Videoscape Control Suite Nodes, choose the node upon which to install the EPM COP file. 3 From COP Install > COP Images to Install, choose the COP file to install (cisco.conductor-endpointManager-3.5-x-x.cop.sgn) 4 From COP Install > COP Images Config Files, click New Config Generation to configure the EPM COP file for installation. Result: The COP Config page is displayed for the EPM COP file. 5 Complete the entry: 6 52 Datastore Primary IP Address: Enter the IP address for one of the NOSQLCB nodes. Datastore Secondary IP Address: Enter a different IP for one of the NOSQLCB nodes. Datastore Admin ID: Enter the Admin ID for the NOSQLCB server, usually Administrator. Datastore Admin Password: Enter the Admin password for the NOSQLCB server, usually Public123. Datastore EPM User ID: Enter the User ID for the EPM NOSQLCB database, such as epmdata. Datastore Password: Enter the password for the EPM User ID entered above, such as cisco123. Datastore EPM RamQuota: Enter the EPM database RAM quota size in MB; default is 2000. Svc PubSub: Enter the PubSub for EPM, such as pubsub.features. Note: This PubSub must be already created. UPM Virtual Svc: Enter UPM. File Proxy Server: Enter the IP address for the File Proxy server. From COP Config > COP Configuration Attributes, choose the node(s) upon which to install the EPM file. OL-27753-06 Install the EPM COP File 7 8 9 10 11 12 13 14 15 16 OL-27753-06 From COP Config > COP Configuration Attributes, click Generate Config to generate the configuration files for the EPM install. Result: A message is displayed: Do you really want to generate selected configuration file(s). Click OK to generate the configuration files. Result: A message is displayed: Node Configuration file(s) generated successfully. Do you want to go back COP Install page? Click OK to generate the config file and return to the COP Install page. In the COP Install page, choose the node upon which to install the EPM COP file from Videoscape Control Suite nodes. From COP Install > COP Images to Install, choose the COP file to install. From COP Install > COP Image Config Files (bottom UI), choose the Config file generated for EPM for that node. From COP Install > COP Images to Install (middle UI), click COP Install. Click OK to confirm. Result: A message is displayed: COP Install initiation is successful. Click OK. Result: In the COP Install UI, under COP Install Status, you will see the status change to “IN_PROGRESS”, while the install is going on. This will change to “SUCCESS” once the install is complete. (Optional) To configure EPM for HA, install a second instance of EPM on another Service node, using the same parameters used to install the first instance. EPM will act in an active-active High Availability configuration. 53 Chapter 7 Install the JBoss COP Files Install the AlertManager COP File Overview of the AlertManager Service The AlertManager (AM) service runs under JBoss. One of the JBoss functions is to manage database connectivity. AM requests connections from JBoss to access the database. Other than this, all database activity is between JBoss and Oracle. Prior to the installation of AM, a user must be defined to Oracle for use by AM. The following command is used to defined this user : grant resource, connect to csamdb1 identified by <csamdb1_password>; If the user needs to be changed it is easiest to drop, and then redefine, the user: drop user csamdb1 cascade; This should be done only if needed, for example to correct a password or if some extreme condition arises. At AM installation, there are four fields that the installer configures for JBoss connectivity to Oracle. These are : Oracle hostname or IP address Oracle listening port number Oracle service name Oracle user password (the password <csamdb1_password> of the csamdb1 user defined in Oracle) Although these fields are found as part of the AM installation, it is important to know that these items are used by JBoss only. They are part of the installation of AM because AM relies on JBoss communicating with the correct Oracle instance, using the correct schema and user. Once these values are initially set, any changes made to the values for JBoss, or for re-creating the Oracle user, requires a JBoss restart. This is not an AM requirement; this is a JBoss requirement. For this reason, it is important that care be used when entering this data, because the JBoss restart effects other services running under JBoss, not simply AM. Additionally, if the Oracle user is dropped, the database connection is impacted, as well. If a connection exists while a user is dropped and then recreated, a JBoss restart is required. If root access is not available to the service instance running AM, the JBoss CLI may be used to alter the values (without a new AM install), but a JBoss restart is still required. In summary, AM relies on JBoss and Oracle to function correctly. Any changes effecting Oracle and/or JBoss resources used by AM require a JBoss restart. 54 OL-27753-06 Install the AlertManager COP File Before You Begin The Alert Manager COP file has a filename similar to the following: cisco.conductor-alertManager-3.5-x-x.cop.sgn where version is listed as x.x.x.x showing the version number of the Videoscape Control Suite. The Template file has a filename similar to the following: cisco.conductor-alertManager-3.5-x-x.tmp.xml where version is listed as x.x.x.x showing the Videoscape Control Suite version number. The Oracle database must be configured to support AlertManager. Run the following command while logged in to the Oracle server as the Oracle user, in order to log in as the sysdba user: grant resource,connect to csamdb1 identified by <csamdb1 user password>; You will need the following information when you install the AlertManager: - Oracle Host IP for the database instance - Oracle database host port - Oracle database instance SID/Service Name - AM user PubSub name - Oracle csamdb1 user password If you need ZIP to FIPS conversion, the following COP files must be installed: OL-27753-06 - HornetQ (on page 23) - User Profile Manager (on page 31) (UPM) Note: The HornetQ and UPM COP files can be the standalone versions that are part of the UHE suite of software. - User Profile Manager Adaptor (on page 35) (UPMCDA) - Location Service Data (on page 90) - Location Service (on page 91) - Work Flow Engine (on page 74) (WFE) 55 Chapter 7 Install the JBoss COP Files Follow these instructions to install the AlertManager COP file: 1 Download the AlertManager COP file using Operate > Download. 2 Install the AlertManager COP file. a Choose Operate > COP Install. b Choose the nodes upon which you would like to install the AlertManager COP file, and then choose the AlertManager file. c Click New Config Generation. 3 Complete the entries: 4 5 6 7 8 audio file conversion target extension (DVS168 only): Options are wav, mp3, or ogg. Location code type: Options are FIPS (US) or SGC (Canada). Unassigned fips to all pub sub flag: Options are true or false. Create a pubsub node for ECS: Options are Y or N. DB node: Enter the IP address of the Oracle database host or the hostname. DB Port: Enter the Oracle database listening port. Service Name: Enter the Oracle Service Name. AM user pubsub: Enter the PubSub for AlertManager. This should be the same PubSub used for UPMCDA). DB user password: Enter the csamdb1 password. Choose the node upon which you would like to install the AlertMAnager COP file from the list of nodes in the COP Configuration Attributes section. Then, click Generate Config to generate the AlertManager configuration file. A confirmation message appears. Click OK to generate the configuration file. Click OK in the message that states that the file was generated successfully. The COP Install page appears. Choose the node upon which you would like to install the AlertManager COP file. Then, choose the COP file that you would like to install, and click COP Install. Click OK in the node selection confirmation message. Click OK to confirm your intent to install the COP file. A message indicating Success will appear after the COP file has successfully installed. Configure Alert Manager High Availability 1 2 56 Follow the same procedure that you used to install the Alert Manager COP file, but choose a different service node -- a service node upon which Alert Manager is not already installed. Install Alert Manager on this newly selected node. Note: The second AM service instance will not show up in the Service Instance list until AM fails over and the secondary node becomes the primary node. When this occurs, the current active AM node will change its state to OOS (Out of Service). OL-27753-06 Install the ECS COP Files Install the ECS COP Files You must complete the following task before installing the ECS COP files: Install the NOSQLCB COP File (on page 19) (if using the NOSQLCB database) To create a database user for the ECS installation, on the Oracle server, log in to Oracle and create the ECS user: 1 Log in to the Oracle server. 2 Change to the Oracle user: su - oracle 3 Log in to Oracle: sqlplus / as sysdba 4 Create the ECS user: grant connect, resource to ECS123 identified by <user password>; 5 Exit from Oracle: exit 6 Log out the Oracle user: exit 7 Log out of the Oracle server: logout Install the ECS DBAccessService COP File 1 2 3 4 5 6 Choose Operate > Download to download the ECS DBAccessService COP file. Choose Operate > COP Install to begin installation of the ECS DBAccessService COP file. Choose the nodes on which to install the ECS DBAccessService COP file, then choose the ECS DBAccessService file. Click New Config Generation. Choose the nodes on which to install the ECS DBAccessService COP file in the list of nodes in the COP Configuration Attributes, and then click Edit. Complete all of the following fields: CB IP1 – NOSQLCB server IP or “-“ if using the Relational Database. CB Admin User Name – NOSQLCB Administrator User Name, example: Administrator or “-“ if using the Relational Database. CB Admin Password – NOSQLCB Administrator Password, example: Public123 or “-“ if using the Relational Database. CB IP2 – NOSQLCB server IP 2 or “-“ if using the Relational Database. Note: If you cannot enter a dash during the configuration generation, edit the configuration file after generating it, and add the dash then. OL-27753-06 57 Chapter 7 Install the JBoss COP Files Bucket Name – ECS Database NOSQLCB bucket name, example: dbbucket or “-“ if using the Relational Database. Bucket Password – ECS Database NOSQLCB bucket password, example: cisco123 or “-“ if using the Relational Database. CB App Port – The NOSQLCB Administrator Port, normally 8091 or “-“ if using the Relational Database. CB Data Port – The NOSQLCB Client Application Port, normally 8092 or “-“ if using the Relational Database. Relational Database Type – Choose either “postgresql” or “oracle” in the drop down. Database, or Instance Name – Enter the database name if postgres or the SID if using oracle. Database Server IP – Enter the IP address of the Database server. Database User Password – Enter the database user password. Database Listening Port – Enter the database listening port. Database User Name – Enter the database user you have created for either the postgres or oracle database. Version – Enter the ECS version number, normally 1.0.0. ClusterID – Enter the clusterid for the ECS DBAccessService COP file, this field is limited to 8-characters/numbers, ex. cluster1. 7 8 9 10 11 12 13 58 ECS PUBSUB SERVICE NAME - The name of the PubSub service domain for the ECS to register with, ex. pubsub.features Click Save to save your entries. Click Generate Config to generate the ECS DBAccessService config file. A confirmation message appears. Click OK to generate the configuration file. Click OK to return to the COP Install page. Choose the node on which to install the ECS DBAccessService COP file, choose the COP file to install. Click COP Install from the COP Images to Install area. A confirmation message appears. Click OK to start the COP installation. The status under COP install changes for the nodes selected for install. When the install completes, the status changes to SUCCESS. OL-27753-06 Install the ECS COP Files Install the ECS RegisterService COP File Prerequisites You must complete the following tasks before installing the ECS RegisterService COP file: Install the ECS DBAccessService COP File (on page 57) Install the NOSQLCB COP File (on page 19) Install the ECS RegisterService COP File 1 Download the ECS RegisterService COP file using Operate > Download. 2 Choose Operate > COP Install. 3 Choose the nodes upon which you would like to install the ECS RegisterService COP file, and then choose the ECS RegisterService file. 4 Click New Config Generation. 5 Choose the nodes upon which you would like to install the ECS RegisterService COP file, from the list of nodes in the COP Configuration Attributes window. Then, click Edit. 6 Edit these fields and then click Save. ECS AUTO ACCEPT: Enter True or False to automatically register an EC. ECS GROUP ID: Enter the ECS group/cluster ID, the same as was entered when the ECS DBAccessService was installed. 7 Click Generate Config to generate the ECS RegisterService config file. A confirmation message appears. 8 Click OK to generate the configuration file. 9 Click OK in the message that says that the file was successfully generated. 10 Choose the nodes upon which you would like to install the ECS RegisterService COP file, and then choose the COP file you would like to install. 11 Click COP Install in the list of COP Images to Install. 12 Click OK in the confirmation message. The COP file begins to install. Note: Once the install has completed, a SUCCESS message is generated. Install the ECS UI Component 1 2 3 OL-27753-06 Choose the management node upon which you would like to install the ECS UI component. Choose the ECS RegisterService COP file, and then choose Install UI Component in the COP Install menu. Result: The ECS UI Component installs and the Management UI logs out to the CMC login window. Log in with CMC credentials and resume operations. 59 Chapter 7 Install the JBoss COP Files Install the ECS Reports DiscoveryService COP File Complete the following steps to install the ECS Reports DiscoveryService COP file. 1 Choose Operate > Download to download the ECS ReportsDiscoveryService COP file . 2 Choose Operate > COP Install to initiate the ECS ReportsDiscoveryService COP file installation. 3 Choose the node(s) on which to install the ECS ReportsDiscoveryService COP file; then, choose the ECS ReportsDiscoveryService file to install. 4 Click New Config Generation. 5 Choose the nodes upon which you would like to install the ECS ReportsDiscoveryService COP file from the list of nodes in the COP Configuration Attributes, and then click Edit. 6 Complete the following entries on this page, and then click Save. ECS GROUP ID: Enter the ECS group/cluster ID, the same as was entered when ECS DBAccessService was installed. CREATE STARTUP LIST: (Optional) Enter yes or no. Interval for Re-query: Enter the re-query interval for Report Discovery; intervals are 3, 5, 10, 15, and 30 seconds. 7 Click Generate Config to generate the ECS ReportsDiscoveryService config file. A confirmation message appears. Click OK to generate the configuration file. 8 Click OK in the message that appears that states that the node Configuration file was successfully generated. 9 Choose the node upon which you would like to install the ECS ReportsDiscoveryService, and then choose the COP file you would like to install. 10 Click COP Install. 11 Click OK in the confirmation message. The status under COP install changes for the node selected for the install. When the install completes, the status changes to SUCCESS. Install the OAMService, the RPSService, and the LoadPIMSService COP Files The OAMService, the RPSService, and the LoadPIMSService COP files all install similarly. Follow this procedure to first install the OAMService COP file, then the RPSService COP file, and then the LoadPIMSService COP file. 1 Choose Operate > Download to download the ECS OAMService COP file. 2 Choose Operate > COP Install to initiate the COP file installation process. 3 Choose the nodes on which to install the ECS OAMService COP file, then choose the ECS OAMService file. 4 Click New Config Generation. 60 OL-27753-06 Install the ECS COP Files 5 6 Choose the nodes on which to install the ECS OAMService COP file from the list of nodes in the COP Configuration Attributes, then click Edit. Complete the following field: 7 8 9 10 11 12 13 ECS Group ID – Enter the clusterid for the ECS OAMService COP file; this field is limited to 8-characters/numbers, such as cluster1. Click Save to save your entries. Click Generate Config to generate the ECS OAMService config file. A confirmation message appears. Click OK to generate the configuration file. Click OK to return to the COP Install page. Choose the node on which to install the ECS OAMService COP file, then choose the COP file to install, then click COP Install from the COP Images To Install area. Click OK to start the COP installation. The status under COP install changes for the nodes selected for install. When the install completes, the status changes to SUCCESS. Repeat this procedure to install the RPSService COP file and then again to install the LoadPIMSService COP file. Install the ECS CPEManagement COP File Prerequisites The following COP files must be installed prior to installing the ECS CPEManagement COP file: HornetQ (on page 23) UPM (on page 31) Install the ECS CpeManagement COP File 1 2 3 4 5 OL-27753-06 Choose Operate > Download to download the ECS CpeManagement COP file. Choose Operate > COP Install to begin installation of the ECS CpeManagement COP file. Choose the nodes on which to install the ECS CpeManagement COP file, then choose the ECS CpeManagement file. Click New Config Generation. Choose the nodes on which to install the ECS CpeManagement COP file from the list of nodes in the COP Configuration Attributes, then click Edit. 61 Chapter 7 Install the JBoss COP Files 6 Configure the following field: ECS GROUP ID: Enter the ECS group/cluster ID, the same ID that was entered when the ECS DBAccessService COP file was installed. UPM Host: Enter the IP address of the UPM host (the UPM COP file). 7 Click Save to save your entries. 8 Click Generate Config to generate the ECS CPEManagement config file. 9 Click OK to generate the configuration file. 10 Click OK to return to the COP Install page. 11 Choose the node on which to install the ECS CPEManagement COP file, then choose the COP file to install, then click COP Install from the COP Images To Install area. 12 Click OK to start the COP installation. The status under COP install changes for the nodes selected for install. When the install completes, the status changes to SUCCESS. ECS CPEManagement UI Component 1 2 3 4 Select the management node upon which you would like to install the ECS CPEManagement UI component. Select the ECS CPEManagement COP file. Click Install CPEManagement. Result: The ECS CPEManagement component installs and the Management UI logs out to the CMC login window. Log in with CMC credentials and resume operations. Install the ECS EASService COP File 1 2 3 62 Choose Operate > Download to download the ECS EASService COP file. Install the ECS EASService COP file: a Choose Operate > COP Install. b Select the nodes upon which you would like to install the ECS EASService COP file and then select the ECS EASService file. c Click New Config Generation. Supply data to the following fields: Target Market — Enter either USA or Canada. Pubsub Domain — Enter the PubSub created when you deployed the message infrastructure on the Infra node. ECS Group ID — Enter the ECS Group ID for your system. Important: This must be the same ECS Group ID used for the DBAccessService. OL-27753-06 Install the ECS COP Files Location Server URL — Enter the URL for the Location Server node. This is usually the IP address of the service node where the Location Server is installed. Example: http://209.165.200.222:8080 DVS-168 Recipient IP — Enter the IP address of where the DVS-168 message should be sent. This is usually the service node where the AlertManager Service is installed. Example: 209.165.200.223 DVS-168 Recipient Port — Enter the port number associated with the recipient IP address. Example: 8080 Send Alert to All Destinations — Enter Yes or No. 4 5 6 7 8 9 OL-27753-06 Send SCTE 18 as forcetune — Enter Yes or No. DTACS/EC Frequency Plan — Enter Standard, IRC, or HRC. Select the node on which to install the COP file and then click Generate Config. A confirmation message appears. Click OK. The configuration file is generated and a message indicating the successful generation appears. Click OK. The system returns you to the COP Install page. Select the node on which to install the COP file and then select the COP file to install. Click COP Install. A confirmation message appears. Click OK to begin the installation. The status changes for the nodes selected for the install and a SUCCESS status appears after the installation has completed. 63 Chapter 7 Install the JBoss COP Files Install the BillingAdaptor (BOA) COP File You must install the following COP files before installing the BOA COP file: HornetQ (on page 23) (COP file Version 2.2.14-3 for Charter DCAS) HornetQ (Standalone Version 2.2.14-4 for Shaw; Standalone Version 2.2.14-6 for Verizon) UPM Standalone Important: The Charter DCAS installation requires that the COP file versions of HornetQ (on page 23) and UPM (on page 31) to come from the Conductor 3.5 release. Required ECS COP Files for Rogers and Charter Installations ECS DBAccessService COP File (on page 57) ECS RegisterService COP File (on page 58) ECS LoadPIMS COP File (on page 60) ECS CPEManagement COP File (on page 61) Complete the following steps to install the Billing Adaptor COP file. 1 Choose Operate > Download to download the BillingAdaptor COP file. 2 Choose Operate > COP Install to initiate the BillingAdaptor COP file installation. 3 Choose the node(s) on which to install the BillingAdaptor COP file, then choose the BillingAdaptor file to install. 4 Click New Config Generation. 5 Complete the following entries on this page: 64 Group ID for Explorer Controllers — Enter the ECS group/cluster ID, the same as was entered when ECS DBAccessService was installed. Notes: – This field must be entered, but this can be a bogus entry if ECS is not needed on the system. – The Group/Cluster ID cannot be longer than 8 characters/numbers. UPM IP Address — Enter the IP address of where the UPM COP file is installed. Store authorizations in UPM — Enter true or false. The default value is false. Use catalog ingest for DefinePPV — Enter true or false. The default value is false. Catalog ingest host — Enter the IP address of the catalog ingest host. Catalog ingest port — Enter the port for the catalog ingest. Usually it is 5150, the EventIS.NotificationPort. OL-27753-06 Install the BillingAdaptor (BOA) COP File 6 7 8 9 10 11 12 13 14 Select the nodes upon which to install the COP file and then choose Generate Config, to generate the BillingAdaptor configuration file. A confirmation message appears. Choose OK. Click OK in the message that appears that states that the node Configuration file was successfully generated. Choose the node upon which you would like to install the BillingAdaptor COP file, and then choose the COP file you would like to install. Click COP Install. Click OK in the confirmation message. The status under COP install changes for the node selected for the install. When the install completes, the status changes to SUCCESS. Select the management node upon which you would like to install the BillingAdaptor UI components. Select the BillingAdaptor file. Click Install UI Components. In the confirmation message, choose OK to start the UI installation. Result: The system logs you out to the CMC UI login window. Log back in and continue working. Note: To add service connections to other UHE components. use the following REST URL: Request: PUT http://10.90.187.39:8080/BillingAdaptor/api/configuration Body: bsc:BoaServiceConnections xmlns:bsc="http://protocols.cisco.com/spvtg/conductor/boa/boaS erviceConnections"><serviceConnections><upmip>10.90.186.203</u pmip><upmport>6040</upmport><cihost>10.90.186.204</cihost><cip ort>5150</ciport><dshost>10.90.186.203</dshost><dsport>6045</d sport><rshost>10.90.186.203</rshost><rsport>6530</rsport><heph ost>10.90.186.204</hephost><hepport>6030</hepport><cmdchost>10 .90.186.208</cmdchost><cmdcport>5600</cmdcport></serviceConnec tions></bsc:BoaServiceConnections> Response: {'date': 'Tue, 17 Jun 2014 14:03:28 GMT', 'status': '200', 'content-length': '198', 'content-type': 'application/xml', 'server': 'Apache-Coyote/1.1'} Install Multiple Instances of the BOA COP File 1 2 OL-27753-06 Follow the installation instructions to install the BOA COP file. In step 3 of the BOA COP file installation instructions, be sure that you choose a different service node. 65 Chapter 7 Install the JBoss COP Files 3 4 Generate the configuration file for that service node. Select the new service node, the BOA COP file, and the new configuration file; then, click COP Install. Upgrade the BOA COP File 1 2 3 4 5 6 7 Uninstall the BOA COP file's UI component: a Select the CMC management node. b Select the NOSQLCB COP file. c Click Uninstall UI Component. Choose Operate > Download to download the BillingAdaptor COP file. Choose Operate > COP Install to initiate the BillingAdaptor COP file installation. Select the node(s) on which to install the BillingAdaptor COP file. Select the BillingAdaptor COP file to install. Click New Config Generation. Enter the information for the following fields: Group ID for Explorer Controllers: Enter the ECS group/cluster ID; this is the same ID that was entered when the ECS DBAccessService COP file was installed. Notes: – This field must be entered, but this can be a bogus entry if ECS is not needed on the system. – The Group/Cluster ID cannot be longer than 8 characters/numbers. 8 9 10 11 12 13 14 66 UPM IP Address: Enter the IP address where the UPM COP file is installed. Select the nodes upon which to install the COP file and then click Generate Config to generate the BillingAdaptor configuration file. A confirmation message appears. Click OK. A message appears that states that the configuration file was successfully generated. Click OK. Select the nodes upon which to install the COP file and then select the COP file. Click COP Upgrade. A confirmation message appears. Click OK. The status changes for the node selected for the upgrade. When the upgrade completes, the status changes to SUCCESS. Select the management node upon which you would like to install the BillingAdaptor UI components. OL-27753-06 Install the BillingAdaptor (BOA) COP File 15 Select the BillingAdaptor file. 16 Click Install UI Components. A confirmation message appears. 17 Click OK to begin the UI installation. Result: You are logged out of the CMC UI. Log back in and continue working. OL-27753-06 67 8 Chapter 8 Install the SRM COP File Introduction This chapter provides instructions for installing the COP file for the Session Resource Manager (SRM). Prerequisites You must complete the following tasks before installing the SRM: Install the NOSQLCB COP File (on page 19) Create an SRM Account JID (Message Infrastructure > Message Fabric > Account ID) Configure the NOSQLCB server to support the SRM installation as described in the Cisco Conductor Session Resource Manager Configuration Guide (OL-26147). In This Chapter OL-27753-06 Install the SRM COP File ..................................................................... 70 69 Chapter 8 Install the SRM COP File Install the SRM COP File After performing all prerequisite tasks, complete the following steps to install the SRM COP File. 1 Open a supported browser and enter the URL of the management console server. The URL has the general form: https: <hostname of the Videoscape Control Suite Management host> or <hostname of the Videoscape Control Suite Management host>:8080 The management console login page appears. 2 In the management console login page, enter your Username and Password. Then, click Login. The management console main page appears, showing the Videoscape Control Suite nodes. 3 If an SFTP user is not already created, go to Create the SFTP User (on page 9), and then proceed to Configure Connection Manager. The management console main page appears, showing the Videoscape Control Suite node types. 4 5 In the management console main page, click Operate and then click COP Install. Choose the service node on which you want to install the SRM COP file. The window updates to show a list of COP images to install. 6 Note: If you are installing on multiple nodes, choose all of the nodes on which you want to install, or you can install them one node at a time. 7 Choose the SRM COP image you want to install. The window updates to allow for the configuration of the new image. 8 Click New Config Generation. The COP Configuration page appears. 9 Choose the service node on which you want to install the COP file. 10 Enter the following information in the COP Configuration Generation table: Select Configuration – Choose a license in the drop-down list (for example, <ComcastNdvrComplete>) 11 12 13 14 70 Select Mode: Select the Primary mode or Standby mode. In the COP Configuration Attributes section, select the SRM Node ID. Click Save, and then click Generate Config. Click OK to generate the configuration file. A pop-up confirmation message is displayed. Click OK to return to the COP install page. OL-27753-06 Install the SRM COP File 15 In COP install page, choose the following: 16 17 18 19 20 OL-27753-06 The service node on which you want to install the COP file The SRM COP file to be installed The Node Configuration file that just generated Click COP Install. A confirmation message appears. Click OK. A pop-up confirmation message is displayed. Wait a few seconds for the COP Install Status column to display SUCCESS or IN_PROGRESS. Wait for the installation to complete. A success message is displayed when the installation is complete. If you did not select all nodes for the installation, repeat these steps for any remaining nodes. 71 9 Chapter 9 Install the WFE COP File This chapter provides instructions for installing the COP file for the Work Flow Engine (WFE). The WFE is an open-source asynchronous messaging system used for delivering messages between the Videoscape Control Suite and the additional unified headend (UHE) added to the Videoscape Control Suite. In This Chapter OL-27753-06 Install the WFE COP File ..................................................................... 74 73 Chapter 9 Install the WFE COP File Install the WFE COP File Installation of the WFE COP file involves the installation of the COP file itself followed by installation of the WFE UI component. This section provides instructions for completing both tasks. Install the WFE COP File Complete the following steps to install the WFE COP file: 1 Log in to the CMC user interface. 2 Choose Operate > Download to download the COP and Template files for the WFE. 3 Choose Operate > COP Install. A list of nodes is displayed. 4 Choose the node on which to install the WFE COP file. The COP Images to Install area becomes available. 5 Choose the WFE COP file to install. The COP Image Config Files window becomes available. 6 In the COP Images to Install area, click COP Install to initiate the COP installation process. A confirmation message appears. 7 Click OK. Another confirmation message appears. 8 Click OK. A pop-up confirmation message is displayed. 9 Click OK to acknowledge the install initiation. Note: When the installation completes, the WFE COP Install page shows SUCCESS. Install the WFE UI Component Complete the following steps to install the WFE UI Component: 1 Choose the management node on which to install the UI component. 2 Choose Install UI Components from the COP Images to Install area. Result: A confirmation message appears. 3 Click OK to confirm the installation. 4 When the installation is completed, you will be logged out of the CMC UI so that the WFE UI component installation can complete. 74 OL-27753-06 Install the WFE COP File OL-27753-06 5 Log in to the CMC UI again and click the Services tab. 6 Confirm that the Workflow Engine menu is now displayed in the Services tab. 75 10 Chapter Install the Targeting Message 10 Service (TMS) COP File Introduction This chapter provides instructions for installing the Targeting Message Service (TMS) COP File. Prerequisites You must complete the following tasks before installing the TMS COP file: Install HornetQ (on page 23). Install Oracle Database 11g. Create Oracle TMS user, table, and indexes. See the Videoscape Control Suite Database User Guide (OL-28290) for details. In This Chapter OL-27753-06 Install the TMS COP File...................................................................... 78 77 Chapter 10 Install the Targeting Message Service (TMS) COP File Install the TMS COP File Note: See Notes Regarding the TMS COP File (on page 78), which follows this procedure, for information that may affect your TMS COP file installation. 1 Choose Operate > Download to download the TMS COP file. 2 Choose Operate > COP Install to initiate the COP file installation process. 3 Choose the nodes on which to install the COP file, then choose the TMS COP file. 4 Click New Config Generation. 5 Complete the following entries: DB Host – Enter the Oracle database host IP address DB Port – Enter the Oracle database connection port DB Service Name – Enter the Oracle listener service name TMS DB User – Enter the TMS database user DB User Password – Enter the TMS database User Password 6 Click Save to save your entries. 7 Choose the nodes on which to install the TMS COP file from the list of nodes in the COP Configuration Attributes, then click Generate Config. 8 Click Generate Config to generate the Target Messaging System config file. A confirmation message appears. Click OK to generate the configuration file. A pop-up confirmation message is displayed. 9 Click OK to return to the COP Install page. 10 Choose the node on which to install the TMS COP file, choose the COP file to install, then click COP Install. A confirmation message appears. 11 Click OK to start the COP file installation. The status under COP install changes for the nodes selected for install. 12 Confirm that the TMS COP file has been successfully installed. Notes Regarding the TMS COP File If the IP address of the TMS-related service nodes (such as nodes upon which UPM is installed) has changed from how it was originally configured, as the root user, modify the /opt/nds/tms/etc/config.properties file with the new IP address. Then, after the IP address change and reboot, run the following command in the CLI: set network hostname <same hostname> As the root user, modify the /opt/nds/tms/etc/config.properties file with this new IP address. 78 OL-27753-06 Install the TMS COP File If the OMS over TMS feature is to be deployed, as the root user, modify appropriate configurations (such as MCC) after installing the TMS COP file. Contact Cisco Services for information regarding which configurations need to be modified. Fix TMS Entries After installation of the COP file, the COP file will be executing with default parameters. For the COP file to execute with the correct parameters, it is necessary to edit the /opt/nds/tms/etc/config.properties file, as described in the following procedure. 1 Log in to the service node on which TMS is installed with root access. 2 Modify the /opt/nds/tms/etc/config.properties file. Note: The following lines need to be modified: Line208 — tms.delivery.xmpp.scm.restHost = 209.165.202.129 //Host IP address for MCC server Line209 — tms.delivery.xmpp.scm.restPort = 8200 (default 8200) Line211 — tms.delivery.xmpp.projectName = svc.conductor.com //service jsm hostname Line214 — tms.delivery.xmpp.pubsubJid = ps.conductor hostname Line239 — tms.delivery.message.remotedata.retriever.host = 209.165.202.128 //service node IP on which UPM is installed Line240 — tms.delivery.message.remotedata.retriever.port = 6040 //UPM port (default 6040) Line331 — auditServer.1.host = 209.165.202.130 same as service node IP where TMS is installed //Port for MCC server //pubsub //IP of UDP server, 3 OL-27753-06 Line332 — auditServer.1.port = 5179 //UDP server port (default 5179) After saving the file, enter service nds_tms restart to restart the TMS service. 79 11 Chapter Install the Headend Purchase 11 (HEP) COP File This chapter provides instructions for installing the Headend Purchase (HEP) COP file. In This Chapter OL-27753-06 Install the HEP COP File ...................................................................... 82 81 Chapter 11 Install the Headend Purchase (HEP) COP File Install the HEP COP File 1 2 3 Choose Operate > Download to download the HEP COP file. Choose Operate > COP Install to initiate the COP file installation process. Choose the nodes on which to install the HEP COP file, then choose the Headend Purchase file. 4 Click New Config Generation. 5 In the HornetQ Host field, enter the IP address where HornetQ is installed. 6 Choose the nodes on which to install the HEP COP file from the list of nodes in the COP Configuration Attributes, then click Generate Config to generate the configuration file for HEP. A pop-up confirmation message is displayed. 7 Click OK to generate the configuration file. A pop-up confirmation message is displayed. 8 Click OK to return to the COP Install page. 9 Choose the node on which to install the HEP COP file, then choose the COP file to install, then click COP Install from the COP Images To Install area. A pop-up confirmation message is displayed. 10 Click OK to start the COP file installation. A pop-up confirmation message is displayed. 11 Click OK to start the COP file installation. A pop-up confirmation message is displayed. Notes: The status under COP install changes for the node selected for install. When the install completes, the status changes to SUCCESS. 12 Confirm that the HEP COP file has been successfully installed. 82 OL-27753-06 12 Chapter Install the Personal Planner 12 Server (PPS) COP File Introduction This chapter provides instructions for installing the Personal Planner server (PPS) COP file. Prerequisites You must complete the following tasks before installing the PPS COP file: Install HornetQ (on page 23). Install Oracle Database 11g. Create Oracle database PPS data and index tablespace. See the Videoscape Control Suite Database User Guide (OL-28290) for details. Create Oracle database user, table, and indexes. See the Videoscape Control Suite Database User Guide (OL-28290) for details. In This Chapter OL-27753-06 Install the PPS COP File ....................................................................... 84 83 Chapter 12 Install the Personal Planner Server (PPS) COP File Install the PPS COP File 1 2 3 4 5 Choose Operate > Download to download the Personal Planner Server (PPS) COP file. Choose Operate > COP Install to initiate the PPS COP file installation process. Choose the nodes on which to install the PPS COP file, then choose the Personal Planner Server file. Click New Config Generation. Complete the following entries. DB Host – Enter the Oracle Database Host IP address. DB Port – Enter the Oracle Database Connection Port. DB Service Name – Enter the Oracle Listener Service Name. PPS DB User – Enter the PPS DB User. DB User Password – Enter the PPS DB User Password. HornetQ Host – Enter the IP address of the HornetQ Host. 6 Choose the nodes on which to install the PPS COP file from the list of nodes in the COP Configuration Attributes, then click Generate Config. 7 Click Generate Config to generate the PPS config file. A pop-up confirmation message is displayed. 8 Click OK to generate the configuration file. A pop-up confirmation message is displayed. 9 Click OK to return to the COP Install page. 10 Choose the node on which to install the PPS COP file, then choose the COP file to install, then click COP Install from the COP Images To Install area. A pop-up confirmation message is displayed. 11 Click OK to start the COP file installation. Notes: The status under COP install changes for the nodes selected for install. When the install completes, the status changes to SUCCESS. 12 Confirm that the PPS COP file has been successfully installed. Fix PPS Entries After installation of the COP file, the COP file will be executing with default parameters. For the COP file to execute with the correct parameters, it is necessary to edit the /opt/nds/tms/etc/config.properties file, as described in the following procedure. 1 Use root access to log in to the TMS server node. 2 Enter the following command to stop the TMS service. service nds_pps stop 84 OL-27753-06 Install the PPS COP File 3 Modify the /opt/nds/tms/etc/config.properties file. Note: The following lines need modification: 4 OL-27753-06 service.pvr.host=<IP of PPS install host> service.web.authenication.upm.1.host = <enter upm host IP> redundancy.isPreferredMaster=true redundancy.host=<IP of PPS install host> redundancy.heartbeatPort=6058 <default port> Enter the following command to restart the TMS service. service nds_pps start 85 13 Chapter Install the Unified Notification 13 Gateway COP File Introduction This chapter provides instructions for installing the Unified Notification Gateway (UNG) COP file. Prerequisites: The Oracle database user and password must have already been created. See the Videoscape Control Suite Database User Guide (OL28290). In This Chapter OL-27753-06 Installing the Unified Notification Gateway COP File .................... 88 87 Chapter 13 Install the Unified Notification Gateway COP File Installing the Unified Notification Gateway COP File 1 2 3 4 5 6 7 8 9 10 11 12 13 88 Download the Unified Notification Gateway (UNG) COP file using Operate > Download. Note: See the Download the COP File Template and COP File (on page 17), if needed. Once downloaded, in the CMC UI Main Menu, click Operate > COP Install. Choose the nodes upon which to install the UNG COP file, and then choose the UNG COP file. Click New Config Generation to configure the UNG COP file for installation. Choose the nodes upon which you would like to install the UNG COP file from the list of nodes in the COP Configuration Attributes area, and then click Edit. Complete the entries and then click Save. APNS Hostname: Hostname of the APNS push gateway service; default value is ‘gateway.push.apple.com’ APNS Port: Port for the APNS push gateway service; default value is 2195 APNS Feedback Port: Port for the APNS feedback service; default value is 2196 UNG DB User: Username of the UNG service database APNS Feedback Hostname: Hostname of the APNS feedback service; default value is ‘feedback.push.apple.com’ UNG DB Password: Password of the UNG service database DB Host: Host name/IP address of the Oracle database server DB Port: Oracle database port DB SERVICE NAME: Oracle database service name Click Generate Config to generate the configuration files for the UNG install. Result: A message is displayed, asking Do you really want to generate selected configuration file(s). Click OK to generate the configuration files. Result: A message is displayed: Node Configuration file(s) generated successfully. Do you want to go back to COP Install page? Click OK to generate the config file and return to the COP Install page. In the COP Install page, select the nodes upon which to install the UNG COP file. Click COP Install. Click OK to confirm. Result: A message is displayed: COP Install initiation is successful. Click OK. Result: In the COP Install UI, under COP Install Status, you will see the status change to “IN_PROGRESS”, while the install is going on. This will change to “SUCCESS” once the install is complete. OL-27753-06 14 Chapter Install the Location Service 14 Data COP File Introduction This chapter provides instructions for installing the Location Service Data COP file. In This Chapter OL-27753-06 Installing the Location Service Data COP File .................................. 90 Install the Location Service COP File ................................................. 91 89 Chapter 14 Install the Location Service Data COP File Installing the Location Service Data COP File 1 2 3 Log in to the CMC. Download the COP and template files for the Location Service. Choose Operate > COP Install to view a list of nodes upon which the COP file can be installed. 4 Choose the node upon which you would like to install the Location Service Data COP file. 5 Choose the Location Service Data COP file you would like to install. 6 In the COP Install window, choose the node upon which you would like to install the Location Service Data COP file. 7 In the COP Images to Install area, click COP Install to initiate the COP installation process. 8 Click OK in the confirmation message. 9 Click OK again on a confirmation message. 10 Click OK to acknowledge that the COP installation has begun. Note: The message SUCCESS will display once the installation process has completed. 90 OL-27753-06 Install the Location Service COP File Install the Location Service COP File 1 2 3 4 5 6 OL-27753-06 Log in to the CMC user interface. Choose Operate > COP Install. A list of nodes is displayed. Choose the node on which to install the Location Service COP file. The COP Images To Install area becomes available. Choose the Location Service COP file to install. The COP Image Config Files window becomes available. Click New Config Generation to access the template required to generate the configuration information needed to install the Location Service COP file. The COP Config window becomes available. Choose the node on which to install the Location Service COP file from COP Configuration Attributes, then click Edit. Additional configuration parameters become available. Note: Location Service COP configuration includes the following: Geolocation Data Source — Maxmind/Quova, default Quova Couchbase Service Admin User Name — default Administrator ISP Textual Name Enabled — true/false, default false Quova Server Listener Port if Using UDP — default 8000 Couchbase Data Grid Enabled — true/false, default false Couchbase Service List IPs or Hostnames — If using Couchbase (noSQLcb) enter the IPs or Hostnames Couchbase Service Admin Password — default Public123 TTL for HTTP Cache Control in Minutes — default 30 Wait Seconds Before Refreshing the Data Source — default 300 Maximum Number of Allowable Errors from Data Loading — default 2147483647 Primary Quova Server IP or Hostname — default 127.0.0.1 Primary Quova Server Port — default 7000 Secondary Quova Server IP or Hostname — default 127.0.0.1 Secondary Quova Server Port — default 7001 Customer ID for Quova Server Connection — Frequency in Seconds for Quova Connection Retry — default 5 Maximum Number of Quova Server Connections Retries — default 3 Transport Protocol Used for Quova Server Connection — TCP/UDP, default TCP Quova Server Connection Timeout in Milliseconds — default 5000 91 Chapter 14 Install the Location Service Data COP File 7 8 9 10 11 12 13 14 15 16 92 Complete the fields and then click Save to save your entries (or Cancel to ignore). Click Generate Config to generate the configuration file. A confirmation message appears. Click OK. Click OK in the message that indicates that the node configuration was generated successfully. In the COP Install page, choose the node on which to install the Location Service COP file. The COP Images to Install area becomes available. Choose the Location Service COP file to install. The COP Image Config Files window becomes available. In the COP Images to install area, click COP Install to initiate the COP installation process. A confirmation message appears. Click OK. Another confirmation message appears. Click OK. The COP install initiation is successful message is displayed. Click OK to acknowledge this initiation. The Location Service COP Install shows SUCCESS once it is completed. OL-27753-06 15 Chapter Install the Conductorapps 15 Manager COP File Introduction Use the instructions in this chapter to install the Conductorapps Manager COP File. In This Chapter OL-27753-06 Installing the Conductorapps Manager COP File ............................ 94 93 Chapter 15 Install the Conductorapps Manager COP File Installing the Conductorapps Manager COP File Use this COP file to enable the Jboss secure port (8443) for Jboss applications. 1 Download the Conductorapps Manager COP file using Operate > Download. 2 Install the Conductorapps Manager COP file. a Choose Operate > COP Install. b Choose the nodes upon which you would like to install the Conductorapps Manager COP file, and then choose the Conductorapps Manager file. c Click New Config Generation. 3 Complete the entries: 4 5 6 7 8 94 ENABLE UNSECURED PORT — Enter true or false ENABLE SECURE PORT — Enter true or false KEYSTORE PASSWORD — Enter a password to store the password information Choose the node upon which you would like to install the Conductorapps Manager COP file from the list of nodes in the COP Configuration Attributes section. Then, click Generate Config to generate the Conductorapps Manager config file. A confirmation message appears. Click OK to generate the configuration file. Click OK in the message that states that the file was generated successfully. The COP Install page appears. Choose the node upon which you would like to install the Conductorapps Manager COP file. Then, choose the COP file you would like to install, and click COP Install from the COP Images To Install list. Click OK in the node selection confirmation message. Click OK to confirm your intent to install the COP file. A message indicating Success will appear after the COP file has successfully installed. OL-27753-06 16 Chapter Install the PortProxy COP File 16 Introduction Use the instructions in this chapter to install the PortProxy COP File. In This Chapter OL-27753-06 Installing the PortProxy COP File ...................................................... 96 95 Chapter 16 Install the PortProxy COP File Installing the PortProxy COP File Use this COP file to enable the Jboss application to use port 80. 1 Download the PortProxy COP file using Operate > Download. 2 Install the PortProxy COP file. a Choose Operate > COP Install. b Choose the nodes upon which you would like to install the PortProxy COP file, and then choose the PortProxy file. 3 Choose the node upon which you would like to install the PortProxy COP file. Then, choose the COP file you would like to install, and click COP Install from the COP Images To Install list. 4 Click OK in the node selection confirmation message. 5 Click OK to confirm your intent to install the COP file. A message indicating Success will appear after the COP file has successfully installed. 96 OL-27753-06 17 Chapter Install the Data Analytics 17 Introduction Data analytics leverages the Cisco Prime Analytics 1.0 release to provide analytics dashboards. As a data source, the Cisco Videoscape Control Suite provides rich data collection and transformation processing, and then feeds the data into the analytics engine. The Videoscape Control Suite also integrates the analytics dashboards into the CMC. In This Chapter OL-27753-06 Data Analytics Overview..................................................................... 98 Installation and Configuration of Data Analytics ............................ 99 Analytics Quick Start.......................................................................... 104 Known Issues and Limitations ......................................................... 108 97 Chapter 17 Install the Data Analytics Data Analytics Overview Message Infrastructure Analytics The VCS message infrastructure uses syslog protocol to transfer the analytics data into the Prime Analytics node. The following image shows the logical view between the VCS node (blue box) and the Prime Analytics node (brown box). The VCS node, as the data source, generates the raw data into the syslog daemon. the syslog daemon is configured to send the raw data to the remote TruLink node for data processing. After filtering and processing by Prime Analytics (brown node), the real time dashboards and historic dashboards are displayed in the Conductor Management Console (CMC). The TruLink node is made up by a chain of handlers, including: UDP Socket handler: Listens on the 514 syslog port for incoming data. Syslog handler: Parses each line of logger data and splits them into a string array by delimiter and regex expression. XML parser: Parses the detailed logger text that follows the pre-defined syntax into the ‘hstore’-kind of string. The three components of the Prime Analytics product can be configured to run in one VM or separate, multiple VMs. See the the documentation supplied by Prime Analytics for the topology details. The previous figure shows the logical view, only. 98 OL-27753-06 Installation and Configuration of Data Analytics Installation and Configuration of Data Analytics This section briefly describes how to install and deploy the Analytics package on top of the Cisco Videoscape Control Suite and Prime Analytics. Software Requirements Ensure that you have installed the Cisco Videoscape Control Suite software. See the Videoscape Control Suite Installation and Upgrade Guide (part number OL-29939) for details. Ensure that the Prime Analytics 1.0 package has been installed. See the Cisco Prime Analytics 1.0 Quick Start Guide (OL-28753) for details. Hardware Requirements See the Videoscape Control Suite Installation and Upgrade Guide (part number OL29939) for the hardware requirement of VCS. See the Cisco Prime Analytics 1.0 Quick Start Guide (part number OL-28753) for the hardware requirement for Prime Analytics. Note: VCS and the Prime Analytics instance must be deployed on two separate machines. File Requirements cisco.conductor-da-installer-xx.tar.gz cisco.conductor-da-msginfra-3.0-0-xxxx.tar.gz Browser Requirements Internet Explorer 9 Mozilla Firefox 5 Note: The browser requirement is used for accessing dashboards in the VCS CMC UI. See the Cisco Prime Analytics 1.0 Quick Start Guide if you want to access dashboards from the Prime Analytics UI. OL-27753-06 99 Chapter 17 Install the Data Analytics Install Prime Analytics 1.0 Prime Analytics 1.0 should be installed on top of Redhat Enterprise Linux 6.2. Make sure that you have one machine with RHEL 6.2 installed. See the Cisco Prime Analytics 1.0 Quick Start Guide for more about how to install the PA 1.0 image. Once you complete the installation, you must turn off the default firewall in RHEL 6.2 by entering the following command: service iptables stop Configure VCS for Analytics The VCS provides a CLI console command to redirect the syslog traffic to a remote syslog server. Analytics leverages this CLI command to specify the centralized Analytics server and listening port. You need to log in to each VCS node and open the platform command line interface. The syntax of the CLI command follows. admin: set syslog server <selector> In the following example, only the debug level messages from syslog traffic will be redirected to 172.16.100.125. 100 OL-27753-06 Installation and Configuration of Data Analytics Note: You need to configure the syslog server in all nodes EXCEPT the management nodes. To retrieve the type of VCS node, click Node/Router/Component under Message Infrastructure. The node type is shown in the node list. In the following example, you should only configure the syslog server on ‘da-sp2-svc1’ and ‘da-sp1-svc2’. OL-27753-06 101 Chapter 17 Install the Data Analytics Install the Analytics Package on Top of Prime Analytics To install the Analytics package on top of Prime Analytics, use the root account to log in to the Prime Analytics node. 1 Decompress (extract) the installer in any folder and put the Data Analytics image in the installer folder. mkdir installer tar zxf cisco.conductor-da-install-3.0-0-5884.tar.gz -C installer mv cisco.conductor-da-msginfra-3.0-0-5885.tar.gz installer Result: The files in the installer folder should look similar to the following example: 2 102 Enter the following command to begin the installation: install.sh <data file> Note: You may need to answer some questions during the installation. OL-27753-06 Installation and Configuration of Data Analytics The installation continues: 3 After the installation completes, go to the data Analytics home folder and start the TruLink connector. cd /opt/cisco/vcs/analytics/connectors/da/xmpp_syslog ./start.sh Uninstall the Analytics Package To uninstall the Analytics package from Prime Analytics, execute uninstall.sh all in the /opt/cisco/vcs/analytics/bin directory. Doing so will complete the uninstallation process automatically. OL-27753-06 103 Chapter 17 Install the Data Analytics Analytics Quick Start Analytics Dashboard for Message Infrastructure 1 2 3 Log in to the CMC. Click Message Infrastructure. Click Analytics, under Message Fabric. Result: Two dashboards appear, a Real-Time Dashboard and a Historical Dashboard. 104 OL-27753-06 Analytics Quick Start Real-Time Dashboard The Real-Time Dashboard makes use of a real-time line chart, showing 5-minutes worth of data with points at 15-second intervals. This chart shows the trend of online and offline devices in the system. The blue line represents the total number of online devices, the red line is the total number of offline devices, and the green line represents the total number of devices, online and offline. OL-27753-06 105 Chapter 17 Install the Data Analytics Real Time Message Throughput This image shows the throughput of the message infrastructure system. Three kinds of messages are transmitted: <message/>, <iq/>, and <presence/>. Historic Dashboard Several examples of graphs obtainable from the Historic Dashboard follow. 106 OL-27753-06 Analytics Quick Start These images show the message throughput in the last hour, last day, last week, or last month. OL-27753-06 107 Chapter 17 Install the Data Analytics Known Issues and Limitations Access Prime Analytics Node Via Hostname The VCS and the Prime Analytics node should be deployed in the same domain. The analytics dashboards from Prime Analytics have been embedded into the VCS CMC page. Because the Prime Analytics node is accessed by hostname, the syntax of the dashboard URL in the CMC page looks like the following example: https://pa_hostname:8443/…<dashboard name> Therefore, the client browser must have the ability to resolve the IP address of the Prime Analytics host machine. This is accomplished by setting up a DNS server. Alternatively, one can configure the hostname on the client machine: In Windows, the configuration file is C:\Windows\System32\drivers\etc\hosts. In Linux, the configuration file is /etc/hosts. Self-Signed Certificates in Prime Analytics Node A self-signed certificate is generated on a Prime Analytics node when installing the VCS Analytics package on the Prime Analytics node. It is used by the web server to enable the HTTPS security transmissions between the client browser and server. Different browsers have different behaviors when opening such a page for the first time. 108 OL-27753-06 Known Issues and Limitations Note: When the security level of Internet Explorer is Medium to High, an alert window is shown when you try to open any dashboard in the CMC. Click Show content at the bottom to continue. This page is redirected back to the previous page. Now the dashboard can be displayed when you click the hyperlink of the dashboard again. Note: An alert page is shown when you open any dashboard in Firefox for the first time. Click I Understand the Risks > Add Exceptions. The Add Security Exception window opens. Click Confirm Security Exception to import the certificate. OL-27753-06 109 Chapter 17 Install the Data Analytics One Dashboard can be Viewed at a Time The CMC UI embeds the dashboard using an <iframe/> HTML tag, which means that only one dashboard can be viewed at a time. You can click the Back button to go to the dashboard landing page and switch to another dashboard. Note: Internet Explorer 9 and Firefox 5.0 are currently the supported browsers. 110 OL-27753-06 18 Chapter Install EPM Analytics 18 Introduction This chapter guides you through the steps of installing the EPM Analytics software. In This Chapter OL-27753-06 Installing EPM Analytics ................................................................... 112 111 Chapter 18 Install EPM Analytics Installing EPM Analytics A tarball is produced for EPM analytics applications. This tarball includes the analytics connector application and a dashboard bundle for both EPM and USRM. The dashboard bundle is installed using the backup/restore facility included in the installer. The basic steps for analytics application installation are: Note: Prime Analytics PA RC3 or later must first be installed. See Cisco Prime Analytics 1.0 Quick Start Guide (part number OL-28753) for details. 1 Create a folder on the Prime Analytics node to use as the installation directory for EPM Analytics. 2 Download a copy of the da-install installer, such as cisco.conductor-da-install3.0-0-xxxx.tar.gz, into a folder named installer. 3 Download a copy of the da-epm analytics package, such as cisco.conductor-daepm-3.0-0-xxxx.tar.gz, into the folder named installer. 4 In the installer folder, untar da-install: untar -xzvf cisco.conductor-da-install-3.0-0-5978.tar.gz 5 In the installer folder, run the installer to install epm: ./install.sh cisco.conductor-da-msginfra-3.0-0-5943.tar.gz Configuration During the Installation During installation of the EPM analytics package, you will be asked to configure both the EPM server and the XMPP server to allow for dynamic topic subscription. The following questions are asked, and answers are provided. 1 Do you want to configure EPM host information? (yes or no): Answer: yes 2 Enter EPM hostname or ip (default): Answer: The IP address or the name of the Endpoint Manager node 3 Enter polling frequency for EPM topics in seconds (60): Answer: Number of seconds (interval) for the EPM server polling for active Topic Names 4 Do you want to configure XMPP host information? (yes or no): Answer: yes 5 Enter XMPP hostname or ip (default): Answer: IP address or the name of the XMPP server(management node) 6 Enter XMPP host port (5222): Answer: Port number for XMPP 7 Enter topic subscriber user name (default): Answer: Subscriber user name 112 OL-27753-06 Installing EPM Analytics 8 Create an Account JID in the CMC. a Choose Message Infrastructure > Message Fabric > Account JID b Under Account JID, click Add. c Enter the following information – User Name: (Enter a user account for EPM Analytics) – Choose a JSM Host from the drop-down list. – Password: (Enter the password for the user account) – Confirm Password: (Re-enter the password for the user account) d Click Save to save this user account, and write these values down for future reference. User Name: __________ Password: __________ 9 Enter subscriber password: 10 Enter PubSub Id (pubsub.features): Answer: Enter the same PubSub used when EPM was installed. OL-27753-06 113 19 Chapter Install USRM Analytics 19 Introduction This chapter guides you through the steps of installing the USRM Analytics software. In This Chapter OL-27753-06 Requirements for Installing USRM Analytics................................. 116 Installing USRM Analytics ................................................................ 117 115 Chapter 19 Install USRM Analytics Requirements for Installing USRM Analytics Software Requirements Ensure that you have installed the Cisco Videoscape Control Suite software. See the Videoscape Control Suite Installation and Upgrade Guide (part number OL-29939) for details. Ensure that Prime Analytics 1.0 has been installed. See the Cisco Prime Analytics 1.0 Quick Start Guide (part number OL-28753) for details. Hardware Requirements See the Cisco Videoscape Control Suite Installation and Upgrade Guide (part number OL-29939) for the hardware requirements of VCS. See the Cisco Prime Analytics 1.0 Quick Start Guide (part number OL-28753) for the hardware requirement for Prime Analytics. Note: The VCS and Prime Analytics instances must be deployed on two separate machines. File Requirements cisco.conductor-da-installer-3.0.x.xxxx.tar.gz cisco.conductor-da-usrm-3.0-0-xxxx.tar.gz Browser Requirements Internet Explorer 9 Mozilla Firefox 5 Note: The browser is used for accessing dashboards in the VCS CMC UI. See the Cisco Prime Analytics 1.0 Quick Start Guide (part number OL-28753) to access dashboards from the Prime Analytics UI. Install Prime Analytics 1.0 Prime Analytics 1.0 should be installed on top of Redhat Enterprise Linux 6.2. Make sure that you have one machine with RHEL 6.2 installed. See the Cisco Prime Analytics 1.0 Quick Start Guide (part number OL-28753) for more information about how to install the Prime Analytics 1.0 image. 116 OL-27753-06 Installing USRM Analytics Installing USRM Analytics A tarball is produced for USRM Analytics applications. This tarball includes the analytics connector application and a dashboard bundle for both EPM and USRM. The dashboard bundle is installed using the backup/restore facility included in the installer. The basic steps for analytics application installation are as follows. 1 Be certain that Prime Analytics PA RC3 or later is installed. See Cisco Prime Analytics 1.0 Quick Start Guide (part number OL-28753). 2 Create a folder on a Prime Analytics node to use as the installer directory for USRM Analytics. 3 Download a copy of the da-install installer, such as: cisco.conductor-da-install3.0-0-xxxx.tar.gz, into the installer folder. 4 In the installer folder, untar da-install: untar -xzvf cisco.conductor-da-install-3.0-0-xxxx.tar.gz 5 In the installer folder, run the installer to install USRM. ./install.sh cisco.conductor-da-usrm-3.0-0-xxxx.tar.gz 6 During the installation of the USRM Analytics package, you will be asked to configure the USRM server to read topology information. The installation process requests the following information. USRM Restful Service IP address — IP address or name of the USRM server Hostname or IP address of the VCS Management node — IP address of the VCS Management node USRM Restful Service Port (80) — Port number for the USRM Restful Service Port number of MCC on the VCS Management node — Default is 8200 Results: HTTPS is enabled 7 8 OL-27753-06 Prime Analytics installs and starts Access the dashboard through the CMC IP address. Start USRM: cd /opt/cisco/vcs/analytics/connectors/usrm/usrm && ./start.sh 117 20 Chapter Upgrade COP Files 20 Introduction This chapter provides the information you need in order to upgrade COP files. The following COP files must be installed; they do not have an upgrade option. Notes: If upgrading the Couchbase COP file from Conductor Release 2.5 to VCS 3.0, see NOSQLCB Server Upgrade Procedures for COP R2.1 to COP R3.0 GA (on page 123). The following COP files do not have an upgrade option. They must be installed: OL-27753-06 - Work Flow Engine (WFE) - Location Service (LS) - Targeting Message Service (TMS) - Personal Planner Service (PPS) - Headend Purchase (HEP) 119 Chapter 20 Upgrade COP Files In This Chapter 120 Upgrade COP Files ............................................................................. 121 NOSQLCB Server Upgrade COP R2.1 to R3.0 GA......................... 123 Upgrade UPM from Version 2.5 to Version 3.0 .............................. 128 Upgrade HornetQ from Version 2.5 to Version 3.0 ....................... 129 Upgrade UPM Adaptor (UPMCDA) from Version 2.5 to Version 3.0............................................................................................ 130 Upgrade OMS from Version 2.5 to Version 3.0 .............................. 131 Upgrade OMS from Version 3.0 to Version 3.1 .............................. 132 Upgrade the UI Component of COP Files ....................................... 133 OL-27753-06 Upgrade COP Files Upgrade COP Files It is now possible to upgrade your COP files to a newer version of the software. This section describes the procedure. Notes: If you are upgrading the Couchbase COP file from Conductor Release 2.5 to VCS 3.0, see NOSQLCB Server Upgrade Procedures for COP R2.1 to COP R3.0 GA (on page 123) for instructions. If you are upgrading AlertManager from 2.1 embedded Oracle to AlertManager 3.0 external Oracle, or AlertManager from 2.5 embedded Oracle to AlertManager 3.0 external Oracle, see the Videoscape Control Suite Database User Guide (OL-28290) for instructions. If your application contains a UI component, make sure to uninstall the UI component prior to upgrading the COP file. Upgrade Procedure 1 2 3 4 5 6 7 8 In the management console main page, navigate to Operate > Download. Download the COP File Template and COP File as described in Download the COP File Template and COP File (on page 17). Under Videoscape Control Suite Nodes, choose the node where you installed the COP file to be upgraded. In the COP Images to Install list, choose the COP file that you wish to install as the upgrade. In the COP Images Config Files area, click New Configuration Generation. The COP Config page opens. Complete the entries for the COP file you are upgrading. Make sure they are the same as when you installed the version of the Service that is already installed on your system. Save your configuration file, and then generate your configuration. After the configuration generates, you return to the COP Install main page. In the COP Install page, choose the following: OL-27753-06 The Videoscape Control Suite node on which you installed the COP file The COP file to be installed as an upgrade The configuration file you just generated 121 Chapter 20 Upgrade COP Files 9 In the COP Images to Install section of the pages, click COP Upgrade. Result: The following pop-up message is displayed: 10 Click OK to confirm (or click Cancel to abort the operation). A pop-up confirmation message is displayed. 11 Click OK to start the upgrade process. As the upgrade proceeds, the COP Install Status column updates to show your progress. 12 Confirm that the installation process completes successfully. Notes: The values in the COP Install Status column should indicate SUCCESS and the Status Message should indicate Install Completed. After the upgrade of the AlertManager COP file, the Native Library will need to be updated. Complete the following steps to update this library: a Enter the following command: cp /opt/conductorapps/alertmanager/lib/NativeLibrary.jar /opt/jboss/jboss-as7.1.0.Final/modules/com/cisco/conductorapp/easnativelib/mai n/NativeLibrary.jar b Bounce the jboss process: /usr/local/cm/bin/controlcenter.sh jboss restart 122 OL-27753-06 NOSQLCB Server Upgrade COP R2.1 to R3.0 GA NOSQLCB Server Upgrade COP R2.1 to R3.0 GA Perform these steps after upgrading the CMC and Videoscape Control Suite (VCS) ISO from Videoscape Conductor 2.1 to Videoscape Control Suite 3.0. Upgrading a Cluster with one NOSQLCB (formerly Couchbase) Server Note: The single NOSQLCB COP is typically used in the labs and developments. 1 Log on to the CMC UI by entering the CMC User and Password. 2 Choose Operate > Download to download the new NOSQLCB COP file and template. Note: Follow the instructions in Download the COP File Template and COP File (on page 17). 3 Once the download has completed, choose Operate > COP Install to install the NOSQLCB UI Component for management node. 4 Choose Services > Nosqlcb > Operations. 5 Choose the Nosqlcb Server Node, then choose Backup. The NOSQLCB Bucket Name list is displayed. 6 Choose the bucket to back up, then click Backup at the bottom of the window. 7 Uninstall the Couchbase COP R2.1 in the CMC page. 8 Install the new NOSQLCB R3.0 COP file in the CMC page of the Service node. Note: Follow the instructions in Install the NOSQLCB COP File (on page 19). OL-27753-06 123 Chapter 20 Upgrade COP Files 9 Choose Administration > Users, Roles & AAA > Service Account and set up a service account for NOSQLCB in the CMC page. 10 Log on to the NOSQLCB UI and create the bucket. 11 Install the NOSQLCB UI. a Choose Operate > COP Install. b Choose the management node on which to install the UI component. c Choose the NOSQLCB COP file for Version 3.0. d Click Install UI Component. e At the confirmation message, click Yes. f After the SUCCESS message is displayed, log out of the CMC and then log back in to see the new menu item, under Services. 12 Click Restore. A pop-up window is displayed listing the backup file(s) available to restore. 13 Choose the file to restore to the NOSQLCB server, then click Restore. The restore process begins, and when completed, displays SUCCESS. 124 OL-27753-06 NOSQLCB Server Upgrade COP R2.1 to R3.0 GA Upgrade a Cluster with Multiple NOSQLCB (formerly Couchbase) Servers 1 Log on to the NOSQLCB UI by entering the Nosqlcb User and Password. 2 Choose the Server Nodes tab. 3 For the last NOSQLCB Server node in the list, click Remove at far right. A confirmation pop-up message is displayed. 4 Click Remove to confirm the operation. A 1 appears in Pending Rebalance to let you know that one server needs to be rebalanced. 5 6 Continue selecting and removing nodes until there is only one NOSQLCB node left. For example, in the window above, you would remove nodes 10.90.185.173 and 10.90.185.172 and leave node 10.90.185.171. Click Rebalance to redistribute the data across the remaining node. The Rebalancing progress bar opens at top right in the UI. 7 Confirm that the Rebalancing progress bar completes and closes before continuing. 8 Log in to the CMC UI by entering the CMC User and Password. 9 Choose Operator > COP Install. 10 Choose the NOSQLCB Server Nodes you just removed using the UI. 11 Click COP Uninstall from the middle set of menus. A pop-up message is displayed. OL-27753-06 125 Chapter 20 Upgrade COP Files 12 Choose the Couchbase COP file installed on that server. 13 Choose Operate > Download to download the new NOSQLCB COP file and template. Note: Follow the instructions in Download the COP File Template and COP File (on page 17). 14 When the download has completed, choose Operate > COP Install and install the NOSQLCB. Note: Follow the instructions in Install the NOSQLCB COP File (on page 19). IP address of the server to be added You can simultaneously install the multiple NOSQLCB nodes that you removed in a previous step. 15 When the installation has completed, log in to the NOSQLCB Server UI. 16 Click Server Nodes, then click Add Server and enter the following: UserName (Administrator by default) Password (Public123 by default) Note: The password must be the same for all servers in the cluster. 17 Click Add Server to add the server to the NOSQLCB. Note: You must add back the same number of servers that you removed previously. 126 OL-27753-06 NOSQLCB Server Upgrade COP R2.1 to R3.0 GA 18 Click Rebalance to redistribute the data across the remaining node. The Rebalancing progress bar appears at top right in the UI. 19 20 21 22 23 OL-27753-06 The Rebalance operation now redistributes the data across all NOSQLCB servers in the cluster. Confirm that the Rebalancing progress bar completes and closes before continuing. Repeat steps 1 through 19 for the remaining NOSQLCB servers. In the CMC page, choose Administration > Users, Roles & AAA > Service Account to set up a Service Account. Note: The UserName and Password must match those in the R2.1 NOSQLCB. The defaults are Administrator (Username) and Public123 (Password). In the CMC page, choose Operate > COP Install to install the NOSQLCB UI component for the management node. Choose Services > Nosqlcb Database > Operations and confirm that the backup and restore page now appears. 127 Chapter 20 Upgrade COP Files Upgrade UPM from Version 2.5 to Version 3.0 UPM was introduced in Videoscape Control Suite Version 2.5 to help manage users, accounts, and devices. Note: If OMS is also deployed, manually modify the UPM configuration after upgrading UPM. 1 Download the latest UPM COP file and template file. 2 Uninstall the UPM Version 2.5 COP file (cisco.conductor-upm-2.5-0-11.cop.sgn): a Choose Operate > COP Install. b Choose the installed UPM node. c Click COP Uninstall. d Choose the cisco.conductor-upm-2.5-0-11.cop.sgn file. e Click Uninstall. 3 Generate the UPM configuration file: a Choose Operate > COP Install. b Choose the node upon which the COP file will be installed. c Click New Config Generation. d Fill in the required information in the configuration page. See the Install the User Profile Manager COP File (on page 32) for field descriptions. e Click Generate Configuration. 4 Install the UPM COP file (cisco.conductor-upm-2.5-0-28.cop.sgn): a Choose Operate > COP Install. b Choose the node upon which the COP file will be installed. c Highlight the new UPM COP file. d Click COP Upgrade. 128 OL-27753-06 Upgrade HornetQ from Version 2.5 to Version 3.0 Upgrade HornetQ from Version 2.5 to Version 3.0 HornetQ was introduced in Version 2.5 for UPM and UPM Adaptor. If you are running UPM, then an upgrade of HornetQ is required. 1 Download the latest HornetQ COP file and template file: Choose Operate > Download. 2 Uninstall Version 2.5 of the HornetQ COP file (cisco.conductor-hornetq-2.5-03.cop.sgn): a Choose Operate > COP Install. b Choose the installed HornetQ node. c Click COP Uninstall. d Choose the cisco.conductor- hornetq-2.5-0-3.cop.sgn file. e Click Uninstall. 3 Generate the HornetQ configuration file: a Choose Operate > COP Install. b Choose the node upon which the COP file will be installed. c Click New Config Generation. d Fill in the required information in the configuration page. See Install HornetQ (on page 24) for field descriptions. e Click Generate Configuration. 4 Install the HornetQ COP file: a Choose Operate > COP Install. b Choose the node upon which the COP file will be installed. c Highlight the new HornetQ COP file. d Click COP Upgrade. OL-27753-06 129 Chapter 20 Upgrade COP Files Upgrade UPM Adaptor (UPMCDA) from Version 2.5 to Version 3.0 To upgrade UPMCDA, complete these steps. 1 Download the latest UPMCDA COP file and template file. Operate > Software > Download 2 Install the UPMCDA COP file. a Operate > Software > COP Install b Choose the node where the old UPMCDA COP file is installed. c Generate the configuration for the new COP file. 3 Choose the same node and upgrade the COP file. 130 OL-27753-06 Upgrade OMS from Version 2.5 to Version 3.0 Upgrade OMS from Version 2.5 to Version 3.0 The Operator Messaging Service (OMS) has dependence upon NOSQLCB, UPM, HornetQ, and the UPM Adaptor COP files. Before upgrading the OMS service, make sure these COP files have been upgraded to R3.0 release. If OMS over TMS is to be deployed, the TMS COP file should also be installed before upgrading the OMS service. 1 Download the latest OMS COP file and template file: Choose Operate > Software > Download. 2 Install the UPMCDA COP file: a Choose Operate > Software > COP Install. b Choose the node where the old OMS COP file is installed. c Generate the configuration for the new COP file. 3 Choose the same node and upgrade the COP file. To guarantee that OMS works properly after the upgrade, manually modify the UPM configuration file: 1 As the root user, log in to the node on which UPM is installed. 2 Open the /opt/nds/upm/etc/config.properties file with a text editor. 3 Locate these two lines: 4 5 6 7 OL-27753-06 upm.filters.userProfile.metadata.com_cisco_oms.userkey1.value = regular1 upm.filters.userProfile.metadata.com_cisco_oms.userkey2.value = regular2 Change the string “userkey1” to “key1”. Change the string “userkey2” to “key2”. Save and close the file. Enter service nds_upm restart to restart the UPM service. 131 Chapter 20 Upgrade COP Files Upgrade OMS from Version 3.0 to Version 3.1 OMS supports an upgrade to R3.1 from R3.0. The data of OMS upgrades automatically and users do not need to generate a configuration file. Note: OMS cannot be upgraded to R3.1 from R2.0 or R2.5. 1 Back up the NOSQLCB data from the CMC. 2 Download the OMS COP R3.1 image from the CMC. a In the CMC, choose Operate > Cop Install. b Choose the node upon which the OMS R3.1 COP image is to be installed. c Click COP Upgrade. Note: No new configuration file needs to be generated. 3 In the confirmation message, click OK. OMS upgrades. Important: Note these important points about the OMS upgrade. The OMS upgrade from R3.0 to R3.1 changes NOSQLCB data. Therefore, a backup of R3.0 NOSQLCB data needs to exist, so that you can restore it in the event that the upgrade fails. If the upgrade fails, OMS rolls back to the previous version automatically. However, your NOSQLCB data may need to be restored. Do not create, delete, or change any parameters, rules, or groups during the upgrade. During the upgrade, the message publishing function is available if there are other OMS services in an In Service status. 132 OL-27753-06 Upgrade the UI Component of COP Files Upgrade the UI Component of COP Files Some COP files now have plug-in components to the management node that integrates their menu items into the Management UI. If you are upgrading the UI component of a COP file, the following steps must be completed to make sure that the Management UI remains stable. 1 Uninstall the UI component of the COP file: a Select the CMC management node and remove the NOSQLCB UI component. b Select the NOSQLCB Cop file. c Click Uninstall UI Component. 2 After the COP file installation, install the COP file's UI component on the management node. OL-27753-06 133 21 Chapter Uninstall COP Files 21 Introduction This chapter provides instructions for uninstalling COP files. In This Chapter OL-27753-06 Uninstall COP Files............................................................................. 136 135 Chapter 21 Uninstall COP Files Uninstall COP Files This section describes how to uninstall COP files. Note: All of the Services except for WFE support uninstalling COP files. Important: Support for uninstalling COP files is currently disabled in EPM. Uninstall Procedure 1 2 3 4 5 136 In the management console main page, navigate to Operate > COP Install. The COP Install main page opens. Under Videoscape Control Suite Nodes, choose the node from which to uninstall the COP file. In the COP Images to Install list, click COP Uninstall. A window appears listing the COP files installed on the selected node. Choose the COP file to be uninstalled from the list. Click Uninstall to confirm (or click Cancel to abort the operation). The following pop-up message is displayed: OL-27753-06 Uninstall COP Files 6 7 Click OK to confirm (or click Cancel to abort the operation). The following pop-up message is displayed: Note: The COP Install Status column updates to show your progress, as shown in the following illustration. Continue watching the display to confirm that the uninstall process completes successfully. Note: After uninstalling a COP file, you can manually remove the Service Instance, Virtual Service Namespace, Account JID, and PubSub(s), as described below, to clean up all files associated with the COP installation. Removing the Service Instance To remove the Service Instance: 1 Choose Message Infrastructure > Service Infrastructure > Service Instance. The Service Instance list is displayed. 2 Choose the Service Instance associated with the COP file that was just uninstalled. 3 Click Remove to remove the Service Instance. Note: The Service Instance cannot be removed if it is IS. Removing the Virtual Service To remove the Virtual Service: 1 Choose Message Infrastructure > Service Infrastructure > Virtual Service. The Virtual Service list is displayed. OL-27753-06 137 Chapter 21 Uninstall COP Files 2 3 Choose the Virtual Service associated with the COP that was just uninstalled. Click Remove to remove the Virtual Service. Removing the Account JID Creating the Service Instance JID also creates an Account JID. To remove the Account JID: 1 Choose Message Infrastructure > Message Fabric > Account JID. The Account JID list is displayed. 2 3 Choose the JID that was removed from the Service Instance. Click Remove to remove the Account JID. Removing PubSub(s) If the COP that was uninstalled creates PubSub entries, you can delete these manually. To remove PubSub entries: 1 Choose Message Infrastructure > Message Fabric > Pubsub Subscribe. The Publish Subscribe list is displayed. 2 Choose the Pubsub to which the Service was subscribed. 3 Choose the Pubsub that was created by the Service from the list at the bottom of the page. 4 Click Remove to remove the PubSub. 138 OL-27753-06 22 Chapter Troubleshooting 22 Introduction This chapter provides information that can help with troubleshooting COP file installations. In This Chapter OL-27753-06 Troubleshoot COP File Installation .................................................. 140 139 Chapter 22 Troubleshooting Troubleshoot COP File Installation This section describes issues that may arise during COP file installation and suggests ways to resolve these issues. Unable to Find SFTP User The following error message indicates that the SFTP account has not been created before installing the COP file: image install initiation error: Unable to find SFTP user. If this error message appears, perform the procedure described in Create the SFTP User (on page 9), and then repeat the COP file installation procedure. Note: This error could occur after an ISO or CMC upgrade on the CMC node. If this error occurs, create a new SFTP user using a name different from that used previously. Problem with EPM Registration The EPM and COP file installation are successful but Registration is displayed in red, indicating a problem with registration. If this occurs, verify that a PubSub for EPM exists and that the secondary PubSubs have been created. If they have not, define the PubSub(s) as described in Verify the PubSub (on page 14), and then uninstall and reinstall the COP file. AM and COP Files Install, but Cannot Create PubSub If this problem occurs, verify that the PubSub used in the Configuration file exists. If it does not, define the PubSub as described in Verify the PubSub (on page 14), and then uninstall and reinstall the COP file. 140 OL-27753-06 Troubleshoot COP File Installation ClientDirectory Installs, but No Communication with EPM or OSM If this problem occurs, confirm that you have done all of the following: Configure Connection Manager as described in Configure Connection Manager Configure JSM as described in Configure Connection Manager Create the OpenPort as described in Configure Connection Manager Edit the CD Configuration to add the JIDMAP entries as described in Install the ClientDirectory COP File Verify that the PubSub used in the Configuration file exists If the PubSub does not exist, define the PubSub as described in Verify the PubSub (on page 14), and then uninstall and reinstall the COP file. OMS and COP Files Install, but a 504 Error is Generated If this error occurs, verify that the PubSub used in the Configuration file exists. If it does not, define the PubSub as described in Verify the PubSub (on page 14), and then uninstall and reinstall the COP file. OL-27753-06 141 23 Chapter Customer Information 23 If You Have Questions If you have technical questions, call Cisco Services for assistance. Follow the menu options to speak with a service engineer. Access your company's extranet site to view or order additional technical publications. For accessing instructions, contact the representative who handles your account. Check your extranet site often as the information is updated frequently. OL-27753-06 143 A Appx auto letter Appendix A NOSQLCB COP File Installation for Videoscape Control Suite 2.1 This appendix provides instructions for installing the NOSQLCB COP file under Cisco Videoscape Control Suite 2.1. In This Appendix OL-27753-06 Install the NOSQLCB COP File (2.1) ................................................ 146 Configure the NOSQLCB Server ...................................................... 149 145 Chapter 23 Customer Information Install the NOSQLCB COP File (2.1) The NOSQLCB installation includes: An Encrypted Username and Password The NOSQLCB Cluster size in Megabytes (MB) An entry whether this is the first node installed The IP address of the first node installed All of this information allows for the automation of the NOSQLCB installation. The following instructions describe the steps for installing a NOSQLCB Cluster. Installing NOSQLCB Servers Install the First NOSQLCB Server 1 In the management console main page, navigate to Operate > COP Install. 2 Under Videoscape Control Suite Nodes, choose the node on which you would like to install the NOSQLCB COP file. 3 In the COP Images to Install list, choose the COP file that you wish to install. 4 In the COP Images Config Files area, click New Configuration Generation. The COP Config dialog for the NOSQLCB COP Install opens. 5 Enter the following encrypted login credentials: User name (Administrator): U2FsdGVkX18wZF11q2U7FRLGZB95XiJz8290kZw2gVw= 6 7 8 146 Password (Public123): U2FsdGVkX183o0m9jIfMKVa/bRWc0jcE+8mmWvTV3T0= Note: If you prefer to generate your own encrypted user name and password, contact Cisco for the required tool. In the Per Node RAM Quota (MB) field, enter the amount of RAM to be allocated to the NOSQLCB cluster. Note: We recommend setting this value to roughly half the total RAM available. In the First NOSQLCB Server field, enter yes. Note: You may also fill in the First Couchbase server IP Address field, but this information is not used for the first NOSQLCB server. Under COP Configuration Attributes, check the box next to the first NOSQLCB server to be configured. OL-27753-06 Install the NOSQLCB COP File (2.1) 9 Click Generate Config from the COP Configuration Attributes section of the dialog. When prompted, click OK to generate the configuration file. After a moment, the following message is displayed to indicate that the configuration file was generated successfully. 10 Click OK to return to the COP Install page. 11 In the COP Install page, choose the following: The service node on which you want to install the COP file When the installation is complete, all rows in the COP Install Status column will display SUCCESS. Before proceeding, be sure that all components installed successfully. The following example shows an installation in which one component is still in progress. The NOSQLCB COP file that you want to install The configuration file that you just created 12 In the COP Images to Install section of the page, click COP Install. A confirmation message appears. 13 Click OK to confirm the COP install. A second message appears confirming that the installation was initiated. 14 Wait a few seconds and confirm that the COP Install Status column displays SUCCESS or IN_PROGRESS. Notes: Install Other NOSQLCB Servers 1 Complete Steps 1-7 of Install the First NOSQLCB Server above for the next NOSQLCB server to be configured. The COP Config page is displayed. 2 In the First Couchbase Server field, enter no. 3 In the First Couchbase Server IP Address field, enter the IP address of the first NOSQLCB server. 4 Under COP Configuration Attributes, check the box next to the NOSQLCB server to be configured. OL-27753-06 147 Chapter 23 Customer Information 5 Click Generate Config from the COP Configuration Attributes section of the dialog. When prompted, click OK to generate the configuration file. After a moment, the following message is displayed to indicate that the configuration file was generated successfully. 6 7 Click OK to return to the COP Install page. In the COP Install page, choose the following: The service node on which you want to install the COP file When the installation is complete, all rows in the COP Install Status column will display SUCCESS. Before proceeding, be sure that all components installed successfully. The following example shows an installation in which one component is still in progress. The NOSQLCB COP file that you want to install The configuration file that you just created 8 In the COP Images to Install section of the page, click COP Install. A confirmation message appears. 9 Click OK to confirm the COP install. A second message appears confirming that the installation was initiated. 10 Wait a few seconds and confirm that the COP Install Status column displays SUCCESS or IN_PROGRESS. Notes: Note: We recommend that you delete all NOSQLCB configured files in the management console page after all the NOSQLCB nodes are installed successfully. 148 OL-27753-06 Configure the NOSQLCB Server Configure the NOSQLCB Server OL-27753-06 1 Open the NOSQLCB page: Example: http://<nodename>:8091 2 Click SETUP. 149 Appendix A NOSQLCB COP File Installation for Videoscape Control Suite 2.1 150 3 In the CONFIGURE SERVER window, enter 50000 in the Per Server RAM Quota field. 4 Click Next. OL-27753-06 Configure the NOSQLCB Server OL-27753-06 5 In the SAMPLE BUCKETS window, click Next; do not select anything on this window. 6 In the CREATE DEFAULT BUCKET window, deselect Index replicas. 7 Click Next. 151 Appendix A NOSQLCB COP File Installation for Videoscape Control Suite 2.1 8 In the NOTIFICATIONS window, uncheck the Enable software update notifications check box. 9 Click Next. 10 In the CONFIGURE SERVER window, enter a Password (Public123) for the administrator account. 11 Click Next. 152 OL-27753-06 Configure the NOSQLCB Server 12 In the Cluster Overview window, click Data Buckets. 13 In the Data Buckets window, click the arrow to the left of default. 14 Click Edit in the Access Control field. OL-27753-06 153 Appendix A NOSQLCB COP File Installation for Videoscape Control Suite 2.1 15 Click Delete to remove the bucket and then click Delete again in the pop-up confirmation message. 16 Click Create New Data Bucket. 154 OL-27753-06 Configure the NOSQLCB Server 17 Configure the Create Bucket window according to this example. Notes: For Bucket Name, enter endpoint. For Bucket Type, click Couchbase. For password, enter cisco123. For Per Node RAM Quota, enter 20000 (20,000). This creates the Endpoint bucket with a size of 20,000 MB. This leaves 30,000 MB free for other buckets or for expansion. Uncheck the Index replicas check box. Important: Write down the Bucket Name and password. You will need this information later when you install the Endpoint Manager. 18 Click Create. Result: The system displays the newly created data bucket. OL-27753-06 155 Appendix A NOSQLCB COP File Installation for Videoscape Control Suite 2.1 19 Click Settings, and then choose Auto-Failover. Check the Enable auto-failover check box, and then click Save. This enables auto-failover on the NOSQLCB cluster. 20 To add additional nodes, click Server Nodes, and then click Add Server. Enter the IP address of the server that you want to add, and then the password that you entered when you created the first server. Then, click Add Server again. 21 Click Server Nodes and then click Rebalance to add the new server to the cluster. 156 OL-27753-06 Configure the NOSQLCB Server 22 Wait for the servers to rebalance. Example: Rebalanced servers. 23 Go to Install the Endpoint Manager Service. The configuration of the NOSQLCB server is complete. OL-27753-06 157 Americas Headquarters http://www.cisco.com Cisco Systems, Inc. Tel: 408 526-4000 170 West Tasman Drive 800 553-6387 San Jose, CA 95134-1706 Fax: 408 527-0883 USA This document includes various trademarks of Cisco Systems, Inc. Please see the Notices section of this document for a list of the Cisco Systems, Inc., trademarks used in this document. Product and service availability are subject to change without notice. © 2014 Cisco and/or its affiliates. All rights reserved. August 2014 Part Number OL-27753-06
© Copyright 2026 Paperzz