Installing Pipeline Configuration Center

9 Installing Pipeline Configuration Center

Learn how to install Pipeline Configuration Center (PCC), which is a Web-based application that serves as the user interface for Pipeline Manager, on top of the Oracle Communications Billing and Revenue Management (BRM) software.

Note:

Localized versions of PCC are supported by BRM 12.0 Patch Set 3 and later releases. The following languages are supported: French, Italian, Spanish, Japanese, Korean, Chinese Simplified, Chinese Traditional, and Portuguese Brazilian.

Topics in this document:

PCC Installation Overview

Note:

If you install a BRM patch set, you must install the same version of PCC 12.0 patch set.

PCC installation should be performed only by experienced system administrators. You must be familiar with the following before you begin the installation:

UNIX operating system
Oracle WebLogic Server administration
Oracle Database 12c administration

Additionally, you should have experience installing Java-related packages.

To learn more about PCC installation, see the following:

About the PCC Architecture

PCC is a Web-based BRM application that serves as the user interface for Pipeline Manager.

PCC runs on a managed server in an Oracle WebLogic Server domain. To interact with PCC, users enter the PCC login page URL in a browser and then enter their PCC user name and password in the login page. After a user is authenticated, the PCC home page appears in the browser.

Figure 9-1 shows how PCC and Pipeline Manager are integrated.

Figure 9-1 PCC and Pipeline Manager Integrated Architecture

Description of "Figure 9-1 PCC and Pipeline Manager Integrated Architecture"

Overview of the PCC Installation Procedure

The following is an overview of the PCC installation procedure:

Plan your installation. Planning an installation involves the following:
- Determining the scale of your implementation (for example, is it a small test system or a large production system?).
- Assessing how many physical computers you need and which software components to install on which computers.
Review system requirements.
Perform the following pre-installation tasks:
- Install and configure Oracle WebLogic Server.
- Set the JAVA_HOME environment variable.
- Install and configure BRM.
- Configure Oracle Database advanced security encryption and integrity algorithms for a secure connection from the installer.
Install PCC.
Perform the post-installation configuration tasks.
Verify the installation.

Performing a Secure PCC Installation

You can install PCC in the following modes:

GUI mode
Silent mode

Oracle recommends that you install PCC using Secure Sockets Layer (SSL) in a production environment. See "Installing PCC" for more information.

The silent mode installation is not meant for production environments. It should be used only in test environments and only for setting up quickly or backing up the properties for later use in another test environment.

See "Secure Deployment Checklist" for information about the checklist to deploy PCC securely.

Ensuring a Successful PCC Installation

To ensure that the PCC installation is successful, follow these guidelines:

As you install each component (for example, the WebLogic Server), verify that the component is installed successfully before continuing the installation process.
Pay close attention to the system requirements.

Before you begin installing the application, ensure that your system has the required software. In addition, ensure that you know all the required configuration values, such as host names and port numbers.
Make a note of any new configuration values as you create them.

You will be required to enter configuration values later.

PCC System Requirements

Before you install and run PCC, ensure that you have installed and configured the required external software, hardware, server, and database systems:

Software Requirements

PCC is supported on Linux (both Oracle Linux and Red Hat Enterprise Linux), Oracle Solaris for SPARC, Windows 8.1 (browser only), and Windows 10 (browser only). PCC is also deployed on an Oracle WebLogic Server domain.

You must install and connect all required software for optimal performance. For the list of supported software versions, see "PCC Software Compatibility" in BRM Compatibility Matrix.

Hardware Requirements

The number and configuration of the computers that you employ for your PCC installation depend on the scale and the kind of deployment you have planned.

Table 9-1 provides the minimum hardware requirements for PCC installed on a single managed server in a domain.

Table 9-1 PCC Minimum Hardware Requirements

Component	Requirement
Hard disk	1.5 GB of free disk space. Note: A minimum of 1.5 GB should be free in the domain home.
Processor	Oracle recommends using twin cores, each running at 1.5 GHz CPU.
Memory	A minimum of 4 GB physical memory and 4 GB swap. If you plan to install the database on the same server as PCC, the minimum memory requirements increase to 6 GB physical memory and 6 GB swap.

Component

Requirement

Hard disk

1.5 GB of free disk space.

Note: A minimum of 1.5 GB should be free in the domain home.

Processor

Oracle recommends using twin cores, each running at 1.5 GHz CPU.

Memory

A minimum of 4 GB physical memory and 4 GB swap.

If you plan to install the database on the same server as PCC, the minimum memory requirements increase to 6 GB physical memory and 6 GB swap.

Overview of Pre-Installation Tasks

Pre-installation tasks for PCC consists of the following steps:

