This chapter describes how to install Oracle Communications Billing and Revenue Management Business Operations Center. Before installing Business Operations Center, read the following chapters:
Business Operations Center supports test and productions installations. See "Installing Business Operations Center for Testing" for information on test installations and "Installing Business Operations Center for Production" for information on production installations.
To download the Business Operations Center installer:
Create a temporary directory (temp_dir).
Go to the Oracle Software Delivery Cloud:
Sign in with your user name and password.
In the Search by field, enter Oracle Communications Billing and Revenue Management 7.5.0.0.0.
From the Select Platform list, select the required platform.
Click Continue.
The Download Queue list appears.
Click Continue.
The license agreements appear.
Review and accept the terms and click Continue.
The File Download box appears.
Download the Oracle Communications Billing and Revenue Management Server package for your platform and language.
Unzip the zip file.
The server zip archive includes the BusinessOperationsCenter_generic.jar installer.
Business Operations Center test installations do not use Oracle Identity and Access Management (IAM) 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 your Java Development Kit is installed correctly, including setting your JAVA_HOME environment variable and that the JAVA_HOME/bin directory is in your path.
Start the Oracle WebLogic Server basic domain administration server or the managed server on which you want to deploy Business Operations Center.
Download the Business Operations Center installer. See "Downloading Business Operations Center" for more information on how to download the installer
Run the following command, which launches the Business Operations Center installer:
java -jar BusinessOperationCenter_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.Note:
Business Operations Center requires post-installation 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 BusinessOperationCenter_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.
The Welcome screen appears.
Click Next.
The Installation Inventory screen appears. Select an Inventory Directory and Operating System Group.
Click Next.
The Installation Location screen appears. Enter your Oracle Home directory path in Oracle Home or click Browse to select a directory.
Click Next.
The Features Sets Selection screen appears.
This screen displays the installable Business Operations Center components. Select Business Operation Center Components.
Click Next.
The WebLogic Server Details screen appears.
Enter the details listed in Table 5-1 for the WebLogic Server domain in which you want to deploy Business Operations Center:
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 (Unselect for test installations) |
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.Click Next.
The Target Server screen appears.
Select the server on which to deploy Business Operations Center. The target server list includes the AdminServer and any managed servers managed by the AdminServer.
Note:
Oracle recommends that you deploy Business Operations Center 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.
A warning appears confirming that the domain is not configured as an OES Client Domain.
Click OK.
The Target Server screen appears.
Select your target server.
Click Next.
The Authentication and Asserter screen appears.
Select Skip Authenticator and Asserter.
Click Next.
A warning appears confirming that the Authenticator and Asserter will not be configured.
Click OK.
The Database Connection Details screen appears.
Enter the database connection details for your BRM database listed in Table 5-2.
Click Next.
The Business Operation Center User Details screen appears.
Enter the user details for your Business Operations Center administrative user listed in Table 5-3.
Table 5-3 Business Operations Center User Details
Field | Description |
---|---|
User Name |
The user name of your Business Operations Center administrative user |
Password |
The Business Operations Center administrative user's password |
Default Tablespace |
The default tablespace for the administrative user |
Temp Tablespace |
The temp tablespace for the administrative user |
Click Next.
The Business Operation Center User Interface Details screen appears.
Enter the user details for your Business Operations Center user interface listed in Table 5-4.
Table 5-4 Business Operations Center User Interface Details
Field | Description |
---|---|
Billing Care URL |
URL of the Oracle Communications 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). |
Click Next.
The Business Operation Center Web Service Details screen appears.
Enter the web service details listed in Table 5-5.
Table 5-5 Business Operations Center Web Service Details
Field | Description |
---|---|
Passwordless SSH User Name |
User name of passwordless SSH user configured for secure communications between the Business Operations Center host and the BRM Server host. See "Creating a Secure Passwordless User on the BRM Server" for more information. |
BRM Server Timezone |
Time Zone (TZ) value of the server operating system on which the BRM is running. |
Click Next.
The Auto Updates screen appears.
Select an auto update option, then click Next.
The Installation Summary screen appears.
Confirm your installation selections, then click Install.
The installation proceeds and executes post install scripts to complete the Business Operations Center installation.
For production installations, run the Business Operations Center installer from the computer hosting the Oracle Entitlements Server (OES) Client 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 OES Client domain:
Verify your Java Development Kit is installed correctly, including setting your JAVA_HOME environment variable and that the JAVA_HOME/bin directory is in your path.
Start the Oracle WebLogic Server basic domain administration server or the managed server on which you want to deploy Business Operations Center.
Download the Business Operations Center installer. See "Downloading Business Operations Center" for more information on how to download the installer
Run the following command, which launches the Business Operations Center installer:
java -jar BusinessOperationCenter_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.The Welcome screen appears.
Click Next.
The Installation Inventory screen appears. Select an Inventory Directory and Operating System Group.
Click Next.
The Installation Location screen appears. Enter your Oracle Home directory path in Oracle Home or click Browse to select a directory.
Click Next.
The Features Sets Selection screen appears.
This screen displays the installable Business Operations Center components. Select Business Operation Center Components.
Click Next.
The WebLogic Server Details screen appears.
Enter the details listed in Table 5-6 for the WebLogic Server domain in which you want to deploy Business Operations Center:
Table 5-6 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 for production installations) |
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.
Business Operations Center requires JSSE-Based SSL enabled in your OES Client domain. See "Using the JSSE-Based SSL Implementation" in Oracle Fusion Middleware Securing Oracle WebLogic Server for more information on using JSEE-Based SSL.
If you have configured SSL in your OES Client 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 on generating a keypair and root certificate for your encrypted password, and storing the certificate, using the Java keytool utility, see:
https://docs.oracle.com/javase/8/docs/technotes/tools/unix/keytool.html
See "Configuring SSL" in Oracle Fusion Middleware Securing Oracle WebLogic Server for more information on using SSL in your domain.
Click Next.
The Target Server screen appears.
Select the server on which to deploy Business Operations Center. The target server list includes the AdminServer and any managed servers managed by the AdminServer.
Note:
Oracle recommends that you deploy Business Operations Center 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 Authentication and Asserter screen appears.
Enter the information listed in Table 5-7 required to connect to the OES OUD authenticator, see Table 4-11, "OES Unified Directory Information" for more information:
Table 5-7 Authentication and Asserter Details
Field | Description |
---|---|
Provider Name |
OUD Authentication provider you configured in your OES 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:
|
Group Base DN |
Base distinguished name (DN) of the tree in the LDAP directory that contains groups. For example:
|
Asserter Name |
Name to use during Business Operations Center deployment. A new asserter is created if a OAMIdentityAsserter type does not exist in your OES Client domain already. |
Click Next.
The Database Connection Details screen appears.
Enter the database connection details for your BRM database listed in Table 5-8.
Click Next.
The Business Operation Center User Details screen appears.
Enter the user details for your Business Operations Center administrative user listed in Table 5-9.
Table 5-9 Business Operations Center User Details
Field | Description |
---|---|
User Name |
The user name of your Business Operations Center administrative user |
Password |
The Business Operations Center administrative user's password |
Default Tablespace |
The default tablespace for the administrative user |
Temp Tablespace |
The temp tablespace for the administrative user |
Click Next.
The Business Operation Center User Interface Details screen appears.
Enter the user details for your Business Operations Center user interface listed in Table 5-10.
Table 5-10 Business Operations Center User Interface Details
Field | Description |
---|---|
Billing Care URL |
URL of the Oracle Communications 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). |
Click Next.
The Business Operation Center Web Service Details screen appears.
Enter the web service details listed in Table 5-11.
Table 5-11 Business Operations Center Web Service Details
Field | Description |
---|---|
Passwordless SSH User Name |
User name of passwordless SSH user configured for secure communications between the Business Operations Center host and the BRM Server host. See "Creating a Secure Passwordless User on the BRM Server" for more information. |
BRM Server Timezone |
Time Zone (TZ) value of the server operating system on which the BRM is running. |
Click Next.
The Auto Updates screen appears.
Select an auto update option, then click Next.
The Installation Summary screen appears.
Confirm your installation selections, then click Install.
The installation proceeds and executes post install scripts to complete the Business Operations Center installation.
See "Business Operations Center Post-Installation 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.
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 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.