掌握Oracle DBA在PeopleSoft技术中的应用

需积分: 0 43 浏览量更新于2024-07-18 收藏 9.39MB PDF 举报

"PeopleSoft.Oracle.DBA.2nd" 这本书是专为Oracle数据库管理员（DBA）设计的，旨在帮助他们理解和应用PeopleSoft技术。对于大多数DBA来说，初次接触PeopleSoft可能会遇到一些意料之外的情况，这些情况可能并非全然令人满意。通常，DBA需要管理多个不同的数据库，每个数据库支持不同的应用程序。他们往往希望以标准化的方式管理所有数据库，但PeopleSoft系统可能并不完全符合这种期望。书中内容涵盖了多个章节，深入浅出地介绍了与PeopleSoft相关的各种主题。以下是一些关键章节的概览： 1. **第1章：概述** - 提供了对PeopleSoft技术的基本介绍，包括其在企业环境中的角色和重要性。 2. **第2章：BEA Tuxedo：PeopleSoft的应用服务器技术** - 解释了PeopleSoft如何利用BEA Tuxedo作为应用服务器平台，以及它如何处理并发性和事务管理。 3. **第3章：数据库连接性** - 讨论了PeopleSoft如何与不同的数据库系统进行交互，包括数据源的配置和连接选项。 4. **第4章：PeopleSoft数据库结构：双数据字典的故事** - 揭示了PeopleSoft特有的双数据字典结构，这是其与其他Oracle应用不同的关键特性。 5. **第5章：键和索引** - 详述了PeopleSoft中的数据模型，包括主键、外键以及优化查询性能的索引策略。 6. **第6章：PeopleSoft DDL** - 阐述了用于创建和管理PeopleSoft对象的SQL语句和DDL命令。 7. **第7章：表空间** - 讨论了如何有效地管理表空间，以满足PeopleSoft系统的存储需求。 8. **第8章：锁定、事务和并发性** - 解释了PeopleSoft的锁定机制，事务处理以及在高并发环境中的最佳实践。 9. **第9章：性能指标** - 介绍了监控和度量PeopleSoft系统性能的关键指标。 10. **第10章：PeopleTools性能实用工具** - 详细介绍了PeopleTools提供的用于性能调优的各种工具和功能。 11. **第11章：SQL优化技巧在PeopleSoft中的应用** - 提供了优化PeopleSoft环境中SQL查询的策略和技术。 12. **第12章：配置应用服务器** - 指导读者如何根据具体需求配置和调整PeopleSoft应用服务器。 13. **第13章：调优应用服务器** - 分享了提高应用服务器性能的技巧和方法。 14. **第14章：过程调度器** - 介绍了PeopleSoft中的任务调度功能，以及如何安排和管理周期性任务。此外，书末还有索引，方便读者快速查找特定主题。本书作者结合实际经验，为Oracle DBA提供了深入了解和管理PeopleSoft系统所需的全面指南，无论是在日常维护还是性能优化方面，都提供了宝贵的洞见。

CHAPTER 1  AN OVERVIEW

This two-tier model started to show strain in a number of areas. The traffic across the network was

mostly SQL conversations with the database; and because a relatively simple action in an application

could generate many messages, network latency became a problem. Another issue was rolling out new

clients and synchronizing the rollout with changes to the database.

Until version 6, PeopleSoft was a fairly typical two-tier client/server application. PeopleTools and

the database connectivity software (SQL*Net in the case of Oracle) had to be installed on every desktop.

The online parts of PeopleSoft applications were stored as metadata in the PeopleTools tables in the

database. The client program loaded, interpreted, and executed the instructions in these tables, and the

development tools manipulated this metadata. This approach mitigated, but did not eliminate, the

problem of rolling out new versions of the client every time the slightest application change was made.

However, the act of querying the PeopleTools tables in turn created significant amounts of database

activity and network traffic, so the PeopleTools client cached the information that it retrieved from the

PeopleTools tables to the local disk of the Windows PC. If the cache was up to date, the PeopleTools

client did not query the PeopleTools tables. This approach is still used in current version of PeopleTools.

Three-Tier Application Server Architecture

Three-tier computing models emerged to deal with the limitations of the two-tier model. As much as

possible of the business logic layer was moved back into the data center, close to the database (see

Figure 1-4). This reduced the size of the client and the volume and number of messages that needed to

travel between client and server.

