You are on page 1of 129

SYMPHONY 19th Dec 21th Dec 2011

Agenda
PeopleSoft Internet Architecture PeopleSoft Internet Architecture Development Framework PeopleSoft Security Application Designer Navigating PeopleSoft Applications Data Organisation & Validation Application Development Overview Objects and Migration Hands-On

Agenda

Pure Internet Architecture (PIA) Overview Physical vs Logical Tier Report Repository Q&A

Peoplesoft Internet Architecture


PeopleSoft Internet Architecture is a multi-tier

environment with four main components enabling users to access Business Applications over the Internet The four components are
Internet Browser Web Server Application Server Database Server

Architecture Overview
Browse r
HTTP Jolt/Tuxedo
SQL

Database Web Server App Server


S Q L

Process Scheduler

Peoplesoft Internet Architecture


Database Server

Houses a database engine and PeopleSoft application database Application Server Runs business logic and issues SQL to the database server Batch/Process Scheduler Server Runs batch processes/reports, also known as Process Scheduler Web Server Handles browser transaction requests Web Browser Interface to access PeopleSoft applications and administrative tools

PeopleSoft Internet Architecture


Database Oracle, DB2, Informix

Application Server
Webserver Browser

Tuxedo
Weblogic, Websphere Internet Explorer

PeopleSoft Internet Architecture


N-Tier Architecture

No Code on Clients (Browser only uses HTML,

JavaScript, Cookies) Benefits:


Easy Access (Standard URL access) Platform Independence (Windows, Mac, Unix) Low Bandwidth Access (HTTP) Low Cost of Maintenance and Deployment

PeopleSoft Internet Architecture


HTML SSL

User Web Client Four Tier

WebServer

Developer Workstation Three Tier

Application Server

SQL Requests PeopleSoft Object Data Application data

Database Server

Developer Workstation Two Tier

SQL

Process Scheduler Server

Physical Vs Logical Tier


Physical Tier means a component resides on its own

physical hardware e.g. if an environment is threephysical-tier, that means that the Web, App and Db Server are located in three separate servers Typically in development environment, users will use one or two physical tiers to minimise cost while going for full three or four physical tiers in production environment

Report Repository
Delivered Functionality in PeopleSoft 8

Allows distribution of reports on the web with built-in

security How It Works


Process Scheduler generates a report Once report generated, Distribution Agent transfer

report and log files to the Report Repository and publish them on the web as URLs

Report Repository Architecture

PeopleSoft Integration Technologies


PeopleSoft Application Messaging - facilitates

synchronous and asynchronous messaging among internal systems and with trading partners, while managing message structure, message format, and transport disparities.
PeopleSoft Component Interfaces - This object-

oriented, request/reply, component architecture enables third-party applications to synchronously invoke PeopleSoft business logic.
PeopleSoft File Layout Robust file processing

capabilities for file-based integration

15

Agenda
PeopleSoft Development Architecture

PeopleSoft Environments
Roles and Responsibilities PeopleSoft Development Tools

PeopleSoft Development Architecture


PeopleSoft uses PeopleTools Development

environment to configure the PeopleSoft Applications. PeopleTools only run on Microsoft Windows workstations. No browser access. Connection can be
Two-tier (directly to the database) Three-tier (through an application server)

PeopleSoft Internet Architecture


HTML SSL

User Web Client

Four Tier

WebServer

Developer Workstation

Three Tier

Application Server
SQL Requests PeopleSoft Object Data Application data

Database Server
SQL

Developer Workstation

Two Tier

Process Scheduler Server

Meta-Driven Architecture
All application objects are stored in Metadata

Repository
Fields, Records, Pages, Components, Application

Message, etc

Benefits Low Cost of Deployment (advanced caching mechanisms) Easier Upgrades Architecture Flexibility

Meta-Driven Illustrated

PeopleSoft Application Designer: Integrated Development Environment

Environments for Typical Project


DEMO DEMO(DMO) SYS Development(DEV) User Acceptance Test(UAT) Training(TRN) Production(PRD)

PeopleSoft Environments
DEMO consists of all the Peopletools Tables loaded with

