For two-tier connections Involves connecting directly to the database. A two-tier connection requires connectivity software to be installed and configured on the workstation. A two-tier connection is required for many upgrade and installation tasks.
PeopleSoft Data Mover runs in two-tier mode only.
Involves connecting to the database through the application server. A three-tier connection requires no connectivity software to be installed on the workstation. In a three-tier connection, the application server maintains the connection to the database for transmitting SQL statements between the application server and the database. Only lightweight Tuxedo messages are sent between the workstation and the application server.
A PeopleSoft user ID is the ID you enter at the PeopleSoft sign-in dialog box and Operate PeopleSoft Online Portal. You assign each PeopleSoft user a user ID and password. The combination of these two items grants users online access ( From PIA ) to the PeopleSoft system.
PeopleSoft no longer creates users at the database level.
The user ID is the key used to identify the user profile definition.
For Example: Valid PeopleSoft Operator ID, such as PS/PS for Human Capital Management or VP1/VP1 for Financials/Supply Chain Management.
Peoplesoft Application Permissions: Obtains all the rights/permission from Roles/Permission Lists.
Types of Account: PeopleSoft User Account.
You can see all the operator Details in “PSOPRDEFN” table. For Example
SELECT * FROM PSOPRDEFN;
The connect ID performs the initial connection to the database.
A connect ID is required for a direct connection (two-tier connection) to the database. Application servers and two-tier Microsoft Windows clients require a connect ID. You specify the connect ID for an application server in the Signon section of the PSADMIN utility. For Microsoft Windows clients, you specify the connect ID in the Startup tab of PeopleSoft Configuration Manager. You can create a connect ID by running the Connect.SQL and Grant.SQL scripts.
For Example: people/peop1e Usually used in PSADMINutility when we need to configure Application Server and Process Scheduler Server.
PeopleSoft Application Permission: Read-only rights to
PSDBOWNER (For Oracle/DB2)
Grant select on PSSTATUS to <CONNECT_ID>
Grant select on PSOPRDEFN to <CONNECT_ID>
Grant select on PSACCESSPRFL to <CONNECT_ID>
Types of Account: RDBMS Account So, Exists in Database Level.
Without a connect ID specified, the system assumes that workstation is accessing PeopleSoft through an application server. The option to override the database type is disabled.
When you create any user ID, you must assign it an access profile, which specifies an access ID and password.
The PeopleSoft access ID is the RDBMS ID with which PeopleSoft applications are ultimately connected to your database after the PeopleSoft system connects using the connect ID and validates the user ID and password. An access ID typically Full RDBMS privileges necessary to access and manipulate data for an entire PeopleSoft application.
Users do not know their corresponding access IDs. They just sign in with their user IDs and passwords. Behind the scenes, the system signs them into the database using the access ID.
If users try to access the database directly with a query tool using their user or connect IDs, they have limited access. User and connect IDs only have access to the few PeopleSoft tables used during sign-in, and that access is Select-level only. Furthermore, PeopleSoft encrypts the sensitive data that resides in those tables.
For Example: SYSADM/SYSADM Usually it is schema owner. They stored encrypted in PSACCESSPRFL Table
Peoplesoft Application Permissions: Full RDBMS privileges
System tables, also called system catalog tables, are analogous to a table of contents for a book or to file allocation tables on a hard drive. The structure and table names vary depending on which RDBMS you use. System catalog tables:
Keep track of all of the objects that reside in the database instance.
Are created by and owned by the RDBMS.
Are often described as system metadata.
PeopleTools Metadata Table
PeopleTools tables provide the infrastructure for PeopleSoft applications by storing and managing PeopleSoft application metadata. This metadata consists of information that defines the application, such as records, fields, pages, PeopleCode, and security. PeopleTools tables:
Define the structure of all object definitions that make up an application.
Use the same table structure for all applications.
Contain data that is added and updated only when the application is installed, or when using development tools such as PeopleSoft Application Designer or Data Mover.
PeopleSoft application data tables
Application data tables store data entered through a PeopleSoft application. The specific tables and their structures vary by application. Application data tables:
Contain day to day transactional data entered and updated by users.
They are empty prior to data entry (except the demo databases).
There are two modes in which Data Mover can be operated:
Most of the time you will log onto Data Mover in regular mode. To do this, you simply enter your PeopleSoft user ID and password ( PS/PS Or VP1/VP1) during sign-in. In regular mode, all data mover commands are valid.
There are times when you may need to launch Data Mover using the database access ID and password (SYADM/SYSADM). This is called launching in “bootstrap” mode. Typically, using bootstrap mode is necessary for database loading, because there are no PeopleSoft security tables established yet. You’ll also find it helpful for accomplishing other security-related tasks, such as running ENCRYPT_PASSWORD commands.
In bootstrap mode, the following commands are not valid: EXPORT,RENAME, and REPLACE_VIEW.