Configuring WebSphere Application Server profiles

There are three types of profiles: a stand-alone server profile, a deployment manager profile (a management profile with a deployment manager server), and a custom profile (managed node). Each profile defines a separate runtime environment, with separate files (commands, configuration files, and log files).

To deploy to a stand-alone server you can create a new stand-alone service registry profile, or augment an existing Application Server profile. To deploy to a federated server or cluster you must create a Service Registry deployment manager profile or augment an existing deployment manager profile. You create custom profiles to create managed nodes for cluster or federated server systems.

Profiles
A profile defines a unique runtime environment, with separate command files, configuration files, and log files. Profiles define three different types of environments on WSRR systems: stand-alone server, deployment manager, and managed node.
Prerequisites for creating or augmenting profiles
Before creating or augmenting a profile, you must ensure that a series of prerequisites have been met.
Creating profiles
You can create new WSRR profiles interactively by using the Profile Management Tool GUI or from a command line by using the manageprofiles command.
Augmenting profiles
You can augment an existing profile for WebSphere® Application Server version 8.5.5 or WebSphere Application Server Network Deployment version 8.5.5 to add support for WSRR. This topic guides you through the steps involved in augmenting profiles interactively by using the Profile Management Tool GUI or, from a command line, by using the manageprofiles command.
Configuring the database using the Profile Management Tool
If you create a stand-alone profile with local DB2 or DB2 Express database, the Profile Management Tool can automatically create the database and tables by using values you provide on the Database Configuration pages. If you create a stand-alone profile with local Oracle or SQL Server databases, or with remote databases of any type, the Profile Management Tool can automatically create the database tables in a database that you have already created for this purpose.
Deleting profiles using the manageprofiles command
You can delete a WebSphere Application Server profile from the command line using the manageprofiles command.
manageprofiles command reference
Use the manageprofiles command to create, augment, or delete a profile. The manageprofiles command and its graphical user interface and the Profile Management Tool, are the only ways to create profiles, or runtime environments.
What is configured when you create or augment a profile
When you create a WSRR profile, or augment an existing profile to include WSRR, you add components and perform configurations in addition to those included in a standard WebSphere Application Server profile.
First steps console
After installing WSRR and creating a profile, you can use the First steps console to get started with WSRR.
Deploying WSRR to clusters and federated servers
The final step in installing WSRR on a cluster or on a federated server is to deploy WSRR.

Parent topic: Installing WebSphere Service Registry and Repository