手机版

主页 > 文库下载 > 实用文档 > 内容

CC&B_Operations_and_Configuration_Guide_V220

发布时间：2024-10-18 来源：未知

小中大

字号：

Oracle CC&B(Customer Care And Billing)批操作与配制指南V2.2.0

Oracle Utilities Customer Care And Billing

Operations and Configuration Guide

Ver 2.2.0 (OUAF SP7)

April 2010

Oracle CC&B(Customer Care And Billing)批操作与配制指南V2.2.0

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 error-free. 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.

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 developed for general use in a variety of information management applications. They are not developed or intended for use in any inherently dangerous applications including applications which may create a risk of personal injury. If you use the Programs in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of the Programs. Oracle disclaims any liability for any damages caused by use of the Programs in dangerous applications.

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.

Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. ©

Oracle CC&B(Customer Care And Billing)批操作与配制指南V2.2.0

Oracle Utilities Customer Care And Billing Operations and Configuration Guide (Ver 2.2.0 (OUAF SP7)) Table of Contents

Introduction ................................................................................................................................ 4

Updates to This Documentation .......................................................................................... 4

Other Documentation .......................................................................................................... 4

Architecture ................................................................................................................................ 5

Roles and Features ............................................................................................................. 6

Concepts .................................................................................................................................... 9

Environment ........................................................................................................................ 9

Administration User Id and Group ....................................................................................... 9

Directory Structure ............................................................................................................ 10

Environment Variables ...................................................................................................... 14

Common Application Logs ................................................................................................ 17

Attaching to an Environment ............................................................................................. 18

Utilities ..................................................................................................................................... 20

splenviron – Set Environment variables ............................................................................ 20

configureEnv – Setup Environment settings ..................................................................... 22

spl – Start/Stop Environment ............................................................................................ 22

genappvieweritems – generate AppViewer ...................................................................... 24

genoasdeploy – Deploy on ORACLE Application Server ................................................. 25

genoc4jdeploy – Deploy on OC4J .................................................................................... 26

genupdatewar – Generate J2EE WAR and EAR files ...................................................... 26

genwasdeploy – Deploy on WebSphere ........................................................................... 27

genwasstubs.sh – Generate WebSphere Stubs for business application server ............. 28

initialSetup – Reset configuration to template .................................................................. 29

Common Operations ............................................................................................................... 31

Starting an Environment.................................................................................................... 31

Stopping an Environment .................................................................................................. 35

Monitoring ................................................................................................................................ 39

Monitoring Regimes .......................................................................................................... 39

Monitoring Client Machines ............................................................................................... 40

Monitoring Web/business Application Server ................................................................... 42

Configuration ........................................................................................................................... 45

Configuration Files ............................................................................................................ 45

Web Browser Configuration .............................................................................................. 51

Web application server Configuration ............................................................................... 52

Business Application Server Configuration ....................................................................... 65

Miscellaneous Operations And Configuration ......................................................................... 78

Enabling Email Logging from Log4j .................................................................................. 78

Installation of decoupled servers ...................................................................................... 79

Overriding the default Oracle database connection information ....................................... 81

Automatic shunning of Child COBOL JVM's ..................................................................... 82

Cache Management .......................................................................................................... 83

Oracle CC&B(Customer Care And Billing)批操作与配制指南V2.2.0

Operations and Configuration Guide (Ver 2.2.0 (OUAF SP7)) Oracle Utilities Customer Care And Billing Contents

Introduction

Architecture

Concepts

Utilities

Common Operations

Monitoring

Configuration

Miscellaneous Operations And Configuration

Introduction

Welcome to the Oracle Utilities Customer Care And Billing Operations and Configuration Guide for Ver

2.2.0 (OUAF SP7). This guide outlines the technical concepts for operating and configuring the product on its platforms as outlined in the product installation documentation.

Contents

Updates to This Documentation

Other Documentation

Updates to This Documentation

This documentation is provided with the version of the product indicated. Additional and updated information about the operations and configuration of the product is available from the Knowledge Base section of ORACLE MetaLink (). Please refer to MetaLink for more information. Other Documentation

This document is part of the product technical documentation. There are groups of manuals that should also be read for additional specific advice and information:

Oracle CC&B(Customer Care And Billing)批操作与配制指南V2.2.0

Oracle Utilities Customer Care And Billing Operations and Configuration Guide (Ver 2.2.0 (OUAF SP7))

Architecture

