PeopleSoft Jobs – PeopleSoft Interview Questions Set # 02
Continued from PeopleSoft Jobs – PeopleSoft Interview Questions Set # 01
Looking for a PeopleSoft job? We’re here to help. We’ve compiled a huge database of PeopleSoft interview questions, which will help you sail through any interview for PeopleSoft jobs. The questions in this and other posts on “PeopleSoft Interview Questions” are good to know irrespective of whether you’re looking for a PeopleSoft developer jobs, PeopleSoft administrator jobs or PeopleSoft functional jobs.
101)You want to change a Application Server name and the WebServer which file will you modify and where?
102)What are the steps to apply a PeopleSoft patch (involving Demo database, prerequisite, post requisite?)?
103)How will you enable SMTP on Application Server?
104)You Migrate some page changes from development to test environment but still the user complaints the changes are still not reflected in the test environment. What could be the problem and how will you resolve it?
105)Briefly describe PeopleSoft and Non PeopleSoft objects?
106)What is the difference between the 7.5X Vs 8X security?
107)Have you done Migration? How to build in PeopleSoft ? Why build from Oracle?
108)How to refresh PeopleSoft security from one Instance to another?
| Reporting Tools | Data Tools |
| Crystal ReportsSQRPSnVision (MS Excel 2000) | COBOLApplication EngineSQR |
OS390 is the only platform on which PeopleSoft Process Scheduler servers are initiated outside of BEA Tuxedo.
108) Why use internet access as the client for PeopleSoft application?
Ans:
There are a number of reasons.
1) Easy Access
2) Platform independence
3) Look and Feel
4) Low Bandwidth Access
5) Maintenance/Deployment
109)If the emphasis in PeopleSoft 8 is the internet, why do we still need windows client?
Ans: Installers, developers and administrators have to be able to peek under the covers and flip some switches. For many of these tasks, you will need to have a development environment setup. This is essentially identical to the system PeopleSoft used to deliver applications previous to PeopleSoft 8. While not required for functional users, this system is still essential for developers and system administrators working in the PeopleSoft environment.
110)What are the three logical sets of tables that make up a PeopleSoft database and what is the purpose of each?
Ans:
- System Catalog Tables— This table contain metadata about all object in the database.
- People Tools Tables—This table contain the metadata about PeopleSoft that is installed on the database. And also the structure that applications use to define specific objects. The structure of the tables is the same for all applications.
- Application Data Tables— This table contain data entered for use by your organization. Any table updated ad part of a component is an application data table.
111) For each PeopleSoft application that is installed, the installer creates two databases. What are they? Explain?
Ans: a) System(SYS) Database b) Demo Database
a) System(SYS) Database – The a) System(SYS) Database is an empty container ready for your organization’s data. It includes all of the People Tools tables, defining the objects that make up the application. The application data tables are empty. This database, or a modified variation of it, will eventually serve as your production database.
b) Demo Database – The Demo Database includes everything found in the System database plus sample application data. You will likely use this database and its sample data to test modifications you make to the application. The Demo database is also ideal for training purposes.
112) What is IVT?
Ans:
- The Installation Verification Test(IVT) is a documented series of tasks that the Installer performs against the environment to ensure that everything is running properly.
- There are separate IVTs for each application and environment; for example, the IVT for HRMS installed on an Oracle database will be very different from the IVT for Student Administration installed on an NT/SQL Server platform.
113) What is nVision Tab?
Ans: nVision is another reporting tool. Naturally, different applications will include different reports.
114) What is Application Designer?
Ans:
- The application development tool for PeopleSoft.
- During installation this program is used to build views and Temporary Tables.
- Application Designer can also be used to import projects atha are made up of database objects. <PS_HOME>bin\client\winx86\pside.exe
115) What areas of your organization need to be involved in the install process?
116) What are the various documents you need to become familiar with prior to the installation?
Ans:
- People Tools Documents
- Application Documents
117) What must be installed prior to running the PeopleSoft installer?
- Oracle
- Tuxedo
118) What is Tnsnames.ora?
Ans: The oracle client needs to determine the parameters necessary to connect to an Oracle database. The tnsnames.ora file, typically located in the %ORACLE_HOME%\network \admin directory, provides these parameters.
119)What is included on the People Tools CD-ROMS?
Ans: People Tools CD-ROMS includes
- SETUP.EXE file
- WEB LOGIC
- WEB SHPERE
- TUXEDO
120) What is the order for installing the application, tools, and third party products?
Ans:
- Third party products
- People Tools
- Application
121)What ID is used to establish the initial connection to the database?
Ans: User ID
122)What do you ‘run’ the Database Wizard?
123)What dose the Database Wizard do?
Ans:
- Takes user configuration input from the console
- Modifies script templates from the <PS_Home>/scripts directory and customizes them with that user information
- Executes the scripts to configure the database server
- Executes scripts to set up the database instance
- Executes scripts to set up the access ID, connect ID, and the user rights profiles they need to access the database instance
- Runs Data Mover to:
a) Create Tables and indexes
b) Create Views
c) Create Temporary Tables
d) Setup the initial People Soft Operator logons(from PSOPRDEFN)
124)What are the different types of databases, why do they differ, and what is the purpose of each?
125)How is PeopleSoft able to provide a database for customers on so many different database platforms?
126)What program do you execute if you want to run Data Mover from the command line?
127)What is the difference between logging into Data Mover in bootstrap mode and logging-in in Regular Mode?
128)Describe two SQR reports you can run to check the integrity of the database?
ANS:
People Soft provides two integrity-checking tool in the form of SQR reports.
a) DDDAUDIT.SQR b) SYSAUDIT.SQR
| DDDAUDIT.SQR | SYSAUDIT.SQR |
|
129) What is the difference between spawning a process and decaying a process?
ANS:
Spawning Process:
- If a process is overloaded, the BBL launches another instance of the process to handle the increased demand. This is called spawning process.
Decaying Process:
- As demand decreases, process are closed by the BBL. This is called decaying processes.
130)Is JOLT an acronym?
131)What is the difference between a Listener process and a Handler process?
Ans: Listener:
- The Listener is responsible for picking up the initial request for service from the Workstation (in this case, the ATM).
Handler:
- When the connection is established, and the user verified, responsibility for further processing for that client is assigned to a Handler, which performs work required for additional requests.
132)What is the Tux IPC Helper?
Ans:
- IPC – Inter Process Communications Helper helps facilitate messaging between the server processes.
- It is only installed for windows, since the inter process communications capabilities are already built into UNIX.
- The Tuxedo IPC Helper must be running on a windows system or the application server will fail. The service should be set to Automatic Startup.
133)What does port 3050 resolve to as hexadecimal?
134)Name the Tuxedo / Jolt Process and describe their functions?
Ans:
TUXEDO Process
a) BBL
b) WSL
c) WSH
BBL: Bulletin Board Liaison
Bulletin Board Liasion is the main Tuxedo engine unless the BBL is loaded nothing on the Application Server will work. It also direct all communication traffic sending data request to the appropriate to process.
WSL: WorkStation Listener
The WorkStation Listener process monitors the network for connection requests sent from windows clients. Once a connection is established, the WSL hands the client to a WSH process to handle the ongoing communication.
JOLT Process
- a. JSL
- b. JSH
JSL: JOLT Station Listener
The Jolt Station Listener process monitors the network for connection requests sent from Java clients (typically processes running on web servers). Once a connection is established. The JSL hands the client to a JSH Process to handle the ongoing communication.
JSH: JOLT Station Handler
The Jolt Station Handler maintains a persistent connection to the Java client until requests for data have been satisfied. The BBL tells the JSH which People Soft process is appropriate one to use.
135)What is an Application Server Domain?
Ans:
An Application Server Domain is nothing more than a set of server process.
136)What utility do you use to create and configure Application Server domains and where is it located?
Ans:
Utility: Psadmin
Location: <PS_Home>appserv
137)What file created when you choose to create a domain in psadmin? From what order files is it created? Where is it located?
Name: Psappsrv.cfg
Location: <HOST_PS_HOME>/APPSERV/<DOMAIN_NAME>
138)What other files are copied to this directory? What is the purpose of each?
jrepository This is the file used by Jolt to determine what services are available to Java clients, and to translate those services for the BBL.
psappsrv.cfg This is the PeopleSoft configuration file. It contains the settings that you are encouraged to change to tune your specific environment. The initial settings are determined by the template that you choose when creating the domain.
psappsrv.psx This file contains the configuration settings for the application messaging processes that are performed on the application server. You should not attempt to directly edit this file.
psappsrv.ubx This is the Tuxedo configuration file You should not attempt to directly edit this file.
psappsrv.val This is the validation file. Depending on the contents of this file, you may be restricted in what you are allowed to enter as a setting when in PSADMIN. Depending on your platform, this file is created from the Windows or UNIX base file.
Psappsrv.ubb
139)Does Tuxedo use psappsrv.cfg in text form to determine run-time parameters for the domain? If not, what does it use?
Ans: Not, PSTUXCFG
140)You’ve manually edited the psappsrv.cfg file. Will the domain recognize the changes?
Ans: Depends on the type of change that you have made, there are few changes which can be done dynamically. For others, you would need to reconfigure application server to activate those changes.
141)What are the client names when you execute a client status in psadmin?
Ans: a) JavaClient b) PLECBT12 c) tmadmin d) WSH e) JSH
142)When is the psappsrv.ubb file created and how is it used?
143)What is Spawn Threshold?
- This allows the dynamic decay of spawned server processes as the transaction volume decreases.
- The value can be loosely translated to mean if in 600 seconds there is less than or equal to one job in the queue the decay process begins.
144)You configure and boot the domain from the command line. Why did more processes than expected start when the domain was booted?
145)When viewing server status, you see programs, group names, and ID numbers. How can you use these when administrating the domain?
146)What is the importance of the queue status?
Ans:
The Queue Status report gives you vital information for tuning your environment.
147)How do you regenerate PSTUXCFG after manually changing psappsrv.cfg?
148)What Web Service software is currently supported in PeopleSoft 8.4?
Ans: Web Server Clustering.
149)What are the PeopleSoft components for the Web Server?
150)What port does the Web Server use?
151)What is Web Server clustering?
Ans:
- Web server clustering is when multiple copies of the HTTP software running on either the same host or other host systems are started, and share configuration and security.
- To share configuration information, multiple copies of the PIA client software need to be installed, one for each server that is part of the cluster.
- Once installed, the administration tool for either WebLogic or WebSphere is used to identify which servers are part of the cluster.
152)Where is the setup.exe to install the PeopleSoft components to the Web Server?
153)What is the main Web Server configuration file for PeopleSoft?
154)What do you execute to start the web server for PeopleSoft?
155)What is the URL for the PeopleSoft homepage?
156)Give an overview of what happens ‘under the covers’ when a user navigates to a PeopleSoft page?
157)How do you configure the Web Server for connection balancing and failover?
158)How many Internet Architecture installs will you need for three application server domains?
159)What are the three main PeopleSoft tables that manage the batch environment?
160)Describe the various server agents that support the process scheduler server?
161)What is the primary configuration file for a process scheduler server and where is it located?
File Name: psprcs.cfg
Location: <HOST_PS_HOME>/appsrev/prcs/
162)What is the ‘heartbeat’?
How often (in Seconds) the server agent check to see (PSSERVERSTAT table) if the server should change the status.
163)What is Batch Environment?
Batch environment is an all-inclusive term. The environment includes the databases, the batch servers, the process files (located on the batch servers or elsewhere), any clients that run batch routines, and all process scheduler servers.
164)What is The process scheduler server ?
The process scheduler server is a single instance of a set of server agents which connect to one Peoplesoft database on a host. A batch server can have one or more process scheduler domains – each dedicated to a single PeopleSoft database. Think of a process scheduler domain as the batch server equivalent to an application server domain.
165)What is The process scheduler server Domain?
- A Process Scheduler Server managed by Tuxedo may be referred to as a Process Scheduler Domain.
- In fact, the terms are nearly synonymous when to describe the Process Scheduler environment when running on a Host, except for the OS/390 environment.
166)Define The Server Agent(PSPRCSRV.EXE)?
The Server Agent is responsible for starting all server processes. Every fifteen seconds, it looks in the Process Request Table for server processes that are scheduled to run. If nothing is scheduled, the Server Agent “sleeps” for fifteen seconds, and then checks again.
167)What is PSPRCSRQST?
The Process Request Table (PSPRCSRQST) resides at the center of all process scheduler activity. When a process is initiated, a row is added to the table with details describing the process. The information here is also replicated in the PSPRCSQUE table which is read by the process scheduler agent. Finally, the Process Monitor and Report Manager use this table to report process activity.
168)What is PSPRCSQUE?
The Process Queue Table (PSPRCSQUE)is used by the Process Scheduler Agents to find new requests and to manage the status of those requests. When a process is initiated, a row is added to the table with details describing the process. The server agent reads the table at regular intervals, and starts processes that are run on the server side. The processes themselves update the status field.
169)What is the Server Table (PSPRCSQUE)?
The Server Status Table (PSSERVERSTAT) maintains a list of process scheduler servers in the environment and whether they are running, suspended or stopped.
170)What is the Server Definition Table(PSSERVERDEFN)?
The Server Definition Table (PSSERVERDEFN) maintains a list of parameters that are used by the Server Agent to setup up the Process Scheduler Domain when it starts. Each row contain information which an agent will use to determine what types of processes can be run, timings, where information will be distributed, and so forth. What definition an agent will use is determined by the configuration file for that agent on the batch host.
171)What are other Server Agents?
There are a number of other Process Scheduler Servers in the domain, which perform a variety of tasks. We will be looking at the configuration of these agents in more detail later in the chapter. The activation of any or all of these servers is optional in the Process Scheduler environment.
PSDSTSRV.EXE The Distribution Agent posts reports and system log files to the Report Repository. When the PSPRCSRV server detects that a process has finished, it sends the PostReport BEA Tuxedo service request to the Distribution Agent to initiate the transfer of the report.
PSAESRV.EXE Processes Application Engine requests. This server must be configured to run if any application engine requests are to be processed by this Process Scheduler Domain.
PSAEOSRV.EXE PSAEOSRV is a specialized Application Engine server to run Application Engine-based programs with a process type of Optimization Engine. Using a BEA Tuxedo request, the PSAEOSRV server communicates to the PSOPTENG server. This processes the majority of the program logic.
PSOPTENG.EXE Processes the core tasks in an Optimization Engine program.
PSDAEMON.EXE A new daemon process that can be set up to run continuously when the Process Scheduler is running, and is intended for recurrent Application Engine jobs.
172)What are The Process Scheduler Configuration Files?
When we create the Process Scheduler Domain, the files you see are created.
psprcs.cfg The configuration file is created by making a copy of the template file (nt.cfx or unix.cfx) in the PRCS directory. This file is used by the Process Scheduler Agent to set up the environment and determines which database and Process Scheduler configuration in the PSSERVERDEFN table will be used.
psprcsrv.ubx This file is a copy of the same file from the <PS_HOME>/appserv/prcs directory. As with the application server, this file has configuration information for Tuxedo that is used to manage the domain.
psprcsrv.ubb As with the Application server, this is the file generated to create the PSTUXCFG file.
psprcsrv.val This file contains validation parameters for PSADMIN when you configure the Process Scheduler Server.
psprcsrv.env This has the environment variables which are used, along with the psprcsrv.ubb file to create…
PSTUXCFG …this file which is used by the BBL to launch the Process Scheduler Domain.
173)PeopleSoft offers two tools for monitoring the status of batch processes. What are they & Explain it?
a) Report Manager b) Process Monitor
Report Manager is a comprehensive management tool for following the path of any reports that are published by the Process Scheduler server.
Process Monitor allows you to view the status of all processes – reports or otherwise – plus a page for looking at the status of all process scheduler servers.
Both of these tools can be accessed through the PeopleTools menu structure.
174)What is the purpose of DDBIN?
175)What Tuxedo process boot?
176)What could be the cause of Tuxedo’s not being able to boot the process scheduler domain?
177)What type of information do you enter to define for a server definition?
178)How is the process type definition used?
179)Does each process scheduler server domain have its own location in the Report Repository?
180)What are the three ways reports can be transferred to the Report Repository?
181)What are the tools used to monitor processes and how do they differ?
182)What does the Archive List is Report manager tell you?
Ans:
The Archived Reports tab simply lists details about files that are no longer in the repository, giving you an aid to find them on your backup media.
183)Why would use Report Folders?
Ans:
Because for organizing Reports in Report Manager.
184)Describe the purge process?
- Updates statistics to all of the process request tables before deleting content.
- Purges of all process requests with a last update date that is past the Days Before Purge value for the specified run statuses.
- Deletes all of the subdirectories in the Log_Output directory that are associated with the process requests that are purged from the process request table if the Purge Process Files option was specified.
- Purges the report repository tables with expired dates, based on the specified number of retention days.
- Deletes all directories from the report repository that are associated with processes purged from the report repository tables.
185)What is the SQL statement executed by the program?
186)How many steps does it execute?
187)What process executed the request?
188)What is PeopleSoft File System?
In PeopleSoft File System, the Important and Manageable Files are
- Application server Log and Trace Files
- Process Scheduler Server Log Files
- Web Server Log
- Cache
- PSreports
189)Describe the Application Server log files?
There are three log files that are generated for all application server domains – one by PeopleSoft and other two by Tuxedo.
APPSRV_mmdd..LOG Path:< HOST_PS_HOME>\APPSERV\< DOMAIN_NAME >\LOGS
This log contains application server-related messages. File is controlled by the LogFence configuration option. This determines the level of detail generated. LogFence is configured for each domain through PSADMIN (under Domain Settings).
Typical types of errors include:
- Database signon / Invalid AccessID
- PeopleTools release number mismatch
- Authentication failure
Ex. LogFence=3(Default)
Here are the valid configuration values for LogFence:
| Level | Function |
| -100 | Suppress logging |
| -1 | Protocol, memory errors |
| 0 | Status information |
| 1 | General errors |
| 2 | Warnings |
| 3 (default) | Tracing level 1 (Errors) |
| 4 | Tracing level 2 (Trace) |
| 5 | Tracing level 3 (Calls) |
Advantage
Disadvantage
A drawback to this is the higher values for logfence generate large quantities of information.
TUXLOG.mmddyy Path: < HOST_PS_HOME>\APPSERV\< DOMAIN_NAME >\LOGS
This log has Tuxedo messages for a domain. This log is generated by the BBL, and has information regarding the Tuxedo processes. Typical types of errors include:
- IPC and semaphore issues
- Tuxedo events (for example, server initiation)
- Port and Addressing Issues (e.g. bad IP address resolution, port collisions)
- Client timeouts
Information in the TUXLOG is not generally user specific except for client timeouts. It can help to identify problems that affect the entire domain, such as lack of resources or conflicts over resources with other applications.
ULOG.mmddyyPath: C:\ (Windows) –or- < HOST_PS_HOME>/ (UNIX)
The ULOG file contains general Tuxedo messages that apply to the entire application server host system. In Windows there will be only one ULOG for all domains. On UNIX, there will be one for each unique $PS_HOME. Generally, it is of limited utility for troubleshooting.
190)What determines the level of detail written to the APPSRV_MMDD.LOG?
191)Describe the Process Scheduler Server log files?
The Process Scheduler environment permits extensive tracing of it’s activities. Some of the areas which information is collected, and the files generated:
Located in < HOST_PS_HOME>\appserv\prcs\< DOMAIN_NAME >\LOGS
TUXEDO log A log is generated by the BBL processes, just as with the Application Server.
SQL trace SQL Trace files are generated for each server running in the Process Scheduler Domain if TraceSQL is set in the domain configuration.
Agent Logs Each Server Process in a Process Scheduler Domain has a log file similar to the APPSRV_mmdd.log created for an application server Domain.
192)Where are log and trace files located?
Location for Log Files:(AppServer) < HOST_PS_HOME>\APPSERV\< DOMAIN_NAME >\LOGS
(PrcsShdServer) < HOST_PS_HOME>\APPSERV\PRCS\< DOMAIN_NAME >\LOGS
Location for Trace Files: The trace file is stored locally on the client hard drive if it is connection directly to the database in 2-tier mode. 3-tier trace files are stored on the application server.
| Client | File Name | Location |
| 2-Tier | DBG1.TMP | C:\TEMP (on client system) |
| 3-Tier | <LOGIN>_<MACHINE>.TRACESQL | <PS_HOME>\APPSERV\<DOMAIN>\LOGS |
193)How are trace files generated?
Developers who log on to PeopleSoft with Windows client systems can generate SQL trace files that track the details of their sessions.
194)What is contained in the trace files and how is that determined?
There are a number of things to be aware of with client-side traces.
Location The trace file is stored locally on the client hard drive if it is connection directly to the database in 2-tier mode. 3-tier trace files are stored on the application server.
Longevity 2-tier trace files are refreshed with each login. 3-tier trace files are appended to.
Detail Filters The application server can be configured to limit the amount of detail that a 3-tier Windows client can trace.
Windows Only Only Windows clients can be configured to generate trace files. User who log on with browsers can generate trace files, but only if the application server is configured to trace all clients.
195)How is caching enabled?
- What level of caching is depends on what resources that available on host system. With EnableServerCaching, Specify what objects the system stores in cache on the application server. To enable application server disk caching set the value to 1 or 2.
- If value is 1, the system caches only the most used classes of objects, and if value is 2, the system caches all object types regardless of the frequency of use.
- To disable application server caching, the value must be set to 0. Turning off caching significantly degrades performance, as it requires the application server to retrieve an object from the database each time the system it is referenced.
196)What is shared cache and how you enable it?
- The system assumes that a preloaded cache exists in the share directory. The preloaded cache contains most instances of the managed object types that are cached to file.
- While booting application server, if shared cache is enabled but no cache files exist, the system reverts to unshared caching.
- To set shared caching for the domain, set the Set ServerCacheMode to 1. With this option enabled, the system stores the cache information in the following directory:
<PS_HOME>\appserv\<DOMAIN_NAME>\cache\share
197)What are the benefits of The Shared Cache Mode?
The shared cache mode offers the following benefits:
- Server processes share a common cache file, which reduce the disk space consumed by multiple cache files.
- Improved initial transaction load performance. Because all objects are already cached, the initial load performance is equivalent to subsequent loads. This is the major difference from previous behavior.
- Improved performance because the system does not write new items to the cache. As such, the cache file never grows. This prevents the host running out of disk space as each PSAPPSRV cache grows in size.
- Simplifies file management by having fewer files for the system to maintain.
198)Describe the web server logs?
The Web Server is the point of contact for most users connecting to a PeopleSoft Application. It makes sense to know where to find the log data that tracks user connections to the server, and the behavior of the web server environment.
Log file Locations:
Web Sphere: The log files for Web Sphere may be found at:
<HOST_WEB_HOME>\AppServer\logs
Web Logic: The log files for Web logic in:
< HOST_BEA _HOME>\wlserver6.1\config\peoplesoft\logs
199)What is Tracing and Masking?
To configure tracing on an application server, consider two distinct actions:
Trace To determine the level of tracing to perform for all clients who connect to the database. The higher the level of tracing, the larger the trace files will grow.
Mask To determine the maximum level of tracing allowed from any individual client. The mask limits what a client can write to the trace files on the application server – it does not affect the amount of tracing requested by the application server.
200)What is PSReports?
Once users run and generate reports, the process has reaches the status of Posted, a new hyperlink appears under the Details column – View. With this link, view the report and any associated files through the browser.
201)What is SMTP?
- The SMTP section allows you to specify the details for what mail gateway will be used, and how the domain will connect to.
- The SMTP Settings section is used to identify a mail server for use by the process scheduler mailing features.
