|
|
|
|
|
|
BEA Jolt 8.0 Preparations
The following sections provide prerequisites for installing the BEA Jolt software components, and installation instructions:
BEA Jolt Server Support
The server components of BEA Jolt 8.0 and BEA Jolt Relay can be installed on any system on which the BEA Tuxedo 8.0 product can be installed. Your environment must provide:
For BEA Jolt system requirements, including a list of platforms on which BEA Jolt is supported, see Appendix A, "BEA Tuxedo 8.0 Platform Data Sheets.
Supported Web Servers
To provide HTTP/HTML-based access to enterprise applications, BEA Jolt supports the Microsoft Internet Information Server (IIS) and the Java Web Server.
BEA Jolt Client Support
BEA Jolt supports Java applets and standalone Java client applications. The client types supported by BEA Jolt 8.0 are listed in the following table.
The HTML-based BEA Jolt client classes run inside a Web server. The Web servers certified with BEA Jolt 8.0 are listed in the following table.
Note: ASP Connectivity for BEA Tuxedo is the name of the Jolt Web application server that works with the existing Microsoft Internet Information Server (IIS) to provide a gateway for HTML clients into a BEA Tuxedo application environment. ASP (short for Active Server Pages) is an open, compile-free application environment in which Visual Basic programmers can combine HTML, scripts, and reusable ActiveX server components to create dynamic Web pages. Interactions between the Web server and Jolt classes are performed through VBScript and VB inside ASP. Note: JSE Connectivity for BEA Tuxedo is the name of the Jolt Web application server that simplifies the handling of servlets in a BEA Tuxedo application environment. JSE is short for Java Servlet Engine. BEA Jolt Client Requirements BEA Jolt has the following client requirements:
BEA Jolt Client Class Library
Various implementations of Java tend to show minor differences in characteristics. BEA Jolt 8.0 is based on JDK 1.3.0.
The BEA Jolt class library is compatible with the browsers and JDK versions shown in the following table.
BEA Jolt Release Migration/Interoperability
The BEA Tuxedo system provides increased interoperability between releases. In BEA Jolt 8.0, however:
If BEA Jolt 1.2 is installed on your system, we recommend uninstalling it before installing BEA Jolt 8.0.
ASP Connectivity Prerequisites
The following components are required before you can install BEA Jolt 8.0 ASP Connectivity for the BEA Tuxedo system:
For details about the Microsoft products listed here, see the online Microsoft 2000 Option Pack product documentation, specifically the documentation about Microsoft Internet Information Server.
Note: Always use the latest version of the Java Virtual Machine (JVM) to ensure that ASP Connectivity for the BEA Tuxedo system works properly.
BEA Jolt Pre-Installation Checklist
BEA Tuxedo 8.0 server software includes BEA Jolt 8.0, so before you start an installation, check the following:
On Windows systems, BEA Jolt 8.0 automatically installs two Microsoft dynamic link libraries (DLLs), MSVCRT.DLL and MFC42U.DLL, and overwrites older versions of these libraries. Before you begin installation, check whether older versions of these dynamic link libraries already exist. If they do exist and you do not want them to be overwritten, back them up.
Installing and Configuring Jolt 8.0 with BEA Tuxedo 8.0 and WebLogic Server 6.0
This section provides supplementary installation and configuration instructions for customers using BEA Jolt 8.0 with BEA Tuxedo 6.5 or 7.1 and WebLogic Server 6.0. It also offers code for a sample servlet that demonstrates how a WebLogic servlet may connect to BEA Tuxedo and call on a BEA Tuxedo service.
Installation
The Jolt client consists of two JAR files: jolt.jar and joltwls.jar. Include both files in your classpath setting. The client should not get the PoolManager by doing a JNDI lookup (as in an earlier release of Jolt). For an example of a Jolt client, go to the section titled Example Servlet and see the code shown after the comment "Required change for Weblogic 6.0" (highlighted in bold). Configuration To configure the Jolt connection pool, open the WebLogic Server Administration Console and complete the following procedure:
Example Servlet
The following sample servlet shows how a WebLogic servlet, invoked from simpapp.html, connects to the BEA Tuxedo system and calls a BEA Tuxedo service.
Listing 7-1 Example WebLogic Servlet
Copyright © 2002 BEA Systems, Inc. All rights reserved.
package examples.jolt.servlet.simpapp;
import bea.jolt.pool.servlet.weblogic.PoolManagerStartUp;
import bea.jolt.pool.servlet.*;
import bea.jolt.pool.ApplicationException;
import bea.jolt.pool.SessionPoolException;
import bea.jolt.pool.ServiceException;
import bea.jolt.pool.SessionPoolManager;
import java.util.Hashtable;
import java.io.IOException;
import java.io.PrintWriter;
import javax.servlet.*;
import javax.servlet.http.*;
import javax.naming.*;
import weblogic.jndi.*;
/**
* This example demonstrates how a WebLogic Servlet may connect to
* TUXEDO and call upon one of its services;
* it should be invoked from the
* <i>simpapp.html</i> file. The servlet creates a session pool
* manager, which is used to obtain a session when the
* <tt>doPost()</tt> method is invoked.
* This session is used to connect to a service
* in TUXEDO with a name described by the posted
* "SVCNAME" argument. In this example the service is called
* "TOUPPER", which transposes the posted "STRING" argument text
* into uppercase, and returns the result. This is
* returned to the client browser within some generated HTML.
* THIS IS SOURCE CODE PUBLISHED FOR DEMONSTRATION PURPOSES
*
* @author Copyright (c) 1998-2000 BEA Systems, Inc. All rights reserved.
*/
public class SimpAppServlet extends HttpServlet {
/**
* Private variable to hold the
* pool manager object.
*/
/* Required change for Weblogic 6.0 */
private ServletSessionPoolManager b_mgr = (ServletSessionPoolManager) SessionPoolManager.poolmgr;
/* End Required change for Weblogic 6.0 */
/**
* Initializes the servlet. The session pool manager and the
* simpapp session pool have been established during the startup.
*
* @param config Servlet configuration
* @exception ServletException if the servlet fails
*/
public void init(ServletConfig config) throws ServletException {
super.init(config);
}
/**
* Destroys this servlet. The ServletSessionPoolManager
* resource is deallocated.
*/
public void destroy() {
b_mgr = null;
}
/**
* Implements the HttpServlet <tt>doPost()</tt> method.
* This method expects POSTed arguments for:
* <dl>
* <dt>"SVCNAME"<dd>The name of the service to be invoked in TUXEDO.
* <dt>"STRING"<dd>The text to be transposed to uppercase.
* </dl>
*
* <p> See the provided simpapp.html for the HTML form
* used to submit the data.
*/
public void doPost(HttpServletRequest req, HttpServletResponse resp)
throws ServletException, IOException
{
ServletResult result;
ServletOutputStream out = resp.getOutputStream();
out.println("<html><head><title>Jolt SimpApp Example
Response</title></head>
");
out.println("<body><font face=\"Helvetica\">" +
"<h2><font color=#DB1260>" +
"This is the response from the SimpAppServlet:" +
"</font></h2>");
/* Begin Required change for Weblogic 6.0 */
// Get the "demojoltpool" session pool
ServletSessionPool session = (ServletSessionPool)
b_mgr.getSessionPool("demojoltpool");
/* End Required change for Weblogic 6.0 */
if (session == null) {
out.println("The servlet failed to obtain a SessionPool for simpapp. "+
"<br>"+
"Possibly the TUXEDO server is not running, "+
"or there is a configuration problem."+
"</font></body></html>"
Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.