Peoplesoft Installation -old

Oracle9i/Peopletools8.46
New in other this is a Old Ref Doc

Introduction-
PeopleSoft Internet Architecture is completely focused on the internet to provide powerful new
functionality for internet-based access and integration. This next generation architecture leverages a number
of internet technologies and concepts to deliver simple, ubiquitous access to PeopleSoft applications and
enable the open flow of information between systems. While looking at PIA (Peoplesoft Internet
Architecture), it is comprised of a variety of components ranging from the browser to the database server,
including the following:
• Web browser
• Web server
• Application server
• Batch server
• Database server
The following example illustrates, at a high level, the physical relationship between the PeopleSoft
components.
Lets look at each of these components to understand what exactly are we talking about.

Component Overview-(Brief)

1.Web Browser

The web browser is the primary means by which end users and even administrators access PeopleSoft applications and
administrative tools.

2.Web Server

A Java-enabled web server is required to support browser transaction requests and the application
messaging technology. You install on the web server a collection of PeopleSoft Java servlets designed to
handle a wide range of PeopleSoft transactions.
Lets look at this a little more closely and recognize all the functionality of the web server. To be clear about it
the web server use Jolt to communicate with the application server and as we can see they both need
Tuxedo to communicate as deduced from the diagram below -
3.Application server

The application server is the core of the PeopleSoft Internet Architecture; it executes business logic and
issues SQL to the database server. The application server consists of numerous PeopleSoft services and
server processes that handle transaction requests.
The application server is responsible for maintaining the SQL connection to the database for the browser
requests and the Windows Development Environment.
Lets also look at the functional aspect of the Application Server (I will go much deeper in the later reports)
and see what is involved in the communication, as the Application server sits in the middle of the PIA –
4.Batch server

The batch server, or batch environment, is where you have PeopleSoft Process Scheduler installed and
configured, and it is the location where many of your batch programs run, such as Application Engine
programs. In most situations this is also where you have your COBOL and SQR executables installed.

5.Database server

The database server houses your database engine and your PeopleSoft database, which includes all of your
object definitions, system tables, application tables, and data. The database server must be running one of
the supported RDBMS/operating system combinations.
The relationship between a database server and an application server is a one-to-many model. That is, a
single database server can have multiple application servers connecting to it. The database server
simultaneously handles the application server connections, Development Environment connections, and
batch programs running against it.

Implementation-

My part in all this will be to show a working model of the Peoplesoft Internet Architecture. And demonstrate
the communication between the servers and the updates made to the Data Base. I will go much into details
later.
For my implementation I will be using-
• RDBMS ( My Data Base) – Oracle 9i.
• Install Jolt, Tuxedo.
• Web Server – Weblogic.
• People Tools.

Oracle 9i the need of a database-

The heart of any application used by Peoplesoft is, of course the database. When all is said and done, all of the
systems are just tools that allow users to access, enter and manipulate data in a peoplesoft database.
Oracle9i Database features full XML database functionality with Oracle XML DB, enhancements to the
groundbreaking Oracle Real Application Clusters, and self-tuning and self-management capabilities to help improve
DBA productivity and efficiency. In addition, the built-in OLAP functionality has been expanded and significant
enhancements and optimizations have been made for the Windows and Linux operating systems.

What is a Database?

All peoplesoft internet applications support industry leading database-management, including Oracle. Of
course, terminology varies from platform to platform, so even a basic term such as a database can carry different
definitions.
In the peoplesoft world, a database is a set of database objects with a single owner ID. A peoplesoft database
includes the objects and application data required for a single application.
This can cause confusion, especially for Oracle user. In oracle parlance, a peoplesoft is a schema or logical
database. In this case, we will use the term Database universally to describe Peoplesoft Databases. This is a onset of
tables that make up a peoplesoft application.

When referring to the tables in a PeopleSoft database, we always categorize them into three different areas:

Application Data
System
PeopleCatalog
Tools
Oracle 9i Installation-

