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.
To
create a new application server, you can either use the Profile Management
tool, 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.
Avoid trouble: If you are using a global resource serialization
(GRS) ring to attach one or more monoplexes to a sysplex environment,
the cell name of any servers running in any of the monoplexes must
be unique within the entire GRS environment. This requirement means
that the cell name of a server running in any of the monoplexes:
- Must be different than the cell name of any servers running in
the sysplex
- Must be different than the cell name of any servers running in
another monoplex that is attached to the sysplex
If you have servers with duplicate cell names within the GRS
environment, WebSphere Application Server cannot differentiate between
the sysplex cell and the monoplex cell, and treats both servers as
part of the same cell, This inaccurate cell association typically
causes unpredictable processing results.
gotcha
You
can use the administrative console to perform the following steps
to create a new application server:
- 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.
If you select
the defaultZOS template, which is the only one that is listed unless
you used the createApplicationServerTemplate command for the
AdminTask object to create additional templates, the first cluster
member uses the default port assignments for the z/OS platform. If
some of these ports are already defined for use elsewhere in your
z/OS system, your newly created cluster member might not start, might
function incorrectly, or might generate unexpected error messages.
Therefore, you must resolve any port conflicts before you start this
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.
Optional: Click Next and
specify a short name for the server. The short name
is also used as the JOBNAME for the server. If you do not specify
a value for the short name field, the short name defaults to BBOSnnn,
where nnn is the first free number in the cell that can be used to
create a unique short name. For example, if default short names are
already assigned to two other servers in the cell, the short name
BBOS003 will be assigned to this server if you do not specify a short
name when you create this server
Important: Make sure that you set up a RACF SERVER class profile
that includes this short name.
Optional: Specify
a generic short name for the server. The generic short
name for the server becomes either the cluster transition name, if
you are creating an unclustered server, or the cluster short name,
if you are creating a clustered server. If you do not specify a value
for the generic short name field, the generic short name defaults
to BBOCnnn, where nnn is the first free number in the cell that can
be used to create a unique generic short name. For example, if default
generic short names are already assigned to three other servers in
the cell, the generic short name BBOC004 is assigned to this server
if you do not specify a generic short name when you create this server.
Important: Make sure that you set up a RACF
SERVER class profile that includes this generic short name.
- 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.
Optional: Run
the updateZOSStartArgs script to enable an application server to use
the z/OS reusable ASID function, if it is not already enabled for
the node that is associated with this application server. This
function enables an application server to reuse all ASIDs, including
those that are associated with cross-process services.
Avoid trouble: Before running this script, verify
that you are running on z/OS Version 1.9 or higher, and that the reuse
ASID function is enabled during the z/OS startup process. If the function
is not enabled on z/OS, running this script has no affect on how ASIDs
are handled.
gotcha
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.
For example, if you
are going to be running a high volume Java application on this application
server, you might want to select the Run in 64 bit JVM mode field.
Selecting this field lets you dedicate more central storage to the
application server than you can if you use the default 31-bit mode
setting.
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.
Use server custom properties
to modify the timer settings if you need to change the default timer
settings for certain operations.
- 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.