Professional Documents
Culture Documents
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
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:
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
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
Contents
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
54 57 58 58
Deploying Oracle eBilling Applications on Solaris or Windows Running the eBilling Applications
Chapter 3:
Managing the Oracle Application Server Environment Configuring the Oracle Database 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
Contents
87
87
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:
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
99
101
Chapter 5:
Contents
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.
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.
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.
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.
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
Supported Browsers
Microsoft Internet Explorer 6.0 and 7.0 Mozilla Firefox 2.0
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
11
Supported Browsers
Microsoft Internet Explorer 6.0 and 7.0 Mozilla Firefox 2.0 or later
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
12
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.
13
14
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
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.
16
Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring the Oracle Database
Note that database clustering is handled by your application server and not by Oracle eBilling. Consult your Professional Services representative for clustered installations.
17
Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring the Oracle Database
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
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.
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.
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
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
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
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)
22
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.
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
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
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.)
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.
26
Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring the Oracle Database
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
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.
27
Installing on WebLogic and Oracle Database (Solaris or Windows) Configuring the Oracle Database
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
28
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.
29
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 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
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
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.
32
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.
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
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
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
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
Grant the create materialized view privilege to the user you are migrating: SQL> grant create materialized view to <username>;
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.
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
36
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;
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;
37
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
38
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.
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
39
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
Table 2. Name
Data Sources for the eBilling Application JNDI Name edx.databasePool edx.xma.databasePool edx.report.databasePool Transaction Emulate Two-Phase Commit
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
40
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
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.
41
Table 5. Name
MS Persistence Store Values for the eBilling Application Target Select Your Server (AdminServer) Directory Directory Location to Save Store
EventsFileStore
Table 6. Name
MS Server Values for the eBilling Application Persistence Store EventsFileStore Target Select Your Server (AdminServer)
EventJMSServer
42
Click Finish.
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
Table 8.
JMS Queue Connection Factory Values for the eBilling Application Name EventsConnectionFactory JNDI Name edx.qcf Target Select Your Server (AdminServer)
Select created connection factory and enable XA Transaction under Transactions tab.
43
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
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.
Under Destinations tab, create a new Foreign Destinations using the following values:
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:
Foreign Connection Factory Values for the Oracle eBilling Application Local JNDI Name edx.foreign.qcf Remote JNDI Name edx.qcf
ForeignConnectionFactory
44
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.
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
45
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
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
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
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
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.
JMS Module Properties for the Command Center Application Description Your JMS Module Name Your Descriptor File Name Example Factories Factories
48
JMS Module Properties for the Command Center Application Description Your Location in Domain Select Your Server Example Factories AdminServer
4 5
Select the check boxes to target the system module at the servers running the Oracle eBilling application. Click Next. 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
Select created connection factory and enable XA Transaction under Transactions tab.
49
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 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.
Queue and JNDI Names for the Command Center Application JNDI Name edx.queue.logger edx.queue.outbound Target LoggerJMSServer EventsJMSServer
LoggerQueue EventsQueue
50
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.
Under the Destinations tab, create a new Foreign Destinations, with the following values:
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:
Foreign Connection Factory Values for the Command Center Application Local JNDI Name edx.foreign.qcf Remote JNDI Name edx.qcf
ccForeignConnectionFactory
51
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
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
53
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.
54
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.
55
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] -----------------------------------------------------------------------[ERROR] BUILD ERROR [INFO] -----------------------------------------------------------------------[INFO] Failed to resolve artifact.
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
Installing on WebLogic and Oracle Database (Solaris or Windows) Deploying Oracle eBilling Applications on Solaris or Windows
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.
Select the deployed EAR and start all services located at the Start > Servicing all requests.
57
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.
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
Table 24.
Sample Oracle eBilling Application URLs URL Example http://localhost:7001/ebilling http://localhost:7003/ebilling http://localhost:7006/ebillingcsr
58
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
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".
59
Installing on WebLogic and Oracle Database (Solaris or Windows) Running the eBilling Applications
60
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
61
Installing on Linux, Oracle Database, and Oracle Application Server Managing the Oracle Application Server Environment
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.
62
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.
63
Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux
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
Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux
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
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.
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).
Run the following command to start the server: $./opmnctl startall Run the following command to stop the server: $./opmnctl stopall
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.
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
Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux
Table 26.
Connection Pools for the eBilling Application Connection Factory Class oracle.jdbc.OracleDriver oracle.jdbc.xa.client.OracleXADataSource oracle.jdbc.xa.client.OracleXADataSource
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
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.
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.
68
Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux
Click Finish.
Data Source Properties Description Data Source Name Data Source Related JNDI Global and Local Transactions Data Source Related Connection Pool Default Value
Table 29.
Data Sources for the eBilling Application JNDI Locations edx.databasePool edx.report.databasePool edx.xma.databasePool Connection Pool edxAdminConnectionPool olapConnectionPool oltpConnectionPool
69
Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux
<!-- 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>
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
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.
71
Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux
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
Table 31.
Queue Destinations for the eBilling Application Destination Name foreignQueue outboundQueue JNDI Location edx.foreign.queue.outbound edx.queue.outbound
To configure opmn.xml 1
Open the OAS_HOME/opmn/conf/opmn.xml file.
72
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 "/".
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>
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>
74
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" />
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" />
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.
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
Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux
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.
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
78
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.
79
Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux
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
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
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 "/".
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
true
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 -
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>
82
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" />
To configure Jikes for the Command Center, follow the instructions given for Configuring Jikes for Oracle eBilling on page 75.
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.
83
Installing on Linux, Oracle Database, and Oracle Application Server Configuring the Oracle Application Server for Linux
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 "/".
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
true
PATH
true
84
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>
85
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 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" / >
Modifying csr.xma.xml
You must configure the csr.xma.xml file with the URL strings CSR needs to impersonate the user.
86
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.
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.
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.
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
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
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.
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]
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
90
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
Login using the user name "admin" and the password oracle.
Log in to the CSR application as the CSR Administrator or CSR role user. Use the usernameedocsadmin and password 111111 to log in.
91
Installing on Linux, Oracle Database, and Oracle Application Server Running the eBilling Applications on Linux and OAS
92
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
93
The database is now ready for installation of the OWB repository schema.
2 3
On the Welcome screen click Next. Select Advanced Setup and click Next.
94
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.
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.
95
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
96
It is recommended that you select Test Connection before clicking OK to verify that you have supplied the correct parameters.
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
97
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.
98
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.
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.
99
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
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.
10 1
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
This chapter describes how to uninstall Oracle eBilling. It includes the following topics: Preparing to Uninstall Oracle eBilling Uninstalling Oracle eBilling
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.
10 3
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