supplied data for application objects from PeopleSoft and all applications-related tables with data supplied by PeopleSoft. This environment is used for demonstrations/reference of PS functionality and does not contain any customisations.
SYS consists of all the Peopletools tables loaded with

supplied data for application objects from Peoplesoft and all applications-related tables without any data. This env is used for creating initial environment for any development/production.

PeopleSoft Environments
DEV used for development activities

TRN used to conduct training


UAT used to conduct system acceptance testing and

all QA-related activities PRD this is the live environment

Roles and Responsibilities


Database Administrator (DBA)

Database Installation, Database Admin, Performance Tuning PeopleSoft Application Administrator PeopleSoft Application Installation, Configuration, Environment Management, Migration Security Administrator Create PeopleSoft User, Manage Roles, ID, Reset password Developer/Programmers Design, Develop, Test PeopleSoft Applications Users Business Users who uses PeopleSoft Application

PeopleSoft Development Tool


PeopleSoft Application Designer

PeopleSoft Configuration Manager


PeopleSoft Data Mover

Hands-on
Use Configuration Manager to configure workstation

Sign-in Application Designer


Sign in as bootstrap and normal mode using Data

Mover

28

Agenda
PeopleTools Security Overview

PeopleSoft Online Security


PeopleSoft Authorisation ID Sign-in Process

Q&A

PeopleTools Security Overview


Permission lists - grants access to PeopleSoft

elements (pages, menu, administrative tools, personalizations, etc) Roles - a collection of permission lists User profiles - a definition that represents one PeopleSoft user. Each user is a unique; the user profile specifies a number of user attributes, including one or more assigned roles

PeopleTools Security Overview

User Profile

User ID
Role

Password Other security access

Permission List
Menu Page Page Page

Sample Security Setup

PeopleSoft Online Security


Sign-in and time-out security - If the user attempts

to sign in during an invalid sign-in time, he or she is not allowed to sign on Page and dialog box security - restrict access to PeopleSoft menus Batch environment security restrict user to access process scheduler through process profile and process groups

PeopleSoft Online Security


Definition security - restrict access to database object

definitions, such as record definitions, field definitions, and page definitions from being modified by certain developers Application data security
Table level (for queries only) - specify which records user is allowed

to access when building and running queries by creating query access groups in PeopleSoft Tree Manager Row level - specify the data that a particular user is permitted to access using SQL views Field level - restrict access to particular fields or columns within application tables using PeopleCode

PeopleSoft Authorisation ID
User IDs ID to login to PeopleSoft Applications Connect ID - performs the initial connection to the

database Access IDs - RDBMS ID with which PeopleSoft applications connected to database after the PeopleSoft system connects using the connect ID and validates the user ID and password Symbolic IDs - acts as an intermediary entity between the user ID and the access ID Administrator access full access ID. PeopleSoft delivers at least one full-access user ID with each delivered database. For HCM, its PS

Sign-in Process
1. User ID, Password 2. User ID, Password 3. User ID, Password, Connect ID

Browser

Web Server
4. Query returns User ID and Password, Symbolic ID, Access ID and password

App Server

Database

5. Disconnect.

Demonstration
Viewing Permission List, Roles, User ID

PeopleSoft Internet Architecture

38

39

Agenda
Navigating PeopleSoft Applications Data Organisation & Validation Application Development Overview Design Application Define Fields Define Records Build SQL Tables/Views Create Page Definitions Define a Component Register a Component Test the Application Objects and Migration

Agenda
Design Consideration and Impact Analysis

Views
Search Records Data Audits

42

Logging on to PeopleSoft

Type your designated User ID and Password into the appropriate fields and click the button to log into the system.

Saving PeopleSoft as a Favourite


Save the URL address by clicking the button or drop down list of your web browser and the new address for access ease. To login next time, just drag and click your favorites list and select PeopleSoft login

Saving a Page to your PeopleSoft Favourites


To save a page to your favourites, click the right corner of your screen. hyper link at the top

Viewing your PeopleSoft Favourites


