for any software, some planning and specific steps are required to ensure a successful installation. This is true for installing and preparing WebSphere application servers and their components. The following describes installing and configuring a WebSphere Application server on Windows NT
- 1. Memory and software requirements
(1) Memory: At least MB RAM, recommended in MB. The WebSphere Application Server installation CD includes the Java development tools (JDK).
(2) Operating system: Microsoft NT version 4.0 and Service Pack 3.
(3) WEB server: WebSphere Application Server requires one of the following servers.
IBM HTTP Server version 1.3.3 Windows NT Edition (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
(4) Java development Component (JDK): JDK1.1.6 is recommended for use with WebSphere application servers.
(5) Java servlet api:websphere Application Server includes JSDK version 2.0 or later.
(6) Web Browser: The manager of the WebSphere application server is the user interface used to manage the servlet. To run the manager,
Browsers that require appletviewer or support JDK1.1, such as:
Netscape Navigator 4.06 or 4.0.7, including integrated JDK 1.1 support and provided by the following WEB sites:
Http://developer.netscape.com/software/jdk/download.html.
or Microsoft Internet Explorer version 4.01 or later with a remediation package.
Sun HotJava version 1.1 or later
Some older browsers are not able to correctly handle text that enables native language support. If you see foreign characters in the user interface, such as "senable" instead of "Enable", you can upgrade your browser to correct it.
- 2. Installing the Web server
If you plan to install an IBM HTTP server, install it before you install the WebSphere application server. You can install the IBM HTTP Server from the WebSphere Application Server installation CD. Installing the WebSphere Application Server changes the WEB server httpd.conf file. If the installation of the WEB server is installed after the WebSphere Application server is installed, no changes will be made and the WebSphere application server will not be able to run correctly. After installing the IBM HTTP server, some configuration is required to enable SSL support. Refer to the IBM HTTP Server documentation for instructions.
For any other Web server that you plan to install (such as Apache server), install it before installing the WebSphere Application Server. The reason is ditto.
- 3. Before installing the WebSphere Application Server
Uninstall all previous versions before installing WebSphere Application Server version 2.0. Back up the WebSphere Application Server version 1.x files before uninstalling.
(1) File backup
Before uninstalling a previous version of the WebSphere Application server from Windows NT, make sure that the files to be migrated are or will be saved. The graphical user interface that is displayed when installing WebSphere Application Server version 2.0 backs up files in the WebSphere Application Server directory, including classes, Realms, Servlets, properties files, where the properties file includes Servlet.properties, Admin_ Port.properties, Rules.properties, Jvm.properties, Aliases.properties, Connmgr.properties, Userprofile.properties. If you have files that reside outside of these four directories (for example, if you create your own directory in the WebSphere Application Server installation), install WebSphere Application Server version 2.0. Backup files in a location other than the WebSphere Application server installation.
The first part of the migration process is included here. The second part must be executed after installing WebSphere Application Server version 2.0. Please refer to the documentation for more information.
(2) Uninstall the previous version
For Windows NT, use Start-to-Add/Remove options in Control Panel, or uninstall from start-to-program, IBM WebSphere-to-WebSphere Application Server version 1.x.
Note: When a version of the WebSphere Application server is installed, it copies the Web site configuration file as a backup file, and then modifies the original configuration file. This modified file becomes the active configuration file when using the Web server. When you uninstall a WebSphere Application server, the previous configuration file is not restored, and it is still a backup file. In order for these settings to be active again, they must be converted from the backup file to the active Web server configuration file.
In addition, you need to clear CLASSPATH. If you already have information from a previous version of WebSphere Application Server in CLASSPATH, remove this information before you install version 2.0. For Web servers that use Go Webserver on Windows NT, Java support on Go Webserver can be uninstalled automatically when installing WebSphere Application server. Please refer to the documentation for other documents.
- 4. Installing the WebSphere Application Server
Before installing the WebSphere Application Server, make sure that you have:
(1) Back up all files that were not automatically backed up by the Setup program (installed from a previous WebSphere application server).
(2) Install the WEB server you plan to use. The WEB server must be installed before installing the WebSphere Application Server.
(3) If the WEB server is running, stop it.
Note: During installation of the WebSphere application server, if you specify to use an IBM HTTP server or Apache server, you will be prompted to confirm the location of the WEB server httpd.conf file.
Install on Windows NT, insert the WebSphere Application Server installation CD, go to a subdirectory named Windows NT operating system, run the executable setup program (Setup.exe). A series of panels will guide you through the installation.
- 5. Configure WebSphere Application Server
The following describes the necessary configuration to enable the WebSphere application server and its components to work together. Once these tasks are completed, the WebSphere Application server will be able to run all features primarily by using the default settings.
(1) Configuring Apache Server
If you are using Apache server as your Web server, make sure that the httpd.conf file contains this line: Addmodule mod_app_server.c.
(2) Use the database.
To ensure that the WebSphere Application server maintains and uses a connection to a relational database (such as Oracle or DB2), add a database. zip file to the file <as_root >/properties/bootstrap.properties The Java.classpath property in the, or the Java engine page that uses the manager interface of the WebSphere application server to specify the file. Again, make sure that the Java.classpath contains a valid driver for the database connection. See the WebSphere Application Server version 2.0 Readme file on the product Web site for additional tips.
(3) Operating mode
The Ose.mode property controls whether the WebSphere application server is running as part of the WEB server (in-process) or in standalone mode (out-of-process). This property is located in the <as_root>/properties/bootstrap.properties file. For all servers, the Ose.mode default value is out. If you are using Apache server or an IBM HTTP server, you must set the Ose.mode property to out, which means that the WebSphere application server is running in standalone mode. For other Web servers, it is possible (but not recommended) to change Ose.mode to in and run the WebSphere Application server as part of the Web server. Please reset ose.mode whenever necessary. For example, if you convert from Netscape Enterprise Server (ose.mode=in) that is running as part of Webserver to an IBM HTTP server (requires ose.mode=out), do not forget to run the IBM HTTP Server , change the Ose.mode property to out.
Compared to manually editing the Bootstrap.properties file containing the Ose.mode property, the Java engine page of the manager interface provides an easy way to lock the 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 standalone mode (ose.mode=out). See About document learning how to access Manager.
The value of the ose.mode is affected. Running WebSphere application servers as part of a WEB server provides high performance for servlets 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 shut down. Running the WebSphere Application Server in standalone mode requires additional steps. Please refer to the documentation for more details.
- 6. Starting and stopping a WebSphere application server
The WebSphere Application server starts automatically when the WEB server is started. The manager of the WebSphere Application server, accessed through a Web browser, provides an interface for viewing and changing the settings and performance of WebSphere application servers. See Customizing configuration settings.
If you run the WebSphere Application server as part of a Web server, the WebSphere application server stops automatically when the Web server is shut down. If you run in standalone mode, the WebSphere application server does not stop automatically. If you use Apache server or IBM HTTP as your Web server, the WebSphere application server must run in standalone mode.
When you run a WebSphere application server outside the process on Windows NT, stop the WebSphere Servlet service to stop the WebSphere application server after you stop the WEB server. Select the WebSphere Servlet service from start-up, and Control Panel--Press the Stop button.
- 7. Installation of inspection and fault search
To verify that the WebSphere Application server is installed and configured correctly, you can invoke the Snoop servlet provided by the WebSphere application server. Open the servlet url:http://your.server.name/servlet/snoop using a Web browser. The Snoop servlet should echo the HTTP request sent by the client and the initialization parameters of the servlet. The code for Snoopservlet and other Servlets is located in the <as_root>/servlets directory. If the servlet fails, try the following steps:
(1) If you have changed the configuration settings of any WebSphere application server by manually editing the. properties file or by using the WebSphere Application server's manager interface, check these files to ensure that no illegal or incorrect values are introduced. Special check <as_root>/properties/bootstrap.properties files. The Documentation Center contains information about the manual configuration of these properties and discussion materials about the acceptability and default values for each configuration.
(2) Open local logs and traces for the Web server. Locate the WebSphere Application Server Bootstrap.properties file (in the <as_root>/properties directory). Set the Ose.trace.enabled property to True to set the Ose.trace.to.webserver property to True. Stop the WEB server and restart. Remember that 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 log in the WebSphere Application Server <as_root>/logs directory to see the error.
(3) Enable the debug console and restart the Web server. The debug console of the WebSphere Application Server provides a central place for collecting and viewing 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 data collection and monitoring server. The Server Console tab of the Debug console allows you to view the stdout and stderr streams of the servlet. By default, the debug console is not enabled. Enable the console. Set the Debug.server.console.enabled property to True in the WebSphere Application server debug.properties file and restart the Web server for the changes to take effect. Or, run Http://your.server.name/servlet/DebugConsoleServlet and 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:
L Select Start-and-click Settings-Control Panel-services.
L Select the appropriate service for the WEB server.
L Click the Start button.
In the Results dialog box, select the check box that allows the service to interact with the desktop.
L Restart the WEB server for the changes to take effect.
For Microsoft Internet Information Server, for each service related to the Web server, such as Web publishing and FTP
Service) to perform the above process. These services must allow interaction with Windows NT desktops. If the WebSphere application Server runtime does not start any WEB server-related processes, perform the above procedure for the WebSphere Servlet service to allow the service to interact with the desktop.
- 8. Porting from version 1.x to version 2.0
After installing the WebSphere Application Server, complete the migration using the following steps:
(1) Please check that the user Servlet, domain, class, JavaServer page (JSP) and other programming-related files saved during the first part of the migration process have been placed in the WebSphere Application Server version 2.0 directory to which they belong. The setup program should have completed these steps for you. If you have backed up user files or directories that you created in the WebSphere Application Server installation, place them in the new installation now.
(2) The transfer jvm.properties file is set to the WebSphere Application Server version 2.0 bootstrap.properties file.
For WebSphere Application Server classpath, migrate only the user-specified classpath section to Bootstrap.properties
Do not transfer the JVM library or WebSphere Application Server version 1.x. jar file path Because these are part of the default configuration for WebSphere Application Server version 1.x and you have not set them yourself. In other words, only the partial classpath that you add is transferred. Do not remove the WebSphere Application Server version 2.0 default classpath; Simply add the version 1.x project.
For Java library paths and paths, only the user-specified sections are moved. Do not remove WebSphere Application Server version 2.0
Default library path and path settings; Simply add to the version 1.x project.
L for other properties, they are only migrated if they have a corresponding person defined in the bootstrap.properties.
To use the WebSphere Application Server Manager to manage servlets that already exist in the WEB server before installing the WebSphere Application Server, you must first port these servlets. To migrate existing servlets, move the servlet from their current location to the <as_root> \servlets directory. The WebSphere Application server monitors the directory and automatically re-loads the servlet when the servlet changes. If there are servlets in other directories and do not want to move them to the <as_root> \servlets directory, you can use the "Reload Servlet classpath" field in the Java engine page of the manager interface to specify the remaining directories to monitor. Use the configuration page in the WebSphere application server to reconfigure the previous servlet parameters. See Customizing configuration settings.
websphere--Installation and Configuration