The product is a multi-layered product with distinct tiers. The diagram below illustrates the architecture of the product:

Web Application Server

Business Application Server

Database Server

The components of the architecture are as follows:

§ Client – The client component is a browser based interface which is "light" and only requires the Internet Explorer browser to operate.

§ Communication between the client and server uses the HTTP protocol across a TCP/IP network.

1Secure Sockets (HTTPS) is also supported. The user simply uses a URL containing the product

hostname and allocated port number in the address bar of Internet Explorer to access the application.

Refer to the J2EE Web application server manuals for information on how to configure the HTTPS

protocol. 1

Oracle CC&B(Customer Care And Billing)批操作与配制指南V2.2.0

Operations and Configuration Guide (Ver 2.2.0 (OUAF SP7)) Oracle Utilities Customer Care And Billing

§ Web application server – The product Web Application is housed in a J2EE compliant Web application server (Refer to the Supported Platforms section of the installation guide for J2EE Web application servers and versions supported) This server can be run on a variety of supported Windows, Linux and Unix platforms (Refer to the Supported Platforms section of the guide for operating systems and versions supported). Within the Web application server the pages for the product are rendered using a combination of meta data and formatting rules to ensure a consistent look and feel. These pages are written using a combination of J2EE Java script and Java. These pages are cached on the Web Server and served to the client upon request. If the page requires business rules to be invoked then business objects are called from this server.

§ Business application server – As of V2.2 of the product, the business component of the architecture can be installed as part of the Web application server or as a separate component. This means the business application server is also housed in a J2EE compliant Web application server (Refer to the Supported Platforms section of the installation guide for J2EE Web application servers and versions supported). This server can be run on a variety of supported Windows, Linux and Unix platforms (Refer to the Supported Platforms section of the installation guide for operating systems and versions supported). Within the business application server the following components are implemented:

§ Business Objects – The business logic for each object in the system is expressed as a

COBOL or Java object. It contains all the SQL, programmatic rules and structures to manage

the data for the transactions. In some products, COBOL is supported for our legacy customers

and it is up to the site whether COBOL or Java is used for any extensions to the business

objects.

§ DB Connection Pool – If any database access is required, we use an industry component called Hibernate to manage and pool the connections to the database. This will reserve

connections and ensure efficient use of connections to the database.

§ To access the database product uses the networking client provided by the DBMS vendors to ensure correct connection. For example, ORACLE provides SQL*NET, DB2 provides UDB Connect and SQL Server uses .NET drivers. These clients are multi-protocol for maximum flexibility.

§ Database Server – The RDBMS used for the implementation is implemented in the database server. The product supports a number of databases (Refer to the Supported Platforms section of the installation guide for databases and versions supported). The database server only stores and retrieves the data for the product as all the business logic is in the business objects.

Roles and Features

Each tier in the architecture has a specific role in the operation of the product. The sections below outline the roles and features of each tier.

Contents

Oracle CC&B(Customer Care And Billing)批操作与配制指南V2.2.0

Oracle Utilities Customer Care And Billing Operations and Configuration Guide (Ver 2.2.0 (OUAF SP7))

Client

Web application server

business application server

Database Server

Client

The Browser User interface (BUI) is a combination of HTML and Java-script. AJAX, shorthand for Asynchronous JavaScript and XML, is a Web development technique for creating interactive Web applications. This makes web pages more responsive by exchanging small amounts of data with the server, so that the entire page does not have to be reloaded each time the user makes a change. This increases the Web page's interactivity, speed, and usability.

There are no ActiveX or Java components in the base product installation. This means that the deployment of the browser client is relatively simple as the only required component to use the product is a supported version of Internet Explorer on the client machine. If the implementation requires ActiveX controls for extensions then you can add them.

The Browser tier of the product is provided for the end users to access the product on a desktop. The client provides the following roles in the architecture:

§ Screen Rendering and Caching – All the screens are rendered using standard HTML and

JavaScript (not Java). The rendering is performed as the screen is served from the Web

Application server and stored in the local browser cache.

User Interaction – The client provides the user with the screen interaction. After page is

rendered the user can interact (manipulate data and screen elements) as per their business

transaction. The browser client is responsible for ensuring that users can navigate and interact

with the screen elements (e.g. resizing, display correctly).

User Context – The product is stateless and therefore the client stores the transactional context

locally and passes this to the transaction as required. The client records the context of the

transaction in the browser memory.

Screen Cookie Management – After a user is authenticated by the Web application server, the