To view the page in My Favourites, expand the Favourites (this is typically the first menu item) menu in the Portal

Your User Profile and Password


Your user profile is embedded in your User ID; it identifies you in the system, so be careful not to share your logon information. During your first login, you should change your password. You have the ability to change what was assigned to you, thus making your login unique to YOU only. Go to the Change my password Page below the PeopleTools Menu

Personalization Options
PeopleSoft version 9.1 allows you personalize some options such as General Options, International & Regional Options, System and Application Messages and Navigation Personalizations. To view the options available, click on the links.

Retrieving Data via Search


A search page appears when a component or prompt is selected.. In the advanced search example below, SMITH was typed into the Last Name field and Employee was selected on the Personnel Status field. Click to activate it

Scroll

Viewing Records

Folder Tabs Content Reference

Tabs (Pages)

view all in the scroll area displays all occurrences in the same page

Scroll Area Header or Navigation Bar identifies additional records.

Edit box with a prompt

Use Insert and Delete buttons to add or remove an effective dated row of data.

Check boxes indicate

Yes or No

Inserting & Deleting Data


Enter Data in the fields. Scroll Area Header or Navigation Bar identifies additional records.

Use Insert and Delete buttons to add or remove an effective dated row of data.

Export To Excel
Export to Excel

PeopleSoft allows the user to export grid information to excel

Personalize Column & Sort Order


Customise column and sort order

PeopleSoft allows you personalize your column and sort order within pages. To view the personalization options, click on the customize hyperlink

PeopleSoft Reports
To utilise PeopleSoft reports go to the reports menu within the appropriate Module as highlighted below. Go To Recruiting Reports -> Job Posting Summary Need to add a run control ID the first time you log into the system Select the appropriate parameters click to activate it. To ensure the report has run successfully click on the Process Monitor.

PeopleSoft Reports
Change server to PSUNX and select Type as File and Format as Other and choose OK. The success or otherwise of your result scan be viewed under the Report Manager. Instance number corresponds to process instance Your report should show a status of posted in the Report List. Access your report directly by clicking Report Manager.

Hands-On
Exercise 1

57

Data Organisation
PeopleSoft Application is built using Relational

Database (RDBMS) Example PS Application is stored in three different types of tables

Database Terminology
PeopleSoft Terms
Records

RDBMS Terms
Tables/Views

Fields
Row

Columns
Record/Row

Table Structure and Key Fields


Relationship of records in a PeopleSoft application

normally fall under two categories:


Parent/Child Prompt Tables

Key Fields are defined in each of the record: Parent Table have key fields Child Table shares all the keys of its parent plus at least one additional key Key values from Prompt Table are stored in the prompting table

Normalisation
In the design phase, the development team needs to

understand the business requirement and design a table structures that support the application. Typically normalisation is applied to the tables to ensure data is not entered in two places Normalisation, however, can lead to complex designs. Therefore compromise is sometimes required to trade complexity for redundancy

Data Validations
PeopleSoft uses several methods to ensure data

accuracy:
Prompt Tables Translate Tables Yes/No Table Effective Dating

Prompt Tables
Prompt Tables Edit Allow only valid values from the

prompt table Prompt Tables Without Edit Values from prompt table only act as suggestion, user can enter any characters that fit the field definition

Translate Table
Translate table is a universal prompt table that is

shared by many fields in an application The table name is PSXLATITEM Use Translate Table if
Only a value, short and long descr required The list is not very long (e.g. Less than 30) The list does not require user maintenance (It is only

accessible through Application Designer)

Yes/No Table
The Yes/No table is a subset of Translate table values.

PeopleSoft delivered field = PSYESNO


The appearance on a page is typically a check box.

Effective Dating
Effective dating is a way in PeopleSoft to keep track of

historical and future records To make a record effective dated, there are three fields that can be added after the Record Keys
EFFDT EFF_STATUS EFF_SEQ

Effective Date Operations

68

Application Designer Interface


Project Workspace

Development Tab

Definition Workspace Output Window Upgrade Tab

Hands-on

