This topic describes how to create runtime environments for WebSphere Application Server. Each runtime environment is created within a profile. A profile is the set of files that define the runtime environment. The Profile Creation wizard creates the profile for each runtime environment.
Before using the Profile Creation wizard, install the core product files.
The Profile Creation wizard is the graphical interface to the wasprofile command. See the description of the wasprofile command for more information.
You must provide enough system temporary space to create a profile. For information on the requirements, see the Profiles: file system requirements topic.
See Creating a deployment manager profile . Create this runtime environment first, to create the administrative node for a multinode, multi-machine group of Application Server nodes that you create later. This logical group of Application Server processes is known as a cell.
See Creating an application server profile .
When you create the application server profile, a default server1 process is created. The process has all of the Sample applications and its own administrative console. You can federate the server1 node into the deployment manager cell with the addNode command or from the administrative console of the deployment manager. The server1 process must be running to begin the federation from the deployment manager.
If you include all of the applications from the application server, the act of federation installs the applications on the deployment manager where they can be redeployed.
Optionally, you can create stand-alone application servers by creating an application server profile and not federating the node. If you remove a federated application server node from a deployment manager, the application server returns to its original configuration, which is a stand-alone application server.
See Creating a custom profile . A custom profile is an empty node that you can customize through the deployment manager to include application servers, clusters, or other Java processes, such as a messaging server. Create a custom profile on a distributed machine and add the node into the deployment manager cell to get started customizing the node.
Each use of the Profile Creation wizard or the wasprofile command-line tool creates one profile.
See the description of the wasprofile command to learn more about the command-line alternative method of creating a profile, and to see examples of using the command.
See Planning the installation for examples of configurations that you can create by creating profiles.