This chapter describes how to install Oracle Communications Pricing Design Center (PDC) 11.2 or 11.2 patch sets. Before installing PDC, read the following:
Overview of the PDC Complete Software Installation Procedure
Pre-Installation Tasks for the Complete PDC Software Installation
You can install PDC by using GUI or in the silent mode. Installing PDC in the silent mode lets you perform a noninteractive install of PDC. You can use the silent mode to install PDC quickly.
PDC install must be performed by a user who has permissions to write to the oraInventory directory and the MW_home/user_projects/domains directory, where MW_home is the directory in which the Oracle Middleware components are installed.
For installation instructions, see the following sections:
The steps for installing PDC by using GUI depend on the PDC components you choose to install:
To install both PDC and BRM Integration Pack, select the Complete installation option.
See "Installing PDC and BRM Integration Pack" for more information.
To install only PDC, select the Pricing Design Center installation option.
This option installs only PDC. See "Installing PDC" for more information.
To install only BRM Integration Pack, select the BRM Integration Pack installation option.
This option installs only BRM Integration Pack. See "Installing BRM Integration Pack" for more information.
To install both the PDC software and BRM Integration Pack on the same machine:
Obtain the PDC software. See "Obtaining the PDC Software".
Start the Oracle WebLogic Server domain administration server or the WebLogic Server domain managed server on which you want to deploy PDC, if it is not already started.
Ensure that the PDC database is running.
Note:
Ensure that the Oracle Database server is in Running state. The Installer connects to the Oracle Database server to verify the information you entered is valid.Go to the temp_dir directory, and run one of the following commands:
To start the GUI installer:
Java_home/bin/java -jar jarfile
where:
Java_home is the directory in which you installed the latest supported Java version.
jarfile is the pdcserver-11.2.0.x.0_generic.jar, x is the PDC 11.2 version that you are installing. For example, for PDC 11.2, the version is 0 and for PDC 11.2 Patch Set 1, the version is 1.
To start the GUI installer and install PDC using the oraInventory directory in a different location:
Java_home/bin/java -jar jarfile -invPtrLoc FilePath/oraInst.loc
where FilePath is the path to the directory in which the oraInst.loc file is located.
To start the GUI installer and create a silent installer response file during the installation:
Java_home/bin/java -jar jarfile -record -destinationFile path
where path is the response file location and name.
The Welcome screen appears.
Click Next.
The Specify Inventory Directory and Credentials screen appears if the oraInst.loc file is corrupt or not present. The default location of the oraInventory directory is in the /etc/oraInst.loc (Linux) file or the /var/opt/oracle/oraInst.loc (Solaris) file.
This screen displays the path to the default inventory directory and the default operating system group name.
(Optional) To change the default inventory directory details, do the following:
Enter the full path of the inventory directory.
Specify the name of the operating system group that has write permission to the inventory directory.
Click Next.
The Installation Location screen appears.
Enter the full path or browse to the directory in which to install PDC.
Click Next.
The Select Installation Type screen appears.
Select Complete and click Next.
The WebLogic Administration Server Connection screen appears.
Enter the following details for the WebLogic Server domain in which you want to deploy PDC:
In the Host Name field, enter the IP address or the host name of the machine on which the WebLogic Server domain is configured.
In the Port Number field, enter the port number assigned to the WebLogic Server domain administration server.
In the User Name field, enter the WebLogic Server domain administrator user name.
In the Password field, enter the WebLogic Server domain administrator user password.
In the WebLogic Home field, enter the path to the directory in which the WebLogic Server software is installed. For example, MW_home/wlserver.
Do one of the following:
If you do not want to enable secure communication for PDC, deselect the Enable SSL? (Recommended) check box.
To enable secure communication for PDC, leave the Enable SSL? (Recommended) check box selected, and in the KeyStore Location field, enter the path of the client-side keystore file generated from the exported public certificate using the keytool utility.
For more information, see "Configuring SSL for the WebLogic Server Domain".
Click Next.
The WebLogic Server screen appears.
Do one of the following:
To deploy PDC on a WebLogic Server domain administration server, select a WebLogic Server domain administration server from the list.
To deploy PDC on a WebLogic Server domain managed server, select a WebLogic Server domain managed server from the list.
Note:
Oracle recommends that you deploy PDC on a WebLogic Server managed server. If you select a WebLogic Server managed server, ensure that the WebLogic Server managed server and the node manager are running.Click Next.
The Pricing Design Center Schema User screen appears.
Do one of the following:
If you want to create a PDC schema user during installation, select Yes.
If you want to use an existing PDC schema user, select No and proceed to step 20.
Click Next.
The Pricing Design Center System Database Connection screen appears.
Enter the following information required to connect to the PDC database:
In the Host Name field, enter the IP address or the host name of the machine on which the PDC database is configured.
In the Port Number field, enter the port number assigned to the PDC database service.
In the User Name field, enter the PDC database user name. This user should be the SYSDBA user or should have the following capabilities on the PDC database: grant create user, grant any role, grant any privilege, select any table to username, and grant dba to username.
In the Password field, enter the PDC database user password.
In the Service Name field, enter the name of the PDC database service.
Note:
Ensure that the Oracle Database server is in Running state. The Installer connects to the Oracle Database server to verify the information you entered is valid.Click Next.
The Pricing Design Center Schema screen appears.
Enter the following information required to create the PDC schema in the PDC database and proceed to step 22:
In the User Name field, enter a PDC schema user name.
In the Password field, enter a PDC schema user password.
In the Confirm Password field, enter the PDC schema user password again.
In the PDC Tablespace field, enter the name of the tablespace for the PDC schema.
In the Temp Tablespace field, enter the name of the temporary tablespace for the PDC schema.
If you want to use the existing schema data for installing PDC on the secondary instances, select the Use the existing schema data check box. This is deselected by default.
Click Next.
The Pricing Design Center Schema screen appears.
Enter the following information required to connect to the PDC schema:
In the Host Name field, enter the IP address or the host name of the machine on which the PDC database is configured.
In the Port Number field, enter the port number assigned to the PDC database service.
In the Service Name field, enter the name of the PDC database service.
Note:
Ensure that the Oracle Database server is in Running state. The Installer connects to the Oracle Database server to verify the information you entered is valid.In the User Name field, enter the PDC schema user name.
In the Password field, enter the PDC schema user password.
If you want to use the existing schema data for installing PDC on the secondary instances, select Use the existing schema data.
This option is deselected by default.
Click Next.
The Pricing Design Center System User screen appears.
Enter the following information to create a PDC user to access the PDC GUI:
In the User Name field, enter a PDC user name.
In the Password field, enter a PDC user password.
Note:
The PDC user password can be a minimum of 8 characters and maximum of 12 characters long and should contain at least one non-alphabetic character. For example, Weblogic123.The user name must not be a part of the password.
In the Confirm Password field, enter the PDC user password again.
Click Next.
The Select Charging Engine for Usage Rating appears.
Do one of the following:
To use Oracle Communications Billing and Revenue Management (BRM) Elastic Charging Engine (ECE) for usage rating, select Elastic Charging Engine.
To use BRM real-time rating and batch rating engines for usage rating, select Realtime Rating and Batch Rating Engines.
Click Next.
The PDC Keystore Credentials screen appears.
Enter the following information required to encrypt the passwords:
In the Key Password field, enter the password PDC uses for accessing the PDC alias key in the keystore.
In the Confirm Key Password field, enter the key password again.
In the Keystore Password field, enter the password used for accessing the keystore.
In the Confirm Keystore Password field, enter the keystore password again.
For more information about keystores, see the discussion about managing passwords in PDC in PDC Security Guide.
Click Next.
The Migration Option screen appears.
Do one of the following:
If you do not want to migrate data, select Do not install Migration Utility and proceed to step 34.
To migrate the BRM real-time and batch rating engines pricing data to a PDC system that supports BRM real-time and batch rating engines, select Migrate RRE and BRE Pricing Data to PDC and proceed to step 34.
To migrate the BRM real-time and batch rating engines pricing data to a PDC system that supports ECE, select Migrate RRE and BRE Pricing Data to PDC with ECE and proceed to step 34.
To migrate the PDC pricing data to a PDC system that supports ECE, select Migrate PDC Pricing Data to PDC with ECE and proceed to step 30.
Click Next.
The Source Pricing Design Center WebLogic Server Connection screen appears.
If you are migrating the PDC pricing data to a PDC system that supports ECE, enter the following details for the WebLogic Server domain in which you deployed the source PDC system:
In the Host Name field, enter the IP address or the host name of the machine on which the WebLogic Server domain for the source PDC system is configured.
In the Port Number field, enter the port number assigned to the WebLogic Server domain administration server.
Note:
If you selected a WebLogic Server domain managed server in step 13, enter the port number to the managed server.In the User Name field, enter the WebLogic Server domain administrator user name.
In the Password field, enter the WebLogic Server domain administrator user password.
Do one of the following.
If you do not want to enable secure communication for PDC, deselect the Enable SSL? check box.
To enable secure communication for PDC, leave the Enable SSL? check box selected, and in the KeyStore Location field, enter the path of the client-side keystore file generated from the exported public certificate using the keytool utility.
For more information, see "Configuring SSL for the WebLogic Server Domain".
Click Next.
The Target Pricing Design Center WebLogic Server Connection screen appears.
If you are migrating the PDC pricing data to a PDC system that supports ECE, enter the following details for the WebLogic Server domain in which you deployed the target PDC system and proceed to step 36:
In the Host Name field, enter the IP address or the host name of the machine on which the WebLogic Server domain for the target PDC system is configured.
In the Port Number field, enter the port number assigned to the WebLogic Server domain administration server.
In the User Name field, enter the WebLogic Server domain administrator user name.
In the Password field, enter the WebLogic Server domain administrator user password.
Do one of the following.
If you do not want to enable secure communication for PDC, deselect the Enable SSL? check box.
To enable secure communication for PDC, leave the Enable SSL? check box selected, and in the KeyStore Location field, enter the path of the client-side keystore file generated from the exported public certificate using the keytool utility.
For more information, see "Configuring SSL for the WebLogic Server Domain".
Click Next.
The Pricing Design Center WebLogic Server Connection screen appears.
Enter the following details for the WebLogic Server domain in which you deployed PDC:
In the Host Name field, enter the IP address or the host name of the machine on which the WebLogic Server domain is configured.
In the Port Number field, enter the port number assigned to the WebLogic Server domain administration server.
In the User Name field, enter the WebLogic Server domain administrator user name.
In the Password field, enter the WebLogic Server domain administrator user password.
Do one of the following.
If you do not want to enable secure communication for PDC, deselect the Enable SSL? check box.
To enable secure communication for PDC, leave the Enable SSL? check box selected, and in the KeyStore Location field, enter the path of the client-side keystore file generated from the exported public certificate using the keytool utility.
For more information, see "Configuring SSL for the WebLogic Server Domain".
Click Next.
The BRM Server Location screen appears.
Enter the BRM batch and real-time rating engine details:
In the BRM field, enter the full path or browse to the directory in which BRM is installed.
In the BRM Pipeline field, enter the full path or browse to the directory in which Pipeline Manager is installed.
In the Perl Home field, enter the full path or browse to the directory in which the Perl libraries for BRM are installed.
Click Next.
The BRM Pipeline Manager Database Connection Screen appears.
Enter the following information required to connect to the BRM database:
In the Host Name field, enter the IP address or the host name of the machine on which the Pipeline Manager database is configured.
In the Port Number field, enter the port number assigned to the Pipeline Manager database service.
In the User Name field, enter the Pipeline Manager database schema user name.
In the Password field, enter the Pipeline Manager database schema user password.
In the Service Name field, enter the name of the Pipeline Manager database service.
Do one of the following:
Click Next.
The Transformation Cross-Reference Database Connection screen appears.
Enter the following information required to connect to the transformation cross-reference database:
In the Host Name field, enter the IP address or the host name of the machine on which the transformation cross-reference database is configured.
In the Port Number field, enter the port number assigned to the transformation cross-reference database service.
In the User Name field, enter the transformation cross-reference database user name. This user should be the SYSDBA user or should have the following capabilities on the transformation cross-reference database: grant create user, grant any role, grant any privilege, select any table to username, and grant dba to username.
In the Password field, enter the transformation cross-reference database user password.
In the Service Name field, enter the name of the transformation cross-reference database service.
Click Next.
The Transformation Cross-Reference Schema screen appears.
Enter the following information required to create the transformation cross-reference schema in the transformation cross-reference database and proceed to step 47:
Note:
If you are migrating the pricing data from a source PDC system to a target PDC system that supports ECE, provide the details of the transformation cross-reference schema that you created for the source PDC system.In the User Name field, enter a transformation cross-reference schema user name.
In the Password field, enter a transformation cross-reference schema user password.
In the Confirm Password field, enter the transformation cross-reference schema user password again.
In the PDC Tablespace field, enter the name of the tablespace for the transformation cross-reference schema.
In the Temp Tablespace field, enter the name of the temporary tablespace for the transformation cross-reference schema.
Click Next.
The Transformation Cross-Reference Schema screen appears.
Enter the following information required to connect to the transformation cross-reference database:
Note:
If you are migrating the pricing data from a source PDC system to a target PDC system that supports ECE, provide the details of the transformation cross-reference schema that you created for the source PDC system.In the Host Name field, enter the IP address or the host name of the machine on which the transformation cross-reference database is configured.
In the Port Number field, enter the port number assigned to the transformation cross-reference database service.
In the Service Name field, enter the name of the transformation cross-reference database service.
In the User Name field, enter the transformation cross-reference schema user name.
In the Password field, enter the transformation cross-reference schema user password.
Click Next.
The PDC User screen appears.
Enter the PDC user information.
In the User Name field, enter the PDC user name.
In the Password field, enter the PDC user password.
Do one of the following:
Do one of the following:
Click Next.
The Migration Cross-Reference Database Connection screen appears.
Enter the following information required to connect to the migration cross-reference database:
In the Host Name field, enter the IP address or the host name of the machine on which the migration cross-reference database is configured.
In the Port Number field, enter the port number assigned to the migration cross-reference database service.
In the User Name field, enter the migration cross-reference database user name. This user should be the SYSDBA user or should have the following capabilities on the transformation cross-reference database: create user, grant any role, grant any privileges, select any table for Enterprise edition, and DBA for XE.
In the Password field, enter the migration cross-reference database user password.
In the Service Name field, enter the name of the migration cross-reference database service.
Click Next.
The Migration Cross-Reference Schema screen appears.
Enter the following information required to create the migration cross-reference schema in the migration cross-reference database:
In the User Name field, enter a migration cross-reference schema user name.
In the Password field, enter a migration cross-reference schema user password.
In the Confirm Password field, enter the migration cross-reference schema user password again.
In the PDC Tablespace field, enter the name of the PDC tablespace for the migration cross-reference schema.
In the Temp Tablespace field, enter the name of the temporary tablespace for the migration cross-reference schema.
Click Next.
The Migration Cross-Reference Schema screen appears.
Enter the following information required to connect to the migration cross-reference database:
In the Host Name field, enter the IP address or the host name of the machine on which the migration cross-reference database is configured.
In the Port Number field, enter the port number assigned to the migration cross-reference database service.
In the Service Name field, enter the name of the migration cross-reference database service.
In the User Name field, enter the migration cross-reference schema user name.
In the Password field, enter the migration cross-reference schema user password.
Do one of the following:
Click Next.
The Migration User screen appears.
If you are migrating the PDC pricing data to a PDC system that supports ECE, proceed to 59.
Enter the migration user details and proceed to 63.
In the User Name field, enter a migration user name.
In the Password field, enter a migration user password.
In the Confirm Password field, enter the migration user password again.
Click Next.
The Source Migration User screen appears.
If you are migrating the PDC pricing data to a PDC system that supports ECE, enter the migration user details that you use to run the migration utility in the source PDC system:
In the User Name field, enter the migration user name.
In the Password field, enter the migration user password.
In the Confirm Password field, enter the migration user password again.
Click Next.
The Target Migration User screen appears.
If you are migrating the PDC pricing data to a PDC system that supports ECE, enter the migration user details that you want to use to run the migration utility in the target PDC system:
In the User Name field, enter the migration user name.
In the Password field, enter the migration user password.
In the Confirm Password field, enter the migration user password again.
Click Next.
The Keystore Credentials screen appears.
Enter the following information required to encrypt the passwords:
In the Key Password field, enter the password PDC uses for accessing the PDC alias key in the keystore.
In the Confirm Key Password field, enter the key password again.
In the Keystore Password field, enter the password used for accessing the keystore.
In the Confirm Keystore Password field, enter the keystore password again.
For more information about keystores, see the discussion about managing passwords in PDC in PDC Security Guide.
Click Next.
The Installation Summary screen appears.
Review the selections you have made in the preceding screens, and click Install.
The Installation Progress screen appears.
Note:
After the installation begins, clicking Stop installation stops the installation process, but the files that are already copied are not removed.When the installation is done, click Next, the Installation Complete screen appears.
Note down the provided URL. You use this URL to access PDC.
Click Finish to complete and exit.
See "Verifying the Pricing Design Center Installation" for information on verifying the successful installation of PDC.
See "About Installation Logs" for information on PDC Installer logs.
PDC installation must be performed by a user who has permissions to write to the oraInventory directory and the MW_home/user_projects/domains directory.
To install the complete PDC software:
Obtain the PDC software. See "Obtaining the PDC Software".
Start the Oracle WebLogic Server domain administration server or the WebLogic Server domain managed server on which you PDC 11.1 was deployed, if it is not already started.
Ensure that the PDC database is running.
Note:
Ensure that the Oracle Database server is in Running state. The Installer connects to the Oracle Database server to verify the information you entered is valid.Go to the temp_dir directory, and run one of the following commands:
To start the GUI installer:
Java_home/bin/java -jar jarfile
where:
Java_home is the directory in which you installed the latest supported Java version.
jarfile is the pdcserver-11.2.0.x.0_generic.jar, x is the PDC 11.2 version that you are installing. For example, for PDC 11.2, the version is 0 and for PDC 11.2 Patch Set 1, the version is 1.
To start the GUI installer and install PDC using the oraInventory directory in a different location:
Java_home/bin/java -jar jarfile -invPtrLoc FilePath/oraInst.loc
where FilePath is the path to the directory in which the oraInst.loc file is located.
To start the GUI installer and create a silent installer response file during the installation:
Java_home/bin/java -jar jarfile -record -destinationFile path
where path is the response file location and name.
The Welcome screen appears.
Click Next.
The Specify Inventory Directory and Credentials screen appears if the oraInst.loc file is corrupt or not present. The default location of the oraInventory directory is in the /etc/oraInst.loc (Linux) file or the /var/opt/oracle/oraInst.loc (Solaris) file.
This screen displays the path to the default inventory directory and the default operating system group name.
(Optional) To change the default inventory directory details, do the following:
Enter the full path of the inventory directory.
Specify the name of the operating system group that has write permission to the inventory directory.
Click Next.
The Select Installation Type screen appears.
Select Pricing Design Center and click Next.
The Specify Home Details screen appears.
This screen displays the default PDC installation name and the path to the default PDC installation directory.
(Optional) To change the default PDC installation details, do the following:
In the Name field, select the name for the installation from the list of names or enter a new installation name.
In the Path field, enter the path to the directory where you want to install PDC. Optionally, click Browse to navigate to the directory where you want to install PDC.
Click Next.
The Pricing Design Center WebLogic Server Connection screen appears.
Enter the following details for the WebLogic Server domain in which you want to deploy PDC:
In the Host Name field, enter the IP address or the host name of the machine on which the WebLogic Server domain is configured.
In the Port Number field, enter the port number assigned to the WebLogic Server domain administration server.
In the User Name field, enter the WebLogic Server domain administrator user name.
In the Password field, enter the WebLogic Server domain administrator user password.
In the WebLogic Home field, enter the path to the directory in which the WebLogic Server software is installed. For example, MW_home/wlserver, where MW_home is the directory in which the Oracle Middleware components are installed.
Do one of the following:
If you do not want to enable secure communication for PDC, deselect the Enable SSL? check box.
To enable secure communication for PDC, leave the Enable SSL? check box selected, and in the KeyStore Location field, enter the path of the client-side keystore file generated from the exported public certificate using the keytool utility.
For more information, see "Configuring SSL for the WebLogic Server Domain".
Click Next.
The WebLogic Server screen appears.
Do one of the following:
To deploy PDC on a WebLogic Server domain administration server, select a WebLogic Server domain administration server from the list.
To deploy PDC on a WebLogic Server domain managed server, select a WebLogic Server domain managed server from the list.
Note:
Oracle recommends that you deploy PDC on a WebLogic Server managed server. If you select a WebLogic Server managed server, ensure that the WebLogic Server managed server and the node manager are running.Click Next.
The Pricing Design Center Schema User screen appears.
Do one of the following:
Click Next.
The Pricing Design Center System Database Connection screen appears.
Enter the following information required to connect to the PDC database:
In the Host Name field, enter the IP address or the host name of the machine on which the PDC database is configured.
In the Port Number field, enter the port number assigned to the PDC database service.
In the User Name field, enter the PDC database user name. This user should be the SYSDBA user or should have the following capabilities on the PDC database: grant create user, grant any role, grant any privilege, select any table to username, and grant dba to username.
In the Password field, enter the PDC database user password.
In the Service Name field, enter the name of the PDC database service.
Note:
Ensure that the Oracle Database server is in Running state. The Installer connects to the Oracle Database server to verify the information you entered is valid.Click Next.
The Pricing Design Center Schema screen appears.
Enter the following information required to create the PDC schema in the PDC database and proceed to step 22:
In the User Name field, enter a PDC schema user name.
In the Password field, enter a PDC schema user password.
In the Confirm Password field, enter the PDC schema user password again.
In the PDC Tablespace field, enter the name of the tablespace for the PDC schema.
In the Temp Tablespace field, enter the name of the temporary tablespace for the PDC schema.
If you want to use the existing schema data for installing PDC on the secondary instances, select the Use the existing schema data check box. This is deselected by default.
Click Next.
The Pricing Design Center Schema screen appears.
Enter the following information required to connect to the PDC schema:
In the Host Name field, enter the IP address or the host name of the machine on which the PDC database is configured.
In the Port Number field, enter the port number assigned to the PDC database service.
In the Service Name field, enter the name of the PDC database service.
Note:
Ensure that the Oracle Database server is in Running state. The Installer connects to the Oracle Database server to verify the information you entered is valid.In the User Name field, enter the PDC schema user name.
In the Password field, enter the PDC schema user password.
If you want to use the existing schema data for installing PDC on the secondary instances, select Use the existing schema data.
This option is deselected by default.
Click Next.
The Pricing Design Center System User screen appears.
Enter the following information to create a PDC user to access the PDC GUI:
In the User Name field, enter a PDC user name.
In the Password field, enter a PDC user password.
Note:
The PDC user password can be a minimum of 8 characters and maximum of 12 characters long and should contain at least one non-alphabetic character. For example, Weblogic123.The user name must not be a part of the password.
Click Next.
The Select charging Engine for Usage Rating appears.
Do one of the following:
To use Oracle Communications Billing and Revenue Management (BRM) real-time rating and batch rating engines for usage rating, select Realtime Rating and Batch Rating Engines.
To use BRM Elastic Charging Engine (ECE) for usage rating, select Elastic Charging Engine.
Click Next.
The Keystore Credentials screen appears.
Enter the following information required to encrypt the passwords:
In the Key Password field, enter the password PDC uses for accessing the PDC alias key in the keystore.
In the Confirm Key Password field, enter the key password again.
In the Keystore Password field, enter the password used for accessing the keystore.
In the Confirm Keystore Password field, enter the keystore password again.
For more information about keystores, see the discussion about managing passwords in PDC in PDC Security Guide.
Click Next.
The Installation Summary screen appears.
Review the selections you have made in the preceding screens, and click Install.
The Installation Progress screen appears.
Note:
After the installation begins, clicking Stop installation stops the installation process, but the files that are already copied are not removed.When the installation is done, click Next, the Installation Complete screen appears.
Note down the provided URL. You use this URL to access PDC.
Click Finish to complete and exit.
See "Verifying the Pricing Design Center Installation" for information on verifying the successful installation of PDC.
See "About Installation Logs" for information on PDC Installer logs.
BRM Integration Pack is a set of utilities that transform and transfer pricing components configured in PDC to the BRM system. If BRM and Pipeline Manager are installed on different machines, you must also install Pipeline Configuration Manager. For instructions on how to install Pipeline Configuration Manager, see BRM Installation Guide.
Note:
BRM Integration Pack installation must be performed as the UNIX user who installed BRM; for example, pin_user.To install BRM Integration Pack:
Obtain the PDC software. See "Obtaining the PDC Software".
Start the Oracle WebLogic Server domain administration server or the WebLogic Server domain managed server on which you PDC 11.1 was deployed, if it is not already started.
Ensure that the PDC database is running.
Note:
Ensure that the Oracle Database server is in Running state. The Installer connects to the Oracle Database server to verify the information you entered is valid.Go to the temp_dir directory, and run one of the following commands:
To start the GUI installer:
Java_home/bin/java -jar jarfile
where:
Java_home is the directory in which you installed the latest supported Java version.
jarfile is the pdcserver-11.2.0.x.0_generic.jar, x is the PDC 11.2 version that you are installing. For example, for PDC 11.2, the version is 0 and for PDC 11.2 Patch Set 1, the version is 1.
To start the GUI installer and install PDC using the oraInventory directory in a different location:
Java_home/bin/java -jar jarfile -invPtrLoc FilePath/oraInst.loc
where FilePath is the path to the directory in which the oraInst.loc file is located.
To start the GUI installer and create a silent installer response file during the installation:
Java_home/bin/java -jar jarfile -record -destinationFile path
where path is the response file location and name.
The Welcome screen appears.
Click Next.
The Specify Inventory Directory and Credentials screen appears if the oraInst.loc file is corrupt or not present. The default location of the oraInventory directory is in the /etc/oraInst.loc (Linux) file or the /var/opt/oracle/oraInst.loc (Solaris) file.
This screen displays the path to the default inventory directory and the default operating system group name.
(Optional) To change the default inventory directory details, do the following:
Enter the full path of the inventory directory.
Specify the name of the operating system group that has write permission to the inventory directory.
Click Next.
The Select Installation Type screen appears.
Select BRM Integration Pack and click Next.
The Specify Home Details screen appears.
This screen displays the default installation name and the path to the default installation directory.
(Optional) To change the default BRM Integration Pack installation details, do the following:
Note:
If you are installing BRM Integration Pack on the machine on which PDC is installed, then you must provide a different name and path for the BRM Integration Pack installation.In the Name field, select the name for the installation from the list of names or enter a new installation name.
In the Path field, enter the path to the directory where you want to install BRM Integration Pack. Optionally, click Browse to navigate to the directory where you want to install BRM Integration Pack.
Click Next.
The Migration Option screen appears.
Do one of the following:
If you do not want to migrate data, select Do not install Migration Utility and proceed to step 16.
To migrate the BRM real-time and batch rating engines pricing data to a PDC system that supports BRM real-time and batch rating engines, select Migrate RRE and BRE Pricing Data to PDC and proceed to step 16.
To migrate the BRM real-time and batch rating engines pricing data to a PDC system that supports ECE, select Migrate RRE and BRE Pricing Data to PDC with ECE and proceed to step 16.
To migrate the PDC pricing data to a PDC system that supports ECE, select Migrate PDC Pricing Data to PDC with ECE and proceed to step 12.
Click Next.
The Source Pricing Design Center WebLogic Server Connection screen appears.
If you are migrating the PDC pricing data to a PDC system that supports ECE, enter the following details for the WebLogic Server domain in which you deployed the source PDC system:
In the Host Name field, enter the IP address or the host name of the machine on which the WebLogic Server domain for the source PDC system is configured.
In the Port Number field, enter the port number assigned to the WebLogic Server domain administration server.
Note:
If you selected a WebLogic Server domain managed server in step 13, enter the port number to the managed server.In the User Name field, enter the WebLogic Server domain administrator user name.
In the Password field, enter the WebLogic Server domain administrator user password.
Do one of the following.
If you do not want to enable secure communication for PDC, deselect the Enable SSL? check box.
To enable secure communication for PDC, leave the Enable SSL? check box selected, and in the KeyStore Location field, enter the path of the client-side keystore file generated from the exported public certificate using the keytool utility.
For more information, see "Configuring SSL for the WebLogic Server Domain".
Click Next.
The Target Pricing Design Center WebLogic Server Connection screen appears.
If you are migrating the PDC pricing data to a PDC system that supports ECE, enter the following details for the WebLogic Server domain in which you deployed the target PDC system and proceed to step 18:
In the Host Name field, enter the IP address or the host name of the machine on which the WebLogic Server domain for the target PDC system is configured.
In the Port Number field, enter the port number assigned to the WebLogic Server domain administration server.
In the User Name field, enter the WebLogic Server domain administrator user name.
In the Password field, enter the WebLogic Server domain administrator user password.
Do one of the following.
If you do not want to enable secure communication for PDC, deselect the Enable SSL? check box.
To enable secure communication for PDC, leave the Enable SSL? check box selected, and in the KeyStore Location field, enter the path of the client-side keystore file generated from the exported public certificate using the keytool utility.
For more information, see "Configuring SSL for the WebLogic Server Domain".
Click Next.
The Pricing Design Center WebLogic Server Connection screen appears.
Enter the following details for the WebLogic Server domain in which you deployed PDC:
In the Host Name field, enter the IP address or the host name of the machine on which the WebLogic Server domain is configured.
In the Port Number field, enter the port number assigned to the WebLogic Server domain administration server.
In the User Name field, enter the WebLogic Server domain administrator user name.
In the Password field, enter the WebLogic Server domain administrator user password.
Do one of the following.
If you do not want to enable secure communication for PDC, deselect the Enable SSL? check box.
To enable secure communication for PDC, leave the Enable SSL? check box selected, and in the KeyStore Location field, enter the path of the client-side keystore file generated from the exported public certificate using the keytool utility.
For more information, see "Configuring SSL for the WebLogic Server Domain".
Click Next.
The BRM Server Location screen appears.
Enter the BRM batch and real-time rating engine details:
In the BRM field, enter the full path or browse to the directory in which BRM is installed.
In the BRM Pipeline field, enter the full path or browse to the directory in which Pipeline Manager is installed.
In the Perl Home field, enter the full path or browse to the directory in which the Perl libraries for BRM are installed.
Click Next.
The BRM Pipeline Manager Database Connection Screen appears.
Enter the following information required to connect to the BRM database:
In the Host Name field, enter the IP address or the host name of the machine on which the Pipeline Manager database is configured.
In the Port Number field, enter the port number assigned to the Pipeline Manager database service.
In the User Name field, enter the Pipeline Manager database schema user name.
In the Password field, enter the Pipeline Manager database schema user password.
In the Service Name field, enter the name of the Pipeline Manager database service.
Do one of the following:
Click Next.
The Transformation Cross-Reference Database Connection screen appears.
Enter the following information required to connect to the transformation cross-reference database:
In the Host Name field, enter the IP address or the host name of the machine on which the transformation cross-reference database is configured.
In the Port Number field, enter the port number assigned to the transformation cross-reference database service.
In the User Name field, enter the transformation cross-reference database user name. This user should be the SYSDBA user or should have the following capabilities on the transformation cross-reference database: grant create user, grant any role, grant any privilege, select any table to username, and grant dba to username.
In the Password field, enter the transformation cross-reference database user password.
In the Service Name field, enter the name of the transformation cross-reference database service.
Click Next.
The Transformation Cross-Reference Schema screen appears.
Enter the following information required to create the transformation cross-reference schema in the transformation cross-reference database and proceed to step 29:
Note:
If you are migrating the pricing data from a source PDC system to a target PDC system that supports ECE, provide the details of the transformation cross-reference schema that you created for the source PDC system.In the User Name field, enter a transformation cross-reference schema user name.
In the Password field, enter a transformation cross-reference schema user password.
In the Confirm Password field, enter the transformation cross-reference schema user password again.
In the PDC Tablespace field, enter the name of the tablespace for the transformation cross-reference schema.
In the Temp Tablespace field, enter the name of the temporary tablespace for the transformation cross-reference schema.
Click Next.
The Transformation Cross-Reference Schema screen appears.
Enter the following information required to connect to the transformation cross-reference database:
Note:
If you are migrating the pricing data from a source PDC system to a target PDC system that supports ECE, provide the details of the transformation cross-reference schema that you created for the source PDC system.In the Host Name field, enter the IP address or the host name of the machine on which the transformation cross-reference database is configured.
In the Port Number field, enter the port number assigned to the transformation cross-reference database service.
In the Service Name field, enter the name of the transformation cross-reference database service.
In the User Name field, enter the transformation cross-reference schema user name.
In the Password field, enter the transformation cross-reference schema user password.
Click Next.
The PDC User screen appears.
Enter the PDC user information.
In the User Name field, enter the PDC user name.
In the Password field, enter the PDC user password.
In the Confirm Password field, enter the PDC user password again.
Do one of the following:
Do one of the following:
Click Next.
The Migration Cross-Reference Database Connection screen appears.
Enter the following information required to connect to the migration cross-reference database:
In the Host Name field, enter the IP address or the host name of the machine on which the migration cross-reference database is configured.
In the Port Number field, enter the port number assigned to the migration cross-reference database service.
In the User Name field, enter the migration cross-reference database user name. This user should be the SYSDBA user or should have the following capabilities on the transformation cross-reference database: create user, grant any role, grant any privileges, select any table for Enterprise edition, and DBA for XE.
In the Password field, enter the migration cross-reference database user password.
In the Service Name field, enter the name of the migration cross-reference database service.
Click Next.
The Migration Cross-Reference Schema screen appears.
Enter the following information required to create the migration cross-reference schema in the migration cross-reference database:
In the User Name field, enter a migration cross-reference schema user name.
In the Password field, enter a migration cross-reference schema user password.
In the Confirm Password field, enter the migration cross-reference schema user password again.
In the PDC Tablespace field, enter the name of the PDC tablespace for the migration cross-reference schema.
In the Temp Tablespace field, enter the name of the temporary tablespace for the migration cross-reference schema.
Click Next.
The Migration Cross-Reference Schema screen appears.
Enter the following information required to connect to the migration cross-reference database:
In the Host Name field, enter the IP address or the host name of the machine on which the migration cross-reference database is configured.
In the Port Number field, enter the port number assigned to the migration cross-reference database service.
In the Service Name field, enter the name of the migration cross-reference database service.
In the User Name field, enter the migration cross-reference schema user name.
In the Password field, enter the migration cross-reference schema user password.
Do one of the following:
Click Next.
The Migration User screen appears.
If you are migrating the PDC pricing data to a PDC system that supports ECE, proceed to 41.
Enter the migration user details and proceed to 45.
In the User Name field, enter a migration user name.
In the Password field, enter a migration user password.
In the Confirm Password field, enter the migration user password again.
Click Next.
The Source Migration User screen appears.
If you are migrating the PDC pricing data to a PDC system that supports ECE, enter the migration user details that you use to run the migration utility in the source PDC system:
In the User Name field, enter the migration user name.
In the Password field, enter the migration user password.
In the Confirm Password field, enter the migration user password again.
Click Next.
The Target Migration User screen appears.
If you are migrating the PDC pricing data to a PDC system that supports ECE, enter the migration user details that you want to use to run the migration utility in the target PDC system:
In the User Name field, enter the migration user name.
In the Password field, enter the migration user password.
In the Confirm Password field, enter the migration user password again.
Click Next.
The Keystore Credentials screen appears.
Enter the following information required to encrypt the passwords:
In the Key Password field, enter the password PDC uses for accessing the PDC alias key in the keystore.
In the Confirm Key Password field, enter the key password again.
In the Keystore Password field, enter the password used for accessing the keystore.
In the Confirm Keystore Password field, enter the keystore password again.
Click Next.
The Installation Summary screen appears.
Review the selections you have made in the preceding screens, and click Install.
The Installation Progress screen appears.
Note:
After the installation begins, clicking Stop installation stops the installation process, but the files that are already copied are not removed.When the installation is done, click Next, the Installation Complete screen appears.
Click Finish to complete and exit.
See "Verifying the Pricing Design Center Installation" for information on verifying the successful installation of BRM Integration Pack.
See "About Installation Logs" for information on PDC Installer logs.
Use silent install mode when you are installing PDC using the same configuration repeatedly. Silent install mode does not use the GUI and it runs in the background.
In this mode, you use a response file template that contains a predefined set of values to install PDC and BRM Integration Pack. You can generate a response file that contains the parameters and values during the PDC GUI installation.
To create a response file:
Create the response file by doing one of the following:
Create a copy of the response file that was generated during the GUI installation. See "Installing PDC and BRM Integration Pack" for more information.
Note:
The GUI Installer does not store passwords provided during installation in the response file. You must manually add the passwords after creating a copy of the response file.Create a response file using the template by running the following command:
Java_home/bin/java -jar jarfile -getResponseFileTemplates
where:
Java_home is the directory in which you installed the latest supported Java version.
jarfile is the pdcserver-11.2.0.x.0_generic.jar, x is the PDC 11.2 version that you are installing. For example, for PDC 11.2, the version is 0 and for PDC 11.2 Patch Set 1, the version is 1.
The following response file is created with the default values.
oracle.communications.pdc.PricingDesignCenter.rsp
Use this file template if you are installing PDC.
You can create as many response files as needed.
Open the file in a text editor.
Modify the response file you copied by specifying the key-value information for the parameters you want in your installation.
Note:
The response file template contains guidelines and examples on how to enter the values in the parameters.
The Installer treats incorrect context, format, and type values in a response file as if no value were specified.
Save and close the response file.
To install PDC in silent mode:
Create the response file. See "Creating a Response File".
Copy the response file you created for PDC to the machine on which you run the silent installation.
On the machine on which you run the silent installation, go to the temp_dir directory to which you have downloaded the PDC server software pack, and run the following command:
Java_home/bin/java -jar jarfile -debug -invPtrLoc Inventory_home/oraInventory/oraInst.loc [parameter=value] -responseFile path -silent
where:
path is the absolute path to the response file.
jarfile is the pdcserver-11.2.0.x.0_generic.jar, x is the PDC 11.2 version that you are installing. For example, for PDC 11.2, the version is 0 and for PDC 11.2 Patch Set 1, the version is 1.
parameter is the name of an installation parameter.
value is the value of the installation parameter.
For example:
Java_home/bin/java -jar pdcserver-11.2.0.0.0_generic.jar -debug -invPtrLoc Inventory_home/oraInventory/oraInst.loc INSTALL_TYPE=Complete -responseFile /tmp/oracle.communications.pdc.PricingDesignCenter.rsp -silent
The installation runs silently in the background.
To install BRM Integration Pack in the silent mode:
Create the response file. See "Creating a Response File".
Copy the response file you created for BRM Integration Pack to the machine on which you run the silent installation.
On the machine on which you run the silent installation, go to the temp_dir directory to which you have downloaded the BRM Integration Pack, and run the following command:
Java_home/bin/java -jar jarfile -debug -invPtrLoc Inventory_home/oraInventory/oraInst.loc [parameter=value] -responseFile path -silent
where:
Java_home is the directory in which you installed the latest supported Java version.
jarfile is the pdcserver-11.2.0.x.0_generic.jar, x is the PDC 11.2 version that you are installing. For example, for PDC 11.2, the version is 0 and for PDC 11.2 Patch Set 1, the version is 1.
parameter is the name of an installation parameter.
value is the value of the installation parameter.
path is the absolute path to the response file.
For example:
Java_home/bin/java -jar pdcserver-11.2.0.0.0_generic.jar -debug -invPtrLoc Inventory_home/oraInventory/oraInst.loc INSTALL_TYPE=Complete -responseFile /tmp/oracle.communications.pdc.PricingDesignCenter.rsp -silent
The installation runs silently in the background.
See "Verifying the Pricing Design Center Installation" for information on verifying the successful installation of BRM Integration Pack.
See "About Installation Logs" for information on PDC Installer logs.
The installation logs are used for debugging purposes. You can check the log files in the oraInventory/logs directory. The default location of the oraInventory directory is in the /etc/oraInst.loc (Linux) file or the /var/opt/oracle/oraInst.loc (Solaris) file.
You use the following log files to monitor installation and post-installations:
installActionTimeStamp.log
oraInstallTimeStamp.err
oraInstallTimeStamp.out
dbScriptsgTimeStamp.log (for the scripts executed using SQL*Plus and JDBC)
silentInstallTimeStamp.log (for silent mode installation)
where TimeStamp is the date and time the log file was created.