web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
Chapter 12 12The VisiClient Container Chapter Important VisiClient is a container that provides a J2EE environment for services for application clients. Containers are an integral part of J2EE applications. Most applications provide containers for each application type. Application clients depend on their containers to supply system services to all J2EE components. For documentation updates, go to www.borland.com/techpubs/bes. Application Client architecture J2EE application clients are first tier client programs that execute in their own Java virtual machines. Application clients obey the model for Java technology-based applications, in that they are invoked at their main method and run until the virtual machine is terminated. Like other J2EE application components, application clients depend on a container to provide system services; though in the case of application clients, these services are limited. Figure 12.1 VisiClient architecture Chapter 12: The VisiClient Container 97
Application Client architecture Packaging and deployment Deploying the application client components into a VisiClient container requires the specification of deployment descriptors using XML. (Refer to J2EE 1.3 Specification for more information about application clients, and their deployment into a J2EE 1.3 compliant container.) Application clients are packaged in JAR files and include a deployment descriptor (similar to other J2EE application components). The deployment descriptor defines the EJB and the external resources referenced by the application. You can use the Borland Enterprise Server Deployment Descriptor Editor for packaging and editing application client components. For more information, go to the User’s Guide. The deployment descriptor is necessary because there are a number of functions that must be configured at deployment time, such as assigning names to EJBs and their resources. The minimum requirements for deployment of an application client into a VisiClient container are: ■ ■ All the client-side classes are packaged into a JAR. See below section on required client JARs and files. A well-formed JAR should have the following: ■ ■ Application specific classes including the class containing the application entry point (main class) The JAR file must have a META-INF subdirectory with the following: ■ A manifest file ■ A standard XML file (application-client.xml), as required by J2EE 1.3 specifications ■ A vendor-specific XML file (application-client-borland.xml) RMI-IIOP stubs which can also be packaged separately. In this case, the file needs the classpath attribute of the manifest file set to the appropriate value. The JAR formed in this manner is deployable to a standalone container or to an EAR file. The following sections in this chapter describe this process in detail. Benefits of the VisiClient Container VisiClient offers users a range of benefits from the use of J2EE applications. These include: ■ ■ Client code portability: Applications can use logical names (as recommended in the J2EE specifications) to access resources such as database connections, remote EJBs and environment variables. The container, per the J2EE specification, exposes the resources as administered objects in the local JNDI namespace (java:comp/env). JDBC Connection Pooling: Client applications in Borland Enterprise Server can use JDBC 2-based datasources (factories). VisiClient Container provides connection pooling to client applications in the Server that employ a JDBC 2-based datasource. For example, the VisiClient container's application uses java.net.URL, JMS, and Mail factories. Datasource and URL factories are deployed in the in-process local JNDI subcontext that resides in the client container virtual machine on startup. Other res-ref-types (such as JMS and Mail) are configured and deployed using the relevant tools from the vendor of these products. Refer to the Deployment, Datasources and Transaction chapters of the Borland Enterprise Server Developer's Guide for more information about configuration and deployment. 98 BES Developer’s Guide
- 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 and 70: Session management with JSS If an i
- 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: 96 BES Developer’s Guide
- 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
- Page 121 and 122: 110 BES Developer’s Guide
- Page 123 and 124: Container-managed persistence and R
- Page 125 and 126: Implementing an entity bean Generat
- Page 127 and 128: Container-Managed Persistence in Bo
- Page 129 and 130: Container-Managed Persistence in Bo
- Page 131 and 132: Setting Properties Setting Properti
- Page 133 and 134: Setting Properties into a BLOB. The
- Page 135 and 136: Setting Properties Automatic table
- Page 137 and 138: 126 BES Developer’s Guide
- Page 139 and 140: Container-managed persistence and R
- Page 141 and 142: Container-Managed Persistence in Bo
- Page 143 and 144: Container-Managed Persistence in Bo
- Page 145 and 146: Container-Managed Persistence in Bo
- Page 147 and 148: Container-Managed Persistence in Bo
- Page 149 and 150: Container-Managed Persistence in Bo
- Page 151 and 152: Container-Managed Persistence in Bo
- Page 153 and 154: 142 BES Developer’s Guide
- Page 155 and 156: Setting Properties J2EE 1.3 Entity
- Page 157 and 158: Setting Properties Figure 16.2 Edit
Chapter<br />
12<br />
12The VisiClient Container<br />
Chapter<br />
Important<br />
VisiClient is a container that provides a J2EE environment for services for application<br />
clients.<br />
Containers are an integral part of J2EE applications. Most applications provide<br />
containers for each application type. Application clients depend on their containers to<br />
supply system services to all J2EE components.<br />
For documentation updates, go to www.borland.com/techpubs/bes.<br />
Application Client architecture<br />
J2EE application clients are first tier client programs that execute in their own Java<br />
virtual machines. Application clients obey the model for Java technology-based<br />
applications, in that they are invoked at their main method and run until the virtual<br />
machine is terminated. Like other J2EE application components, application clients<br />
depend on a container to provide system services; though in the case of application<br />
clients, these services are limited.<br />
Figure 12.1<br />
VisiClient architecture<br />
Chapter 12: The VisiClient Container 97
Change language