Let’s install the Database and move on from there. For Oracle 9i installation on Windows-2000(and above),
Linux, Sun Solaris 8(and above) etc.. the oracle database comes equipped with a Oracle Universal Installer. We can use
this GUI tool provided by the Oracle Software to install, and configure the Database( but this setup is only for a
database on one machine that is a home computer, for corporate computers they require stable machines like Sun
Solaris/AIX/Unix-HP). But our task does not stop at this we also need to configure and build tables according to the
peoplesoft applications, about this we will be learning further(more included in Data Mover script).
The Oracle Universal Installer looks like the following Window-
The next window shows us where our Oracle Home folder will be created and we have the option to change it (as in UNIX it is
recommended to installation files and the Database on different Mount points or physical devices).

After selecting our home folder we will be prompted with a list of products we have available. The Available Products
window appears. Choose Oracle9i Database and click Next.
The Installation Types window appears. We will perform a “typical” install to get a basic set of Oracle software
installed and a starter database. You can rerun the installer again later and choose Custom to install additional products
individually. For now, choose Standard Edition or Enterprise Edition. The Enterprise Edition of Oracle9i has some very
sophisticated features missing from Standard Edition, and the opportunity to purchase additional options that might be
valuable to a large enterprise. However, the Enterprise Edition is much more expensive than Standard Edition. It is very
important that you choose the edition that matches your license, as this will be difficult to fix later. I use the Enterprise
Edition. Click Next.
The Database Configuration window appears. We will go the easy route here and choose a General Purpose database
and click Next. Alternatively, you could choose Customized and tailor the starter database to your own specifications.
Or you could choose Software Only and not create a starter database at all. (You can always run the Database
Configuration Assistant later to create, drop, or reconfigure databases.)
 If you have any existing Oracle databases on your server that are at a version prior to what you are now
installing, the installer will ask if you would like to run the Database Upgrade Assistant at the end of the installation to
migrate or upgrade these older databases to the current version. Make your decision and click Next. (We won’t be
covering the Database Upgrade Assistant here.)

The Database Identification window appears. You need to specify both a global database name and an SID
(instance name) for the starter database that will be created. The SID will default to the setting of the ORACLE_SID
environment variable, but you can override it here if you wish. You should give your database a global name that is the
same as the SID, with your domain name appended. Click Next.
The Database File Location window appears. The starter database will have all of its files in one directory under this
mount point. This may or may not be a good design for high performance and availability, but is fine for a starter
database. Click Next.
The Database Character Set window appears. We will leave this to default and move on. Click Next.
The Summary window appears. Review all of the selections you have made to confirm they are correct. Click Install.

If you are installing from CD ROM, you’ll be prompted to mount the second and third CD ROMs at various points
during the install.
 A Configuration Tools window appears a minute later and the Oracle Net Configuration Assistant launches to
configure networking so that your database will be able to accept requests from remote clients. No action is required on
your part, and this step completes quickly. The Database Configuration Assistant launches to create a starter database.
A progress window will show you how the database creation is going. Database creation took about five minutes on my
server, but will take substantially longer if you chose a customized database configuration. When database creation is
complete, a window will appear telling you that most user accounts on the database have been locked and that you must
change the passwords for the SYS and SYSTEM database users. You may enter the new passwords and click OK.
Alternatively, you may click the Password Management button and unlock accounts and set passwords for all database
users as you wish.

The Agent Configuration Assistant launches to configure Oracle’s “intelligent agent”, a monitoring and job-
running agent that you control through Oracle’s Enterprise Manager tool. No action is required on your part, and this
step completes quickly.

The Apache HTTP listener will now start. No action is required on your part, and this step completes quickly.
The End of Installation window appears. You may click Exit to exit the installer or Next Install to begin another
installation. You might click Next Install, for example, to perform a custom installation to install individual products
that did not get installed as part of the “typical” installation—such as Pro*C/C++.

It is important to note that the default Enterprise Edition install loads certain extra cost options, such as table
partitioning, onto your database server. If you are not licensed to use these options, then you should deinstall them. To
deinstall products, click the Deinstall Products button on the Welcome window.

