Installing the WebSphere was application server

WebSphere Application Server includes the servlet run engine, high-performance database connectors, application services for pre-connect, session, and state management, and WebSphere supports the XML document structure. In addition, WebSphere supports the 1.0 version of JSP, the 2.1 version of the servlet. There is a high-speed database buffer pool (support for databases such as DB2 Universal Database,oracle,microsoft SQL Server). ）

WebSphere can be installed on the NT, 95/98 operating system platform. Installation WebSphere must require more than 128 megabytes of memory, if 256 trillion is better. The operating system requires Windows NT (Pack 3). Before you install, you must have a Web server, which can be one of the following:

IBM HTTP Server version 1.3.3 Windows NT version (WebSphere Application Server installation CD includes IBM HTTP server)

Apache Server version 1.3.2 Windows NT Edition

Domino version 5.0 Windows NT Edition

Lotus Domino Go Webserver version 4.6.2.5 Windows NT Edition

Microsoft Internet Information Server version 3.x and version 4.0 Windows NT Edition

Netscape Enterprise Server version 3.01 and version 3.51 Windows NT Edition (recommended version 3.5.1)

Netscape FastTrack Server version 3.01 Windows NT Edition

The Java Development Component (JDK) is also required, and we recommend using the JDK1.1.6 provided with the WebSphere application server. You also need the Java servlet api,websphere application server to include JSDK version 2.0 or later. Of course, you also need web browsers and appletviewer or browsers that support JDK1.1. For example: Netscape Navigator 4.06 or 4.0.7, or Microsoft Internet Explorer 4.01 or later with a fix pack, or Sun HotJava 1.1 or later. Some older browsers do not properly handle text that enables native language support. If you see a foreign character on the user interface, such as "senable" instead of "Enable," you can correct it by upgrading your browser.
First step: Install the Web server:

If you plan to install an IBM HTTP server, you must install it before you install the WebSphere application server. The WebSphere Application Server installation CD has IBM HTTP server. Installing the WebSphere Application Server changes the WEB server httpd.conf file. However, if the Web server was installed after the WebSphere Application server was installed, no changes were made and the WebSphere application Server was not able to run correctly. After you install the IBM HTTP server, you need some configuration to enable SSL support. For specific configuration, refer to the IBM HTTP Server documentation for instructions.

For other Web servers that you plan to install, such as Apache server, install the WebSphere Application Server before installing it.

Step two: Before installing:

Before installing, if you have an older version of WebSphere in your system, uninstall the old version first. Then install the new version. Before uninstalling, it is a good idea to back up the WebSphere Application Server version 1.x file.

(1) File backup

Before uninstalling a previous version of WebSphere Application Server from Windows NT, make sure that the files you want to migrate are already or will be saved. The graphical user interface that is displayed when you install the WebSphere Application Server version 2.0 backs up the files in the WebSphere Application Server directory, including classes, domains, Servlet, property files, where the property files include Servlet.properties, Admin_ Port.properties, Rules.properties, Jvm.properties, Aliases.properties, Connmgr.properties, Userprofile.properties. If a file resides outside these four directories (for example, if you create your own directory in a WebSphere Application Server installation), install WebSphere Application Server version 2.0. Before, back up files in a location other than the WebSphere Application server installation.

(2) Uninstall previous version

For Windows NT, use the Add/Remove option in the Start--> Control Panel, or uninstall from the IBM WebSphere--> WebSphere Application Server version 1.x from the start--> program-->.

In addition, you need to clear the CLASSPATH. Delete this information before you install version 2.0. For Web servers using Go Webserver on Windows NT, Java support on the Go Webserver is automatically uninstalled when the WebSphere Application server is installed. Please refer to the documentation for other information.

Step three: Install the WebSphere server:

Before you install the WebSphere application Server, make sure that you have:

(1) Back up all files that have not been automatically backed up by Setup

(2) Install the WEB server that you plan to use. The WEB server must be installed before the WebSphere Application server is installed.

(3) Make sure that the Web server has stopped running before you install it.

Note: If you specify the use of an IBM HTTP server or Apache server during the installation of the WebSphere application server, you will be prompted to confirm the location of the WEB server httpd.conf file.

On Windows NT, insert the WebSphere Application Server installation CD, go to a subdirectory named after the Windows NT operating system, and run the executable installer (Setup.exe). A series of dashboards will guide you through the installation.

Configuring the WebSphere Application Server

The following describes how to configure a WebSphere application server so that it and its components can work together. After these tasks are completed, the WebSphere Application server is able to run almost all functions by default configuration.

(1) Configure Apache Server

If you are using Apache server as your Web server, join this line in the httpd.conf file:

Addmodule mod_app_server.c.

(2) using the database.

To ensure that the WebSphere application server is connected to a relational database such as Oracle or DB2: Add the. zip file to the file <as_root >/properties/bootstrap.properties Java.classpath property. You can also specify files by using the Java engine page of the manager interface of the WebSphere application server. Also, make sure Java.classpath contains valid drivers for database connections.

(3) Operating mode

The Ose.mode property is used to control whether the WebSphere application server is part of a Web server (in-process) or run in standalone mode (out-of-process). This property is in the <as_root>/properties/bootstrap.properties file. The default value for Ose.mode is out. The Apache server or IBM HTTP server requires that the set Ose.mode property must be out, meaning that the WebSphere application server must be running in standalone mode. For other Web servers, you can ose.mode as in and run the WebSphere Application server as part of the Web server. But that's not usually the way to do it. If necessary, reset Ose.mode means to set the value of Ose.mode to out. For example, if you convert from Netscape Enterprise Server (ose.mode=in), which runs as part of Webserver, to an IBM HTTP server (requiring ose.mode=out), don't forget to run the IBM HTTP Server , change the Ose.mode property to out.

In addition to the manual editing of the Bootstrap.properties file, the Java engine page of the manager interface provides an easy way to lock the Ose.mode property value. The Java engine page provides a radio button that can be used to indicate that a WebSphere application server is running as part of a WEB server (ose.mode=in) or in stand-alone mode (ose.mode=out).

Running the WebSphere Application server as part of a WEB server provides high performance for the servlet and other applications, but is less secure. Running the WebSphere Application server as part of a Web server allows the WebSphere application server to stop automatically when the Web server is closed. Running the WebSphere Application Server in standalone mode requires additional steps.
Start and stop the WebSphere application server

When you start a WEB server, the WebSphere application server starts automatically.

If you run a WebSphere application server as part of a Web server, the WebSphere application server will automatically stop when the Web server is closed. If you run in standalone mode, the WebSphere application server does not automatically stop.

When the WebSphere application server is running out-of-process on Windows NT, stopping the WEB server requires you to manually stop the WebSphere Servlet service to stop the WebSphere application server. To do this, select the WebSphere Servlet service from the Start--> Settings--> Control Panel--> and press the Stop button.

Installation inspection and fault finding

To verify that the WebSphere Application server is installed and configured correctly, invoke the Snoop servlet provided by the WebSphere application server. Use a Web browser to enter in the Address bar: Http://your.server.name/servlet/snoop. The Snoop Servlet should echo the HTTP requests sent by the client and the initialization parameters of the servlet. The code for Snoopservlet and other servlet is located in the <as_root>/servlets directory. If the servlet fails:

(1) If you have previously edited the. properties file by hand or changed the configuration of the WebSphere application server, first look at the files to see if they introduce illegal or incorrect values. In particular, check <as_root>/properties/bootstrap.properties files.

(2) Open local logs and traces for the Web server. Locate the WebSphere Application Server Bootstrap.properties file first. The ose.trace.enabled and Ose.trace.to.webserver properties are then set to true. Stop the WEB server and restart. If the WebSphere application server is running in standalone mode, it does not stop when the WEB server is stopped. Check the WEB server error log and the logs in the <as_root>/logs directory of the WebSphere application server. Look at the cause of the error.

(3) Enable the debug console and restart the Web server. The debug console for the WebSphere Application server is used to collect and view tracking and monitoring data. For example, from the debug console, you can act as a set of monitoring programs that start and stop columns in the collection and monitoring of server data. In the server console of the debug console, the stdout and stderr streams of the servlet are allowed to be viewed. By default, the console is not started. Set the Debug.server.console.enabled property to True in the WebSphere Application server Debug.properties file, and then restart the Web server to make the changes take effect. Alternatively, you can run Http://your.server.name/servlet/DebugConsoleServlet in the Web to enable the debug console. On Windows NT, to successfully view the debug console, you must configure Windows NT to allow one or more services to interact with the Windows desktop. If you are using a WEB server that is running as a Windows NT service:

Select Start--> Settings--> Control Panel--> service.

Select the appropriate service for the WEB server.

Click the Start button.

In the Results dialog box, select the check boxes that allow the service to interact with the desktop.

Restart the WEB server for the changes to take effect.

For Microsoft's IIS servers, perform the above procedures for each service associated with the Web server, such as Web publishing and FTP services. These services must be allowed to interact with the Windows NT desktop. If the WebSphere application server does not start any WEB server-related processes at run time, you need to perform the above procedure for the WebSphere Servlet service to allow the service to interact with the desktop.