Creating a profile on a local WAS V6.1

This topic describes how to create runtime environments for a local WebSphere® Application Server V6.1. Each runtime environment is created within a profile. A profile is the set of files that define the runtime environment.

The Profile Management Tool is a graphical user interface to the WAS V6.1 command-line tool, manageprofiles for creating profiles. You can use the development workbench in this product to start the Profile Management Tool provided by the WAS product.

When the WAS V6.1 integrated test environments are installed using the IBM® Installation Manager that comes with the installation of the IBM Rational® Software Delivery Platform, the installation procedure creates a profile which is assigned a default role. By default, if you did not change the

Profile name text field in the IBM Installation Manager, the default naming convention of the profile name is was61profile#, where # is a number that increments by one to create a unique profile name each time a WAS v6.1 profile is created by the Profile Management Tool. In addition, the installation procedure creates an application server with the default name, server1.

You can use the Profile Management Tool to create multiple profiles on the same machine. The need for defining multiple profiles to create multiple runtime environments on the same machine is common. An example use case is allowing different teams to test independently of each other on the same machine by using their own profiles. Another example use case is allowing a developer to create separate profiles of the application server for development and testing.

Restriction:

• If you install multiple instances of WAS as the root user and give a non-root user access to only a subset of those instances, there is a known limitation where the Profile Management tool does not function correctly for the non-root user in the Windows® Vista and Windows 2008 operating system. To workaround this limitation a non-root user can install the WAS product or be given permission to access the other WAS instances. For more details, see the Limitations of non-root installers topic available in the WAS 6.1 Information Center.

Prerequisites:

• See the Profiles: required disk space topic from the WAS information center to verify that you have the required disk space.

• Set the user of your operating system to have administrator authority, which is required to run the WAS's Profile Management Tool. For example, the root user on Linux®.

• Important: Concurrent profile creation is not supported for one set of core WAS product files. Concurrent attempts to create profiles result in a warning about a profile creation already in progress.

To create a profile on a local WAS V6.1:

1. From the menu bar of the workbench, select

   Window | Preferences.

2. In the Preferences window, expand

   Server | WebSphere Application Server.

3. Under the

   WAS local profile management list, select a server runtime environment for which you want to create a profile.

   Tip: To add a server runtime environment to this list, see the Defining the server runtime environments preferences topic.

4. Beside the

   WebSphere profiles defined in the runtime selected above list, which lists all the profiles defined for the currently selected runtime environment in the previous step, click the

   Run Profile Management Tool button:

5. Configure your profile by following instructions in the Profile Management Tool. For more information on configuring a profile using the Profile Management tool, see the Using the Profile to create an application server topic.

   Tip: In the case you select the Advanced profile creation option, in the Windows Service Definition page of the Profile Management Tool, clear the

   Run the Application Server process as a Windows service check box. Window services are global settings on an operating system. Clearing this check box avoids conflict of service requests between different profiles. For example, if you configure an application server as a Windows service and issue the startServer command, the wasservice command attempts to start the defined service. As a result, you can loose track of which profile issued the startServer command, as any profile can start this globally defined Window service.

6. In order for the workbench to communicate to the server, grant a non-root user access to the newly created profile. See the Creating profiles for non-root users topic for details.

7. (Optional) You can delete a profile:

   1. Under the

      WAS local profile management list, select the server runtime environment containing the profile for which you want to delete.

   2. Under the

      WebSphere profiles defined in the runtime selected above list, select the profile for which you want to delete and click the

      Delete button. The registry and configuration files associated to the deleted profile are removed from the file system; however, any log files remain on the file system.

---