web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
Chapter 6 6Java Session Service (JSS) Chapter configuration The Java Session Service (JSS) is a service that stores information pertaining to a specific user session. JSS is used to store session information for recovery in case of container failure. Borland provides an Interface Definition Language (IDL) interface for the use of JSS. Two implementations are bundled, one using DataExpress and another with any JDBC capable database. JSS provides a mechanism to easily store session information in a database. For example, in a shopping cart scenario, information about your session (the number of items in the shopping cart, and such) is stored by the JSS. So, if a session is interrupted by a Borland web container unexpectedly going down, the session information is recoverable by another Borland web container instance through the JSS. The JSS must be running on the local network. Any web container (within the cluster configuration) finds the JSS and connects to it and continues session management. For more information about the Borland web container, go to Chapter 4, “Web components.” Session management with JSS The following diagrams show typical landscapes of web components and how session information is managed by the JSS. The JSS session management is completely transparent to the client. In the “JSS Management with a Centralized JSS and Two Web Containers” diagram, there are four virtual machines: ■ ■ ■ The first machine hosts the Apache web server, two other machines contain an instance of the Borland web container, and the fourth machine hosts the JSS and relational database (JDataStore or a JDBC datasource). Chapter 6: Java Session Service (JSS) configuration 57
Session management with JSS If an interruption occurs between the Apache web server (Machine 1) which is passing a client request to the first web container instance (Machine 2), then the second web container instance (Machine 3) can continue processing the client request by retrieving the session information from the JSS (Machine 4). The items in the Shopping Cart are retained and the client request continues to be processed. Figure 6.1 JSS Management with a Centralized JSS and Two Web Containers In the “JSS Management with Two Web Containers and a Centralized Backend Datastore” diagram, are the following four virtual machines: ■ ■ ■ The first machine hosts the Apache web server, the two other machines contain an instance of the Borland web container as well as each hosting the JSS, and the fourth machine hosts the relational database (JDataStore or a JDBC datasource). If an interruption occurs between the Apache web server (Machine 1) which is passing a client request to the first web container instance (Machine 2), then the second web container instance (Machine 3) can continue processing the client request by retrieving the session information from the JSS (Machine 4). The items in the Shopping Cart are retained and the client request continues to be processed. 58 BES Developer’s Guide
- Page 17 and 18: Contacting Borland support World Wi
- Page 19 and 20: BES services overview Figure 0.1 Bo
- Page 21 and 22: The Partition and its services ■
- Page 23 and 24: Borland Enterprise Server and J2EE
- Page 25 and 26: 14 BES Developer’s Guide
- Page 27 and 28: Creating Partitions Creating Partit
- Page 29 and 30: Running Partitions Table 3.1 Option
- Page 31 and 32: Configuring Partitions You can also
- Page 33 and 34: JMX support in Partitions ■ ■ A
- Page 35 and 36: JMX support in Partitions Figure 3.
- Page 37 and 38: Thread pools Partition properties r
- Page 39 and 40: 28 BES Developer’s Guide
- Page 41 and 42: Apache web server implementation Fo
- Page 43 and 44: Borland web container implementatio
- Page 45 and 46: Borland web container implementatio
- Page 47 and 48: Borland web container implementatio
- Page 49 and 50: Smart Agent implementation Smart Ag
- Page 51 and 52: 40 BES Developer’s Guide
- Page 53 and 54: Apache web server to Borland web co
- Page 55 and 56: Apache web server to Borland web co
- Page 57 and 58: Apache web server to Borland web co
- Page 59 and 60: Large data transfer Downloading lar
- Page 61 and 62: Large data transfer Uploading large
- Page 63 and 64: IIS web server to Borland web conta
- Page 65 and 66: IIS web server to Borland web conta
- Page 67: IIS web server to Borland web conta
- Page 71 and 72: Managing and configuring the JSS Co
- Page 73 and 74: The Borland IIOP connector BES supp
- Page 75 and 76: Setting up your web container with
- Page 77 and 78: 66 BES Developer’s Guide
- Page 79 and 80: Web-enabling your CORBA server Impo
- Page 81 and 82: Configuring your Apache web server
- Page 83 and 84: Configuring your Apache web server
- Page 85 and 86: Web Services and Partitions ■ ■
- Page 87 and 88: Web Service providers Java:RPC prov
- Page 89 and 90: How Borland Web Services work
- Page 91 and 92: Packaging Web Service Application A
- Page 93 and 94: Tools Overview Java2WSDL tool Note
- Page 95 and 96: 84 BES Developer’s Guide
- Page 97 and 98: Client view of an enterprise bean L
- Page 99 and 100: Client view of an enterprise bean E
- Page 101 and 102: Managing transactions Managing tran
- Page 103 and 104: Support for JNDI Support for JNDI T
- Page 105 and 106: EJB to CORBA mapping A CORBA progra
- Page 107 and 108: 96 BES Developer’s Guide
- Page 109 and 110: Application Client architecture Pac
- Page 111 and 112: Document Type Definitions (DTDs) my
- Page 113 and 114: Support of references and links The
- Page 115 and 116: Use of Manifest files Use of Manife
- Page 117 and 118: 106 BES Developer’s Guide
Chapter<br />
6<br />
6Java Session Service (JSS)<br />
Chapter<br />
configuration<br />
The Java Session Service (JSS) is a service that stores information pertaining to a<br />
specific user session. JSS is used to store session information for recovery in case of<br />
container failure.<br />
<strong>Borland</strong> provides an Interface Definition Language (IDL) interface for the use of JSS.<br />
Two implementations are bundled, one using DataExpress and another with any JDBC<br />
capable database.<br />
JSS provides a mechanism to easily store session information in a database. For<br />
example, in a shopping cart scenario, information about your session (the number of<br />
items in the shopping cart, and such) is stored by the JSS. So, if a session is<br />
interrupted by a <strong>Borland</strong> <strong>web</strong> container unexpectedly going down, the session<br />
information is recoverable by another <strong>Borland</strong> <strong>web</strong> container instance through the JSS.<br />
The JSS must be running on the local network. Any <strong>web</strong> container (within the cluster<br />
configuration) finds the JSS and connects to it and continues session management.<br />
For more information about the <strong>Borland</strong> <strong>web</strong> container, go to Chapter 4, “Web<br />
components.”<br />
Session management with JSS<br />
The following diagrams show typical landscapes of <strong>web</strong> components and how session<br />
information is managed by the JSS. The JSS session management is completely<br />
transparent to the client.<br />
In the “JSS Management with a Centralized JSS and Two Web Containers” diagram,<br />
there are four virtual machines:<br />
■<br />
■<br />
■<br />
The first machine hosts the Apache <strong>web</strong> <strong>server</strong>,<br />
two other machines contain an instance of the <strong>Borland</strong> <strong>web</strong> container,<br />
and the fourth machine hosts the JSS and relational database (JDataStore or a<br />
JDBC datasource).<br />
Chapter 6: Java Session Service (JSS) configuration 57
Change language