Chapter 1 System Overview

tukwilagleefulInternet και Εφαρμογές Web

31 Οκτ 2013 (πριν από 4 χρόνια και 2 μήνες)

111 εμφανίσεις


10/31/2013

Proprietary and Confidential to CedarCrestone, Inc.

1
-
1


and
Arizona State University


Chapter 1

System Overview

This is a system overview of the People
S
oft
technical environment
and development
requirements
.

Chapter Objectives

This chapter
provides:



Basic understanding of PeopleSoft Internet Architecture



Basic underst
anding of a Relational Database



Requirements for Development


Chapter Contents

This chapter contains the following
items
:

Overview of PeopleSoft
Internet Architecture

................................
.......

2

What Is A Relational Database?

................................
.............................

4

Development Requirements

................................
................................
....

5



Chapter 1: Systems Overvi ew

Designing An Application

1
-
2

Proprietary and Confidential to CedarCrestone, Inc.

1/12/2006


an
d
Arizona State University

Overview

of
PeopleSoft
Internet Architecture

PeopleSoft
application runs on People
S
oft Internet Architecture
(PIA)
which consists of the following elements:



Web Browser
s



Web Server
s



Application Server
s



Database Server
s



Batch Server
s


High Level People
S
oft Intern
et Architecture Relationships


Web Browser

The web browser interprets the HTML that is being sent from the
Web Server and also passes it transaction requests from the
application.
It is r
esponsible for displaying the HTML that is built
by Application Ser
ver.

Web Server

The web server interprets the browser requests and works with the
application server messaging to pass data back and forth from the
browser to the
PeopleSoft
application.

Designing An Application

Chapter 1: Systems Overview

01/12/2006

Proprietary and Confidential to CedarCrestone, Inc.

1
-
3


and
Arizona State University


Application Server

The application server
runs all the business logic

on the requested
data and is also responsible for keeping the connection to the
database server. It sends requests for retrieving as well as saving
data to the database server.


Batch Server

The batch server is responsible for
running the
PeopleSoft Pro
cess
Scheduler
, which is used to run reports and processes against the
data.

Database Server

The database server holds the database engine that contains all
the People
S
oft application object definitions, system tables,
application tables, and data.


Chapter 1: Systems Overvi ew

Designing An Application

1
-
4

Proprietary and Confidential to CedarCrestone, Inc.

1/12/2006


an
d
Arizona State University

What I
s A Relational Database?

PeopleSoft’s database is a relational database. This means that
data is broken down into a series of tables. When retrieving data,
the system only accesses the tables that contain the requested
data.

You can think of a relational d
atabase as a filing cabinet. The filing
cabinet represents the database. The drawers of the cabinet
represent data files or tables, while individual forms represent data
records or rows.

What is a

Table?

In a relational database, tables are used to store
information. This
information is stored in a format that is similar to a spreadsheet.
The table consists of a series of columns and rows. The columns
represent the fields on the various pages in the system. The rows
represent the actual data on those pages
.

This is a partial example of the Personal Data table:

Personal

Data
Table

EMPLID

COUNTRY_NM_FORMAT

NAME

NAME
INITIALS

NAME
PREFIX

SA0001

USA

Prince,Nathan

NP

Mr

SA0002

USA

Norman,Bruce

BN


SA0003

USA

Kuhn,Tricia G

TK

Miss

SA0004

USA

Rocha,Juan

JR

Mr


Student Career Table

EMPLID

ACAD_CAREER

CAR_REQ_TERM

SA0001

UGRD

2077

SA000
1

GRAD

2097

SA0003

UGRD

2077

SA0004

UGRD

2077


Each table in the database contains unique data, data that is not
available in any other table. Therefore, it only needs

to be
maintained in one place but can be accessed from various pages
in the system.


Each table
consists of several
records. Therefore, the
terms “
table
” and

records
” are often used
interchangeably.

Field Names

Records

Designing An Application

Chapter 1: Systems Overview

01/12/2006

Proprietary and Confidential to CedarCrestone, Inc.

1
-
5


and
Arizona State University


Development Requirements

How
is it
determine
d

that a modification is needed to the application?

There are differing reasons for making modifications to the
PeopleSoft sy
s
t
em.
Some possible scenarios:



Business Processes



Missing Data



Presentation of data



Extend Functionality


Business Processes

A modification to a business process is needed or a new one
created. Examples might be a new interface to export/import data
to a

new vendor or a process that does a new calculation on data
that already exists. A business process can cause change to an
SQR Report, Application Engine or even workflow logic.

Missing Data

Missing data could be something that you want to track that is
n’t
being kept anywhere in the database. This can include anything
from a simple edit value on a field to an entire record needing
many fields.

This will generally call for changes to fields and
records and possibly pages to capture and display the new d
ata.

Presentation of Data

This is normally when the data you want exists in the data
base but
is not being presented, either online or in a report,
in the manner

which is desired. There might simply
be a
need
for
a new query
written, changes to pages, or
entire new report.

Extend Functionality

Delivered functionality of a component may not be adequate to
satisfy all your business needs. In which case, t
here may be a
need to extend the functionality of an existing module within the
application.




Chapter 1: Systems Overvi ew

Designing An Application

1
-
6

Proprietary and Confidential to CedarCrestone, Inc.

1/12/2006


an
d
Arizona State University

Modific
ation Considerations


Questions you should a
sk

when considering making modifications to the
application.



What type of development is required?



Does it already exist in the system?



Does it require changes to delivered objects or will it be a bolt
-
on
modifi
cation?



What is the effort involved to make the modification?



What benefits will it render?



Can a large solution be submitted as a smaller unit of work?



What is the impact to the maintenance of the application (i.e.
upgrades)?