Oracle CC&B的研究

Posted 2022-07-16 田攀

tags:

篇首语：本文由小常识网(cha138.com)小编为大家整理，主要介绍了Oracle CC&B的研究相关的知识，希望对你有一定的参考价值。

Oracle CC&B资料非常的少，花了些时间研究了下CC&B，分享了。

Oracle CC&B全称Oracle Utilities Customer Care and Billing Solutions（即Oracle公用事业-客户服务、计费解决方案）。

Oracle官方对CC&B的宣传口号是： 最完整的公用事业解决方案，实现卓越运营，提升客户服务。
===CC&B的历史=== * 1979年SPL WorldGroup在San Francisco成立。SPL公司主要为公用事业企业开发计费和运营管理软件，为政府部门开发税务管理软件。电力公司、燃气公司和自来水公司等客户使用这些软件用于客户和帐单管理、移动人员管理、停电和配电管理以及资产管理。
* 2006年11月Oracle收购SPL WorldGroup，随着这一收购完成，Oracle开始进军公用事业领域。并且Oracle逐步把自身的强项数据库、中间件、ERP与SPL相融合，形成更全面，更系统的行业解决方案。
*故事还没有结束，2007年4月，Oracle又收购了Lodestar，这是一家仪表数据管理和公用事业产品提供商，从而公用事业企业提供更完美的服务。
CC&B最早是SPL公司下边的一个产品，后来随着上述收购、融合，逐渐形成了现在的Oracle CC&B (Oracle Utilities Customer Care and Billing Solutions)，

Links: Oracle Buys SPL Oracle and SPL Oracle and LODESTAR Acquisition Announcement
===CC&B市场情况=== 在美国，Oracle应用系统在公用事业领域，占有率非常高。

(上述数据为2007年的市场情况)
2008年Oracle公用事业产品赢得的客户，以及上线的客户。
典型客户

===功能模块=== Oracle CC&B 为水、电、气等公用事业产业处理客户服务和计费，管理流动作业员工需求、资产管理、销售和损耗。

模块（一）Customer Care
    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
===CC&B优势功能=== * 公共事业领域(水、电、气...)的专业系统 * 客户服务 * 计费 * 税务管理
===技术架构=== CC&B在早期的版本（V1,V2.0）主要采取 Java + Cobol语言的J2EE架构(Cobol是一门非常古老的面向商业的通用语言) ；随着V2.2,V2.3以及之后的版本，Java的比重在逐步提升，很多后台的Cobol的业务逻辑代码也被Java所替代。

从界面上看，CC&B貌似使用的是Oracle ADF技术框架，但一些资料（eg. Note 1204543.1）显示，CC&B只是使用了ADF的界面展示效果（长相类似与Oracle Fusion），实际的技术框架很可能还是SPL原来自有的J2EE架构+COBOL
逻辑架构图（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.

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. Secure Sockets (HTTPS) is also supported 1 . 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.

§ 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.