Figure 1-4. A first-generation three-tier client/server model

Oracle developed PL/SQL (Procedural SQL) to make it possible to write procedural program code

that could either be stored and executed within the database or within Oracle applications or bespoke

applications written with Oracle development tools. In this scenario, some of the business logic was

moved inside the database server itself.

CHAPTER 1  AN OVERVIEW

However, PeopleSoft’s platform-independent approach precludes the use of database server–based

code. None of the PeopleSoft application is executed within the database, although much of it is stored

in the database in the form of metadata. However, in version 8, PeopleSoft started to make limited use of

database triggers for populating audit tables and the now-discontinued Mobile Agents.

When PeopleSoft introduced a three-tier client with an application sever in PeopleTools 7.0, it chose

to use BEA’s Tuxedo product. The application server is a completely separate tier from the database, and

it is normally placed on a different machine. This model (see Figure 1-5) can therefore be scaled

horizontally by using multiple application servers on different nodes.

Figure 1-5. The Tuxedo second-generation three-tier client/server model

PeopleSoft developed its own procedural language, PeopleCode, in which it codes additional

business logic. Pieces of PeopleCode are defined on certain columns in the application, and that code is

executed when certain events in the client occur. In the two-tier client, PeopleCode was executed on the

client, but in three-tier mode most of the PeopleCode is executed by the application server.

As a result, it is now the application server, rather than the client, that makes the connection to the

database. The server loads the application metadata from the PeopleTools tables, executes most of the

application code, and retrieves and updates the application data. Both the client and the application

server cache the application code retrieved from the PeopleTools tables. The end result is that there are

fewer connections to the database, easing memory management.

 Note Only application code (metadata) is cached by client processes. This includes the application server, and

Application Engine from PeopleTools 8. Since PeopleTools 7, application data is never cached by the client

processes, although in earlier versions the PeopleTools client could optionally cache static application data.

Not only is the total volume of network traffic between the client and the application server reduced

in the three-tier model, but the number of network messages is also greatly reduced. There are fewer,

CHAPTER 1  AN OVERVIEW

although individually larger, messages in three-tier mode. Every time a two-tier client fetches a row from

a SQL cursor, a message is sent to the database, and the client must wait for a response. In a three-tier

application, all of the data, possibly from many cursors, is returned to the client in a single message.

Thus, three-tier clients are less susceptible to network latency.

Four-Tier Internet Architecture

In PeopleTools version 8, the Windows client was replaced by the PeopleSoft Internet architecture. The

client is now just a web browser. There is no longer a problem rolling out PeopleSoft software or

packaging it into a corporate desktop. Now you can use PeopleSoft from something other than a

Windows PC.

This change has been achieved by building on the existing PeopleSoft three-tier model. PeopleSoft

now delivers a Java servlet that runs on the web server (see Figure 1-6), and this servlet is the client of the

application server. The web server can be placed on the same or a different physical server from the

application server.

Figure 1-6. The PeopleSoft Internet Architecture (PIA)

“No code on the client” was the mantra of every PeopleSoft presentation I saw when version 8 was

introduced. PeopleSoft code does execute on the client, but you don’t have to preinstall it. The HTML

pages include JavaScript, which is generated by the application server and then served up to the browser

via the servlet. The JavaScript is executed when certain buttons are pushed or fields are navigated. Some

output formats require Microsoft Excel or Adobe Acrobat to be installed on the client.

Release History

PeopleSoft’s applications and PeopleTools have different version numbers that change independently.

The first digit for both of them, sometimes called the Enterprise Release Number, is usually, but not

always, the same. Some Enterprise releases have also had major upgrades (PeopleTools 7.5 and 8.4, for

example) to both the application and PeopleTools that must effectively be treated as if they were new

Enterprise releases. It is confusing, so it is important to specify whether a version number refers to an

application or to PeopleTools.

PeopleTools versions 3.x and 5.x were 16-bit Windows applications.

They only connected directly to

the database via the database API, which on Oracle is SQL*Net. Since it was a 16-bit application, it was

There was no PeopleTools version 4 because it is considered to be an unlucky number in some Asian

countries. Financials 3 and HRMS 4 ran on PeopleTools 3.

CHAPTER 1  AN OVERVIEW

only possible to use 16-bit SQL*Net. PeopleTools 5.x saw a major overhaul in the interface, replacing

