Installing Business Operations Center

5 Installing Business Operations Center

Learn how to install Oracle Communications Billing and Revenue Management (BRM) Business Operations Center using a GUI installer or a silent, command-line installer.

Topics in this document:

Downloading the Business Operations Center Installer

You can download the Business Operations Center software from one of the following locations:

For Business Operations Center 15.0.0 or any 15.0.x maintenance release: From the Oracle software delivery website (https://edelivery.oracle.com)
For any 15.0.x.y patch set release: From the Oracle support website (https://support.oracle.com)

Search for and download the Oracle Communications Billing and Revenue Management 15.0.x.y.0 software, where x refers to the maintenance release and y refers to the patch set release of Business Operations Center that you are installing.

The Zip archive includes the installer: BusinessOperationsCenter_generic.jar.

Installing Business Operations Center for Testing

Business Operations Center test installations do not use Oracle Identity Management (IDM) security. The installer deploys the application to a basic Oracle WebLogic domain with Business Operations Center authorization disabled. Use test installations for internal development and testing only.

To install a Business Operations Center test installation in a basic domain:

Verify that your Java Development Kit is installed correctly, including setting your JAVA_HOME environment variable and confirming that the Java_home/bin directory is in your path.
Start the Oracle WebLogic Server basic domain administration server, managed server, or cluster on which you want to deploy Business Operations Center.
Run the following command, which launches the Business Operations Center installer:
```
java -jar BusinessOperationsCenter_generic.jar
```
Note:
- Specify the -invPtrLoc flag and an Oracle Inventory path location in the Java command for launching the Business Operations Center installer if you are using an existing or custom Oracle inventory location for maintaining your installed Oracle products and installation logs.
- Business Operations Center requires postinstallation configuration of an Oracle WebLogic Server data source. By default, the installer uses the value bocdb for this data source's name. To use a custom data source name, specify the name by passing the following flag when launching the installer:
  
  DS_NAME="new_value"
  
  For example:
```
java -jar BusinessOperationsCenter_generic.jar DS_NAME=''name'' 
```
  where name is the name of the WebLogic Server data source.
  
  See "Creating the Business Operations Center WebLogic Server Data Source" for more information on configuring the WebLogic data source after installation completes.
In the Welcome window, click Next.
In the Installation Inventory window, select an Inventory Directory and Operating System Group and then click Next.
In the Installation Location window, enter or browse to your Oracle Home directory and then click Next.
In the Feature Sets Selection window, select Business Operation Center Components and then click Next.
In the Prerequisite Libraries Location window, enter the full path or browse to the directory in which the ojdbc8.jar file is stored, and then click Next.

In the WebLogic Server Details window, enter the details listed in Table 5-1 for the WebLogic Server domain in which you want to deploy Business Operations Center, and then click Next.

Table 5-1 WebLogic Server Details

Field	Description
Host Name	IP address or the host name of the computer on which the WebLogic Server domain is configured.
Port Number	Port number assigned to the WebLogic Server domain administration server.
User Name	WebLogic Server domain administrator user name.
Password	Password for the WebLogic Server domain administrator user.
WebLogic Home	Path of the directory in which the WebLogic Server software is installed.
Use SSL?	Whether to use SSL. Deselect the checkbox for test installations.
KeyStore Type	The type of KeyStore file used in the WebLogic domain for SSL: JKS or PKCS12.
KeyStore Location	The path to your KeyStore file, which is used for authentication through SSL.
KeyStore Password	The password required to access the certificates from the KeyStore.

Note:

The Business Operations Center installer will not proceed until it verifies that the information you entered is valid. The domain must be in a RUNNING state.

In the Target Server window, select the server on which to deploy Business Operations Center and then click Next.

The target server list includes the administration server, any managed servers, and any clusters. For example, the target list might include:
- admin-server:RUNNING
- managed-server1:RUNNING
- managed-server2:RUNNING
- managed-server3:SHUTDOWN
- cluster-1:RUNNING
In this example, cluster-1 is formed by managed-server1, managed-server2, and managed-server3.
Note:
- You can deploy Business Operations Center on managed servers that are in an offline state.
- When a cluster is selected as the target, all managed servers in the cluster are targets.
- Oracle recommends that you deploy Business Operations Center on a WebLogic Server managed server or cluster. If you select a WebLogic Server managed server, ensure that the WebLogic Server managed server and the node manager are running.
- If you deploy Business Operations Center on a WebLogic Cluster, you must enable sticky sessions in your load balancer.
A warning appears confirming that the domain is not configured as an Oracle Platform Security Services (OPSS) Oracle Java Required Files (JRF)-enabled Domain.
In the Authentication and Asserter window, select Skip Authenticator and Asserter. A warning appears confirming that the Authenticator and Asserter will not be configured. Click OK and then click Next.

In the Database User Details window, enter the details in Table 5-2 and then click Next.

Table 5-2 Database User Details

Field	Description
Host Name	The IP address or the host name of the machine on which the BRM database is installed.
Port Number	The port number assigned to the BRM database. For example: 1521.
Service Name	The database service name. For example: orcl.
User Name	The name of the Business Operations Center database user. For example: boc.
Password	The Business Operations Center user's password.
Confirm Password	Enter the Business Operations Center user's password again.
SSL Enabled	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	The type of TrustStore and KeyStore file that is used for the SSL connection: SSO or PKCS12.
Truststore Location	The directory in which your TrustStore file is located. This file is used for authentication through SSL.
Truststore Password	The password required to access the certificates from the TrustStore.
Keystore Location	The directory in which your KeyStore file is located. This file is used for authentication through SSL.
Keystore Password	The password required to access the certificates from the KeyStore.

The installer checks whether the Business Operations Center database user and Business Operations schema already exist, and then does one of the following:

If the user already exists but the schema does not: The installer will create the Business Operations Center schema. Proceed to step 14.
If both the user and schema already exist: The installer displays a warning. Click OK to have Business Operations Center reuse the existing schema. Proceed to step 14.
If the user does not exist: The installer displays a warning. Click OK to have the installer create the user and schema for you. You will need to provide the database administrator credentials in the next window. Proceed to the next step.

In the Database Administrator Details window, enter the database administrator and tablespace details listed in Table 5-3.

Table 5-3 Database Administrator Details

Field	Description
User Name	The database administrator user name.
Password	The password for the database administrator user.
Role	The role of the database administrator user, such as sysdba.
Default Tablespace	The default tablespace for the Business Operations Center schema.
Temp Tablespace	The temporary tablespace for the Business Operations Center schema.

The installer checks whether the default and temp tablespaces already exist, and then does one of the following:

If they do not exist, the installer displays a warning. Click OK to have the installer create the tablespaces for you.
If they already exist, the installer uses the existing tablespaces.

In the User Interface Details window, enter the user details listed in Table 5-4 and then click Next.

Table 5-4 Business Operations Center User Interface Details

Field	Description
Billing Care URL	The URL of the Billing Care instance configured for use with your BRM Server if installed. Leave blank if Billing Care is not installed in your environment.
Logout URL	The redirect URL where Business Operations Center sends a user after logout and session termination.
Help URL	The URL location of the Business Operations Center Online Help Guide located on the Oracle Help Center.
Timeout Warning Duration	The number of session idle seconds before Business Operations Center displays a timeout warning to a user (default value is 90 seconds).

In the BRM Connection Details window, enter the details listed in Table 5-5 and then click Next.

Table 5-5 BRM Connection Details

Field	Description
User Name	The user name for connecting to BRM.
Password	The BRM user's password.
Host Name	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	The TCP port number of the CM or CMMP on the host computer. The default value is 11960.
Service Type	The BRM service type. The default value is /service/admin_client.
Service POID Id	The POID of the BRM service. The default value is 1.
Use SSL?	Whether to use SSL: 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	The password for the Business Operations Center wallet.
Confirm Wallet Password	Enter the password for the Business Operations Center wallet again.

In the Web Services Details window, enter the details listed in Table 5-6 and then click Next.

Table 5-6 Business Operations Center Web Services Details

Field	Description
BRM Server Timezone	Time Zone (TZ) value of the server operating system on which the BRM is running.

In the Auto Updates window, select an auto update option and then click Next.
In the Installation Summary window, confirm your installation selections and then click Install.

The installation proceeds and runs postinstallation scripts to complete the Business Operations Center installation.

Installing Business Operations Center for Production

For production installations, run the Business Operations Center installer from the computer hosting the OPSS JRF-enabled domain on which you deploy Business Operations Center. The installation must be performed by a user who has permissions to write to the oraInventory directory and the Middleware_home/user_projects/domains directory, where Middleware_home is the directory in which you installed the Oracle Middleware components.

To install Business Operations Center on your OPSS JRF-enabled domain:

Verify that your Java Development Kit is installed correctly, including setting your JAVA_HOME environment variable and confirming that the Java_home/bin directory is in your path.
Start the Oracle WebLogic Server basic domain administration server, managed server, or cluster on which you want to deploy Business Operations Center.
Run the following command, which launches the Business Operations Center installer:
```
java -jar BusinessOperationsCenter_generic.jar
```
Note:

Specify the -invPtrLoc flag and an Oracle Inventory path location in the Java command for launching the Business Operations Center installer if you are using an existing or custom Oracle inventory location for maintaining your installed Oracle products and installation logs.
In the Welcome window, click Next.
In the Installation Inventory window, select an Inventory Directory and Operating System Group, and then click Next.
In the Installation Location window, enter or browse to your Oracle Home directory path and then click Next.
In the Features Sets Selection window, select Business Operation Center Components and then click Next.
In the Prerequisite Libraries Location window, enter the full path or browse to the directory in which the ojdbc8.jar files are stored and then click Next.

In the WebLogic Server Details window, enter the details listed in Table 5-7 for the WebLogic Server domain in which you want to deploy Business Operations Center. Click Next.

Table 5-7 WebLogic Server Details

Field	Description
Host Name	IP address or the host name of the computer on which the WebLogic Server domain is configured.
Port Number	Port number assigned to the WebLogic Server domain administration server.
User Name	WebLogic Server domain administrator user name.
Password	Password for the WebLogic Server domain administrator user.
WebLogic Home	Path of the directory in which the WebLogic Server software is installed.
Use SSL?	Whether to use SSL. Select the check box for production installations.
KeyStore Type	The type of KeyStore file that is used for the SSL connection: JKS or PKCS12.
Keystore Location	The directory in which your KeyStore file is located. This file is used for authentication through SSL.
Keystore Password	The password required to access the certificates from the KeyStore.

Note:

The Business Operations Center installer will not proceed until it verifies that the information you entered is valid. The domain must be in a RUNNING state.

Enter the required SSL information and then click Next.

Business Operations Center requires JSSE-based SSL enabled in your OPSS JRF-enabled domain. For more information, see "Using the JSSE-Based SSL Implementation" in Oracle Fusion Middleware Administering Security for Oracle WebLogic Server.

If you have configured SSL in your OPSS JRF-enabled domain, 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 information about using the Java keytool to generate a key pair and root certificate for your encrypted password and to store the certificate, see:

https://docs.oracle.com/javase/8/docs/technotes/tools/unix/keytool.html

See "Configuring SSL" in Oracle Fusion Middleware Administering Security for Oracle WebLogic Server for more information about using SSL in your domain.
In the Target Server window, select the server on which to deploy Business Operations Center and then click Next.

The target server list includes the administration server, any managed servers, and any clusters. For example, the target list might include:
- admin-server:RUNNING
- managed-server1:RUNNING
- managed-server2:RUNNING
- managed-server3:SHUTDOWN
- cluster-1:RUNNING
In this example, cluster-1 is formed by managed-server1, managed-server2, and managed-server3.
Note:
- You can deploy Business Operations Center on managed servers that are in an offline state.
- When a cluster is selected as the target, all managed servers in the cluster are targets.
- Oracle recommends that you deploy Business Operations Center on a WebLogic Server managed server or cluster. If you select a WebLogic Server managed server, ensure that the WebLogic Server managed server and the node manager are running.
- If you deploy Business Operations Center on a WebLogic Cluster, you must enable sticky sessions in your load balancer.
A warning appears confirming that the domain is not configured as an Oracle Platform Security Services (OPSS) Oracle Java Required Files (JRF)-enabled Domain.

In the Authenticator and Asserter window, do one of the following and then click Next.

If you are not using Oracle Unified Directory, select Skip Authenticator and Asserter. A warning appears confirming that the Authenticator and Asserter will not be configured. Click OK.

Enter the information listed in Table 5-8 for connecting to the Oracle Unified Directory authenticator.

Table 5-8 Authentication and Asserter Details

Field	Description
Provider Name	Oracle Unified Directory Authentication provider you configured in your OPSS JRF-enabled domain administration server.
Host Name	Host name or IP address of the LDAP server.
Port Number	Port number on which the LDAP server is listening.
Admin User Name	Distinguished Name (DN) of the LDAP user that WebLogic Server should use to connect to the LDAP server.
Admin Password	Credential (usually a password) used to connect to the LDAP server.
User Base DN	Base distinguished name (DN) of the tree in the LDAP directory that contains users. For example: `cn=Users,dc=example,dc=com`
Group Base DN	Base distinguished name (DN) of the tree in the LDAP directory that contains groups. For example: `cn=Groups,dc=example,dc=com`
Asserter Name	Name to use during Business Operations Center deployment. A new asserter is created if a OAMIdentityAsserter type does not exist in your OPSS JRF-enabled domain already.

In the Database User Details window, enter the details in Table 5-9 and then click Next.

Table 5-9 Database User Details

Field	Description
Host Name	The IP address or the host name of the machine on which the BRM database is installed.
Port Number	The port number assigned to the BRM database. For example: 1521.
Service Name	The database service name. For example: orcl.
User Name	The name of the Business Operations Center database user. For example: boc.
Password	The Business Operations Center user's password.
Confirm Password	Enter the Business Operations Center user's password again.
SSL Enabled	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	The type of TrustStore and KeyStore file that is used for the SSL connection: SSO or PKCS12.
Truststore Location	The directory in which your TrustStore file is located. This file is used for authentication through SSL.
Truststore Password	The password required to access the certificates from the TrustStore.
Keystore Location	The directory in which your KeyStore file is located. This file is used for authentication through SSL.
Keystore Password	The password required to access the certificates from the KeyStore.

The installer checks whether the Business Operations Center database user and Business Operations schema already exist, and then does one of the following:

If the user already exists but the schema does not: The installer will create the Business Operations Center schema. Proceed to step 15.
If both the user and schema already exist: The installer displays a warning. Click OK to have Business Operations Center reuse the existing schema. Proceed to step 15.
If the user does not exist: The installer displays a warning. Click OK to have the installer create the user and schema for you. You will need to provide the database administrator credentials in the next window. Proceed to the next step.

In the Database Administrator Details window, enter the database administrator and tablespace details listed in Table 5-10.

Table 5-10 Database Administrator Details

Field	Description
User Name	The database administrator user name.
Password	The password for the database administrator user.
Role	The role of the database administrator user, such as sysdba.
Default Tablespace	The default tablespace for the Business Operations Center schema.
Temp Tablespace	The temporary tablespace for the Business Operations Center schema.

The installer checks whether the default and temp tablespaces already exist, and then does one of the following:

If they do not exist, the installer displays a warning. Click OK to have the installer create the tablespaces for you.
If they already exist, the installer uses the existing tablespaces.

In the User Interface Details window, enter the user details listed in Table 5-11 and then click Next.

Table 5-11 User Interface Details

Field	Description
Billing Care URL	URL of the Billing Care instance configured for use with your BRM Server if installed. Leave blank if Billing Care is not installed in your environment.
Logout URL	Redirect URL where Business Operations Center sends a user after logout and session termination.
Help URL	URL location of the Business Operations Center Online Help Guide located on the Oracle Help Center.
Timeout Warning Duration	Number of session idle seconds before Business Operations Center displays a timeout warning to a user (default value is 90 seconds).

In the BRM Connection Details window, enter the BRM server connection details listed in Table 5-12 and then click Next.

Table 5-12 BRM Connection Details

Field	Description
User Name	The user name for connecting to BRM.
Password	The BRM user's password.
Host Name	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	The TCP port number of the CM or CMMP on the host computer.
Service Type	The BRM service type, such as /service/admin_client.
Service POID ID	The POID of the BRM service. The default value is 1.
Use SSL?	Whether to use SSL. SSL is required for production systems.
Wallet Password	The password for the BOC wallet.
Confirm Wallet Password	Enter the password for the BOC wallet again.

In the Web Services Details window, enter the details listed in Table 5-13 and then click Next.

Table 5-13 Web Services Details

Field	Description
BRM Server Timezone	Time Zone (TZ) value of the server operating system on which the BRM is running.

In the Installation Summary window, confirm your installation selections and then click Install.

The installation proceeds and runs post install scripts to complete the Business Operations Center installation.
Click Finish to complete the installation.

See "Business Operations Center Postinstallation Tasks" for required tasks to complete after the Business Operations Center installer exits.

See "Verifying the Business Operations Center Installation" for information on verifying the successful installation of Business Operations Center.

See "About Installation Logs" for information on the Business Operations Center installer logs.

About Installation 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 file.

You use the following log files to monitor the installation and postinstallation process:

installActionTimeStamp.log
oraInstallTimeStamp.err
oraInstallTimeStamp.out
launcherTimeStamp.log

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