Open definitions View definitions View and edit definition properties Create definitions Rename definitions Delete definitions Insert definitions into a project Remove definitions from a project Find definitions Save and Close definitions

Project Definition
Project is a container of PeopleSoft objects such as

fields, records, components, etc Used to Migrate to another environment and easy of maintenance SQR, COBOL and Crystal can not be stored in PeopleSoft projects

Application Development Steps


TEST PLAN
Test Application Design Application

Register Components Define Components

Define Fields Define Records Build Tables Define Pages

USER INTERFACE

DATA DESIGN

Application Development Steps


Designing the Application

Defining Fields
Defining Records Building Tables

Defining Pages
Defining Components Registering Components

Testing the Application

Step 1: Planning the Application


Application Design outputs Functional Specification Describes functional requirements such as data, business rules, user groups Technical Specification Describes the complete definitions with properties including Data Model

Step 2: Defining Field


Types of field Character Alphanumeric of fixed length (maximum 254 characters) Long Characters Alphanumeric of variable length (maximum up to 2GB) Number Positive numeric Signed Number Positive or Negative numeric Date, Time, DateTime Image Store image such as JPEG

Field Properties
Field Name, Type, Length, Label Options, Translate Values Record Field Key Structure, Search, Default Value, Required Setting, Edit Type (Prompt, Translate, Y/N) Page Field Source, Alignment and Display Options, Label

Translate Values
Translate Values can be accesed through field

properties

Translate Values have these properties Value Eff Date Eff Status Long Name Short Name

Fields Design Consideration


Making use of existing PS fields EFFDT EFF_STATUS DESCR DATE NOTE: Changes to a field definition impact all records

that refer to the field

Step 3: Defining Record


Types of record

How to View Record Definitions


There are four ways to view record

Field Display

Use Display

Edits Display

PeopleCode Display

Field Display

Use Display

Edits Display

PeopleCode Display

Record Field Use Properties


Key Structures

Record Field Edits Properties

Edits Option

Step 4: Build Tables


PC
Definitions

Build Tables

Development Workstation

Build Tables
There are two scopes of Build Project Current Definition Build Page

Build Tables Settings


Build Settings

Build Tables Settings

Step 5: Designing a Page


Types of page Standard Page Sub Page Secondary Page

Page Levels
Level 0 only

Page Levels
Level 0 Key With Level 1 Effective Date

Page Levels
Level 0 Key With Level 1 Child Data

Related Field
To Display an information that is not necessarily part

of the underlying data tables, we use the combination of:


Display Control Field Display Related Field

Page Properties

Page Level
Level 0

Level 1

Page Field Properties

Page Field Properties and Ordering

Page Controls
Group boxes Horizontal rules Radio buttons Subpages

Images
Static text Check boxes

Grids
HTML areas Push buttons or links

Drop-down list boxes


Edit and long edit boxes

Scroll areas and bars


Secondary pages

Hands-On
Exercise 2

Step 6: Defining Component


Component contains one or multiple pages

Component Definitions are combined with menu

definitions to create a reference point. This combination is then used as a hook to assign navigation and security access
Navigation Security

Component / Menu Definition

Search Records
Primary Record The record used in the page

definition Search Record The record that holds the search keys and alternate search keys for the page

Component Properties
Search Record

Component Properties
Search Mode

Buttons on Page

Step 7: Registering Component


Registering Component involve three tasks Attach a component to a menu definition Attach the component and menu combination to a security permission list Assign the component and menu combination to a content reference in a folder for user navigation

Menu Definition
Menu is an object from PS 6, 7

Menu definitions are containers for components


Navigation is designed in Portal Registry, therefore

menu only serves as a bridge between component definitions, navigation, and security Menu contains
Bar Items (Setup, Use, Process) Menu items

PS Security
PS Security is designed around three definitions Permission Lists Roles User Profiles (User IDs)

Portal Registry
Portal Registry Structure contains Folders Content Reference

Step 8: Test
Navigate through Web Browser

Ensure valid data in prompt tables


Add high-level keys (if Add action supported) Check default values

Insert, Update, Delete Records


Test effective-date logic Test tab orders

Review Application Development Steps


