How to install WebSphere Application Server

IBM WebSphere Application Server provides the ability to build from e-commerce, publishing to management. Its standard version provides open and standard platforms. WebSphere Application Server includes a servlet run engine, a high-performance database connection, providing pre-connection, session, and status management application services, and WebSphere also supports the XML document structure. In addition, WebSphere also supports JSP version 1.0, version 2.1 of Servlet. There is a high-speed database buffer joint pool (support DB2 Universal Database, Oracle, Microsoft SQL Server and other databases.) WebSphere can be installed on the NT, 95/98 operating system platform, which describes how to install and configure WebSphere App Servers on Windows NT. Installing WebSphere must require 128 megaby memory, if it is 256 trillion. The operating system requires Windows NT (Pack 3). Before installation, there must be a web server, which can be one: 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 version Domino version 5.0 Windows NT version of Lotus Domino Go Webserver version 4.6.2.5 Windows NT version of Microsoft Internet Information Server version 3.x and version 4.0 Windows NT version of the Netscape Enterprise Server version 3.01 and version 3.51 Windows NT version (recommended version 3.5.1) Netscape FastTrack Server version 3.01 The Windows NT version requires Java Development Components (JDK). Here we recommend using JDK1.1.6 that is provided with the WebSphere application server. The Java Servlet API is also required, and the WebSphere application server includes JSDK version 2.0 or higher. Of course, web browsers and AppletViewer are also required, or support JDK1.1 browsers. For example: Netscape Navigator 4.06 or 4.0.7, or a Microsoft Internet Explorer 4.01 or higher with amendment package, or Sun HotJava 1.1 or higher. Some old browsers do not correctly process text that enabled local language support. If you see a foreign character on the user interface, such as "Senable", instead of "enable", you can correct it by upgrading the browser. Step 1: Install the web server: If you intend to install the IBM HTTP server, you must install it before installing the WebSphere application server. WebSphere Application Server Installing CDs with IBM HTTP Server. Installing the WebSphere Application Server changes the web server httpd.conf file. However, if the web server is installed after installing the WebSphere application server, it will not be changed, and the WebSphere application server is not able to run correctly. After installing the IBM HTTP server, you need some configuration to enable SSL support. How to configure, see the IBM HTTP server document to obtain the instruction information.

For scheduled to install other web servers (such as Apache Server), please install it before installing the WebSphere application server. Step 2: Before installation: Before installation, if there is an old version of WebSphere in the system, you must uninstall the old version first. Then install a new version. Before uninstall, you should back up the WebSphere Application Server version 1.x file. (1) File backup From Windows NT uninstall the previous version of the WebSphere application server, make sure that the file to be transplanted or saved. Installing WebSphere Application Server Version 2.0 Displayed Graphical User Interface Backup WebSphere Application Server Directory, including classes, domains, servlets, properties files, where properties files include servlet.properties, admin_port.properties, rules.properties, JVM .properties, aliases.properties, connmgr.properties, userprofile.properties. If the file resides in these four directories (for example, if you create your own directory in the WebSphere Application Server installation), install the WebSphere Application Server version 2.0. Previous backup files outside the WebSphere application server installation. (2) Uninstall the previous version for Windows NT, use the Add / Delete option in the Start -> Control Panel, or from the Start -> Program -> IBM WebSphere -> WebSphere Application Server Version 1.x Uninstall. Note: When a version of the WebSphere application server is installed, it copies the web site configuration file as a backup file and modifies the original configuration file. This has become an active configuration file when using a web server. When unloading the WebSphere application server, the previous configuration file will not be restored, it is still a backup file. In order to make these settings again, they must convert them to the active web server profile from the backup file. In addition, the ClassPath needs to be cleared. Remove this information before installing version 2.0. For web servers using Go Webserver on Windows NT, you can automatically uninstall the Java support on Go Webserver when installing a WebSphere application server. Please check the relevant documents. Step 3: Install WebSphere Server: Before you are about to install WebSphere Application Server, make sure you have already: (1) Backup All files that are not automatically backed up through the installer (2) Install the web server you plan to use. The web server must be installed before the WebSphere application server is installed. (3) Make sure the web server has stopped running before installing. Note: During the installation of the WebSphere application server, if you specify the IBM HTTP server or Apache Server, you will be prompted to confirm the location of the web server httpd.conf file. On Windows NT, insert the WebSphere application server to install the disc, turn to subdites named after Windows NT operating system, run the executable installer (Setup.exe). A series of panels will guide you through the installation. Configuring WebSphere Applications The following describes how to configure WebSphere application servers to make it and its components to work together. After completing these tasks, the WebSphere Application Server can run almost all functions over the default configuration.

(1) Configuring Apache Server If you use Apache Server as a web server, add this line in the httpd.conf file: addModule MOD_APP_SERVER.C. (2) Use the database. To ensure the connection of the WebSphere application server and the relational database (such as Oracle or DB2): add the .zip file to the java.classpath attribute in the file /properties/bootstrap.properties. You can also specify the file using the Java engine page of the Manager interface of the WebSphere application server. Similarly, make sure Java.ClassPath contains a valid driver for database connections. (3) Run mode OSE.Mode Properties is used to control the WebSphere application server as part of the web server (within the process), or run in standalone mode (outside). This attribute is in the /properties/bootstrap.properties file. OSE.Mode default is OUT. Apache Server or IBM HTTP server requires setting an OSE.Mode property to be OUT, that is, the WebSphere application server must run in standalone mode. For other web servers, OSE.MODE can be used as IN and run a WebSphere application server as part of the web server. But usually don't do this. If necessary, it is necessary to reset OSE.Mode means that the value of OSE.Mode is OUT. For example, if Netscape Enterprise Server (OSE.MODE = IN) running as part of Web Server is converted to the IBM HTTP server (requiring OSE.Mode = OUT), don't forget to put OSE.Mode properties before running the IBM HTTP server. Change to OUT. In addition to manually editing the bootstrap.properties file, the Java engine page of the manager interface provides a simple way to lock the OSE.Mode property value. The Java engine page provides a radio button that can be used to indicate part of the web server (OSE.Mode = in) or running a WebSphere application server with independent mode (OSE.Mode = OUT). Running a WebSphere application server as part of the web server provides high performance for servlets and other applications, but is poor security. Run the WebSphere application server as part of the web server, allowing the WebSphere application server to automatically stop when turning off the web server. Running a WebSphere application server in stand-alone mode requires other steps. Start and stop the WebSphere Application Server When starting a web server, the WebSphere application server will start automatically. If the WebSphere application server is run as part of the web server, the WebSphere application server will automatically stop when you turn off the web server. If you run in a stand-alone mode, the WebSphere application server will not stop automatically. When running a WebSphere application server outside Windows NT, stop the WebSphere Servlet service to stop the WebSphere application server after the Web Server is running outside the WINDOWS NT. The method is: Select the WebSphere Servlet service from the start -> Settings -> Control Panel -> and press the Stop button.