6 Billing Care Post-Installation Tasks

This chapter provides instructions for Oracle Communications Billing Care post-installation tasks.

Post-Installation Tasks

After installing Billing Care test or production systems, do the following on each domain host where Billing Care is deployed:

• Copy the Billing Care Infranet.properties file created during installation to the domain administrative user's home directory on each domain server where Billing Care is deployed. See "Copying the Infranet.properties File to the Domain Administrative User's Home Directory".

• Add the Oracle Communications Billing and Revenue Management (BRM) connection manager credentials to the Infranet.properties file. See "Encrypting and Adding BRM Connection Information in Infranet.properties File".

• If your BRM system uses Oracle Business Intelligence (BI) Publisher to view invoices, encrypt and add the credentials for accessing BI Publisher to the Infranet.properties file on each domain host where Billing Care is deployed. See "Encrypting and Adding BI Publisher Connection Information in Infranet.properties".

• Adjust your BRM connection pool settings and enable logging in the Infranet.properties file for your Billing Care system. See "Configuring Additional Settings in Infranet.properties".

• If you use Internet Explorer, configure the browser cache refresh setting to retrieve new data on each page visit. See "Configuring Internet Explorer for Billing Care".

For production installations:

• Import the Billing Care OES Administration Server policy configuration. The Billing Care SDK includes a default policy configuration file that must be imported into your OES Administration Server. See "Importing the Billing Care Security Policies into OES".

• If you are using Security Assertion Markup Language (SAML) for single sign-on (SSO), configure SAML. See "Configuring SAML for SSO".

About Encryption

Encrypting your BRM and BI Publisher passwords and using SSL increases the security of your Billing Care deployment. For more information about securing Billing Care, see Billing Care Security Guide.

Copying the Infranet.properties File to the Domain Administrative User's Home Directory

You must copy the Billing Care Infranet.properties file provided in the Billing Care installation to the domain administrative user's home directory. The Infranet.properties file contains BRM and BI Publisher connection information and logging settings described in the following sections.

To copy the Billing Care Infranet.properties file to the domain administrative user's home directory:

1. Log in to your domain server using a secure shell or console terminal session as the administrative user for the domain host.

2. 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 Billing Care 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 Billing Care domain server:

1. Log in to your BRM server host using a secure shell or console terminal session.

2. Use the BRM pin_crypt_app utility to encrypt your BRM user's password.

   For information on encrypting BRM passwords, see "About Encrypting Passwords" in BRM Developer's Guide.

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

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

   Table 6-1 Billing Care 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:[e-mail]:8888/service/admin_client 1

4. Save the Infranet.properties file.

5. For production installations, if not already done, enable SSL for the OES Client domain where Billing Care is deployed.

6. Restart the domain on which Billing Care is deployed.

Encrypting and Adding BI Publisher Connection Information in Infranet.properties

You must configure the Infranet.properties file in each domain server hosting a Billing Care deployment with the connection details for your BI Publisher server if used in your environment.

To encrypt your BI Publisher password and add connection credentials to the Infranet.properties file on each Billing Care domain server:

1. Log in to your domain server using a secure shell or console terminal session.

2. Use the WebLogic Server encrypt Java utility to encrypt your BI Publisher user's password.

   For information on encrypting passwords, see "encrypt" in Oracle Fusion Middleware Command Reference for Oracle WebLogic Server.

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

   Table 6-2 Billing Care Connection Information for Infranet.properties

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

   
   

4. Save the Infranet.properties file.

5. For production installations, if not already done, enable SSL for the OES Client domain where Billing Care is deployed.

6. Restart the domain where Billing Care is deployed.

Configuring Additional Settings in Infranet.properties

Billing Care uses the default connection pool settings for your BRM instance. You can customize the Billing Care connection pool settings by adding additional entries to the Infranet.properties file. You can also enable logging by adding optional entries to the Infranet.properties file.

For more information on customizing the default connection pool, see "Configuring the Connection Pool" in BRM System Administrator's Guide.

For more information on enabling logging for Billing Care connections to BRM, see "Optional Entries in the Infranet.properties File" in BRM Developer's Guide.

Importing the Billing Care Security Policies into OES