pushbuttons with a menu. PeopleTools 5.1 has not been supported since 1999, and it was never certified

for Y2K.

PeopleTools 6 was a 32-bit Windows application. It corresponded to the introduction of Windows

95, the first 32-bit Windows release. However, it was still almost exclusively a two-tier application. I say

“almost” because this release saw the first appearance of the BEA Tuxedo application server, although it

was only used for Remote Call functionality. This allowed batch processes to be initiated from the client,

apparently synchronously, but to be executed on the application server. Within the delivered PeopleSoft

applications, Remote Call was only used in Financials for online voucher editing and posting.

PeopleTools 7.0 was released in September 1997. This release introduced the full three-tier model in

PeopleSoft. The Windows client was also able to connect to the BEA Tuxedo application server, which in

turn connected to the database as the client did in two-tier mode. In this version, the separate

development utilities (record designer, panel designer, and menu designer) were consolidated in the

new Application Designer.

PeopleTools 7.5 was released in May 1998. It saw the consolidation of the application server—new

application-server services were introduced to combine several service calls into one. This release also

saw the introduction of the Java client, a Java applet that was downloaded to the browser on a client PC.

It ran in the Java Virtual Machine (JVM) within the browser and connected to the application server.

Java-enabled browsers were, at that time, still relatively new, and this client was never particularly

popular, mainly due to the size of the applet download and memory leaks in some JVMs.

PeopleTools 8.0 was released at the very end of 1999, and it introduced a new and radical concept: a

purely Internet client. Each screen or panel in the PeopleTools applications was a page in this iClient.

This meant that the only software now needed on the user’s PC was a standard web browser. The pages

were rendered with JavaScript to enable the buttons on the page, and the client’s session is a thread

within a Java servlet that runs in a JVM that is either in or close to the web server. The servlet connects to

the application server, just as the Java client did in the previous release.

In August 2000, PeopleTools version 8.1 was introduced. The iClient was renamed as the PeopleSoft

Internet Architecture (PIA). Although the Windows client was still delivered, it was no longer a supported

runtime environment. PS/Query (the ad hoc reporting tool) and the nVision reporting plug-in for Excel

still exist as Windows executable applications to provide an alternative to the PIA functionality.

Application development is still done via a Windows client that connects in both two- and three-tier

modes.

PeopleTools 8.4 was the second release of the PIA, and there have been some changes to the look

and feel of the products. The breadcrumb navigation of version 8.1 was replaced with a menu portlet.

This release also no longer includes the Windows client, pstools.exe. With the exception of Query and

nVision, the PeopleSoft application is only available via the PIA.

Since acquisition, Oracle has continued to maintain and enhance both PeopleTools and the

PeopleSoft Applications. In 2006, Oracle’s Applications Unlimited commitment explicitly promised

indefinite “sustaining support” for PeopleSoft and announced a roadmap for version 9 applications.

However, Oracle cancelled the planned PeopleTools 9 release. There probably will never be a

PeopleTools 9, but each annual release of PeopleTools has brought enhancements and new features.

Generally, PeopleSoft remains platform agnostic, but Oracle has introduced features to help

manage PeopleSoft running on an Oracle database, and to use some Oracle database features. There is a

PeopleSoft plug-in to Oracle Enterprise Manager.

PeopleTools 8.50 uses the Oracle session instrumentation package (see Chapter 9).

PeopleTools 8.51 can perform read-only processing on an Active Data Guard standby database and

has support for Transparent Application Failover and Fast Application Notification. Application

Designer preserves any table or index partitioning.

剩余540页未读，继续阅读

breakenarrow

粉丝: 1
资源: 7

掌握Oracle DBA在PeopleSoft技术中的应用

Oracle PeopleSoft 8.56 更新镜像安装部署指南

Oracle PeopleSoft 开发指南：Application Designer 中文翻译

Oracle数据库入门详解与Oracle公司产品概览

PeopleSoft.for.the.Oracle.DBA.2nd.Edition

PeopleSoft.Developers.Guide.for.PeopleTools.and.PeopleCode.2009

英文原版-PeopleSoft for the Oracle DBA 2nd Edition

PeopleSoft for the Oracle DBA.pdf

D17108GC21.Oracle.Database.10g.SQL.Fundamentals.I

PeopleSoft vs Oracle：谁是谁的终结者.pdf

peoplesoft笔记.pdf

最新资源