Vijai Gandikota IBM Discovery Support

Transcription

1 Installation and configuration of the IBM HTTP Server and its plugin for IBM WebSphere Application Server V 8.0 for installation with IBM Content Analytics with Enterprise Search 3.0 Vijai Gandikota IBM Discovery Support June 2013

2 Contents Installation and configuration of the IBM HTTP Server and its plugin for IBM WebSphere Application Server V 8.0 for installation with IBM Content Analytics with Enterprise Search Introduction and scope... 1 The web server, plugin, and application server... 1 Advisory for installation on 64-bit Windows, such as Windows 2008 Server... 2 HTTP Server Installation... 2 Creating a Profile for WebSphere Application Server... 7 Configuring the Web Server Plug-ins Configuration Tool Running the configuration batch file for webserver Generating and Propagating the Plugin Configuring Remote web server management Verification... 48

3 Installation and configuration of the IBM HTTP Server and its plugin for IBM WebSphere Application Server V 8.0 for installation with IBM Content Analytics with Enterprise Search 3.0. Introduction and scope The purpose of this document is to describe the process of installing, setting up, and configuring the web server and its plugin to be the front end of an application server so that requests for applications can be sent via the web server to the appropriate application deployed to the application server. The scope of the document is limited to activities necessary and sufficient for the setup of the IBM HTTP Server web server and IBM WebSphere Application Server (WAS) for use with the IBM Content Analytics with Enterprise Search 3.0 (ICAwES 3.0). Because ICAwES 3.0 does not support a remote web server where the HTTP Server is on a separate machine from the WAS server, this document describes only the steps for the local installation where both the HTTP Server and WAS are on the same machine. If the following steps are not done after the installation of WAS, and an installation of ICAwES 3.0 is attempted, the installation results in an error saying that the webserver is not valid. If you proceed with the installation and ignore this error message, the installation will be incorrect and the applications cannot be accessed correctly. The web server, plugin, and application server Applications are installed to the application server with a certain context root and a port number on which they can be accessed. When an application is accessed via a browser, the requests are sent to the HTTP server, which acts as a front end. The HTTP server uses the plugin to route the requests to the appropriate applications. The applications in turn interact with other applications or databases to process or retrieve data and return the responses. The HTTP server routes these responses back to the browsers. To not directly expose the application and its port, an HTTP server and its plugin is needed to route the requests and responses. 1

4 Advisory for installation on 64-bit Windows, such as Windows 2008 Server The following steps describe the procedure done on a Windows 32-bit operating system. If you perform this installation on a Windows 64-bit operating system, the default installation location of the HTTP Server and the WebSphere Application Server is the Program Files (x86) folder. However, this location causes a problem with the plug-in installation due to the parentheses. The HTTP Server documentaion gives the following warning: Restriction: Do not install Web server plug-ins into directories with parentheses () characters in the path name. On Windows Server 2008, for example, the plug-in installation fails if you use the default installation path of C:\Program Files (x86)\ibm\websphere\plugins. To recover from this situation: If you installed the Web server plug-in or IBM HTTP Server into a directory that has parentheses in the path name, complete one of the following actions: Uninstall the product and reinstall it to a directory location that does not have parentheses in the path name. Manually update the following values with the correct path names: a. Update the ServerRoot, AuthUserFile, and Keyfile values in the IHS_install_root\conf\admin.conf file. b. Update the ServerRoot.AfpaLogFile, DocumentRoot, Directory, Alias/icons/, and ScriptAlias values in IHS_install_root\conf\httpd.conf file. c. Update the JAVA_HOME and GSK_HOME values in IHS_install_root\bin\ikeyman.bat file. d. Update the shortcut key values with the correct path name. For example, C:\Documents and Settings\All Users\Start Menu\Programs\IBM HTTP Server V6.1. It is therefore recommended that you install the HTTP server to an alternate location such as C:\IBM to avoid this issue and the manual steps to recover from it. HTTP Server Installation This procedure begins with the screen during WebSphere Application Server installation that gathers the information for the HTTP Server. The installation of WebSphere Application Server 8 is done with the Installation Manager. If you created the repository for both the WebSphere Application Server and also the Supplements, you will also be able to install the HTTP Server and the Plugins. 2

5 The default port for the HTTP server is 80. You can choose to run the HTTP server as a Windows Service with a local system account and the startup type set to Automatic. 3

