5 Installing Billing Care

This chapter describes how to install Oracle Communications Billing Care. Before installing Billing Care, read the following chapters:

Billing Care supports test and productions installations. For more information on test and production installations, see "Installing Billing Care for Testing" and "Installing Billing Care for Production" respectively.

Downloading the Billing Care Installer

To download the Billing Care installer:

  1. Create a temporary directory (temp_dir).

  2. Go to the Oracle support web site:

    https://support.oracle.com

  3. Sign in with your user name and password.

  4. Click the Patches & Updates tab.

  5. From the list, select Patch Name or Number.

  6. In the text field, enter PatchNumber and click Search, where PatchNumber is patch number of the latest Oracle Communications Billing and Revenue Management (BRM) 7.5 patch set that includes Billing Care software. See BRM 7.5 Patch Set Installation Guide for more information about the patch number.

    The Patch Search Results page appears.

  7. Click the patch name.

    The patch details appear.

    Important:

    Ensure that the BRM 7.5 patch set README has Billing Care listed as one of the components included in the patch set.

  8. From the Platform list, select the platform and click Download.

    The File Download dialog box appears.

  9. Download the appropriate pPatchNumber_750_platform.zip software pack to temp_dir, where platform is Linux or solaris_64.

  10. Unzip the pPatchNumber_750_platform.zip file.

    The zip archive includes the BillingCare_generic.jar installer.

Installing Billing Care for Testing

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

To install Billing Care for testing:

  1. Disable Billing Care authorization in the WebLogic domain. See "Configuring WebLogic Server for a Test Installation" for more information.

  2. Run the Billing Care installer without specifying IAM host details and confirming that authorization is not being used. See "Running the Billing Care Installer for Testing" for more information.

Configuring WebLogic Server for a Test Installation

Use a WebLogic domain that is not configured as an OES Client Domain when installing test installations of Billing Care. Test installations are not supported in production environments. For a secure Billing Care installation, use an OES Client Domain.

See Oracle Communications Billing Care Security Guide for more information about securing your installation.

To configure a WebLogic domain for a test Billing Care installation:

  1. On the WebLogic Server, add the following property to the JAVA_OPTIONS parameter in the setDomainEnv.sh configuration script located in Middleware_home/user_projects/domains/billingcaredomain/bin directory, where Middleware_home is the directory where WebLogic Server is installed and billingcaredomain is the directory containing the test installation domain you want to install Billing Care:

    -DdisableBillingCareAuthorization=true

    For example:

    JAVA_OPTIONS="${JAVA_OPTIONS} ${JAVA_PROPERTIES} -Dwlw.iterativeDev=${iterativeDevFlag} -Dwlw.testConsole=${testConsoleFlag} -Dwlw.logErrorsToConsole=${logErrorsToConsoleFlag} -DdisableBillingCareAuthorization=true"

  2. Restart the WebLogic Server domain.

  3. Run the Billing Care installer.

Running the Billing Care Installer for Testing

To install a Billing Care test installation in a basic domain:

  1. 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.

  2. Start the Oracle WebLogic Server basic domain administration server or the managed server on which you want to deploy Billing Care.

  3. Download the Billing Care installer. See "Downloading the Billing Care Installer" for more information on how to download the installer.

  4. Run the following command, which launches the Billing Care installer:

    java -jar BillingCare_generic.jar

    Note:

    Specify the -invPtrLoc flag and an Oracle Inventory path location in the java command for launching the Billing Care 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.

  5. Click Next.

    The Installation Location screen appears. Enter your Oracle Home directory path in Oracle Home or click Browse to select a directory.

  6. Click Next.

    The Features Sets Selection screen appears.

    This screen displays the installable Billing Care components. Select either the Billing Care Application or the Billing Care SDK components. To install both on the same host, select Billing Care Components.

  7. Click Next.

    The WebLogic Server Details screen appears.

  8. Enter the following details for the WebLogic Server OES Client domain in which you want to deploy Billing Care, see Table 4-9, "OES Client Domain Information" for more information:

    1. In the Host Name field, enter the IP address or the host name of the computer on which the WebLogic Server domain is configured.

    2. In the Port Number field, enter the port number assigned to the WebLogic Server domain administration server.

    3. In the User Name field, enter the WebLogic Server domain administrator user name.

    4. In the Password field, enter the password for the WebLogic Server domain administrator user.

    5. In the WebLogic Home field, enter the path of the directory in which the WebLogic Server software is installed.

      Note:

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

    6. Deselect the Use SSL? check box.

    7. Click Next.

      The Target Server screen appears.

  9. Select the server on which to deploy Billing Care. The target server list includes the AdminServer and any managed servers managed by the AdminServer.

    Note:

    Oracle recommends that you deploy Billing Care 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.

  10. Click Next.

    The Authenticator and Asserter screen appears.

  11. Select Skip Authenticator and Asserter.

  12. Click Next.

    The Batch Payment Details screen appears.

  13. Enter the following file locations used for processing batch payments:

    1. In the Batch Payment Files Location field, enter the directory where batch payment files are placed for uploading and processing by Billing Care. The installer creates unprocessed, processed, and failure folders in this directory for managing batch payment files.

    2. In the Batch Payment Templates Location field, enter the directory where payment file templates are installed.

  14. Click Next.

    The Auto Updates screen appears.

  15. Select your Auto Updates preferences.

  16. Click Next.

    The Installation Summary screen appears.

  17. Review your Billing Care installation summary and correct any errors.

  18. Click Install.

    The Installation Progress screen appears.

  19. When the Installation completes, Click Next.

    The Installation Complete screen appears. Make note of the Billing Care Links.

  20. Click Finish.

    The Billing Care installer exits.

