“Web accessible” means making Oracle Tuxedo application services available to Web-based applications. Figure 5‑1 illustrates Web client access to Oracle Tuxedo application services.A Web application server may be a Web server or a cross between a Web server and an application server. The standard definition of a Web server is “a server software system that serves static content to a Web browser by loading a file from a disk and serving it across the network to a user’s Web browser. This entire exchange is mediated by the browser and server talking to each other using Hypertext Transfer Protocol (HTTP).” The standard definition of an application server is “a server software system that occupies a large chunk of computing territory between database servers and the end user, and often connects the two. An application server is sometimes referred to as a type of middleware.” The Oracle Tuxedo system, itself, is essentially two high-performance application servers, a transaction processing application server and an object application server.Exposing Tuxedo services as Web services opens the application to the outside world without any application code changes. The application can be broken down into smaller modular components, or shared services, that can be shared by and used as components of distributed Web-based applications.For information about the Web services technologies, see W3C - Web Services Activity at http://www.w3.org/2002/ws.Figure 5‑2 shows the principal software components comprising Oracle Tuxedo native Web Services solution to expose Tuxedo application services as Web services.Oracle SALT provided Tuxedo system server (GWWS), connects with other Web service applications via SOAP over HTTP/S protocol. The GWWS server acts as a Tuxedo gateway process and is managed in the same manner as general Tuxedo system servers. Each GWWS server has bi-directional (inbound/outbound) capability. The GWWS server:Figure 5‑4 Exposing Tuxedo Application Services as Web Services Through Oracle AquaLogic Service BusThis Jolt client personality is a Jolt HTTP servlet, running in a Java Web application server environment (for example, Oracle WebLogic Server), through which simple Web-browser clients can invoke Tuxedo ATMI services. Accessing Tuxedo ATMI services in this manner requires the installation of Jolt class packages jolt.jar and joltjse.jar on the machine running the Web application server.This Jolt client personality is a customized version of Jolt JSE Connectivity for the Oracle WebLogic Server. Accessing Tuxedo ATMI services in this manner requires the installation of Jolt class packages jolt.jar, joltjse.jar, and joltwls.jar on the machine running Oracle WebLogic Server.For information on configuring the Jolt server and the Oracle Tuxedo server to work with Jolt, see “Oracle Jolt 10g Release 3 (10.3) Overview and Installation Information” in Installing the Oracle Tuxedo System.For common client and Web server deployment considerations, see Using Oracle Jolt and Using Oracle Jolt with Oracle WebLogic Server.Figure 5‑7 Web Access to Tuxedo Using Jolt or WTCFor details about using Jolt or WTC to achieve interoperability between Oracle Tuxedo and Oracle WebLogic Server, see “Interoperability with Oracle WebLogic Server” in Oracle Tuxedo Interoperability.