Exit the installer when you have completed installations and deinstallations. This way now we have our peoplesoft
database, but we still need to update it with our peoplesoft tables(as it is all metadata driven). We will discuss it further
with data mover scripts which we run for our database.
Understanding the PeopleSoft Installer
This section discusses:
• Defining the PeopleSoft Installer
• Understanding PeopleSoft Servers

Defining the PeopleSoft Installer

The PeopleSoft Installer is a Java-based tool that delivers software to your servers.The PeopleSoft Installer enables you
to transfer files directly to various PeopleSoft servers—including application servers, batch servers, web servers, and
database servers—without first copying all files to a file server. You run the PeopleSoft installer from your
PeopleTools CD to install the necessary products on the target machines. Which files are installed depends on which
products you are licensed for, the operating system on the target machine, the database platform, and the selected server
option. The PeopleSoft Installer installs files directly to Windows, UNIX, and Linux machines. PeopleTools and
PeopleSoft Applications use the same PeopleSoft Install template. This chapter discusses the installation of
PeopleTools, followed by the installation of applications CDs and the Multilanguage CD.

Prerequisites
The PeopleSoft Installer requires Java Virtual Machine (JVM), which is bundled for all OS platforms. The PeopleSoft
Installer searches for the JVMs in the directories in which users would typically install JVM. If the search fails, the
bundled JVM will be used. For the PeopleSoft Installer to run successfully, you must have JRE/JDK version 1.4.x or
higher. Before running the PeopleSoft installer, you must verify that you have the correct patches for your JVM level.

Make sure you have at least 4.5 GB of free space to perform your installation. If you are installing
Enterprise Resource Planning Connectors, you will need an additional 400 MB of disk space. See Running the
PeopleSoft Installer. The installation process also requires at least 1.5 GB of free temporary disk space, which is
needed only for the duration of the process. The process uses the directory defined by the TEMP environment variable
on your installation computer. The user who installs PeopleTools must be root or the owner of <PS_HOME>. You
must have admin privileges to install the PeopleSoft web server.

Running the PeopleSoft Installer

This section discusses:
• Understanding the PeopleSoft Installer PeopleSoft Proprietary and Confidential 87 Using the PeopleSoft Installer
Chapter 3.
• Starting the PeopleSoft Installer.
• Running the PeopleSoft Installer in GUI Mode

Understanding the PeopleSoft Installer

The PeopleSoft Installer guides you through the process of installing files to your various servers. You must run the
PeopleSoft Installer on each machine that you use for one or more PeopleSoft server.

Running the PeopleSoft Installer in GUI Mode

To run the PeopleSoft Installer in GUI mode:
• Launch the installer. Click Next when you see the Welcome screen.
• Click the radio button to accept the license agreement and click Next.
 • Enter “I Agree” if you have read and understood the license agreement (this is very important as you should
know what kind of a deal you are getting into).
• Select your Unicode or Non-Unicode Database.
Unicode databases are beneficial if you intend to deploy your applications globally and would otherwise have to
implement multiple databases to handle different languages. However, Unicode databases require much more disk
space than non-Unicode databases.

• Enter your license code and click Next.

