You are on page 1of 104

Installation Guide for Oracle eBilling

Version 6.0 December, 2007

Copyright 2005, 2008, Oracle. All rights reserved. The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be errorfree. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. PRODUCT MODULES AND OPTIONS. This guide contains descriptions of modules that are optional and for which you may not have purchased a license. Siebels Sample Database also includes data related to these optional modules. As a result, your software implementation may differ from descriptions in this guide. To find out more about the modules your organization has purchased, see your corporate purchasing agent or your Oracle sales representative. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.

Contents

Chapter 1:

Getting Started
7 8 8

Operating System Administration Tasks Database Administration Tasks Preparing Your Platform 8 9 Application Server Administration Tasks Process of Installing Oracle eBilling

Configuring Your Database Server 9 Configuring Your Application Server 9 Deploying the Oracle eBilling Applications

Oracle eBilling System Requirements

10

Sun Solaris, BEA WebLogic, Oracle Database 10 Microsoft Windows, BEA WebLogic, Oracle Database 11 Linux, Oracle Application Server, Oracle Database 12 Third-Party Software 13

Chapter 2:

Installing on WebLogic and Oracle Database (Solaris or Windows)


15 16

Installing Oracle eBilling Software Configuring the Oracle Database

Before Getting Started 17 Configuring Oracle Services 17 Creating the eStatement Component Using Ant 19 Creating the Oracle ePayment Component Using Ant Create the Oracle eBilling Database using Ant 23 Using the Automated Ant Targets 26

22

Migrating from the CBA 5.1.1 Database to Oracle eBilling 6.0

30

Migrating the CBA 5.1.1 Database from Oracle 9i to Oracle 10.2.0.2 (UNIX and Windows) 30 Migrating the CBA 5.1.1 eStatement Component to Oracle eBilling 6.0 (on UNIX and Windows) 31 Installing the ePayment Database on an Existing Oracle CBA 5.1.1 OLTP Database 32 Migrating the CBA 5.1.1 OLTP Database to Oracle eBilling 6.0 OLTP on UNIX 33 Migrating CBA 5.1.1 OLTP to Oracle eBilling 6.0 OLTP on Windows 34 Migrating the CBA 5.1.1 OLAP Schema to Oracle eBilling 6.0 on Windows 36

Installation Guide for Oracle eBilling Version 6.0

Contents

What to Do if the Database Configuration Fails

38 38 45

Configuring WebLogic

38

Configuring WebLogic for the Oracle eBilling J2EE Applications EAR Configuring WebLogic for the Oracle eBilling Command Center EAR Configuring WebLogic for the Oracle eBilling CSR EAR 52

Repackaging LGPL Running Scheduler

54 57 58 58

Deploying Oracle eBilling Applications on Solaris or Windows Running the eBilling Applications

Chapter 3:

Installing on Linux, Oracle Database, and Oracle Application Server


61 62

About Installing on Oracle Application Server Installing Oracle eBilling Software 62 63

Managing the Oracle Application Server Environment Configuring the Oracle Database for Linux

Configuring the Oracle Application Server for Linux

64

Installing on Oracle Application Server 10g 64 Creating an OC4J Instance for Oracle eBilling 66 Configuring JDBC for Oracle eBilling 66 JTA Transaction Configuration 69 Configuring JMS for the Oracle eBilling Application 69 Configuring opmn.xml for Oracle eBilling 72 Configuring Log4j for Oracle eBilling 74 Configuring Jikes for Oracle eBilling 75 Configuring the Oracle eBilling and Command Center Applications for Notification Creating an OC4J Instance for Command Center 76 Configuring JDBC for the Command Center 77 Configuring JMS for the Command Center 78 Configuring opmn.xml for the Command Center 80 Configuring Log4j for the Command Center 82 Configuring Jikes for the Command Center 83 Creating an OC4J Instance for CSR 83 Configuring JDBC for CSR 84 Configuring opmn.xml for CSR 84 Configuring Log4j for the CSR 86 Configuring the Jikes Compiler for the CSR 86 Modifying csr.xma.xml 86

76

Installation Guide for Oracle eBilling Version 6.0

Contents

Modifying persistence.xma.xml Repackaging LGPL 88

87
87

Example of edited persistence.xma.xml file

Deploying Oracle eBilling Applications for Linux on OAS Running Scheduler on Linux and OAS 89 90 Running the eBilling Applications on Linux and OAS

88

Chapter 4:

Installing Oracle eBilling ETL


93 93

ETL Module System Requirements Installing the OWB Repository

Tuning the OLAP Database 94 Creating the OWB Repository Owner 94 Creating the OWB Repository User 95 Creating an OWB Project 96 Creating Database Modules 96 Creating a Process Flow Module 97 Creating File System Locations 97 Registering Locations 98 Granting Rights to MAP_USER 98

Installing the ETL Module

99
101

Installing ETL 99 Running the ETL Loader Job

Chapter 5:

Uninstalling Oracle eBilling


103 103

Preparing to Uninstall Oracle eBilling Uninstalling Oracle eBilling

Installation Guide for Oracle eBilling Version 6.0

Contents

Installation Guide for Oracle eBilling Version 6.0

Getting Started

This chapter covers the tasks you must perform to prepare to install Oracle eBilling and the system requirements necessary for Oracle eBilling. It includes the following topics: Operating System Administration Tasks Database Administration Tasks Application Server Administration Tasks Preparing Your Platform Process of Installing Oracle eBilling Oracle eBilling System Requirements

This guide is intended for system administrators and other IT professionals, and assumes in-depth understanding of and practical experience with system administrator responsibilities, including the tasks described in this chapter.

Operating System Administration Tasks


Operating system administrators must know to perform these tasks. Start up and shut down the operating system Log in and out Determine software patch or pack levels Install software and patches or packs Navigate the file system Manipulate text files Create files and directories Change permissions of files and directories Use basic network commands Transfer files Monitor processes and system resource usage Perform system backups and recovery Implement system security

Installation Guide for Oracle eBilling Version 6.0

Getting Started Database Administration Tasks

Database Administration Tasks


Database administrators must know how to perform these tasks. Install and configure your database server Start and stop your database server and database instances Use administrative tools Manage users, privileges, and resources Create an operational database Manage database files Manage tables and indexes Back up and restore databases Monitor database performance

Application Server Administration Tasks


Application server administrators must know how to perform these tasks. Install and configure your application server Start and stop your application server Use administrative tools Manage users, privileges, and resources Configure Java resources Package and deploy Web applications Monitor application server performance

This guide does not describe general UNIX system administration. If you are unfamiliar with any of these tasks, please consult the related documentation for your system requirements.

Preparing Your Platform


Before installing Oracle eBilling, verify that your platform is ready: Install and test required hardware and software for your platform. Define required user and group permissions for your database server and application server. Start and test your database server. For details, see your server documentation. Start and test your application server. For details, see your application server documentation. For distributed environments, make sure you have any required database client software installed on your application server and any other client machines of your database server.

Installation Guide for Oracle eBilling Version 6.0

Getting Started Process of Installing Oracle eBilling

Process of Installing Oracle eBilling


The process of installing and setting up Oracle eBilling includes the following steps:

1 2 3

Installing Oracle eBilling on your database and application servers. Configuring the database server. Configuring the application server.

Follow the chapters in this guide in sequence. Consult any third-party documentation as needed. You must use the same user to install Oracle eBilling that you used to install the application server. After you successfully install Oracle eBilling and configure your database and application servers, you can customize and deploy your J2EE application.

Configuring Your Database Server


Configuring your database server requires you to: Define database server environment variables. Create and configure the Oracle eBilling database. Connect to your Oracle eBilling database before configuring your application server.

Configuring Your Application Server


Configuring your application server requires you to: Create and configure three separate domains for the Oracle eBilling J2EE applications, the Command Center, and the CSR application. Configure JDBC and JMS resources (where appropriate). Configure the application server environment.

Deploying the Oracle eBilling Applications


After installing Oracle eBilling and configuring your database and application servers, you can: Deploy the Oracle eBilling applications:

User Interface Command Center CSR Interface

Run the Oracle Scheduler Run the applications

Installation Guide for Oracle eBilling Version 6.0

Getting Started Oracle eBilling System Requirements

Oracle eBilling System Requirements


Oracle eBilling runs on the following three platform combinations: Table 1. Oracle eBilling Platforms Database Oracle Oracle Oracle Application Server BEA WebLogic BEA WebLogic Oracle Application Server

Operating System Sun Solaris 10 Microsoft Windows 2003 SP1 Red Hat Enterprise Linux 4

Specific system requirements for each platform are listed below. Be sure to check the Release Notes for Oracle eBilling 6.0 on Oracle MetaLink for any updates to these requirements. Required JDK versions, system patches, fix packs and other updates might not be listed in this section.

Sun Solaris, BEA WebLogic, Oracle Database


This topic describes the system requirements for installing and running Oracle eBilling on Solaris, WebLogic, and Oracle database.

Operating System
Sun Solaris 10 Operating Environment

Hardware
CD-ROM (optional) Disk space (database) 2.6 GB Disk space (software) 250 MB Swap space 512 MB for each CPU (1 GB recommended) RAM 512 MB for each CPU (1 GB recommended)

Java
Sun Java SDK Standard Edition 5 (version shipped with BEA WebLogic Server)

Other Software
Apache Ant version 1.6.5 or later Jikes Compiler 1.22

10

Installation Guide for Oracle eBilling Version 6.0

Getting Started Oracle eBilling System Requirements

Supported Database Servers


Oracle Database 10g Version 10.2.0.2 (for new installations of Oracle eBilling)

Supported Application Servers


BEA WebLogic Server 9.2

Supported Browsers
Microsoft Internet Explorer 6.0 and 7.0 Mozilla Firefox 2.0

Microsoft Windows, BEA WebLogic, Oracle Database


This topic describes the system requirements for installing and running Oracle eBilling on Windows, WebLogic, and Oracle database.

Operating System
Microsoft Windows 2003 Server SP1

Hardware
CD-ROM (optional) Disk space (database) 2.6 GB Disk space (software) 250 Swap space 512 MB for each CPU (1 GB recommended) RAM 512 MB for each CPU (1 GB recommended)

Java
Sun Java SDK Standard Edition 5 (version shipped with BEA WebLogic Server)

Other Software
Apache Ant version 1.6.5 or later Jikes Compiler Version 1.22

Supported Database Servers


Oracle 10g Version 10.2.0.2 (for new installations of Oracle eBilling)

Installation Guide for Oracle eBilling Version 6.0

11

Getting Started Oracle eBilling System Requirements

Supported Application Servers


BEA WebLogic Server 9.2

Supported Browsers
Microsoft Internet Explorer 6.0 and 7.0 Mozilla Firefox 2.0 or later

Linux, Oracle Application Server, Oracle Database


This topic describes the system requirements for installing and running Oracle eBilling on Linux, Oracle Application Server, and Oracle database.

Operating System
Red Hat Enterprise Linux 4

Hardware
CD-ROM (optional) Disk space (database) 2.6 GB Disk space (software) 250 MB Swap space 512 MB for each CPU (1 GB recommended) RAM 512 MB for each CPU (1 GB recommended)

Java
Sun Java SDK Standard Edition 5 (version shipped with Oracle Application Server)

Other Software
Apache Ant version 1.6.5 or later Jikes Compiler 1.22

Supported Database Servers


Oracle Database 10g Version 10.2.0.2 (for new installations of Oracle eBilling)

Supported Application Servers


Oracle Application Server 10g Version 10.1.3.2

12

Installation Guide for Oracle eBilling Version 6.0

Getting Started Oracle eBilling System Requirements

Supported Browsers
Microsoft Internet Explorer 6.0 and 7.0 Mozilla Firefox 2.0

Third-Party Software
Some third-party software identified in the Oracle product installation documentation might not be distributed directly by Oracle. Although such third-party software is certified with Oracle products, updates and fixes are available only from the source provider. The customer must certify that any software not distributed by Oracle is malware and virus free. If a security patch is required for software not distributed by Oracle, but required for the secure operation of the Oracle product, a notification of patch availability for third-party software will be provided when such a patch is certified for use with the Oracle product.

Installation Guide for Oracle eBilling Version 6.0

13

Getting Started Oracle eBilling System Requirements

14

Installation Guide for Oracle eBilling Version 6.0

Installing on WebLogic and Oracle Database (Solaris or Windows)

This chapter describes how to install Oracle eBilling on Solaris and Windows using the Oracle Database and WebLogic Application Server. It includes the following topics: Installing Oracle eBilling Software Configuring the Oracle Database Migrating from the CBA 5.1.1 Database to Oracle eBilling 6.0 Configuring WebLogic Repackaging LGPL Deploying Oracle eBilling Applications on Solaris or Windows Running Scheduler Running the eBilling Applications

Installing Oracle eBilling Software


Oracle eBilling is distributed as an InstallAnywhere package. You can change the default installation directory when prompted during the installation procedure. This document refers to the directory where you install Oracle eBilling as the EDX_HOME directory, by default /opt/Oracle/eBilling (C:\Oracle\eBilling on Windows). Scripts for database creation and configuration can be found in /opt/Oracle/eBilling/db (C:\Oracle\eBilling\db on Windows). Web applications to be deployed to your application server can be found in /opt/Oracle/eBilling/ J2EEApps (C:\Oracle\eBilling\J2EEApps on Windows).

To install the Oracle eBilling software using InstallAnywhere 1 2


(Solaris Only) Log in using the user and group name of the application server owner, such as edxadmin:edxadmin. Launch InstallAnywhere in UI mode by typing ./eBilling.bin (or by double-clicking the eBilling.exe on Windows). For UNIX, make sure DISPLAY is set. (Solaris Only) To launch InstallAnywhere in Console Mode, type: $eBilling.bin -i console Follow the on-screen instructions.

Installation Guide for Oracle eBilling Version 6.0

15

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring the Oracle Database

3 4 5 6

On the Introduction screen, read the Oracle eBilling introductory information. Click Next to continue. On the License Agreement screen, read the licensing agreement carefully, select the terms acceptance, then click Next. On the Enter Serial Number screen, enter your product serial number. Then click Next. (Solaris Only) On the Owner of Web Application Server screen, enter the name of the application server owner (if you have installed other Oracle Self-Service products, use the same owner here that you used for those product installations). Then click Next. (Solaris Only) On the Group of Web Application Server screen, enter the name of the group for the application server (if you have installed other Oracle Self-Service products, use the same group here that you used for those product installations). Then click Next. On the Choose Install Folder screen, accept the default installation folder or click Choose and enter the directory where you want to install the Oracle eBilling files and directories. (This document refers to that directory as EDX_HOME.) Click Next to continue. On the Choose Product Features screen, click eBilling Group, then click Next. will be installed and click Next.

10 (Windows Only) On the Choose Shortcut Folder, choose the Program Group where the product 11 On the Pre-Installation Summary screen, verify that the information is correct, and click Install.
To correct any entries, click Previous. The installer copies the Oracle eBilling software components to the designated installation folder. A status bar on the bottom of the screen shows each component being installed. If installation is successful, you see a congratulatory message and the directory that contains the Oracle eBilling components. Click Next.

12 Click Done to exit the installer.


If the installation fails, determine the cause of the problem and run InstallAnywhere again to reinstall Oracle eBilling.

Configuring the Oracle Database


For distributed environments, make sure you have any required database client software installed on your application server and any other client machines of your database server. It is recommended that you install and configure Oracle eBilling in the same top-level directory structure, first on the database server, then the application server. CAUTION: The installation and configuration examples in this guide use default Oracle eBilling pathnames, privileges, and permissions. If you choose not to accept the default values, make sure your values are consistent on all servers across your installation of Oracle eBilling An Ant script is provided for you to create and configure your Oracle eBilling database.

16

Installation Guide for Oracle eBilling Version 6.0

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring the Oracle Database

Before Getting Started


Before running the database installation Ant script, be sure to: Upgrade your database server software as necessary. Make a full backup of your current database. Start the database instance that accesses the database you are installing. Check the status of all user objects. If any of them indicate an INVALID status, contact the database administrator to correct this problem. Have any required database passwords available. Check with your database administrator for custom passwords. Check the Release Notes for Oracle eBilling on Oracle MetaLink for updated disk space requirements and confirm that you have sufficient space on your database server. Insufficient disk space can cause the database configuration to fail. Configure Oracle Services as described in the next section.

Note that database clustering is handled by your application server and not by Oracle eBilling. Consult your Professional Services representative for clustered installations.

Configuring Oracle Services


You must edit the following Oracle configuration files that control access to the Oracle eBilling production database: listener.ora. Includes a list of service names and address of all listeners on a computer, the instance names of the databases for which they listen, and listener control parameters. The address for a server in listener.ora requires the SID (SID_NAME) of a database server in tnsnames.ora. You modify listener.ora on the database servers. tnsnames.ora. Includes a list of service names of network databases that are mapped to connect descriptors. It is used by clients and distributed database servers to identify potential server destinations. The address of a given database server in tnsnames.ora matches the address of a listener for that server in listener.ora. You modify tnsnames.ora on the database clients. By default, these files are installed to the network administration directory of your database server $ORACLE_HOME/network/admin (%ORACLE_HOME%\network\admin on Windows). Consult with your onsite DBA and your Professional Services representative to configure database connectivity, to make sure you comply with client standards for the enterprise.

Installation Guide for Oracle eBilling Version 6.0

17

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring the Oracle Database

To configure Oracle services 1


Change directory to the network administration directory of your database server. For example: Solaris: $ORACLE_HOME/networks/admin Windows: > cd %ORACLE_HOME%\networks\admin

Open listener.ora and edit the SID_LIST_LISTENER section to reflect your Oracle SID and database home directory. For example: (SID_DESC = (SID_NAME = OLTP) (ORACLE_HOME = /opt/oracle/product/10.2.0) ) (SID_DESC = (SID_NAME = OLAP) (ORACLE_HOME = /opt/oracle/product/10.2.0) )

3 4 5

Save and close listener.ora. Change directory to the network administration directory of your database client. For example: > cd %ORACLE_HOME%\networks\admin Open tnsnames.ora and edit the database service that identifies your protocol, host, and port. This example uses the service names OLTP and OLAP (your service names might be different), installed on the database server localhost. OLTP = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521)) ) (CONNECT_DATA = (SID = OLTP) ) ) OLAP =

18

Installation Guide for Oracle eBilling Version 6.0

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring the Oracle Database

(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521)) ) (CONNECT_DATA = (SID = OLAP) ) )

