Installation Guide for Cisco Unified Provisioning Manager 1.3
Installing, Upgrading and Uninstalling Cisco Unified Provisioning Manager
Downloads: This chapterpdf (PDF - 300.0KB) The complete bookPDF (PDF - 1.1MB) | Feedback

Installing, Upgrading and Uninstalling Cisco Unified Provisioning Manager

Table Of Contents

Installing, Upgrading and Uninstalling Cisco Unified Provisioning Manager

Preparing to Install Provisioning Manager

Preparing the Server

Enabling the Full 4 GB of RAM

Enabling SSL on the Provisioning Manager Server

Preparing End Systems

Cisco Unified Communications Manager Preconfiguration Dependencies

Cisco Unified Communications Manager Express Preconfiguration Dependencies

Cisco Unity and Cisco Unity Connection System Preconfiguration Dependencies

Cisco Unity Express Preconfiguration Dependencies

Interfaces that Provisioning Manager Uses

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

Removing the CUPM Windows User

Upgrading Provisioning Manager 1.2 to Provisioning Manager 1.3

Upgrading Provisioning Manager on One System (Application and Database on the Same System)

Upgrading Provisioning Manager on a Distributed System (Application and Database Are on Separate Systems)

Provisioning Manager Database Backup

Backing Up the Single-Machine Provisioning Manager Database

Backing Up Provisioning Manager on a Distributed Database

Restoring Provisioning Manager 1.2 If the Provisioning Manager 1.3 Installation Fails

Cleaning Up the Old Installation

Restoring Provisioning Manager 1.2

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

Upgrading Provisioning Manager 1.2 to Provisioning Manager 1.3

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-3.)

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.