Install and configure Oracle WebLogic Server. See "Installing and Configuring Oracle WebLogic Server".
- Enable SSL for the target Oracle WebLogic Server server domain, configure the server KeyStore certificate, and get the client KeyStore trusted certificate (.p12 [recommended] or .jks file).
- If SSL is enabled, ensure that the KeyStore file is created in a secure drive and access is strictly limited to the user account.
Set the JAVA_HOME environment variable. See "Setting the JAVA_HOME Environment Variable".
Download and save the ojdbc8.jar file to your PCC system. See "Obtaining the Oracle JDBC Driver File".
Install and configure BRM. See "Installing and Configuring BRM".
Configure Oracle Database advanced security encryption and integrity algorithms for a secure connection from the installer. See the Oracle Database documentation for advanced security configuration parameters. This is required for the PCC installer to make a secured (encrypted) database connection over the network.
Download the PCC software. See "Downloading the PCC Software".

Installing and Configuring Oracle WebLogic Server

This section describes procedures related to installing Oracle WebLogic Server and configuring the Oracle WebLogic Server domain on which you will deploy PCC.

Installing Oracle WebLogic Server

Oracle WebLogic Server is available as a component of the Oracle Fusion Middleware software. For more information on supported versions, see BRM Compatibility Matrix.

Download Oracle WebLogic Server from the Oracle software delivery website:

http://edelivery.oracle.com

For information on installing Oracle WebLogic Server, see the Oracle WebLogic Server documentation.

Installing and Configuring Oracle Application Development Runtime

Oracle Application Development Runtime must be installed on the computer on which you install PCC. You can download Oracle Application Development Runtime from the Oracle software delivery website:

http://edelivery.oracle.com

For information on installing Oracle Application Development Runtime, see the Oracle Application Development Runtime documentation.

Note:

The Oracle Fusion Middleware Application Developer installer installs both Oracle Application Development Runtime and Oracle Enterprise Manager.

See Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework for more information on Application Development Framework.

Creating an Oracle WebLogic Server Domain

To create a domain on which to deploy PCC, see the Oracle WebLogic Server documentation.

You must create the domain with at least one managed server and one administration server. Oracle recommends that you deploy PCC on a managed server in a production environment.

Table 9-2 shows the values to choose when creating the domain for PCC.

Table 9-2 Oracle WebLogic Server Domain Configuration Values

Configuration Value	Description
Domain Source	Select Generate a domain configured automatically to support the following BEA products. From the list, select Oracle JRF - 12.2.1 [oracle_common].
Domain Mode Configuration	Select Production Mode.
Optional Configuration	Select Administration Server, Managed Servers, Clusters and Machines and Deployments and Services.
Administration Server Listen Address	Use a listen address that is equal to a resolvable DNS host or IP address. Do not use localhost or 127.0.0.1. Those addresses interfere with clustered servers.
Managed Server Listen Address	Enter a listen address that is equal to a resolvable DNS host or IP address.
Target Deployments to Clusters or Servers	Add all libraries to both the managed server target and the Administration Server.
Target Services to Clusters or Servers	Add all services to the managed server target.

See Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite for more information on Oracle WebLogic Server domains.

You can now start the domain administration server manually and log in to WebLogic Server Administration Console.

Configuring SSL for the Oracle WebLogic Server Domain

To enable secure communication for PCC, you must configure secure socket layer (SSL) for the domain on which you want to deploy PCC.

To configure SSL for the domain:

Generate the server-side keystore file using the keytool utility.

See the Key and Certificate Management Tool online documentation for more information.
Export the public certificate from the server-side keystore file using the keytool utility.

See the Key and Certificate Management Tool online documentation for more information.
Generate the client-side keystore file from the exported public certificate using the keytool utility.

See the Key and Certificate Management Tool online documentation for more information.

Note:

Note the path of the client-side keystore file. You must provide this path during the PCC installation if you choose to use SSL.
In WebLogic Server Administration Console, configure SSL for the domain managed server on which you want to deploy PCC.

See the Oracle WebLogic Server Administration Console Help for more information.

Setting the JAVA_HOME Environment Variable

You must set the JAVA_HOME environment variable to the latest version of JRE/JDK 1.8 on the machine on which you want to deploy PCC and for the WebLogic Server domain.

To set the JAVA_HOME environment variable on the machine on which you want to deploy PCC:

On the machine on which you want to deploy PCC, set the JAVA_HOME environment variable to the directory in which JRE/JDK 1.8 is installed.

See "Software Requirements" for the supported JDK 1.8 version.
Verify the Java version by running the following command:
```
$JAVA_HOME/bin/java -version
```
The Java version is displayed.

If the version displayed does not start with 1.8.0_, the update was not successful.

To set the JAVA_HOME environment variable for the WebLogic Server domain:

On the machine on which Oracle WebLogic Server is installed, go to the WebLogic_home/user_projects/domains/Domain_Name/bin directory.