6 7 8 9

If you paste this into your tnsnames.ora file, ensuring the values for the host, port number and SID are correct. Save and close tnsnames.ora. Repeat Step 5 for the tnsnames.ora file on your application server. This file is installed with your database client software. Single machine environments can skip this step. Stop and restart the Oracle listener with the listener control commands. > lsnrctl stop > lsnrctl start

10 After the Oracle listener is restarted, to see the service summary for the Oracle eBilling instance,
run: > lsnrctl status

Services Summary... OLAP has 1 service handler(s) OLTP has 1 service handler(s) This service handler must match the name you entered for the Oracle SID during database configuration, in this example, OLTP and OLAP.

Creating the eStatement Component Using Ant


If you already have an OWB/OWF repository set up, you do not have to recreate the database instance. Instead, you can drop the OLAP and OLTP schema and recreate the schemas using the following script. You can also use automated Ant targets to install the eStatement component on an existing instance. For details about the install-existing target, see Using the Automated Ant Targets on page 26.

Installation Guide for Oracle eBilling Version 6.0

19

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring the Oracle Database

The file edxadmin.properties contains configuration parameters specific to each installation and is used by the Ant script that installs the Oracle eBilling database. You must update this file before running the eStatement Ant script.

To verify configuration parameters for eStatement (in edxadmin_unix.properties or edxadmin.properties on Windows) 1


Verify that the following values are correct for the current installation. edxadmin_unix.properties can be found under $EDX_HOME/db/eStatement/oracle. For Windows, edxadmin.properties can be found under %EDX_HOME%\db\eStatement\oracle.

ORACLE_BASE and ORACLE_HOME locations OLTP database SID, and username and password SYSTEM password for OLTP Database file locations Redo file locations Trace file location

To create the eStatement component 1


Change directory to the location of the eStatement Oracle Database installation files in your software installation. Solaris: >cd $EDX_HOME/db/eStatement/oracle Windows: > cd %EDX_HOME%\db\eStatement\oracle

Configure the Apache Ant environment: Solaris: $ export ANT_HOME=/opt/apache-ant-1.6.5 $ export JAVA_HOME=$BEA_HOME/JDK150_04 (with your specific JDK version) $ export PATH=$JAVA_HOME/bin:$ANT_HOME/bin:$PATH Windows: > set ANT_HOME=C:\apache-ant-1.6.5 > set JAVA_HOME=$BEA_HOME/JDK150_04 (with your specific JDK version) > set PATH=%PATH%;%JAVA_HOME%\bin;%ANT_HOME%\bin

20

Installation Guide for Oracle eBilling Version 6.0

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring the Oracle Database

Run the build script by typing ant. By default, Ant picks up the build.xml in the current directory. The Main Menu appears: main: [echo] [1]. Install eStatement Database [echo] [2]. Initial Data Population [echo] [Q]. Quit [input] Enter your selection(1,2,q,Q)

From the top level Main Menu, select Option 1, [1] Install eStatement Database to start. The Install eStatement Database menu appears: CreateInitDatabaseMenu: [echo] Install eStatement Database [echo] [1]. Create Oracle Instance [echo] [2]. Shutdown Database [echo] [3]. Startup Database [echo] [4]. Install Application Database I - Create tablespace/user [echo] [5]. Install Application Database II - Create tables [echo] [6]. Install Application Database III - Install PL/SQL Code Base [echo] [Q]. Quit [input] Enter your selection(1,2,3,4,5,6,q,Q) Note that if you want to create a schema only on an existing database instance, you only need to run options 4-6 on this menu. If you want to create a database instance as well, run all the options as described below.

Select Option 1, Create Oracle Instance. This step creates a database instance for the eStatement component, defines a data dictionary and stored procedure for the new database and modifies the stored procedures to contain the absolute pathnames you defined in edxadmin.properties. No user input is required, although several progress messages appear. Note that this step can take anywhere from 20 minutes to 2 hours to complete, depending on the speed of your platform. If this step is successful, Ant exits with a "Build Successful" message.

Run Ant again and navigate back to the Install eStatement Database Menu from the previous step. Select Option 2, Shutdown Database. If this step is successful, Ant exits with a "Build Successful" message. Run Ant again and navigate back to the Install eStatement Database Menu. Select Option 3, Startup Database. If this step is successful, Ant exits with a "Build Successful" message. Run Ant again and navigate back to the Install eStatement Database Menu. Select Step 4, Install Application Database I - Create tablespace/user.

7 8

Installation Guide for Oracle eBilling Version 6.0

21

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring the Oracle Database

Run Ant again and navigate back to the Install eStatement Database Menu. Select Step 5, Install Application Database II - Create tables. Application Database III - Create PL/SQL Code Base.

10 Run Ant again and navigate back to the Install eStatement Database Menu. Select Step 6, Install 11 Optionally, you can run Ant again and from the top level menu, select Option 2, Initial Data
Population, and select Option 2 - Export eStatement Database Data. Other Operations Menu: [echo] [1]. Import initial data set [echo] [2]. Export eStatement database data [echo] [Q]. Quit [input] Enter your selection(1,2,q,Q)

Creating the Oracle ePayment Component Using Ant


Before running Ant, make sure that the payusr.properties instead is configured with the same database SID, username, password as you used for the eStatement component installation. The file payusr.properties contains configuration parameters specific to each installation and is used by the Ant script that installs the Oracle ePayment database. It is important to verify that payusr.properties contains the correct values for the current installation.

To verify configuration parameters in payusr.properties for ePayment 1


In the payusr.properties file, make sure that you give the same OLTP database SID, and username and password that you specified in edxadmin.properties of the eStatement installation. payusr.properties can be found under $EDX_HOME/db/ePayment/oracle (%EDX_HOME%\db\epayment\oracle on Windows).

To create the ePayment component 1


Change directory to the location of the ePayment component installation files in your software installation: Solaris: $ cd $EDX_HOME/db/ePayment/oracle Windows: > cd %EDX_HOME%\db\epayment\oracle

22

Installation Guide for Oracle eBilling Version 6.0

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring the Oracle Database

If you have not configured the Apache Ant environment, do so now: Solaris: $ export ANT_HOME=/opt/apache-ant-1.6.5 $ export PATH=$ANT_HOME/bin:$PATH $ export JAVA_HOME=$BEA_HOME/JDK150_04 (with your specific JDK version) Windows: > set ANT_HOME=C:\apache-ant-1.6.5 > set PATH=%PATH%;%ANT_HOME%\bin > set JAVA_HOME= $BEA_HOME/JDK150_04 (with your specific JDK version)

Run the build script by typing ant. By default Ant picks up the build.xml in the current directory. The Main Menu appears: main: [echo] Install Payment database [echo] [1]. Install Application Database I [echo] [2]. Install Application Database II [echo] [3]. Initial Data Population [echo] [Q]. Quit

[input] Enter your selection(1,2,3,q,Q) From the top level Main Menu select option 1, [1] Install Application Database I.

4 5

Type ant again, and from the top level Main Menu select option 2, [2] Install Application Database II. Type ant again, and from the top level Main Menu select option 3, [3] Initial Data Population.

Create the Oracle eBilling Database using Ant


Before running Ant, make sure that the edxadmin_unix.properties (or edxadmin.properties on Windows) is configured with the same OLTP database SID, username, password as you used for the eStatement component installation.

To verify configuration parameters in edxadmin_unix.properties (or edxadmin.properties on Windows) for eBilling 1


Verify that the following values in $EDX_HOME/db/ebilling/oracle/edxadmin_unix.properties (or %EDX_HOME%\db\ebilling\oracle\edxadmin.properties on Windows) are correct for the current installation.

Installation Guide for Oracle eBilling Version 6.0

23

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring the Oracle Database

ORACLE_BASE and ORACLE_HOME locations OLTP and OLAP database SID, and username and password SYSDBA password and tnsnames for OLTP and OLAP Database file locations Redo file locations Trace file location

To create the Oracle eBilling database 1 2


Change directory to the location of the Oracle Database installation files in your software installation: $EDX_HOME/db/ebilling/oracle (%EDX_HOME%\db\ebilling\oracle for Windows). If you have not configured the Apache Ant environment, do so now: Solaris: $ export ANT_HOME=/opt/apache-ant-1.6.5 $ export PATH=$ANT_HOME/bin:$PATH $ export JAVA_HOME= $BEA_HOME/JDK150_04 (with your specific JDK version) Windows: > set ANT_HOME=C:\apache-ant-1.6.5 > set PATH=%PATH%;%ANT_HOME%\bin > set JAVA_HOME= $ BEA_HOME/JDK150_04 (with your specific JDK version)

Run the build script by typing ant. By default, Ant picks up the build.xml in the current directory. The Oracle eBilling DB Administration Main Menu appears: Main: [echo] Oracle eBilling DB Administration Main Menu Version 1.0 [echo] [1]. Install OLAP [echo] [2]. Install OLTP [echo] [3]. Install ETL [echo] [Q]. Quit [input] Enter your selection (1,2,3,q,Q)

24

Installation Guide for Oracle eBilling Version 6.0

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring the Oracle Database

Select Option 1 - Install OLAP. The OLAP menu appears: Main: [echo] Install Oracle eBilling Reporting [echo] [1]. Create Oracle Instance [echo] [2]. Shutdown Database [echo] [3]. Startup Database [echo] [4]. Create OLAP Tablespaces [echo] [5]. Create OLAP schema [echo] [6]. Create OLAP Database Objects [echo] [7]. Create Initial Data [echo] [8]. Create Sample Data (optional) [echo] [Q]. Quit [input] Enter your selection(1,2,3,4,5,6,7,8,q,Q)

Note that if you want to create a schema only on an existing database instance, you only need to run options 4-8 on this menu. If you want to create a database instance as well, run all the options shown in Step 4. Select Option 1, Create Oracle Instance. This step creates a new database instance for Oracle eBilling reporting, defines a data dictionary and all the system database objects only. No user input is required, although several progress messages appear. Note that this step can take anywhere from 20 minutes to 2 hours to complete, depending on the speed of your platform If this step is successful, Ant exits and a "Build Successful" message appears.

(Optional when creating a new instance/schema) Run Ant again and navigate back to the OLAP main menu. Select Option 2, Shutdown Database. If successful, a "Build Successful" message appears. Run Ant again and navigate back to the OLAP main menu. This time, select Option 3, Startup Database. If successful, a "Build Successful" message appears.

Run Ant again and navigate back to the OLAP main menu. Select Step 4, Create OLAP Tablespaces. Repeat this step for Options 5 - Create OLAP schema, 6 - Create OLAP Database Objects, and 7 - Create Initial Data. Note that Option 7 can take up to 20 minutes to complete.

(Optional) Select Step 8, Sample Data Population. If you choose to skip this step, you can load the sample data later. (For more information about loading sample data, see Administration Guide for Oracle eBilling.)

Installation Guide for Oracle eBilling Version 6.0

25

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring the Oracle Database

10 Run Ant again, and select Option 2, Install OLTP from the Oracle eBilling DB Administration Main
Menu. The OLTP Install menu appears: [echo] [1]. Create OLTP Tablespaces [echo] [2]. Create OLTP Database Objects [echo] [3]. Create Initial Data [echo] [4]. Create Sample Data [echo] [5]. Export Database Data (optional) [echo] [Q]. Quit [input] Enter your selection (1,2,3,4,5,q,Q)

11 Select Option 1 - Create OLTP Tablespaces. This option creates new Oracle eBilling database
tablespaces, users, and rollback segment data files. When you see the final success message, press Enter to return to the Install menu.

12 Run Ant again and navigate back to the OLTP Install menu. Select Option 2 - Create OLTP
Database Objects. This option creates database tables and indexes. No user input is required. The error messages at the start of this step are an expected part of the process and can be ignored.

13 Run Ant again and navigate back to the OLTP Install menu. Select Option 3 - Create Initial Data.
This option compiles stored procedures to support database processing, and creates the initial data in some of the seed tables. No user input is required.

14 Run Ant again and navigate back to the OLTP Install menu. Select Option 4 - Create Sample Data. 15 (Optional) If you want a backup of the database, run Ant again and navigate back to the OLTP
Install menu. Select Option 5 - Export Database Data (Optional).

16 Install ETL. For details on installing ETL, see Chapter 4, Installing Oracle eBilling ETL.

Using the Automated Ant Targets


Instead of running manually performing each of the database setup steps, you can use the following Ant targets to automate the database creation process. You can use automated Ant targets to install the eStatement and ePayment database components and the eBilling database. Note that you must successfully create the eStatement and ePayment components before running the automated script for eBilling. As with the manual procedure, you must still update the corresponding properties files with the appropriate values before executing the scripts as described below. Use the usernames and passwords specified in the properties file when installing the databases.

26

Installation Guide for Oracle eBilling Version 6.0

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring the Oracle Database

Automated Ant Script for eStatement


To verify configuration parameters for eStatement 1
Verify that the following values in edxadmin_unix.properties (edxadmin.properties for Windows) are correct for the current installation. For Solaris, edxadmin_unix.properties can be found under $EDX_HOME/db/eStatement/oracle. For Windows, edxadmin.properties can be found under %EDX_HOME%\db\eStatement\oracle.

ORACLE_BASE and ORACLE_HOME locations OLTP database SID and username/password SYSDBA password and tnsnames for OLTP and OLAP Database file locations Redo file locations Trace file location

To run the automated Ant targets for eStatement 1


Change directory to the location of the Oracle eStatement Database installation files in your software installation: $EDX_HOME/db/eStatement/oracle (> cd %EDX_HOME%\db\eStatement\oracle on Windows) Run the install-new target to create a new OLTP instance, OLTP schema and eStatement schema objects (tables, indexes, packages, procedures, and so on). Run the following command: ant install-new

Or, on an existing instance, run the install-existing target to create an OLTP schema, eStatement Schema Objects (tables, indexes, packages, procedures, and so on). Run the following command: ant install-existing

Both install-new and install-existing also create initial data for eStatement.

Automated Ant Script for ePayment


To verify configuration parameters for ePayment 1
In the payusr.properties file, make sure that you give the same OLTP database SID and username and password that you specified in edxadmin.properties of the eStatement installation. payusr.properties can be found under $EDX_HOME/db/ePayment/oracle (%EDX_HOME%\db\epayment\oracle on Windows).

Installation Guide for Oracle eBilling Version 6.0

27

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring the Oracle Database

To run the automated Ant targets for ePayment 1


Change directory to the location of the Oracle ePayment Database installation files in your software installation: $EDX_HOME/db/ePayment/oracle (%EDX_HOME%\db\ePayment\oracle on Windows). Run the install-new target to create ePayment related database objects (tables, packages, procedures, and so on). This also creates the initial data for ePayment. Note that this does not create a new instance even though you are using install-new. ant install-new

Automated Ant Script for Oracle eBilling


Before running Ant, make sure that the edxadmin_unix.properties file (edxadmin.properties for Windows) is configured with the same OLTP and OLAP database SID, username, password, tnsnames and database file locations as you used for the eStatement component installation (for creating a new instance for OLAP and other database objects.)

To verify configuration parameters for Oracle eBilling 1


Verify that the following values in edxadmin_unix.properties (edxadmin.properties for Windows) are correct for the current installation. For Solaris, edxadmin_unix.properties can be found under $EDX_HOME/db/ebilling/oracle. For Windows, edxadmin.properties can be found under %EDX_HOME%\db\ebilling\oracle.

ORACLE_BASE and ORACLE_HOME locations OLTP and OLAP database SIDs, usernames and passwords, tnsnames SYSDBA password for OLTP and OLAP Database file locations Redo file locations Trace file location

To run the automated Ant targets for Oracle eBilling 1


Verify that you have completed the steps to install the eStatement and ePayment database components before installing eBilling.

28

Installation Guide for Oracle eBilling Version 6.0

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring the Oracle Database

Change directory to the location of the Oracle eBilling Database installation files in your software installation: $EDX_HOME/db/ebilling/oracle (%EDX_HOME%\db\ebilling\oracle on Windows). Run the install-new target to create new OLAP instance, OLAP schema, OLAP schema objects (tables, indexes, packages, procedures, and so on) and OLTP schema objects (pertaining to eBilling) using the SIDs specified in the properties file. (The OLTP instance was created during the eStatement database installation.) Note that this command does not create sample eBilling data for OLTP or OLAP. Run: ant install-new Or, use the install-existing target to create the OLAP schema, OLAP schema objects (tables, indexes, packages, procedures, and so on) and OLTP schema objects (pertaining to eBilling) on an existing instance with the usernames and passwords specified in the properties file. This command does not create the eBilling sample data for OLTP or OLAP. Run: ant install-existing If you want to install sample data (for both OLAP and OLTP), add the -DloadSampleData=true argument to the Ant call, for example: ant install-existing -DloadSampleData=true You can optionally run the OLAP-and OLTP-specific Ant build files, buildedxadmin.xml and buildedxolapadmin.xml. You can run any of the targets and flags using these instance-specific files with the -f <filename> flag. For example, to install a new OLAP instance with sample data only, you would run the following: ant install-new -f buildedxolapadmin.xml -DloadSampleData=true

3 4

Go to Chapter 4, Installing Oracle eBilling ETL and complete the steps to set up and install the ETL (the OWB Repository). After you have completed the ETL chapter, you must complete the ETL database installation using Ant. Change directory to the location of the Oracle eBilling Database installation files in your software installation: $ cd $EDX_HOME/db/ebilling/oracle (> cd %EDX_HOME%\db\ebilling\oracle on Windows). Type Ant and select Option 3 - Install ETL from the Oracle eBilling DB Administration Main Menu. The following options appear: [echo] [1]. Create ETL package. [echo] [2]. Import MDL [echo] [3]. OWB Mappings Deployment [echo] [Q]. Quit [input] Enter your selection (1, 2, 3, q, Q)

6 7 8

Select Option 1 - Create ETL package. This step adds new ETL tables into the OLAP database. Select Option 2 - Import MDL. This step imports mappings, process flow definitions, and so on from the MDL file into the OWB repository. Select Option 3 - OWB Mappings Deployment. This step deploys all the ETL mappings, process flows, and so on into the OWB repository.

Installation Guide for Oracle eBilling Version 6.0

29

Installing on WebLogic and Oracle Database (Solaris or Windows) Migrating from the CBA 5.1.1 Database to Oracle eBilling 6.0

Migrating from the CBA 5.1.1 Database to Oracle eBilling 6.0