Note The system that you use for your Provisioning Manager server should meet all the security guidelines that Microsoft recommends for Windows 2003 Server. See the Microsoft website for security guidance (http://www.microsoft.com/technet/security/prodtech/WindowsServer2003.mspx).


Enabling the Full 4 GB of RAM

Provisioning Manager will not install either the medium (up to 10,000 phones) or the large (up to 30,000 phones) configuration if Windows 2003 reports that less than 4 GB of memory is installed. There is a known issue with Windows 2003 when working with certain hardware. Even though 4 GB of memory is installed on the system, Windows 2003 reports that there is less than 4 GB of memory installed. For more details, see http://msdn2.microsoft.com/en-us/library/ms791485.aspx.

To enable all 4 GB of RAM on the system, use the following procedure:


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.


Enabling SSL on the Provisioning Manager Server

Secure Socket Layer (SSL) is an application-level protocol that enables secure transactions of data through privacy, authentication, and data integrity. It relies upon certificates, public keys, and private keys.

Provisioning Manager supports SSL between clients and the server. When you start Provisioning Manager, the login page always opens in secure mode, providing secure access between the client browser and the Provisioning Manager server. In secure mode, SSL is used to encrypt the transmission channel between the browser and the server. To use secure mode throughout Provisioning Manager, you must enable SSL.

To enable SSL, you must install Win32 OpenSSL and then configure the Apache server.

Installing OpenSSL and Generating a Certificate


Step 1 On the Provisioning Manager system, install Win32 OpenSSL v0.9.7m in C:\OpenSSL. You can find Win32 OpenSSL at http://www.slproweb.com/products/Win32OpenSSL.html.

Step 2 In a command prompt, go to <Install directory>\httpd\conf.


Note If you accepted the default location during installation, the installation directory is C:\CUPM.


Step 3 In the command prompt, run the following command:

c:\OpenSSL\bin\openssl.exe genrsa -des3 -out server.key 1024

Step 4 A prompt appears, asking for a passphrase. Enter a phrase.

Step 5 Run the following command:

c:\OpenSSL\bin\openssl.exe req -new -x509 -days 365 -key server.key -out server.crt


Note This command assumes the certificate is valid for 365 days. If you need a longer license, enter a higher number of days.


Step 6 At the prompted, enter the passphrase you entered previously. Enter it again.

Step 7 Enter the information for the Distinguished Name fields for the certificate.

Step 8 Run the following command:

copy server.key server.key.orig 

Step 9 Run the following command:

c:\OpenSSL\bin\openssl.exe rsa -in server.key.orig -out server.key

Step 10 Enter the passphrase you used previously. This removes the need to enter the passphrase every time you start Provisioning Manager.


Configuring the Apache Server


Step 1 On the Provisioning Manager system, in the httpd.conf file (located at <install directory>/httpd/conf), uncomment the line LoadModule ssl_module modules/mod_ssl.so.

Step 2 If you upgraded from Provisioning Manager 1.2 you must update the ssl.conf file.
Set @DOCROOT@ to <install directory>/httpd/htdocs (it should be changed in two places).

If this is a new installation, you can skip this step.

Step 3 Restart the Apache2 Windows Service.

Now you can log into Provisioning Manager using HTTPS.



Note When using SSL, remember the following:

The URL for logging in uses HTTPS (For example, https://<host name or IP address>/cupm/Login).

If you upgraded from Provisioning Manager 1.2, the ssl.conf file may be read only. Remove the read only property using Windows Explorer.

By default, port 443 is configured in the ssl.conf file. If you need to change the port number, in the ssl.conf file, change the line Listen 443 to the desired port.

If you want to exclusively run only HTTPS, you must disable the nonsecure HTTP by commenting out the line Listen 80 in the C:\CUPM\httpd\conf\httpd.conf file, and then restart the Apache server.


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.

If Cisco Unity is used in this configuration, configure the Cisco Unified Communications Manager voicemail ports.

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 Accounts Required to Access 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, 6.x, or 7.x

N/A

A Unified Communications Manager user who 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 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.

Before you can create a Call Processor based on a Cisco Unified Communications Manager Express in Provisioning Manager, you must do the following:

Disable the auto-allocation of directory numbers. Do this through the Cisco IOS interface (see Disabling the Auto-Allocation of Directory Numbers and Ephone Auto-Registration).

Disable the ephone auto-registration. You must do this through for Cisco Unified Communications Manager Express 4.0 or later (see Disabling the Auto-Allocation of Directory Numbers and Ephone Auto-Registration).

If you have changed the Rivest, Shamir, and Adelman (RSA) key pair for Secure Shell Version 2 (on the router where Cisco Unified Communications Manager Express resides) to a length less than 512 bits, you must reconfigure the RSA key back to a length equal to or greater than 512 bits. For information on configuring the RSA keys in Secure Shell Version 2, see your router's documentation.

Disabling the Auto-Allocation of Directory Numbers and Ephone Auto-Registration

Do the following configurations 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


Note Provisioning Manager does not support Cisco Unity when it is configured with multiple Cisco Unified Communications Manager clusters.


Before you can create a Unified Message Processor based on Cisco Unity 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 corresponding Cisco Unified Communications Manager.

Create a SQL Server user and password that can be used by Provisioning Manager to access the SQL Server database on Cisco Unity. The SQL Server user requires access to both the Cisco Unity and master databases. See Creating an SQL Server User and Password for Cisco Unity. (Required for Cisco Unity only.)

Verify the TCP/IP port used by Cisco Unity. This port number is required when you create a Unified Message Processor. (Required for Cisco Unity only.)

Define Class of Service and Subscriber templates.

Configure IMAP in Cisco Unity Connection. This is required so that Provisioning Manager can provision email and Unified Messaging Services in Cisco Unity Connection. (Required for Cisco Unity Connection only.)


Note To configure IMAP: on the Cisco Unity Connection system, go to System Settings > External Services > Add New, and fill in all the fields required to add external services.


Creating an SQL Server User and Password for Cisco Unity


Step 1 On the Cisco Unity 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.

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


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 do the following:

If you have changed the RSA key pair for Secure Shell Version 2 (on the router where Cisco Unity Express resides) to a length less than 512 bits, you must reconfigure the RSA key back to a length equal to or greater than 512 bits. For information on configuring the RSA keys in Secure Shell Version 2, see your router's documentation.

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 (see Determining the Service Engine Interface Number for Cisco Unity Express).

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.


Interfaces that Provisioning Manager Uses

Table 2-2 lists the interfaces that Provisioning Manager uses to communicate with the end systems.

Table 2-2 Interfaces that Provisioning Manager Uses 

Call Processor/ Unified Message Processor
Interface

Cisco Unified Communications Manager

AXL and SOAP

Cisco Unified Communications Manager Express

CLI over Telnet and SSH

Cisco Unity

JDBC

Cisco Unity Connection

Webservice API

Cisco Unity Express

CLI over Telnet and SSH


Ports that Provisioning Manager Uses

Before installing Provisioning Manager, make sure that the appropriate ports are available.

Table 2-3 lists the ports that need to be open on the Provisioning Manager system. Table 2-4 lists the ports that need to be open on the firewall between Provisioning Manager and the device.

Table 2-3 Ports Used on the Provisioning Manager System 

Port Numbers
Additional Information

1098

1099

1602

Network Interface and Configuration Engine (NICE). This is configurable during the advanced installation process.

4444

4445

5432

PostgreSQL database. This is configurable during the advanced installation process.

8008

JBoss Application Sever. This is configurable during the advanced installation process.

8009

8083

8093

80

HTTP/Apache Web Server. This is configurable during the advanced installation process.


Table 2-4 Ports Used to Communicate with Other Devices 

Port Numbers
Service Name/Protocols
Application

80

HTTP/Apache Web Server

Cisco Unified Communications Manager.

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.


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 and 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 (default is postgres).

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-3.

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.3 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.3-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 (default is postgres), then click Next.


Note Enter only alphanumeric characters for the password. Do not enter any special characters.


c. Enter a password for the Provisioning Manager administrator user.


Note Provisioning Manager is preconfigured with a permanent administrator account (pmadmin).


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 Provisioning Manager application server that can connect to the PostgreSQL database. This is required if the database or the application is being installed on a separate system.

Username and password for the Windows user that the PostgreSQL database uses—Enter only alphanumeric characters for the password. Do not enter any special characters.


Note If the username already exists on the system, the password entered must be the current password for that user. Also, the Windows user should not have administrator privileges.


Username and password for the PostgreSQL administrator (default is postgres)—Enter only alphanumeric characters for the password. Do not enter any special characters.

Application (JBoss) server name.

Port number for the JBoss application server.

Username and password for the application database user—Enter only enter alphanumeric characters for the password. Do not enter any special characters.

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.3. If you need to clean up a failed upgrade of Provisioning Manager 1.2 to 1.3, see Restoring Provisioning Manager 1.2 If the Provisioning Manager 1.3 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 folder C:\Program Files\Common Files\InstallShield\Universal\common\Gen1.

Delete the Documents and Settings\cupmuser folder.

Remove the Windows user cupmuser (cupmuser is the default name provided during installation). The Windows username 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.2 to Provisioning Manager 1.3

There are two upgrade scenarios; select the procedure that matches your scenario:

Upgrading Provisioning Manager on One System (Application and Database on the Same System)

Upgrading Provisioning Manager on 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 back up your database. For instructions, see Provisioning Manager Database Backup.


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.2 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-3.

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.3 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.3-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, telling you that an upgrade to Provisioning Manager 1.3 will occur. Click Next. 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.

That there are not any unsupported devices configured in Provisioning Manager.


Note For device support information, see the Supported Devices Table for Cisco Unified Provisioning Manager 1.3 at http://www.cisco.com/en/US/products/ps7125/products_device_support_tables_list.html.


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.3 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 Select a directory in which to back up the Provisioning Manager 1.2 data during upgrade. Click Next. The Summary page appears.

Step 10 Click Install.


Note If an error message similar to the following appears, it means that the installation has failed:

C:\CUPM\httpd\conf\httpd.conf exists on this system and it has been modified since instllation. Do you want to remove this file?

Before trying to install Provisioning Manager again, you must clean up the system. See Provisioning Manager Database Backup.


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 After upgrading Provisioning Manager, you must synchronize all of your Unified Message Processors in Provisioning Manager before placing any orders for a processor.



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 on 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 Back up the Provisioning Manager 1.2 database. For information, see Provisioning Manager Database Backup.

Step 2 Upgrade the Provisioning Manager 1.2 database to 1.3. The installation program will only take you through the applicable 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.2 application to 1.3. The installation program will only take you through the applicable upgrade screens. If you need additional information, see Upgrading Provisioning Manager on One System (Application and Database on the Same System).


Note After upgrading Provisioning Manager, you must synchronize all of your Unified Message Processors in Provisioning Manager before placing any orders for a processor.



Provisioning Manager Database Backup

There are two backup scenarios; select the procedure that matches your scenario:

Backing up on a single machine; see Backing Up the Single-Machine Provisioning Manager Database.

Backing up for a distributed scenario; see Backing Up Provisioning Manager on a Distributed Database.


Note When backing up files, you should place the files on a different file server. Also, you should burn the backup data onto a CD.


Backing Up the Single-Machine Provisioning Manager Database

This procedure requires that you have administrator-level access to the Provisioning Manager database (the PostgreSQL database).


Step 1 On the Provisioning Manager system, stop the following services:

Apache

cupm JBossService

cupm NiceService

a. On the Windows desktop, select Start > Control Panel > Administrative Tools > Services.

b. Right-click each of the services and click Stop.

Step 2 On the Windows desktop, select Start > All Programs > PostgreSQL8.2 > Command Prompt. A command prompt opens in the <Install directory>\pgsql\bin directory.


Note If you accepted the default location during installation, the installation directory is C:\CUPM.


Step 3 In the command prompt, run the following command and enter the PostgreSQL administrator password when prompted:

pg_dumpall -o -U<username> > <directory>\<backup file name>

where:

<username> is the username of the PostgreSQL administrator. If you accepted the default, the administrator username is postgres.

<directory> is an existing directory.

<backup file name> is a filename that does not currently exist.


Note Enter the password each time that you are prompted.


Use this command to back up the database. The command tells Provisioning Manager to store the database information in a file.

Step 4 If you are backing up for the same installation, proceed to the next step. If you are backing up for a new installation, make backup copies as described in this step.

In a backup folder, make copies of the following files and directories:

<Installation directory>\install.log

<Installation directory>\sep\dfc.properties

<Installation directory>\sep\dfc.keystore

<Installation directory>\jboss-4.0.3SP1\server\cupm\conf\login-config.xml

Step 5 Start the following services:

Apache

cupm JBossService

cupm NiceService

a. On the Windows desktop, select Start > Control Panel > Administrative Tools > Services.

b. Right-click each of the services and click Start.


Backing Up Provisioning Manager on a Distributed Database

This procedure requires that you have administrator-level access to the Provisioning Manager database (the PostgreSQL database).


Step 1 On the system where Provisioning Manager is running, stop the following services:

Apache

cupm JBossService

cupm NiceService

a. On the Windows desktop where Provisioning Manager is running, select Start > Control Panel > Administrative Tools > Services.

b. Right-click each of the services and click Stop.

Step 2 On the Windows desktop where the Provisioning Manager database is running, select Start > All Programs > PostgreSQL8.2 > Command Prompt. A command prompt opens in the <Installation directory>\pgsql\bin directory.


Note If you accepted the default location during installation, the installation directory is C:\CUPM.


Step 3 In the command prompt, run the following command and enter the PostgreSQL administrator password when prompted:

pg_dumpall -o -U<username> > <directory>\<backup file name>

where:

<username> is the username of the PostgreSQL administrator. If you accepted the default, the administrator username is postgres.

<directory> is an existing directory.

<backup file name> is a filename that does not currently exist.


Note Enter the password each time that you are prompted.


This command is used to backup the database, by storing the database information in a file.

Step 4 If you are backing up for the same installation, proceed to the next step. If you are backing up for a new installation, either with the same IP address or a new one, do the following. On the machine where Provisioning Manager is running, in a backup folder, make copies of the following files and directories:

<Installation directory>\install.log

<Installation directory>\sep\dfc.properties

<Installation directory>\sep\dfc.keystore

<Installation directory>\jboss-4.0.3SP1\server\cupm\conf\login-config.xml

Step 5 Start the following services:

Apache

cupm JBossService

cupm NiceService

a. On the Windows desktop, select Start > Control Panel > Administrative Tools > Services.

b. Right-click each of the services and click Start.


Restoring Provisioning Manager 1.2 If the Provisioning Manager 1.3 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.2 (see Cleaning Up the Old Installation).

Restore Provisioning Manager 1.2 (see Restoring Provisioning Manager 1.2).

Cleaning Up the Old Installation


Step 1 Uninstall the Provisioning Manager installation. Depending upon where the installation failed, the installed application may appear as Provisioning Manager 1.2 or Provisioning Manager 1.3. 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. Uninstall Postgres 8.2 if it still exists. If PostgreSQL 8.2 is listed under Windows Control Panel > Add or Remove Programs, click Remove to uninstall it.

b. 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.


c. 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\.

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 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.2

There are two restore scenarios; select the procedure that matches your scenario:

Restoring on a single machine, see Restoring the Single-Machine Provisioning Manager Database.

Restoring for a distributed scenario, see Restoring Provisioning Manager for a Distributed Database.

Restoring the Single-Machine Provisioning Manager Database

If you are restoring to a new installation, have the system with the new installation up and running before beginning this procedure.

This procedure requires that you have administrator-level access to the Provisioning Manager database (the PostgreSQL database).

Before You Begin

If you are restoring the database on a new system, you must verify that the following ports are not being used by another application:

dfc.jboss.port=8008

dfc.postgres.port=5432

dfc.nice.rmi.registry.internal.port=1602

dfc.webport=80

If a port is being used by another application, you must change the port number to a vacant port. These settings are defined in the <Installation directory>\sep\dfc.properties file. (If you accepted the default location during installation, the installation directory is C:\CUPM.)


Step 1 Stop Provisioning Manager services (for information on which services to stop, see Step 1 ).

Step 2 On the Windows desktop, select Start > All Programs > PostgreSQL8.2 > Command Prompt.

A command prompt opens in the <Installation directory>\pgsql\bin folder.


Note If you accepted the default location during installation, the installation directory is C:\CUPM.


Step 3 To enter the PostgreSQL prompt, run the following command and enter the PostgreSQL administrator password for the current installation when prompted:

psql.exe -U<username>

where <username> is the username of the PostgreSQL administrator. If you accepted the default, the administrator username is postgres.

Step 4 Before restoring the database, you must drop the database name and role. In the command prompt, run the following commands exactly as shown, one at a time and in the following order:

DROP DATABASE cupm;

where cupm is the database name to be removed.

Expected output: DROP DATABASE

DROP ROLE <rolemame>;

where <rolename> is the username for the SEP database user. If you accepted the default, the username is cupm.

Expected output: DROP ROLE

ALTER ROLE <username> WITH PASSWORD `<password>';

where username is the username of the PostgreSQL administrator user, and <password> should be the password that was set for the PostgreSQL administrator with backed-up data. If you accepted the default administrator username, the username is postgres.

Expected output: ALTER ROLE

Step 5 Enter \q to quit the PostgreSQL prompt.

Step 6 From the command line, run the following command; when prompted, enter the password that was set in the previous step for the PostgreSQL user:

psql.exe -U<username> -d postgres < <directory>\<file name to be restored from>

where <username> is the username of the PostgreSQL administrator. If you accepted the default, the administrator username is postgres.

This command restores the database.

Step 7 Copy the following backed-up files to the location where they were backed up from:

<Installation directory>\install.log

<Installation directory>\sep\dfc.properties

<Installation directory>\sep\dfc.keystore

<Installation directory>\jboss-4.0.3SP1\server\cupm\conf\login-config.xml

Step 8 Start the following services:

Apache

cupm JBossService

cupm NiceService

a. On the Windows desktop, select Start > Control Panel > Administrative Tools > Services.

b. Right-click each of the services and click Start.


Restoring Provisioning Manager for a Distributed Database

If you are restoring to a new installation, either with the same or a new IP address, have the system with the new installation up and running before beginning this procedure.

This procedure requires that you have administrator-level access to the Provisioning Manager database (the PostgreSQL database).

Before You Begin

If you are restoring the database on a new system, you must verify that the following ports are not being used by another application:

dfc.jboss.port=8008

dfc.postgres.port=5432

dfc.nice.rmi.registry.internal.port=1602

dfc.webport=80

If a port is being used by another application, you must change the port number to a vacant port. These settings are defined in the <Installation directory>\sep\dfc.properties file. (If you accepted the default location during installation, the installation directory is C:\CUPM.)

Also, you will need to change the system name in one of the following settings:

dfc.postgres.host=<system name> (If the database is on one system.)

dfc.postgres.hostlist=<system names> (If the database is on multiple systems.)


Step 1 On the Provisioning Manager application system, stop the Provisioning Manager services (for information on which services to stop, see Step 1 ).

Step 2 On the Windows desktop where the Provisioning Manager database is running, select Start > All Programs > PostgreSQL8.2 > Command Prompt.

A command prompt opens in the <Installation directory>\pgsql\bin folder.


Note If you accepted the default location during installation, the installation directory is C:\CUPM.


Step 3 To enter the PostgreSQL prompt, run the following command and enter the PostgreSQL administrator password for the current installation when prompted:

psql.exe -U<username>

where <username> is the username of the PostgreSQL administrator. If you accepted the default, the administrator username is postgres.

Step 4 Before restoring the database, you must drop the database name and role. In the command prompt, run the following commands exactly as shown, one at a time and in the following order:

DROP DATABASE cupm;

where cupm is the database name to be removed.

Expected output: DROP DATABASE

DROP ROLE <rolemame>;

where <rolename> is the username for the SEP database user. If you accepted the default, the username is cupm.

Expected output: DROP ROLE

ALTER ROLE <username> WITH PASSWORD `<password>';

where <username> is the username of the PostgreSQL administrator, and <password> is the password that was set for the PostgreSQL administrator with backed-up data. If you accepted the default administrator username, the username is postgres.

Expected output: ALTER ROLE

Step 5 Enter \q to quit the PostgreSQL prompt.

Step 6 From the command line, run the following command; when prompted, enter the password that was set in the previous step for the PostgreSQL user:

psql.exe -U<username> -d postgres < <directory>\<file name to be restored from>

where <username> is the username of the PostgreSQL administrator. If you accepted the default, the administrator username is postgres.

This command restores the database.

Step 7 Copy the following backed-up files to the machine where the Provisioning Manager application is running:

<Installation directory>\install.log

<Installation directory>\sep\dfc.properties

<Installation directory>\sep\dfc.keystore

<Installation directory>\jboss-4.0.3SP1\server\cupm\conf\login-config.xml

Step 8 On the system where the Provisioning Manager application is running, start the following services:

Apache

cupm JBossService

cupm NiceService

a. On the Windows desktop, select Start > Control Panel > Administrative Tools > Service.

b. Right-click each of the services and click Start.


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.