Application server profiles are the run-time environments for application server processes. This topic describes common scenarios for creating application server profiles and provides links to profile creation procedures for each scenario.
Before you begin
Install the core product files for a WebSphere Application Server product before using the Profile Creation wizard to create additional application server run-time environments.
Why and when to perform this task
This topic describes how to create cell profiles, deployment manager profiles, stand-alone application server profiles, and custom profiles. The cell profile actually creates two profiles, a deployment manager profile and a federated application server profile. Each profile for a deployment manager or an application server is a run-time environment, with data files, configuration files, applications, and an administrative console. The custom profile is an empty node that you must federate into a deployment manager cell before it is of use.
Steps for this task
The first part of the process is to install the Network Deployment product to create the core product files. Then you can use the Profile Creation wizard to create a custom profile.
The next part of the process is to federate the custom profile
into the deployment manager cell. This changes the custom profile into a managed
node.
Issue the addNode command from the bin directory of the custom profile.
A federated custom node has a nodeagent process but does not have Sample applications or an application server process. Use the administrative console of the deployment manager to create server processes on the federated custom node.
Contrast a federated custom node to a stand-alone application server that has been federated with the includeapps parameter. The federated application server has a nodeagent process, a server1 process, and the default application installed. If you installed the Sample applications, the federated server1 process also has the Sample applications installed.
Use the startNode command to start the nodeagent process if it is not running. The addNode command starts the nodeagent process initially.
Use the administrative console of the deployment manager to create server processes on the managed node.
Use the Profile Creation wizard to create a deployment manager and a managed node at any time after installation of the core product files. Or, you can use the wizard to create a managed node on a machine where a deployment manager already exists.
Any time that you create two or more application server processes on one machine, verify that the machine is capable of hosting both processes. See the hardware prerequisites on the Supported hardware and software Web site.
Result
Following this procedure results in reviewing common installation scenarios to find a possible match for the topology that you intend to create. This procedure shows how to use the Profile Creation wizard to create additional profiles.
What to do next
After determining a possible topology, follow the steps in the overall procedure.
One step not mentioned in any of these scenarios is to prepare the operating system for installation. Useful links to the installation procedures for each installable component are in the list of related topics.
Related information
Planning the installation
Preparing the operating system for product installation
Installing the product and additional software
Creating profiles through the graphical user interface
addNode command
startNode command
startManager command
startServer command