6 Business Operations Center Post-Installation Tasks

This chapter provides instructions for Oracle Communications Billing and Revenue Management Business Operations Center post-installation tasks.

Post-Installation Tasks

After installing Business Operations Center test or production installations, do the following on each domain host where Business Operations Center is deployed:

Copy the Business Operations Center Infranet.properties configuration file created during installation to the domain administrative user's home directory on each domain server where Business Operations Center is deployed. See "Copying Configuration File to the Domain Administrative User's Home Directory" for more information.
Add the Oracle Communications Billing and Revenue Management (BRM) connection manager credentials in the Infranet.properties file previously copied to the domain administrative user's home directory. See "Encrypting and Adding BRM Connection Information in Infranet.properties File" for more information.
Adjust your BRM connection pool settings and enable logging in the Infranet.properties file for your Business Operations Center environment. See "Configuring Additional Settings in Infranet.properties" for more information.
If using Internet Explorer, configure the browser cache refresh setting to retrieve new data on each page visit. See "Configuring Internet Explorer for Business Operations Center" for more information.
Create an Oracle WebLogic Server data source for use with Business Operations Center. See "Creating the Business Operations Center WebLogic Server Data Source" for more information.
Run the boc_view.sql script. See "Running SQL Scripts".

For production installations:

Import the Business Operations Center OES Administration Server policy configuration. See "Importing the Business Operations Center Security Policies into OES" for more information.

About Encryption

Encrypting your BRM and BIP passwords and using SSL increases the security of your Business Operations Center deployment. See Oracle Communications Billing and Revenue Management Security Guide for more information about securing your Business Operations Center environment.

Copying Configuration File to the Domain Administrative User's Home Directory

You must copy the Business Operations Center Infranet.properties configuration file provided in the Business Operations Center installation to the domain administrative user's home directory. The Infranet.properties file contains BRM and BIP connection information, and logging settings described in the following sections.

To copy the Business Operations Center Infranet.properties configuration file to the domain administrative user's home directory:

Log in to your domain server using a secure shell or console terminal session as the administrative user for the domain host.
Copy Middleware_home/setup/Infranet.properties, where Middleware_home is your WebLogic home directory, to the home directory of the domain administrative user.

Encrypting and Adding BRM Connection Information in Infranet.properties File

You must configure the Infranet.properties file in each domain server hosting a Business Operations Center deployment with the connection details for your BRM server.

To encrypt your BRM connection manager password and add connection credentials to the Infranet.properties file on each Business Operations Center domain server:

Log in to your BRM server host using a secure shell or console terminal session.
Use the BRM pin_crypt_app utility to encrypt your BRM user's password.

See "About Encrypting Passwords" in Oracle Communications Billing and Revenue Management Developer's Guide for information on encrypting BRM passwords.

Edit the User_home/Infranet.properties file, where User_home is the domain administrative user's home directory, by adding the following information listed in Table 6-1. Remove the preceding and trailing underscore characters for your values.

For more information on establishing a SSL connection to BRM, see "Enabling SSL in Connection Managers" in Oracle Communications BRM System Administrator's Guide.

Table 6-1 Business Operations Center Connection Information for Infranet.properties

Field	Description
USER	BRM system user with connection manager access
PASSWORD	Encrypted BRM system user's password
HOST	BRM host where connection manager is running
PORT	Port number for connection manager

For example:

infranet.connection=pcp://brm123:0D5E11BFDD97D2769D9B0DBFBD1BBF7EE03F1642861DFA57502C7FB85A654267@example.com:8888/service/admin_client 1

Save the Infranet.properties file.
For production installations, if not already done, enable SSL for the OES Client domain where Business Operations Center is deployed.
Restart the domain on which Business Operations Center is deployed.

Encrypting and Adding BIP Connection Information in Infranet.properties File

You must configure the Infranet.properties file in each domain server hosting a Business Operations Center deployment with the connection details for your BIP server, if used in your environment.

To encrypt your BIP password and add connection credentials to the Infranet.properties file on each Business Operations Center domain server:

Log in to your domain server using a secure shell or console terminal session.
Use the WebLogic Server encrypt Java utility to encrypt your BIP user's password.

See "encrypt" in Oracle Fusion Middleware Command Reference for Oracle WebLogic Server for information on encrypting passwords.
Edit the User_home/Infranet.properties file, where User_home is the home directory of the domain administrative user, by adding the following information listed in Table 6-2. Remove the preceding and trailing underscore characters for your values.