If you are migrating from Oracle Communications Billing Analytics (CBA) 5.1.1 or CBA 5.1.1 QF2, follow these steps to migrate your database to eBilling 6.0. Be sure to back up your existing OLTP and OLAP databases before starting the migration process. In UNIX, be sure to log on as the ORACLE user for any migration activity.

Migrating the CBA 5.1.1 Database from Oracle 9i to Oracle 10.2.0.2 (UNIX and Windows)
To migrate the Oracle CBA 5.1.1 QF2 database from Oracle 9i to Oracle 10.2.0.2 1
Export your existing CBA 511 database (OLAP and OLTP) from Oracle9i: exp system/manager@olap_sid file=olap_export.dmp FULL=Y exp system/manager@oltp_sid file=oltp_export.dmp FULL=Y

2 3 4 5

Install Oracle10g (10.2.0.2) to upgrade your database software. Create a new Oracle10g database instance for OLAP and OLTP to migrate your databases (follow the procedures in this guide to create a new instance for both OLAP and OLTP). Create tablespaces/user in the new OLAP and OLTP databases (follow the steps in this guide to create tablespaces/users in the new OLAP and OLTP databases). Create the database link (TAM_LINK) in the OLTP schema (if it was not successfully created during the import):

Logon to the OLTP instance as SYSDBA and execute the following command: GRANT CREATE DATABASE LINK TO <OLTP_SCHEMA>;

b c

Change to the $EDX_HOME/db/ebilling/oracle (%EDX_HOME%\db\ebilling\oracle on Windows) folder. Logon to the OLTP schema using SQL*Plus (not as SYSDBA) and run the following SQL script at the SQL prompt providing the three input parameters: SQL> DROP DATABASE LINK TAM_LINK; SQL>@ crt_db_link.sql <Input1 - OLAP USER> <Input2 - OLAP Password> <Input3 - TNS name for OLAP instance >

Import your Oracle9i database into the new database: imp system/manager@olap_sid fromuser=olap touser=olap file=olap_export.dmp imp system/manager@oltp_sid fromuser=oltp touser=oltp file=olap_export.dmp

30

Installation Guide for Oracle eBilling Version 6.0

Installing on WebLogic and Oracle Database (Solaris or Windows) Migrating from the CBA 5.1.1 Database to Oracle eBilling 6.0

Migrating the CBA 5.1.1 eStatement Component to Oracle eBilling 6.0 (on UNIX and Windows)
To migrate the CBA 5.1.1 eStatement Component to eBilling 6.0 (on UNIX and Windows) 1
Change directory to: UNIX: $EDX_HOME/db/eStatement/oracle/migration Windows: %EDX_HOME%\db\eStatement\oracle\migration

Edit the migrate.properties file modifying the parameters in the following statements for your OLTP database environment. This file controls the eStatement database migration. DB_SID=EDX44 - Change the OLTP instance name. DB_USERNAME=edx_dba - Change the OLTP schema name. DB_PASSWORD=edx - Change the OLTP schema password.

Also in migrate.properties, specify the large data tablespace file location in the following statement: LARGE_DB_EDX_DATA_TB_FILE_LOC=/export/home/oracle/oradata

Specify the large index tablespace file location in the following statement: LARGE_DB_EDX_INDX_TB_FILE_LOC=/export/home/oracle/oradata

Specify the medium data tablespace file location in the following statement: MEDIUM_DB_EDX_DATA_TB_FILE_LOC=/export/home/oracle/oradata

6 7

Specify the medium index tablespace file location in the following location: MEDIUM_DB_EDX_INDX_TB_FILE_LOC=/export/home/oracle/oradata Change to your eStatement database home directory, for example: UNIX: $EDX_HOME/db/eStatement/oracle Windows: %EDX_HOME%\db\eStatement\oracle

Installation Guide for Oracle eBilling Version 6.0

31

Installing on WebLogic and Oracle Database (Solaris or Windows) Migrating from the CBA 5.1.1 Database to Oracle eBilling 6.0

Run the following Ant target to migrate. The install-migrate target migrates eStatement instances with the SIDs specified in the properties file: ant migrate The following message appears: get_backup_confirm: [echo] **Warning** [echo] We strongly advise a full backup of your existing [echo] database before applying the migration. [input] Do you have a backup(Y,y,N,n)

Enter Y if you have a backup, or N if you do not. The following menu appears: continue: [input] still continue with migration...(Y,y,N,n)

10 Enter Y to continue the migration process. The Migration Main Menu appears:
main: [echo] Migration Main Menu [echo] -----------------[echo] [1]. Migrate from 4.3.0.0 Migrate to 4.7.0.0 [echo] [Q]. Quit [input] Enter your selection(1,q,Q)

11 Select Option 1, Migrate from 4.3.0.0 Migrate to 4.7.0.0. The eStatement database migrates
from 4.3.0 to 4.7.0.

Installing the ePayment Database on an Existing Oracle CBA 5.1.1 OLTP Database
You must create an ePayment database on your existing CBA 5.1.1 OLTP database before migrating OLTP.

To install the ePayment database on an existing CBA 5.1.1 OLTP database 1 2


Go to the $EDX_HOME/db/ePayment/oracle folder (%EDX_HOME%\db\ePayment\oracle on Windows). Follow the steps described in Creating the Oracle ePayment Component Using Ant on page 22 to install the ePayment database component.

32

Installation Guide for Oracle eBilling Version 6.0

Installing on WebLogic and Oracle Database (Solaris or Windows) Migrating from the CBA 5.1.1 Database to Oracle eBilling 6.0

Migrating the CBA 5.1.1 OLTP Database to Oracle eBilling 6.0 OLTP on UNIX
To migrate the CBA 5.1.1 OLTP database to Oracle eBilling 6.0 on UNIX 1
Change to the migration directory $EDX_HOME/db/ebilling/oracle/oltp/migration/ 511_to_6.0 and make sure the following files exist: migrate_oltp_511_to_6.0.sh migrate_oltp_511_to_6.0.sql

Run the following commands at the shell prompt: chmod 777 migrate_oltp_511_to_6.0.sh ./migrate_oltp_511_to_6.0.sh

Provide the correct values for your environment: Enter Database ID - Enter the instance name, such as OLTP. Enter Database Username - Enter the Schema name, such as OLTP. Enter Database Password - Enter the Schema Password, such as OLTP. Enter SYS Password - Enter the password of the SYSDBA, such as change_on_install.

Check for errors in the following log files: db_oltp_migrate_511_6.0.log migrate_oltp_511_to_6.0.log

Note that after running the OLTP migration (migrate_oltp_511_to_6.0.sh), you will get the following error messages in the log file. Please ignore these errors. After compiling the schema, these errors will go away. Warning: Package Body created with compilation errors. Errors for PACKAGE BODY OLTP_PROD_LOADER_PKG: LINE/COL ERROR -------- ----------------------------------------------------------------400/6 PL/SQL: SQL Statement ignored 437/5 PL/SQL: ORA-00904: "SERVICE_FACT"."ETL_KEY": invalid identifier

Warning: Package Body created with compilation errors.

Installation Guide for Oracle eBilling Version 6.0

33

Installing on WebLogic and Oracle Database (Solaris or Windows) Migrating from the CBA 5.1.1 Database to Oracle eBilling 6.0

Errors for PACKAGE BODY PKG_COPY_HIERARCHY: LINE/COL ERROR -------- ----------------------------------------------------------------316/2 PL/SQL: Statement ignored 316/2 PLS-00905: object OLTP6.PR_COPY_ACCOUNT_WSPACE is invalid

Migrating CBA 5.1.1 OLTP to Oracle eBilling 6.0 OLTP on Windows


To migrate the CBA 5.1.1 to Oracle eBilling 6.0 OLTP database on Windows 1
Change to the migration directory %EDX_HOME%\db\ebilling\oracle\oltp\migration\511_to_6.0 and make sure the following file exists: migrate_oltp_511_to_6.0.sql

Run the userlock.sql command from SQL*Plus, providing the exact path of ORACLE_HOME: C:\set ORACLE_SID=oltp C:\sqlplus sys/<sys_password> as sysdba SQL> @ <Oracle_home path>\rdbms\admin\userlock.sql SQL> exit;

Run the migration script migrate_oltp_511_to_6.0.sql: C:\set ORACLE_SID=oltp C:\sqlplus oltp/oltp SQL> @ migrate_oltp_511_to_6.0.sql SQL> exit;

Verify that there were no Oracle errors in migrate_oltp_511_to_6.0.log. Note that after running the OLTP migration (migrate_oltp_511_to_6.0.sql), you will get the following error messages in the log file. Please ignore these errors. After compiling the schema, these errors will go away. Warning: Package Body created with compilation errors. Errors for PACKAGE BODY OLTP_PROD_LOADER_PKG: LINE/COL ERROR -------- -----------------------------------------------------------------

34

Installation Guide for Oracle eBilling Version 6.0

Installing on WebLogic and Oracle Database (Solaris or Windows) Migrating from the CBA 5.1.1 Database to Oracle eBilling 6.0

400/6 PL/SQL: SQL Statement ignored 437/5 PL/SQL: ORA-00904: "SERVICE_FACT"."ETL_KEY": invalid identifier

Warning: Package Body created with compilation errors. Errors for PACKAGE BODY PKG_COPY_HIERARCHY: LINE/COL ERROR -------- ----------------------------------------------------------------316/2 PL/SQL: Statement ignored 316/2 PLS-00905: object OLTP6.PR_COPY_ACCOUNT_WSPACE is invalid

Migrating the CBA 5.1.1 OLAP schema to Oracle eBilling 6.0 on UNIX
To migrate the CBA 5.1.1 OLAP schema to Oracle eBilling 6.0 on UNIX 1
Change to the <edx_home>\db\oracle\olap\migration\511_to_6.0 migration directory and make sure the following files exist: migrate_olap_511_to_6.0.sh migrate_olap_511_to_6.0.sql Create_Tables.sql Load_Data.sql Create_Sequences.sql Create_Procedure.sql Create_Views.sql Create_Indexes.sql Create_Constraints.sql dblink.sql

Login to the database as SYSDBA: $ export ORACLE_SID=myolap $ sqlplus /as sysdba

Grant the create materialized view privilege to the user you are migrating: SQL> grant create materialized view to <username>;

Installation Guide for Oracle eBilling Version 6.0

35

Installing on WebLogic and Oracle Database (Solaris or Windows) Migrating from the CBA 5.1.1 Database to Oracle eBilling 6.0

Modify the dblink.sql file with the following parameters: OLTP_USERNAME OLTP_PASSWORD OLTP_SID.

Log in to the OLAP database as the user who you are migrating, Run the following script to create the database link name OLTP_LINK (do not run the dblink.sql script as SYSDBA): dblink.sql

Execute the following commands at the shell prompt: chmod 777 migrate_oltp_511_to_6.0.sh ./migrate_oltp_511_to_6.0.sh

Provide the correct values for your environment: Enter OLAP Database SID - Enter the OLAP instance name, such as OLAP. Enter OLAP Database Username - Enter the OLAP schema name, such as OLAP. Enter OLAP Database Password - Enter the OLAP Schema Password, such as OLAP. Enter OLAP SYS Password - Enter the password of the SYSDBA, such as change_on_install Enter OLTP TNS Name - Enter the TNS name for OLTP, such as OLTP. Enter OLTP Database Username - Enter the OLTP schema name, such as OLTP. Enter OLTP Database Password - Enter the OLTP schema password, such as OLTP.

Check for errors in the following log files: db_olap_migrate_511_6.0.log migrate_olap_511_to_6.0.log

Migrating the CBA 5.1.1 OLAP Schema to Oracle eBilling 6.0 on Windows
To migrate the CBA 5.1.1 OLAP schema to Oracle eBilling 6.0 (on Windows) 1
Change to the <cba_install>\db\oracle\olap\migration\511_6.0 migration directory and make sure the following file exists: migrate_olap_511_to_6.0.sql

Login to the database as SYSDBA: $ export ORACLE_SID=myolap $ sqlplus /as sysdba

36

Installation Guide for Oracle eBilling Version 6.0

Installing on WebLogic and Oracle Database (Solaris or Windows) Migrating from the CBA 5.1.1 Database to Oracle eBilling 6.0

Grant the create materialized view privilege to the user you are migrating: SQL> grant create materialized view to <username>;

Modify the dblink.sql file with the following parameters: OLTP_USERNAME OLTP_PASSWORD OLTP_TNS_NAME

Log in to the OLAP database as the user you are migrating. Run the following script to create the database link name OLTP_LINK (do not run the dblink.sql script as SYSDBA): dblink.sql

Run the migrate_olap_511_to_6.0.sql script from SQL*Plus: C:\set ORACLE_SID=olap C:\sqlplus oltp/oltp SQL> @ migrate_olap_511_to_6.0.sql SQL> exit;

Make sure there are no Oracle errors in the migrate_olap_511_to_6.0.log file.

Compiling the Schema After the Successful Migration of OLTP and OLAP Databases
After successfully migrating the OLTP and OLAP databases, you must compile the schema.

To compile the schema after the successful migration of OLTP and OLAP 1 2 3
Go to the folder /opt/Oracle/eBilling/db/ebilling/oracle Logon to the OLTP schema using SQL*Plus (not as SYSDBA). Run the following commands: SQL>@ compile_schema.sql SQL>exit;

4 5

Logon to the OLAP schema using SQL*Plus (not as SYSDBA). Run the following commands: SQL>@ compile_schema.sql SQL>exit;

Installation Guide for Oracle eBilling Version 6.0

37

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring WebLogic

What to Do if the Database Configuration Fails


If you receive errors during database creation and configuration, you must first remove the partially configured database before configuring the database again.

Configuring WebLogic
This topic assumes in-depth understanding of and practical experience with application server administration. Consult the BEA WebLogic Server documentation as necessary. BEA WebLogic Server documentation is available at http://edocs.bea.com/wls/docs92/index.html You must start your BEA WebLogic Server instance and bring up the Administration Console before you begin this chapter. If you cannot bring up the Administration Console, you will be unable to proceed with configuring your application server for Oracle eBilling. If you have not already installed database server components and configured the database server for Oracle eBilling, do so now. For distributed environments, verify that you have any required database client software installed on the WebLogic Application Server and any other client machines of your database server. Note: The installation and configuration examples in this guide use default Oracle eBilling pathnames, privileges and permissions. If you choose not to accept the default values, ensure your values are consistent on all servers across your installation of Oracle eBilling. You must create three separate WebLogic domains, for: Oracle eBilling J2EE Applications Oracle eBilling Command Center Oracle eBilling CSR

Configuring WebLogic for the Oracle eBilling J2EE Applications EAR


Creating the WebLogic Domain for the eBilling J2EE Applications
You must create a WebLogic domain for the Oracle eBilling EAR.

To create a WebLogic domain for the Oracle eBilling EAR 1


For Solaris, run the following command from $WEBLOGIC_HOME/common/bin: ./config.sh For Windows, run the following command from %WEBLOGIC_HOM%E/common/bin: config.cmd

38

Installation Guide for Oracle eBilling Version 6.0

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring WebLogic

2 3 4 5 6 7

On the WebLogic Configuration Wizard select "Create a new WebLogic domain". Click Next. Leave the option to automatically configure the domain selected and click Next. Enter the username and password of the user to administer the WebLogic domain and click Next. Select the JDK to use for this domain and click Next. Choose No to skip configuring the WebLogic domain. Click Next. Enter the name of the domain to create, such as ebilling_domain, and enter a location for the domain (such as port 7001 and default Admin Server). Click Create.

Defining the WebLogic Environment for the eBilling Application Domain


You must set environment variables and other options in the WebLogic environment to correctly set up the eBilling J2EE domain.

To set environment variables for the WebLogic eBilling J2EE application domain 1
Open the setDomainEnv file in a text editor. This file is located in the domain's home directory, for example: Solaris: $BEA_HOME/user_projects/domains/ebilling_domain/bin/setDomainEnv.sh Windows: %BEA_HOME%\user_projects\domains\ebilling_domain\bin\setDomainEnv.cmd

Define the environment variable EDX_HOME as the directory in which Oracle eBilling is installed: Solaris: export EDX_HOME=/opt/Oracle/eBilling Windows: set EDX_HOME=C:\oracle\eBilling

Add the following entries to the file: Solaris: export CLASSPATH=$CLASSPATH:$EDX_HOME/config Windows: set CLASSPATH=%CLASSPATH%;%EDX_HOME%\config

Installation Guide for Oracle eBilling Version 6.0

39

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring WebLogic

In the JAVA OPTIONS section, add the Java option -Dedx.home=%EDX_HOME% to the end of the JAVA_VM variable definition. Solaris: JAVA_VM="${JAVA_VM} ${JAVA_DEBUG} ${JAVA_PROFILE} -Dedx.home=${EDX_HOME} Dlog4j.configuration=${EDX_HOME}/config/log4j.xml" export JAVA_VM Windows: set JAVA_VM=%JAVA_VM% %JAVA_DEBUG% %JAVA_PROFILE% -Dedx.home=%EDX_HOME% -Dlog4j.configuration = file:%EDX_HOME%/config/log4j.xml

Save the changes and close the file.

Configuring JDBC Resources for Oracle eBilling


You must configure JDBC resources for J2EE applications deployed with BEA WebLogic Server 9.2 using the WebLogic Administration Console. You must create three Data sources for the eBilling application as shown in Tables 2 and 3.

Table 2. Name

Data Sources for the eBilling Application JNDI Name edx.databasePool edx.xma.databasePool edx.report.databasePool Transaction Emulate Two-Phase Commit

edxAdminDataSource edxXMADataSource reportDataSource

To create three data sources for the Oracle eBilling application 1 2


For all Data Sources Select Database Type as Oracle and Database Driver as shown in the following table and click Next. Select Check box Supports Global Transactions for all Data Sources and select the corresponding Transaction option.

Table 3. Name

Data Source Detail for the eBilling Application Driver Class Name oracle.jdbc.OracleDriver oracle.jdbc.xa.client.OracleXADataSource oracle.jdbc.xa.client.OracleXADataSource Database oltp olap oltp

edxAdminDataSource olapConnectionPool oltpConnectionPool

40

Installation Guide for Oracle eBilling Version 6.0

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring WebLogic

For Connection Properties provide the correct value:

Table 4.

Connection Properties

Connection Properties Database Name Host Name Port Database User Name Password Your Oracle Database Alias Name Your Oracle Database server host name DB server listening port Your Oracle Database User Name Your Oracle Database Password

