Response files for creating profiles

You can create a profile by defining profile parameters in a response file, and calling the manageprofiles command with that response file.

WSRR has a number of sample response files for creating different profiles. You can use these as a base for your own profile. The sample response files are located in the directory WAS_install/WSRR/install/profile-responsefiles.

Use the following command to use a response file:

manageprofiles -response response_file

Where response_file is the path to the response file.

The sample files for creating profiles are listed in the following table:

Table 1. Sample response files for creating profiles
File name	Description
create-oracle-standalone-singledb.txt	Use this file to create a profile for a stand-alone server using Oracle with a single database.
create-oracle-standalone-separatedbs.txt	Use this file to create a profile for a stand-alone server using Oracle with three separate databases.
create-mssql-standalone-singledb.txt	Use this file to create a profile for a stand-alone server using SQL Server with a single database.
create-mssql-standalone-separatedbs.txt	Use this file to create a profile for a stand-alone server using SQL Server with three separate databases.
create-db2zos-standalone-singledb.txt	Use this file to create a profile for a stand-alone server using DB2/zOS with a single database.
create-db2zos-standalone-separatedbs.txt	Use this file to create a profile for a stand-alone server using DB2/zOS with three separate databases.
create-db2-standalone-singledb.txt	Use this file to create a profile for a stand-alone server using DB2 with a single database.
create-db2-standalone-separatedbs.txt	Use this file to create a profile for a stand-alone server using DB2 with three separate databases.
create-dmgr.txt	Use this file to create a deployment manager profile. It contains parameters for specifying only the following settings: profile name profile path template path WebSphere Application Server security It does not have WSRR security or databases settings.
create-managed.txt	Use this file to create a custom profile. It contains parameters for specifying only the following settings: profile name profile path template path deployment manager It does not have WSRR security or databases settings.

The parameters specified in the response files that create databases are described in the topic manageprofiles parameters for WSRR configuration (per database product), where they are grouped by database type.

After you have created a deployment manager profile, you must use the administrative console for that profile to deploy WSRR to the cluster or federated servers (see Deploying WSRR to clusters and federated servers).

As general guidance, you should edit the following parameters in the response file before running manageprofiles, or ensure that the default value is what you require:

Profile details

profileName: This is WSRRSrv01 by default. If you already have a profile named WSRRSrv01, or you want to use a different name, you can edit this field.
profilePath: The path to the profile. Edit this to reflect your WSRR installation, and the name you specified for your new profile.
templatePath: Specify the path to the default.wsrr profile template.

WAS security and WSRR security settings

If you leave enableAdminSecurity to true, then you must specify an administrative username and password. You can use the same administrative username and password for the WSRR security settings.

Database settings

When creating profiles for stand-alone servers, you must specify the details for the database that your profile is using (or ensure the defaults are correct). Some databases also require that you specify authentication details for the owner of the database. By default the response file specifies that a new database is created and configured, but you can override these settings if required.

The profile creation generates default values for host name, cell name, node name, and port numbers. You can add additional parameters to the response file to specify these explicitly, if required. (See manageprofiles parameters: stand-alone server profiles or manageprofiles parameters: deployment manager profiles for details of how to do this).