Profiles in websphere

WebSphere installation is not complete until there is no any profile

Profiles:- basically profile is the set of the configuration files that are create run time environment to interact with  the WebSphere environment .

In WAS 7.0 there is five profiles that are generally used.

1.Cell profiles

2. App server profiles

3. Custom profiles

4. Management profiles



1 Cell profiles :-  cell is a special type of profile it create the one dmgr profile and one application server profile. when we create cell profile then it will create the package of the two profiles and auto federated to each other.

Admin tool :- it contain the one administrative tool
Access tool :-  http://host_name:admin_port/ibm/console
Example :- http://localhost:9060/ibm/console


2 App Server profiles :-  it is a application server profiles or also called stand alone or unmanaged node
                                   one jvm is also create with this profile which called server1 and also contain own administrative tool called admin console to administer self .

Access tool :-  http://host_name:admin_port/ibm/console


3 Custom profiles :- this profile is the empty node profile that is used when create a cluster then this profile has federated with dmgr profile. and there is no any administration tool to administer the node.

4 Management profiles :-  In this profiles we have three different management profile

1. Admin agent profiles
2. Job manager profiles
3. Deployment manager profiles

4-1 Admin agent profiles:- this profile manage the multiple stand alone profile from the single point of administration from the admin agent console we can administer to any application server profile.

Admin tool :- it contain the one administrative tool

Access tool :-  http://host_name:admin_port/ibm/console

4-2 Deployment manager profiles :- this is the most important profile in the was this profile provide the management capability to multiple federated node with dmgr  it has single point of administration to  multiple node there is one config file call master repository that contain the all federated node details also provide the many feature like cluster and HA and WLM.

Admin tool :- it contain the one administrative tool
Access tool :-  http://host_name:admin_port/ibm/console


4-3 Job manager profiles: - job manager profiles provide the management capability of the multiple stand alone profile and admin agent and deployment manager profiles from the single point.

Admin tool :- it contain the one administrative tool
Access tool :-  http://host_name:admin_port/ibm/console




Comments

Post a Comment

Popular posts from this blog

ERROR: Port values must be a positive integer between 0 and 65535. while install IBM Http Server 8.5.5

While Installing IBM Http server in Exception coming. [root@localhost IHS]# /WebSphere8.5/IM/InstallationManager/eclipse/tools/imcl install  com.ibm.websphere.IHSILAN.v85_8.5.5000.20130514_1044 - repositories /root/Desktop/Data/IHS_and_PluginSetup/IHS/repository.config -acceptLicense -showProgress                  25%                50%                75%                100% ------------------|------------------|------------------|------------------| ............................................................................ ERROR: Port values must be a positive integer between 0 and 65535. Solution to fix. Run Command Like this :-   [root@localhost IHS]# /WebSphere8.5/IM/InstallationManager/eclipse/tools/imcl install  com.ibm.websphere.IHSILAN.v85_8.5.5000.20130514_1044 -repositories /root/De...
Read more

How to remove the node from the deployment manager profile

Execute the below command to un-federate the profile from the dmgr Run this command from the bin directory of federated node. [root@localhost bin]# pwd /opt/IBM/WebSphere/AppServer/profiles/Custom01/bin [root@localhost bin]# ./removeNode.sh  ADMU0116I: Tool information is being logged in file            /opt/IBM/WebSphere/AppServer/profiles/Custom01/logs/removeNode.log ADMU0128I: Starting tool with the Custom01 profile ADMU2001I: Begin removal of node: localhostNode02 ADMU0009I: Successfully connected to Deployment Manager Server: localhost:8879 ADMU0505I: Servers found in configuration: ADMU0506I: Server name: nodeagent ADMU2010I: Stopping all server processes for node localhostNode02 ADMU0512I: Server nodeagent cannot be reached. It appears to be stopped. ADMU2021I: Removing all servers on this node from all clusters in the cell. ADMU2014I: Restoring original configuration. ADMU2017I: The local original configuratio...
Read more

What is clean start in websphere application server

For doing clean start / stop we follow some step. 1.First we take the jvm or clone to down. ---------------------------------------------------------------------   For taking the clone down we issue this command Command :- D:\IBM\WebSphere\AppServer\ AppSrv01\ bin>stopServer.bat  server1 ADMU0116I: Tool information is being logged in file            D:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\server1\stopServer. log ADMU0128I: Starting tool with the AppSrv01 profile ADMU3100I: Reading configuration for server: server1 ADMU3201I: Server stop request issued. Waiting for stop status. ADMU4000I: Server server1 stop completed. 2. Delete three directory under the profile root. Path : -   D:\IBM\WebSphere\AppServer\profiles\AppSrv01 These are files name .  temp , wstemp , tranlog Issue the below command to delete the directory Command :-    rm  -rf  temp wstemp  tran...
Read more