Two tier Architecture
=====================
A PeopleSoft client connected to the PeopleSoft Database server is simple two tier architecture. The Client is a fat client. as-in it has all the PeopleTools executables installed on it. There could be another scenario that there is an additional component called the file server. This file server can hold all the PS executables and the Client just maps to the PeopleSoft folder carrying the executables. In either case this is a PeopleSoft 2 tier Architecture. In this architecture Data storage and processing take place on the server and the business rules and presentation of the data are managed by the individual client workstations
Three tier Architecture
=======================
The 3 tier PeopleSoft architecture consists of the Client, the Application server and the Database server. The application server handles most of the business rules and data processing, database server manages the data and the client handles the presentation of data. This was actually the PeopleSoft architecture in ver 7 and 7.5. There is usually a File server also which holds all the PeopleSoft executables and the Clients map to the File server to run the executables. In case of implementation over a Wide area network, the Application server is kept near the Database server and the clients connect to the application server over the WAN. It gives better performance than a 2 tier architecture since the heavy part of the transaction happens between the AS and the DS on the local LAN and only the resulting output is sent back to the client.
nTier Architecure or PeopleSoft Internet Architecture
=====================================================
nTier architecture or PIA is PeopleSoft’s Internet architecture designed for version 8. It consists of four tiers with six different components-Internet access device, web server, application server, and database server. In addition it also has a File Server and a Batch Server that runs scheduled processes against the database.
Protocols between different tiers:
Web Client and WebServer - HTTP/HTTPS over port 80/433
WebServer and Apps Server - Jolt over JSL port 9000
Apps/Batch Server and DB Server - SQL over TCP/IP, Oracle Listener Process port 1521
3-T Client and Apps Server - Tuxedo messages over TCP/IP, WSL Workstation listener proces7000
PIA Client connects with Web Server through HTTP or HTTPs ports. This port is define in the Web Server in a file called config.xml. The connectivity between Web Server and Application Server is done through JOLT port. This JSL port is defined in two places one is at Web Sever side in a file called configuration.properties & 2nd at application server side in a file called PSAPPSRV.cfg. The connectivity between Application Server & Database Server is done through sql.net and the file used for this connectivity is tnsnames.ora at client side i.e. Application Server and listner.ora at server side i.e. Database Server
PIA is the combination of 3 servers
====================================
1) Web Server
The role of web server is to support browser requests and present the Peoplesoft content over the web. It has 3 components. Web services such as Websphere/Web logic server, Servlet engine such as JServ, and PeopleSoft Java servlets such as page servlet, Report repository servlet or portal servlet etc. The main servlet is the page servlet. This job of the page servlet is to communicate the browser requests to the Apps server via Jolt. Also when the App server returns pure HTML the page servlet formats it and presents it in the browser. (Portal handles all of the requests and formatting for portal users
Gateway Servlet transmits the received messages between message nodes
Report rep helps the user to retrieve the output of his process and serves on the browser)
2) Application Server
The application server is the core of the PeopleSoft Internet Architecture. It executes business logic and issues SQL to the database server. It is made up of 3 components. Jolt, Tuxedo and PeopleSoft server processes. TUXEDO is the orchestrator that manages the database side transactions through the server processes and webserver side requests via Jolt.
3) Database Server
Complete Working of PeopleSoft Internet Architecture:
=====================================
- User enters a URL for PeopleSoft (or performs some action such as invoking a panel through his PS interface by clicking on a menu link).
- This Link is interpreted as a URL by the web Browser URL points to the PS Webserver and includes the name of the Page Servlet on the Web Server. Browser passes this request to the servlet. (Other servlets are report servelet, portal servlet, gateway servlet)
- Servlet interprets the request and comes up with the list of Objects required to build the page.
- Requests for all objects are sent to apps server in the form of a Jolt message. Jolt is acting as the communications layer between the Page Servlet and Tuxedo.
- Tuxedo then receives the Jolt message and converts it in to a service request and routes to the appropriate PeopleSoft server process (e.g. PSAPPSERV for page build).
- PeopleSoft process converts service requests in to SQL statements which will fetch the objects from the database
- SQL Statements are fired against the Database.
- Data requested is supplied by the database.
- PeopleSoft process (PSAPPSERV) constructs HTML page out of object data.
- Tuxedo takes this HTML page and routes it back to the requesting Java Servlet.
- When all objects are in place, HTML page is forwarded to the Web services.
- Browser views page.
=====================
A PeopleSoft client connected to the PeopleSoft Database server is simple two tier architecture. The Client is a fat client. as-in it has all the PeopleTools executables installed on it. There could be another scenario that there is an additional component called the file server. This file server can hold all the PS executables and the Client just maps to the PeopleSoft folder carrying the executables. In either case this is a PeopleSoft 2 tier Architecture. In this architecture Data storage and processing take place on the server and the business rules and presentation of the data are managed by the individual client workstations
Three tier Architecture
=======================
The 3 tier PeopleSoft architecture consists of the Client, the Application server and the Database server. The application server handles most of the business rules and data processing, database server manages the data and the client handles the presentation of data. This was actually the PeopleSoft architecture in ver 7 and 7.5. There is usually a File server also which holds all the PeopleSoft executables and the Clients map to the File server to run the executables. In case of implementation over a Wide area network, the Application server is kept near the Database server and the clients connect to the application server over the WAN. It gives better performance than a 2 tier architecture since the heavy part of the transaction happens between the AS and the DS on the local LAN and only the resulting output is sent back to the client.
nTier Architecure or PeopleSoft Internet Architecture
=====================================================
nTier architecture or PIA is PeopleSoft’s Internet architecture designed for version 8. It consists of four tiers with six different components-Internet access device, web server, application server, and database server. In addition it also has a File Server and a Batch Server that runs scheduled processes against the database.
Protocols between different tiers:
Web Client and WebServer - HTTP/HTTPS over port 80/433
WebServer and Apps Server - Jolt over JSL port 9000
Apps/Batch Server and DB Server - SQL over TCP/IP, Oracle Listener Process port 1521
3-T Client and Apps Server - Tuxedo messages over TCP/IP, WSL Workstation listener proces7000
PIA Client connects with Web Server through HTTP or HTTPs ports. This port is define in the Web Server in a file called config.xml. The connectivity between Web Server and Application Server is done through JOLT port. This JSL port is defined in two places one is at Web Sever side in a file called configuration.properties & 2nd at application server side in a file called PSAPPSRV.cfg. The connectivity between Application Server & Database Server is done through sql.net and the file used for this connectivity is tnsnames.ora at client side i.e. Application Server and listner.ora at server side i.e. Database Server
PIA is the combination of 3 servers
====================================
1) Web Server
The role of web server is to support browser requests and present the Peoplesoft content over the web. It has 3 components. Web services such as Websphere/Web logic server, Servlet engine such as JServ, and PeopleSoft Java servlets such as page servlet, Report repository servlet or portal servlet etc. The main servlet is the page servlet. This job of the page servlet is to communicate the browser requests to the Apps server via Jolt. Also when the App server returns pure HTML the page servlet formats it and presents it in the browser. (Portal handles all of the requests and formatting for portal users
Gateway Servlet transmits the received messages between message nodes
Report rep helps the user to retrieve the output of his process and serves on the browser)
2) Application Server
The application server is the core of the PeopleSoft Internet Architecture. It executes business logic and issues SQL to the database server. It is made up of 3 components. Jolt, Tuxedo and PeopleSoft server processes. TUXEDO is the orchestrator that manages the database side transactions through the server processes and webserver side requests via Jolt.
3) Database Server
Complete Working of PeopleSoft Internet Architecture:
=====================================
- User enters a URL for PeopleSoft (or performs some action such as invoking a panel through his PS interface by clicking on a menu link).
- This Link is interpreted as a URL by the web Browser URL points to the PS Webserver and includes the name of the Page Servlet on the Web Server. Browser passes this request to the servlet. (Other servlets are report servelet, portal servlet, gateway servlet)
- Servlet interprets the request and comes up with the list of Objects required to build the page.
- Requests for all objects are sent to apps server in the form of a Jolt message. Jolt is acting as the communications layer between the Page Servlet and Tuxedo.
- Tuxedo then receives the Jolt message and converts it in to a service request and routes to the appropriate PeopleSoft server process (e.g. PSAPPSERV for page build).
- PeopleSoft process converts service requests in to SQL statements which will fetch the objects from the database
- SQL Statements are fired against the Database.
- Data requested is supplied by the database.
- PeopleSoft process (PSAPPSERV) constructs HTML page out of object data.
- Tuxedo takes this HTML page and routes it back to the requesting Java Servlet.
- When all objects are in place, HTML page is forwarded to the Web services.
- Browser views page.
No comments:
Post a Comment