6 The summary page shows the HTTP Server and other components. Notice the WebSphere Customization toolbox that is installed with the WebSphere Application Server as part of the supplements. Make sure that this toolbox is selected for installation. Allow the Profile Management Tool and the Web Server Plug-ins Configuration Tool to be installed when given the choice. 4

7 Once the installation manager is done installing WebSphere 8 along with the fixes, it will ask you to select the program that you want to start. Select Profile Management Tool to create a profile. Click Finish. This returns the installation manager back to its first screen. 5

8 6

9 Creating a Profile for WebSphere Application Server The Profile Management Tool opens in WebSphere Customization Toolbox 8.0. Click the Create button. 7

10 In the Environment Selection screen, select Application server. 8

11 Click on Next. You can select the Typical profile creation radio button to set up the profile. Here we are also setting up a web server definition, so select the Advanced profile creation option. Click Next. 9

12 Select both options, Deploy the administrative console and Deploy the default application. Click Next. 10

13 Enter a profile name or accept the default value. For ICAwES installation, accept the default name, AppSrv01. Click Next. 11

14 Accept the default values on the Node and Host Names screen. Click Next. 12

15 In the Administrative Security page, select the Enable administrative security checkbox. This is for the WebSphere Application Server administrative user. Enter a user name and password, and confirm the password. This example uses the following values: Username: wasadmin Password: wasadmin Click Next. 13

16 In the Security Certificate (Part 1) screen, select Create a new default personal certificate. Click Next. 14

17 In the Security Certificate (Part 2) screen, accept the default values. Click Next. 15

18 Review the default port assignments. Click Next. 16

19 In the Windows Service Definition screen, select Run the application server process as a Windows service checkbox and select the Log on as a local system account radio button. Select the Startup type to be Automatic. Click Next. 17

20 In the Web Server Definition page, select the Create a Web server definition checkbox. Ensure that the default Web server type, operating system, name, and host name values are all correct. In this example, the web server name is webserver1. Click Next. 18

21 In the Web Server Definition (Part 2) screen, ensure that the default paths are pointing to the actual locations where the HTTP server was installed and where the Plugins folder is located. Click Next. 19

22 After reviewing the Profile Creation Summary, click Create. 20

23 This will start the profile creation process. 21

24 Select the Launch the First steps console checkbox and click Finish. 22

25 This brings you back to the Profile Management Tool and shows the newly created profile, AppSrv01. 23

26 Configuring the Web Server Plug-ins Configuration Tool Click on Start > Programs > IBM WebSphere > WebSphere Customization Toolbox V8.0 > WebSphere Customization Toolbox to open the WebSphere Customization Toolbox. The Web Server Plug-ins Configuration Tool is displayed. 24

27 Notice the Web Server Plug-in Runtime Locations Window and the Web Server Plug-in Configurations window. In the first window, we will add the location of the web server plug-in runtime binaries that we previously installed with WebSphere Application Server. This example uses the following name and location: Name: Main Location: C:\Program Files\IBM\WebSphere\Plugins The Location is the location of the Plugins folder under WebSphere. Click Finish. 25

28 You can see the newly created location item in the Web Server Plug-in Runtime Locations window. Now we will create a Web Server Plug-in Configuration. Click on the Create button. 26

29 Select the Web Server you are using from the list of supported web servers. In this example, we select IBM HTTP Server V8. 27

30 Enter the location of the configuration file and accept the default port 80 for the HTTP server. 28

31 Select the Setup IBM HTTP Server Administration Server checkbox. Accept the default port of 8008 for the HTTP Administration Port and select the Create a user ID for IBM HTTP Server Administration Server authentication checkbox. This example uses the following values: User ID: httpadmin Password: httpadmin Click Next. 29

32 Select the Run IBM HTTP Server Administration Server as a Windows Service checkbox and select the Log on as a local system account radio button. Select the Startup type as Automatic. Click Next. 30

33 Type webserver1 for the unique web server definition name. Click Next. 31

34 On the Configuration Scenario Selection screen, click (Local) Installation location of WebSphere Application Server and enter the path to the AppServer folder. Click Next. 32

35 If the previous step was done correctly, the profile that was created, AppSrv01, will be populated in the Available Profiles list. Select AppSrv01 from the list and click Next. 33

36 Review the Plug-in Configuration Summary and click Configure. 34

37 The configuration process commences. 35

38 Once the configuration process completes, review the results. Click Finish if the configuration completed successfully. 36

