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.
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.
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. In this mixed environment,
there are restrictions on what you can do with the servers that are
at the older release level:
- You can only create new server definitions on nodes that are running
on the current release level.
- 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 Servers
> Application servers > New.
- Select a node for the application server.
- Enter a name for the application server. The name must
be unique within the node.
- Select a server template for the
new server. The new application server inherits all of
the configuration settings of the template server.
- Select whether you want unique ports
generated for the application server.
By default, this
option is enabled. If you select this option, 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,
ensure that the default port values do not conflict with other servers
on the same physical machine.
- If you use an existing application
server as the template for this server, select whether to map applications
from the existing server to the new server. By default,
this option is disabled.
- Click Apply, and then click Save to
save your changes.
- Click Synchronize changes with
nodes if you want to force node synchronization now and save your
changes to the master repository. If you don't click Synchronize
changes with nodes than the changes will note be applied across
the node until normal node synchronization occurs.
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.