During the installation process, the product creates a
default application server, named server1. Most installations require
several application servers to handle the application serving needs
of their production environment. You can use the command-line tool
or the administrative console to create additional applications servers.
Before you begin
Determine if you want to use the application
server that you are creating as part of a cluster. If this application
server is going to be part of a cluster, you must use the Create a
new cluster wizard instead of the Create a new application server
wizard to create this application server.
About this task
To create
a new application server, you can either use the createApplicationServer,
createWebServer, or createGenericServer wsadmin command, or you can
use the administrative console.
You can also create a new application server when
you add a cluster member to a server cluster.
If you are migrating from a previous
version of the product, then you can upgrade a portion of the nodes
in a cell, while leaving others at the previous product level. This
means that, for a period of time, you might be managing servers that
are running at two different release levels in the same cell. However,
when you create a new server definition, you must use a server configuration
template, and that template must be created from a server instance
that matches the version of the node on which you are creating a server.
There
are no restrictions on what you can do with the servers running on
the current release level.
You
can use the administrative console to perform the following steps
to create a new application server:
Procedure
- In the administrative console, click either Servers
> Application servers > New, or Servers > Clusters.
The Servers > Application servers > New path
starts the Create a new application server wizard. The Servers
> Clusters > New path starts the Create a new cluster wizard.
Only use this path if the application server is part of a cluster.
The
Servers > Clusters path brings you
to the administrative console page where you can complete one of the
following actions:
- Click New if this application server is the first member
of a new cluster, or
- Click on the name of an existing cluster to make this application
server a new member of that cluster.
Both actions start the Create a new cluster wizard.
- Select a node for the application server.
- Enter a name for the application server. The name must
be unique within the node.
- Click Next.
- Select a server template for the new server.
You can use a default application server template for your
new server or you can use the template that is optimized for development
uses. The new application server inherits all of the configuration
settings of the template server.
- Click Next, and then select Generate
unique HTTP ports if you want the wizard to generate unique ports
for the application server.
By default, this option
is enabled. If you select this option, then you might need to update
the alias list for the virtual host that you plan to use with this
server to contain these new port values. If you deselect this option,
then ensure that the default port values do not conflict with other
servers on the same physical machine.
- Click Next. Review the settings
for the new server. If you want to change any of the settings,
click Previous until you return to a page where you can change
that setting. If you do not want to make any changes, click Finish.
- Click Review, select Synchronize
changes with Nodes, and then click Save to save any configuration
changes that you made.
Results
The
new application server is displayed in the list of servers on the
administrative console Application servers page.
What to do next
This
newly created application server is configured with default settings
that are not displayed when you run the Create New Application Server
wizard.
You can:
- Click Servers > Application servers in the administrative
console, and then click the name of this application server to view
all of the configuration settings for this application server. You
can then use this page to change some of the configuration settings
for this server.
- Set the client.encoding.override Java Virtual Machine (JVM) argument
to UTF-8 if you need to use multiple language encoding support in
the administrative console.