39 The Web Server Plug-in Configuration Tool window is now populated with the newly created configuration for webserver1. 37

40 Open the Services window to verify that the HTTP Administration Server and the HTTP Server definitions are both present. Running the configuration batch file for webserver1 You must run the configuration batch file to add webserver1 to the WebSphere Application Server configuration. Open a command prompt and change to the following folder: C:\>cd C:\Program Files\IBM\WebSphere\Plugins\bin\ Verify the batch files in this folder. Look for configurewebserver1.bat. C:\Program Files\IBM\WebSphere\Plugins\bin>dir *.bat Volume in drive C has no label. Volume Serial Number is C03F-BF83 Directory of C:\Program Files\IBM\WebSphere\Plugins\bin 03/28/ :30 PM 3,351 ConfigureApachePlugin.bat 03/28/ :30 PM 4,541 ConfigureDomino7Plugin.bat 03/28/ :30 PM 3,338 ConfigureIHSPlugin.bat 03/28/ :30 PM 3,058 ConfigureIIS6Plugin.bat 03/28/ :30 PM 3,091 ConfigureIIS7Plugin.bat 03/28/ :30 PM 3,922 ConfigureSunOnePlugin.bat 05/18/ :46 AM 2,296 configurewebserver1.bat 03/20/ :35 PM 147 genhistoryreport.bat 03/20/ :35 PM 189 genversionreport.bat 03/20/ :35 PM 690 historyinfo.bat 03/20/ :35 PM 166 ikeyman.bat 03/20/ :35 PM 706 ikeyman_old.bat 03/20/ :39 PM 2,188 managesdk.bat 03/20/ :45 PM 2,780 postinstall.bat 03/28/ :28 PM 926 setupcmdline.bat 05/18/ :46 AM 62 setupgskitlibpath.bat 03/20/ :35 PM 680 versioninfo.bat 03/20/ :25 PM 4,840 ws_ant.bat 18 File(s) 36,971 bytes 0 Dir(s) 27,417,268,224 bytes free 38

41 Copy the configurewebserver1.bat file to the bin folder of WebSphere Application Server: C:\Program Files\IBM\WebSphere\Plugins\bin>copy configurewebserver1.bat "C:\Prog ram Files\IBM\WebSphere\AppServer\bin" 1 file(s) copied. Change to the C:\Program Files\IBM\WebSphere\AppServer\bin folder and run the configurewebserver1 batch script with the parameters as shown below. For your convenience, the usage information is shown prior to the command execution. The output of this execution is also displayed for your reference. Usage: configurewebserver1 [-profilename profile_name] [-user WAS_Admin_userID] [-password WAS_Admin_password] [-ihsadminpassword IHS_Admin_password] [-help ] Where: profilename user password ihsadminpassword is the name of the profile in which web server should be created is the WebSphere Administration userid is the WebSphere Administration password is the password to access the IHS Adminstration server Example: configurewebserver1 -profilename AppSrv01 -user admin -password admin1 C:\Program Files\IBM\WebSphere\AppServer\bin>configurewebserver1 -profilename Ap psrv01 -user wasadmin -password wasadmin Using the profile AppSrv01 Using WebSphere admin userid wasadmin WASX7209I: Connected to process "server1" on node IBM-C4FEB0165E1Node01 using SO AP connector; The type of process is: UnManagedProcess WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: "[webserver1, IHS, C:\\Program Files\\IBM\\HTTPServer, C:\\Program Files\\IBM\\HTTPServer\\conf\\h ttpd.conf, 80, MAP_ALL, C:\\Program Files\\IBM\\WebSphere\\Plugins, unmanaged, I BM-C4FEB0165E1-node, IBM-C4FEB0165E1, windows, 8008, httpadmin, httpadmin, IBM H TTP Server V8.0]" Input parameters: Web server name - webserver1 Web server type - IHS Web server install location - C:\Program Files\IBM\HTTPServer Web server config location - C:\Program Files\IBM\HTTPServer\conf\httpd.conf Web server port - 80 Map Applications - MAP_ALL Plugin install location - C:\Program Files\IBM\WebSphere\Plugins Web server node type - unmanaged Web server node name - IBM-C4FEB0165E1-node Web server host name - ibm-c4feb0165e1 Web server operating system - windows IHS Admin port IHS Admin user ID - httpadmin 39