client is issued a JSR compliant cookie which is used as the credentials for all subsequent

transactions. This cookie is a session cookie, which means it is stored in memory and removed

when the browser is shutdown. § § §

No business logic is stored on the client component.

Web Application Server

The product is a J2EE set of Web applications that are housed in a J2EE compliant Web application server. The product and the Web application server provide the following roles in the architecture:

§ Authentication – The Web application server software that houses the product provides

adapters to common security repositories. This means that security products interfaced to the

Web application server software can be used in conjunction (with configuration) with the product.

Oracle CC&B(Customer Care And Billing)批操作与配制指南V2.2.0

Operations and Configuration Guide (Ver 2.2.0 (OUAF SP7)) Oracle Utilities Customer Care And Billing

§

§ Managing Client connections – The Web application server software manages any client connections (during and after they are authenticated) for processing and availability. Page Server – The major responsibility of the Web application server is to "serve" pages to the

client on demand. At startup time (or at the first request for a particular page) the product generates the screens dynamically using metadata and rendering style sheets. These are cached

for reuse locally.

Cache management – For performance reasons, the static data (usually metadata and configuration data) is cached in memory on the Web application server. §

No business logic is stored on the Web application server component. The Web application server Component of the product is written in Java and JavaScript.

Business Application Server

The product is a J2EE set of business applications that are housed in a J2EE compliant Web application server (this can be the same instance of the Web application server or a separate one). The product and the business application server provide the following roles in the architecture:

§ Authorization – After authentication has been performed by the Web application server, the

Business Application server is responsible for determining which functions and which data can be

accessed.

Data Integrity – The business application server contains the business logic to maintain referential integrity for the product data.

Validation – The business application server contains the business logic that contains all the validation rules for the product data.

Business Rules – The business application server contains the business logic that implements

business rules and performs calculations.

SQL – The business application server contains all the SQL statements and formats and

processes results from those SQL statements. § § § §

The business application server Component of the product is written in Java and may contain COBOL for backward compatibility.

Database Server

The product contains a database schema within a database management system. The database server has the following roles in the architecture:

§

§ Data Storage – The database is responsible for efficiently storing all data. Data Retrieval – The database is responsible for efficiently retrieving data using SQL provided by the business application server. Data Management – The database is responsible for efficiently managing all data. No business logic is stored on the Database Server.

Oracle CC&B(Customer Care And Billing)批操作与配制指南V2.2.0

Oracle Utilities Customer Care And Billing Operations and Configuration Guide (Ver 2.2.0 (OUAF SP7)) Concepts

Before you attempt to configure or operate the product, there are important concepts that you should understand. These concepts are addressed in this document as a basis for the other documents in the technical documentation.

Contents

Environment

Administration User Id and Group

Directory Structure

Environment Variables

Common Application Logs

Attaching to an Environment Environment

In a product implementation and post-implementation there will be a number of copies of the product installed. Each copy of the product is known as an environment. Each environment will be created for a specific purpose, according to your site plans, and accessible to a group of users deemed necessary for that purpose. For example, there will be at least one testing environment where designated personnel will perform their testing tasks.

For planning purposes an environment is a single instance of:

§

§ The Web applications deployed in a J2EE Web application server. The business applications deployed in a J2EE Web application server. This can be the same physical J2EE Web application server or another instance (such as a separate server). A database containing the product schema. Physically, a schema can exist in an individual

database instance or shared within a database instance (i.e. you can install multiple schemas of

the product in the same database).

While there is no restriction on the number of environments it is recommended that the minimal number of copies of the product be installed using the guidelines outlined in the "Environment Management" document in the "Software Configuration Management" series on MetaLink (Refer to Other Documentation). Administration User Id and Group

Prior to installing the product, you create a UNIX administration user ID and administration group. This account is used to install and operate the product. The product administration user ID and product group is provided as a parameter during the installation process. By default, the product administration user ID is cissys (CCBUSER parameter) and the group is cissys (CCBGROUP parameter). However, alternative values can be used according to your site standards.

The administration user ID is responsible for the following:

§ It is the owner of the majority of the files installed for the product.

Oracle CC&B(Customer Care And Billing)批操作与配制指南V2.2.0

Operations and Configuration Guide (Ver 2.2.0 (OUAF SP7)) Oracle Utilities Customer Care And Billing

§

§ It is the only user ID that should be used to run any of the administration tools provided with the product. It is the user ID that owns the UNIX resources used by the product. When the product is running,