Table 6-2 Business Operations Center Connection Information for Infranet.properties

Field Description

BIP_USERID

BIP user with web access

BIP_PASSWORD

Encrypted BIP user's password

BIP_URL

URL address to access BIP instance
Save the Infranet.properties file.
For production installations, if not already done, enable SSL for the OES Client domain where Business Operations Center is deployed.
Restart the domain where Business Operations Center is deployed.

Field	Description
BIP_USERID	BIP user with web access
BIP_PASSWORD	Encrypted BIP user's password
BIP_URL	URL address to access BIP instance

Configuring Additional Settings in Infranet.properties

Business Operations Center uses the default connection pool settings for your BRM instance. You can customize the Business Operations Center connection pool settings by adding additional entries into the Infranet.properties file. You can also enable logging by adding optional entries in the Infranet.properties file.

See "Configuring the Connection Pool" in Oracle Communications Billing and Revenue Management System Administrator's Guide for more information on customizing the default connection pool.

See "Optional Entries in the Infranet.properties File" in Oracle Communications Billing and Revenue Management Developer's Guide for more information on enabling logging for Business Operations Center connections to BRM.

Creating the Business Operations Center WebLogic Server Data Source

Configure a JDBC data source in the Business Operations Center WebLogic Server domain. The deployed Business Operations Center application uses this data source to connect to the database schema created by the installer.

By default, Business Operations Center uses a value of bocdb for the WebLogic Server data source. If you did not specify a custom name for your Business Operations Center database when launching the installer, create a data source named bocdb using the WebLogic Server Administration Console. See "Configuring JDBC Data Sources" in Oracle Fusion Middleware Configuring and Managing JDBC Data Sources for Oracle WebLogic Server for information on creating the required data source for Business Operations Center.

If you specified a custom name for your Business Operations Center database schema during installation, create the WebLogic Server data source using this name. Additionally, you must edit the quartz.properties file with your data source's name.

To edit the quartz.properties file data source name:

Open the Domain_home/lib/quartz.properties file where Domain_home is the WebLogic Server domain home directory of the domain in which Business Operations Center is deployed.
In the DS_NAME parameter, change the value to your custom data source name.
Save the file.
Restart the domain.

Importing the Business Operations Center Security Policies into OES

Business Operations Center includes the system-jazn-data.xml file containing default OES policies, resource-types, resource, and actions. You must import this file into your OES Administration Server to set up the initial Business Operations Center OES configuration. This procedure only needs to be complete once for each OES Administration Server.

The system-jazn-data.xml file is located in the following directory:

Domain_home/lib/oes_config

where Domain_home is the WebLogic domain home directory location of the OES Client domain in which Business Operations Center is deployed.

To import the Business Operations Center security policies into your OES Administration Server:

Open a secure shell or terminal session on the server where you installed Business Operations Center.
Change to the Domain_home/lib/oes_config directory.

Open the jps-config.xml file and modify the following parameters:

sourceContext. Specify the location of the system-jazn-data.xml file, which contains the policies to be migrated to the database. The system-jazn-data.xml file is in the same location as the jps-config.xml file.

<serviceInstance name="src.xml" provider="policystore.xml.provider"
location="location of the system-jazn-data.xml file">
 <description>File Based Policy Store Service Instance</description>
        </serviceInstance>

destinationContext. Specify the location of your OES schema.

<serviceInstance name="policystore.db.destination" provider="policystore.provider">
 <description>DB Based Policy Store Service Instance</description>
 <property name="policystore.type" value="DB_ORACLE"/>
 <property name="jdbc.url" value="jdbc:oracle:thin:@host:1521:mydb"/>
 <property name="jdbc.driver" value="oracle.jdbc.driver.OracleDriver"/>
 <property name="security.principal" value="OES_OPSS"/>
 <property name="security.credential" value="sys"/>
 <property name="oracle.security.jps.ldap.root.name" value="cn=jpsroot"/>
 <property name="oracle.security.jps.farm.name" value="cn=oesAdmin"/>
        </serviceInstance>

jpsContext. Specify the source context and the destination context.

 <jpsContext name="sourceContext">
                <serviceInstanceRef ref="src.xml"/>
        </jpsContext>
        <jpsContext name="destinationContext">
                <serviceInstanceRef ref="policystore.db.destination"/>
        </jpsContext>

Save the file.
Run the migrateSecurityStore utility to import the Business Operations Center policy into your OES Administration Server.

