Use the Profile creation wizard

 

+

Search Tips   |   Advanced Search

 

 

Before you begin

This topic describes how to create run-time environments for WebSphere Application Server. Each run-time environment is created within a profile. A profile is the set of files that define the run-time environment. The Profile creation wizard creates the profile for each run-time environment.

Before using the Profile creation wizard, install the core product files.

The Profile creation wizard is the wizard interface to the profile creation tool, wasprofile.

An error can occur when you have not provided enough system temporary space to create a profile. Verify that you have a minimum of 40 MB of temp space available before creating a profile.

You must have 200 MB of available disk space in the directory where you create an Application Server profile.

You must have 30 MB of available disk space in the directory where you create a deployment manager profile.

You must have 10 MB of available disk space in the directory where you create a custom profile.

Manually verify that the required space for creating a profile is available on AIX. A known problem in the underlying InstallShield for Multiplatforms (ISMP) code prevents proper space checking on AIX systems at the time that the product disc was created.

Concurrent profile creation is not supported at this time for one set of core product files. Concurrent attempts to create profiles result in a warning about a profile creation already in progress.

 

Overview

The installation procedure for the Network Deployment product does not create a run-time environment by default because three possibilities exist. After installing the core product files for the Network Deployment product, use the Profile creation wizard to create any combination of the following three profiles to have an operational run-time environment:

Each use of the Profile creation wizard or the wasprofile command line tool creates one profile.

 

Procedure

  1. Install the product to create the core product files.

  2. Start the Profile creation wizard to create a new run-time environment.

    Several ways exist to start the wizard. The initial way to start the wizard is at the end of installation by selecting the check box to launch the Profile creation wizard.

    One way to start the wizard is to issue the command directly from a command line.

    The command is in...

    install_root/bin/ProfileCreator

    The name of the command varies per platform:

    • pctAIX.bin
    • pctHPUX.bin
    • 64-bit platforms: pctHPUXIA64.bin
    • pctLinux.bin
    • 64-bit platforms: pct.bin S/390 platforms: pctLinux390.bin
    • Power platforms: pctLinuxPPC.bin
    • pctSolaris.bin
    • pctWindows.exe
    • 64-bit platforms: pctWindowsIA64.exe

    Another way to start the Profile creation wizard is to select the wizard from the First steps console.

    1. Open a command window.

    2. Change directories to $WAS_HOME/firststeps and execute firststeps.sh

    3. Select the Profile creation wizard option on the console.

      The Profile creation wizard is an InstallShield for Multiplatforms application. The wizard loads the Java 2 SDK and then displays its Welcome panel.

  3. Create a profile.

    You can create profiles in any order. However, to create a functioning cell in the shortest possible time, create a deployment manager profile first. Then create an application server profile and add it to the deployment manager cell. You now have a functioning cell with a managed node that one can manage from the administrative console of the deployment manager.

    A custom profile requires a greater amount of customization. When you create a custom profile, use the addNode command to federate it into the deployment manager cell. In contrast to an application server profile, a custom profile does not have a default application server on its node. The server1 application server does not exist by default on the custom node. Nor are there any default applications on the custom node. Use the administrative console of the deployment manager to customize the empty node for production or other uses. You can create application servers or clusters on the node, for example.

    Create any of the following profiles:

    • Create a deployment manager.

      Create a deployment manager to establish a cell. Although one can create an application server profile and use it as a stand-alone application server, have a deployment manager to use a custom profile. So there is no point in creating a custom profile until you have created a deployment manager.

    • Create an application server profile,

      Federate the application server into the deployment manager cell to create a federated server1 application server. A stand-alone application server has default applications. You can include the applications as you federate the application server to install the default applications on the deployment manager.

      Two methods exist for federating application servers into a deployment manager cell:

      • Start the deployment manager and the application server and use the administrative console of the deployment manager to federate the node. Click...

        System administration | Nodes | Add node | Managed node | Next

        ...and identify the host name and the SOAP port of the machine where you created the application server.

      • Start the deployment manager.

        Go to...

        $WAS_HOME/install_root/profiles/profile/bin

        ...and issue the addNode command.

    • Create a custom profile

      The first part of the process is to install the Network Deployment product to create the core product files. Then use the Profile creation wizard to create a managed profile.

      The next part of the process is to federate the managed profile into the deployment manager cell. This changes the custom profile into a managed node.

      After federation, a custom profile has a nodeagent process but does not have an application server process. Contrast this situation to an application server profile that has a server1 process, but does not have a nodeagent process until you federate the node.

      Start the nodeagent process to allow the administrative console of the deployment manager to create server processes on the managed node.

      Two methods exist for federating a custom node into a deployment manager cell:

      • Federate the custom node during custom profile creation, either with the wizard or as the wizard runs in silent mode.

        The deployment manager must be running and accessible at the host address you supply. The deployment manager must also use the default JMX connector type, which is SOAP. The deployment manager must not have security enabled. If any of these conditions are not met, do not federate the custom profile as you create it, but federate it later with the addNode command. Otherwise, you create a faulty profile that move or delete from the profiles repository directory before creating another profile.

      • Use the addNode command to federate the custom node after you create the custom profile.

        1. Start the deployment manager.

        2. Go to...

          $WAS_HOME/profiles/profile/bin

          ...and issue the addNode command.

        3. Within the same directory, issue the startNode command.

      After federation, go to the administrative console of the deployment manager to customize the empty node.

    • Create a deployment manager and a managed node on the same machine:

      1. Create a deployment manager

      2. Start the deployment manager with the startManager command.

      3. Create an application server profile

      4. Start the application server with the startServer command. more information.

      5. Use the administrative console of the deployment manager to add the application server node into the deployment manager cell. Click...

        System administration | Nodes | Add node | Managed node | Next

        ...and identify the host name of the machine and the SOAP port of the application server.

        The SOAP port is identified in the file...

        $WAS_HOME/profiles/profile/config/cells/cell/nodes/node/serverindex.xml

        You can also use the administrative console of the application server to view its SOAP port setting. Click...

        Servers | Application servers | server1 | Ports

        The SOAP port is usually the second port in the list.

        Select the check box to include applications that are installed on the application server. The default application has the snoop servlet and the hitcount servlet, which are useful for testing.

        Adding the stand-alone application server node to the deployment manager node changes the server1 process into a managed node. Use the administrative console of the deployment manager to configure the server1 process.

        You can also create a custom profile and federate the node during profile creation, or use the addNode command to federate the empty node into the cell after the custom profile exists. A managed node created from a custom profile requires customization to create an application server and install applications. Use the administrative console of the deployment manager to configure the custom node.

 

See also


Use the Profile creation wizard to create a deployment manager
Use the Profile creation wizard to create a custom profile
Use the Profile creation wizard to create an application server
Delete a profile
wasprofile command
Install silently
responsefile.pct.NDdmgrProfile.txt
responsefile.pct.NDmanagedProfile.txt
responsefile.pct.NDstandAloneProfile.txt

 



 

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.
AIX is a trademark of the IBM Corporation in the United States, other countries, or both.