Planning the Application

Defining Fields
Defining Records Building Tables

Defining Pages
Defining Components Registering Components

Testing the Application

Hands-On
Exercise 3

Exercise 4

Effective Dating
How to create an effective-dated record Add EFFDT Areas that are impacted Page Levels Components Options Permission List Setup

Record and Page Definition

EFFDT field as Key

Level 0

Level 1

Component Options
Effective Dating Actions

Permission List Setup


Effective Dating Actions

Hands-On
Exercise 5

Exercise 6
Exercise 7

118

Agenda
PeopleSoft Objects Overview

PeopleSoft Data and Interface Tool


Data Integrity and Auditing

PeopleSoft Objects Overview


Field

Record
Page Component

Menu
Portal Security

Project Definition

PeopleSoft Data Mover


PeopleSoft Data Mover enables you to perform the

following tasks:
Transfer application data between PeopleSoft databases. Move PeopleSoft databases across operating systems and database

platforms. Execute Structured Query Language (SQL) statements against any PeopleSoft database, regardless of the underlying operating system or database platform. Export data in a platform independent manner. Control database security and access. Create, edit, and run scripts which combine SQL commands and PeopleSoft Data Mover commands for exporting and importing data

Data Mover: Mode


Regular mode

This is the mode commonly used. To sign in to regular mode, just enter PeopleSoft user ID and password. In regular mode, all commands are valid.
Bootstrap mode

In bootstrap mode, user sign in using database access ID and password. Typically, this mode is used for database loading, because no PeopleSoft security tables are established yet. This mode is also required to run some security commands, such as ENCRYPT_PASSWORD.

Common Data Mover Commands


Command ENCRYPT_PASSWORD EXPORT IMPORT Description Encrypt one or all user passwords (operator and access) defined in PSOPRDEFN for users. Select record information and data from records and store the result set in a file. Insert data into tables using the information in an export file. If a tablespace or table does not exist, this command creates tablespace, table, and indexes for the record, using the information in the export file, and inserts the data. Rename a PeopleSoft record, a field in one record, or a field in all records. This is a variation of the IMPORT command. If a table already exists, use this command to drop the table and its indexes from the database and create the table and indexes using the information in the export file. Then, the command inserts data into the table using the information in the export file.

RENAME REPLACE_ALL

Common Data Mover Commands


Command REPLACE_DATA Description This is a variation of the IMPORT command. Delete data in existing tables and insert the corresponding data from the export file. Recreate specified views found in the database. Run a specified .DMS file from within a PeopleSoft Data Mover script. The file cannot contain nested RUN commands. When a command is followed by valid SET parameters, it forms a statement that establishes the conditions under which PeopleSoft Data Mover runs the PeopleSoft Data Mover and SQL commands that follow. Indicate comment statements. (Optional) If this command is set, then all errors during the swap base language are ignored. Otherwise, the system stops on errors.

REPLACE_VIEW RUN

SET

REM, REMARK, and -SET IGNORE_ERRORS

Data Integrity Tool


SQL Alter

Bring SQL tables into accordance with PeopleTools record definitions. SQL Alter can be run in audit-only mode that alerts discrepancies between record definitions and SQL tables, but that doesn't actually perform an alter.
DDDAUDIT

Detects inconsistencies between PeopleTools record and index definitions and the database objects. This audit consists of nine queries: four on tables, two on views, and three on indexes.
SYSAUDIT

Identifies orphaned PeopleSoft objects and other inconsistencies within the system. An example of an orphaned object is a module of PeopleCode that exists, but which does not relate to any other objects in the system.

Trigger-Based Database Level Auditing


Trigger-based auditing functionality allows

organisations to audit changes to certain data, as part of company/regulatory requirements. The levels of audit such as who, what, when can be defined using database triggers When a certain change meet the audit requirements, it will triggers the audit function.

Migration Best Practices


Before performing migration need to run compare

reports Create scripts and log files Development Conventions


XYZ_*_VW (For Views) XYZ_*_SRC (For Search)

Hands-On
Exercise 7.5

Questions & Answers

129

You might also like