Cisco Prime Service Catalog 11.1.1 Virtual Appliance Quick Start Guide
Contents
- Introduction
- Overview
- Before You Begin
- System Requirements
- Licensing
- Preparing the Virtual Appliance for Deployment
- Installing Prime Service Catalog Virtual Appliance
- Installing Prime Service Catalog Virtual Appliance for a Complete (All-in-One) Setup
- Installing Prime Service Catalog Virtual Appliance for a Distributed Setup
- Installing the Database Node
- Installing the Prime Service Catalog Node
- Installing the Puppet Node
- Installing the Orchestration Node
- Installing Prime Service Catalog Cluster Node
- Performing Post Installation Tasks
- Launching Shell Menu
- Configuring SMTP
- Configuring Proxy Server Settings
- Configuring Prime Service Catalog Virtual Appliance With Cisco ONE Enterprise Cloud Suite
- Upgrading the Cisco Prime Service Catalog Virtual Appliance
- Backing up the Database on Cisco Prime Service Catalog Virtual Appliance 11.0 or 11.1
- Exporting Prime Service Catalog Schema and Importing to the External Oracle Database
- Upgrading to the Latest Virtual Appliance Database
- Performing Post-upgrade Tasks for the Virtual Appliance
- Uninstalling Prime Service Catalog
- Removing Virtual Appliance
- Limitations
- Additional Configuration for Firefox ESR 31.x Browser
- HTTP Server Configuration
Introduction
Overview
Cisco Prime Service Catalog software is a self-service portal to order and manage any type of IT services from the data center to desktop. You can also order Infrastructure as a Service (IaaS) such as virtual machines, fenced containers, and VACS (if integrated with UCSD), and use Prime Service Catalog for lifecycle management of these entities.
Cisco Prime Service Catalog Virtual Appliance (OVF) package enables you to deploy Cisco Prime Service Catalog product as a Virtual Machine.
The Virtual Appliance comes with the following pre-installed and pre-configured software:
Red Hat Enterprise Linux Operating System, version 7.1
Red Hat OpenJDK , version 1.7.0_79
Apache HTTP Server , version 2.4.6
WildFly Application Server , version 8.2.0. Final
Oracle 12c Database Enterprise Edition , version 12.1.0.2
Puppet Master , version 3.8.1
Rabbit MQ, version 3.3.5
Prime Service Catalog (with Orchestration Service, and contents for applications), version 11.1.1
The Cisco Prime Service Catalog Quick Start Guide provides information on deploying and configuring Prime Service Catalog Virtual Appliance. For more information about using Prime Service Catalog, see the Cisco Prime Service Catalog 11.1.1 User Guide.
Contents
- Introduction
- Overview
- Before You Begin
- System Requirements
- Licensing
- Preparing the Virtual Appliance for Deployment
- Installing Prime Service Catalog Virtual Appliance
- Installing Prime Service Catalog Virtual Appliance for a Complete (All-in-One) Setup
- Installing Prime Service Catalog Virtual Appliance for a Distributed Setup
- Installing the Database Node
- Installing the Prime Service Catalog Node
- Installing the Puppet Node
- Installing the Orchestration Node
- Installing Prime Service Catalog Cluster Node
- Performing Post Installation Tasks
- Launching Shell Menu
- Configuring SMTP
- Configuring Proxy Server Settings
- Configuring Prime Service Catalog Virtual Appliance With Cisco ONE Enterprise Cloud Suite
- Upgrading the Cisco Prime Service Catalog Virtual Appliance
- Backing up the Database on Cisco Prime Service Catalog Virtual Appliance 11.0 or 11.1
- Exporting Prime Service Catalog Schema and Importing to the External Oracle Database
- Upgrading to the Latest Virtual Appliance Database
- Performing Post-upgrade Tasks for the Virtual Appliance
- Uninstalling Prime Service Catalog
- Removing Virtual Appliance
- Limitations
- Additional Configuration for Firefox ESR 31.x Browser
- HTTP Server Configuration
Before You Begin
System Requirements
The OVF file for Prime Service Catalog 11.1.1 Virtual Appliance can be deployed only in VMware vSphere version 5.x. To deploy the Prime Service Catalog OVF file, you need to open a vSphere Client and connect it to your VMware vCenter Server 5.x.
Make sure that your VMware vCenter Server has enough resources to accommodate the Virtual Appliance: 4 CPU, 8 GB of memory, 100 GB of disk space.
Note
If you plan to deploy the Cisco Prime Service Catalog Virtual Appliance in Complete mode (all components in a single VM), we recommend increasing the VM's CPU count to 8, and memory to 16 GB.
An SMTP server is highly desirable but not required. After deploying the OVF, you can enter the SMTP server setting via the Shell Menu, as described in the Installation Instructions. The SMTP server that you use must listen to port 25, and should not require authentication.
Licensing
Prime Service Catalog is part of the Cisco ONE Enterprise Cloud Suite. Cisco ONE Enterprise Cloud Suite is licensed on a per server basis.
Prime Service Catalog is also licensed to manage desktop, communications, bring your own devices, and other end-user service requests through a catalog of workplace services for employees. When licensed for workplace services, the Prime Service Catalog is licensed on a per user basis.
These use cases are licensed separately. The licenses are determined as follows:
Prime Service Catalog per server edition license is based on the number of servers managed by the product and Cisco ONE Enterprise Cloud Suite includes per server license.
Prime Service Catalog per user edition license is based on the number of users who are given permission to access the product.
If you choose to use Prime Service Catalog to manage both data center and workplace use cases you need to license both the per user and per server options. You may also discuss the Enterprise License Agreement (ELA) with your account manager.
Prime Service Catalog is also an integral part of Cisco Intelligent Automation for Cloud.
For more information about licensing contact your account manager.
Contents
- Introduction
- Overview
- Before You Begin
- System Requirements
- Licensing
- Preparing the Virtual Appliance for Deployment
- Installing Prime Service Catalog Virtual Appliance
- Installing Prime Service Catalog Virtual Appliance for a Complete (All-in-One) Setup
- Installing Prime Service Catalog Virtual Appliance for a Distributed Setup
- Installing the Database Node
- Installing the Prime Service Catalog Node
- Installing the Puppet Node
- Installing the Orchestration Node
- Installing Prime Service Catalog Cluster Node
- Performing Post Installation Tasks
- Launching Shell Menu
- Configuring SMTP
- Configuring Proxy Server Settings
- Configuring Prime Service Catalog Virtual Appliance With Cisco ONE Enterprise Cloud Suite
- Upgrading the Cisco Prime Service Catalog Virtual Appliance
- Backing up the Database on Cisco Prime Service Catalog Virtual Appliance 11.0 or 11.1
- Exporting Prime Service Catalog Schema and Importing to the External Oracle Database
- Upgrading to the Latest Virtual Appliance Database
- Performing Post-upgrade Tasks for the Virtual Appliance
- Uninstalling Prime Service Catalog
- Removing Virtual Appliance
- Limitations
- Additional Configuration for Firefox ESR 31.x Browser
- HTTP Server Configuration
Preparing the Virtual Appliance for Deployment
Procedure
Contents
- Introduction
- Overview
- Before You Begin
- System Requirements
- Licensing
- Preparing the Virtual Appliance for Deployment
- Installing Prime Service Catalog Virtual Appliance
- Installing Prime Service Catalog Virtual Appliance for a Complete (All-in-One) Setup
- Installing Prime Service Catalog Virtual Appliance for a Distributed Setup
- Installing the Database Node
- Installing the Prime Service Catalog Node
- Installing the Puppet Node
- Installing the Orchestration Node
- Installing Prime Service Catalog Cluster Node
- Performing Post Installation Tasks
- Launching Shell Menu
- Configuring SMTP
- Configuring Proxy Server Settings
- Configuring Prime Service Catalog Virtual Appliance With Cisco ONE Enterprise Cloud Suite
- Upgrading the Cisco Prime Service Catalog Virtual Appliance
- Backing up the Database on Cisco Prime Service Catalog Virtual Appliance 11.0 or 11.1
- Exporting Prime Service Catalog Schema and Importing to the External Oracle Database
- Upgrading to the Latest Virtual Appliance Database
- Performing Post-upgrade Tasks for the Virtual Appliance
- Uninstalling Prime Service Catalog
- Removing Virtual Appliance
- Limitations
- Additional Configuration for Firefox ESR 31.x Browser
- HTTP Server Configuration
Installing Prime Service Catalog Virtual Appliance
Using Cisco Prime Service Catalog 11.1.1 Virtual Appliance (OVF) package, you can deploy Cisco Prime Service Catalog in two modes:
- Complete (All in One): This type of OVF installation performs a streamlined installation using default settings. All the Virtual Appliance components- Prime Service Catalog application, Prime Service Catalog Database, Puppet Master, and the Orchestration components are installed on a single appliance. For installation steps, see Installing Prime Service Catalog Virtual Appliance for a Complete (All-in-One) Setup.
- Distributed: This type of OVF installation will install all the Virtual Appliance components on different nodes. The nodes should be deployed in the same order as shown in the Virtual Appliance prompt. You can also add additional Prime Service Catalog nodes to set up a cluster for failover. For installation steps, see Installing Prime Service Catalog Virtual Appliance for a Distributed Setup.
Installing Prime Service Catalog Virtual Appliance for a Complete (All-in-One) Setup
Before You BeginProcedure
- Prepare the Virtual Appliance for deployment. For more information, see Preparing the Virtual Appliance for Deployment.
- After deploying the VA in your vCenter Server, make sure that you edit the VM and the change the specifications as:
The installation of the Prime Service Catalog Virtual Appliance is completed.
After the installation is complete, the following configurations are performed automatically: These configurations can be verified in .What to Do Next
Proceed to the Post Installation Tasks section to perform the additional configuration tasks, which are required if you plan to use more advanced features of Prime Service Catalog.
Installing Prime Service Catalog Virtual Appliance for a Distributed Setup
In the Distributed setup of OVF installation, all the Virtual Appliance components are installed on different nodes. The nodes should be deployed in the same order as mentioned below. You can also add additional Prime Service Catalog nodes to set up a cluster for failover.
Installing the Database Node
Before You BeginProcedure
Prepare the Virtual Appliance for deployment. For more information, see Preparing the Virtual Appliance for Deployment.
What to Do Next
Proceed to the Installing the Prime Service Catalog Node.
Installing the Prime Service Catalog Node
Before You BeginProcedure
Prepare the Virtual Appliance for deployment. For more information, see Preparing the Virtual Appliance for Deployment.
Set up the database node and ensure that it is up and running. For information on setting up a database node, see Installing Prime Service Catalog Database Node.
What to Do Next
Proceed to the Installing the Puppet Node.
Installing the Puppet Node
Before You BeginProcedure
Prepare the Virtual Appliance for deployment. For more information, see Preparing the Virtual Appliance for Deployment .
Make sure the database and Prime Service Catalog nodes are up and running.
What to Do Next
Proceed to the Installing the Orchestration Node.
Installing the Orchestration Node
Before You BeginProcedure
Prepare the Virtual Appliance for deployment. For more information, see Preparing the Virtual Appliance for Deployment .
Make sure that the database, Prime Service Catalog, and the Puppet Master nodes are up and running.
Note
Make sure that the root user is enabled on both the Prime Service Catalog and the Puppet Master nodes. To enable root user, use the Shell Menu called Manage Users on each Node. For information on Shell Menu, see Launching Shell Menu.What to Do Next
Proceed to the Installing Prime Service Catalog Cluster Node section if you want to configure a clustered environment for Prime Service Catalog .
Installing Prime Service Catalog Cluster Node
Use the procedure detailed here only if you want to configure a clustered environment for Prime Service Catalog. In this section, you will deploy the OVF file for a second Prime Service Catalog Node, that will act as a secondary cluster node. The first Prime Service Catalog Node that you already have will act as the primary cluster node.Before You BeginProcedure
Prepare the Virtual Appliance for deployment. For more information, see Preparing the Virtual Appliance for Deployment.
Set up the database node and ensure that it is up and running. For information on setting up a database node, see Installing Prime Service Catalog Database Node.
Install the Prime service Catalog node and ensure that it is up and running. For more on installing a Prime Service Catalog node, see Installing Prime Service Catalog Node.
Make sure that root login is enabled on the Prime Service Catalog Primary node. You can enable the root login through shell admin menu. For more information, see Launching Shell Menu.
Make sure that all the Firewall ports for services such as Service Link, Domain Controller, and Prime Service Catalog Application Management Port are open. You can enable these ports through shell admin menu. For more information on Shell Menu, see Launching Shell Menu.
Step 1 Open the VM's Console in your vSphere Client. The VM console will display the following prompts:
Step 2 The Prime Service Catalog Node that you just deployed is the secondary cluster node. You must go back to the primary cluster node, and add the information of the second Prime Service Catalog Node to the load balancer. To do this, log in as shelladmin user on the first Prime Service Catalog Node, and choose the Manage Cluster shell menu. For more information on how to use the shell menu, see Launching Shell Menu.
What to Do Next
Proceed to Post Installation Tasks section to perform the additional configuration tasks, which are required if you plan to use more advanced features of Prime Service Catalog .
Contents
- Introduction
- Overview
- Before You Begin
- System Requirements
- Licensing
- Preparing the Virtual Appliance for Deployment
- Installing Prime Service Catalog Virtual Appliance
- Installing Prime Service Catalog Virtual Appliance for a Complete (All-in-One) Setup
- Installing Prime Service Catalog Virtual Appliance for a Distributed Setup
- Installing the Database Node
- Installing the Prime Service Catalog Node
- Installing the Puppet Node
- Installing the Orchestration Node
- Installing Prime Service Catalog Cluster Node
- Performing Post Installation Tasks
- Launching Shell Menu
- Configuring SMTP
- Configuring Proxy Server Settings
- Configuring Prime Service Catalog Virtual Appliance With Cisco ONE Enterprise Cloud Suite
- Upgrading the Cisco Prime Service Catalog Virtual Appliance
- Backing up the Database on Cisco Prime Service Catalog Virtual Appliance 11.0 or 11.1
- Exporting Prime Service Catalog Schema and Importing to the External Oracle Database
- Upgrading to the Latest Virtual Appliance Database
- Performing Post-upgrade Tasks for the Virtual Appliance
- Uninstalling Prime Service Catalog
- Removing Virtual Appliance
- Limitations
- Additional Configuration for Firefox ESR 31.x Browser
- HTTP Server Configuration
Performing Post Installation Tasks
This section consists of the following sub-sections:
Launching Shell Menu
The Shell Menu allows you to perform various administrative tasks for the Virtual Appliance such as configuring SMTP setting, configuring Proxy server, changing passwords, starting and stopping services on the Linux operating system, etc.
Login to the Virtual Appliance as the shelladmin user. You can do this via the VM Console in your vSphere Client, or via an SSH connection to the IP address of the VM. On the Login Prompt, type shelladmin for the user name, and type the password value that you provided in Step 1d of the Installing Prime Service Catalog section. Once logged in, you will see the Shell Menu depending upon the type of installation. Following is the list of commands that appears in a Shell Menu for different types of installation. For details on these prompts, see the table below.
Complete (All-in-One) Installation Shell Menu OptionsDatabase Node Shell Menu OptionsPrime Service Catalog Node Shell Menu OptionsPuppet Node Shell Menu OptionsOrchestration Node Shell Menu OptionsThe following table contains the descriptions of all the menu items available on the Shell Menu:
Note
For some of the menu items, you may be presented with a list of choices to select. If you don’t see any choices that you want and you want to get back to the previous menu, press Control-C (Ctrl+C).
Menu
Description
Manage Users
This menu option allows you to enable or disable root access to Linux, and to set the password for the root user. It also allows you to change the System Passwords for the Virtual Appliance.
Display Services Status
This menu option displays the status (running or stopped) of all services on the VM that are related to the Prime Service Catalog.
Stop Services
This menu option allows you stop individual services on the VM, such as, Prime Service Catalog Services, Orchestration Services, Prime Service Catalog, Prime Service Link, and so on.
Start Services
This menu option allows you to start individual services on the VM.
Manage Databases
This menu option allows you to perform database backup, restore, upgrade previous version of Prime Service Catalog database, execute custom SQL on database, and update the data source.
Manage Firewall
This menu option allows you to open or close the TCP port numbers for certain services.
Manage Puppet Master
This menu option allows you to view the Puppet Master certificate.
View/Configure Network Interface
This menu option allows you to view the existing network information, and to configure the proxy server settings.
Note: The Virtual Appliance is not required to have Internet access. If you want to have Internet access for the Virtual Appliance, and your network requires your VM to go through a proxy server to connect to the internet, use this menu to configure the proxy settings on your VM.
View/Configure SMTP
This menu option allows you to configure the SMTP server setting.
View Logs
This menu option allows you to view the runtime logs of various services on the VM.
Show Version
This menu option displays the version information for the Prime Service Catalog product and its related components.
Apply Patch
This menu option allows you to install a patch for the appliance, should there be a patch released by Cisco in the future for this version of the Virtual Appliance.
Login as Root
This menu option allows you to login to Linux as the root user. You must first enable the root access via Shell Menu Manage Users option.
Shutdown Appliance
This menu option shuts down the Linux operating system and power off the VM.
Reboot Appliance
This menu option reboots the Linux operating system.
Quit
This menu option logs you out of Linux and returns you to the Linux Login Prompt.
Configuring SMTP
Configuring Proxy Server Settings
ProcedureIf your VM must go through a proxy server to connect to the internet, do the following on the Shell Menu:
Contents
- Introduction
- Overview
- Before You Begin
- System Requirements
- Licensing
- Preparing the Virtual Appliance for Deployment
- Installing Prime Service Catalog Virtual Appliance
- Installing Prime Service Catalog Virtual Appliance for a Complete (All-in-One) Setup
- Installing Prime Service Catalog Virtual Appliance for a Distributed Setup
- Installing the Database Node
- Installing the Prime Service Catalog Node
- Installing the Puppet Node
- Installing the Orchestration Node
- Installing Prime Service Catalog Cluster Node
- Performing Post Installation Tasks
- Launching Shell Menu
- Configuring SMTP
- Configuring Proxy Server Settings
- Configuring Prime Service Catalog Virtual Appliance With Cisco ONE Enterprise Cloud Suite
- Upgrading the Cisco Prime Service Catalog Virtual Appliance
- Backing up the Database on Cisco Prime Service Catalog Virtual Appliance 11.0 or 11.1
- Exporting Prime Service Catalog Schema and Importing to the External Oracle Database
- Upgrading to the Latest Virtual Appliance Database
- Performing Post-upgrade Tasks for the Virtual Appliance
- Uninstalling Prime Service Catalog
- Removing Virtual Appliance
- Limitations
- Additional Configuration for Firefox ESR 31.x Browser
- HTTP Server Configuration
Configuring Prime Service Catalog Virtual Appliance With Cisco ONE Enterprise Cloud Suite
Procedure
Contents
- Introduction
- Overview
- Before You Begin
- System Requirements
- Licensing
- Preparing the Virtual Appliance for Deployment
- Installing Prime Service Catalog Virtual Appliance
- Installing Prime Service Catalog Virtual Appliance for a Complete (All-in-One) Setup
- Installing Prime Service Catalog Virtual Appliance for a Distributed Setup
- Installing the Database Node
- Installing the Prime Service Catalog Node
- Installing the Puppet Node
- Installing the Orchestration Node
- Installing Prime Service Catalog Cluster Node
- Performing Post Installation Tasks
- Launching Shell Menu
- Configuring SMTP
- Configuring Proxy Server Settings
- Configuring Prime Service Catalog Virtual Appliance With Cisco ONE Enterprise Cloud Suite
- Upgrading the Cisco Prime Service Catalog Virtual Appliance
- Backing up the Database on Cisco Prime Service Catalog Virtual Appliance 11.0 or 11.1
- Exporting Prime Service Catalog Schema and Importing to the External Oracle Database
- Upgrading to the Latest Virtual Appliance Database
- Performing Post-upgrade Tasks for the Virtual Appliance
- Uninstalling Prime Service Catalog
- Removing Virtual Appliance
- Limitations
- Additional Configuration for Firefox ESR 31.x Browser
- HTTP Server Configuration
Upgrading the Cisco Prime Service Catalog Virtual Appliance
You can upgrade from 11.0 to 11.1.1 and 11.1 to 11.1.1. Only these two upgrade paths are supported.
To upgrade to Cisco Prime Service Catalog Virtual Appliance 11.1.1, you must perform a migration process rather than an in-place upgrade. This is because many third-party components have changed in version 11.1.1, such as the Operating System, OpenStack, RabbitMQ, Orchestration, and so on. Therefore, you must deploy a new 11.1.1 virtual appliance prior to migrating the existing 11.0 or 11.1 virtual appliance. For instructions to deploy Cisco Prime Service Catalog Virtual Appliance 11.1.1, see Installing Prime Service Catalog Virtual Appliance.
At a high level, the upgrade procedures are as follows:
Table 1 High-Level Upgrade Procedures Step 1
Disable the UCS Director automatic polling flag. This setting should be disabled on the Prime Service Catalog 11.0 or 11.1 virtual appliance set up .
Go to Administration > Settings and disable the UCSD Scheduler option.
Step 2
Back up the database on 11.0 or 11.1 virtual appliance.
See Backing Up the Database on 11.0 or 11.1 Virtual Appliance
Step 3
Installing a new 11.1.1 Virtual Appliance.
Step 4
Upgrade the database from 11.0 or 11.1 virtual appliance to 11.1.1 virtual appliance. You can either manually copy the database from the backup in Step 2 or you can let the system copy it from the remote location using the shell menu option.
Step 5
Perform the post upgrade steps to complete the upgrade/migration process.
Backing up the Database on Cisco Prime Service Catalog Virtual Appliance 11.0 or 11.1
Procedure
What to Do Next
Install the 11.1.1 virtual appliance. For more information, see Installing Prime Service Catalog Virtual Appliance for 11.1.
Exporting Prime Service Catalog Schema and Importing to the External Oracle Database
Procedure
Step 1 Back up the database. For detailed procedure, see section Backing up the Database on Cisco Prime Service Catalog Virtual Appliance 11.0 or 11.1. Step 2 Login as the root user on the Prime Service Catalog Virtual Appliance. Step 3 Go to the Oracle Backup Directory by executing the following command: cd /opt/cisco/.backups/oracle/cpscuserStep 4 Execute the following command to copy the backup files from previous Virtual Appliance to the external Oracle database: scp CPSCUSER_backup_<timestamp>.dmp root@{IP_of_external oracle database}:/<external oracle directory>Step 5 Enter the password of the external oracle database. Step 6 Execute the following command on the external oracle to create the directory in the external oracle database by logging in as system user: SQL> create or replace directory CPSC_BACKUPS as ‘opt/cisco/.backups/oracle/cpscuser’Step 7 Execute the following command on the external oracle to verify the location of the dump file in the specified directory: SQL> select directory_name,directory_path from dba_directoriesStep 8 Execute the following command on the external oracle to import the backup files: impdp <systemuser>_schemas=cpscuser directory=CPSC_BACKUPS dumpfile=CPSCUSER_backup_<timestamp>.dmp
Upgrading to the Latest Virtual Appliance Database
Before You BeginProcedure
- Make sure the root user is enabled on the database node. From the Shell Menu, select .
Make sure the old database files are backed up. For more information on backing the old database, see Backing Up the Database on 11.0 Virtual Appliance.
Note
In case of distributed set up, these instructions should be executed only on the Database Node.
What to Do Next
Perform the post upgrade steps to complete the upgrade/migration process. For more information, see Performing the Post-upgrade Tasks.
Performing Post-upgrade Tasks for the Virtual Appliance
Procedure
Contents
- Introduction
- Overview
- Before You Begin
- System Requirements
- Licensing
- Preparing the Virtual Appliance for Deployment
- Installing Prime Service Catalog Virtual Appliance
- Installing Prime Service Catalog Virtual Appliance for a Complete (All-in-One) Setup
- Installing Prime Service Catalog Virtual Appliance for a Distributed Setup
- Installing the Database Node
- Installing the Prime Service Catalog Node
- Installing the Puppet Node
- Installing the Orchestration Node
- Installing Prime Service Catalog Cluster Node
- Performing Post Installation Tasks
- Launching Shell Menu
- Configuring SMTP
- Configuring Proxy Server Settings
- Configuring Prime Service Catalog Virtual Appliance With Cisco ONE Enterprise Cloud Suite
- Upgrading the Cisco Prime Service Catalog Virtual Appliance
- Backing up the Database on Cisco Prime Service Catalog Virtual Appliance 11.0 or 11.1
- Exporting Prime Service Catalog Schema and Importing to the External Oracle Database
- Upgrading to the Latest Virtual Appliance Database
- Performing Post-upgrade Tasks for the Virtual Appliance
- Uninstalling Prime Service Catalog
- Removing Virtual Appliance
- Limitations
- Additional Configuration for Firefox ESR 31.x Browser
- HTTP Server Configuration
Uninstalling Prime Service Catalog
Removing Virtual Appliance
Procedure
Contents
- Introduction
- Overview
- Before You Begin
- System Requirements
- Licensing
- Preparing the Virtual Appliance for Deployment
- Installing Prime Service Catalog Virtual Appliance
- Installing Prime Service Catalog Virtual Appliance for a Complete (All-in-One) Setup
- Installing Prime Service Catalog Virtual Appliance for a Distributed Setup
- Installing the Database Node
- Installing the Prime Service Catalog Node
- Installing the Puppet Node
- Installing the Orchestration Node
- Installing Prime Service Catalog Cluster Node
- Performing Post Installation Tasks
- Launching Shell Menu
- Configuring SMTP
- Configuring Proxy Server Settings
- Configuring Prime Service Catalog Virtual Appliance With Cisco ONE Enterprise Cloud Suite
- Upgrading the Cisco Prime Service Catalog Virtual Appliance
- Backing up the Database on Cisco Prime Service Catalog Virtual Appliance 11.0 or 11.1
- Exporting Prime Service Catalog Schema and Importing to the External Oracle Database
- Upgrading to the Latest Virtual Appliance Database
- Performing Post-upgrade Tasks for the Virtual Appliance
- Uninstalling Prime Service Catalog
- Removing Virtual Appliance
- Limitations
- Additional Configuration for Firefox ESR 31.x Browser
- HTTP Server Configuration
Limitations
Additional Configuration for Firefox ESR 31.x Browser
If you use the Firefox ESR 31.x browser and have problem connecting to the Prime Service Catalog URL, you may need to perform the configuration settings for your Firefox as described in this section.Procedure
HTTP Server Configuration
The mod_evasive module of the HTTP server in the Virtual Appliance is disabled by default, to prevent overly aggressive DDOS protection that causes the 403 Forbidden error in real sessions. Users who want to turn it back on should research and understand how to tune this module for the HTTP server.
Copyright © 2016, Cisco Systems, Inc. All rights reserved.