See "Migrating From XML to Database" in Oracle Fusion Middleware Administrator's Guide for Oracle Entitlements Server for detailed information on how to import the Business Operations Center system-jazn-data.xml file into your OES Administration Server.

Configuring Internet Explorer for Business Operations Center

Internet Explorer browser users must change the default cache configuration for Business Operations Center to properly refresh Business Operations Center data.

To configure Internet Explorer to refresh Business Operations Center data on each page visit in Internet Explorer, on each client where Internet Explorer is installed:

Open Internet Explorer.
Click the gear options menu.
Click Internet Options.

The Internet Options window opens.
In the General tab, under Browsing History, click Settings.

The Website Data Settings window opens.
In the Temporary Internet Files tab, select Every time I visit the webpage for the Check for newer versions of stored pages option.
Click OK.

The Website Data Settings window closes.
Click OK to close the Internet Options window.

Running SQL Scripts

You run some SQL scripts to create JOB_INSTANCE_DETAIL_VIEW in the Business Operations Center database.

To run the SQL scripts:

Connect to the Oracle database with SQL*Plus:
```
% sqlplus BRM_Username/BRM_Password@DatabaseAlias
```
where:
- BRM_Username is the Oracle database user name.
- BRM_Password is the Oracle database user password.
- DatabaseAlias is the Oracle database alias.

Run the following scripts:

Note:

Before you run the scripts, do the following:

Update the __BOC_USERNAME__ parameter with the corresponding Business Operations Center database username.
Update the __BOC_PASSWORD__ parameter with the corresponding Business Operations Center database password.
Update the __BRM_USERNAME__ parameter with the BRM database username.

GRANT SELECT ON JOB_BOC_T TO __BOC_USERNAME__ ;
 
GRANT SELECT ON JOB_TEMPLATE_T TO __BOC_USERNAME__ ;
 
GRANT SELECT ON JOB_T TO __BOC_USERNAME__ ;
 
CONNECT __BOC_USERNAME__/__BOC_PASSWORD__ ;
 
CREATE VIEW JOB_INSTANCE_DETAIL_VIEW AS
SELECT  JOB_TEMPLATE_T.POID_ID0 TEMPLATE_ID, JOB_TEMPLATE_T.NAME JOB_NAME, JOB_TEMPLATE_T.CAT_TYPE CATEGORY_CODE, JOB_TEMPLATE_T.CREATED_BY CREATED_BY,
JOB_TEMPLATE_T.USER_TAG TAGS, JOB_TEMPLATE_T.JOB_TYPE JOB_FREQ , JOB_BOC_T.OBJ_ID0 JOB_ID,JOB_BOC_T.STATUS JOB_STATUS,
JOB_T.TRACKING_ID TRACKING_ID,JOB_T.PROCESS_START_T START_TIME,JOB_T.PROCESS_END_T END_TIME
FROM __BRM_USERNAME__.JOB_TEMPLATE_T JOIN __BRM_USERNAME__.JOB_BOC_T ON JOB_TEMPLATE_T.POID_ID0 = JOB_BOC_T.TEMPLATE_OBJ_ID0 JOIN __BRM_USERNAME__.JOB_T ON JOB_T.POID_ID0 = JOB_BOC_T.OBJ_ID0
UNION ALL
SELECT  JOB_TEMPLATE_T.POID_ID0 TEMPLATE_ID, JOB_TEMPLATE_T.NAME JOB_NAME,
JOB_TEMPLATE_T.CAT_TYPE CATEGORY_CODE,  JOB_TEMPLATE_T.CREATED_BY CREATED_BY,
JOB_TEMPLATE_T.USER_TAG TAGS, JOB_TEMPLATE_T.JOB_TYPE JOB_FREQ , JOB_INSTANCE_DETAIL_T.job_instance_id JOB_ID, JOB_INSTANCE_DETAIL_T.job_status JOB_STATUS, NULL TRACKING_ID ,JOB_INSTANCE_DETAIL_T.start_time START_TIME, NULL END_TIME
FROM __BRM_USERNAME__.JOB_TEMPLATE_T JOIN JOB_INSTANCE_DETAIL_T ON JOB_TEMPLATE_T.POID_ID0 = JOB_INSTANCE_DETAIL_T.job_template_id;

Enabling Logging

Business Operations Center writes log messages using the Java Logging API. See "Java Logging" in Oracle Fusion Middleware Configuring Log Files and Filtering Log Messages for Oracle WebLogic Server for more information on enabling Business Operations Center logging.