Augmenting profiles using the manageprofiles command

Augmentation is the ability to change an existing profile with an augmentation template. You can augment existing WebSphere® Application Server or WebSphere Application Server Network Deployment profiles into WSRR profiles. You can augment a profile from the command line using the manageprofiles command.

Before you begin

Before using this procedure, ensure that you have completed the following tasks:

You have viewed the list of prerequisites for augmenting a profile at Prerequisites for creating or augmenting profiles.
You have shut down any servers associated with the profile that you plan to augment.
You have verified that you are not already running the manageprofiles command on the same profile. If an error message is displayed, determine if there is another profile creation or augmentation action in progress. If so, wait until it completes.

Note: It is only possible to augment "management" based deployment manager profiles. Those created using the "cell" profile cannot be augmented using the dmgr.wsrr profile Template.

About this task

You can augment a profile silently by running a script that calls the manageprofiles command with a response file. The response file provides all the parameters required to augment the profile. WSRR provides a number of sample response files for various combinations of database type, and profile type (stand-alone, federated node, or cluster). The sample response files are located in WAS_install/WSRR/install/profile-responsefiles.

Procedure

To use the manageprofiles command to augment a profile, complete the following steps.

Determine the template that was used to create the existing profile (deployment manager, stand-alone, or managed). You can determine the template that was used for creating the profile by looking at the profile registry. The registry is located in install_root/properties/profileRegistry.xml. Do not modify this file, use it to get information.
Select a sample response file on which to base your response file, and copy it to a temporary directory.
Edit the response file to supply the parameters required for the augmentation of the profile. You can use the default values in the sample response files for most of the parameters, but you typically have to edit fields to identify the profile to augment and the database that your profile will use, as well as supplying user ID and password details for the user who is running the augmentation task. See the topic on response files for guidance.
Run the manageprofiles command with the -response argument, specifying the path to your response file. For example:
- manageprofiles.sh -response /temp/augment-oracle-standalone-singledb.txt
- manageprofiles.bat -response c:\temp\augment-oracle-standalone-singledb.txt
The command displays status as it runs. Wait for it to finish. Normal syntax checking on the response file applies as the file is parsed like any other response file. Individual values in the response file are treated as command-line parameters.

What to do next

After you have augmented a WebSphere Application Server or WebSphere Application Server Network Deployment profile into a WSRR profile, you should:

Check the logs

You can see that your profile augmentation completed successfully if you receive the message "INSTCONFSUCCESS: Profile augmentation succeeded.", and you can check the following log file:

On Linux and UNIX platforms: install_rootinstall_root/logs/manageprofiles/profile_name_augment.log
On Windows platforms: install_root\logs\manageprofiles\profile_name_augment.log

Run the Installation Verification Test (IVT) tool to verify that the profile was augmented successfully. To do this, run the following command:

On Linux and UNIX platforms: profile_root/bin/wsrr_ivt.sh
On Windows platforms: profile_root\bin\wsrr_ivt.bat

Start the server

Check the server operation by selecting Start the server from the First steps console. An output window opens. If you see a message like the following one, your server is operating properly:

ADMU3000I: Server server1 open for e-business; process id is 3348

You can also check server operation by running the Installation Verification Test (IVT) from the First steps console or running the ivt command. This test verifies that your deployment manager or stand-alone server installation is operating properly. For a stand-alone server profile, it also runs a System Health check and generates a report.

Load and activate a WSRR configuration profile

To make use of WSRR, you must load and activate a WSRR configuration profile. located in the <WAS_INSTALL_ROOT>/WSRR/config directory.After your server is started, load and activate a profile; see Loading a configuration profile and Activating a configuration profile for details.