42 IHS Admin password - httpadmin IHS service name - IBM HTTP Server V8.0 Found node with matching hostname. Using existing node IBM-C4FEB0165E1Node01 Node definition IBM-C4FEB0165E1Node01 already exists. Web server definition for webserver1 already exists. Start computing the plugin properties ID. Plugin properties ID is computed. Start updating the plugin install location. Plugin install location is updated. Start updating the plugin log file location. Plugin log file location is updated. Start updating the RemoteConfigFilename location. Plugin remote config file location is updated. Start updating the RemoteKeyRingFileName location. Plugin remote keyring file location is updated. Start saving the configuration. Configuration save is complete. Computed the list of installed applications. Processing the application DefaultApplication. Get the current target mapping for the application DefaultApplication. Computed the current target mapping for the application DefaultApplication. Start updating the target mappings for the application DefaultApplication. ADMA5075I: Editing of application DefaultApplication started. ADMA5058I: Application and module versions are validated with versions of deploy ment targets. ADMA5005I: The application DefaultApplication is configured in the WebSphere App lication Server repository. ADMA5005I: The application DefaultApplication is configured in the WebSphere App lication Server repository. ADMA5005I: The application DefaultApplication is configured in the WebSphere App lication Server repository. ADMA5005I: The application DefaultApplication is configured in the WebSphere App lication Server repository. ADMA5113I: Activation plan created successfully. ADMA5011I: The cleanup of the temp directory for application DefaultApplication is complete. ADMA5076I: Application DefaultApplication edited successfully. The application o r its web modules may require a restart when a save is performed. Target mapping is updated for the application DefaultApplication. Processing the application ivtapp. Get the current target mapping for the application ivtapp. Computed the current target mapping for the application ivtapp. Start updating the target mappings for the application ivtapp. ADMA5075I: Editing of application ivtapp started. ADMA5058I: Application and module versions are validated with versions of deploy ment targets. ADMA5005I: The application ivtapp is configured in the WebSphere Application Ser ver repository. ADMA5005I: The application ivtapp is configured in the WebSphere Application Ser ver repository. ADMA5005I: The application ivtapp is configured in the WebSphere Application Ser ver repository. 40

43 ADMA5005I: The application ivtapp is configured in the WebSphere Application Ser ver repository. ADMA5113I: Activation plan created successfully. ADMA5011I: The cleanup of the temp directory for application ivtapp is complete. ADMA5076I: Application ivtapp edited successfully. The application or its web mo dules may require a restart when a save is performed. Target mapping is updated for the application ivtapp. Processing the application query. Get the current target mapping for the application query. Computed the current target mapping for the application query. Start updating the target mappings for the application query. ADMA5075I: Editing of application query started. ADMA5058I: Application and module versions are validated with versions of deploy ment targets. ADMA5005I: The application query is configured in the WebSphere Application Serv er repository. ADMA5005I: The application query is configured in the WebSphere Application Serv er repository. ADMA5005I: The application query is configured in the WebSphere Application Serv er repository. ADMA5005I: The application query is configured in the WebSphere Application Serv er repository. ADMA5113I: Activation plan created successfully. ADMA5011I: The cleanup of the temp directory for application query is complete. ADMA5076I: Application query edited successfully. The application or its web mod ules may require a restart when a save is performed. Target mapping is updated for the application query. Start saving the configuration. Configuration save is complete. C:\Program Files\IBM\WebSphere\AppServer\bin> Once this process completes, we are ready to log in to WebSphere Application Server to complete the final steps of the Web Server Configuration. 41

44 Generating and Propagating the Plugin Ensure that server1 of WebSphere Application Server is started. Log in to the WebSphere Integrated Solutions Console. 42

45 Click on Servers > Server Types > Web servers. The web server definition for webserver1 should be displayed. However, you cannot start it because it cannot yet communicate with the HTTP Administration Server. 43

46 Click the checkbox next to webserver1 to select it and then click Generate Plug-in. Then click Propagate Plug-in. 44

47 Click webserver1. 45

48 Review its configuration. Configuring Remote web server management Click Remote Web server management. Ensure that the port is the same as the number you entered or accepted for the HTTP Administration Server, and enter the username and password for the HTTP administrative ID. 46

49 Click OK and then click Save. Click the checkbox next to webserver1 and click Start. If all the steps were correctly and successfully done, the web server is started. 47

50 Verification To verify that the plugin is properly configured and propagated, enter to get the snoop servlet from the WebSphere Application Server. For more information on this document please contact Vijai Gandikota via at 48