You can create profiles, which define runtime environments, using the Profile Management tool. Using profiles instead of multiple product installations saves disk space and simplifies updating the product because a single set of core product files is maintained.
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.
See Creating a cell profile. With a cell profile, you can create a deployment manager profile and a profile for a federated application server node in a single pass through the Profile Management tool. Use the cell profile creation option to create the deployment manager profile and the federated application server node profile, unless you have a specific reason to create them separately.
See Creating a deployment manager profile. With a deployment manager profile you can 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. If you select Typical profile creation, then the process has the default application and its own administrative console. If you choose the Advanced profile creation option, then you can choose which applications to deploy. 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, then 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, then 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.
See the description of the manageprofiles command to learn more about the command-line alternative method of creating a profile and to see examples of using the command.
Read about planning for installation for examples of configurations that you can create by creating profiles.
In this information ...Subtopics
Related tasks
| IBM Redbooks, demos, education, and more(Index) |