(iSeries)

Manage default profiles

Create default profiles for the operating system. Scripts that do not specify a profile use the default profile.

Default profiles are included with the product. A profile is a set of configuration files and installed applications that make up the WebSphere Application Server environment.

Tasks

• Install the web server plug-in feature without the core product feature to create a default remote HTTP profile.

• Install the secure proxy server feature without the core product feature to create a default secure proxy profile.

• Install the application client feature without the core product feature to create the default application client profile.

• Install WAS ND to create the default cell profile.

  The cell profile consists of two profiles:

  • The deployment manager profile
  • A federated node profile belonging to the cell that the deployment manager profile manages. The federated node profile contains a single application server.

Depending on the steps that we performed, we have created at least one default profile.

What to do next

Continue configuring the environment if we have not completed the configuration.

Subtopics

• (iSeries) Default application server profiles
  The default WAS profile provides the necessary configuration files for starting and managing the application server that it contains. Become familiar with the cell, node, servers, applications and ports for the default profile.
• (iSeries) Default secure proxy profiles
  The name of the default secure proxy profile is SecureProxySrv01. This profile is created when we install the secure proxy server feature.
• (iSeries) Default application client profiles
  The application client profile contains configuration files and properties files used to configure and run an application client. This profile does not contain an application server.
• (iSeries) Default federated server profiles
  Use the addNode script or the WAS ND administrative console to federate a profile into a WAS ND cell.
• (iSeries) Default deployment manager profiles
  When we install WAS ND, two profiles are created: a standalone application server profile named default; and a deployment manager profile named dmgr. The standalone application server profile is the default profile with respect to scripts.
• (iSeries) Default remote HTTP profiles
  The name of the default remote HTTP profile is http. This profile is created when we install the web server plug-in.

(iSeries) Default secure proxy profiles

(iSeries) Default application client profiles

(iSeries) Default federated server profiles

(iSeries) Default deployment manager profiles

(iSeries) Default remote HTTP profiles