Table Of Contents
Installing, Upgrading and Uninstalling Cisco Unified Provisioning Manager
Preparing to Install Provisioning Manager
Preparing the Server
Preparing End Systems
Ports that Provisioning Manager Uses
Gathering Information to Provide During Installation
Installing Provisioning Manager
Adding the Provisioning Manager Home Page to the Internet Explorer Trusted Sites Zone
Cleaning Up a Failed New Installation
Upgrading Provisioning Manager 1.0 to Provisioning Manager 1.1
Upgrading Provisioning Manager on One System (Application and Database on the Same System)
Upgrading Provisioning Manager for a Distributed System (Application and Database are on Separate Systems)
Backing Up The Provisioning Manager 1.0 Database
Restoring Provisioning Manager 1.0 when Provisioning Manager 1.1 Installation Fails
Uninstalling Provisioning Manager
Installing, Upgrading and Uninstalling Cisco Unified Provisioning Manager
This chapter describes installing Cisco Unified Provisioning Manager.
It includes:
•
Preparing to Install Provisioning Manager
• Installing Provisioning Manager
• Uninstalling Provisioning Manager
Preparing to Install Provisioning Manager
The information in this section helps you to deploy Provisioning Manager in your network. Do the following before you install Provisioning Manager:
•Make sure that hardware and software requirements for the server are met. (See Server Requirements, page 1-2.)
•Preparing the Provisioning Manager server for installation. (See Preparing the Server.)
•Configure end systems so that Provisioning Manager can obtain correct information from them. ( Preparing End Systems.)
•Determine whether your existing applications are already using ports that Provisioning Manager uses. (Existing applications should not use the ports that Provisioning Manager requires.) See Ports that Provisioning Manager Uses.
•Gather information that you might need to provide during the Provisioning Manager installation. (See Gathering Information to Provide During Installation.)
Preparing the Server
This section describes procedures that you may need to perform to prepare your server for installing Provisioning Manager on it.
Enabling the Full 4 GB RAM
On 4 GB system, Windows only detects 3.5 GB of RAM even though your system has 4 GB installed. If you want to choose the medium or large installation when installing Provisioning Manager, you must first enable all 4 GB of RAM on the system. Do the following:
Step 1 On the Provisioning Manager system, in Windows right-click My Computer.
Step 2 Select Properties.
Step 3 Select the Advanced tab.
Step 4 Under Startup and Recovery, click Settings.
Step 5 Click Edit. The boot.ini file opens.
Step 6 In the file, add "/PAE" in line starting with "multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=..."
Step 7 Restart the system.
Preparing End Systems
In Provisioning Manager, the physical resources (end systems that deliver voice and messaging services) are modeled as Processors. For example, a Cisco Unified Communications Manager or Cisco Unified Communications Manager Express system is modeled as a Call Processor and a Cisco Unity, Cisco Unity Express, or Cisco Unity Connection voicemail/unified messaging system is modeled as a Unified Message Processor.
Using Provisioning Manager, an administrator creates and configures these various processors. After the processors have been configured, all configuration and interaction with the end systems is handled by Provisioning Manager.
Some minimal configuration is required on the end systems before you can use them with Provisioning Manager. This section describes the preconfiguration steps required for Cisco Unified Communications Manager, Cisco Unified Communications Manager Express, Cisco Unity systems, Cisco Unity Connection, and Cisco Unity Express.
Cisco Unified Communications Manager Preconfiguration Dependencies
The Cisco Unified Communications Manager is the software-based, call-processing component of the Cisco IP telephony solution, and is part of Cisco Architecture for Voice, Video and Integrated Data (AVVID).
Additional data, voice, and video services such as unified messaging, multimedia conferencing, collaborative contact centers, and interactive multimedia response systems interact with the IP telephony solution through Cisco Communications Manager's open telephony application programming interface (API). Cisco Communications Manager is installed on the Cisco Media Convergence Server (MCS).
No specific preconfiguration is generally required on the Cisco Unified Communications Manager for Provisioning Manager. However, the following conditions should already have been met during a normal installation or upgrade, and are noted here as installation dependencies for creating a Call Processor in Provisioning Manager:
•Install Cisco Unified Communications Manager.
•For Cisco Unified Communications Manager release 4.x, ensure that the Cisco Unified Communications Manager service and Internet Information Service (IIS) (at minimum) are running on the Cisco Unified Communications Manager.
•If Cisco Unity is used in this configuration, configure the Cisco Unified Communications Manager voicemail ports.
•Configure Cisco Unified Communications Manager to not allow autoregistration of phones, which indicates that the Cisco Unified Communications Manager can assign phone numbers. When Provisioning Manager is deployed, this functionality exists within Provisioning Manager.
•Create a user and password with administrator privileges that can be used by Provisioning Manager to access Cisco Unified Communications Manager. The requirements of the user and password vary depending on whether multilevel administration access (MLA) is enabled (see Table 2-1).
Note All interactions with Cisco Unified Communications Manager and Provisioning Manager are through the AVVID XML Layer APIs (AXL/SOAP).
Determining the Media Server Account to Use for Cisco Unified Communications Manager Access
To enable Provisioning Manager to access a Cisco Unified Communications Manager, you must supply the username and password for an account on the media server. The account to use depends upon the Cisco Unified Communications Manager version and might also depend on whether MLA is enabled for the Cisco Unified Communications Manager. Table 2-1 lists the options.
Table 2-1 Username and Password for Accessing the Cisco Unified Communications Manager
Cisco Unified Communications Manager Version on Media Server
|
MLA Enabled
or Disabled for Cisco Unified Communications Manager
|
Required Account
|
4.x
|
Enabled
|
Multilevel administration access account with full access to the Standard Serviceability Functional Group.
|
Disabled
|
Valid Windows 2000 administrator account on the media server.
|
5.x
|
N/A
|
A Unified Communications Manager user that is assigned a role with the privilege to use the AXL Database API resource in the Cisco Call Manager AXL Database application.
Standard AXL API Access is one of the predefined roles in Unified Communications Manager that has this privilege.
|
6.x
|
N/A
|
A Unified Communications Manager user that is assigned a role with the privilege to use the AXL Database API resource in the Cisco Call Manager AXL Database application.
Standard AXL API Access is one of the predefined roles in Unified Communications Manager that has this privilege.
|
Cisco Unified Communications Manager 4.x with More than 500 Users
Cisco Unified Communications Manager 4.x has a default search results limit of 500 for listing users. If you have more than 500 users, you must increase the setting for "Maximum Search Results" on the Cisco Unified Communications Manager.
Step 1 On the Cisco Unified Communications Manager server, start DC Directory Administrator.
Step 2 Log in using Directory Manager with the Cisco Unified Communications Manager password.
Step 3 Click the cisco.com node. Admin, CCN, Groups and Users should appear.
Note If these do not appear select View > Zoom To Admin Node.
Step 4 Click CCN.
Step 5 Select systemProfile. On the right, you should see Hoteling Profile and System Profile.
Step 6 Double-click System Profile.
Step 7 Select the CCM Configuration tab.
Step 8 Click Modify.
Step 9 Change Maximum Search Results to a value higher than the number of users that you expect to have (maximum supported is 30,000).
Step 10 Click OK.
Step 11 You can verify your changes by doing the following:
a. Open Internet Explorer and log into Cisco Unified Communications Manager.
b. Select User > Global Directory, then click Search. This lists all users. You should not receive any warning messages if you get more than 500 results.
Cisco Unified Communications Manager Express Preconfiguration Dependencies
Cisco Unified Communications Manager Express is a solution, embedded in Cisco IOS Software, that provides call processing for Cisco Unified IP phones.
Like Cisco Unified Communications Manager, Cisco Unified Communications Manager Express is modeled in Provisioning Manager as a Call Processor. The only difference from an administrative aspect is that it is represented by a different type of Call Processor.
Provisioning Manager requires that the Cisco Unified Communications Manager Express be installed on a supported platform with the appropriate Cisco IOS Software version and Cisco Unified Communications Manager Express load.
Provisioning Manager requires the following preconfiguration be performed on Cisco Unified Communications Manager Express:
•Disabling of auto-allocation of directory numbers. This is done through the Cisco IOS interface.
•Disabling of ephone auto-registration. This is required for Cisco Unified Communications Manager Express 4.0 or later.
These configurations are done through the Cisco IOS interface.
Step 1 First, verify that auto-allocation is enabled.
$ telnet 172.19.50.247
Trying 172.19.50.247...
Connected to 172.19.50.247.
Escape character is '^]'.
User Access Verification
Password:
CCME-1>enable
Password:
CCME-1#show telephony
CONFIG (Version=3.0)
=====================
Cisco Communications Manager Express
ip source-address 172.19.50.247 port 2000
max-ephones 24
max-dn 100
max-conferences 4
max-redirect 5
time-format 12
date-format mm-dd-yy
keepalive 30
timeout interdigit 10
timeout busy 10
timeout ringing 180
web admin system name root password cisco
web admin customer name cisco password cisco
edit DN through Web: enabled.
edit TIME through web: enabled.
Log (table parameters):
max-size: 150
retain-timer: 15
(password): abcd
create cnf-files version-stamp 7960 Jan 15 2004 16:48:05
auto assign 1 to 100 type 7960 cfw 5001 timeout 30
local directory service: enabled.
xml schema http://gkar.cisco.com/schema/axlsoap.xsd
In this case, auto-allocation is on, as shown by the auto assign line.
Step 2 To disable auto-allocation, run the following command at the enable prompt:
CCME-1#config term
Enter configuration commands, one per line. End with CNTL/Z.
CCME-1(config)#telephony-service
CCME-1(config-telephony)#no auto assign 1 to 100 type 7960 cfw 5001 timeout 30
CCME-1(config-telephony)#no auto-reg-ephone
Note The no auto-reg-ephone command is required for Cisco Unified Communications Manager Express 4.0 or later.
CCME-1(config-telephony)#exit
CCME-1(config)#exit
CCME-1#show telephony
Step 3 To verify that the change has taken effect, run another show telephony command. The auto assign line should no longer appear.
Step 4 Run a write memory command, which will write the changes out to the system's nonvolatile memory in case of a reboot.
How Provisioning Manager Manages Communications Manager Express
Cisco Unified Communications Manager Express uses two main commands to provision phones for end subscribers:
•telephony ephone-dn—Manages directory numbers.
•telephony ephone—Assigns directory numbers to lines on one or more phones.
Both commands allow subscriber information to be associated to the directory number or the line. Provisioning Manager uses these native abilities in Cisco Unified Communications Manager Express to store and synchronize subscriber information.
Provisioning Manager is able to synchronize back the phones, lines, directory numbers, and subscriber information from an existing Cisco Unified Communications Manager Express. Depending on how the subscriber information was used in the telephony ephone and telephony ephone-dn commands, Provisioning Manager is able to fully construct a user account for that subscriber. Provisioning Manager supports shared lines and directory numbers while doing this.
When provisioning, Provisioning Manager uses the description command in the ephone configlet to hold the subscriber name and department information. Provisioning Manager also uses the name command in the ephone-dn configlet to hold the subscriber's first and last names.
Note The Cisco Unified Communications Manager Express ephone-dn name field is limited to 30 characters. If the subscriber's first and last names (combined) exceed that limit, you may get an error.
Cisco Unity and Cisco Unity Connection System Preconfiguration Dependencies
Before you can create a Unified Message Processor based on Cisco Unity or Cisco Unity Connection (only required for Cisco Unity Connection 1.1.1) in Provisioning Manager, you must do the following:
•Install and configure the message store using Microsoft Exchange 2000 or 2003. (Required for Cisco Unity only.)
•Configure an integration with one or more corresponding Cisco Unified Communications Manager systems.
•Create a SQL Server user and password that can be used by Provisioning Manager to access the SQL Server database on Cisco Unity or Cisco Unity Connection (only required for Cisco Unity Connection 1.1.1). The SQL Server user requires access to both the Cisco Unity (or Cisco Unity Connection) and master databases. See Creating a SQL Server User and Password for Cisco Unity or Cisco Unity Connection.
•Verify the TCP/IP port used by Cisco Unity or Cisco Unity Connection (only required for Cisco Unity Connection 1.1.1). This port number is required when you create a Unified Message Processor.
•Define Class of Service and Subscriber templates.
Creating a SQL Server User and Password for Cisco Unity or Cisco Unity Connection
Step 1 On the Cisco Unity (or Cisco Unity Connection) system, select Start > SQL Server > Enterprise Manager. The Enterprise Manager window appears.
Step 2 In the navigation tree, select Microsoft SQL Servers > SQL Server Group > (local) (Windows NT).
Step 3 Right-click (local) (Windows NT) and select Properties. The SQL Server Properties (Configure) window appears.
Step 4 Click the Security tab.
Step 5 Under Authentication, select SQL Server and Windows.
Step 6 In the navigation tree under (local) (Windows NT), select Security > Logins.
Step 7 Create a new login. Do the following:
a. Right-click Logins. The SQL Server Login Properties - New Login window appears.
b. Enter a name for the login.
c. Select SQL Server Authentication.
d. Select UnityDb (this is for Cisco Unity, for Cisco Unity Connection the database is UnityDirDb) for the default database.
e. Click the Database Access tab.
f. Select both the UnityDb and the master database.
g. For both databases, select the following roles: db_owner, db_datareader, and db_datawriter.
h. Reboot the SQL server.
Verifying the TCP/IP Port Used by Cisco Unity or Cisco Unity Connection
Step 1 On the Cisco Unity system, select Start > SQL Server > Enterprise Manager. The Enterprise Manager appears.
Step 2 From the menu, click Action. Then select Properties. The SQL Server Properties (Configure) dialog box appears.
Step 3 In the General tab, click Network Configuration. The SQL Server Network Utility window appears.
Step 4 Select TCP/IP, then click Properties.
Step 5 In the window that appears, the default TCP/IP port is displayed. You will need to know this port number when you create a Unified Message Processor.
Cisco Unity Express Preconfiguration Dependencies
Before you can create a Unified Message Processor based on Cisco Unity Express in Provisioning Manager, you must determine the Service Engine Interface number for Cisco Unity Express. The Service Engine Interface number is required when adding a Cisco Unity Express to Provisioning Manager.
Determining the Service Engine Interface Number for Cisco Unity Express
The Service Engine Interface number is located on the router that hosts Cisco Unity Express.
Step 1 Log in to the router that hosts Cisco Unity Express.
Step 2 Run the command show running-config.
In the resulting output, look for the following:
Interface Service-Engine 2/0
In this example, 2/0 is the Service Engine Interface number.
Ports that Provisioning Manager Uses
Before installing Provisioning Manager, make sure that the appropriate ports are available.
Table 2-2 lists the ports that need to be open on the Provisioning Manager system. Table 2-3 lists the ports that need to be open on the firewall between Provisioning Manager and the device.
Table 2-2 Ports Used on the Provisioning Manager System
Port Numbers
|
Service Name/Protocols
|
1098
|
JBoss RMI activation.
|
1099
|
JBoss JNDI.
|
1602
|
Network Interface and Configuration Engine (NICE). This is configurable during the advanced installation process.
|
4444
|
JBoss RMI/JRMP.
|
4445
|
JBoss pooled invoker.
|
5432
|
PostgreSQL database. This is configurable during the advanced installation process.
|
8008
|
JBoss Application Sever. This is configurable during the advanced installation process.
|
8009
|
AJP Connector.
|
8083
|
JBoss Webservice.
|
8093
|
JBoss UILServerILService.
|
80
|
HTTP/Apache Web Server. This is configurable during the advanced installation process.
|
Table 2-3 Ports Used to Communicate with Other Devices
Port Numbers
|
Service Name/Protocols
|
Application
|
80
|
HTTP/Apache Web Server
|
Cisco Unified Communications Manager.
|
443
|
HTTPS
|
Cisco Unified Communications Manager 4.x.
|
8443
|
HTTPS
|
Cisco Unified Communications Manager 5.0.
|
22
|
SSH
|
Cisco Unified Communications Manager Express and Cisco Unity Express.
|
23
|
Telnet
|
Cisco Unified Communications Manager Express and Cisco Unity Express.
|
1433
|
MS SQL
|
Cisco Unity and Cisco Unity Connection(1.1.1 only).
|
Gathering Information to Provide During Installation
You might need to supply the following information while you are installing Provisioning Manager:
•For a simple installation, you will need to have the following:
–A license file, or you can choose to use the evaluation version.
–Password for the administrator user.
–Username ans password for the PostgreSQL administrator (default is postgres).
•For an advanced installation, what you need depends on your installation. The following list contains information you may need to have:
–A license file, or you can choose to use the evaluation version.
–A port number for the Apache web server.
–A port number for the PostgreSQL database.
–Hostname or IP address for the systems that can connect to the PostgreSQL database.
–Username and password for the Windows user that the PostgreSQL database uses.
–Username and password for the PostgreSQL administrator.
–The JBoss application server name.
–The port number for the JBoss application server.
–Username and password for the application database user.
–Password for the administrator user.
–Port number for the NICE service.
Installing Provisioning Manager
The installation process takes approximately 60 minutes to complete.
Follow these guidelines when installing Provisioning Manager:
•Provisioning Manager requires a dedicated system; do not install it on a system with:
–Third-party management software (such as HP OpenView or NetView).
–Cisco Secure Access Control Server (ACS).
–Any Cisco applications other than those that are documented to be able to coexist with Provisioning Manager.
•If installing on a system with Cisco Security Agent, before installing Provisioning Manager disable Cisco Security Agent.
•Do not install on any of your voice application servers on a Cisco Unified Communications Manager server.
•Verify that the system date and time are set properly.
•To speed up installation, disable all virus-scan software while installing.
Step 1 Make sure your system meets these prerequisites:
•Required (or desired) operating system upgrades have been performed.
•Required service packs are installed.
For system requirements, see Server Requirements, page 1-2.
Step 2 Close all open or active programs. Do not run other programs during the installation process.
Step 3 As the local administrator, log in to the machine on which you will install the Provisioning Manager software, and insert the Cisco Unified Provisioning Manager CD-ROM into the CD-ROM drive. The Cisco Unified Provisioning Manager 1.1 window opens.
Note If the CD-ROM is already in the CD-ROM drive and you stopped the installation process to close programs or if Autostart is disabled, click cupm1.1-setup.exe to restart the process.
Step 4 Click Install. The Welcome window appears.
Step 5 Click Next. The Software License Agreement window appears.
Step 6 Accept the Software License Agreement and then click Next.
Step 7 In the Destination Directory window, click Next to accept the default installation directory.
Note Do not install Provisioning Manager under any directory where the directory name contains a space (for example, Program Files).
Step 8 Select the appropriate sizing for your Provisioning Manager installation.
Note The options that appear depend on the amount of memory that your system has.
Step 9 Click Next.
Step 10 Choose an installation type, Simple or Advanced:
•Select Simple, and click Next.
a. Select one of the following, and then click Next:
–If you have a license file for this product, specify its location—Browse to enter the location.
–Select this option to evaluate the product—You can complete the installation and then register the license file later.
b. Enter a username and password for the PostgreSQL administrator, then click Next.
c. Enter a password for the administrator user.
d. Click Next.
e. Select the appropriate time zone, then click Next. The Summary page appears.
f. Click Install.
•Select Advanced, and click Next. The advanced installation has two distribution options. In the first, all of Provisioning Manager (application and database) is installed on one system. In the second, the Provisioning Manager application and database are installed on separate systems. This scenario requires that you enter the IP address of the two systems.
a. Choose the components:
–Database—Installs the Provisioning Manager database only.
–CUPM—Installs the Provisioning Manager application only.
Note If you choose to install the database and the application on separate systems, Provisioning Manager is not completely installed until both the database and application are installed.
When you install the database on a separate machine, at the end of the installation you will receive a message that states Provisioning Manager was installed successfully. But only the database is installed on that system.
Advanced installation enables you to configure the following information, depending on which components you are installing:
–Port number for the Apache web server.
–Port number for PostgreSQL database.
–Hostname or IP address for the systems that can connect to the PostgreSQL database. This is required if the database is being installed on a separate system.
–Host name or IP Address of the computers that can connect to the PostreSQL database. This is required if the application is being installed on a separate system.
–Username and password for the Windows user.
Note If the username already exists on the system, the password entered must be the current password for that user.
–Username and password for the PostgreSQL administrator.
–The JBoss application server name.
–Port number for the JBoss application server.
–Username and password for the application database user.
–Password for the Provisioning Manager administrator user.
–Port number for the NICE service.
b. Select one of the following, and then click Next:
–If you have a license file for this product, specify its location—Browse to enter the location.
–Select this option to evaluate the product—You can complete the installation and then register the license file later.
c. Select the appropriate time zone, then click Next. The Summary page appears.
d. Click Install.
Note If an error message appears similar to the following appears, it means that the installation has failed:
Postgres install failed with error code 1603
Before trying to install Provisioning Manager again, you must clean up the system. See Cleaning Up a Failed New Installation.
Step 11 Eject the CD-ROM.
Note Store the CD-ROM in a secure, climate-controlled area for safekeeping.
Step 12 Click Finish.
Step 13 After the installation completes, verify that Provisioning Manager is installed correctly by accessing the Provisioning Manager login page. From the Windows desktop, select Start > Programs > Cisco Unified Provisioning Manager > Log in to Cisco Unified Provisioning Manager.
Note If Enhanced Security is enabled on the Windows 2003 system, you must add the Provisioning Manager home page to the Internet Explorer Trusted Sites Zone. You will not be able to access the Cisco Unified Provisioning Manager home page until it is added to the trusted sites. See Adding the Provisioning Manager Home Page to the Internet Explorer Trusted Sites Zone.
Adding the Provisioning Manager Home Page to the Internet Explorer Trusted Sites Zone
If Enhanced Security is enabled on the Windows 2003 system, you must perform the following procedure before you can access the Provisioning Manager home page.
Step 1 Open Provisioning Manager and select Start > Programs > Cisco Unified Provisioning Manager.
Step 2 From the File menu, select Add this site to.
Step 3 Click Trusted Sites Zone.
Step 4 In the Trusted Sites dialog box, click Add to move the site to the list.
Step 5 Click Close.
Step 6 Refresh the page to view the site from its new zone.
Step 7 Check the Status bar of the browser to confirm that the site is in the Trusted Sites Zone.
Cleaning Up a Failed New Installation
If Provisioning Manager did not install correctly, you must first clean up the system before trying to install Provisioning Manager again. These procedures are for a failed new installation of Provisioning Manager 1.1. If you need to clean up a failed upgrade of Provisioning Manager 1.0 to 1.1, see Restoring Provisioning Manager 1.0 when Provisioning Manager 1.1 Installation Fails.
After a failed installation, do the following:
•Delete the CUPM installation folder. If you selected the default location during installation, it is C:\CUPM.
•Delete the Documents and Settings\cupmuser folder.
•Remove the Windows user; cupmuser (cupmuser is the default name provided during installation). The Windows user name can be different, if you changed it during installation. For instructions on removing the Windows cupmuser, see Removing the CUPM Windows User.
Removing the CUPM Windows User
Step 1 On the Windows desktop, select Start > Settings > Control Panel.
Step 2 Double-click Administrative Tools.
Step 3 Double-click Computer Management.
Step 4 In the console tree, under Local Users and Groups, click Users.
Step 5 Right click the user account cupmuser and delete it.
Note The Windows username, cupmuser, is the default name provided during installation. The Windows username can be different, if you changed it during installation.
Step 6 Delete cupmuser's home direcotry. The default location is in the directory C:\Documents and Settings\.
Upgrading Provisioning Manager 1.0 to Provisioning Manager 1.1
There are two upgrade scenarios; select the set of procedures that matches your scenario:
• Upgrading Provisioning Manager on One System (Application and Database on the Same System)
• Upgrading Provisioning Manager for a Distributed System (Application and Database are on Separate Systems)
Upgrading Provisioning Manager on One System (Application and Database on the Same System)
Step 1 Manually backup your database. For instructions, see Backing Up The Provisioning Manager 1.0 Database.
Note This manual backup is not the same backup that occurs automatically during upgrade. Both backups must be performed.
Step 2 On the system where Provisioning Manager 1.0 is installed, make sure the following prerequisites are met:
•Required (or desired) operating system upgrades have been performed.
•Required service packs are installed.
For system requirements, see Server Requirements, page 1-2.
Step 3 Close all open or active programs. Do not run other programs during the installation process.
Step 4 As the local administrator, log in to the machine on which you will install the Provisioning Manager software, and insert the Cisco Unified Provisioning Manager CD-ROM into the CD-ROM drive. The Cisco Unified Provisioning Manager 1.1 window opens.
Note If the CD-ROM is already in the CD-ROM drive and you stopped the installation process to close programs or if Autostart is disabled, click cupm1.1-setup.exe to restart the process.
Step 5 Click Install. The Welcome window appears.
Step 6 Click Next. The Software License Agreement window appears.
Step 7 Accept the Software License Agreement and then click Next.
Step 8 A confirmation box appears, asking if you want to upgrade to Provisioning Manager 1.1. Click Install. A check of the system is performed, which verifies the following:
•No orders are in the Released state.
•All service actions are in the Closed state.
•All workflows are in the Finished state.
•No infrastructure, subscriber, or Domain synchronizations are running.
•No batch projects are running or are in the Active state.
If any of these conditions are not met, the installation will stop.
Note If you are upgrading only the database or only the application (because you have a distributed setup) not all the screens will appear during the upgrade process. Also, to complete the upgrade of a distributed setup, you must run the Cisco Unified Provisioning Manager 1.1 installation CD on both systems.
When only upgrading the database (for distributed setup), you will be required to re-enter the PostgreSQL database administrator password and the application database user username (the default is cupm) and password.
Step 9 In the resulting dialog box, click Ok.
Step 10 Either re-enter the old password for the cupmuser (Windows user), or leave the field empty (a random password will be generated). Do not enter a new password. Click Next.
Step 11 Select a directory to backup the Provisioning Manager 1.0 data in, during upgrade.
Step 12 Select the appropriate time zone, then click Next. The upgrade proceeds.
Note If an error message appears, similar to the following:
C:\CUPM\httpd\conf\httpd.conf exists on this system and it has been modified since instllation. Do you want to remove this file?
The installation failed. Before trying to install Provisioning Manager again, you must clean up the system. See Restoring Provisioning Manager 1.0 when Provisioning Manager 1.1 Installation Fails.
Step 13 Eject the CD-ROM.
Note Store the CD-ROM in a secure, climate-controlled area for safekeeping.
Step 14 Click Finish.
Step 15 After the installation completes, verify that Provisioning Manager is installed correctly by accessing the Provisioning Manager login page. From the Windows desktop, select Start > Programs > Cisco Unified Provisioning Manager > Log in to Cisco Unified Provisioning Manager.
Note If Enhanced Security is enabled on the Windows 2003 system, you must add the Provisioning Manager home page to the Internet Explorer Trusted Sites Zone. You will not be able to access the Cisco Unified Provisioning Manager home page until it is added to the trusted sites. See Adding the Provisioning Manager Home Page to the Internet Explorer Trusted Sites Zone.
Upgrading Provisioning Manager for a Distributed System (Application and Database are on Separate Systems)
You must upgrade both the Provisioning Manager application and the Provisioning Manager database systems.
Step 1 Backup the Provisioning Manager 1.0 database. For information, see Backing Up The Provisioning Manager 1.0 Database.
Step 2 Upgrade the Provisioning Manager 1.0 database to 1.1. Since only the database is installed on the system, the installation program will only take you through the aplicable database upgrade screens. If you need additional information, see Upgrading Provisioning Manager on One System (Application and Database on the Same System).
Step 3 Upgrade the Provisioning Manager 1.0 application to 1.1. Since only the application is installed on the system, the installation program will only take you through the aplicable application upgrade screens. If you need additional information, see Upgrading Provisioning Manager on One System (Application and Database on the Same System).
Backing Up The Provisioning Manager 1.0 Database
Note This procedure requires postgres administrator level access.
Step 1 Shut down Provisioning Manager:
a. On the Windows desktop, select Start > All Programs > Cisco Unified Provisioning Manager > Stop Cisco Unified Provisioning Manager.
Note Alternately, you can stop the postgres process; go to Control Panel > Administrative Tools > Services > cupmPostgreSQL, select the service and click Stop.
Step 2 In a backup folder, make copies of the following files and directories (preferably on a different file server, also it is recommended that you burn the backup data onto a CD):
•<Installation directory>\install.log
•<Installation directory>\pgsql\data
•<Installation directory>\sep\dfc.properties
•<Installation directory>\sep\dfc.keystore
•<Installation directory>\jboss-4.0.3SP1\server\cupm\conf\login-config.xml
Note If you accepted the default location during installation, the installation directory is C:\CUPM.
Step 3 Restart Provisioning Manager (Start > All Programs > Cisco Unified Provisioning Manager > Start Cisco Unified Provisioning Manager).
Restoring Provisioning Manager 1.0 when Provisioning Manager 1.1 Installation Fails
If Provisioning Manager did not upgrade correctly, you must first clean up the system before trying to install Provisioning Manager again. These procedures are only for a failed upgrade. If you need to restore a failed new installation of Provisioning Manager, see Cleaning Up a Failed New Installation.
After a failed upgrade, do the following:
•Clean up the old installation of Provisioning Manager 1.0 (see Cleaning Up the Old Installation).
•Restore Provisioning Manager 1.0 (see Restoring Provisioning Manager 1.0).
If the database and the application are installed on separate systems, you must perform additional steps. See Additional Steps for Restoring a Provisioning Manager 1.0 Distributed Deployment to a Different Set of Hosts.
Cleaning Up the Old Installation
Step 1 Uninstall the Provisioning Manager installation. Depending upon where the installation failed, the application installed may appear as Provisioning Manager 1.0 or Provisioning Manager 1.1. Try to use the standard uninstallation process (see Uninstalling Provisioning Manager).
If the standard uninstallation process does not work, go to Step 2.
Step 2 If standard uninstallation fails, you will have to perform some or all of the following steps:
a. Remove the installation directory CUPM. This step may require a system reboot if the Provisioning Manager services are still running and using the resources from the installation location.
Note If you selected the default location during installation, it is C:\CUPM.
b. Remove the cupmuser (Windows user) if it still exists:
1. Select Start > Settings > Control Panel.
2. Double-click Administrative Tools.
3. Double-click Computer Management.
4. In the console tree, under Local Users and Groups, click Users.
5. Right-click the user account cupmuser and delete it.
6. Delete cupmuser's home directory. The default location is in the directory C:\Documents and Settings\.
c. Uninstall Postgres 8.1/8.2 if still exists.
d. Remove the folder C:\Program Files\Common Files\InstallShield\Universal\common\Gen1.
e. (Optional) You may need to delete the Provisioning Manager services. Make sure the services are not running before you delete them.
Provisioning Manager 1.0 services that need to be deleted:
•Apache2
•cupm JbossService
•cupm NICEService
•pgsql-8.1
Provisioning Manager 1.1 services that need to be deleted:
•Apache2
•cupm JbossService
•cupm NICEService
•pgsql-8.2
Use the following command to delete Windows services: sc.exe delete <service name>.
Restoring Provisioning Manager 1.0
Note These instructions assume that you are backing up and restoring on the same system.
Step 1 Shut down Provisioning Manager.
Step 2 Place copies of the the backup files into their original folders. Make sure you use the original names of the files and folders.
Note You must restore on the same drive that you backed up from. If you backed up from drive C:\, you must restore on drive C:\.
Step 3 Change the permission of the database directory:
a. Open Windows Explorer.
b. Right click the <Installation directory>/pgsql/data folder.
Note If you accepted the default location during installation, the installation directory is C:\CUPM.
c. Click Properties.
d. Click the Security tab.
e. Click Advanced.
f. Click cupmuser (if it is not present, add it).
Note Two cupmuser may appear, one will have Deny in the Type column. If there are two, delete the cupmuser that displays Deny in the Type column.
g. Click Edit ....
h. Select all the checkboxes in the Allow column, except for the following:
–Full Control
–Delete Subfolder and Files
–Take Ownership
–ChangePermission
i. Make sure the following checkbox is not selected: Apply these permissions to objects and/or containers within this container only.
j. Click OK..
k. Make sure the following checkbox is not selected: Allows inheritable permissions from the parent to propagate to this object and all child objects. Include these with entries explicitly defined here.
If this check box is selected, unchecking the box causes a warning dialogue box to appear. Click Remove.
l. Select the following checkbox: Replace permission entries on all child objects with entries shown here that apply to child objects.
m. Click OK..
Step 4 Start and stop the postgres service.
a. Go to Control Panel > Administrative Tools > Services > cupmPostgreSQL.
b. Click Start. Make sure that the service can be started.
c. Click Stop.
Step 5 Restart the system.
Additional Steps for Restoring a Provisioning Manager 1.0 Distributed Deployment to a Different Set of Hosts
If the database and the Provisioning Manager application are installed on separate systems, you must perform specific procedures on each system.
Step 1 On the system where the database is installed, you must change the following file:
<installLocation>\pgsql\data\pg_hba.conf
Add the line, host all all <New App Server IP Address>/32 md5.
Step 2 On the system where Provisioning Manager is running, in the file dfc.properties, find the property dfc.postgres.host, and change it to:
dfc.postgres.host=<New DB Server IP Address>
Step 3 On the system where the database is installed, open Start > Programs > PostgresSQL 8.2 > pgAdmin III. Login using the postgres admin password.
Step 4 On the system where the database is in installed, run the following:
delete from nicesyseng where host='<Old NICE Server IP Address>'
Step 5 On the system where the database is installed, restart the cupmPostgreSQL service.
Step 6 On the system where Provisioning Manager is running, restart the following services:
•cupm JbossService
•cupm NICEService
Uninstalling Provisioning Manager
Caution You must use the Provisioning Manager uninstallation program to remove Provisioning Manager from your system. If you try to remove the files and programs manually, you can seriously damage your system.
Step 1 Close all applications that are using Provisioning Manager files.
Step 2 As the local administrator, log in to the system on which Cisco Unified Provisioning Manager is installed.
Step 3 To start the uninstallation process, from the Windows desktop select Start > Programs > Cisco Unified Provisioning Manager > Uninstall Cisco Unified Provisioning Manager.
Step 4 Click Next to begin uninstalling.
A window appears, listing the components selected for uninstallation.
Step 5 Click Uninstall.
Messages showing the progress of the uninstallation appears.
Step 6 A message appears, reminding you that the cupmuser (Windows user) directory and the CUPM installation folder must be removed manually. Click Next.
Note The default Windows user name provided during installation is cupmuser. If you changed it during installation, the Windows user name may be different.
Step 7 Click Finish.
Step 8 If you want to reboot the system, select Yes, restart my computer, then click Finish.
Step 9 Manually delete the following folders from the Provisioning Manager system:
•The CUPM installation folder. If you selected the default location during installation, it is C:\CUPM.
•The Documents and Settings\cupmuser folder.
