Oracle CC&B的研究
Oracle CC&B全称Oracle Utilities Customer Care and Billing Solutions（即Oracle公用事业-客户服务、计费解决方案）。
Customer Care:Customer Interaction，Order Entry，Contract Management, Affinity Programs
（二）Customer Billing
Customer Billing：Rating Engine, Billing, and Loans
（三）Receivables Management
Receivables Management：Payment Processing，Non-billed Budgets and Credit & Collections，Overdue Processing，Deposits
（四）Competitive Energy Market
Competitive Energy Market: Multi-Party Billing，Open Market Interchange。
（五）Field Operations
Field Operations:Geographic Data Management，Premise Management, Service Points Management, Meter & Device Management, Meter Reading，Field Work，Appointments
（六）Energy Data Management
Meter Data Management, Complex Billing
逻辑架构图（Source）：
Information is presented in a web browser (Internet Explorer 6.0) using HTML and JavaScript (not Java, e.g. no applets).The browser communicates with a Web Application Server via HTTP.
The Web Application Server is divided into several logical tiers: presentation services, business logic, and data access.
Inbound HTTP requests are handled by Java Servlets in the presentation layer, which may in turn invoke data service objects. In turns, these objects may route control to Java-based business entities, which use the Hibernate ORM framework for data access and persistence. Various static data (control tables for drop-downs, language-specific messages/labels, etc.) are cached in the presentation layer of the Web Application Server. The presentation layer makes use of XSL/T technology to create HTML for the browser.
As the browser may need several "pages" to show all the information relating to a particular business entity, a JavaScript "model" is used to manage the data in toto, and the Internet Explorer XMLHTTP object is used to send the data to the server as an XML document. Data is provided to the browser as literal JavaScript. The specialized portal and dashboard areas use server-side XSL/T technology to render the final HTML directly on the server. The HTML for grids in the browser is
created using client-side MSXML XSL/T transforms.
This kind of architecture has been described by the term "AJAX", meaning Asynchronous Javascript and XML.
§ Client – The client component is a browser based interface which is "light" and only requires the Internet Explorer browser to operate.
§ 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.
Oracle Utilities Software Development Kit - 基于Eclipse平台的开发套件
9537502 - Oracle Utilities SDK 2.2.0.11 (for OUAF V2.2 based products)
10043375 - Oracle Utilities SDK 4.0.0.4 (for OUAF V4.0.2 based products)
（OUAF - Oracle Utilities Application Framework）
===CC&B官方文档===
Oracle Utilities Customer Care and Billing Documents: Link
Oracle Utilities Application Framework Software Development Kit - Developer's Guide
Oracle Utilities Customer Care And Billing Operations and Configuration Guide Ver 2.3.1
注明：以上数据多来自于Oracle官方网站的宣传资料，具体查看相关链接。
转载请注明出处： http://blog.csdn.net/pan_tian/article/details/9933373