Join the supporters of the Stop Global Warming Virtual March
Main Menu
HomeBasicsFusionPS on LinuxSecurityDocumentsScriptsSearchRSS FeedsWeb LinksSiteMapDiscussion ForumPodCastsGuest BookPeopleSoft Jobs
Translation
Translation may not be accurate.
** Thanks to Google Anyway***


To Change between languages
go to English and change again.
Login Form





Lost Password?
No account yet? Register
FeedBurner
Get Postings by Email
without Account.


Who's Online
We have 131 guests online
Statistics
Postings: 70
PeopleSoft Blog Feeds: 15
PeopleSoft Job Feeds: 16
Oracle Feeds: 12

Registered Members: 429
Unique Visitors: 891292
Syndicate
Home arrow Basics arrow COMPONENTS and COMPONENT DEFINITION
COMPONENTS and COMPONENT DEFINITION PDF Print E-mail
Written by RD   
Wednesday, 26 March 2008

There was question in the forum section about the difference between COMPONENT PROCESSOR and PSAPPSRV. I wanted to add some more and some images to my response and post it as a seperate post. Most of them are basics. So it will be placed in Basics category.

What is Component or component Definition?

A component represents a complete business transaction. It comprises either a single page or a set of pages that are meant to be processed as one. After you create pages, you add them to one or more components to access them through menus or in business processes. It is the method used in PeopleSoft to access the business rule and or data without straining the client [which is browser]. This is the basic rule for the PeopleSoft PIA, designed around using PIA Servlets.

What is Component Buffer?

When you open any page in a component, the system retrieves all of the data records for the entire component and stores them in one set of record buffers, organized by scroll level.

and then by page level. This component buffer consists of rows of buffer fields that hold data for the various records that are associated with page controls, including the primary records, related display records, derived work records, and translate table records.

You can change the records in memory either through the user actions on the page or through PeopleCode that is associated with different page controls. At runtime, you open and save the entire component, not just individual pages. When you save any page in the component, you automatically save the whole component.

Sometimes, this might be annoying, especially when you enter data in fields and the component makes trips to the server while you navigate over fields. Sometimes it is advantages to avoid the user to enter all the fileds and reponse comes with some errors. We can also conrol this by checking the "Allow Deferred Processing" field in page, component. you may want the user to be able to input data with minimal interruption or trips to the server. Each trip to the server results in the page being refreshed on the browser, which may cause the display to flicker. It can also slow down your application. By specifying a component as deferred processing mode, you can also achieve better performance with this option. you can then specify whether a page within a component, or a field on a page, also performs processing in deferred mode.


What is Component Processor?

Component processor is the People Tools runtime engine that controls processing of an application from the time that a user requests a component from an application menu until the database is updated and processing of the component is complete. Here the application menu is mostly the menu in PIA though the browser.

This means it involves the Web Server, application Server and Database Query and back to the browser with full cycle of the user request of Component from PIA. When a full cycle is complete it involves browser, web server, app server and database server depending on the request.

For example, during the "Field Modification" process if the user does anything like "Changes the contents of a field, and then leaves the field", then depending on the system edits it is handled differently.

Image

How the Component Processor behaves?

Before a user selects a component, the system is in reset state, in which no component is displayed. The Component Processor's flow of execution begins when a user selects a component from a PeopleSoft menu. The Component Processor then:


  1. Performs search processing, in which it obtains and saves search key values for the component.
  2. Retrieves from the database server any data needed to build the component.
  3. Builds the component, creating buffers for the component data.
  4. Performs any additional processing for the component or the page.
  5. Displays the component and waits for user action.

 


Add as favourites (47) | Quote this article on your site | Views: 1716 | Print

Be first to comment this article
RSS comments

Write Comment
  • Thankyou for your comments.
  • Feel free to comment if there are any mistake in the postings also.
  • If you have a Blog or website, feel free to provide the link. We will take a peak.
  • Just ensure to *Refresh* your browser for a new security code to be displayed prior to clicking on the 'Send' button.
  • Keep in mind that the above process only applies if you simply entered the wrong security code.
Name:
Homepage
BBCode:Web AddressEmail AddressBold TextItalic TextUnderlined TextQuoteCodeOpen ListList ItemClose List
Comment:

Code:* Code
I wish to be contacted by email regarding additional comments

Copy Right: AKOComments v.1.4.6

Last Updated ( Friday, 28 March 2008 )
 
< Prev   Next >

xkcd and whatever..?

© 2010 PSADMIN.org
PSAdmin.org is for & by the PeopleSoft Administrators to share their Experience.