INTRODUCTION TO TUXEDO, WSL, JSL

INTRODUCTION

Tuxedo is often called middleware, it is also referred to as a messaging protocol. In PeopleTools it stands between the Client and the database. It passes messages between the client and the database. It also performs some of the processing that is done on the client in two-tier operation. The client connects to Tuxedo and Tuxedo connects to the database. Conceptually, the PeopleTools client in three-tier mode is the same in the two-tier. However, the client has been cut in half. The front half consists of the presentation layer and some of the application logic processing that is still on the client. The back half has the rest of the application logic layer, which makes the connection to the database. The two halves are reconnected by Tuxedo.

Conceptually it is the cans on each end of the string in the above cartoon. It is made up of a number of server processes that communicate with the client via shared memory segments and queues. Servers are software modules responsible for processing requests and sending replies back to clients. Services are application-specific code within servers that process clients' requests. Often, as in the case with PeopleSoft, they process calls for accessing a database Tuxedo has the ability to spawn addition copies of server processes in response to demand, to assign priorities to client requests, and allow parallel execution of service requests, thus increasing throughput,

Workstation Listener (WSL) & Workstation Handler (WSH) The WSL listens on a particular IP address and ports for requests for connection from clients. The client is then assigned a port on a WSH. The WSL will if necessary, and if the configuration allows spawn an additional WSH process. There can be multiple WSL as well as WSH processes in a single domain.

TU X

X TU

CONFIGURATION MANAGER

The PeopleSoft Client must be told where to find the WSLs, so in the configuration manager there is a Tuxedo connection string.

JOLT COMPONENTS

Jolt Components
Jolt is used by PeopleSoft to connect the Web client, which is written in Java, to the application server

The requests from the Java client are passed through the Jolt Server into the Tuxedo domain. Thus, one application server can support both Web and Windows clients.

Jolt Server Listener (JSL) & Jolt Server Handlers Jolt servers listen for network connections from clients, translate Jolt messages, multiplex multiple clients into a single process, and submit and retrieve requests to and from TUXEDO based applications running on one or more TUXEDO servers. The JSL handles the initial Jolt client connection, and is responsible for spawning JSH processes, and assigning a Jolt client to the Jolt Server Handler The JSH manages network connectivity, executes service requests on behalf of the client and translates TUXEDO buffer data into the Jolt buffer and vice versa. These processes mirror the WSL and WSH processes, and have the same command line parameters.

Jolt Repository Server (JREPSRV) The Jolt Repository is a database where TUXEDO services are defined, such as name, number, type, parameter size, and permissions. The Repository functions as a central database of definitions for TUXEDO services and permits new and existing TUXEDO services to be made available to Jolt client applications. All or only a few of these definitions may be exported to the Jolt Repository. Within the Jolt Repository, the developer or system administrator can export these services to the Jolt client application. The JREPSVR retrieves Jolt service definitions from the Jolt Repository and returns the service definitions to the JSH. The JREPSVR also updates or adds Jolt service definitions.

Jolt Relay Adapter (JRAD) JRAD is a TUXEDO application server, but does not include any TUXEDO services. It requires command line arguments to allow it to work with the JSH and TUXEDO.

Within PeopleTools, it is typically used when the web server for the Java client is on a different IP address to the JSL/JSH processes. It is a security restriction of Java that it can only connect to the server from which it was served up. Jolt Relay is used to redirect the connection from the web server to the application server. The Jolt relay is transparent to Jolt clients and Jolt servers. A Jolt server can simultaneously connect clients directly to the Jolt Server (intranet clients) and via the Jolt Relay (Internet clients) The JRLY (front-end relay) process may be started before or after the JRAD is started. If the JRAD is not available when the JRLY is started, the JRLY attempts to connect to the JRAD when it receives a client request. If JRLY is unable to connect to the JRAD, the client is denied access and is disconnected. A warning is written to the JRLY error log file. JRAD receives client requests from JRLY, and forwards the request to the appropriate server. Replies from the server are forwarded back to JRAD, which sends the response and back to the requesting client. A single Jolt Internet Relay (JRLY/JRAD pair) handles multiple clients concurrently.

PeopleSoft Components
PeopleSoft has written various server processes. They each perform various functions. Each function, which has literally be been coded as a single function, corresponds to an activity within the client, such C as a panel load, a panel save, executing a SQL query statement. PeopleSoft delivers platform specific versions of the application servers for each platform. This partly explains the size of the PeopleTools patches. This explains the size of PeopleTools patches, because compiled executables for 10 different platforms are delivered. HANDLING COMMUNICATION All communications from clients to the application server domain are in the form of messages requesting a service. At the initial connection the client contacts the workstation listener (WSL) who then assigns it to a workstation handler (WSH). There after the client communicates with the WSH

SOURCE : PEOPLE BOOKS

COMPILED : GIRIDARAN S