Select your target server and click Finish. Default is AdminServer.

To create a JDBC data source for Oracle eBilling 1 2 3 4 5 6 7 8 9


Start the newly created Oracle eBilling domain and open the administration console in a browser. The default URL is http://<server-name>:<server-port>/console. Log in to the console using the username and password defined when the domain was created. Click Lock and Edit to allow you to make configuration changes. Click Data Sources under JDBC in the services section. Click New to create a new data source. Enter the data source name and JNDI name. For each data source, select Oracle as the Database Type and select the appropriate driver. Click Next. Leave the default transaction options unchanged and click Next. On the Connections Properties page, enter the database name (SID), hostname, port number and user credentials. Click Next. Next.

10 Click Test Configuration to test whether the database connection is configured correctly. Click 11 Target the data source to the Oracle eBilling domain. Click Finish. 12 Click Activate Changes to commit the changes. 13 Repeat from Step 5 to create each data source.

Configuring JMS Resources for Oracle eBilling


You must configure JMS resources for J2EE applications deployed with BEA WebLogic Server 9.2 using the WebLogic Administration Console.

Installation Guide for Oracle eBilling Version 6.0

41

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring WebLogic

JMS Persistence Store for eBilling

To configure JMS Persistence Store 1 2 3


Select the Services->Persistence Stores. Select New->Create File Store. Create the file store with appropriate values as shown in the following table:

Table 5. Name

MS Persistence Store Values for the eBilling Application Target Select Your Server (AdminServer) Directory Directory Location to Save Store

EventsFileStore

JMS Servers for Oracle eBilling

To configure JMS Servers 1 2


Select the Services->Messaging->JMS Servers->New Create a JMS Server using the values as shown in the following table:

Table 6. Name

MS Server Values for the eBilling Application Persistence Store EventsFileStore Target Select Your Server (AdminServer)

EventJMSServer

JMS Connection Factories for Oracle eBilling

To create the JMS module 1 2 3 4


Click the JMS Modules link on the Administration Console page for the Oracle eBilling domain. Click Lock and Edit to allow configuration changes to be made. Click New to create a new JMS module. Set the name of the JMS system module and provide the other JMS module properties as shown in the table below. Click Next. Select the check boxes to target the system module at the servers running the Oracle eBilling application. Click Next.

42

Installation Guide for Oracle eBilling Version 6.0

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring WebLogic

Click Finish.

Table 7. Property Name

JMS Module Values for the Oracle eBilling Application Description Your JMS Module Name Your Descriptor File Name Your Location in Domain Select Your Server Example Factories Factories Factories AdminServer

Descriptor File Name Location in Domain Targets

To create JMS Queue Connection Factories 1 2 3 4 5


Click the JMS Modules link on the Administration Console page for the Oracle eBilling domain. Click Lock and Edit to allow configuration changes to be made. Click the module link. Click New. Select the radio button next to Connection Factory and click Next. Enter the connection factory name and JNDI name for the connection factory, using the following parameters. Click Finish.

Table 8.

JMS Queue Connection Factory Values for the eBilling Application Name EventsConnectionFactory JNDI Name edx.qcf Target Select Your Server (AdminServer)

Connection Factory Type Queue

Select created connection factory and enable XA Transaction under Transactions tab.

JMS Queue for Oracle eBilling

To add the JMS Queue Destination 1 2 3 4


Click the JMS Modules link on the Administration Console page for the Oracle eBilling domain. Click Lock and Edit to allow configuration changes to be made. Click the module link. Click New. Select the radio button next to Queue and click Next.

Installation Guide for Oracle eBilling Version 6.0

43

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring WebLogic

Enter the queue name and JNDI name for the queue, using the following parameters. Click Next.

Table 9.

JMS Queue Destination Values for the Oracle eBilling Application Name EventsQueue JNDI Name edx.queue.outbound Target EventsJMSServer

Destination Type Queue

6 7 8 9

Click Create a New Subdeployment. WebLogic shows the newly created queue name as Subdeployment Name. Accept it and Click OK. (If you plan to add more JMS resources into the subdeployment, you can rename it.) Select the newly created Subdeployment and Corresponding target JMS Server (EventsJMSServer). Click Activate Changes to commit changes after the JMS configuration is complete.

Setting up a Foreign JMS Server for Oracle eBilling You must set up a Foreign JMS for batch reporting to process correctly.

To add the Foreign Server 1 2 3


Create a new JMS Module targeted to your server (AdminServer). Add a Foreign Server in the JMS Module you just created targeted to your server (AdminServer). You do not need to specify a JNDI name for the Foreign Server. Click the Foreign Server, under the General tab, and enter t3://<commandcenter-appserverName:portNumber> in the JNDI Connection URL field, for example: t3://localhost:7003

Under Destinations tab, create a new Foreign Destinations using the following values:

Table 10. Name

Foreign Destination Values for the Oracle eBilling Application Local JNDI Name edx.foreign.queue.outbound Remote JNDI Name edx.queue.outbound

ForeignDestination

Under Connection Factories tab, create a new Foreign Connection Factory using the following values:

Table 11. Name

Foreign Connection Factory Values for the Oracle eBilling Application Local JNDI Name edx.foreign.qcf Remote JNDI Name edx.qcf

ForeignConnectionFactory

44

Installation Guide for Oracle eBilling Version 6.0

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring WebLogic

Configuring WebLogic for the Oracle eBilling Command Center EAR


Creating the WebLogic Domain for Command Center
You must create a WebLogic domain for the Oracle eBilling Command Center EAR.

To create a WebLogic domain for the Oracle eBilling Command Center EAR 1
For Solaris, run: ./config.sh For Windows, run: .\config.cmd

2 3 4 5 6 7

On the WebLogic Configuration Wizard select "Create a new WebLogic domain". Click Next. Leave the option to automatically configure the domain selected and click Next. Enter the username and password of the user to administer the WebLogic domain and click Next. Select the JDK to use for this domain and click Next. Choose No to skip configuring the WebLogic domain. Click Next. Enter the name of the domain to create, such as cc_domain, use the Customize Environment and Services Settings to configure the port to 7003 and the default Admin Server. Click Create.

Defining the WebLogic Environment for the Command Center Domain


You must set environment variables and other options in WebLogic environment for Command Center.

To set environment variables for the WebLogic Oracle eBilling J2EE applications domain 1
Open the file setDomainEnv in a text editor. This file is located in the domain's home directory, for example: Solaris: /opt/bea/user_projects/domains/cc_domain/bin/setDomainEnv.sh Windows: C:\bea\user_projects\domains\cc_domain\bin\setDomainEnv.cmd

Installation Guide for Oracle eBilling Version 6.0

45

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring WebLogic

Define the environment variable EDX_HOME as the directory in which Oracle eBilling is installed: Solaris: export EDX_HOME=/opt/Oracle/eBilling Windows: set EDX_HOME=C:\oracle\eBilling

Add the following entries to the file: Solaris: export CLASSPATH=$CLASSPATH:$EDX_HOME/config Windows: set CLASSPATH=%CLASSPATH%;%EDX_HOME%\config

In the JAVA OPTIONS section, add the Java option -Dedx.home=%EDX_HOME% to the end of the JAVA_VM variable definition. set JAVA_VM=%JAVA_VM% %JAVA_DEBUG% %JAVA_PROFILE% -Dedx.home=%EDX_HOME% Dedx.log4jconfigfile=log4j_ccenter.xml = file:log4j_ccenter.xml

Save the changes and close the file.

Configuring JDBC Resources for Command Center


You must configure JDBC resources for the Command Center application deployed with BEA WebLogic Server 9.2 using the WebLogic Administration Console. You must configure the following data sources (five data sources for running eBilling jobs and two for running the reporting application):

Table 12.

Data Sources for the Command Center Application JNDI Name edx.databasePool edx.logger.databasePool edx.messaging.databasePool edx.xma.databasePool edx.user.databasePool edx.report.databasePool Emulate Two-Phase Commit Transaction Emulate Two-Phase Commit Emulate Two-Phase Commit

Data Source Name edxAdminDataSource edxLoggerDataSource edxMessagingDataSource edxXMADataSource edxUserDataSource reportDataSource

To create data sources for the Oracle eBilling Command Center domain 1
Start the newly created Oracle eBilling Command Center domain and open the administration console in a browser. The default URL is http://<server-name>:<server-port>/console.

46

Installation Guide for Oracle eBilling Version 6.0

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring WebLogic

2 3 4 5 6 7

Log in to the console using the username and password defined when the domain was created. Click Lock and Edit to allow you to make configuration changes. Click the Data Sources link under JDBC in the services section. Click New to create a new data source. Enter the data source name and JNDI name. For all data sources, select Oracle as the Database Type and select the Database Driver. Click Next.

Table 13.

Driver Class Names for the Command Center Data Sources Driver oracle.jdbc.OracleDriver oracle.jdbc.OracleDriver oracle.jdbc.xa.client.OracleXADataSource oracle.jdbc.xa.client.OracleXADataSource oracle.jdbc.OracleDriver oracle.jdbc.xa.client.OracleXADataSource oracle.jdbc.OracleDriver Database oltp oltp oltp oltp oltp olap oltp

Data Source Name edxAdminDataSource edxLoggerDataSource edxMessagingDataSource edxXMADataSource edxUserDataSource reportDataSource edxAdminDataSource

8 9

Select "Supports Global Transactions" for all Data Sources and select the corresponding transaction option and click Next. On the Connections Properties page, provide the correct values for the following properties:

Table 14.

Connection Property Values for the Command Center Data Sources Description Your Oracle Database Alias Name Your Oracle Database Server Host Name Database Server Listening Port Your Oracle Database User Name Your Oracle Database Password

Connection Property Database Name Host Name Port Database User Name Password

10 Click Test Configuration to test whether the database connection is configured correctly. Click
Next.

11 Target the data source to the Oracle eBilling Command Center domain. 12 Click Finish. 13 Click Activate Changes to commit the changes.
Installation Guide for Oracle eBilling Version 6.0 47

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring WebLogic

Configuring JMS Resources for Command Center


To configure the connection pools for Command Center 1 2 3
Go to the Summary of JDBC Data Sources. Click any datasource name link. On the Connection Pool tab, enter the values for the connection pool settings for each JDBC data source you created:

Table 15. Property

Connection Pool Settings for Command Center Data Sources Value 5 20 5 FIXED 300 Selected 120 DUAL 15 1

Initial Capacity Maximum Capacity Capacity Increment Statement Cache Type Statement Cache Size Text Connections on Reserve Test Frequency Test Table Name Shrink Frequency Login Delay

JMS Connection Factories for Command Center To create JMS Connection factories you must first create the Module.

To create the JMS module 1 2 3


Click Services, Messaging, and the JMS Modules link on the Administration Console page for the Oracle eBilling domain. Click Lock and Edit to allow configuration changes to be made. Click New to create a new JMS module. Set the name of the JMS system module and provide the other JMS module properties. Click Next.

Table 16. Property Name

JMS Module Properties for the Command Center Application Description Your JMS Module Name Your Descriptor File Name Example Factories Factories

Descriptor File Name

48

Installation Guide for Oracle eBilling Version 6.0

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring WebLogic

Table 16. Property

JMS Module Properties for the Command Center Application Description Your Location in Domain Select Your Server Example Factories AdminServer

Location in Domain Targets

4 5

Select the check boxes to target the system module at the servers running the Oracle eBilling application. Click Next. Click Finish.

To create JMS Queue Connection Factories 1 2 3 4 5


Click the JMS Modules link on the Administration Console page for the Oracle Command Center domain. Click Lock and Edit to allow configuration changes to be made. Click the module link. Click New. Select the radio button next to Connection Factory and click Next. Add two Connection Factories using the following parameters. Click Finish.

Table 17.

Connection Factory Values for the Command Center Application Name LoggerConnectionFactory EventsConnectionFactory JNDI Name edx.lcf edx.qcf Target Select Your Server (AdminServer) Select Your Server

Connection Factory Type Queue Queue

Select created connection factory and enable XA Transaction under Transactions tab.

JMS Persistence Store for Command Center

To configure JMS Persistence Store 1 2


Select Services->Persistence Stores. Select New->Create File Store.

Installation Guide for Oracle eBilling Version 6.0

49

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring WebLogic

Create two file stores with the values shown here:

Table 18. Name

JMS Persistence Store Values for the Command Center Application Target Select Your Server (AdminServer) Select Your Server (AdminServer) Directory Directory Location to save Store Directory Location to Save Store

LoggerFileStore EventsFileStore

JMS Servers for Command Center

To configure JMS Servers 1 2


Select the Services->Messaging->JMS Servers->New Create two JMS Servers using the following values:

Table 19. Name

JMS Server Values for the Command Center Application Persistent Store LoggerFileStore EventsFileStore Target Select Your Server (AdminServer) Select Your Server (AdminServer)

LoggerJMSServer EventsJMSServer

JMS Queues for Command Center You must create two JMS queues for the Command Center application.

To add the JMS Queue Destinations 1 2 3 4 5


Click the JMS Modules link on the Administration Console page for the Oracle eBilling domain. Click Lock and Edit to allow configuration changes to be made. Click the module link. Click New. Select the radio button next to Queue and click Next. Provide the Queue Name and JNDI Name as shown in the following table. Click Next.

Table 20. Name

Queue and JNDI Names for the Command Center Application JNDI Name edx.queue.logger edx.queue.outbound Target LoggerJMSServer EventsJMSServer

LoggerQueue EventsQueue

50

Installation Guide for Oracle eBilling Version 6.0

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring WebLogic

6 7 8 9

Click Create a New Subdeployment. WebLogic shows the newly created queue name as Subdeployment Name. Accept it and Click OK. (If you plan to add more JMS resources into the subdeployment, you can rename it.) Select the newly created Subdeployment and the corresponding target JMS Server. Repeat this process for the second JMS queue shown in the table.

10 Click Activate Changes to commit changes after the JMS configuration is complete.
Foreign JMS Server For batch reporting to process correctly, you must set up a Foreign JMS Server in the Command Center domain to retrieve the JMS messages sent in the eBilling domain.

To create a Foreign JMS Server 1 2 3


Create a new JMS Module targeted to your server (AdminServer). Add a Foreign Server in the JMS Module just created and targeted to your server (AdminServer). There is no need to specify a JNDI name for the Foreign Server. Click the Foreign Server, General tab, and in the JNDI Connection URL field, enter: t3://<eBilling-app-serverName:portNumber> For example, t3://localhost:7001

Under the Destinations tab, create a new Foreign Destinations, with the following values:

Table 21. Name

Foreign Destination Values for Command Center Local JNDI Name edx.foreign.queue.outbound Remote JNDI Name edx.queue.outbound

ccForeignDestination

Under Connection Factories tab, create a new Foreign Connection Factory with the following values:

Table 22. Name

Foreign Connection Factory Values for the Command Center Application Local JNDI Name edx.foreign.qcf Remote JNDI Name edx.qcf

ccForeignConnectionFactory

Editing edx_config (or edx.config.bat) and edx_env.bat for Command Center


You must edit the edx_config (edx.config.bat on Windows) configuration file to set jar classpaths. Windows users must also edit the edx_env.bat configuration file.

Installation Guide for Oracle eBilling Version 6.0

51

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring WebLogic

To edit edx_config (edx.config.bat on Windows) 1


Edit $EDX_HOME/bin/edx_config (%EDX_HOME%\config\edx.config.bat on Windows) and add following entries: Solaris: CLASSPATH=${CLASSPATH}${CLASSPATHSEP}${EDX_HOME}/config export CLASSPATH

Windows: @set CLASSPATH=%CLASSPATH%;%EDX_HOME%

To edit edx_env.bat (Windows only) 1


Edit %EDX_HOME%\config\edx_env.bat and add following entries: @Set EDX_HOME=d:\oracle\ebilling @set APP_SERVER=wl @set WL_HOME= D:\bea92\weblogic92

Configuring WebLogic for the Oracle eBilling CSR EAR


Creating the WebLogic Domain for the Oracle eBilling CSR Application
You must create a WebLogic domain for the Oracle eBilling CSR EAR.

To create a WebLogic domain for the Oracle eBilling CSR EAR 1


For Solaris, run: ./config.sh For Windows, run: config.cmd

2 3 4 5 6 7

On the WebLogic Configuration Wizard select "Create a new WebLogic domain". Click Next. Leave the option to automatically configure the domain selected and click Next. Enter the username and password of the user to administer the WebLogic domain and click Next. Select the JDK to use for this domain and click Next. Choose No to skip configuring the WebLogic domain. Click Next. Enter the name of the domain to create, such as CSR_domain, and enter a location for the domain (such as port 7006 and default Admin Server). Click Create.

52

Installation Guide for Oracle eBilling Version 6.0

Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring WebLogic

Defining the WebLogic Environment for the CSR Domain


You must set environment variables and other options in the WebLogic environment to correctly set up the CSR domain.

To set environment variables for the WebLogic CSR domain 1


Open the setDomainEnv file in a text editor. This file is located in the domain's home directory, for example: Solaris: /opt/bea/user_projects/domains/csr_domain/bin/setDomainEnv.sh Windows: C:\bea\user_projects\domains\csr_domain\bin\setDomainEnv.cmd

Define the environment variable EDX_HOME as the directory in which Oracle eBilling is installed: Solaris: export EDX_HOME=/opt/Oracle/eBilling Windows: set EDX_HOME=C:\oracle\eBilling

Add the following entries to the file: Solaris: export CLASSPATH=$CLASSPATH;$EDX_HOME/config Windows: set CLASSPATH=%CLASSPATH%;%EDX_HOME%\config

In the JAVA OPTIONS section, add the Java option -Dedx.home=%EDX_HOME% to the end of the JAVA_VM variable definition. Solaris: JAVA_VM="${JAVA_VM} ${JAVA_DEBUG} ${JAVA_PROFILE} -Dedx.home=${EDX_HOME} Dlog4j.configuration=${EDX_HOME}/config/log4j_csr.xml" export JAVA_VM Windows: set JAVA_VM=%JAVA_VM% %JAVA_DEBUG% %JAVA_PROFILE% -Dedx.home=%EDX_HOME% -Dlog4j.configuration = file:%EDX_HOME%/config/log4j_csr.xml

Save the changes and close the file.

Installation Guide for Oracle eBilling Version 6.0

53

Installing on WebLogic and Oracle Database (Solaris or Windows) Repackaging LGPL

Access WebLogic Console

To access the WebLogic console after the server is up running 1