where:
- WebLogic_home is the directory in which you installed the WebLogic Server.
- Domain_Name is the domain directory in which PCC will be deployed.
Open the setDomain.sh file in a text editor.
Add or modify the following entries before the EXTRA_JAVA_PROPERTIES entry:
```
JAVA_HOME="${JAVA_HOME}"
export JAVA_HOME
```
Save and close the file.
Restart Oracle WebLogic Server. See the Oracle WebLogic Server documentation for more information.
Verify the Java version used by Oracle WebLogic Server. The Java version is displayed when the WebLogic server is started.

If the version displayed does not start with 1.8.0_, the update was not successful. See the Oracle WebLogic Server documentation for more information.

Obtaining the Oracle JDBC Driver File

Obtain the Oracle JDBC driver file (ojdbc8.jar) and save it in a directory on the machine on which you want to install PCC. Note the path to this directory, because you are required to specify this path in the Specify Prerequisite Libraries Location screen during PCC installation.

You can download the ojdbc8.jar file from the following location:

https://www.oracle.com/database/technologies/appdev/jdbc.html

Installing and Configuring BRM

To install and configure BRM:

Install BRM. See "Installing BRM" for more information.
Set the PriceDesignCenterInst business parameter. See "Setting Up the Business Parameter" for more information.

Setting Up the Business Parameter

To use PCC with PDC, you must set up the PriceDesignCenterInst business parameter.

To set up PriceDesignCenterInst:

Go to BRM_home/sys/data/config and run the following command, which creates an editable XML file from the pricing instance of the /config/business_params object.
```
pin_bus_params -r BusParamsPricing bus_params_pricing.xml
```
This directory includes the support files used by the pin_bus_params utility.

This command creates the XML file named bus_params_pricing.xml.out in your working directory. If you do not want this file in your working directory, specify the path as part of the file name.
Search for the following line in the XML file:
```
<PriceDesignCenterInst>disabled</PriceDesignCenterInst>
```
By default, PriceDesignCenterInst is set to disabled.
Change disabled to enabled.
Save the file as bus_params_pricing.xml.
Use the following command to load this updated file into the /config/business_params object:
```
pin_bus_params bus_params_pricing.xml
```
Read the object with the testnap utility or Object Browser to verify that all fields are correct.

Downloading the PCC Software

You can download and install full versions of the PCC 12.0 or PCC 12.0 Patch Set software.

Note:

If you install a BRM 12.0 Patch Set, you must install the same version of the PCC 12.0 Patch Set.

