InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.3: Administering application servers >
6.6.3.1: Administering application servers with the Java administrative console >
6.6.3.1.1: Configuring new application servers

6.6.3.1.1: Configuring new application servers

The product offers several ways to configure new application servers:

  • By clicking Console -> Tasks -> Create Application Server from the console menu bar.
  • By clicking Create Application Server from the drop-down list on the Wizards toolbar button.
  • Using menus on resources in the Topology and Type trees (see Related information)

The first two methods lead to the Create Application Server task wizard, for which detailed help is provided here.

  1. Follow the wizard instructions. On the first page, specify whether the application server will support Web applications.

    If you do not select Web applications, the wizard will lead you through only the configuration of the application server.

  2. Click Next to proceed. Specify application server properties. Only the name by which you will administer the server is required.

  3. Click Next to proceed. Specify whether to start the server automatically after you finish this configuration wizard.

  4. Click Next to proceed. Specify the node (physical machine) on which the application server will reside.

  5. Click Next to proceed to the virtual host page of the wizard. Specify the virtual host for this application server's files, or specify a new virtual host to be configured.

    View virtual host properties help

  6. If you specified that this application server will support servlets, you will now begin specifying configuration information about the servlet support.

    Click "Next" to proceed through the wizard pages as you specify a servlet engine and other servlet engine properties that are optional because they will use the default values if you do not customize them.

    View servlet engine properties help

    View servlet properties help

  7. Click Next to proceed to Web application properties.
    • Specify a name by which to administer the Web application.

    • Optionally, describe the Web application.

    • Specify the virtual host part of the Web application's served path. That is, what host name (or its aliases) will users specify when they access the Web application from a Web browser?

    • Specify the Web Path for the Web application. That is, what should users type in after the host name when requesting this Web application?

      For example, if you would like users to type

      http://default_host_alias/webapp/mywebapp
      to access the application (where default_host_alias is any valid alias for the default virtual host), specify:
      • Virtual Host = "default_host"

      • Web Application Web Path= "/webapp/mywebapp"

    • Specify the document root for the Web application. This is the fully qualified path to where the HTML and JSP files for the Web application will be found.

    • Specify the classpath, adding either a directory for servlets or specifying servlets individually. Also specify any other resources the Web application needs to know about in order to operate correctly.

      Note that both the document root and the classpath contain default values. You can accept the default values and then move your files there after finishing the task. Alternatively, you can change the default values to point to your files in their present locations, or a location to which you plan to move them.

    • Specify other Web application properties or accept the default values for them.

    • Enable the file servlet if you plan to drop servlets "anonymously" into a specified servlet directory in the Web application classpath.

      Alternatively, you can configure each servlet so that it is known explicitly by name in the administrative domain.

    • Specify to serve servlets by classname if you plan to drop servlets into a servlet directory without configuring them explicitly in the domain.

    • Specify the JavaServer Pages (JSP) specification level to use. If you anticipate adding JSP files to the Web application later, make sure you select the anticipated JSP level. If your Web application will never contain JSP files, this value does not matter.

    View Web application properties help

  8. Click Finished.

Go to previous article: Administering application servers with the Java administrative console Go to next article: Starting and stopping application servers with the Java administrative console

 

 
Go to previous article: Administering application servers with the Java administrative console Go to next article: Starting and stopping application servers with the Java administrative console