Use the following URL: http://localhost:7006/console Where localhost:7006 is the server name and application port number where you installed the CSR application.

Configuring JDBC Resources for CSR


Set the same data sources and connection pool settings for CSR as you did for the Oracle eBilling J2EE application. Go to Configuring JDBC Resources for Oracle eBilling on page 40.

Configuring JMS Resources for CSR


No JMS configuration is required for CSR.

Modifying csr.xma.xml for CSR


You must modify the CSR URL in the csr.xma.xml file.

To modify csr.xma.xml 1 2
In $EDX_HOME/xma/config/modules/application/csr (%EDX_HOME%\xma\config\modules\application\csr on Windows), open csr.xma.xml. Modify the "custAppURL" property to point to the correct server name or IP address where the eBilling CSR application is deployed. This URL string is used by CSR to impersonate users. The default is: http://localhost:7001/ebilling/j_acegi_security_check?

Repackaging LGPL
You must repackage LGPL (GNU Lesser General Public License) on your Oracle eBilling system (all platforms). Before you can repackage the LGPL, you must have Maven set up on your system.

To set up Maven2 on your system 1 2


Go to http://maven.apache.org and download Maven 2.0.7. (Oracle eBilling also supports versions 2.0.5 and 2.0.6.) Unzip the downloaded archive to your local Maven home directory (such as maven-2.0.7).

54

Installation Guide for Oracle eBilling Version 6.0

Installing on WebLogic and Oracle Database (Solaris or Windows) Repackaging LGPL

Create the environment variable M2_HOME, for example: Solaris: export M2_HOME=<mven_home_dir> Windows: set M2_HOME=<mven_home_dir>

Add the bin directory from M2_HOME to a PATH variable: Solaris: export PATH=$M2_HOME/bin:$PATH; Windows: set PATH=%M2_HOME%\bin;%PATH%

If your computer does not have direct access to the Internet, set up a proxy in the Maven configuration.

To set up a proxy Maven configuration 1


Edit file %M2_HOME%/conf/settings.xml (or %M2_HOME%\conf\settings.xml for Windows) and add lines below into appropriate section of your settings.xml: <settings> . . <proxies> <proxy> <active>true</active> <protocol>http</protocol> <host>www-proxy.us.oracle.com</host> <port>80</port> <nonProxyHosts>localhost|*.siebel.com|*.corp.siebel.com|*.oraclecorp.com</ nonProxyHosts> </proxy> </proxies> . . </settings>

Installation Guide for Oracle eBilling Version 6.0

55

Installing on WebLogic and Oracle Database (Solaris or Windows) Repackaging LGPL

To repackage LGPL 1 2
Change the directory to $EDX_HOME/repackage (or %EDX_HOME%\repackage in Windows). Run the following Maven installation command: mvn install This command places all EAR files in the packaged LGPL libraries in the $EDX_HOME/J2EEApps directory (or %EDX_HOME%\J2EEApps in Windows). If you receive an error similar to this one, or any error indicating jars are missing, the command was not able to access and download LGPL components from the Internet. Follow the instructions in this chapter to manually download and install these components.

[INFO] --------------------------------------------------------------------------[INFO] Building eBilling application [INFO] task-segment: [install]

[INFO] --------------------------------------------------------------------------[INFO] -----------------------------------------------------------------------[ERROR] BUILD ERROR [INFO] -----------------------------------------------------------------------[INFO] Failed to resolve artifact.

To manually download and install the required LGPL jars 1 2


Go to the following location and download swarmcache-1.0RC2.jar: http://mirrors.ibiblio.org/pub/mirrors/maven2/swarmcache/swarmcache/1.0RC2/ Install swarmcache-1.0RC2.jar using the following command: mvn install:install-file -DgroupId=swarmcache -DartifactId=swarmcache \ -Dversion=1.0RC2 -Dpackaging=jar -Dfile=/path/to/file

Go to the following location and download hibernate-3.1.3.jar http://mirrors.ibiblio.org/pub/mirrors/maven2/org/hibernate/hibernate/3.1.3/

Install hibernate-3.1.3.jar using the following command: mvn install:install-file -DgroupId=org.hibernate -DartifactId=hibernate \ -Dversion=3.1.3 -Dpackaging=jar -Dfile=/path/to/file

56

Installation Guide for Oracle eBilling Version 6.0

Installing on WebLogic and Oracle Database (Solaris or Windows) Deploying Oracle eBilling Applications on Solaris or Windows

Go to the following location and download jgroups-all-2.4.1.jar: http://mirrors.ibiblio.org/pub/mirrors/maven2/jgroups/jgroups-all/2.4.1/

Install jgroups-all-2.4.1.jar using the following command: mvn install:install-file -DgroupId=jgroups -DartifactId=jgroups-all \ -Dversion=2.4.1 -Dpackaging=jar -Dfile=/path/to/file

Repackage LGPL.

Deploying Oracle eBilling Applications on Solaris or Windows


You must deploy each of the three J2EE application EAR files using your application server: Table 23. Oracle eBilling Application File Names on WebLogic File Name and Location Solaris: $EDX_HOME/eBilling/J2EEApps/ebilling/weblogic/ ebilling-weblogic-9-6.0.EAR Windows: %EDX_HOME%\eBilling\J2EEApps\ebilling\weblogic\ebillingweblogic-9-6.0.EAR Command Center Solaris: $EDX_HOME/J2EEApps/commandcenter/weblogic/commandcenter-weblogic-9-6.0.EAR Windows: %EDX_HOME%\J2EEApps\commandcenter\weblogic\commandcenter-weblogic-9-6.0.EAR CSR Application Solaris: $EDX_HOME/J2EEApps/csr/weblogic/csr-weblogic6.0.EAR Windows: %EDX_HOME%\J2EEApps\csr\weblogic\csr-weblogic6.0.EAR

eBilling Applications eBilling Application

To deploy an EAR file on WebLogic 1 2


Open the WebLogic Administration Console and click Lock and Edit. Click the Deployments link to display the deployments page for the WebLogic domain for the particular application you are deploying, such as ebilling_domain. Click New to launch the Install Application Assistant, which guides you through the steps required to deploy the application. Click the links to navigate to the location of the application EAR file to deploy, such as (Solaris): $EDX_HOME/eBilling/J2EEApps/ebilling/weblogic/ebilling-weblogic-9-6.0.EAR

Select the deployed EAR and start all services located at the Start > Servicing all requests.

Installation Guide for Oracle eBilling Version 6.0

57

Installing on WebLogic and Oracle Database (Solaris or Windows) Running Scheduler

Restart the server.

Repeat this procedure for each Oracle eBilling application.

Running Scheduler
The Oracle eBilling scheduler manages the Command Center jobs. Scheduler must be running for scheduled jobs to execute. For information on running the PWC job scheduler, see Administration Guide for Oracle eBilling.

To start the Scheduler on Windows or Solaris 1 2


On the command line, change to the directory $EDX_HOME/bin (%EDX_HOME%\bin on Windows). Run the following command (Solaris only): $./edx_config

Run the following command: ./wl_scheduler -start -url t3://localhost:7003 -verbose Note that localhost is the application server name and 7003 is the port number of the Command

To stop the Scheduler, replace the -start parameter with the -stop parameter. ./wl_scheduler -stop -url t3://localhost:7003 -verbose

Running the eBilling Applications


After successfully deploying the applications, you can log in to the sample Oracle eBilling applications.

To log in to a sample Oracle eBilling application 1


In your browser, point to one of the following applications, where localhost:7001 is the server name and application port number where you installed the application (either the eBilling, Command Center, or CSR applications).

Table 24.

Sample Oracle eBilling Application URLs URL Example http://localhost:7001/ebilling http://localhost:7003/ebilling http://localhost:7006/ebillingcsr

Sample Application eBilling Command Center CSR

The sample login page appears for the particular application.

58

Installation Guide for Oracle eBilling Version 6.0

Installing on WebLogic and Oracle Database (Solaris or Windows) Running the eBilling Applications

For the sample eBilling application, log in as an administrator using the one of the following admin or user roles. Note that the user you log in as determines whether you see the Business (B2B) or Consumer (B2C) Edition of the eBilling application:

Table 25.

Sample Usernames and Passwords Provided for the eBilling Application Password jsmith ftown twalsh tbrown Role Admin B2B Admin User B2C User B2C User

Username jsmith ftown twalsh tbrown

For the Command Center, log using the user name "admin" and the password "Oracle. For the CSR application, use the username "edocsadmin" and password "111111".

Installation Guide for Oracle eBilling Version 6.0

59

Installing on WebLogic and Oracle Database (Solaris or Windows) Running the eBilling Applications

60

Installation Guide for Oracle eBilling Version 6.0

Installing on Linux, Oracle Database, and Oracle Application Server

This chapter describes how to install Oracle eBilling on Linux using the Oracle Database and Oracle Application Server. It includes the following topics: About Installing on Oracle Application Server Managing the Oracle Application Server Environment Installing Oracle eBilling Software Configuring the Oracle Application Server for Linux Modifying persistence.xma.xml Repackaging LGPL Deploying Oracle eBilling Applications for Linux on OAS Running Scheduler on Linux and OAS Running the eBilling Applications on Linux and OAS

About Installing on Oracle Application Server


This guide assumes that you have an in-depth understanding of and practical experience with administrating your operating system. Consult your system documentation as necessary. Oracle Application Server 10g provides a complete Java 2, Enterprise Edition (J2EE) environment written entirely in Java that executes on the Java Virtual Machine (JVM) of the standard Java Development Kit (JDK). You can run Oracle Application Server Containers for J2EE 10g (OC4J) on the standard JDK that exists on your operating system. OC4J is a fast, lightweight, highly scalable, and easy-to-use J2EE server that is fully J2EE 1.3 compatible. Oracle Application Server 10g is built entirely on a J2EE framework that supports the latest industry standard technologies and programming languages, including J2EE API specifications, XML, and Web services. This comprehensive and flexible framework enables you to design, develop, and deploy dynamic Web sites, portals, and transactional applications by using familiar programming languages and technologies such as servlets, Java Server pages, XML, PL/SQL Server Pages, and SOAP. Oracle Application Server 10g also provides comprehensive Web services to expose business functions to authorized parties over the Internet from any Web device.

Installation Guide for Oracle eBilling Version 6.0

61

Installing on Linux, Oracle Database, and Oracle Application Server Managing the Oracle Application Server Environment

Managing the Oracle Application Server Environment


The Oracle Application Server 10g environment is managed by Oracle Enterprise Manager 10g Application Server Control. Using the Web-based Application Server Control Console, administrators can: Manage and configure application server components Monitor server performance Access a graphical view of their server environment Deploy and monitor J2EE applications Manage port values across application server components View server and application diagnostic logs

This document explains the configuration steps specific to Oracle Application Server 10g (R3) Version 10.1.3.2. This guide is intended for system administrators and other technical personnel responsible for installing, configuring, and maintaining Oracle Application Server. TIP: Oracle Corporation recommends you implement the Optimal Flexible Architecture (OFA) standard when you install Oracle products.

Installing Oracle eBilling Software


Oracle eBilling is distributed as an InstallAnywhere package. You can change the default installation directory when prompted during the installation procedure. This document refers to the directory where you install Oracle eBilling as the EDX_HOME directory, by default /opt/Oracle/eBilling. Scripts for database creation and configuration can be found at /opt/Oracle/eBilling/db. Web applications to be deployed to your application server can be found at /opt/Oracle/eBilling/ J2EEApps.

To install the Oracle eBilling software using InstallAnywhere 1 2 3 4 5


Log in using the user and group name of the application server owner, such as edxadmin:edxadmin. Launch InstallAnywhere by typing eBilling.bin. Make sure DISPLAY is set. (To install in console mode, type ./eBilling -i console. Follow the on-screen instructions instead of these steps.) On the Introduction screen, read the Oracle eBilling introductory information. Click Enter to continue. On the License Agreement screen, read the licensing agreement carefully, accept the agreement, then click Enter. On the Enter Serial Number screen, enter your product serial number. Then click Enter.

62

Installation Guide for Oracle eBilling Version 6.0

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Database for Linux

On the Owner of Web Application Server screen, enter the name of the application server owner (if you have installed other Oracle Self-Service products, use the same owner here that you used for those product installations). Then click Enter. On the Group of Web Application Server screen, enter the name of the group for the application server (if you have installed other Oracle Self-Service products, use the same group here that you used for those product installations). Then click Enter. On the Choose Install Folder screen, accept the default installation folder or click Choose and enter the directory where you want to install the Oracle eBilling files and directories. (This document refers to that directory as EDX_HOME.) Click Next to continue. On the Choose Product Features screen, click eBilling Group, then click Enter.

10 Choose a folder where shortcuts will be installed and click Enter. 11 On the Pre-Installation Summary screen, verify that the information is correct, and click Install.
To correct any entries, click Previous. The installer copies the Oracle eBilling software components to the designated installation folder. A status bar on the bottom of the screen shows each component being installed. If installation is successful, you see a congratulatory message and the directory that contains the Oracle eBilling components.

12 Click Done to exit the installer.


If the installation fails, determine the cause of the problem and run InstallAnywhere again to reinstall Oracle eBilling.

Configuring the Oracle Database for Linux


You must configure your Oracle database for use on Linux.

To configure the Oracle database for Linux 1 2


Use the database configuration and migration procedures given for Solaris. See Configuring the Oracle Database on page 16. When creating the eStatement, ePayment, and eBilling database components, replace this WebLogic statement: export JAVA_HOME=$BEA_HOME/JDK150_04 With the following statement: export JAVA_HOME=/export/home/oracle/oas/10.1.3.2/jdk

Installation Guide for Oracle eBilling Version 6.0

63

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux

Configuring the Oracle Application Server for Linux


This topic provides a step-by-step guide to configuring the application tier of Oracle eBilling. It assumes an in-depth understanding of and practical experience with application server administration. Consult the Oracle Application Server documentation as necessary. TIP: Oracle Application Server Documentation is available at http://www.oracle.com/technology/documentation/appserver.html You must start your Oracle Application Server instance and bring up the Enterprise Manager (EM) Console before you begin. If you cannot bring up the EM Console, you will be unable to proceed with configuring your application server for Oracle eBilling. It is recommended that you install and configure Oracle eBilling in the same top-level directory structure, first on the database server, then the application server. If you have not already installed database server components and configured the database server for Oracle eBilling, do so now. For distributed environments, ensure that you have any required database client software installed on Oracle Application Server and any other client machines of your database server. NOTE: The installation and configuration examples in this guide use default Oracle eBilling pathnames, privileges and permissions. If you choose not to accept the default values, ensure your values are consistent on all servers across your installation of Oracle eBilling.

Installing on Oracle Application Server 10g


Setting Configuration Properties
Before setting up eBilling on the Oracle Database, you must make sure that the appropriate properties files are configured with the same OLTP database SID, username, password as you used for the component installations. You must verify configuration properties for eStatement, ePayment, and eBilling.

To verify configuration parameters for eStatement 1


Verify that the following values are correct in edxadmin_unix.properties for the current installation. For eStatement, update the edxadmin_unix.properties file found under $EDX_HOME/ db/eStatement/oracle.

ORACLE_BASE and ORACLE_HOME locations OLTP database SID, and username and password SYSTEM password and tnsnames for OLTP Database file locations Redo file locations

64

Installation Guide for Oracle eBilling Version 6.0

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux

Trace file location

To verify configuration parameters for Oracle eBilling 1


Verify that the following values are correct in edxadmin_unix.properties for the current installation. For eBilling, update the edxadmin_unix.properties file found under $EDX_HOME/db/ ebilling/oracle.

ORACLE_BASE and ORACLE_HOME locations OLTP and OLAP database SID, and username and password SYSDBA password and tnsnames for OLTP and OLAP Database file locations Redo file locations Trace file location

To verify configuration parameters for ePayment 1


In the payusr.properties file found under $EDX_HOME/db/ePayment/oracle, make sure you give the same OLTP database SID, and username and password that you specified in the edxadmin_unix.properties.

Accessing Oracle Enterprise Manager (EM) Console


To verify that you have access to the Oracle Application Server EM console. 1
Open your browser and enter the URL for your Oracle Application Server EM console: http://<hostname>.<domain>:<port number>/em/console The Administration port number is automatically assigned at installation time.

When prompted for user name and password, enter oc4jadmin and the password that you entered at installation time.

Note: When you create the OAS server, use the host name instead of the IP address. If you give the IP address, you must access the applications with the IP address to avoid entering the username and password twice while logging in.

Starting, Stopping, and Restarting the Oracle Application Server 10g R3 Components
To start (stop, or restart) the HTTP Server and the OC4J components 1
On the Application Server Control Console's Home page, display the System Components table.

Installation Guide for Oracle eBilling Version 6.0

65

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux

Select the check box next to the HTTP Server and each component and click Start (Stop, or Restart).

Starting and Stopping OAS from the Command Line


To start or stop OAS from the command line 1
At the command line, go to the application server opmn directory: $ OAS_HOME/opmn/bin

Run the following command to start the server: $./opmnctl startall Run the following command to stop the server: $./opmnctl stopall

Creating an OC4J Instance for Oracle eBilling


To create an OC4J Instance for Oracle eBilling 1
At the command prompt, change to the directory location of the server bin directory, OAS_HOME/ bin, for example: $cd /export/home/oas/10.1.3/bin

Create an instance using the createinstance.bat -instanceName <name> command, for example: $./createinstance -instanceName ebilling

3 4

Select the check box of the eBilling instance and click Start to start the instance. At the Oracle EM console, select the OC4J component link (created for this application) from the list to navigate to the OC4J component page.

Configuring JDBC for Oracle eBilling


This section covers how to configure JDBC configuration for J2EE applications to Oracle Application Server 10g R3 by using Oracle Enterprise Manager 10g Application Server Control. A data source can be configured at two levels: Container level which is meant for all applications deployed to an OC4J Application level which is meant for a specific application

This guide describes how to create container-level data sources. These data sources provide access to the database used to store and retrieve data for the eBilling application.

66

Installation Guide for Oracle eBilling Version 6.0

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux

Creating the Connection Pools for Oracle eBilling


You must create three connection pools with the following information for eBilling:

Table 26.

Connection Pools for the eBilling Application Connection Factory Class oracle.jdbc.OracleDriver oracle.jdbc.xa.client.OracleXADataSource oracle.jdbc.xa.client.OracleXADataSource

Connection Pool Names edxAdminConnectionPool olapConnectionPool oltpConnectionPool