The Billing Care SDK includes the system-jazn-data.xml file containing default OES policies, resource types, resources, and actions. You must import this file into your OES Administration Server to set up the initial Billing Care OES configuration. This procedure must be completed only once for each OES Administration Server.

The system-jazn-data.xml file is in the following directory created during the Billing Care SDK installation:

Middleware_home/BillingCare_SDK/reference/OESDataModel

where Middleware_home is the WebLogic Middleware home directory containing the OES client domain on which Billing Care is deployed.

To import the Billing Care security policies into your OES Administration Server:

1. Open a secure shell or terminal session on the server where you installed the Billing Care SDK.

2. Change to the Middleware_home/BillingCare_SDK/reference/OESDataModel directory.

3. 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. Enter the credentials for the 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:@dbhost:dbport:SID"/>
       <property name="jdbc.driver" value="oracle.jdbc.driver.OracleDriver"/>
       <property name="security.principal" value="OPSS Schema Name(Ex:CC_OPSS)"/>
       <property name="security.credential" value="OPSS Schema Password"/>
       <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> 
     

4. Save the file.

5. Run the migrateSecurityStore utility to import the Billing Care policy into your OES Administration Server.

6. Restart the OES client domain.

For more details on how to import the Billing Care system-jazn-data.xml file into your OES Administration Server, see "Migrating From XML to Database" in Oracle Fusion Middleware Administrator's Guide for Oracle Entitlements Server.

Configuring Internet Explorer for Billing Care

Internet Explorer browser users must change the default cache configuration for Billing Care to properly refresh Billing Care data.

To configure Internet Explorer to refresh Billing Care data on each page visit, do the following on each client where Internet Explorer is installed:

1. Open Internet Explorer.

2. Click the gear options menu.

3. Click Internet Options.

   The Internet Options window opens.

4. In the General tab under Browsing History, click Settings.

   The Website Data Settings window opens.

5. In the Temporary Internet Files tab, select Every time I visit the webpage for the Check for newer versions of stored pages option.

6. Click OK.

   The Website Data Settings window closes.

7. Click OK to close the Internet Options window.

Enabling Logging

Billing Care writes log messages using the Java Logging API.

For more information on enabling Billing Care logging, see "Java Logging" in Oracle Fusion Middleware Configuring Log Files and Filtering Log Messages for Oracle WebLogic Server.

Configuring SAML for SSO

You can use SAML 2.0 for enabling SSO in Billing Care. SSO allows you to log in to applications using a single user name and password combination.

To configure SAML for SSO, do the following:

1. Creating SAML Assertion Provider

2. Creating SAML Authenticator

3. Specifying General Information

4. Configuring the SAML Service Provider

5. Publishing the Service Provider Metadata

6. Updating the Deployment Plan of Billing Care

Creating SAML Assertion Provider

To create a SAML assertion provider:

1. Log in to WebLogic Server Administration Console.

2. In the Domain Structure section, click the Security Realms link.

   The Summary of Security Realms page appears.

3. Click the myrealm link.

   The Settings for myrealm page appears.

4. Click the Providers tab.

5. Click the Authentication subtab.

6. Click New.

   The Create a New Authentication Provider page appears.

7. In the Name field, enter samlBC.

8. From the Type list, select SAML2IdentityAsserter.

9. Click OK.

10. Restart WebLogic Server.

11. In the Authentication subtab, click samlBC link to view the settings for samlBC.

12. Click the Management tab.

13. Click New and select Web Single Sign-On Identity Provider Partner.

    The Create a Web Single Sign-On Identity Provider Partner page appears.

14. In the Name field, enter WebSSO-IdP-Partner-1.

15. In the Path field, enter the path to the XML file that contains the identity provider's metadata.

16. Click OK.

17. Click WebSSO-IdP-Partner-1 link.

18. Ensure that the identity provider details are displayed in the Site Info and Single Sign-On Signing Certificate tabs.

19. In the General tab, select the Enabled, Virtual User, and Process Attributes check box.

