This small document contains some useful background information on WAS profiles. Use this information as part of automating WebSphere migrations and or installations.
You can also download this free guide in PDF format here
Profile types WAS 8.5.5.x
Templates for each profile are located in the <app_server_root>/profileTemplates directory.
Multiple 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 types of profiles:
Management profile with a deployment manager server
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.
Specify management for the -templatePath parameter and DEPLOYMENT_MANAGER for the -serverType parameter to create this type of management profile with the manageprofiles command.
Management profile with an administrative agent server
The basic function of the administrative agent is to provide a single interface to administer multiple unfederated 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/management for the -templatePath parameter and ADMIN_AGENT for the -serverType parameter to create this type of management profile.
Specify management for the -templatePath parameter and ADMIN_AGENT for the -serverType parameter to create this type of management profile with the manageprofiles command.
Management profile with a job manager server
The basic function of the job manager is to provide a single console to administer multiple base servers, multiple deployment managers, and do asynchronous job submission.
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/management for the -templatePath parameter and JOB_MANAGER for the -serverType parameter to create this type of management profile.
Specify management for the -templatePath parameter and JOB_MANAGER for the -serverType parameter to create this type of management profile with the manageprofiles command.
Application server profile
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 the status 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.
The application server profile is created by default if you do not specify the -templatePath parameter. You can alternatively specify default for the -templatePath parameter on the manageprofiles command to create the application server profile.
Cell profile
Use the cell profile to make applications available to the Internet or to an intranet under the management of the deployment manager.
Creation of a cell profile generates a deployment manager and a federated node in one iteration through the Profile Management Tool. The result is a fully functional cell on a given system.
To create a cell profile using the manageprofiles command, you must create two portions of the profile: the cell deployment manager portion and the cell node portion. Additionally, you can have only one cell deployment manager and one cell node associated with each other when you create a cell. The initial cell profile that you create with the manageprofiles command is equivalent to the cell profile you create with the Profile Management Tool. After you create the initial cell profile, you can create custom profiles or standalone profiles and federate the profiles into the deployment manager.
On the manageprofiles command, specify <app_server_root>/profileTemplates/cell/dmgr for the -templatePath parameter for the deployment manager and <app_server_root>/profileTemplates/cell/default for the -templatePath parameter for the cell node.
On the manageprofiles command, specify <app_server_root>/profileTemplates/cell/dmgr on the -templatePath parameter for the deployment manager and <app_server_root>/profileTemplates/cell/default on the -templatePath parameter for the cell node. You can read about the cell profile type in the article on creating a cell profile with the manageprofiles command.
After you create the two portions that make up the cell profile, you have a deployment manager and federated node. The federated node contains an application server and the default application, which contains the snoop servlet, the HitCount application, and the HelloHTML servlet.
Custom 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.
Profile types WAS 7
Templates for each profile are located in the <app_server_root>/profileTemplates directory.
Multiple 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 -templatePathoption. You can also specify profile templates that exist outside the profileTemplates directory, if you have any.
The manageprofiles command in the product can create the following types of profiles:
Management profile with a deployment manager server
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.
Management profile with an administrative agent server
The basic function of the administrative agent is to provide a single interface to administer multiple unfederated application servers.
You can create the management profile with an administrative agent 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 ADMIN_AGENT for the -serverType parameter to create this type of management profile.
Management profile with a job manager server
The basic function of the job manager is to provide a single console to administer multiple base servers, multiple deployment managers, and do asynchronous job submission.
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/management for the -templatePathparameter and JOB_MANAGER for the -serverType parameter to create this type of management profile.
Application server profile
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 the status 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 -templatePathparameter to create this type of profile.
Cell profile
Use the cell profile to make applications available to the Internet or to an intranet under the management of the deployment manager.
Creation of a cell profile generates a deployment manager and a federated node in one iteration through the Profile Management Tool. The result is a fully functional cell on a given system.
To create a cell profile using the manageprofiles command, you must create two portions of the profile: the cell deployment manager portion and the cell node portion. Additionally, you can have only one cell deployment manager and one cell node associated with each other when you create a cell. The initial cell profile that you create with the manageprofiles command is equivalent to the cell profile you create with the Profile Management Tool. After you create the initial cell profile, you can create custom profiles or standalone profiles and federate the profiles into the deployment manager.
On the manageprofiles command, specify <app_server_root>/profileTemplates/cell/dmgr for the -templatePath parameter for the deployment manager and <app_server_root>/profileTemplates/cell/default for the -templatePath parameter for the cell node.
After you create the two portions that make up the cell profile, you have a deployment manager and federated node. The federated node contains an application server and the default application, which contains the snoop servlet, the HitCount application, and the HelloHTML servlet.
|
![]()
|
IBM provide the Cell profile option, but I never personally use this because it uses default naming conventions, and you may not want to use the default profile names, and profile locations etc in your installation. |
Custom 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 -templatePathparameter to create this type of profile.
Secure proxy profile
Use the secure proxy server to take requests from the Internet and forward them to application servers. The secure proxy server resides in the DMZ.
You can create the profile using the manageprofiles command. If you create the profile with the manageprofiles command, specify <app_server_root>/profileTemplates/secureproxy for the –templatePath parameter to create this type of profile.
Profile Types WAS 6.1
Similar to WAS 7, but a few subtle differences
Profile types
Templates for each profile are located in the <app_server_root>/profileTemplates directory.
Multiple 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 installation root, if you have any.
The manageprofiles command in the Network Deployment product can create the following types of profiles:
Deployment manager profile
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.
Specify app_server_root/profileTemplates/dmgr for the -templatePath parameter to create this type of profile.
Application server profile
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 stand-alone 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 the status of a stand-alone application server.
Each stand-alone application server has 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 stand-alone 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 stand-alone 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 stand-alone application server node to manage the process.
Specify app_server_root/profileTemplates/default for the -templatePath parameter to create this type of profile.
Cell profile
Use the cell profile to make applications available to the Internet or to an intranet under the management of the deployment manager.
Creation of a cell profile generates a deployment manager profile and a federated node profile in one iteration through the Profile Management tool. The result is a fully functional cell on a given system.
To create a cell profile using the manageprofiles command, you must create two individual profiles: the cell deployment manager profile and the cell node profile. Additionally, you can have only one cell deployment manager profile and one cell node profile associated with each other when you create a cell. The initial cell profile that you create with the manageprofiles command is equivalent to the cell profile you create with the Profile Management tool. After you create the initial cell profile, you can create custom profiles or stand-alone profiles and federate the profiles into the deployment manager.
On the manageprofiles command, specify <app_server_root>/profileTemplates/cell/dmgr for the -templatePath parameter for the deployment manager profile and app_server_root/profileTemplates/cell/default for the -templatePath parameter for the cell node profile.
After you create the two profiles which make up the cell profile, they have a deployment manager and federated node. The federated node contains an application server and the default application, which contains the snoop servlet, the HitCount application, and the HelloHTML servlet.
Custom 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.
Otherwise, specify <app_server_root>/profileTemplates/managed for the -templatePath parameter to create this type of profile.
Example: Using predefined port numbers
File locations of default port values, which can show you how to craft your own portFiles.
This table lists the file locations of default port values by type of profile.
| Profile |
File path |
| Application server |
<app_server_root>/profileTemplates/default/actions/portsUpdate/portdef.props |
| Cell – application server portion |
<app_server_root>/profileTemplates/cell/dmgr/actions/portsUpdate/nodeportdef.props |
| Cell – deployment manager portion |
<app_server_root>/profileTemplates/cell/dmgr/actions/portsUpdate/portdef.props |
| Custom |
<app_server_root>/profileTemplates/managed/actions/portsUpdate/portdef.props |
| Management profile for a deployment manager server |
<app_server_root>/profileTemplates/management/actions/portsUpdate/dmgr.portdef.props |
| Management profile for an administrative agent server |
<app_server_root>/profileTemplates/management/actions/portsUpdate/adminagent.portdef.props |
| Management profile for a job manager server |
<app_server_root>/profileTemplates/management/actions/portsUpdate/jmgr.portdef.props |
| Secure proxy |
<app_server_root>/profileTemplates/secureproxy/actions/portsUpdate/portdef.props |
The manageprofiles command recommends initial port values when you do not explicitly set port values. You can use predefined port values instead.
The manageprofiles command recommends port values when the options of -defaultPorts, -startingPort, or -portsFile are not specified.
To customize the port values in the portdef.props file before creating your profile, perform the following steps. The following example creates the default profile. For other types of profiles, you must substitute the file path with the file path of the profile that you want to create.
Copy the <app_server_root>/profileTemplates/default/actions/portsUpdate/portdef.props file from the default profile template path and place a copy of the file in an arbitrary temporary directory such as:
![]() ![]() c:\temp\ports
![]() ![]() /temp/ports
In the new file, modify the port settings to specify your port values.
Create your profile with the manageprofiles command. Use the modified port values. Specify the location of your modified portdef.props file on the -portsFile parameter. Specify the -validatePorts parameter to ensure that ports are not reserved or in use. Use the following example as a guide:
![]() ![]()
manageprofiles.bat
-create
-profileName Wow_Profile
-profilePath profile_root
-templatePath <app_server_root>\profileTemplates\default
-nodeName Wow_node
-cellName Wow_cell
-hostName lorriemb
-portsFile C:\temp\ports\portdef.props
-validatePorts
![]() ![]() ![]() ![]()
manageprofiles.sh
-create
-profileName Wow_Profile
-profilePath profile_root
-templatePath <app_server_root>\profileTemplates\default
-nodeName Wow_node
-cellName Wow_cell
-hostName lorriemb
-portsFile \temp\ports\portdef.props
-validatePorts
Suppose that the portdef.props file has the following values:
WC_defaulthost=39080
WC_adminhost=39060
WC_defaulthost_secure=39443
WC_adminhost_secure=39043
BOOTSTRAP_ADDRESS=32809
SOAP_CONNECTOR_ADDRESS=38880
IPC_CONNECTOR_ADDRESS=39633
SAS_SSL_SERVERAUTH_LISTENER_ADDRESS=39401
CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS=39403
CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS=39402
ORB_LISTENER_ADDRESS=39100
DCS_UNICAST_ADDRESS=39353
SIB_ENDPOINT_ADDRESS=37276
SIB_ENDPOINT_SECURE_ADDRESS=37286
SIB_MQ_ENDPOINT_ADDRESS=35558
SIB_MQ_ENDPOINT_SECURE_ADDRESS=35578
SIP_DEFAULTHOST=35060
SIP_DEFAULTHOST_SECURE=35061
OVERLAY_UDP_LISTENER_ADDRESS=35062
OVERLAY_TCP_LISTENER_ADDRESS=35063
STATUS_LISTENER_ADDRESS=35064
After running the manageprofiles command to create your profile with the user defined port values, a success or fail result displays.
The manageprofiles command creates a copy of the current portdefs.props file in the profile_root\properties directory.
Use only one of the three port values parameters, -startingPort, -defaultPorts, or -portsFile with the manageprofiles command. The three parameters are mutually exclusive.
|
To learn more about the courses available from The Middleware Shop, please go to http://www.themiddlewareshop.com/products to see a full list of the current courses available.
Default profiles
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>:
<profile_type> 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
Addressing a profile in a multiprofile environment: 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.
Consulting
If you or your organization require support in architecture, performance tuning, automation or simply advice, then please contact me via my support site and request a conversation, where we can discuss your requirement.
About Steve
Steve is a seasoned passionate technology professional, strategist and leader.
An expert in technical communications, and adept in almost all forms of Internet and mobile related technology, Steve has time and time again proven his tenacity to improve systems around him and deliver.
Steve has worn many hats during his career such as Chief Technical Officer, Founding Member of several business ventures, Programmer, Systems Administrator, Architect, Blogger and Published Author to name a few.
Due to 20 years Industry experience in Middleware, Programming, Networks and Internet Technologies, He combines systems knowledge with efficient working methods and inter personal skills required to build effective relationship with clients and colleagues alike. Exceeding typical expectations in any role undertaken, Steve is certain to become a valuable asset within any organisation He joins.
Key Skills
• Leadership (Team, Project, Business, People).
• Architecture (Solutions, Information, Technical, Applications).
Simply, I help you deal with CANETI: Constant And Never Ending Technological Innovation
Specific IBM WebSphere skills:
- WebSphere Application Server (WAS Base, WAS ND & Liberty Profile & Liberty Runtime)
- Automation
- Security, SSL
- Dev Ops
- Architecture
- Performance Tuning
Middleware Integration Skills:
- .NET programming, and Architecture
- Java Programming, and Architecture
- SOA, SOAP and XML messaging
- JBoss Fuse, WMQ, IIB, Mule
Integration Skills:
- SOA
- Process Improvement
- ICD’s
- Messaging Architecture
- Governance
General Digital Architecture & Governance
- Lightweight Architectures
- Digital Strategy, platform stacks for example IAAS, PAAS, SAAS
- PCI DSS
Industry Qualifications & Recognition
- TOGAF 9.1
- IBM Champion 2013
![facebook]( "Share on Facebook")
![google_plus]( "Share on Google+")
![reddit]( "Share on Reddit")
![pinterest]( "Pin it with Pinterest")
![linkedin]( "Share on Linkedin")
![mail]( "Share by email")
