Create a new profile

To create a new profile, run the wasprofile script from the Qshell command line. This script creates all new server directories and sets up the correct authorities. To run this script, your iSeries user profile must have *ALLOBJ authority.

1. On the OS/400 command line, enter the STRQSH (Start Qshell) command.

2. On the Qshell command line, use the cd command to change to the directory that contains the script:

   cd install_root/bin

   where install_root is /QIBM/ProdData/WebSphere/AppServer/V6/Base for WebSphere Application Server and WebSphere Application Server Express, and /QIBM/ProdData/WebSphere/AppServer/V6/ND for WebSphere Application Server Network Deployment.

3. Run the wasprofile script:

   wasprofile -create -profileName profile -templatePath templatename
       -startingPort portnumber

   where

   • profile is the name of the profile that is created.
   • templatename is the name of the profile template from which to create the profile. This parameter is optional. Unless a template name is specified, the template will be named default.
   • portnumber is the first port in the block of ports to use for the profile.

   For more information on the wasprofile script and additional parameters, see wasprofile command.

   Standard Templates

   Several templates are included with WebSphere Application Server. The following list contains the names of the included tamplates along with a brief discription of their functions or uses:

   • defaultnosamp - No sample installed
   • defaultnoexamp - No samples, no DefaultApplication installed
   • defaultnoadmin - No admin console installed
   • defaultnosampnoadmin - No samples and no admin console installed
   • dmgr - Deployment manager profile (Network Deployment only)
   • managed - Simple profile ready to be added to a network deployment cell (Network Deployment only)
   • client - Application client profile
   • http - Remote HTTP profile

   All of the templates that start with default are stand-alone application server profiles. Also, unless noted otherwise, the template exists in Express/Base/ND.

4. After you create a profile, see Start and stop application servers for instructions on starting the profile.

Examples

The following examples illustrate how to create an application server profile. The profile is created under directory the profile_root/myprofile directory, where profile_root is /QIBM/UserData/WebSphere/AppServer/V6/Base/profiles for WebSphere Application Server and WebSphere Application Server Express, and /QIBM/UserData/WebSphere/AppServer/V6/ND/profiles for WebSphere Application Server Network Deployment.

• Creating an application server profile and making it the default profile:

  wasprofile -create -profileName myprofile -startingPort 10320 -isDefault

• Creating an application server profile that does not have the sample applications installed:

  wasprofile -create -profileName myprofile -templatePath defaultnosamp -startingPort 10320

The following example shows how to create a deployment manager profile. The profile is created under directory the profile_root/devmgr directory, where profile_root is /QIBM/UserData/WebSphere/AppServer/V6/Base/profiles for WebSphere Application Server and WebSphere Application Server Express, and /QIBM/UserData/WebSphere/AppServer/V6/ND/profiles for WebSphere Application Server Network Deployment.

wasprofile -create -profileName devmgr -templatePath dmgr -startingPort 11320

The following example shows how to create a managed or custom profile. The profile is created under directory the profile_root/mnginst directory, where profile_root is /QIBM/UserData/WebSphere/AppServer/V6/Base/profiles for WebSphere Application Server and WebSphere Application Server Express, and /QIBM/UserData/WebSphere/AppServer/V6/ND/profiles for WebSphere Application Server Network Deployment.

wasprofile -create -profileName mnginst -templatePath managed -dmgrHost  myiseries.mycompany.com -dmgrPort 8879 -startingPort 12320