• If you would (or according to specifications require ERP then you could say ‘yes’ but we do not require it so we
will say ‘no’ for now. If you choose Yes, specify the installation directory. Note that this directory must not be
the location in which PeopleTools is installed, or a subdirectory of that directory.

• Specify your oracle bin path for connectivity of our PeoplTools with our Oracle Database. The default location
for the connectivity software for your platform (as set by the vendor) is listed in the following table. If the
database connectivity software was installed to a different directory, enter that path instead.
• If you need icons then you could install them. This is a option for your convenience.
• For your reference (Only for windows install) see where your PeopleTools program folder will be residing.

• At this point, enter the configuration information for Environment Management. Select the machine name of the web
server running the Environment Manager Hub. (This will very likely be the machine on which you're running PIA).
Select the hub port number (the default is 80). This needs to match the PIA port. If you change the port number for the
PIA configuration, you must also change the web server listener port number for all the agents in the
configuration.properties file.
 • The next screen lists the PeopleTools components (features) for which you are licensed.
Accept the defaults for the PeopleTools features and click Next.
• Select PeopleTools to install PeopleTools and the PeopleSoft Internet Architecture. This
component contains the core PeopleTools files and is required for the proper operation of
the PeopleSoft system and the PeopleSoft Internet Architecture.
• Select PeopleTools System Database to allow your developers to create custom PeopleTools applications outside of
the delivered PeopleSoft Application.
• The PeopleTools Language Pack and PeopleTools Language Development Kit contain the translated PeopleTools
DLLs and the resource files and headers needed to build them.
Select PeopleTools Language Pack if you plan on running the Windows components of
the installation in languages other than English. This component contains the compiled
PeopleSoft translations for the Windows client. If you are not using multiple languages
throughout your implementation, you do not need this component.
Select PeopleTools Language Development Kit if you plan on modifying or creating your own new translations for the
PeopleTools Windows client components. It contains the source and header files required to modify and compile new
versions of these translations. Again, you do not need this component if you are not using multiple languages.
• You will see an installation confirmation window. If the information is correct, choose Next. If you need to
modify any of the information, choose the Back button and make your changes.
 • If prompted, change your CD during the installation process.
• After the files have been installed, click Finish to complete the setup.

ERP

ERP General Description

Short for enterprise resource planning, a business management system that integrates all facets of the business,
including planning, manufacturing, sales, and marketing. As the ERP methodology has become more popular,
software applications have emerged to help business managers implement ERP in business activities such as
inventory control, order tracking, customer service, finance and human resources.
Take a customer order, for example. Typically, when a customer places an order, that order begins a mostly paper-
based journey from in-basket to in-basket around the company, often being keyed and rekeyed into different
departments' computer systems along the way. All that lounging around in in-baskets causes delays and lost orders, and
all the keying into different computer systems invites errors. Meanwhile, no one in the company truly knows what the
status of the order is at any given point because there is no way for the finance department, for example, to get into the
warehouse's computer system to see whether the item has been shipped. "You'll have to call the warehouse" is the
familiar refrain heard by frustrated customers.
ERP vanquishes the old standalone computer systems in finance, HR, manufacturing and the warehouse, and replaces them with
a single unified software program divided into software modules that roughly approximate the old standalone systems. Finance,
manufacturing and the warehouse all still get their own software, except now the software is linked together so that someone in
finance can look into the warehouse software to see if an order has been shipped. Most vendors' ERP software is flexible enough
that you can install some modules without buying the whole package. Many companies, for example, will just install an ERP
finance or HR module and leave the rest of the functions for another day.

General Duration Of ERP projects

Companies that install ERP do not have an easy time of it. Don't be fooled when ERP vendors tell you about a three or six month
average implementation time. Those short (that's right, six months is short) implementations all have a catch of one kind or
another: The company was small, or the implementation was limited to a small area of the company, or the company used only
the financial pieces of the ERP system (in which case the ERP system is nothing more than a very expensive accounting system).
To do ERP right, the ways you do business will need to change and the ways people do their jobs will need to change too. And
that kind of change doesn't come without pain. Unless, of course, your ways of doing business are working extremely well (orders
all shipped on time, productivity higher than all your competitors, customers completely satisfied), in which case there is no reason
to even consider ERP.

PeopleSoft Enterprise
Oracle’s PeopleSoft Enterprise applications are designed for the most complex business requirements. They provide
web services integration with multivendor and homegrown applications and can be easily configured and adapted to
meet the most unique customer requirements. In addition, PeopleSoft Enteprise supports a very broad choice of
technology infrastructure.

Oracle's PeopleSoft Enterprise Performance Management (EPM) enables organizations to achieve world-class performance by
aligning the right information and resources to strategic objectives.
PeopleSoft EPM offers performance management solutions for every budget and every phase of the management cycle, helping
managers formulate strategies for profitable growth, align strategies with operational plans, actively monitor day-to-day operations,
and collaborate across the enterprise.
With the latest release of PeopleSoft EPM, customers gain real-time interactive profitability and planning tools, next-generation
global compliance functionality, and rich packaged analytic content to speed application deployment. And EPM 8.9 is the first
release that will have a supported migration path to Project Fusion and Oracle's adoption of a service-oriented architecture.
 As we are more interested in financial criterions we will be installing financials. Our FIN version is FIN 8.9. In the same
process as before we launch the installation wizard, but make note that we will be installing Financials on top of our People Tools
folder so as to make our people tools Financial based. The first window of installation looks like:

In the next window it asks you to accept the license agreement, if you do not agree to the terms your installation will
not initiate and you will not be able to install, if you agree to the terms you may continue:
Enter the key for your product, which contains all the material you are entitled to according to your install:

Specify if your Data Base is Unicode or Non-Unicode:

Check everything you would like to install or un-check anything which you think can be done without:

Specify your People Tools directory:

The next window will list out products, only install products which you want, modules which you wont be using will
only waste your system space and lower performance:

This next window will confirm your selection and ask for your conformation to proceed and install, if you agree select
next:
The next window appears and at the end of install prompts that you are done will install:

Converting your Oracle Database to a Peoplesoft Database

Alright now we are done with our ERP installation. We have installed a Oracle database, now how do we insert data
into this database which does not know what are our peoplesoft tables. Peoplesoft database is Metadata driven,
meaning it contains data about data and groups it, in layman’s terms something like making tables in MS Excel. So first
we create table spaces in our database according to our ERP and then start pumping in data related to our peoplesoft in
those tables using Data Movers.
First we create the table spaces and create users in accordance with our install. Now first we need to know where these
scripts are. We look into the peoplesoft home folder in our case PT8.46, into scripts folder NT folder and modify six
scripts namely:

1. Utlspace.sql
2. Dbowner.sql
3. Epddl.sql ( this is specific to our ERP which is financials, in case of EPM it would be PFddl.sql)
4. Psroles.sql
5. Psadmin.sql
6. Connect.sql

The changes will be as follows:

UTLSPACE.SQL:
CREATE TEMPORARY TABLESPACE PSTEMP TEMPFILE
set termout on 'c:\oracle\oradata\orcl\pstemp01.dbf' SIZE 60M REUSE
set echo off AUTOEXTEND ON NEXT 100M MAXSIZE unlimited
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
set echo on
spool c:\log\utlspace.log – change it to any specific folder or log area you would like. They are best used for
troubleshooting errors. Do this to all the other logs too.

REM * Create a temporary tablespace for database users.

REM *
CREATE TEMPORARY TABLESPACE PSTEMP
TEMPFILE '<drive>:\oradata\<SID>\pstemp01.dbf' SIZE 300M
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K
;

REM * Create a tablespace for database users default tablespace.

REM *
CREATE TABLESPACE PSDEFAULT
DATAFILE '<drive>:\oradata\<SID>\psdefault.dbf' SIZE 100M
EXTENT MANAGEMENT LOCAL AUTOALLOCATE
; This script will create a user PS and grant
it the owner privlages. Let it connect to
spool off the database and create the tablespace
PSDBOWNER.
DBOWNER.SQL:

set echo on
spool C:\LOG\dbowner.log – I store my log files in a log folder.

GRANT CONNECT, RESOURCE, DBA TO PS IDENTIFIED BY PS;

CONNECT PS/PS@EPMDEV;
CREATE TABLE PSDBOWNER (DBNAME VARCHAR2(8) NOT NULL, OWNERID VARCHAR2(8) NOT
NULL ) TABLESPACE PSDEFAULT;
CREATE UNIQUE INDEX PS_PSDBOWNER ON PSDBOWNER (DBNAME) TABLESPACE PSDEFAULT;
CREATE PUBLIC SYNONYM PSDBOWNER FOR PSDBOWNER;
GRANT SELECT ON PSDBOWNER TO PUBLIC;
CONNECT SYSTEM/password@EPMDEV;
REVOKE CONNECT, RESOURCE, DBA FROM PS;

spool off
EPDDL.SQL

This script is substantially long so I will not put it in our document instead will show what changes we will need to
make.

Replace <drive>:\oradata\<SID> with your specific database extension which in our case is
C:\oracle\oradata\EPMDEV, do this for the whole document.

Also replace REMARK ALTER with ALTER. Meaning take the Remark out and let it alter the database. This is
the script which will create the peoplesoft table spaces for our oracle Database.

PSROLSE.SQL

set echo on
spool c:\log\psroles.log

DROP ROLE PSUSER;  This is just to make sure that the user does not exist.
DROP ROLE PSADMIN; This drops the roles PSADMIN

CREATE ROLE PSUSER; Creates the user

GRANT CREATE SESSION TO PSUSER;

CREATE ROLE PSADMIN;

GRANT
ANALYZE ANY,
ALTER SESSION, ALTER TABLESPACE, ALTER ROLLBACK SEGMENT,
CREATE CLUSTER, CREATE DATABASE LINK, CREATE PUBLIC DATABASE LINK,
CREATE PUBLIC SYNONYM, CREATE SEQUENCE, CREATE SNAPSHOT,
CREATE SESSION, CREATE SYNONYM, CREATE TABLE, CREATE VIEW,
CREATE PROCEDURE, CREATE TRIGGER, CREATE TABLESPACE, CREATE USER,
CREATE ROLLBACK SEGMENT,
DROP PUBLIC DATABASE LINK, DROP PUBLIC SYNONYM, DROP ROLLBACK SEGMENT,
DROP TABLESPACE, DROP USER, MANAGE TABLESPACE, RESOURCE,
EXP_FULL_DATABASE, IMP_FULL_DATABASE,
GRANT ANY ROLE, ALTER USER, BECOME USER
TO PSADMIN WITH ADMIN OPTION;

spool off

This script creates the user PSADMIN and grants it admin privileges.

PSADMIN.SQL

set echo on
spool c:\log\psadmin.log

REMARK -- Create the PeopleSoft Administrator schema.

create user SYSADM identified by SYSADM default tablespace PSDEFAULT

temporary tablespace pstemp;
grant PSADMIN TO SYSADM;
 grant unlimited tablespace to SYSADM;

connect system/password@EPMDEV

set echo off

REM @%ORACLE_HOME%\rdbms\admin\catdbsyn
REM @%ORACLE_HOME%\sqlplus\admin\pupbld

spool off

CONNECT.SQL

set echo on
spool c:\log\connect.log

REMARK -- drop user people cascade;

create user people identified by peop1e default tablespace PSDEFAULT

temporary tablespace PSTEMP;

GRANT CREATE SESSION to people;

REMARK -- drop user <CONNECTID> cascade;

REMARK -- create user <CONNECTID> identified by <PASSWORD> default tablespace <TSPACE>

REMARK -- temporary tablespace <TSPACE>;

REMARK -- GRANT CREATE SESSION to <CONNECTID>;

spool off

Next log into SQL Plus with the user SYSTEM/password into database EPMDEV.
Once you are logged in run the script using the commands:

@c:\ your folder \utlspace.sql

@c:\ your folder \dbowner.sql
@c:\ your folder \epddl.sql
@c:\ your folder \psroles.sql
@c:\ your folder \psadmin.sql
@c:\ your folder \connect.sql

Once you have run the scripts navigate to your Configuration Manager and make the following changes:
Now navigate to your Data Mover and login as SYSADM.

In your data mover navigate to FILEDATABASE SETUP.

Select Demo and add the database setup file and click next.
Make your changes in the following screen and click FINISH:
Your Data Mover Script looks like:

REM - epmdevora.dms
REM - Created by Data Mover 8.46 Sat Nov 12 04:59:21 2005
REM -
REM - Database Platform: Oracle
REM - Non-Unicode Database
REM - Selected Character Set: WE8ISO8859P1 - Western European ISO 8859-1
REM - Generate Latin-1 Code
REM -
/
REM - PeopleSoft FIN/SCM Database - US English
/
SET LOG C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\epengs.log;
SET INPUT C:\PT8.46\data\epengs.db;
SET COMMIT 30000;
SET NO VIEW;
SET NO SPACE;
SET NO TRACE;
SET UNICODE OFF;
SET IGNORE_DUPS;
IMPORT *;

REM - PeopleSoft FIN/SCM Database - US English

/
SET LOG C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\epengl.log;
SET INPUT C:\PT8.46\data\epengl.db;
SET COMMIT 30000;
SET NO VIEW;
SET NO SPACE;
SET NO TRACE;
SET UNICODE OFF;
SET IGNORE_DUPS;
IMPORT *;

REM - Final Database cleanup

REM -
REM - Based on your inputs to Database Setup, you will be using
REM - ConnectID's to connect to your PeopleSoft Application
REM -
/
INSERT INTO PS.PSDBOWNER VALUES('EPMDEV', 'SYSADM');
UPDATE PSSTATUS SET OWNERID = 'SYSADM';
UPDATE PSOPRDEFN SET SYMBOLICID = 'SYSADM1', OPERPSWD = OPRID, ENCRYPTED = 0;
UPDATE PSACCESSPRFL SET ACCESSID = 'SYSADM', SYMBOLICID = 'SYSADM1', ACCESSPSWD =
'SYSADM', VERSION = 0, ENCRYPTED = 0;
UPDATE PSOPTIONS SET LICENSE_CODE = '1377ffffffffffffff819ff812nk7mk', LICENSE_GROUP = '2';
UPDATE PS_INSTALLATION SET
AM='Y', BI='Y', TR='Y', CCM='Y', WR='Y', CA='Y', CCU='Y', DEAL='Y', DP='Y', EB='Y',
EG='Y', PV='Y', PPESA='Y', MPA='Y', ES='Y', EX='Y', PPFIN='Y', FP='Y', GL='Y', GM='Y',
INV='Y', IP='Y', MG='Y', TE='Y', OM='Y', FO_PBM='Y', AP='Y', CP='Y', PGM='Y', PC='Y',
TD='Y', PM='Y', PO='Y', QS='Y', AR='Y', RS='Y', RISK='Y', SP='Y', PIPS='Y', AUC='Y',
PPSCM='Y', SPL='Y', CAT='Y';
GRANT SELECT ON PSSTATUS TO PEOPLE;
GRANT SELECT ON PSOPRDEFN TO PEOPLE;
GRANT SELECT ON PSACCESSPRFL TO PEOPLE;
CREATE VIEW SYSKEYS
(IXCREATOR, IXNAME, COLNAME, COLNO, COLSEQ, ORDERING, FUNCTION)
AS SELECT
A.OWNERID, B.INDEX_NAME, B.COLUMN_NAME, B.COLUMN_POSITION, B.COLUMN_POSITION,
'a', ' '
FROM PSSTATUS A, USER_IND_COLUMNS B
/
CREATE VIEW SYSINDEXES
(TBCREATOR, NAME, TBNAME, CREATOR, UNIQUERULE, COLCOUNT, IXTYPE, CLUSTERRULE,
IXSIZE, PERCENTFREE)
AS SELECT
TABLE_OWNER, INDEX_NAME, TABLE_NAME, TABLE_OWNER, SUBSTR(UNIQUENESS,1,1), 1, 'b',
'n', 1, PCT_FREE
FROM USER_INDEXES
/

REM - ENCRYPT PASSWORD

/
SET LOG c:\docume~1\admini~1\locals~1\temp\encrypt.log;
ENCRYPT_PASSWORD *;

REM - CREATE TRIGGERS

/
SET LOG c:\docume~1\admini~1\locals~1\temp\triggers.log;
CREATE_TRIGGER *;

REM - CREATE VIEWS

/
SET LOG c:\docume~1\admini~1\locals~1\temp\views.log;
REPLACE_VIEW *;

REM - CREATE TEMP TABLES

/
SET LOG c:\docume~1\admini~1\locals~1\temp\temptbls.log;
CREATE_TEMP_TABLE *;
Now you are all set with your Peoplesoft Database. All you need to do next is to configure your Application Server,
Process Scheduler and Webserver and you are all set.