To create the connection pools 1 2 3 4 5 6 7


Click the Administration tab on the Oracle EM console. On the Administration page, under Services, click the Go to Task icon next to JDBC Resources. On the JDBC Resources page, under the Connection Pools section, click Create. Select the application as default, and Connection Pool Type as New Connection Pool. Click Continue. Provide the Connection Pool Name and the Connection Factory Class as shown in Table 26. Provide the JDBC URL under URL portion in the format: <Driver Type>:@//<DB Host Name>:<Port Number>/DB Alias Name For example: jdbc:oracle:thin:@//172.20.2.51:1521/oltp

Under credentials, provide the database login information, such as the username and password. For olapConnectionPool, while providing the JDBC URL, give the OLAP database alias name and credentials specific to the OLAP database. For example: jdbc:oracle:thin:@//172.20.2.51:1521/olap Under credentials, specify: username=olap password=olap

Installation Guide for Oracle eBilling Version 6.0

67

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux

After the connection pool is created, select the Attribute Tab and update the properties. For the Connection Pools with the Connection Factory Class oracle.jdbc.xa.client.OracleXADataSource (oltpConnectionPool and olapConnectionPool), use the following values. Otherwise use the default values.

Table 27. Attribute

Connection Pool Attributes for the eBilling Application Value 0 0 20 1 3 0 30 0

Initial Size of Connection Cache Minimum Number of Connections Maximum Number of Connections Connection Retry interval (seconds) Maximum Connection Attempts Maximum Number of Statements Cached Inactivity timeout (seconds) Maximum Number of Statements Cached

10 Click Apply to create connection pool. 11 Repeat these steps to create each connection pool.

Creating the Data Sources for Oracle eBilling


To create the data sources 1 2 3 4 5 6 7 8
Click the Administration tab. On the Administration page, under Services, click the Go to Task icon next to JDBC Resources. On the JDBC Resources page, under the Data Sources section, click Create. On the Create Data Source - Application and Type page, select Default as the application. Select Managed Data Source as the Data Source Type. Click Continue. On the Create Data Source - Managed Data Source page, select the connection pool from the drop-down list. Provide the properties for each data source shown in the tables below.

68

Installation Guide for Oracle eBilling Version 6.0

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux

Click Finish.

Table 28. Property Name

Data Source Properties Description Data Source Name Data Source Related JNDI Global and Local Transactions Data Source Related Connection Pool Default Value

JNDI Location Transaction Level Connection Pool Login Timeout (seconds)

Table 29.

Data Sources for the eBilling Application JNDI Locations edx.databasePool edx.report.databasePool edx.xma.databasePool Connection Pool edxAdminConnectionPool olapConnectionPool oltpConnectionPool

Data Source Names edxAdminDataSource olapDataSource oltpDataSource

JTA Transaction Configuration


You must configure JTA transactions for eBilling.

To configure JTA transactions for Oracle eBilling 1 2 3 4 5


Select the eBilling application (OC4J). Click the Administration tab. Select Administration Tasks, Services, Transaction Manager (JTA). Click the Administration tab Enter 360 in the Transaction Timeout field.

Configuring JMS for the Oracle eBilling Application


To configure batch reports, you must configure remote connection factories by specifying the host and (JMS) port number.

Installation Guide for Oracle eBilling Version 6.0

69

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux

To configure JMS for the Oracle eBilling applications 1 2


Open the OAS_HOME/j2ee/ebilling/config/jms.xml file. Add the following configuration information to this file: -server host="bossllin01" port="12604"> <!-- queue connection factories -->

<xa-queue-connection-factory location="edx.foreign.qcf" host="bossllin01" port="12603" />

<xa-queue-connection-factory location="edx.qcf" host="bossllin01" port="12604" />

<!-- queues --> <queue name="outboundQueue" location="edx.queue.outbound" persistence-file="ebilling_outbound" > <description>edx outbound queue</description> </queue> <queue name="foreignQueue" location="edx.foreign.queue.outbound" persistence-file="ebilling_foreign" > <description>edx foreign outbound queue</description> </queue>

..... ..... </jms-server>

Replace host name bossllin01 with your server name. The port is the one that the server is listening to. Each server instance has a different JMS port that its JMS server listens to. (See the procedure below for how to find the JMS port number of a server instance.)

70

Installation Guide for Oracle eBilling Version 6.0

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux

Replace the port numbers with your eBilling server instance's JMS port number and your Command Center's JMS port number. 12604: eBilling server instance's JMS port. 12603: Command Center server instance's JMS port.

Replace the port number in "<xa-queue-connection-factory location="edx.foreign.qcf" host="bossllin01" port="12603" />" with the JMS port number of the Command Center application. Note that you must reset this configuration every time the OC4J server is restarted.

Finding the JMS Port Number of a Server Instance


You can find the JMS port number of a server instance using the console or in command mode.

To find JMS port number of a server instance using the console 1 2 3


On the OC4J console, go to Administration, Server Properties. At the end of the page, under Related Links, click the System Properties link. Keep pressing Next until you see the port.jms on the last page in Properties. The port.jms is where the JMS port is.

To find JMS port number of a server instance using command mode 1 2


Go to the <OAS Home>/opmn/bin directory. Type the following command exactly as shown: ./opmnctl status -fmt %prt18%pid7R%sta8%por42 The following text appears on your console screen, indicating which port number OAS assigned to the eBilling, CSR, and Command Center applications: Processes in Instance: dev.bossllin01 -------------------+---------+----------+----------------------------------------process-type | pid | status | ports -------------------+---------+----------+----------------------------------------ASG | N/A | Down | N/A OC4J:ebilling | 20972 | Alive | jms:12602,ajp:12502,rmis:12702,rmi:12402 OC4J:ebilling_csr | 15582 | Alive | jms:12603,ajp:12503,rmis:12703,rmi:12403 OC4J:ebilling_cc | 23097 | Alive | jms:12604,ajp:12504,rmis:12704,rmi:12404 OC4J:home | 15579 | Alive | jms:12601,ajp:12501,rmis:12701,rmi:12401 HTTP_Server | 15578 | Alive | https1:4443,http2:7200,http1:7777

Installation Guide for Oracle eBilling Version 6.0

71

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux

Creating JMS Connection Factories for Oracle eBilling


Use the values shown in the following table when creating the connection factories for eBilling. When creating the JMS connection factories, be sure to select the XA Enabled check box.

Table 30.

Connection Factories for the eBilling Application JNDI Location edx.qcf edx.foreign.qcf Host <Host_name> <Host_name> Port Jms.port number of eBilling server Jms.port number of Command Center Server

Connection Factory Type Queue Queue

Configuring JMS Queue Destinations for Oracle eBilling


Use the values shown in the following table when configuring queue destinations for eBilling. Be sure to choose file-based queue types when creating the queues. You can place the persistence file in any location. Be sure to enter the path and name of the persistence file, such as: $OAS_HOME/j2ee/ebilling/persistence/ebilling_default_group_1/ebilling_foreign for foreignQueue, and $OAS/j2ee/ebilling/persistence/ebilling_default_group_1/ebilling_outbound for outboundQueue.

Table 31.

Queue Destinations for the eBilling Application Destination Name foreignQueue outboundQueue JNDI Location edx.foreign.queue.outbound edx.queue.outbound

Destination Type Queue Queue

Configuring opmn.xml for Oracle eBilling


You must edit the opmn.xml file and configure it for eBilling.

To configure opmn.xml 1
Open the OAS_HOME/opmn/conf/opmn.xml file.

72

Installation Guide for Oracle eBilling Version 6.0

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux

To configure command line options, find the tag <process-type></process-type> related to your created OC4J instance, for example, ebilling. Under tag <category id="start-parameters"></ category> (which is chilled tag of <module-data>), add your corresponding JAVA and OC4J environmental variables into the <data id="java-options" value=""/> and <data id="oc4joptions" value=""/>portion. To configure environment variables, find the tag <process-type></process-type> related to your created OC4J instance, for example, ebilling. Add the tag <environment></environment> above the <module-data>tag, and within that add your environmental variable name and value in the following format: <variable id="VARIABLE_NAME" value="VARIABLE_VALUE" append="BOOLEAN_VALUE"/> See the table for path variables to add and an edited sample opmn.xml file below. Don't use the Append tag for the fields that are not mentioned in following tables. Keep one space between two command line options. All paths mentioned must extend with "/".

Table 32. Name

Path Variables to add to opmn.xml for the Oracle eBilling Applications Value eBilling Home Directory For example: /opt/Oracle/eBilling Append true

EDX_HOME

LD_LIBRARY_PAT H

<EDX_HOME>/lib/Linux_ia32:$LD_LIBRARY_PATH For example: /opt/Oracle/eBilling /lib/Linux_ia32/ :$LD_LIBRARY_PATH <Oracle DB Client Home Directory>/bin:$PATH For example: /opt/Oracle/oracle/product/10.1.3/ client_1/bin:$PATH

true

PATH

true

Example of an edited opmn.xml file for Oracle eBilling <process-type id="ebilling" module-id="OC4J" status="enabled"> <environment> <variable id="EDX_HOME" value="/export/home/Oracle/eBilling"/> <variable id="LD_LIBRARY_PATH" value="/export/home/Oracle/eBilling/lib/ Linux_ia32" append="true"/> <variable id="PATH" value="$PATH:/export/home/Oracle/eBilling/bin:/export/ home/oas/10.1.3/jdk:/export/home/oas/10.1.3/bin" append="true"/> </environment> <module-data>

Installation Guide for Oracle eBilling Version 6.0

73

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux

<category id="start-parameters"> <data id="java-options" value="-server Djava.security.policy=$ORACLE_HOME/j2ee/ebilling/config/java2.policy Djava.awt.headless=true -Dhttp.webdir.enable=false -Djava.ext.dirs=$EDX_HOME/lib/ ext:$ORACLE_HOME/jdk/jre/lib/ext -Dcom.edocs.tasks.loader.user=oltp Dcom.edocs.tasks.loader.password=oltp -Dcom.edocs.tasks.loader.alias=myoltp Dedx.home=$EDX_HOME -Djava.protocol.handler.pkgs=com.edocs.protocol Dclass.load.log.level=finest -Dclass.load.log.file=/export/home/oracle/log/ classLoaderLatest.log"/> <data id="oc4j-options" value="-userThreads"/> </category> <category id="stop-parameters"> <data id="java-options" value="-Djava.security.policy=$ORACLE_HOME/ j2ee/ebilling/config/java2.policy -Djava.awt.headless=true Dhttp.webdir.enable=false"/> </category> </module-data> <start timeout="600" retry="2"/> <stop timeout="120"/> <restart timeout="720" retry="2"/> <port id="default-web-site" range="12501-12600" protocol="ajp"/> <port id="rmi" range="12401-12500"/> <port id="jms" range="12601-12700"/> <process-set id="default_group" numprocs="1"/> </process-type>

Configuring Log4j for Oracle eBilling


To edit the log4j configuration for Oracle eBilling 1 2
In opmn.xml in the OC4J instance for Oracle eBilling. Add the option for log4j configuration under <category id="start-parameters"> <data id="javaoptions"> tag in the following format: -Dlog4j.configuration=file:<exact_path_to_file>/<log4j_file_name> For example: -Dlog4j.configuration=file:$EDX_HOME/config/log4j.xml

74

Installation Guide for Oracle eBilling Version 6.0

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux

Note that <log4j_file_name> is different for each application; it is log4j.xml for the eBilling instance. Also, you can change the location of the log4j log file in the log4j.xml file; provide the actual path to the log file in the following line (by default it goes to $OAS_HOME/j2ee/home: <param name="File" value="eBilling.log"/>

Example of opmn.xml configured for log4j file for the Oracle eBilling instance <category id="start-parameters"> <data id="java-options" value="-server -Djava.security.policy=$ORACLE_HOME/j2ee/ ebilling/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false Djava.ext.dirs=$EDX_HOME/lib/ext;$ORACLE_HOME/jdk/jre/lib/ext Dcom.edocs.tasks.loader.user=oltp -Dcom.edocs.tasks.loader.password=oltp Dcom.edocs.tasks.loader.alias=myoltp -Dedx.home=$EDX_HOME Djava.protocol.handler.pkgs=com.edocs.protocol -Xms1024m -Xmx1024m XX:MaxPermSize=378m -Dclass.load.log.level=finest -Dclass.load.log.file=D:/log/ classLoaderLatest.log -Dlog4j.configuration=file:$EDX_HOME/config/log4j.xml" />

Configuring Jikes for Oracle eBilling


To configure Jikes for Oracle eBilling 1 2 3
Extract the jikes zip file in a directory. Change directory to the jikes folder and the src subfolder (the directory where you extracted jikes), for example: /home/mbhatia/jikes-1.22. At the command prompt, run the following commands using the Bourne shell or C shell. ./configure -prefix=PATH (this PATH is where you want to install jikes. You must have permissions on that directory) make make install

In the OAS_HOME/j2ee/<ebilling(OC4J Instance)>/config folder, modify the server.xml file with the following: Find the <java-compiler> tag and rename the name attribute to jikes, add the bindir attribute, and give the value of the path to the jikes bin directory, for example: <java-compiler name="jikes" in-process="false" options="-J-Xmx1024m -encoding UTF8" bindir="/home/mbhatia/jikes/bin" extdirs=" /export/home/oas/10.1.3/jdk/jre/lib/ext" />

Installation Guide for Oracle eBilling Version 6.0

75

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux

Configuring the Oracle eBilling and Command Center Applications for Notification
To configure the Oracle eBilling and Command Center applications for notification 1 2 3
After creating the ebilling and Command Center instances, create a shared library that points to the $EDX_HOME/config directory for both instances. When deploying the eBilling and Command Center EAR files, make sure this shared library is checked. For both ebilling and command center application server instances add the following Server Properties by clicking the Server Properties tab under Administration: -Dnotification.trace=true

Update the templates.xsl files under $EDX_HOME/config to reflect correct URL information and the content you want to deliver through email.

Creating an OC4J Instance for Command Center


To create an OC4J instance for the Command Center 1
At the command prompt, change to the directory location of the server bin directory, OAS_HOME/ bin, for example: $cd /export/home/oas/10.1.3/bin

Create an instance using the createinstance.bat -instanceName <name> command, for example: $./createinstance -instanceName ebilling_cc

3 4

Select the check box for the eBilling instance and click Start to start the instance. At the Oracle EM console, select the OC4J component link (created for this application) from the list to navigate to the OC4J component page.

76

Installation Guide for Oracle eBilling Version 6.0

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux

Configuring JDBC for the Command Center


Creating the Connection Pools for the Command Center
To create the connection pools 1
Follow the same steps for creating connection pools as you did for the Oracle eBilling application, except create the connection pools shown in the table below. See Creating the Connection Pools for Oracle eBilling on page 67 for details.

Table 33.

Connection Pools for the Command Center Application Connection Factory Class oracle.jdbc.OracleDriver oracle.jdbc.OracleDriver oracle.jdbc.OracleDriver oracle.jdbc.xa.client.OracleXADataSource oracle.jdbc.xa.client.OracleXADataSource oracle.jdbc.xa.client.OracleXADataSource Note: For reportConnectionPool, provide the olap instance with the olap username and password.

Connection Pool Name edxAdminConnectionPool edxLoggerConnectionPool edxUserConnectionPool edxMessagingConnectionPool edxXMAConnectionPool reportConnectionPool

Configuring the Command Center Application for Notification


To create the shared library required for Command Center, see Configuring the Oracle eBilling and Command Center Applications for Notification on page 76 for details.

Creating the Data Sources for the Command Center


To create the data sources 1
Follow the same steps for creating data sources as you did for the Oracle eBilling application, except create the data sources using the data shown in the table below. See Creating the Data Sources for Oracle eBilling on page 68 for details. Table 34. Data Source Names for the Command Center Application JNDI Location edx.databasePool edx.logger.databasePool Connection Pool edxAdminConnectionPool edxLoggerConnectionPool

Data Source Name edxAdminDataSource edxLoggerDataSource

Installation Guide for Oracle eBilling Version 6.0

77

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux

Table 34.

Data Source Names for the Command Center Application JNDI Location edx.user.databasePool edx.messaging.databasePool edx.xma.databasePool edx.report.databasePool Connection Pool edxUserConnectionPool edxMessagingConnectionPool edxXMAConnectionPool reportConnectionPool

Data Source Name edxUserDataSource edxMessagingDataSource edxXMADataSource reportDataSource

Configuring JMS for the Command Center


To configure batch reports, you must configure remote connection factories by specifying the host and (JMS) port number.

To configure JMS for the Command Center application 1 2


Open the OAS_HOME/j2ee/ebilling_cc/config/jms.xml file. Add the following configuration information to this file: <OAS_HOME>/j2ee/ebilling_cc/config/jms.xml

<jms-server host="bossllin01" port="12603"> <xa-queue-connection-factory name="outboundQueueConnectionFactory_cc" location="edx.qcf" host ="bossllin01" port="12603"/>

<xa-queue-connection-factory name="edxForiegnJMSConnectionFactory" location="edx.foreign.qcf" host ="bossllin01" port="12604"/>

<xa-queue-connection-factory name="edxLoggerConnectionFactory" location="edx/lcf" host ="bossllin01" port="12603"/>

78

Installation Guide for Oracle eBilling Version 6.0

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux

<queue name="outboundQueue" location=" edx.foreign.queue.outbound " persistence-file="ebilling_cc_foriegn"> <description>edx foreign outbound queue</description> <queue name="outboundQueue_cc" location="edx.queue.outbound" persistence-file="ebilling_cc_outbound"> <description>edx outbound queue</description> </queue> <queue name="QueueBindingName" location="edx/queue/logger" > </queue> ... ... </jms-server>

Replace host name bossllin01 with your server name. The port is the JMS port number that the server is listening. Each server instance has a different JMS port that its JMS server listens to. (To find the JMS port number of a server instance, see Finding the JMS Port Number of a Server Instance on page 71. Replace the port numbers with your eBilling server instance's JMS port number and your Command Center's JMS port number. 12604: eBilling server instance's JMS port. 12603: Command Center server instance's JMS port.

Replace the port number in <xa-queue-connection-factory name="edxForiegnJMSConnectionFactory" location="edx.foreign.qcf" host ="bossllin01" port="12604"/>" with the JMS port number of the eBilling server. And the name of the queue "outboundQueue" with JNDI name edx.foreign.queue.outbound on the Command Center server must be same as name of the queue "outboundQueue" with JNDI name "edx.queue.outbound" on the eBilling server.

Installation Guide for Oracle eBilling Version 6.0

79

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux

Creating JMS Connection Factories for Command Center


Use the values shown in the following table when creating the connection factories for the Command Center.

Table 35.

Connection Factories for the Command Center Application JNDI Location edx/lcf edx.foreign.qcf edx.qcf Host host_name host_name host_name Port Jms.port number of the Command Center server Jms.port number of the eBilling server Jms.port number of the Command Center server

Connection Factory Type Queue Queue Queue

Creating JMS Queue Destinations for Command Center


Use the values shown in the following table when configuring the queue destinations for the Command Center. Table 36. Queue Destinations for the Command Center Application Destination Name QueueBindingName EventsforeignQueue EventsQueue JNDI Location edx/queue/logger edx.foreign.queue.outbound edx.queue.outbound

Destination Type Queue Queue Queue

Configuring opmn.xml for the Command Center


You must edit the opmn.xml file and configure it for the Command Center.

To configure opmn.xml 1 2
Open the OAS_HOME/opmn/conf/opmn.xml file. Find the tag <process-type></process-type> related to your created OC4J instance, for example, ebilling. Under tag <category id="start-parameters"></category> (which is chilled tag of <module-data>), add your corresponding JAVA and OC4J environmental variables into the <data id="java-options" value=""/> and <data id="oc4j-options" value=""/>portion.

80

Installation Guide for Oracle eBilling Version 6.0

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux

To configure environment variables, find the tag <process-type></process-type> related to your created OC4J instance. Add the tag <environment></environment> above the <moduledata>tag, and within that add your environment variable name and value in the following format: <variable id="VARIABLE_NAME" value="VARIABLE_VALUE" append="BOOLEAN_VALUE"/> See the table for path variables to add and an edited sample opmn.xml file below. Don't use the Append tag for the fields that are not mentioned in following table. Keep one space between two command line options. All paths mentioned must extend with "/".

Table 37. Name

Path Variables to add to opmn.xml for the Command Center Application Value eBilling Home Directory For example: /opt/Oracle/eBilling Append

EDX_HOME

LD_LIBRARY_PATH

<EDX_HOME>/lib/Linux_ia32:$LD_LIBRARY_PATH For example: /opt/Oracle/eBilling/lib/Linux_ia32/ :$LD_LIBRARY_PATH

true

PATH

OAS_HOME/bin:$PATH For example: /export/home/OAS/10.1.3/bin:$PATH

true

Example of an edited opmn.xml file for Command Center <process-type id="ebilling_cc" module-id="OC4J" status="enabled"> <environment> <variable id="EDX_HOME" value="/export/home/Oracle/eBilling"/> <variable id="LD_LIBRARY_PATH" value="/export/home/Oracle/eBilling/lib/ Linux_ia32" append="true"/> <variable id="PATH" value="$PATH:/export/home/Oracle/eBilling/bin:/export/ home/oas/10.1.3/jdk:/export/home/oas/10.1.3/bin" append="true"/> </environment> <module-data> <category id="start-parameters"> <data id="java-options" value="-server Djava.security.policy=$ORACLE_HOME/j2ee/ebilling_cc/config/java2.policy Djava.awt.headless=true -Dhttp.webdir.enable=false -Djava.ext.dirs=$EDX_HOME/lib/ ext:$ORACLE_HOME/jdk/jre/lib/ext -Dcom.edocs.tasks.loader.user=oltp Dcom.edocs.tasks.loader.password=oltp -Dcom.edocs.tasks.loader.alias=myoltp -

Installation Guide for Oracle eBilling Version 6.0

81

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux

Dedx.home=$EDX_HOME -Djava.protocol.handler.pkgs=com.edocs.protocol Dclass.load.log.level=finest -Dclass.load.log.file=/export/home/oracle/log/ classLoaderLatest.log" -Dedx.log4jconfigfile=log4j_ccenter.xml Dnotification.trace=true/> <data id="oc4j-options" value="-userThreads"/> </category> <category id="stop-parameters"> <data id="java-options" value="-Djava.security.policy=$ORACLE_HOME/ j2ee/ebilling/config/java2.policy -Djava.awt.headless=true Dhttp.webdir.enable=false"/> </category> </module-data> <start timeout="600" retry="2"/> <stop timeout="120"/> <restart timeout="720" retry="2"/> <port id="default-web-site" range="12501-12600" protocol="ajp"/> <port id="rmi" range="12401-12500"/> <port id="jms" range="12601-12700"/> <process-set id="default_group" numprocs="1"/> </process-type>

Configuring Log4j for the Command Center


You must configure the Log4j for Command Center in the opmn.xml file. Note that you can change the location of the log4j log file in the log4j_ccenter.xml file.

To edit the log4j configuration for the Command Center 1 2


In opmn.xml for the Command Center OC4J instance. Add the option for log4j configuration under <category id="start-parameters"> <data id="javaoptions"> tag in the following format: add -Dlog4j.configuration=file:<exact_path_to_file>/<log4j_file_name>; For example: -Dedx.home=${EDX_HOME} -Dedx.log4jconfigfile=log4j_ccenter.xml

82

Installation Guide for Oracle eBilling Version 6.0

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux

Example of opmn.xml configured for log4j file for Command Center instance <category id="start-parameters"> <data id="java-options" value="-server -Djava.security.policy=$ORACLE_HOME/j2ee/ ebilling_cc/config/java2.policy -Djava.awt.headless=true Dhttp.webdir.enable=false -Djava.ext.dirs=$EDX_HOME/lib/ext;$ORACLE_HOME/jdk/jre/ lib/ext -Dcom.edocs.tasks.loader.user=oltp -Dcom.edocs.tasks.loader.password=oltp Dcom.edocs.tasks.loader.alias=myoltp -Dedx.home=$EDX_HOME Djava.protocol.handler.pkgs=com.edocs.protocol -Xms1024m -Xmx1024m XX:MaxPermSize=378m -Dclass.load.log.level=finest -Dclass.load.log.file=D:/log/ classLoaderLatest.log -Dlog4j.configuration=file:$EDX_HOME/config/ log4j_ccenter.xml" />

Configuring Jikes for the Command Center


Before configuring Jikes for the Command Center, you must create a shared library for the Command Center.

To create a shared library for the Command Center 1 2 3 4 5


Click the instance for Command Center. Click the Administration tab, then click the "Go to Task" icon next to Shared Libraries. Click Create and give any name and version and then click Next. Click Add and provide the full path of the $EDX_HOME/config folder and then click Continue. Click Finish.

To configure Jikes for the Command Center, follow the instructions given for Configuring Jikes for Oracle eBilling on page 75.

Creating an OC4J Instance for CSR


To create an OC4J instance for the CSR 1
At the command prompt, change to the directory location of the server bin directory, OAS_HOME/ bin, for example: $cd /export/home/oas/10.1.3/bin

Create an instance using the createinstance.bat -instanceName <name> command, for example: $./createinstance -instanceName csr

3 4

Select the check box for the CSR instance and click Start to start the instance. At the Oracle EM console, select the OC4J component link (created for this application) from the list to navigate to the OC4J component page.

Installation Guide for Oracle eBilling Version 6.0

83

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux

Configuring JDBC for CSR


Set the same data sources and connection pool settings for CSR as you did for the Oracle eBilling J2EE application. See Creating the Connection Pools for Oracle eBilling on page 67 for details.

Configuring opmn.xml for CSR


You must edit the opmn.xml file and configure it for the CSR application.

To configure opmn.xml 1 2
Open the OAS_HOME/opmn/config/opmn.xml file. Find the tag <process-type></process-type> related to your created OC4J instance, for example, ebilling. Under tag <category id="start-parameters"></category> (which is chilled tag of <module-data>), add your corresponding JAVA and OC4J environmental variables into the <data id="java-options" value=""/> and <data id="oc4j-options" value=""/>portion. To configure environment variables, find the tag <process-type></process-type> related to your created OC4J instance. Add the tag <environment></environment> above the <moduledata>tag, and within that add your environment variable name and value in the following format: <variable id="VARIABLE_NAME" value="VARIABLE_VALUE" append="BOOLEAN_VALUE"/> See the table for path variables to add and an edited sample opmn.xml file below. Don't use the Append tag for the fields that are not mentioned in following table. Keep one space between two command line options. All paths mentioned must extend with "/".

Table 38. Name

Path Variables to add to opmn.xml for the CSR Application Value eBilling Home Directory For example: /opt/Oracle/eBilling Append

EDX_HOME

LD_LIBRARY_PATH

<EDX_HOME>/lib/Linux_ia32:$LD_LIBRARY_PATH For example: /opt/Oracle/eBilling/lib/Linux_ia32/ :$LD_LIBRARY_PATH

true

PATH

<Oracle DB Client Home Directory>/bin:$PATH For example: /opt/oracle/oracle/product/10.2.0/client_1/ bin:$PATH

true

84

Installation Guide for Oracle eBilling Version 6.0

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux

Example of an edited opmn.xml file for CSR <process-type id="csr" module-id="OC4J" status="enabled"> <environment> <variable id="EDX_HOME" value="/export/home/Oracle/eBilling"/> <variable id="LD_LIBRARY_PATH" value="/export/home/Oracle/eBilling/lib/ Linux_ia32" append="true"/> <variable id="PATH" value="$PATH:/export/home/Oracle/eBilling/bin:/export/ home/oas/10.1.3/jdk:/export/home/oas/10.1.3/bin" append="true"/> </environment> <module-data> <category id="start-parameters"> <data id="java-options" value="-server Djava.security.policy=$ORACLE_HOME/j2ee/csr/config/java2.policy Djava.awt.headless=true -Dhttp.webdir.enable=false -Djava.ext.dirs=$EDX_HOME/lib/ ext:$ORACLE_HOME/jdk/jre/lib/ext -Dcom.edocs.tasks.loader.user=oltp Dcom.edocs.tasks.loader.password=oltp -Dcom.edocs.tasks.loader.alias=myoltp Dedx.home=$EDX_HOME -Djava.protocol.handler.pkgs=com.edocs.protocol Dclass.load.log.level=finest -Dclass.load.log.file=/export/home/oracle/log/ classLoaderLatest.log"/> <data id="oc4j-options" value="-userThreads"/> </category> <category id="stop-parameters"> <data id="java-options" value="-Djava.security.policy=$ORACLE_HOME/ j2ee/csr/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false"/ > </category> </module-data> <start timeout="600" retry="2"/> <stop timeout="120"/> <restart timeout="720" retry="2"/> <port id="default-web-site" range="12501-12600" protocol="ajp"/> <port id="rmi" range="12401-12500"/> <port id="jms" range="12601-12700"/> <process-set id="default_group" numprocs="1"/> </process-type>

Installation Guide for Oracle eBilling Version 6.0

85

Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux

Configuring Log4j for the CSR


To edit the log4j configuration for the CSR 1 2
In opmn.xml for the CSR OC4J instance. Add the option for log4j configuration under <category id="start-parameters"> <data id="javaoptions"> tag in the following format: add -Dlog4j.configuration=file:<exact_path_to_file>/<log4j_file_name>; For example: -Dlog4j.configuration=file:$EDX_HOME/config/log4j_csr.xml Note that <log4j_file_name> is different for each application; it is log4j_csr.xml for the CSR instance.

Example of opmn.xml configured for log4j file for the CSR instance <category id="start-parameters"> <data id="java-options" value="-server -Djava.security.policy=$ORACLE_HOME/j2ee/ ebilling/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false Djava.ext.dirs=$EDX_HOME/lib/ext;$ORACLE_HOME/jdk/jre/lib/ext Dcom.edocs.tasks.loader.user=oltp -Dcom.edocs.tasks.loader.password=oltp Dcom.edocs.tasks.loader.alias=myoltp -Dedx.home=$EDX_HOME Djava.protocol.handler.pkgs=com.edocs.protocol -Xms1024m -Xmx1024m XX:MaxPermSize=378m -Dclass.load.log.level=finest -Dclass.load.log.file=D:/log/ classLoaderLatest.log -Dlog4j.configuration=file:$EDX_HOME/config/log4j_csr.xml" / >

Configuring the Jikes Compiler for the CSR


To configure Jikes for the CSR, follow the instructions given for Configuring Jikes for Oracle eBilling on page 75.

Modifying csr.xma.xml
You must configure the csr.xma.xml file with the URL strings CSR needs to impersonate the user.

To modify the csr.xma.xml file 1


Edit the $EDX_HOME/xma/config/modules/application/csr/csr.xma.xml file. Modify the property of "custAppURL" to the value where the eBilling application is deployed, using the correct server name or IP address, for example: http://sdchs20n258.corp.siebel.com:7001/ebilling/j_acegi_security_check?

86

Installation Guide for Oracle eBilling Version 6.0

Installing on Linux, Oracle Database, and Oracle Application Server Modifying persistence.xma.xml

Modify the property of "custLogoutAppURL" to the value where the eBilling application is deployed, for example: http://sdchs20n258.corp.siebel.com:7001/ebilling/j_acegi_logout

Modifying persistence.xma.xml
You must configure the persistence.xma.xml file.

To modify the persistence.xma.xml file 1 2


Edit $EDX_HOME/xma/config/modules/persistence.xma.xml file. Update the <bean id ="TransactionManager> tag as follows: Comment the transactionManagerName " <property name="transactionManagerName">tag For <property name="userTransactionName"> give the value as <value>java:comp/ UserTransaction</value>.

In bean id defaultHibernatePropsTx, update the property with key "hibernate.transaction.manager_lookup_class" to: org.hibernate.transaction.OC4JTransactionManagerLookup

After making the necessary changes in the persistence.xma.xml and opmn.xml file, stop and restart the server from the command line.

Example of edited persistence.xma.xml file


<bean id="TransactionManager" class="org.springframework.transaction.jta.JtaTransactionManager"> <!--<property name="transactionManagerName"><value>javax.transaction.TransactionManager</ value></property>--> <property name="userTransactionName"><value>java:comp/UserTransaction</ value></property>

<bean id="defaultHibernatePropsTx" class="org.springframework.beans.factory.config.PropertiesFactoryBean"> <prop key="hibernate.transaction.manager_lookup_class">org.hibernate.transaction.OC4JTra nsactionManagerLookup</prop>

Installation Guide for Oracle eBilling Version 6.0

87

Installing on Linux, Oracle Database, and Oracle Application Server Repackaging LGPL

Repackaging LGPL
You must repackage LGPL (GNU Lesser General Public License) on your Oracle eBilling system. This is required by all systems and applies to all platforms. Before you can repackage the LGPL, you must have Maven set up on your system. See Repackaging LGPL on page 54 for details.

Deploying Oracle eBilling Applications for Linux on OAS


Use the Oracle Application Server Enterprise Manager (EM) console to deploy each of the three J2EE application ear files.

Table 39.

Oracle eBilling Application Files Names on OAS File Name and Location $EDX_HOME/eBilling/J2EEApps/ebilling/OAS/ebilling-OC4J-10g6.0.ear $EDX_HOME/J2EEApps/commandcenter/OAS/command-center-OC4J10g-6.0.ear $EDX_HOME/J2EEApps/csr/OAS/csr-OC4J-10g-6.0.ear

eBilling Applications eBilling Application Command Center CSR Application

To deploy an ear file on Oracle Application Server 1 2 3


On the Oracle EM, click the Applications property page link to display the applications for the home instance. Click Deploy to launch the Deploy Application Wizard. The Deploy Application Wizard in Application Server Control guides you through the steps required to deploy an application. On the Deploy Application page, click Browse to select the ear file to deploy. Enter the application name. Click Continue. On the Application Attributes page, enter an application name. Use the appropriate Context Root value for each application: ebilling, ebillingcsr, or eBilling (for Command Center). When deploying the eBilling and Command Center applications, select the check box for the shared library you created as well.

4 5

6 7

On the Deployment Settings page, next to Configure Class Loading, click the Go to Task icon. On the Configure Class Loading page, uncheck the oracle.toplink, oracle.xml, and oracle.xml.security Import check boxes. Note: For OAS version 10.1.3.2 you need to uncheck apache.commons.logging checkbox. When deploying the eBilling and Command Center applications, select the check box for the shared library you created as well.

88

Installation Guide for Oracle eBilling Version 6.0

Installing on Linux, Oracle Database, and Oracle Application Server Running Scheduler on Linux and OAS

8 9

During deployment, the Application Server Control Console might display a page tracking the deployment process. When the Confirmation page appears, click Return. Restart the server instance.

Running Scheduler on Linux and OAS


The Oracle eBilling Scheduler manages the Command Center jobs. Scheduler must be running for scheduled jobs to execute. NOTE: Note: For information on running the PWC job scheduler, see the Administration Guide for Oracle eBilling. Before starting the Scheduler you must set up a user name and password using the OAS Security Provider.

To set up the Security Configuration for Command Center 1 2 3


At the Oracle EM console, select the deployed Command Center application and go to Administration -> Security -> Security Provider. Click Edit for the application -> Realms tab. Click Users (the link on the number of users enrolled). Create the user admin with password welcome. Specify the available user roles.

To start the Scheduler on Linux 1 2 3 4


On the command line, change to the directory $EDX_HOME/bin. Run the following command: $./edx_config Set the appropriate details for database server, application server name, Oracle home directory, java home, and application server J2EE home directory. Start the Scheduler with the following command, where 6005 is the request port number in the OAS_HOME/opmn/conf/opmn.xml file for your machine, where CC is the Command Center instance name, and eStatement is the name of the deployed application: oas_scheduler -start -url opmn:ormi://localhost:6005:CC/eStatement

Example - Starting the Scheduler on Linux bash-3.00$ ./edx_config Enter the database server to use, Oracle (oracle) or DB2 (db2) : [oracle] [q] oracle Enter Oracle home directory : [/opt/oracle/product/10.2.0/client_1] [q]

Installation Guide for Oracle eBilling Version 6.0

89

Installing on Linux, Oracle Database, and Oracle Application Server Running the eBilling Applications on Linux and OAS

/export/home/oracle/10.2.0.2 Oracle DB username : [edx_dba] [q] oltp Oracle password : [edx] [q] oltp Oracle DB alias (tnsname) : [edx.db] [q] oltp Enter the application server to use, weblogic (wl) or websphere (ws) oracle (oas) : [wl] [q] oas Enter Oracle Application Server J2EE home directory : [/opt/ora_j2ee/j2ee/home] [q] /export/home/oas/10_1_3/j2ee/home Enter Java root directory : [/usr/local/java] [q] /export/home/oas/10_1_3/jdk bash-3.00$ pwd /export/home/oracle/eBilling/bin bash-3.00$ oas_scheduler -start -url opmn:ormi://localhost:6005:CC/eStatement

Running the eBilling Applications on Linux and OAS


After you have deployed the eBilling application and started the Scheduler, you can run the sample Oracle eBilling applications: eBilling J2EE application Command Center CSR

To run eBilling on OAS 1


In your browser, enter a URL in the following format: http://<hostname>:<port number>/ebilling. Example:- http://sdchs21n128.corp.siebel.com:7777/ebilling The application main welcome page appears.

90

Installation Guide for Oracle eBilling Version 6.0

Installing on Linux, Oracle Database, and Oracle Application Server Running the eBilling Applications on Linux and OAS

If you are going to create a new user on the Security page, Users section, you must add new user and password information for the scheduler as follows: Default user - admin JAVA_OPTIONS="$JAVA_OPTIONS -Djava.naming.security.principal=admin" Default user - password JAVA_OPTIONS="$JAVA_OPTIONS -Djava.naming.security.credentials=welcome"

Oracle eBilling provides the following sample user names and passwords with the eBilling application:

Table 40.

Sample Usernames and Passwords Provided for the eBilling Application Password jsmith ftown twalsh tbrown Role Admin B2B Admin User B2C User B2C User

Username jsmith ftown twalsh tbrown

To run the Command Center application 1


In your browser, enter a URL in the following format: http://<hostname>:<port number>:/eBilling For example:- http://sdchs21n128.corp.siebel.com:7777/eBilling The application main welcome page appears.

Login using the user name "admin" and the password oracle.

To run the CSR application 1


In your browser, enter a URL in the following format: http://<hostname>:<port number>/ebillingcsr For example: http://sdchs21n128.corp.siebel.com:7777/ebillingcsr The application main welcome page appears.

Log in to the CSR application as the CSR Administrator or CSR role user. Use the usernameedocsadmin and password 111111 to log in.

Installation Guide for Oracle eBilling Version 6.0

91

Installing on Linux, Oracle Database, and Oracle Application Server Running the eBilling Applications on Linux and OAS

92

Installation Guide for Oracle eBilling Version 6.0

Installing Oracle eBilling ETL

This chapter describes how to install and deploy the Oracle eBilling ETL module into a production environment. It includes the following topics: ETL Module System Requirements Installing the OWB Repository Installing the ETL Module

ETL Module System Requirements


This guide assumes you are installing the Oracle eBilling ETL Module on a correctly configured Oracle eBilling installation and that you have installed the following prerequisite software: Oracle RDBMS 10g 10.2.0.2 Oracle Warehouse Builder (OWB) 10.2.0.1 with OWB Patches 5384468 and 5696353 Oracle Workflow 2.6.4 (Install this using ORACLE Companion CD 10.2.0.2.) Apache Ant 1.6.5

Installing the OWB Repository


To install the OWB Repository you must perform the following sequence of tasks, described in detail in this chapter: Tuning the OLAP Database Creating the OWB Repository Owner Creating the OWB Repository User Creating an OWB Project Creating Database Modules Creating a Process Flow Module Creating File System Locations Registering Locations Granting Rights to MAP_USER

Installation Guide for Oracle eBilling Version 6.0

93

Installing Oracle eBilling ETL Installing the OWB Repository

Tuning the OLAP Database


There are several important database parameters you must tune for OWB and the ETL Module to function properly. Note that the values provided here are for a minimum requirement. Set values appropriate for your operating system and database environment.

To tune the database parameters 1


Edit the init file found in $ORACLE_HOME%/database/init<SID>.ora (or %ORACLE_HOME%\database\init<SID> for Windows) for the Oracle eBilling OLAP database. Modify the value of or add the following parameters: Db_cache_size=256m Large_pool_size=64m Pga_aggregate_target=512m Shared_pool_size=500m job_queue_processes=10 aq_tm_processes=1 o7_dictionary_accessibility=true

Restart the OLAP database.

The database is now ready for installation of the OWB repository schema.

Creating the OWB Repository Owner


You must create an OWB repository owner using the OWB Repository Assistant. For additional information about the Repository Assistant, see the Oracle Warehouse Builder documentation at http://www.oracle.com/technology/documentation/warehouse.html.

To create the OWB repository owner 1


Start the OWB Repository Assistant. On UNIX and Linux, log in as the oracle user, change the directory to OWB_HOME/owb/bin/unix and run ./reposinst.sh. Note: The UNIX and Linux Repository Assistant requires a correctly configured X Window environment in order to run. On Windows, log in as an administrator and click the link on the Start Menu to the Repository Assistant (Administration).

2 3

On the Welcome screen click Next. Select Advanced Setup and click Next.

94

Installation Guide for Oracle eBilling Version 6.0

Installing Oracle eBilling ETL Installing the OWB Repository

4 5 6 7 8 9

Enter the SYSDBA password, host name, port number, and service name for the Oracle eBilling OLAP database and click Next. Select "Manage a Warehouse Builder repository owner" and click Next. Select "Create a new Warehouse Builder repository owner" and click Next. Enter repository owner user name "rep_admin" and a password, and click Next. Re-enter the password and click OK. Enter the following tablespace information: Tablespace for Data: EDX_REPORT_CDR_DATA Tablespace for Indexes: EDX_REPORT_CDR_IDX Tablespace for Temporary Data: TEMP (Default) Tablespace for Snapshots: EDX_REPORT_CDR_DATA

10 progress bar shows the installation status. When it finishes, click OK on the Installation
Successful dialog.

11 Click Finish.

Creating the OWB Repository User


You must create an OWB repository user using the OWB Design Center.

To create the OWB repository user 1


Start the OWB Design Center. On UNIX and Linux, log in as the oracle user, change the directory to OWB_HOME/owb/bin/unix, and run ./owbclient.sh. On Windows, log in as an administrator and click the link in the Start Menu to the Design Center. If you want to connect to a UNIX-hosted OWB repository you can use the Windows native client if OWB is installed.

2 3 4 5 6

Log in to the Design Center as the repository owner. After successfully logging in the Design Center, expand the security tree in the Global Explorer pane. Right-click the User element and click New to launch the Warehouse Builder User Wizard. Click Create DB User. Enter the SYSDBA password, username "map_user" (required) and a password for the new database user. Click OK. Check the "Used as target schema?" box and click Next.

Installation Guide for Oracle eBilling Version 6.0

95

Installing Oracle eBilling ETL Installing the OWB Repository

Creating an OWB Project


You must create an OWB project in the OWB Design Center.

To create an OWB project 1 2 3


Start the OWB Design Center and log in as the repository owner. On the Design menu, click New to create a new project. Enter the name of the project, such as EBILLING_ETL and click OK.

Creating Database Modules


You must create four Oracle database modules using the OWB Design Center and the parameters described here.

To create the Oracle database modules 1 2 3 4


Expand the newly created project tree and navigate to the Databases -> Oracle. Right-click the Oracle element and click New to start the Create Module Wizard. Enter the name of the module to create (such as STAGE_TABLES) and click Next. Click Edit next to the location drop-down box. Enter the location name and database connection details of the Oracle eBilling OLAP database. Verify that the correct database version is selected and click OK. It is recommended that you test each connection before pressing OK to ensure the correct parameters have been supplied.

5 6

Click Finish to create the new database module. Create four database modules using the following information. The database parameters for each module must be those used for the Oracle eBilling installation. For each module, enter the OLAP database schema username and password.

Table 41.

Database Modules to Create Module Location STAGE_TABLES_LOCATION TARGET_TABLES_LOCATION MAPPINGS_LOCATION OLTP_LOCATION Oracle eBilling Database OLAP OLAP OLAP OLTP Oracle eBilling Schema OLAP OLAP MAP_USER OLTP

Module Name STAGE_TABLES TARGET_TABLES MAPPINGS OLTP

96

Installation Guide for Oracle eBilling Version 6.0

Installing Oracle eBilling ETL Installing the OWB Repository

Creating a Process Flow Module


You must create a process flow module in the OWB Repository.

To create a process flow module 1 2 3 4


Expand the newly created project tree and navigate to the Process Flows -> Process Flow Modules. Right-click the Process Flow Modules element and click New to start the Create Module Wizard. Enter the name of the module to create (such as ETL_PF_MODULE) and click Next. Click Edit next to the location drop-down box. Enter the location name as EBILLING_ETL_LOCATION and the database connection details of the Oracle eBilling OLAP database, and the username and password for the Oracle Workflow user (OWF_MGR). Verify that the correct Oracle Workflow version is selected and click OK. Module Name ETL_PF_MODULE Module Location Name EBILLING_ETL_LOCATION Oracle eBilling Database OLAP Oracle eBilling Schema OWF_MGR

It is recommended that you select Test Connection before clicking OK to verify that you have supplied the correct parameters.

Click Finish to create the new process flow module.

Creating File System Locations


You must create file locations within the OWB repository to define where the data files used in the ETL process flow are located.

To create a file system location 1 2 3


Expand the newly created Locations Node in the Connection Explorer and navigate to Files. Right-click the Files node and click New to open the Create File System Location dialog. Enter a name and file system location (path) and click OK. Define the following locations. The specific file system location depends on your individual installation.

Table 42. Name

File System Locations to Create Description Where incoming data is located Where bad data files are written Example /export/home/oracle/testdata/ OWF_OUTDATA /export/home/oracle/testdata/bad

DATA_FILES_LOCATION BAD_FILE_LOCATION

Installation Guide for Oracle eBilling Version 6.0

97

Installing Oracle eBilling ETL Installing the OWB Repository

Table 42. Name

File System Locations to Create Description Where discarded data is written Where log files are written Example /export/home/oracle/testdata/ discard /export/home/oracle/testdata/log

DISCARD_FILE_LOCATION LOG_FILE_LOCATION

Registering Locations
You must register all the database and file locations in the OWB Design Center using Control Center.

To register a location 1
In the Design Center, select the Tools menu and click Control Center Manager. If you receive error "RTC-5301 The Runtime Platform Service cannot be started (Not Available)," verify that you have added the parameter job_queue_processes to the OLAP database configuration. If the Control Center Service is still not available, you can try starting it in one of the following ways: Connect to SQL*Plus as the runtime environment owner. Navigate to $OWB_HOME\owb\rtp\sql and run the start_service.sql script. If it runs successfully you receive the message "Available." If it says "Not Available," shut down and restart both OLAP and OLTP instances and try the script again. Or, if OWB is installed locally, use the Start Control Center Service script on the local machine; provide connection parameters to connect to the host on which the Control Center has to be started.

2 3

Right click each of the locations listed in the left hand pane and click Register. Verify that the name and location path are correct and click OK. Repeat this step for each database and file location you created previously.

Granting Rights to MAP_USER


You must grant the MAP_USER database user permissions to use the OWB resources.

To grant the necessary rights to MAP_USER 1


Using SQL*Plus, log on to OLAP database as SYSDBA: export ORACLE_SID=<OLAP Instance> SQLPLUS "/ as sysdba"

98

Installation Guide for Oracle eBilling Version 6.0

Installing Oracle eBilling ETL Installing the ETL Module

Execute the following SQL statements: grant SELECT ANY DICTIONARY to map_user; grant SELECT ANY TABLE to map_user; grant INSERT ANY TABLE to map_user; grant UPDATE ANY TABLE to map_user; grant DELETE ANY TABLE to map_user; grant EXECUTE ANY PROCEDURE to map_user; grant SELECT ANY SEQUENCE to map_user; grant OWB_O_REP_ADMIN to owf_mgr; OR Go to the eBilling 6.0 database installation folder $EDX_HOME/db/ebilling/oracle/olap/etl/ packages (%EDX_HOME%\db\ebilling\oracle\olap\etl\packages on Windows) and make sure that repository_grants.sql exists in the folder. Then logon to OLAP DB SQLPLUS as sysdba using below command and execute the following command: at sqlplus prompt.

export ORACLE_SID=<OLAP Instance> SQLPLUS / as sysdba SQL>@repository_grants.sql SQL>exit;

Installing the ETL Module


This topic describes how to install the ETL module and test the ETL Loader job using sample data. For Windows, change the slashes and root where needed.

Installing ETL
This topic assumes you have set up the OWB Repository according to the instructions in the previous chapter. The ETL Module is included in the Oracle eBilling software installation directory.

Installation Guide for Oracle eBilling Version 6.0

99

Installing Oracle eBilling ETL Installing the ETL Module

To install the ETL Module 1


Open the owbadmin.properties ETL module configuration file in a text editor. This file is located in $EDX_HOME/db/ebilling/oracle/olap/etl/ (or %EDX_HOME%\db\ebilling\oracle\olap\etl\ in Windows) Modify the properties to reflect your Oracle eBilling environment. (On Windows you must use two forward slashes when entering file system paths.) Note that the OUTPUT_DIR path/directory in this properties file must be the same as the path/directory of the DATA_FILES_LOCATION in the OWB repository. The path/directory of the OUTPUT_DIR directory must not be the same as path/ directory of the INPUT_DIR.

OWB_ORACLE_HOME=/export/home/oracle/10.2.0.2/owb/10gR2 TCL_SCRIPTS_DIRECTORY=/export/home/oracle/darwin_qadrop3/ebilling/oracle/olap/etl MDL_LOCATION=/export/home/oracle/darwin_qadrop3/ebilling/oracle/olap/etl MDL_NAME=ebilling_etl_v6.0.mdl PROJECT_NAME=EBILLING_ETL TARGET_MODULE=MAPPINGS REP_USER=rep_admin TGT_USER=rep_admin TGT_PWD=darwin OWB_HOST=sdcv440s098.siebel.com OWB_PORT=1521 OWB_SERVICE=darwin SYS_PASSWD=change_on_install OLAP_USER=OLAP OLAP_PASSWD=OLAP OLAP_SID=darwin INPUT_DIR=/export/home/oracle/testdata/OWF_INDATA OUTPUT_DIR=/export/home/oracle/testdata/OWF_OUTDATA REJECT_DIR=/export/home/oracle/testdata/OWF_REJDATA

SHELL_VAR=/usr/bin/sh

Open a command prompt and change to the directory containing the owbadmin.properties file.

100

Installation Guide for Oracle eBilling Version 6.0

Installing Oracle eBilling ETL Installing the ETL Module

Enter the following commands to set up your OWB and Apache Ant environments, substituting the paths of your OWB and Ant installations (and correct lashes for your platform). set OWB_HOME=/export/home/oracle/product/owb_home set ANT_HOME=/opt/apache-ant-1.6.5 set PATH=%PATH%;%ANT_HOME%/bin

From the /opt/Oracle/eBilling/db/ebilling/oracle/olap/etl (or Oracle\eBilling\db\ebilling\oracle\olap\etl in Windows) directory, run the command: ant (This runs the build.xml file in that directory.) The ETL Module installation menu appears: Main: [echo] [1]. Create ETL package [echo] [2]. Import MDL [echo] [3]. OWB Mappings Deployment [echo] [Q]. Quit [input] Enter your selection(1,2,3,q,Q)

5 6

Select Option 1 and press enter to create the ETL package. When finished, check the etl_packages.log file for errors. After the create ETL package task completes, run Ant again and choose Option 2. When finished, check the <MDL File Name>.log file for errors. Login to the Design Center and make sure all modules are connected to the database locations. For ETL_PF_MODULE, check the LOCATION and Evaluation Location as well. After the import MDL task completes, run Ant again and choose Option 3. When finished, check the deploy.log file for errors.

Running the ETL Loader Job


The ETL module is now ready to load data. Sample data is provided with Oracle eBilling for testing purposes.

Installation Guide for Oracle eBilling Version 6.0

10 1

Installing Oracle eBilling ETL Installing the ETL Module

To run the ETL Loader job using sample data 1


Copy the following sample data files from $EDX_HOME\db\ebilling\oracle\olap\etl\sample_data (%EDX_HOME%/db/ebilling/oracle/olap/etl/sample_data on Windows) to the ETL input directory: MASTER-DATA-FILE-20070509.DAT EBILLING_B2B-DATA-FILE-20070510.DAT EBILLING_B2B-DATA-FILE-20070512.DAT EBILLING_B2C-DATA-FILE-20070516.DAT For consistency, it is recommended that you create the input directory in the same directory as the file locations previously defined in OWB Design Center.

2 3 4

Log in to the OWB Design Center as the repository owner. Launch the Control Center from the Tools menu. Expand the EBILLING_ETL_LOCATION, ETL_PF_MODULE, and ETL_SUP nodes. Right click the ETL_SUPER_PF_2 node (the ETL Loader job) and click Start. A dialog box might appear stating that the object must be deployed before execution. If this dialog appears click OK.

102

Installation Guide for Oracle eBilling Version 6.0

Uninstalling Oracle eBilling

This chapter describes how to uninstall Oracle eBilling. It includes the following topics: Preparing to Uninstall Oracle eBilling Uninstalling Oracle eBilling

Preparing to Uninstall Oracle eBilling


You must perform the tasks described here before uninstalling Oracle eBilling.

To prepare to uninstall Oracle eBilling components 1 2 3


Stop your application server. Stop your database instance. Stop your database server.

Uninstalling Oracle eBilling


You can uninstall and remove Oracle eBilling components and deployed J2EE applications using the Oracle eBilling Uninstaller. Uninstall Oracle eBilling from the database server first, then the application server. Note that the Uninstaller does not delete any directories that contain files modified since installation. Instead, it lists these items, which you must then remove manually.

To uninstall Oracle eBilling 1


Navigate to the Uninstall folder of your Oracle eBilling home directory. Launch the Oracle eBilling Uninstaller: Solaris and Linux: Run the command $EDX_HOME/Uninstall/Uninstall_eBilling Windows: Click the "Uninstall eBilling.exe" icon

2 3

When the Uninstall screen appears, click Uninstall. A second uninstall screen appears showing Oracle eBilling components being removed from your machine. When the Uninstaller is finished, a screen appears listing any items that could not be removed.

Installation Guide for Oracle eBilling Version 6.0

10 3

Uninstalling Oracle eBilling Uninstalling Oracle eBilling

4 5 6

Change the directory to your Oracle eBilling home directory and manually remove any remaining files and directories as necessary. Click Done to close the Uninstaller. Repeat this procedure on your application server and any other installations.

104

Installation Guide for Oracle eBilling Version 6.0

You might also like