Create an application server profile so that you can make applications
available to the Internet or to an intranet, typically using Java technology.
You can create an application server profile using the Profile Management tool.
Before you begin
Before
you use the Profile Management tool,
install the core product files.
The Profile Management tool is
the graphical user interface to the manageprofiles command. See the description of the manageprofiles command for more information.
You must provide enough
system temporary space to create a profile. For information, read about the
file system requirements for profiles.
Running the Profile Management tool on Microsoft Windows Vista™ and Windows 2008 operating systems: After installing WebSphere Application
Server Version 6.1, install a service pack containing Version 6.1.0.9 or later
on your Microsoft Windows Vista operating system before you attempt to create
any profiles using the Profile Management tool. If you are running Windows
2008, install a service pack containing Version 6.1.0.17 or later before you
attempt to create any profiles using the Profile Management tool.
About this task
newfeatAfter installing the core product
files for the Network Deployment product, you must create a profile. It can
be a Network Deployment deployment manager profile, a deployment manager profile
enabled for Feature Pack for Web Services, a Network
Deployment application server profile, an application server profile enabled
for Feature Pack for Web Services, a cell profile,
or a custom profile. If you are running on Version 6.1.0.21 or higher, it
can also be a custom profile that is enabled for theFeature
Pack for Web Services.
This procedure describes
creating an application server profile using the graphical user interface
that is provided by the Profile Management tool.
An application
server profile has a default server, which is server1, the default application
that includes the Snoop servlet and the Hitcount servlet, and application
Samples. You can federate the application server or use it as a stand-alone
application server.
You can also use the manageprofiles command to create an application server profile. See the description
of the manageprofiles command
for more information.
- Start the Profile Management tool to
create a new runtime environment.
Select the Profile Management tool from the First steps
console:
- Open a command prompt.
- Change directories
to the firststeps directory in the profile root directory.
The profile root varies by the following platforms:
- Issue one of the following firststeps command to start
the console:
./firststeps.sh
firststeps.bat
- Select the Profile Management tool option
from the console.
See the description of the firststeps command
for more information.
Ways to start the wizard
Several
ways exist to start the wizard:
Click Create to create a new profile.
- Click Next on the Welcome panel.
The wizard displays the Environment
Selection panel.
- Select
the type of application server profile that you want to create, and click Next.
newfeat
- Choose Application server if you want to create an application
server profile that is not enabled for the Feature Pack
for Web Services.
- Choose Feature Pack for Web Services if
you want to create an application server profile that is enabled for the Feature Pack for Web Services.
The Profile type selection
panel is displayed.
- Select Application server with Feature Pack for
Web Services. Click Next.
The Profile creation
options panel is displayed.
-
Select either Typical profile creation or Advanced profile
creation, and click Next.
The Typical profile
creation option creates a profile that uses default configuration settings.
With the Advanced profile creation option, you can specify your own
configuration values for a profile.
If
you chose not to deploy the administrative console, then the administrative
console ports are disabled on the Ports panel.
-
If you selected Typical profile creation, then go to the step
on administrative
security.
-
If you selected Advanced profile creation, then select the applications
that you want to deploy; and click Next.
The wizard displays
the Profile name and location panel.
- Specify
a name for the profile and the directory path for the profile directory, or
accept the defaults. Then, click Next.
Profile
naming guidelines: Double-byte characters are supported. The profile name
can be any unique name with the following restrictions. Do not use any of
the following characters when naming your profile:
- Spaces
- Special characters that are not supported within the name of a directory
on your operating system, such as *&?
- Slashes (/) or (\)
The default profile
The first
profile that you create on a machine is the default profile. The default profile
is the default target for commands that are issued from the bin directory
in the product installation root. When one profile exists on a machine, every
command works on the only server process in the configuration. You
can make another profile the default profile when you create that profile
by checking Make this profile the default on the Profile name and location
panel of the Advanced profile creation path.
Addressing
a profile in a multiprofile environment
When multiple
profiles exist on a machine, certain commands require that you specify the
profile to which the command applies. These commands use the -profileName
parameter to identify which profile to address. You might find it easier to
use the commands that are in the bin directory of each profile.
The commands are found in the following location:
A command has two lines. Set the WAS_USER_SCRIPT environment variable
on the first line for the command prompt. You use the variable to set up the
command environment to address the profile. Use the second line to call the
command in the following location:
Use the command to query the command shell to determine
the calling profile and to autonomically address the command to the calling
profile.
Default profile information
The default profile
name is
profileTypeProfileName, where:
- profileType is a value of AppSrv, DMgr,
or Custom.
- ProfileName is a sequential number that is used to create a unique
profile name.
The
default profile directory is app_server_root/profiles,
where app_server_root is
the installation root.
The
default profile directory is app_server_root\profiles,
where app_server_root is
the installation root.
- On the Node and host names panel, specify the characteristics
for the application server, and click Next.
Use unique
names for each application server that you create.
Reserved
names: Avoid using reserved folder names as field values. The use of reserved
folder names can cause unpredictable results. The following terms are reserved
folder names:
- cells
- nodes
- servers
- clusters
- applications
- deployments
Field Name |
Default Value |
Constraints |
Description |
Node name |
shortHostNameNodeNodeNumber where:
- shortHostName is the short host name.
- NodeNumber is a sequential number starting at 01.
|
Avoid using the reserved terms. |
Select any name you want. To help organize your installation,
use a unique name if you plan to create more than one application server on
the machine. |
Host name |
The long form of
the domain name server (DNS) name.
|
Addressable through your network. |
Use the DNS name or IP address of your machine to enable
communication with your machine. See additional information about the host
name following this table. |
Node name considerations: If
you plan to migrate an installation of Version 5 Network Deployment to Version
6 and migrate one of the managed nodes in the cell, use the same node name
for the Version 6 application server that you used for the V 5 managed node.
Directory path considerations: The
installation directory path must be less than or equal to 60 characters.
Host
name considerations:
The host name is the network name
for the physical machine on which the node is installed. The host name must
resolve to a physical network node on the server. When multiple network cards
exist in the server, the host name or IP address must resolve to one of the
network cards. Remote nodes use the host name to connect to and communicate
with this node. Selecting a host name that other machines can reach within
your network is important. Do not use the generic identifier, localhost,
for this value. Also, do not attempt to install WebSphere Application Server
products on a machine with a host name that uses characters from the double-byte
character set (DBCS). DBCS characters are not supported when used in the host
name.
If you define coexisting nodes on the same computer
with unique IP addresses, define each IP address in a domain name server (DNS)
look-up table. Configuration files for stand-alone application servers do
not provide domain name resolution for multiple IP addresses on a machine
with a single network address.
The value that you specify
for the host name is used as the value of the hostName property in configuration
documents for the stand-alone application server. Specify the host name value
in one of the following formats:
- Fully qualified domain name server (DNS) host name string, such as xmachine.manhattan.ibm.com
- The default short DNS host name string, such as xmachine
- Numeric IP address, such as 127.1.255.3
The fully qualified DNS host name has the advantages
of being totally unambiguous and flexible. You have the flexibility of changing
the actual IP address for the host system without having to change the application
server configuration. This value for the host name is particularly useful
if you plan to change the IP address frequently when using Dynamic Host Configuration
Protocol (DHCP) to assign IP addresses. A format disadvantage is a dependency
on DNS. If DNS is not available, then connectivity is compromised.
The short host name is also dynamically resolvable. A short name
format has the added function of being redefined in the local hosts file so
that the system can run the application server, even when disconnected from
the network. Define the short name as the loopback address, 127.0.0.1,
in the hosts file to run disconnected. A format disadvantage is a dependency
on DNS for remote access. If DNS is not available, then connectivity is compromised.
A numeric IP address has the advantage of not requiring name resolution
through DNS. A remote node can connect to the node that you name with a numeric
IP address without DNS being available. A format disadvantage is that the
numeric IP address is fixed. You must change the setting of the hostName property
in Express configuration documents whenever you change the machine IP address.
Therefore, do not use a numeric IP address if you use DHCP, or if you change
IP addresses regularly. Another format disadvantage is that you cannot use
the node if the host is disconnected from the network.
After specifying application
server characteristics, the wizard displays the Administrative security panel.
- Optionally enable administrative
security, and click Next.
You can enable
administrative security now during profile creation, or later from the console.
If you enable administrative security now, then enter a user name and password
to log onto the administrative console.
If
you installed the Samples, and you chose to deploy them, then the Samples
require an account under which to run. Supply the Samples password for the
account. You cannot change the user name of the account.
After specifying
security characteristics, the wizard displays the Port value assignment panel
if you previously selected Advanced profile creation.
- If you selected Typical profile creation at
the beginning of these steps, go to the step that displays the Profile
summary panel.
- Verify that the ports specified for the stand-alone application
server are unique, and click Next.
If
you chose not to deploy the administrative console, then the administrative
console ports are disabled on the Ports panel.
Port conflict resolution:
Ports are recognized as being in use if one of the following conditions
exists:
- The ports are assigned to a profile created under an installation performed
by the current user.
- The port is currently in use.
Validation of ports occurs when you access the Port value assignment
panel. Conflicts can still occur between the Port value assignment panel and
the Profile Creation Complete panel because ports are not assigned until profile
creation completes.
If you suspect a port
conflict, then you can investigate the port conflict after the profile is
created. Determine the ports that are used during profile creation by examining
the following files:
Included in this file are the keys and values used in setting the ports.
If you discover ports conflicts, then you can reassign ports manually. To
reassign ports, run the updatePorts.ant file by using the ws_ant script.
The
wizard displays the Windows service definition panel if you are installing
on a Windows platform and the installation ID has the administrative group
privilege. The wizard displays the Linux service definition panel if you are
installing on a supported Linux platform and the ID that runs the Profile Management tool is the root user.
- Choose
whether to run the application server as a Windows service on a Windows platform
or as a Linux service on a Linux platform, and then click Next.
The Windows service definition
panel is displayed for the Windows platform only if the ID that installs the
Windows service has the administrator group privilege. However, you can run
the WASService.exe command to create the Windows service as long as the installer
ID belongs to the administrator group. Read about automatically restarting
server processes for more information.
Running an application server as a service on the Microsoft Windows Vista™ operating system:
- An application server that is running as a service needs to run with Administrator
privileges if it is to be started or stopped on the Microsoft Windows Vista
operating system.
The service can be configured to automatically start
on system reboot, or it can be manually started and stopped from the Windows
Services panel after accepting the elevation prompt for Administrator privileges.
- Using the WASService.exe utility to change the characteristics of the
service or to create a new service also requires running with Administrator
privileges.
To do this, run
WASService.exe from a command
prompt that is launched by performing the following actions:
- Right-click the command file or its shortcut.
- Click Run As Administrator.
- The following .bat files can run to create service
actions:
- startServer.bat
- stopServer.bat
- startNode.bat
- stopNode.bat
- startManager.bat
- stopManager.bat
You cannot alter or control these service actions while running with
standard user privileges. Administrator privileges are required.
If
an application server is installed as a service, then the service can be controlled
by running the .bat files from a command prompt that is launched by performing
the following actions:
- Right-click a command prompt shortcut.
- Click Run As Administrator.
If an application server is not configured to run as a service,
then running these utilities from an elevation prompt for Administrator privileges
is not required.
The product attempts to start Windows
services for application server processes that are started by a startServer
command. For example, if you configure an application server as a Windows
service, and issue the startServer command, then the wasservice command
attempts to start the defined service.
If you chose to install
a local system service, then you do not have to specify your user ID or password.
If you create a specified user type of service, then you must specify the
user ID and the password for the user who runs the service. The user must
have Log on as a service authority for the service to run
properly. If the user does not have Log
on as a service authority, then the Profile Management tool automatically
adds the authority.
To perform this
installation task, the user ID must not have spaces in its name. In addition
to belonging to the administrator group, the ID must also have the advanced
user right Log on as a service. The Installation wizard grants
the user ID the advanced user right if it does not already have it and if
the user ID belongs to the administrator group.
You can also
create other Windows services after the installation is complete, to start
other server processes. Read about automatically restarting server processes
for more information.
You can remove the
Windows service that is added during profile creation during profile deletion.
IPv6 considerations
Profiles created
to run as a Windows service fail to start when using Internet Protocol Version
6 (IPv6) if the service is configured to run as local system. Create a user-specific
environment variable to enable IPv6. Since this environment variable is a
user variable instead of a local system variable, only a Windows service that
runs as that specific user can access this environment variable. By default,
when a new profile is created and configured to run as a Windows service,
the service is set to run as local system. When the Windows service for the
product tries to run, the service is unable to access the user environment
variable that specifies IPv6, and thus tries to start as IPv4. The server
does not start correctly in this case. To resolve the problem, when creating
the profile, specify that the Windows service for the product runs with the
same user ID under which the environment variable that specifies IPv6 is defined,
instead of as local system.
Default values for the
Windows service
![[Windows]](../../windows.gif)
The default
values for the Windows service definition panel are as follows:
- The default is to run as a Windows service.
- The service process is selected to run as a system account.
- The user account is the current user name. User name requirements are
the requirements that the Windows operating system imposes for a user ID.
- The startup type is automatic. The values for the startup
type are those values that the Windows operating system imposes. If you want
a startup type other than automatic, you can either select
another available option from the drop down list or change the startup type
after you create the profile. You can also remove the created service after
profile creation, and add it later with the desired startup type. You can
choose not to create a service at profile creation time and optionally create
it later with the desired startup type.
The
Linux service definition panel is displayed if the current operating
system is a supported version of Linux and the current user has the appropriate
permissions.
The product attempts to start
Linux services for application server processes that are started by a startServer
command. For example, if you configure an application server as a Linux service
and issue the startServer command, then the wasservice command attempts
to start the defined service.
By default,
the product is not selected to run as a Linux service.
To create the service, the user that runs the Profile Management tool must
be the root user. If you run the Profile Management tool with
a non-root user ID, then the Linux service definition panel is not displayed,
and no service is created.
You must specify
a user name under which the service runs.
To
delete a Linux service, the user must be the root user or have appropriate
privileges for deleting the service. Otherwise, a removal script is created
that the root user can run to delete the service for the user.
The
next wizard panel displays the Web server definition panel, if you previously
selected Advanced profile creation.
- For advanced profile creation,
if you choose to include a Web server definition in the profile now, specify
the Web server characteristics on the panels, and click Next until
you complete the Web server definition panels.
If you use a
Web server to route requests to the product, then you need to include a Web
server definition. You can include the definition now, or define the Web server
to the product later. If you define the Web server definition during the creation
of this profile, then you can install the Web server and its plug-in after
you create the profile. However, you must install both to the paths that you
specify on the Web server definition panels. If you define the Web server
to the product after you create this profile, then you must define the Web
server in a separate profile.
The wizard displays the Profile Creation
Summary panel.
- Click Create to
create the application server, or click Back to change the characteristics
of the application server.
The Profile creation
progress panel, which shows the configuration commands that are running, is
displayed.
When the profile creation
completes, the wizard displays the Profile Creation Complete panel.
- Optionally, select Launch the
First steps console, Create another profile, or both. Click Finish to
exit.
With the First steps console, you can create additional
profiles and start the application server. Use the Create another profile option
to create additional profiles.