this user ID owns the processes associated with running the base software.

The administration user ID should be protected from unauthorized use. If components of the responsibility of administration need to be delegated to other users on the machine, we recommend not giving out the administration user ID. Instead, an alternative solution should be sought (such as using sudo or similar security tools).

The administration user ID should not be used for any of the following:

§

§ As a product end user. By default, the administration user ID does not have access to the functionality of the product. To run product background processes. To manipulate data files exported from or imported into the product from any interfaces.

This technical document will refer to the administration user ID as cissys. If your site uses an alternative user ID as the administration user ID, substitute that user ID value for cissys.

Directory Structure

In an effort to facilitate upgrades and ease maintenance, the product installation process creates a very specific directory hierarchy under the administration user ID of cissys

(by default). The structure holds all the code, system products, scripts and temporary files that are created by the product during installation and operation.

There are two different directory structures that the product application uses:

§

§ Base code directory structure known as <SPLDIR> Application output directory structure / log directory known as <SPLDIROUT>

Within each of the structures, there is a mount point and a subdirectory for each environment <environment> installed on the machine. The base mount point <SPLDIR> contains the environment directories that hold all of the application software for each particular environment. The application output mount point <SPLDIROUT> contains the environment directories that hold temporary files (such as the output from Doc 1) as well as batch log files. The default <SPLDIR> directory is /spl and the default <SPLDIROUT> directory is /spl/sploutput.

Oracle CC&B(Customer Care And Billing)批操作与配制指南V2.2.0

Oracle Utilities Customer Care And Billing Operations and Configuration Guide (Ver 2.2.0 (OUAF SP7)) When a user logs on to a particular environment of the product either using the browser-based interface or directly on UNIX/Windows, the environment is set up (i.e. environment variables, etc.) to point to the appropriate directory structure under the mount point. The environment variable that points to an environment directory under <SPLDIR> is $SPLEBASE (or %SPLEBASE% in Windows). The environment variable that points to an environment directory under <SPLDIROUT> is $SPLOUTPUT (or %SPLOUTPUT% on Windows). The SPLEBASE and SPLOUTPUT environment variables are two of the standard environment variables used by the utilities provided with the product and runtime.

The actual location for the mount points can differ per environment if you want. This is handy if you need to vary the location because you do not have enough space for all your non-production environments. Typically the number of environments during an implementation varies according to the level of access and desired amount of testing and training. The only restriction is that there can only be one location for SPLEBASE and SPLOUTPUT per environment.

Contents

Software Directory Structure Output Structure

Software Directory Structure

The following components are stored in the base code directory structure:

§

§ Runtimes for Components – All the runtime executables for the base software. Business Object Binaries – All the binaries that contain the business logic. Configuration Files – All the configuration files for the business objects and runtimes Scripts – Any administration or runtime scripts that are supplied to the customer. Supported Plug-ins – Source and executable for supplied plug-ins.

The following illustration depicts the layout of where the product code is placed upon installation into the file system:

Oracle CC&B(Customer Care And Billing)批操作与配制指南V2.2.0

Operations and Configuration Guide (Ver 2.2.0 (OUAF SP7)) Oracle Utilities Customer Care And Billing

Contents of the directories:

Oracle CC&B(Customer Care And Billing)批操作与配制指南V2.2.0

Oracle Utilities Customer Care And Billing Operations and Configuration Guide (Ver 2.2.0 (OUAF SP7))

Oracle CC&B(Customer Care And Billing)批操作与配制指南V2.2.0

Operations and Configuration Guide (Ver 2.2.0 (OUAF SP7)) Oracle Utilities Customer Care And Billing Output Structure

The product processes (batch and online) that produce output and logs place information in this directory structure. The environment directories are referenced by the variable SPLOUTPUT. By default, this directory is created as /spl/splapp, though an alternative may be used during the installation process.

Environment Variables

The product uses a number of environment variables to determine where information is stored and to be placed for its internal operations. Becoming familiar with these variables will assist you in finding information quickly and efficiently.

The following table outlines all the variables:

Oracle CC&B(Customer Care And Billing)批操作与配制指南V2.2.0

CC&B_Operations_and_Configuration_Guide_V220.doc 将本文的Word文档下载到电脑，方便复制、编辑、收藏和打印

下载这篇word文档

上一篇：南玻A：2011年非公开发行A股股票预案 2011-01-19

下一篇：氟离子选择电极测定尿氟正常值

×

二维码

相

关

文

章