Configuring a Web server for a non-default profile

This topic describes installing a Web server plug-in and configuring an application server that is not the default profile.

 

Before you begin

When multiple profiles exist, the plug-ins installer configures only the default profile.

If you intend to create a Web server definition for an application server that is not the default profile, force the Plug-ins installation wizard to configure a profile that is not the default profile.

If you are planning to add the application server node into a deployment manager cell but have not done so yet, start the deployment manager and federate the node before installing the plug-in. You cannot add an application server with a Web server definition into the deployment manager cell.

This procedure assumes that you have installed the Web server on one machine and the WAS product on a separate machine. This procedure also works when the Web server and the application server profile are on the same machine. In such a case, select the Remote installation type when installing the plug-ins so that the Plug-ins installation wizard creates the configuration script for the application server.

 

About this task

This procedure describes how to create a Web server definition for an application server that is not the default profile. This procedure describes selecting a remote installation scenario and issuing a command for the configuration script that points the command to a profile that you select.

The ordinary behavior of the configuration script is to work on the default profile on the machine where the script runs. This procedure describes how to redirect the script to configure a profile that is not the default.

 

Procedure

  1. Log on to the operating system.

    Log on as root on an operating system such as AIX or Linux, or as a member of the administrator group on a Windows system.

    In addition, select a umask that would allow the owner to read/write to the files, and allow others to access them according to the prevailing system policy. For root, a umask of 022 is recommended. For non-root users a umask of 002 or 022 could be used, depending on whether or not the users share the group. To verify the umask setting, issue the following command

    umask
    
    To set the umask setting to 022, issue the following command

    umask 022
    

    When installing on a Windows system, a Windows service is automatically created to autostart the application server if your installer user account has the following advanced user rights:

    • Act as part of the operating system

    • Log on as a service

    For example, on some Windows systems, click Administrative Tools > Local Security Policy > User Rights Assignments to set the advanced options. See your Windows documentation for more information.

    The installation wizard grants your Windows user ID the advanced user rights, if the user ID belongs to the administrator group. The silent installation does not grant these rights. If you create a new user ID on a Windows platform to perform a silent installation, restart the system to activate the proper authorizations for the user ID before you can perform a successful silent installation.

    If you plan to run the application server as a Windows service, do not install from a user ID that contains spaces. A user ID with spaces cannot be validated. Such a user ID is not allowed to continue the installation. To work around this problem, install with a user ID that does not contain spaces.

  2. Launch the Plug-ins installation wizard on the machine with the Web server.

    Select the Plug-ins installation wizard from the launchpad or change directories to the plugin directory on the product disc or in the downloaded installation image and issue the install command.

  3. Clear the check box for the roadmap or select the check box to view the roadmap, then click Next.

    If you are unsure of which installation scenario to follow, display the roadmap instead. Print and keep the roadmap as a handy overview of the installation steps.

    Press Ctrl-P to print the roadmap if the Web browser navigation controls and the menu bar are not present on the browser window that displays the Plug-ins roadmap. Press Ctrl-W to close the browser window if the navigation controls and the menu bar do not display. Or close the browser window with the window control in the title bar.

  4. Read the license agreement and accept the agreement it if you agree to its terms. Click Next when you are finished.

  5. If your system does not pass the prerequisites check, stop the installation, correct any problems, and restart the installation. If your system passes the prerequisites check, click Next.

    Look for the appropriate log file for information about missing prerequisites. If you stop the installation, see the temporaryPluginInstallLog.txt file in the temporary directory of the user who installed the plug-ins. For example, the /tmp/temporaryPluginInstallLog.txt file might exist if the root user installed the plug-ins on an operating system such as AIX or Linux.

    See Troubleshooting installation for more information about log files.

  6. Select the type of Web server that you are configuring and click Next.

    The Plug-ins installation wizard panel prompts you to identify the Web servers to configure. Actually you can select only one Web server each time you run the Plug-ins installation wizard.

    Stop any Web server while you are configuring it. A step later in the procedure directs you to start the Web server as you begin the snoop servlet test.

    If you select the Web server identification option labeled None, the Web server installs the binary plug-ins but does not configure the Web server.

  7. Select Web server machine (remote) and click Next.

  8. Accept the default location for the installation root directory for the plug-ins. Click Next.

    You can type another new directory or click Browse to select an empty directory. The fully qualified path identifies the plug-ins installation root directory.

    The default location is shown in Directory conventions .

    A possibility exists that the Web server might run on a platform that WAS does not support.

  9. Click Browse to select the configuration file for your Web server, verify that the Web server port is correct, and then click Next when you are finished.

    Select the file and not just the directory of the file. Some Web servers have two configuration files and require you to browse for each file.

    The following list shows configuration files for supported Web servers:

    Apache HTTP Server

    apache_root/config/httpd.conf

    Domino Web Server

    names.nsf and Notes.jar

    The wizard prompts for the notes.jar file. The actual name is Notes.jar.

    The Plug-ins installation wizard verifies that the files exist but the wizard does not validate either file.

    IBM HTTP Server

    IHS_root/conf/httpd.conf

    Microsoft Internet Information Services (IIS)

    The Plug-ins installation wizard can determine the correct files to edit.

    Sun ONE Web Server 6.0 or Sun Java System Web Server, V6.1

    obj.conf and magnus.conf

    The wizard displays a naming panel for the nickname of the Web server definition.

  10. Specify a nickname for the Web server. Click Next when you are finished.

    The wizard uses the value to name configuration folders in the plug-ins installation root directory. The wizard also uses the name in the configuration script for the application server to name the Web server definition.

    If the application server profile already has a Web server definition, delete the Web server definition before continuing. Use the following commands to delete the Web server definition

    $AdminTask deleteServer { -serverName webserver1 -nodeName webserver1_node }
    $AdminTask removeUnmanagedNode { -nodeName webserver1_node }
    $AdminConfig save
    
    

  11. Type a value for the location of the plugin-cfg.xml file.

    For a federated node, the deployment manager creates the file in the app_server_root/profiles/Dmgr01/config/cells/ cell /nodes/ app_server_node /servers/ web_servername /plugin-cfg.xml file path.

    For a stand-alone application server node, the application server creates the file in the profile_root /config/cells/ cell /nodes/ web_servername_node/servers/ web_servername /plugin-cfg.xml file path.

    Specify the location in the field so that the Web server can access the file when the Web server and the application server are on the same machine. Accept the default value if the Web server and the application server are on separate machines.

    The location of the plugin-cfg.xml file is used in the Web server configuration file. If you cannot enter the location correctly at this point, you can edit the Web server configuration file manually to correct the location so that the location points to the plugin-cfg.xml file in the non-default application server profile. On a remote installation, the default location is within the plug-ins installation root directory. Propagation copies the current file from the application server machine to the Web server machine.

  12. Identify the host name or IP address of the application server machine, then click Next.

  13. Examine the summary panel. Click Next when you are finished.

    The panel notifies you that you have manual steps to perform to complete the installation and configuration. The type of Web server, the nickname of the Web server, and the location of the plugin-cfg.xml file displays on the panel.

    The Plug-ins installation wizard creates the configureweb_servername script in the plugins_root/bin/ directory.

    The Plug-ins installation wizard also creates a default plugin-cfg.xml file in the plugins_root/config/web_servername directory.

  14. Click Next on the pre-installation summary panel to begin the installation or click Back to change any characteristics of the installation.

    The panel specifies the plug-ins installation root directory, the Web server plug-ins feature, and the disc size of the code that installs when you click Next.

  15. After the wizard installs the code and creates the uninstaller program, examine the post-installation summary panel. Click Next when you are finished to display the Plug-ins installation roadmap.

    The Plug-ins installation wizard installs the binary plug-in module. On a Linux system, for example, the installation creates the plugins_root directory. The plugins_root/config/web_servername directory contains the plugin-cfg.xml file.

    The wizard displays the name and location of the configuration script and the plugin-cfg.xml file. The wizard also displays the type of Web server that is configured and the nickname of the Web server.

    If a problem occurs and the installation is unsuccessful, examine the logs in the plugins_root/logs directory. Correct any problems and reinstall.

  16. Close the road map and click Finish to exit the wizard.

    Log files from the installation are in the plugins_root/logs/install directory.

  17. Copy the configureweb_servername.sh script on systems such as AIX or Linux, the configureweb_servername script on i5/OS, or the configureweb_servername.bat script on Windows systems to the app_server_root/bin directory on the application server machine.

    For example, on a Linux system with an IBM HTTP Server named webserver1 in the default location, copy /opt/IBM/WebServer/Plugins/bin/configurewebserver1.sh to the /opt/IBM/WebSphere/AppServer/bin directory on the application server machine.

    If one platform is a system such as AIX or Linux and the other is a Windows platform, copy the script from the crossPlatformScripts directory. For example:

  18. Compensate for file encoding differences to prevent script failure.

    The content of the configureweb_servername.bat script or the configureweb_servername.sh script can be corrupt if the default file encoding of the two machines differs. This scenario is possible when one machine is set up for a double-byte character set (DBCS) locale and the other machine is not.

    Determine the file encoding and use one of the following procedures to circumvent the failure. To determine the default file encoding, run the appropriate command.

    • Run the following command on a system such as AIX or Linux

      locale
      

    • Run the following command on a Windows machine

      CHCP
      

    Use the result of the command on each machine as the value of the web_server_machine_encoding variable and the application_server_machine_encoding variable in one of the following procedures.

    Procedures for compensating for encoding differences

    Suppose that the Web server is running on a Linux machine and Network Deployment is running on a Windows machine.

    Web server running on a system such as AIX or Linux

    Run the following command on the system to encode the script file that configures the Web server definition, before you FTP the file to the Windows machine in binary mode

    iconv -f web_server_machine_encoding \
       -t application_server_machine_encoding \
       configureweb_servername.bat 
    
    Omit the continuation characters (\) if you enter the command on one line. Important: The name of the Web server (nick name) is used in the name of the script file. The name cannot contain characters from a double-byte character set (DBCS) if you intend to set up IBM HTTP Server for automatic propagation.

    Suppose that the Web server is running on a Windows machine and Network Deployment is running on a machine with a system such as AIX or Linux.

    Web server running on a Windows machine

    Run the following command on the machine with a system such as AIX or Linux to encode the script file that configures the Web server definition, after you FTP the file in binary mode

    iconv -f web_server_machine_encoding \
       -t application_server_machine_encoding \
       configureweb_servername.sh 
    
    Omit the continuation characters (\) if you enter the command on one line.

    If the conversion mapping is not supported by the iconv command on your system, copy the contents of the Web server configuration script to a clip board and paste it onto the machine where the application server is running.

  19. Copy the configureweb_servername.sh script on systems such as AIX or Linux, the configureweb_servername.bat script on Windows systems, or the configureweb_servername script on i5/OS from Machine B to the app_server_root /bin directory on Machine A.

    Use the startServer command to start the application server, for example:

  20. Start the nodeagent process if the application server is federated.

    Use the startNode command, for example:

  21. Start the deployment manager if the application server is federated.

    Use the startManager command, for example:

  22. Stop the Web server if it is running.

  23. Edit the script using a flat file editor, such as Kate on SLES.

    1. Insert the -profilename parameter into the command string within the script:

      wsadmin -profilename profile_of_the_non-default_profile -f configureWebserverDefinition.jacl ...
      
      

    2. Save the script and close the editor.

  24. Run the script on the application server machine to create a Web server definition for the non-default profile. The profile name should be passed as a parameter when the script is executed.

    Open a command window to run the script that you copied to Machine A.

    As soon as the Web server definition is created, the application server creates a plugin-cfg.xml file for the Web server. For example, the file on a Linux system might have the following file path: profile_root/config/cells/cellname/nodes/webserver1_node/servers/webserver1/plugin-cfg.xml

  25. From the administrative console of the deployment manager, click System administration > Save Changes to Master Repository > Synchronize changes with Nodes > Save.

  26. Domino Web server only: Set the WAS_PLUGIN_CONFIG_FILE environment variable.

    On platforms such as AIX or Linux, sourcing a script to the parent shell allows child processes to inherit the exported variables. On Windows systems, run the script as you would run any other command. Sourcing is automatic on Windows systems.

    1. Open a command window.

    2. Change directories to the plug-ins installation root directory.

    3. Issue the appropriate command for the plugins_root/bin/setupPluginCfg.sh script:

      • . plugins_root/bin/setupPluginCfg.sh (Notice the space between the period and the installation root directory.)

      • source plugins_root/bin/setupPluginCfg.sh

    The script is also in the lotus_root/notesdata directory on operating systems such as AIX or Linux.

    Issue the appropriate command for the script before starting the Domino Web Server.

  27. Start the Snoop servlet to verify the ability of the Web server to retrieve an application from the Application Server.

    Test your environment by starting your Application Server, your Web server, and using the snoop servlet with an IP address.

    1. Start the Application Server. In a Network Deployment environment, the Snoop servlet is available in the cell only if you included the DefaultApplication when adding the Application Server to the cell. The -includeapps option for the addNode command migrates the DefaultApplication to the cell. If the application is not present, skip this step.

      Change directories to the profile_root/bin directory and run the startServer command:

      • ./startServer.sh server1

      • startServer server1

    2. Start the IBM HTTP Server or the Web server that you are using.

      Use a command window to change the directory to the IBM HTTP Server installed image, or to the installed image of your Web server. Issue the appropriate command to start the Web server, such as these commands for IBM HTTP Server:

      To start the IBM HTTP Server from the command line:

      Access the apache and apachectl commands in the IBMHttpServer/bin directory.

      • ./apachectl start

      • apache

    3. Point your browser to http://localhost:9080/snoop to test the internal HTTP transport provided by the Application Server. Point your browser to http://Host_name_of_Web_server_machine/snoop to test the Web server plug-in.

      The HTTP Transport port is 9080 by default and must be unique for every profile. The port is associated with a virtual host named default_host, which is configured to host the installed DefaultApplication and any installed Samples. The snoop servlet is part of the DefaultApplication. Change the port to match your actual HTTP Transport port.

    4. Verify that snoop is running.

      Either Web address should display the Snoop Servlet - Request/Client Information page.

    5. Remote IBM HTTP Server only:

      Verify that the automatic propagation function can work on a remote IBM HTTP Server by using the following steps. This procedure is not necessary for local Web servers.

      1. Create a user=adminUser, password=adminPassword in the IHS_root /conf/admin.passwd file. For example: c:\ws\ihs60\bin\htpasswd -cb c:\ws\ihs60\conf\admin.passwd adminUser adminPassword

      2. Use the administrative console of the deployment manager or the Application Server to enter the User ID and password information that you created for the administrative user of IBM HTTP Server. Go to Servers > Web server > Web_server_definition > Remote Web server administration. Set the following values: admin Port=8008, User Id=adminUser, Password=adminPassword.

      3. Set the correct read/write permissions for the httpd.conf file and the plugin-cfg.xml file. See the IHS_root /logs/admin_error.log file for more information.

      Automatic propagation of the plug-in configuration file requires the IBM HTTP administrative server to be up and running. If you are managing an IBM HTTP Server using the WAS administrative console, the following error might display

      "Could not connect to IHS Administration server error"
      

      Perform the following procedure to correct the error:

      1. Verify that the IBM HTTP Server administration server is running.

      2. Verify that the Web server host name and the port that is defined in the WebSphere Application Server administrative console matches the IBM HTTP Server administration host name and port.

      3. Verify that the fire wall is not preventing you from accessing the IBM HTTP Server administration server from the WAS administrative console.

      4. Verify that the user ID and password that is specified in the WAS administrative console under remote managed, is created in the admin.passwd file, using the htpasswd command.

      5. If you are trying to connect securely, verify that you export the IBM HTTP Server administration server keydb personal certificate into the WAS key database as a signer certificate. This key database is specified by the com.ibm.ssl.trustStore directive in the sas.client.props file in the profile where your administrative console is running. This consideration is primarily for self-signed certificates.

      6. If you still have problems, check the IBM HTTP Server admin_error.log file and the WAS logs (trace.log file) to determine the cause of the problem.

 

Results

This procedure results in the installation of the Web server plug-ins for WAS on a Web server machine. After modification, the resulting script creates a Web server definition for an application server that is not the default profile. The Plug-ins installation wizard also configures the Web server to support the application server.

If you can see the Snoop servlet through the Web server, you have successfully configured the Web server and the application server.

The installation of the binary plug-in modules results in the creation of the Plugins directory and several subdirectories. The following directories are among those created on a Linux system, for example:

 

What to do next

After configuring a Web server and creating a Web server definition, you can deploy applications and serve them through the Web server. See Fast paths for WebSphere Application Server to get started deploying applications.


Related tasks
Installing Web server plug-ins Editing Web server configuration files

 



 

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.
AIX is a trademark of the IBM Corporation in the United States, other countries, or both.