Profile Management on WebSphere Application Server
Profile Concepts
A profile defines the runtime environment. The profile includes all the files that the server processes in the runtime environment and that you can change.You can create a runtime environment either through the manageprofiles command or the Profile Management Tool graphical user interface. You can use the Profile Management Tool to enter most of the parameters that are described in this article. Some parameters, however, require you to use the manageprofiles command.
You must use the manageprofiles command to delete a profile, for instance, because the Profile Management Tool does not provide a deletion function. You can use either the Profile Management Tool or the manageprofiles command to create a cell profile. The Profile Management Tool creates the cell in a single step, whereas the manageprofiles command requires two separate invocations.
Why and when to create a profile
The manageprofiles command-line tool defines each profile for the product.Run the Profile Management Tool or the manageprofiles command each time that you want to create a profile. A need for more than one profile on a machine is common.
Administration is greatly enhanced when using profiles instead of multiple product installations. Not only is disk space saved, but updating the product is simplified when you maintain a single set of product core files. Also, creating new profiles is more efficient and less prone to error than full product installations, allowing a developer to create separate profiles of the product for development and testing.
You can run the Profile Management Tool or the command-line tool to create a new profile on the same machine as an existing profile. Define unique characteristics, such as profile name and node name, for the new profile. Each profile shares all runtime scripts, libraries, the Java™ SE Runtime Environment environment, and other core product files.
Profile types
Templates for each profile are located in the app_server_root/profileTemplates directoryMultiple directories exist within this directory, which correspond to different profile types and vary with the type of product that is installed. The directories are the paths that you indicate while using the manageprofiles command with the -templatePath option. You can also specify profile templates that exist outside the profileTemplates directory, if you have any. See the -templatePath parameter description in the manageprofiles command topic for more information. The manageprofiles command in the WebSphere® Application Server Network Deployment product can create the following common types of profiles:
The basic function of the deployment manager is to deploy applications to a cell of application servers, which it manages. Each application server that belongs to the cell is a managed node.
You can create the management profile with a deployment manager server using the Profile Management Tool or the manageprofiles command. If you create the profile with the manageprofiles command, specify app_server_root/profileTemplates/management for the -templatePath parameter and DEPLOYMENT_MANAGER for the -serverType parameter.
Use the application server to make applications available to the Internet or to an intranet. An important product feature is the ability to scale up a standalone application server profile by adding the application server node into a deployment manager cell. Multiple application server processes in a cell can deploy an application that is in demand. You can also remove an application server node from a cell to return the node to thestatus of a standalone application server.
Each standalone application server can optionally have its own administrative console application, which you use to manage the application server. You can also use the wsadmin scripting facility to perform every function that is available in the administrative console application.
No node agent process is available for a standalone application server node unless you decide to add the application server node to a deployment manager cell. Adding the application server node to a cell is known as federation. Federation changes the standalone application server node into a managed node. You use the administrative console of the deployment manager to manage the node. If you remove the node from the deployment manager cell, then use the administrative console and the scripting interface of the standalone application server node to manage the process.
You can create the profile using the Profile Management Tool or the manageprofiles command. If you create the profile with the manageprofiles command, specify app_server_root/profileTemplates/default for the -templatePath parameter to create this type of profile.
Use the custom profile, which belongs to a deployment manager cell, to make applications available to the Internet or to an intranet under the management of the deployment manager.
The deployment manager converts a custom profile to a managed node by adding the node into the cell. The deployment manager also converts an application server node into a managed node when you add an application server node into a cell. When either node is added to a cell, the node becomes a managed node. The node agent process is then instantiated on the managed node. The node agent acts on behalf of the deployment manager to control application server processes on the managed node. The node agent can start or stop application servers, for example.
A deployment manager can create multiple application servers on a managed node so long as the node agent process is running. Processes on the managed node can include cluster members that the deployment manager uses to balance the workload for heavily used applications.
Use the administrative console of the deployment manager to control all of the nodes that the deployment manager manages. You can also use the wsadmin scripting facility of the deployment manager to control any of the managed nodes. A custom profile does not have its own administrative console or scripting interface. You cannot manage the node directly with the wsadmin scripting facility.
A custom profile does not include default applications or a default server like the application server profile includes. A custom profile is an empty node. Add the node to the deployment manager cell. Then, you can use the administrative interface of the deployment manager to customize the managed node by creating clusters and application servers.
You can create the profile using the Profile Management Tool or the manageprofiles command. If you create the profile with the manageprofiles command, specify app_server_root/profileTemplates/managed for the -templatePath parameter to create this type of profile.
Profiles use the concept of a default profile when more than one profile exists. The default profile is set to be the default target for scripts that do not specify a profile. You can use the -profileName parameter with most of the scripts to enable the scripts to act on a profile other than the default profile.
The default profile name is:
<profile_type> <profile_number>
– is a value of AppSrv, Dmgr, Custom, AdminAgent, JobMgr, or SecureProxySrv.
<profile_number>
– is a sequential number that is used to create a unique profile name
Tip: When multiple profiles exist on a machine, certain commands require that you specify the -profileName parameter if the profile is not the default profile. In those cases, it might be easier to use the commands that are in the bin directory of each profile. When you issue one of these commands within the bin directory of a profile, the command acts on that profile unless the -profileName parameter specifies a different profile.
manageprofiles command
Managing profiles by using the graphical user interface
Managing profiles for non-root users
Deleting profiles
Creating management profiles with deployment managers
Creating custom profiles
Creating application server profiles
Using the “Manage Profiles Interactive” tool to create new profiles in WebSphere Application Server
Configuring port settings
Swinging profiles between product installations
WebSphere profile creation crashes on Windows 2019 environments
WebSphere Application Server Profile creation fails on doImportConfigArchive
How to delete the WAS profile completely using manageprofiles.sh command?
The manageprofiles.bat -listProfiles command fails to return any output
MustGather: Profile creation and removal problems with WebSphere Application Server
MustGather: Websphere Application Server profile creation failed due to JVMSHRC287E and JVMJ9VM015W
“IBM prides itself on delivering world class software support with highly skilled, customer-focused people. ”
Contact Support