20. In the Redirect URIs field, enter /bc/*.

21. Click Save.

Creating SAML Authenticator

To create a SAML authenticator:

1. Log in to WebLogic Server Administration Console.

2. In the Domain Structure section, click the Security Realms link.

   The Summary of Security Realms page appears.

3. Click the myrealm link.

   The Settings for myrealm page appears.

4. Click the Providers tab.

5. Click the Authentication subtab.

6. Click New.

   The Create a New Authentication Provider page appears.

7. In the Name field, enter samlBCAuth.

8. From the Type list, select SAMLAuthenticator.

9. Click OK.

10. Click the samlBCAuth link and modify the Control Flag to SUFFICIENT.

11. Click Save.

12. Click the DefaultAuthenticator link and modify the Control Flag to SUFFICIENT.

13. Click Save.

14. Reorder the providers in the following order:

    • samlBCAuth

    • samlBC

    • DefaultAuthenticator

    • DefaultIdentityAsserter

15. Click OK.

Specifying General Information

To specify the SAML general information:

1. Log in to WebLogic Server Administration Console.

2. In the Domain Structure section, click Environment > Servers > AdminServer.

3. In the Settings for AdminServer page, select Configuration > Federation Services > SAML 2.0 General.

4. In the Published Site URL field, enter http://billingcare_hostname:port/saml2.

   where:

   • billingcare_hostname is the Billing Care application host.

   • port is the port on which Billing Care is listening on.

5. In the Entity ID field, enter samlBC.

6. Click Save.

Configuring the SAML Service Provider

To configure the SAML service provider:

1. Log in to WebLogic Server Administration Console.

2. In the Domain Structure section, click Environment > Servers > AdminServer.

3. In the Settings for AdminServer page, select Configuration > Federation Services > SAML 2.0 Service Provider.

4. Select the Enabled checkbox.

5. Select POST from the Preferred Binding list.

6. In the Default URL field, enter http://billingcare_hostname:port/bc/login.html.

   where:

   • billingcare_hostname is the Billing Care application host.

   • port is the port on which Billing Care is listening on.

7. Restart WebLogic Server.

Publishing the Service Provider Metadata

To publish the service provider metadata:

1. Log in to WebLogic Server Administration Console.

2. In the Domain Structure section, click Environment > Servers > AdminServer.

3. In the Settings for AdminServer page, select Configuration > Federation Services > SAML 2.0 General.

4. Click Publish Meta Data.

   The Publish SAML 2.0 Meta Data page appears.

5. In the Path field, enter the full path and filename of the metadata file. For example, C:\mydomain\myserver\sppmeta.xml.

6. Click OK.

Updating the Deployment Plan of Billing Care

To update the deployment plan of Billing Care:

1. Create an XML file with the deployment plan:

   <?xml version='1.0' encoding='UTF-8'?>
   <deployment-plan xmlns="http://xmlns.oracle.com/weblogic/deployment-plan"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:schemaLocation="http://xmlns.oracle.com/weblogic/deployment-plan
   http://xmlns.oracle.com/weblogic/deployment-plan/1.0/deployment-plan.xsd"
   global-variables="false">
     <application-name>BillingCare.war</application-name>
     <variable-definition> 
       <variable>
          <name>cookie-name</name>
         <value>JSESSIONID</value>
       </variable>
     </variable-definition>
   <module-override>
     <module-name>BillingCare.war</module-name>
     <module-type>war</module-type>
     <module-descriptor external="true">
       <root-element>weblogic-web-app</root-element>
       <uri>WEB-INF/weblogic.xml</uri>
         <variable-assignment>
           <name>cookie-name</name>
   <xpath>/weblogic-web-app/session-descriptor/cookie-name</xpath>
   <operation>replace</operation>
         </variable-assignment>
         </module-descriptor>
     </module-override>
   </deployment-plan>
   

2. Log in to the Oracle WebLogic Server Administration Console.

3. In the Domain Structure section, click Deployments.

4. In the Control tab, select BillingCare in the Deployments table.

5. Click Update.

6. In the Update Application Assistant screen, select Redeploy this application using the following deployment files:.

7. Click Change Path next to the Deployment plan path.

8. Enter or browse to the directory in which the xml file created in step 1 is located and click Next.

9. Click Finish.

Verifying SAML Configuration

To verify the SAML configuration:

1. Go to the URL http://billingcare_hostname:port/bc.

   where:

   • billingcare_hostname is the Billing Care application host.

   • port is the port on which Billing Care is listening on.

   The login page of the identity provider is displayed.

2. Enter the login credentials.

   The Billing Care home page appears.