This chapter describes how to install Oracle Communications Pricing Design Center (PDC). Before installing PDC, read the following:
Overview of the PDC Complete Software Installation Procedure
Pre-Installation Tasks for the Complete PDC Software Installation
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, where MW_Home is the directory in which the Oracle Middleware components are installed.
To install the complete PDC software:
On the machine hosting the Oracle WebLogic Server domain, create a temporary directory (temp_dir).
Go to the My Oracle Support Web site:
Sign in with your user name and password.
Click the Patches & Updates tab.
From the list, select Patch Name or Number.
In the text field, enter 27531591.
Click Search.
The Patch Search Results page appears.
Click the patch name.
The patch details appear.
From the Platform list, select the platform and click Download.
The File Download dialog box appears.
Download the appropriate p27531591_1110120_platform.zip file to temp_dir, where platform is linux or solaris.
Unzip the p27531591_1110120_platform.zip file.
Unzip the PricingDesignCenter-11.1.0.12.0-platform.zip file.
The following folder structure is created:
pdc/Disk1/install/
pdc/Disk1/stage/
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.In the pdc/Disk1/install/ directory, do one of the following:
To install the complete PDC software using the default oraInventory directory, run the following command:
./runInstaller.sh
To install the complete PDC software using the oraInventory directory in a different location, enter the following command:
./runInstaller.sh -invPtrLoc FilePath/oraInst.loc
where FilePath is the path to the directory in which the oraInst.loc file is located.
To record the response file contents during the GUI installation, run the following command:
./runInstaller.sh -record -destinationFile path
where path is the complete path and name of the response file.
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_10.3, 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 Use SSL? check box.
To enable secure communication for PDC, leave the Use 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/Cluster 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 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 have the following capabilities on the PDC 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 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:
In the User Name field, enter a PDC schema user name.
In the Password field, enter a PDC schema user password.
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.
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 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) 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 Summary screen appears.
Review the selections you have made in the preceding screens, and click Install.
The Install 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 End of Installation screen appears, note down the provided URL.
You use this URL to access PDC.
Click Exit.
The Exit confirmation box appears.
Click Yes.
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:
Start the Oracle WebLogic Server domain administration server or the managed server on which you want to deploy PDC, if it is not already started.
Verify that you are able to connect to the BRM database.
In the pdc/Disk1/install/ directory, do one of the following:
To install BRM Integration Pack using the default oraInventory directory, run the following command:
./runInstaller.sh
To install BRM Integration Pack using the oraInventory directory in a different location, enter the following command:
./runInstaller.sh -invPtrLoc FilePath/oraInst.loc
where FilePath is the path to the directory in which the oraInst.loc file is located.
To record the response file contents during the GUI installation, run the following command:
./runInstaller.sh -record -destinationFile path
where path is the complete path and name of the response file. See "Installing PDC in Silent Mode" for more information.
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 Migration not required and proceed to step 15.
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 17.
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 17.
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 11.
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.
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 Use SSL? check box.
To enable secure communication for PDC, leave the Use 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:
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 Use SSL? check box.
To enable secure communication for PDC, leave the Use 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 Select charging Engine for Usage Rating Screen appears.
Do one of the following:
To use BRM real-time rating and batch rating engines for usage rating, select Realtime Rating and Batch Rating Engines.
To use ECE for usage rating, select Elastic Charging Engine.
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 Use SSL? check box.
To enable secure communication for PDC, leave the Use 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 path to the directory in which BRM is installed.
In the BRM Pipeline field, enter the path to the directory in which Pipeline Manager is installed.
In the BRM ThirdParty Software field, enter the path to the directory in which BRM ThirdParty Software is 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.
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 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 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:
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 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 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:
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.
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 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.
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 35.
Enter the migration user details and proceed to 39.
In the User Name field, enter a migration user name.
In the Password field, enter a migration user password.
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.
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.
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 Summary screen appears.
Review the selections you have made in the preceding screens, and click Install.
The Install screen appears.
Note:
After the installation begins, if you click Stop installation, the installation process stops, but the files that are already copied are not removed.The End of Installation screen appears.
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.
A response file contains answers to installation questions that you would otherwise provide in an interactive installation session. Each answer is stored as a value for a variable identified in the response file.
When you extract the PDC pack, the response file templates are saved in the following locations:
pdc/Disk1/stage/Response/oracle.communications.pdc.PricingDesignCenter.rsp
Use this file template if you are installing PDC.
pdc/Disk1/stage/Response/oracle.communications.pdc.BRMIntegrationPack.rsp
Use this file template if you are installing BRM Integration Pack.
The response file templates contain all the parameters that the Installer requires during the silent, unattended installation but does not contain the parameter values. You can generate a response file that contains the parameters and values during the PDC GUI installation.
To generate a complete response file, run the following command to launch the Installer in the GUI mode:
./runInstaller.sh -record -destinationFile path
Where path is the response file location.
To install PDC in silent mode:
Create a copy of the pdc/Disk1/stage/Response/oracle.communications.pdc.PricingDesignCenter.rsp file or the response file that was generated during the GUI installation and open it in a text editor.
Enter the values in the parameters to reflect the PDC installation requirements.
Notes:
The pdc/Disk1/stage/Response/oracle.communications.pdc.PricingDesignCenter.rsp file contains guidelines and examples on how to enter the values in the parameters.
In silent install mode, the Installer treats incorrect context, format, or type values within a response file as if no value were specified.
Save and close the file.
Go to the pdc/Disk1/install/ directory and enter the following command:
./runInstaller.sh -responseFile path -silent
where path is the PDC response file name and location.
For example:
./runInstaller.sh -responseFile /response_files/PricingDesignCenter.rsp -silent
The installation runs silently in the background.
To install BRM Integration Pack in silent mode:
Create a copy of the pdc/Disk1/stage/Response/oracle.communications.pdc.BRMIntegrationPack.rsp file or the response file that was generated during the GUI installation and open it in a text editor.
Enter the values in the parameters to reflect the BRM Integration Pack installation requirements.
Notes:
The pdc/Disk1/stage/Response/oracle.communications.pdc.BRMIntegrationPack.rsp file contains guidelines and examples on how to enter the values in the parameters.
In silent install mode, the Installer treats incorrect context, format, or type values within a response file as if no value were specified.
Save and close the file.
Go to the pdc/Disk1/install/ directory and enter the following command:
./runInstaller.sh -responseFile path -silent
where path is the BRM Integration Pack response file name and location.
For example:
./runInstaller.sh -responseFile /response_files/BRMIntegrationPack.rsp -silent
The installation runs silently in the background.
See "Verifying the Pricing Design Center Installation" for information on verifying the successful installation of PDC and BRM Integration Pack.
See "About Installation Logs" for information on the 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.