web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
Managing and configuring the JSS Figure 6.2 JSS Management with Two Web Containers and a Centralized Backend Datastore Managing and configuring the JSS The JSS configuration is defined through its properties. BES supports two types of configurations; the default is to use a JDatastore, but BES supports any JDBC datasource. ■ ■ If JSS is configured to use a JDataStore file, the database tables are automatically created by JSS. If JSS is configured to use a JDBC datasource, three database tables needs to be pre-created in the backend database by your system administrator using the following SQL statements: CREATE TABLE "JSS_KEYS" ("STORAGE_NAME" STRING PRIMARY KEY, "KEY_BASE" BIGINT); CREATE TABLE "JSS_WEB" ("KEY" STRING PRIMARY KEY, "VALUE" BINARY, "EXPIRATION" BIGINT); CREATE TABLE "JSS_EJB" ("KEY" STRING PRIMARY KEY, "VALUE" BINARY, "EXPIRATION" BIGINT); The JSS can run as part of the Partition side-by-side with other Partition services. Chapter 6: Java Session Service (JSS) configuration 59
Managing and configuring the JSS Configuring the JSS Partition service As a “Partition service”, JSS configuration information is located in each Partition's data directory in the partition.xml file. By default, this file is located in the following directory: /var/domains/base/configurations//mos/ /adm/properties. For example, for a Partition named “MyPartition”, by default the JSS configuration information is located in: /var/domains/base/configurations//mos/ mypartition/adm/properties/partition.xml For more information, go to Chapter 30, “Partition XML reference.” Otherwise, for the location of a Partition data directory, go to the configuration.xml file located in: /var/domains/base/configurations// and search for the Partition Managed Object directory attribute:
- 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 and 68: IIS web server to Borland web conta
- Page 69: Session management with JSS If an i
- 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
- Page 119 and 120: Sessions in secondary storage If yo
Managing and configuring the JSS<br />
Figure 6.2<br />
JSS Management with Two Web Containers and a Centralized Backend Datastore<br />
Managing and configuring the JSS<br />
The JSS configuration is defined through its properties. BES supports two types of<br />
configurations; the default is to use a JDatastore, but BES supports any JDBC<br />
datasource.<br />
■<br />
■<br />
If JSS is configured to use a JDataStore file, the database tables are automatically<br />
created by JSS.<br />
If JSS is configured to use a JDBC datasource, three database tables needs to be<br />
pre-created in the backend database by your system administrator using the<br />
following SQL statements:<br />
CREATE TABLE "JSS_KEYS" ("STORAGE_NAME" STRING PRIMARY KEY, "KEY_BASE" BIGINT);<br />
CREATE TABLE "JSS_WEB" ("KEY" STRING PRIMARY KEY, "VALUE" BINARY, "EXPIRATION"<br />
BIGINT);<br />
CREATE TABLE "JSS_EJB" ("KEY" STRING PRIMARY KEY, "VALUE" BINARY, "EXPIRATION"<br />
BIGINT);<br />
The JSS can run as part of the Partition side-by-side with other Partition services.<br />
Chapter 6: Java Session Service (JSS) configuration 59