Installation Guide for Oracle Self-Service E-Billing > Migrating to Oracle Self-Service E-Billing Version 6.2 from Other Products >

Roadmap for Migrating Oracle eStatement Manager Version 4.7 to Oracle Self-Service E-Billing Version 6.2

This topic describes the tasks necessary to migrate the Oracle eStatement Manager 4.7 to Oracle Self-Service E-Billing, version 6.2. Oracle eStatement Manager can consist of either of the following application sets:

• Oracle Siebel eStatement Manager 4.7 Fix Pack 1
• Oracle Siebel eStatement Manager 4.7 Fix Pack 1 with Oracle Siebel ePayment Manager 4.7

You must run the migration process on the Oracle Self-Service E-Billing 6.0.3 database server only.

To migrate from Oracle eStatement Manager to Oracle Self-Service E-Billing version 6.1 database, perform the following processes and tasks:

1. Verify that you have at least one month of billing cycle data loaded in the Oracle Self-Service EBilling database, using the ETL process described in Administration Guide for Oracle Self-Service E-Billing.
2. Verify that you have the ebilling-weblogic-10-6.0.3.ear file.

   This file is required for migrating the OLTP database and is packaged with LGPL libraries.

   For more information about LGPL libraries, see Process of Repackaging the GNU Lesser General Public License.

3. Use the Oracle Self-Service E-Billing Command Center to create all Oracle eStatement Manager applications, or Data Definition Names (DDNs), in Oracle Self-Service E-Billing 6.0.3.

   For details on creating application DDNs using Command Center, see Administration Guide for Oracle Self-Service E-Billing.

4. Follow these procedures to install the Oracle Self-Service E-Billing 6.0.3 database and create the schemas:
   1. Preparing to Configure the Oracle Self-Service E-Billing Database
   2. Configuring Oracle Services
   3. Choosing a Database Encryption Method
   4. Perform one of the following:
      • Creating the Oracle Self-Service E-Billing Database Using Ant (Single Node)
      • Creating the Oracle Self-Service E-Billing Database Using the Automated Ant Target
5. Follow these procedures to set up the ETL and load your data:
   1. Verifying ETL Module System Requirements
   2. Creating the Oracle Workflow Manager
   3. Process of Installing the Oracle Warehouse Builder Repository
   4. Installing the ETL Module
   5. Loading Sample Billing Files
   6. Determine the number of months of user transactional data you want to reside in the database. Load the summary data for the previous X months into the Oracle Self-Service E-Billing database, using the ETL Loader Job.
6. Migrating Oracle eStatement Manager Version 4.7 to Oracle Self-Service E-Billing 6.0.3
7. (Optional) After migrating Oracle eStatement Manager Version 4.7 to Oracle Self-Service E-Billing version 6.0.3, new statements appear in the application. If you want to retrieve historical statements for migrated users and display the statements in the original style as Oracle eStatement Manager, then perform the following tasks to integrate flat-file functionality in Oracle Self-Service E-Billing:
   1. Repackaging the Flat-File Component
   2. Loading Historical Bill Data Using ETL
   3. (Optional) If you want to display the historical bills using a format other than the view currently published, then publish a new view (DDF, ALF, and HTML template files) in the Command Center in Oracle eStatement Manager now.

      For information about publishing view files, see Administration Guide for Oracle Siebel eStatement Manager.

   4. Configuring the Media Retrieval Functionality
   5. Customizing the Media Retrieval Functionality
   6. Customizing the Oracle Self-Service E-Billing User Interface to Render the Statement
8. Process of Migrating Oracle Self-Service E-Billing Version 6.0.3 to Version 6.0.4
9. Process of Migrating Oracle Self-Service E-Billing from Version 6.0.4 to Version 6.1
10. Process of Migrating Oracle Self-Service E-Billing from Version 6.1 to Version 6.1.1
11. Process of Migrating Oracle Self-Service E-Billing from Version 6.1.1 to Version 6.2