To download the PCC package, go to the Oracle support website (https://support.oracle.com). Search for and download the Oracle Communications Billing and Revenue Management 12.0.0.x.0 software, where x is 1 for Patch Set 1, 2 for Patch Set 2, and so on.

Unzip the pPatchNumber_12.0.0.x.0_Generic.zip file. The Zip archive includes the PipelineConfigurationCenter_12.0.0.x.0_generic.jar file for installing PCC.

Installing PCC

Before installing PCC, read the following:

You can install PCC in the following modes:

GUI mode: Use GUI mode when you want to interact with the PCC installer GUI during installation. See "Installing PCC in GUI Mode".
Silent mode: Use silent mode when you install PCC using the same configuration repeatedly. Silent install mode does not use the GUI, and it runs in the background. See "Installing PCC in Silent Mode".

The PCC installer must be launched from the computer hosting the Oracle WebLogic Server domain. PCC installation must be performed by the user who has permissions to write to the Oracle Inventory (oraInventory) directory and the WebLogic_home/user_projects/domains directory, where WebLogic_home is the directory in which you installed the WebLogic Server.

For more information about the oraInventory directory, see the Oracle documentation:

http://docs.oracle.com

Installing PCC in GUI Mode

Note:

To perform a GUI installation, install a GUI application, such as X Windows, and set the DISPLAY environment variable before you install PCC.

To install PCC in GUI mode:

Ensure that the Pipeline Manager database server is running.
Start the Oracle WebLogic Server domain administration server and managed server on which you want to deploy PCC.
Obtain the PCC software. See "Downloading the PCC Software".
Go to the temp_dir directory, and run one of the following commands:
- To start the GUI installer:
```
Java_home/bin/java -jar PipelineConfigurationCenter_12.0.0.v.0_generic.jar
```
  where:
  - Java_home is the directory in which you installed the latest supported Java version.
  - v is the PCC version. For example, 0 is the version for PCC 12.0 and 1 is the version for PCC 12.0 Patch Set 1.
- To start the GUI installer and install PCC in the oraInventory directory in a different location:
```
Java_home/bin/java -jar jar_file -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 jar_file -record -destinationFile path
```
  where path is the absolute path to the response file.
In the Welcome screen, click Next.
If the oraInst.loc file is corrupt or not present, the Specify Inventory Directory and Credentials screen appears. 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:
1. Enter the full path of the inventory directory.
2. Specify the name of the operating system group that has write permission to the inventory directory.
3. Click Next.
In the Installation Location screen, enter the full path or browse to the directory in which to install PCC. Click Next.
In the Feature Sets Selection screen, select Pipeline Configuration Center and then click Next.
In the Prerequisite Libraries Location screen, enter the full path or browse to the directory in which the ojdbc8.jar file is located. Click Next.

In the WebLogic Server Details screen, enter the details listed in Table 9-3 for the domain on which you want to deploy PCC. Click Next.

Table 9-3 WebLogic Server Details Screen

Field Name	Description
Host Name	Enter the IP address or the host name of the computer on which the domain is configured.
Port Number	Enter the port number assigned to the domain administration server.
Username	Enter the domain administrator user name.
Password	Enter the password for the domain administrator user.
WebLogic Home	Enter the path of the directory where the Oracle WebLogic Server software is installed. Caution! The PCC installer does not proceed until it verifies with the running instance of Oracle WebLogic Server that the domain administration server information you entered is valid.
Use SSL?	Do one of the following: If the server does not support SSL, deselect the Use SSL? check box. If the server supports SSL, leave the Use SSL? check box selected. When the check box is selected, the Keystore Type, Keystore Location, and Keystore Password fields are mandatory. See "Configuring SSL for the Oracle WebLogic Server Domain" for more information.
Keystore Type	Select the KeyStore certificate type: PKCS12 or JKS.
Keystore Location	Enter or browse to the directory of your client-side KeyStore certificate file, which was generated from the exported public certificate using the keytool utility.
Keystore Password	Enter the password for the KeyStore file.

In the Target Server screen, select the domain administration server or managed server on which you want to deploy PCC. Click Next.

Note:

Oracle recommends deploying PCC on a managed server. If you select a managed server, ensure that the managed server and the node manager are running.

In the Pipeline Manager Database Connection screen, enter the details listed in Table 9-4 for connecting to the Pipeline Manager database. Click Next.

Table 9-4 Pipeline Manager Database Connection Screen

Field Name	Description
Host Name	Enter the IP address or the host name of the computer on which the Pipeline Manager database is configured.
Port Number	Enter the port number assigned to the Pipeline Manager database service.
User Name	Enter the user name of the Pipeline Manager database user.
Password	Enter the password of the Pipeline Manager database user.
Service Name	Enter the name of the Pipeline Manager database service. Caution! The PCC installer will not proceed until it verifies with the running instance of the Pipeline Manager database server that the database information you entered is valid.
SSL Enabled	Select the type of connection required to connect to the database: Yes-One Way: One-way SSL authentication is required. Yes-Two Way: Two-way SSL authentication is required. No: SSL authentication is not required.
Store Type	Select the type of TrustStore and KeyStore file that is used for the SSL connection: SSO or PKCS12.
Truststore Location	Enter or browse to the directory in which your TrustStore file is located. This file is used for authentication through SSL.
Truststore Password	Enter the password required to access the certificates from the TrustStore.
Keystore Location	Enter or browse to the directory in which your KeyStore file is located. This file is used for authentication through SSL.
Keystore Password	Enter the password required to access the certificates from the KeyStore.

In the BRM Connection Details screen, enter the details listed in Table 9-5 for connecting to the BRM server. Click Next.

Table 9-5 BRM Connection Details Screen

Field Name	Description
User Name	Enter the user name for connecting to BRM.
Password	Enter the BRM user's password.
Host Name	Enter the IP address or the host name of the machine on which the primary BRM Connection Manager (CM) or CM Master Process (CMMP) are running.
Port Number	Enter the TCP port number of the CM or CMMP on the host computer. The default value is 11960.
Service Type	Enter the BRM service type. The default value is /servide/admin_client.
Service POID ID	Enter the POID of the BRM service. The default value is 1.
Use SSL?	Do one of the following: If you have not enabled SSL for BRM, deselect the Use SSL? check box. If you have enabled SSL for BRM, leave the Use SSL? check box selected.
Wallet Password	Enter the password for the PCC wallet.
Confirm Wallet Password	(PCC 12.0 Patch Set 1 Installation only) Enter the password for the PCC wallet again.

In the Pipeline Configuration Center User screen, enter the details listed in Table 9-6 for creating a PCC user. Click Next.

Note:

Entering information in this screen is optional. You do not have to create a PCC user now.

Table 9-6 Pipeline Configuration Center User Screen

Field Name	Description
Username	Enter the name for the PCC user.
Password	Enter a password for the PCC user. Note: The PCC user password can contain up to 12 characters and should contain at least one nonalphabetic character. In addition, the user name must not be a part of the password.
Confirm Password	Enter the password again.

Field Name

Description

Username

Enter the name for the PCC user.

Password

Enter a password for the PCC user.

Note: The PCC user password can contain up to 12 characters and should contain at least one nonalphabetic character. In addition, the user name must not be a part of the password.

Confirm Password

Enter the password again.

In the Installation Summary screen, review the selections you made in the preceding screens, and then click Install.
The Installation Progress screen appears. When installation completes, click Next.

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 Installation Complete screen appears. Make note of the PCC URL. You use this URL to access PCC.
Note:

If the server supports SSL, the secure connection is established for PCC even if you deselect the Use SSL? check box in the WebLogic Administration Server Connection screen. In this case, two connection URLs are displayed:
- A secured connection URL with SSL listen port and the HTTPS schema
- An unsecured connection URL with the HTTP schema
Click Finish.

The PCC installer exits.

If you did not create a PCC user during installation, you must create one after the installation is complete. See "PCC Post-Installation Tasks".

See "Verifying the PCC Installation" for information on verifying the successful installation of PCC.

See "About Installation Logs" for information on PCC installer logs.

Installing PCC in Silent Mode

Silent-mode installation enables you to set installation configurations only once and then use those configurations to duplicate the installation on many machines. In this mode, you use a response file template that contains a predefined set of values to install PCC.

Note:

The silent installation is not meant for production environments, and it should be used in test environments only for setting up quickly or backing up the properties for later use in another test environment.

About the Response File Template

The PCC installer includes a response file template, temp_dir/pcc/Disk1/stage/Response/oracle.communications.pcc.Complete.rsp, where temp_dir is the directory in which you unzipped the PCC software.

This response file template contains all the parameters that the PCC installer requires during the silent, unattended installation, but it does not contain the parameter values. You must update the response file template per your installation requirements before starting the silent installation.

Creating a Response File

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 PCC" 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 PipelineConfigurationCenter_12.0.0.v.0_generic.jar -getResponseFileTemplates
```
  where:
  - Java_home is the directory in which you installed the latest supported Java version.
  - v is the PCC version. For example, 0 is the version for PCC 12.0 and 1 is the version for PCC 12.0 Patch Set 1.
  A response file is created with the default values.
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 PCC installer treats incorrect context, format, and type values in a response file as if no value were specified.
Save and close the response file.

Installing PCC in Silent Mode

To install PCC in silent mode:

Create a response file. See "Creating a Response File".
Copy the response file you created 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, and run the following command:
```
Java_home/bin/java -jar PipelineConfigurationCenter_12.0.0.v.0_generic.jar -debug -invPtrLoc Inventory_home/oraInventory/oraInst.loc [parameter=value] -responseFile path -silent
```
where:
- v is the PCC version. For example, 0 is the version for PCC 12.0 and 1 is the version for PCC 12.0 Patch Set 1.
- path is the absolute path to the response file.
- parameter is the name of an installation parameter.
- value is the value of the installation parameter.
For example:
```
Java_home/bin/java -jar PipelineConfigurationCenter_12.0.0.1.0_generic.jar -debug -invPtrLoc Inventory_home/oraInventory/oraInst.loc INSTALL_TYPE=Complete -responseFile /response_files/myresponsefile.rsp  -silent
```
The installation runs silently in the background.
Open the PCC_Home/install/readme.txt file, where PCC_Home is the directory in which you installed PCC.
Copy the URL and paste it in your browser's address field.

You can now access the PCC application.

See "Verifying the PCC Installation" for information on how to verify that the PCC installation was successful.

See "About Installation Logs" for information on the PCC installer logs.

About Installation Logs

The PCC Installer logs can be found in the oraInventory/logs directory.

Use the following log files to monitor installations and post-installations:

installActionTimeStamp.log
oraInstallTimeStamp.err
oraInstallTimeStamp.out
silentInstallTimeStamp.log (for silent mode installation)

where TimeStamp is the date and time the log file was created.

PCC Post-Installation Tasks

After you install PCC, perform the following post-installation tasks:

Creating a PCC User after Installing PCC

During the PCC installation, the installer creates the Config Admin Oracle WebLogic Server group. Users belonging to this group have read and write access to perform all the tasks in PCC.

You can create a PCC user during or after the installation. When you create a user during the installation, the installer automatically adds it to the Config Admin group.

To create a PCC user after installing PCC, use WebLogic Server Administration Console to create a user and to add the user to the Config Admin group.

Note:

Do not use your browser's remember password feature for the WebLogic Server Administration Console URL. As a precaution, always enter the WebLogic server user name and password manually.

To create a PCC user after installing PCC:

Log in to WebLogic Server Administration Console.
In the Domain Structure panel, click the Security Realms link.

The Summary of Security Realms page appears.
Click the myrealm link.

The Settings for myrealm page appears.
Click the Users and Groups tab.
Click the Users subtab.
Click New.

The Create a New User page appears.
Do the following:
1. In the Name field, enter a name for the PCC user.
2. (Optional) In the Description field, enter a brief description for the PCC user.
3. In the Password field, enter a password for the PCC user.
  
  Note:
  
  The PCC user password can contain up to 12 characters and should contain at least one nonalphabetic character. In addition, the user name must not be a part of the password.
4. In the Confirm Password field, enter the password again to confirm it.
Click OK.

The user name appears in the User table.
Click the user link, where user is the PCC user that you created.

The Settings for user page appears.
Click the Groups tab.
In the Parent Groups section's Available list, select Config Admin.
Move Config Admin to the Chosen list.
Click Save.

Configuring a Connection from PCC to BRM

After the PCC installation is complete, configure a connection from PCC to BRM.

To configure a connection from PCC to BRM:

Open the PCC_Home/plan/AppFileOverrides/PCCView.war/Infranet.properties file, where PCC_Home is the directory in which you installed PCC.

Note:

As a backup, a copy of the Infranet.properties file might also be in the location specified in the HOME environment variable of the operating system user who starts WebLogic Server. In this situation, you must configure the connection in both instances of the file.
Search for the infranet.connection entry.
Edit the infranet.connection entry as follows:
```
infranet.connection=pcp://username:password@hostname:port/service 1
```
where:
- username is the login name to use for connecting to BRM. You can use any valid CSR login name.
- password is the password for username.
- hostname is the name or IP address of the computer running the primary Connection Manager (CM) or CM Master Process (CMMP).
- port is the TCP port number of the CM or CMMP on the host computer. The port number must match the corresponding cm_ports entry in the primary CM or CMMP configuration file.
- service is the service type. The trailing 1 is the POID of the service.
Save and close the file.
Log in to WebLogic Server Administration Console for the PCC domain, and do the following:
1. In the Domain Structure panel, click Deployments.
  
  The Summary of Deployments page appears.
2. In the Deployments table, select the PipelineConfigurationCenter check box.
3. Click Update.
  
  The Update Application Assistant starts.
4. Select the Update this application in place with new deployment plan changes option.
5. Set Deployment plan path to the location of the Infranet.properties file. Use the Change Path button to browse to the file.
6. Click Next, and review your choices.
7. Click Finish.
8. Restart WebLogic Server.
See the Oracle WebLogic Server Administration Console Help for more information about the console.
Secure the BRM connection information as follows:
- Encrypt the password by using the pin_crypt_app utility. See "About Encrypting Passwords" in BRM Developer's Guide.
- Set the Infranet.properties file permissions to permit only specified system administrators to access the file.

Using Secure Cookies

Oracle recommends deploying PCC only on SSL, which encrypts sensitive data, thus eliminating problems like session stealing.

WebLogic Server enables a user to securely access HTTPS resources in a session that was initiated using HTTP, without loss of session data.

To use secure cookies:

Open the WebLogic_home/user_projects/domains/Domain_Name/config/config.xml file.

where:
- WebLogic_home is the directory in which you installed WebLogic Server.
- Domain_Name is the name of the domain you are configuring.

Add AuthCookieEnabled="true" to the <WebServer> element:

<WebServer Name="myserver" AuthCookieEnabled="true"/>.

Note:

By default, AuthCookieEnabled is set to true. The secured cookies are enabled by default even if the config.xml file does not contain this entry. You can set AuthCookieEnabled to false to disable secured cookies. However, Oracle recommends not disabling it.

You can also set this entry by using WebLogic Server Administration Console:

Log in to WebLogic Server Administration Console.

The home page appears.
In the Domain Configurations section, under Domain, click Domain.

The Settings for Domain_Name page appears.
Click the Web Applications tab.
Verify that the Auth Cookie Enabled check box is selected.
Click Save.

By default, the Auth Cookie Enabled check box is selected, but it is not present in the config.xml file. If you deselect it, the <AuthCookieEnabled> element is added to the config.xml file.

Setting AuthCookieEnabled to true, the default setting, causes the WebLogic Server instance to send a new secure cookie, _WL_AUTHCOOKIE_JSESSIONID, to the browser when authenticating through an HTTPS connection. After the secure cookie is set, the session is allowed to access other security-constrained HTTPS resources only if the cookie is sent from the browser.

For more information, see the discussion about using secure cookies to prevent session stealing in Oracle Fusion Middleware Developing Applications with the WebLogic Security Service.

Oracle recommends keeping cookie settings enabled in the browser. Disabling cookies in the browser disables several features, such as Help.

Configuring the Session Timeout

The default session timeout in PCC is 600 seconds. The WebLogic Server administrator can change this value as follows:

Log in to WebLogic Server Administration Console.
In the Domain Structure panel, click Deployments.

The Summary of Deployments page appears.
In the Deployments table, click PipelineConfigurationCenter.

The Settings for PipelineConfigurationCenter page appears.
Click the Configuration tab.
In the Session Timeout (in seconds) field, enter a new timeout value in seconds.
Click the Overview tab.
In the Modules and Components table, click PCC-PCCViewController-context-root.
Click the Configuration tab.
In the Session Timeout (in seconds) field, enter the same timeout value, in seconds, that you entered in step 5.
Click Save.

If no deployment plan is created, WebLogic Server creates one with the preceding changes and prompts you to save the deployment plan. Provide the name and path for the deployment plan, and click OK.
In the Domain Structure panel, click Deployments.
Select the PipelineConfigurationCenter check box.
Click Update.

The Update Application Assistant starts.
Select the Update this application in place with new deployment plan changes option.
Set Deployment plan path to the deployment plan created in step 10. Use the Change Path button to browse to the file.
Click Next.
Click Finish.
Restart WebLogic Server.
Verify your changes by doing the following:
1. Log in to WebLogic Server Administration Console.
2. In the Domain Structure panel, click Deployments.
3. Click PipelineConfigurationCenter.
  
  The Settings for PipelineConfigurationCenter page appears.
4. Click the Configuration tab.
5. Verify that Session Timeout (in seconds) is set to the value you specified.

For more information, see the discussion about configuring applications for production deployment in Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server.

Verifying the PCC Installation

Verify whether PCC was installed successfully by doing the following:

Checking the State of All Installed Components

You can verify that PCC is installed correctly by checking the state of all installed components.

To check the state of all installed components:

Log in to the PCC domain in WebLogic Server Administration Console.
In the Domain Structure panel, click Deployments.

The Summary of Deployments page appears.
In the Control tab, if PCC is installed correctly, the deployed PipelineConfigurationCenter application appears in the Active state.

Logging In to PCC

You can log in to PCC to verify that PCC is installed.

To log in to PCC:

Open a browser window.
Enter the URL provided by the PCC installer at the end of the installation into the browser's address field.

Note:

The URL to access PCC is also available in the PCC_Home/install/readme.txt file, where PCC_Home is the directory in which you installed PCC.
Press Enter.

The PCC login page appears.
Do the following:
1. In the Username field, enter the user name.
2. In the Password field, enter the password.
Click Login.

The PCC home page appears, verifying that PCC is successfully installed.

About File Permissions

The following default permissions are set for the installed files:
- rw------- 600 (for all nonexecutable files)
- rwx------ 700 (for all executable files)
Permissions are set to the lowest possible level, and the WebLogic Server administrator can add or revoke permissions. Oracle recommends keeping the permissions as restrictive as possible.
Protect the WebLogic configuration (JMS, JDBC, and so on) file, config.xml, in the domain's config directory with proper permissions.

Verifying Configuration Entries

The installer stores the configuration entries in the PCC wallet. These entries are used to control the connections from Java applications to BRM.

After PCC has been installed on each machine, check the configuration entries stored in the PCC wallet. You can verify the entries by doing the following:

Note:

If PCC and the BRM server are installed on separate machines, copy the PCC wallet to the machine in which the BRM server is installed and perform the following procedure on the machine in which the BRM server is installed.

Go to the directory in which you installed PCC, and source the source.me file:

Bash shell:
```
source source.me.sh
```
C shell:
```
source source.me.csh
```
Run the following command:
```
orapki wallet display -wallet PCC_Wallet_Path
```
where PCC_Wallet_Path is the path to the PCC wallet.

The entries stored in the client wallet appear.

If the entries do not appear, you must store the entries manually in the PCC wallet by using the pin_crypt_app utility.

To secure this connection information, encrypt the password by using the pin_crypt_app utility. See "About Encrypting Passwords" in BRM Developer's Guide.

Uninstalling PCC

Note:

After uninstalling PCC, you must manually undeploy the PCC application deployed on the WebLogic server domain. See the discussion about undeploying applications in the Oracle WebLogic Server documentation.

To uninstall PCC:

Go to the PCC_home/oui/bin directory.
Run the following command from a GUI (for example, VNC server):
```
./deinstall.sh
```
The Distribution to Uninstall screen appears.
Select the components you want to uninstall.
Click Uninstall.

The Welcome screen appears.
Click Next.

The Uninstallation Summary screen appears.
Click Uninstall.

The Uninstallation Progress screen appears.
Click Next.

The Uninstallation Complete screen appears.
Click Finish.

The PCC installer removes all files except log files. You must delete the log files manually. The log files are in the oraInventory/logs directory.

Uninstalling PCC in Silent Mode

To uninstall PCC in silent mode:

Go to the PCC_home/oui/bin directory.
Run the following command:
```
./deinstall.sh -responseFile path -silent
```
where path is the absolute path to the response file.

A message indicating that PCC has been uninstalled successfully appears.

Deleting Files after Uninstalling PCC

The following files remain in the system after PCC is uninstalled:

Install logs

The log files are in the oraInventory/logs directory.
PCC_home/oui/data.properties

This file is used to auto-populate the data during reinstalls.

Delete these files manually if you do not need them, or protect them appropriately if they are required for further installations.

By default, these files are created with the file-level permission 640 (owner can read/write; group members can read; others cannot do anything).

Administering PCC

A PCC administrator is responsible for the day-to-day tasks of maintaining and managing PCC and its users. You perform the following tasks as a PCC administrator:

Managing PCC Security

Oracle WebLogic Server includes a security architecture that provides a secure foundation for applications. PCC depends on the WebLogic Server security framework to secure its resources and servers. Managing PCC security involves the following:

Managing security realms: Configuring new security realms, changing the default security realm, and deleting security realms
Managing users and groups: Defining users and assigning them to a group that can be authenticated in a security realm
Managing security providers: Managing security providers that provide security services to applications to protect WebLogic Server resources

See the Oracle WebLogic Server Administration Console Help for more information on managing security realms, managing users and groups, and managing security providers.

Monitoring PCC

Regularly monitoring your system ensures fast recognition and resolution of problems or issues. You can use WebLogic Server Administration Console to monitor the following:

PCC domain
PCC administration server and managed servers

See the Oracle WebLogic Server Administration Console Help for more information.

Managing PCC

You manage PCC by managing the WebLogic server on which PCC is installed. This includes starting and stopping the PCC administration server and managed servers.

See the Oracle WebLogic Server Administration Console Help for more information.

Troubleshooting PCC

Although PCC installation is designed to be trouble free, you might encounter a problem. You can troubleshoot PCC installation problems by using log files, diagnosing common problems, and contacting Oracle support.

Troubleshooting Checklist

When problems occur, it is best to do some troubleshooting before you contact Oracle support:

You know your installation better than Oracle support does. You know whether anything in the system has been changed, so you are more likely to know where to look first.
Troubleshooting skills are important. Relying on Oracle support to research and solve all your problems prevents you from being in full control of your system.

If you have a problem with your PCC system, ask yourself the following questions because Oracle support will ask them:

What exactly is the problem? Can you isolate it?

Oracle support needs a clear and concise description of the problem, including when it began to occur.
What do the log files say?

This is the first thing that Oracle support asks for. Check the error log for the PCC component you are having problems with.
Has anything changed in the system? Did you install any new hardware or new software? Did the network change in any way? Does the problem resemble another one you had previously? Has your system usage recently jumped significantly?
Is the system otherwise operating normally? Has response time or the level of system resources changed? Are users complaining about additional or different problems?

Using Error Logs to Troubleshoot PCC

PCC error log files provide detailed information about system problems. If you are having a problem with PCC, look in the log files.

PCC records information about actions performed in the PCC GUI in Oracle WebLogic Server log files. See the Oracle WebLogic Server Administration Console Help for more information.

Diagnosing PCC Problems

PCC problems can be diagnosed using the Oracle WebLogic Server Diagnostic Framework, which enables you to collect, archive, and access diagnostic information about applications hosted on the WebLogic server. See the Oracle WebLogic Server Administration Console Help for more information.

This section lists some common PCC problems and describes how to diagnose the error messages and resolve the problems.

Refreshing the Browser

Do not refresh your browser.

Refreshing the browser causes unpredictable problems in PCC.

Unable to Perform Any Task after Logging In

After you log in to PCC, the links in the navigation pane are not displayed, and you cannot perform any task.

This means that you are not in the Config Admin WebLogic Server group. Contact your system administrator, and request to be added to that group.

Getting Help for PCC Problems

If you cannot resolve a PCC problem, contact Oracle support.

Before you contact Oracle support, try to resolve the problem with the information in the log files. See "Using Error Logs to Troubleshoot PCC" for more information. If this does not help resolve the problem, gather the following information:

A clear and concise description of the problem, including when it began to occur.
Relevant portions of the relevant log files.
Relevant configuration files.
Recent changes in your system after which the problem occurred, even if you do not think they are relevant.
A list of all PCC components and patches installed on your system.

When you are ready, report the problem to Oracle support.

Secure Deployment Checklist

To deploy PCC securely, follow this checklist:

Pre-installation steps:
1. Enable SSL for the target Oracle WebLogic Server domain.
2. Configure the server KeyStore certificate, and get the client KeyStore trusted certificate.
3. Configure Oracle Database advanced security encryption and integrity algorithms for a secure connection from the installer.
4. Verify that you have JDK 1.8 with the latest security update installed and configured with your PCC/WebLogic Server installation.
Installation steps:
1. Select the SSL mode, select the KeyStore type, and provide the client KeyStore certificate (.p12 [recommended] or .jks file) for connecting to a WebLogic server over SSL.
Post-installation steps:
1. If you do not need the installation log files, delete them.
2. The WebLogic Server administrator must create PCC users based on the roles and privileges.
3. Do not use your browser's remember password feature for the WebLogic Server Administration Console URL.
4. Enable secure cookies.
5. Verify that file permissions for the installed files are 600 for all nonexecutable files and 700 for all executable files.
Un-installation steps:
1. Delete the log files in the oraInventory/logs directory manually if you do not need them, or protect them appropriately if they are required for further installations.