The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The Cisco Prime Service Catalog product requires an OLTP database, which is referred to as the ServiceCatalog database.The ServiceCatalog database can be manually created by the DBA prior to executing the Cisco Prime Service Catalog installer, or automatically created by the installer if the user selects the "Create Database" option on the installation wizard. The following sub-sections contain the manual instructions for creating the ServiceCatalog database on either Oracle or SQL Server.
Note The installer does not automatically create the Oracle tablespaces for you. It only creates a ServiceCatalog schema with a fixed size of 500 MB in the tablespaces specified by you on the installation wizard. Thus, even if you decide to let the installer create the ServiceCatalog schema automatically, you may still want to follow the instructions in the subsequent sections to prepare your Oracle server with the appropriate tablespaces, prior to running the Cisco Prime Service Catalog installer.
If you choose to use Oracle for your database, follow the instructions in this section to prepare the Oracle server and to create an Oracle user to be the owner of the ServiceCatalog schema.
Configure the following Oracle parameters:
Step 1 Execute the following commands to find out the current values for the following Oracle parameters:
Step 2 If CURSOR_SHARING is not set to EXACT, use the following command to change it:
Step 3 If OPEN_CURSORS is less than 1000, use the following command to change it:
Step 4 If PROCESSES parameter is smaller than 500, then work with your DBA to bump up the PROCESSES parameter for your Oracle database to 500 (or higher).
Step 5 Restart the Oracle instance to make sure that the new parameters take effect.
Step 1 Execute the following sql command as the Oracle “sys” user to find out if the catcio.sql package has been installed on the Oracle database:
select count(*) from all_tables where owner='SYS' and table_name like 'IND_ONLINE$';
Step 2 If the returned value is ZERO, then log in to Oracle database as “sys” user (connect as “sysdba”), and install the catcio.sql package. This needs to be done before you proceed with the Prime Service Catalog installation. The catcio.sql script is usually located in the $ORACLE_HOME/rdbms/admin directory.
For a new installation, you must configure the Oracle database to use one of the following Unicode characters sets: “AL32UTF8" or "AL16UTF16”.
To determine if the database character set is Unicode, execute the following sql command:
If the value returned for the NLS_CHARACTERSET parameter is neither "AL32UTF8" nor "AL16UTF16", then you need to create a new Oracle database, and specify the character set to be either "AL32UTF8" or "AL16UTF16" at creation time.
Note For an upgrade installation from release 9.x, the database character set does not have to be Unicode.
For a new installation, you can prepare the tablespaces and database schema as described in this section before executing the Service Catalog installer, or you can let the Service Catalog installer create the database schema on the default tablespaces for you by selecting the "Create Database" option presented by the installation wizard. The "Create Database" option of the Service Catalog installer is described in more detail in the Installing Prime Service Catalog on WildFly Application Server.
To create tablespaces and database schema:
Step 1 Create a new tablespace named SERVICECATALOG, with initial size of 500 MB and AUTOEXTEND ON.
Step 2 Create a new temporary tablespace named SERVICECATALOG_TEMP, with initial size of 30 MB and AUTOEXTEND ON.
Step 3 Create a database user named CPSCUser, with default tablespace set to SERVICECATALOG and temporary tablespace set to SERVICECATALOG_TEMP. CPSCUser should be granted QUOTA UNLIMITED on the SERVICECATALOG tablespace.
Step 4 Log in to the Oracle server as the "sys" user, and execute the following commands to grant the permissions to "CPSCUser":
Step 5 The permissions listed above are required for the normal operation of the Service Catalog application. There are some special permissions needed for the application to monitor and automatically recover from long-running queries that may affect the performance of the product. If these additional permissions are not granted to "CPSCUser", the product will not fail; but the user may see an error message in the application server's log file that is similar to the following.
(Optional) To grant these special permissions, log in to the Oracle server as the "sys" user, and execute the following commands:
Note As an additional validation, the installer verifies if the database user is granted the optional privileges and if not, a warning message shows up indicating the missing privileges. Click OK to continue without the optional privileges or click Cancel to exit the installation. Not having the optional privileges does not cause the application to fail but limits its functionality.
If you want to perform database connection failover, you can use Oracle RAC 12C for your databases. For instructions to install Oracle RAC 12c, see Oracle documentation.
After you set up Oracle RAC , note down the cluster SCAN name and the service name. These parameters are required while configuring database during the Prime Service Catalog installation.
If you cannot use a DNS server or the DNS server is inaccessible on the Prime Service Catalog server, you must manually map the SCAN IP addresses to the SCAN name in the /etc/hosts file in that server. The following is an example of this mapping in the /etc/hosts file:
scan_ip-x is the SCAN IP address and scan_name is the SCAN name.
If you choose to use Microsoft SQL Server for your databases, follow the instructions in this section to prepare the SQL Server, and to create the ServiceCatalog database.
The SQL Server can be set up as a Default Instance or a Named Instance. The port number for each instance must be unique per database host.
The SQL Server must be configured to use mixed-mode authentication. This is because the Prime Service Catalog Installer needs to connect to the SQL Server as the "sa" user in order to create the Service Catalog schema.
For a new installation, you can prepare the ServiceCatalog database and login user as described in this section before executing the Service Catalog installer, or you can let the Service Catalog installer create the database and login user for you by selecting the "Create Database" option presented by the installation wizard. The "Create Database" option of the Service Catalog installer is described in more detail in the Installing Prime Service Catalog on WildFly Application Server.
To create the ServiceCatalog database and login user:
Step 1 Create a database named ServiceCatalog in the SQL Server, with the following settings for the data file
Step 2 Set the collating sequence for the ServiceCatalog database to case-insensitive.
Step 3 Put the ServiceCatalog database in SINGLE-USER mode, and execute the following command:
ALTER DATABASE ServiceCatalog SET READ_COMMITTED_SNAPSHOT ON.
Step 4 Put the ServiceCatalog database back in MULTI-USER mode.
Step 5 Create a SQL Server Login named CPSCUser, with the Default Database property set to “ServiceCatalog”.
Note CPSCUser must be a SQL Server login account that authenticates to the SQL Server using SQL Server authentication method, and not Windows authentication method.
Step 6 Ensure that the “Enforce Password Policy” option is unchecked in the Security setting properties for CPSCUser. Furthermore, the password for CPSCUser must contain only alphanumeric characters. For example, enter only letters and numbers for password. Do not enter any special characters like underlines, asterisks, brackets, and so on. Some combinations of these special characters may cause the installer to fail at product installation time with a "Database Connection Test failed" error message.
Step 7 Assign this CPSCUser to be the db_owner of the “ServiceCatalog” database. Verify your setting to ensure that:
Step 8 There are some special permissions needed for the application to monitor and automatically recover from long-running queries that may affect the performance of the product. If these additional permissions are not granted to "CPSCUser", the product will not fail; but the user may see some error messages in the application server's log file that are similar to the following:
(Optional) To grant these special permissions, log in to the SQL Server as the "sa" user, and execute the following commands:
When SQL Server 2012 is restarted, the requisition identity value jumps by 1000 after each restart of SQL Server 2012. To resolve this issue, add the -T272 as the database property for the SQL Server database. This will force the identity column value to increment by 1 instead of 1000 each time the SQL Server is restarted.
Step 1 Open SQL Server Configuration Manager.
Step 2 Click on the SQL Server Services in the left pane.
Step 3 Right click on the SQL Server (MSSQLSERVER) to open the properties window.
Step 4 In the Startup Parameters tab, enter -T272 in the Specify a startup parameter filed and click Add .
Step 5 Click OK to close the properties window.
Step 6 For the changes to take effect, you must restart the SQL Server 2012.