Installing Billing Care for Production

The Billing Care installer must be run from the computer hosting the Oracle Entitlements Server (OES) Client domain on which you deploy Billing Care. Billing Care 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 Billing Care on your OES Client domain:

  1. 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.

  2. Copy the oamAuthnProvider.jar file from Middleware_home/oracle_common/modules/oracle.oamprovider_11.1.1, where Middleware_home is the WebLogic Server directory containing your OES Client domain (for example, /u01/app/Oracle/Middleware), to Middleware_home/wlserver_10.3/server/lib/mbeantypes.

  3. Start the Oracle WebLogic Server domain administration server or the managed server on which you want to deploy Billing Care. The domain must be configured with the Oracle Entitlements Server (OES) WebLogic Server Security Module. See "Installing and Configuring Oracle Entitlements Server Client" for information on creating an OES Client domain.

  4. Download the Billing Care installer. See "Downloading the Billing Care Installer" for more information on how to download the installer.

  5. Run the following command, which launches the Billing Care installer:

    java -jar BillingCare_generic.jar

    Note:

    Specify the -invPtrLoc flag and an Oracle Inventory path location in the java command for launching the Billing Care 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.

  6. Click Next.

    The Installation Location screen appears. Enter your Oracle Home directory path in Oracle Home or click Browse to select a directory.

  7. Click Next.

    The Features Sets Selection screen appears.

    This screen displays the installable Billing Care components. Select either the Billing Care Application or the Billing Care SDK components. To install both on the same host, select Billing Care Components.

  8. Click Next.

    The WebLogic Server Details screen appears.

  9. Enter the following details for the WebLogic Server OES Client domain in which you want to deploy Billing Care, see Table 4-9, "OES Client Domain Information" for more information:

    1. In the Host Name field, enter the IP address or the host name of the computer on which the WebLogic Server domain is configured.

    2. In the Port Number field, enter the port number assigned to the WebLogic Server domain administration server.

    3. In the User Name field, enter the WebLogic Server domain administrator user name.

    4. In the Password field, enter the password for the WebLogic Server domain administrator user.

    5. In the WebLogic Home field, enter the path of the directory in which the WebLogic Server software is installed.

      Note:

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

    6. Do one of the following:

      If the server does not support SSL, deselect the Use SSL? check box.

      Billing Care 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.

    7. Click Next.

      The Target Server screen appears.

  10. Select the server on which to deploy Billing Care. The target server list includes the AdminServer and any managed servers managed by the AdminServer.

    Note:

    Oracle recommends that you deploy Billing Care 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.

  11. Click Next.

    The Authenticator and Asserter screen appears.

  12. Enter the following information required to connect to the OES OUD authenticator, see Table 4-10, "OES Unified Directory Information" for more information:

    Note:

    Select Skip Authenticator and Asserter if performing a test installation. Production installations should not use this option.

    1. In the Provider Name field, enter the OUD Authentication provider you configured in your OES Administration Server.

    2. In the Host Name field, enter the host name or IP address of the LDAP server.

    3. In the Port Number field, enter the port number on which the LDAP server is listening.

    4. In the Admin User Name field, enter the Distinguished Name (DN) of the LDAP user that WebLogic Server should use to connect to the LDAP server.

    5. In the Admin Password field, enter the credential (usually a password) used to connect to the LDAP server.

    6. In the User Base DN field, enter the base distinguished name (DN) of the tree in the LDAP directory that contains users. For example:

      cn=Users,dc=example,dc=com

    7. In the Group Base DN field, enter the base distinguished name (DN) of the tree in the LDAP directory that contains groups. For example:

      cn=Groups,dc=example,dc=com

    8. In the Asserter Name field, enter a name to use during Billing Care deployment. A new asserter is created if a OAMIdentityAsserter type does not exist in your OES Client domain already.

  13. Click Next.

    The Batch Payment Details screen appears.

  14. Enter the following file locations used for processing batch payments:

    1. In the Batch Payment Files Location field, enter the directory where batch payment files are placed for uploading and processing by Billing Care. The installer creates unprocessed, processed, and failure folders in this directory for managing batch payment files.

    2. In the Batch Payment Templates Location field, enter the directory where payment file templates are installed.

  15. Click Next.

    The Auto Updates screen appears.

  16. Select your Auto Updates preferences.

  17. Click Next.

    The Installation Summary screen appears.

  18. Review your Billing Care installation summary and correct any errors.

  19. Click Install.

    The Installation Progress screen appears.

  20. When the Installation completes, Click Next.

    The Installation Complete screen appears. Make note of the Billing Care Links.

  21. Click Finish.

    The Billing Care installer exits.

See "Billing Care Post-Installation Tasks" for required tasks to complete after the Billing Care installer exits.

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

See "About Installation Logs" for information on the Billing Care 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 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.