Essential Guide to PeopleSoft Development and Customization

Essential Guide to PeopleSoft Development and Customization

by Tony Delia, Galina Landres, Prakash Sankaran, Isidor Rivera

Design and development techniques for implementing PeopleSoft.


Design and development techniques for implementing PeopleSoft.

Editorial Reviews

A comprehensive reference and tutorial for the collection of software modules for common business functions known as PeopleSoft. Written for both novice and experienced programmers, the book covers basics of application development, PeopleCode, PeopleTools, structured query report writer (SQR), PeopleSoft for online applications, customization with real examples, the Application Engine and Application Designer, and PeopleSoft COBOL and the PTPSQLRT module. Includes an overview of new features in release 8.0. Annotation c. Book News, Inc., Portland, OR (

Product Details

O'Reilly Media, Incorporated
Publication date:
Product dimensions:
7.45(w) x 9.26(h) x 2.17(d)

Read an Excerpt

Chapter 1: PeopleSoft Architecture

Two-tier architecture

Traditional client/server installations are defined as two-tier architecture, which means that two components exist in a two-tier structure, Client and Server. Client refers to the workstation used to access the application; Server refers to either a database server or some other type application server. In PeopleSoft, Server, in client/server architecture, always implies the database server which hosts the application database.

The following illustration can help us understand the two components and how they communicate between each other.

The client workstation converts the client request into SQL statements and communicates to the database server using database connectivity tools. The client workstation processes all user requests and transmits them across the network to the database server. Some advantages of a two-tier architecture are as follows:

  • simple architecture
  • easier administration
  • cost reduction
A two-tier architecture is ideal when the client is connected to the server on a local area network, but SQL transmissions are voluminous and, as a result, efficient transmissions are not possible across the wide area network. PeopleSoft and other client/server software applications wanted to overcome this challenge and make it possible for client workstations across wide area networks to have faster access to the application.

Three-tier architecture

Citrix Systems introduced an application server, which runs processes that would otherwise run on a client workstation. Users log in to the application server and sessions are run on the remote application server.Users transmit keystrokes and mouse-clicks to the application server which then transmits images back to the client workstation.

The application server acts as the third tier. The key advantage in configuring a third tier is that it is physically located near the database server. Communication between the database server and the application server is within a local area network or better. Data transmitted between the client and the application server is less voluminous than sending SQL requests across the wide area network directly to the database server. This concept reduces the size of data transmitted on the wide area network. Application servers provide a central point of administration as well. They are usually configured to have more processing power and memory. Multiple application servers can be configured to share loads from numerous clients accessing applications across the wide area network. Citrix servers are physical application servers, and there is always a cost involved in maintaining hardware. PeopleSoftjoined with BEA Systems to introduce a transaction-based application server called Tuxedo. Tuxedo application server is a collection of server processes that communicate to the database server. On the server side, workstation listeners are listening to client Tuxedo requests and sending them to the appropriate server process. These server processes request individual services, which can handle jobs such as SQL calls, panel group build, panel group save, and so forth. Some advantages in a physical three-tier architecture include:

  • remote session capabilities near the database server
  • reduction of network traffic by transmitting only keystrokes, mouse-clicks, and images across the wide area network
  • single point of administration and monitoring per application server
  • single point of installation per application server
  • load balancing using multiple application servers Some advantages in a Tuxedo-based three-tier architecture include:
  • the ability to transmit more requests using Tuxedo services than using SQL on a network
  • the ability to process Tuxedo requests close to where data resides
  • the ability to reduce bottleneck in the database server because Tuxedo requests are queued in the application server and transmitted to the database using Tuxedo services as they become available
  • the ability to achieve a minimum installation of clientside software, thereby resulting in thin clients
  • load balancing by installing many application servers that process data requests from clients
  • the ability to encrypt data transmitted from the database serve

Meet the Author

DeLia has over 15 years' experience working with client-server and relational database development.

Galina Landres has developed IS solutions for Waldenbooks, Entex, Coopers & Lybrand, Seagram, and Universal Studios. Vlad Landres has 25 years of experience with systems design, programming, and project management for the banking and insurance industries. They live in Stamford, Connecticut.

Sankaran has been developing PeopleSoft applications for nine years since its original release.

Rivera is a computer professional with over 19 years of experience in financial applications and PeopleSoft.

Customer Reviews

Average Review:

Write a Review

and post it to your social network


Most Helpful Customer Reviews

See all customer reviews >