Planning to create application server environments

Application server profiles are the runtime 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 runtime environments.

About 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 runtime 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.

Procedure

  1. Create a deployment manager. See Creating a deployment manager profile for more information on how to create a deployment manager.


    Creating a deployment manager profile

  2. Create a custom profile. See Creating a custom profile for more information.

    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.


    Creating 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.
    Federating a custom profile

    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.


    Federated node

    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.

  3. Create a deployment manager and a managed node on the same machine.

    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.

    1. Create a deployment manager. See Creating a deployment manager profile for more information.
    2. Create a stand-alone application server node. See Creating an application server profile for more information.
    3. Start the deployment manager with the startManager command.
    4. Start the stand-alone application server with the startServer server1 command.
    5. Use the administrative console of the deployment manager to federate the application server node. Click Administration > Nodes > Add node.

Results

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.

Use the Profile Creation wizard to create:
  • A deployment manager profile
  • A stand-alone application server profile
  • Custom profiles for a deployment manager cell

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.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 9:00:59 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-dist&topic=tins_scenario4
File name: tins_scenario4.html