Websphere Profiles

Websphere Profiles


Profiles are set of files that represent a Websphere Application Server configuration.

Generally a Websphere Application Server installation takes 300MB. If you want to install more than one WAS it wastes the memory to overcome that we use the concept of profiles.

Websphere Application Server files are split into two categories, They are
  1. Product Binaries
  2. Configuration Files  

1. Product Binaries: Product binary files are set of shared read only Static file or  Binary files that are used to run on Application Server. So, using one server binary files we can install more than one application server with their own configuration.

2. Configuration Files: These are set of user customizable data files. It contains "Websphere Configuration", Installed applications, Resource Adopters, Properties, Logfiles, etc., 

Advantages of Profiles: 

  • Each profile uses the same product binary files
  • Simpler than multiple Websphere installations & updates
  • Less disk space

Managing Profiles:

  • PMT (Profile Management Tools) - Eclipse base GUI
  • ManageProfiles.sh (bat) - Command Line

Websphere Network Deployment Profiles: 

When we install " ND Packages " then it will comes with types of profiles use the same product files.

  1. Cell Profile
  2. DMGR (Deployment Manager) Profile -- (Management)
  3. Application Server Profile -- (Standalone)
  4. Custom Profile -- (Managed)
  5. Administrative Agent
  6. Job Manager
  7. Secure proxy






These Profiles are used in Production or Real Time.

    1. Cell Profile:  
  • It creates a instant cell
  • Creates both a Deployment Manager(DMGR) and a Federated Node 

    2. DMGR Profile:

  • It just creates a Deployment Manager
  • 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.

    3. Application Server Profile:

  • It just creates a Standalone application server
  • This is equivalent to Base or Express application server
  • Has a Node name, Cell name property and corresponding directories
  • Cell directory is over written upon federation

    4. Custom Profile:

  • It just creates an empty Node
  • Even Nodeagent is also not available
    5. Administrative Agent:

                The basic function of the administrative agent is to provide a single interface to administer multiple unfederated application servers.

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.

   6. Job Manager

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.

   7. Secure Proxy 

                  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.


Below are the sample commands to create various profiles using manageprofiles command .

Application Server Profile:

Go to <was-root>/bin 

./manageprofiles.sh -create -profileName appsrv01 -profilePath   <was_root>/profiles/appsrv01 -templatePath   <was_root>/profileTemplates/default -cellName appsrv01node01  -hostName node01.waslocal.com -nodeName node01


The expected outcome of it will be:

INSTCONFSUCCESS: Success: Profile appsrv01 now exists. Please consult <was_root>/profiles/appsrv01/logs/AboutThisProfile.txt for more information about this profile.

Please check the –help parameter of the manageprofiles shell in order to see all the available options for this command. 

DMGR Profile :

./manageProfiles.sh   -create   -profileName   Dmgr01  -templetPath    /opt/IBM/WebSphere/AppServer/profileTemplates/dmgr or management   -serverType   DEPLOYMENT_MANAGER   -hostname  your_ServerName


After creation it will show the path /opt/IBM/WebSphere/AppServer/Profiles/Dmgr01/logs/AboutThisProfile.txt  for to see more information about DMGR profile, Like Node_Name, Cell_Name, Host_Name, Admin_Security, AdminConsole_Port(9060), AdminConsole_SecurePort(9043), Management_BootstrapPort(9809), Management_SOAP(8878), Etc.,

Custom Profile:

./manageProfiles.sh   -create   -profileName   Custom01  -templetPath    /opt/IBM/WebSphere/AppServer/profileTemplates/managed

After creation it will show the path /opt/IBM/WebSphere/AppServer/Profiles/Custom01/logs/AboutThisProfile.txt
for to see more information about Custom profile


Comments

Post a Comment

Popular posts from this blog

IBM WebSphere - Synchronize a node (syncNode)

Image
  IBM WebSphere - Synchronize a node (syncNode) Before we get into synchronization, let's talk about nodes and the master configuration. The master configuration is a collection of XML files that contain all sorts of information about a cell, such as the security settings and the applications in the cell. A node contains one or more WebSphere application servers. When a managed nodes is federated into the dmgr, the node needs to be synchronized with the master configuration so that the node is using the dmgr configuration. The synchronization is always from Dmgr to Nodes and it never happens vise versa. If you made any changes from the node side it will be cleared during next synchronization process. Let's consider a common example. You make some change in the WebSphere admin console, and you are presented wit the Save option. Selecting save updates the master configuration. This will cause the node to be out of sync with the master configuration. To know if a node is synchroni...
Read more

Daily usage Linux Commands for Any Middleware Administration

Daily usage Linux Commands for Any Middleware Administration Processes related: ------------------ $ ps -ef | grep <process_name> ----- will show the process ID of the proces $ ps -eaf --> to see the Process ID's $ telnet <hostname> <Port_Number> --> It is used to check whether port(server) is listening or not $ scp    -r     file_Name     username@hostname:path  ----- If you want to copy a file from one linux server to another sever $ kill -9 PID ----- Killing an unwanted process $ kill -3 PID ----- Used to take thredDump of the process $ ssh username@servername --> Command used to login to server $ nslookup <host_name> --> Query the nameserver for the IP address of the given HOST optionally using a specified DNS server (To identify the server ip_address by using nslookup command ) $ crontab Minute Hour DayOfMonth Month DayOfWeek (eg: 30 08 10 06 * /home/was/full-backup) ----- Used to scheduled a job on Li...
Read more

Backup and Restore of WebSphere Application Server configuration

                      Backup & Restore of IBM WebSphere Application Server Configuration Backup configuration in  WebSphere One of the major activity that we can perform in Websphere as a pre-requisites when ever we intended to perform any major configuration changes like Fix Pack upgrade ,Interim Fix upgrade, JDK upgrade etc. For any mission critical application, taking frequent backups is essential for recovering from severe errors. In the case of WebSphere Application Server, setting up of the application server environment is a demanding task and it is not an easy to repeat the setup if something bad happens. So, its wise to take backups whenever we make the first setup or when we do configuration changes. Depending upon our diskspace availability two types of backups is possible . 1) Full Backup A full backup can be performed by running the ./backupConfig command from the<WAS-ROOT>/bin di...
Read more