Create appservers
During the installation process, WAS creates a default appserver, named server1. Use the command-line tool or the admin console to create additional appservers.
If the appserver is going to be part of a cluster, use the Create a new cluster wizard instead of the Create a new appserver.
To create a new appserver not part of a cluster, we can use...
If migrating from a previous version of WAS ND, we 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, we might be managing servers that are running at two different release levels in the same cell. However, when creating a new server definition, use a server configuration template, and that template must be created from a server instance that matches the version of the node for which we are creating the server.
There are no restrictions on what we can do with the servers running on the more current release level.
Complete the following steps to use the admin console to create a new appserver not part of a cluster.
- In the admin console, click...
Servers | Server Types | WebSphere application servers | New
The Create a new appserver wizard starts.
- Select a node for the appserver.
- Enter a name for the appserver. The name must be unique within the node.
- Click Next.
- Select a server template for the new server.
We can use a default appserver template for the new server, or we can use the template that is optimized for development uses. The new appserver inherits all of the settings of the template server.
- Click Next.
By default, this option is enabled.
If we select this option, then we 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 we deselect this option, then verify the default port values do not conflict with other servers on the same physical machine.
- Select Generate unique HTTP ports if we want the wizard to generate unique ports for the appserver.
- Click Next. Review the settings for the new server.
- To change any of the settings, click Previous until you return to a page where we can change that setting.
- Click Finish when you do not want to make any additional changes.
- Click Review, select Synchronize changes with nodes, and then click Save to save the changes.
Results
The new appserver is in the list of servers on the admin console Application servers page.
What to do next
This newly created appserver is configured with default settings that are not displayed when you run the Create New Application Server wizard.
We can:
- In the admin console, click...
Servers | Server Types | WebSphere application servers | appserver
...to view all of the configuration settings for this appserver. We can then use this page to change some of the settings for this server.
For example, if we do not need to have all of the sever components start during the server startup process, we might want to select Start components as needed, which is not automatically selected when a new server is created. When this property is selected, server components are dynamically started as they are needed. When this property is not selected, all of the server components are started during the startup process. Therefore, selecting this property usually results in improved startup time because fewer components are started during the startup process.
Avoid trouble: If running other WebSphere products on top of this product, make sure that those other products support this functionality before you select this property.
- Set the client.encoding.override JVM argument to UTF-8 if we need to use multiple language encoding support in the admin console.
Create server templates
Delete server templates
Related tasks
Set appservers for UCS Transformation Format
Add members to a cluster
Create a server using scripting Getting started with scripting
Add members to a cluster
Related
Server collection
Application server settings