Ibm Websphere Application Server, Websphere Middleware Admin

Thread-Dump is the snapshot of  the state of thread in JVM. thread dump are used to diagnose the application performance issue like deadlock and hung thread. Taking thread in Websphere application server . 1. generate thread dump through wsadmin command Step1 . cd /opt/IBM/WebSpeher/AppServer/Profiles/AppSrv01/bin ./wasadmin   -user wasadmin -password wasadmin Step 2. set the parameter <wsadmin> set jvm [$AdminControl completeObjectName type =JVM, process=<servername>,*] Step 3. Invoke the command. <wsadmin>$AdminControl invoke $objectName dumpThreads Execute this command three times in the interval of the atleast 3 or 4  second . Note :- See Real Example   [root@localhost bin]# ./wsadmin.sh -user wasadmin -password wasadmin WASX7209I: Connected to process "dmgr" on node localhostCellManager01 using SOAP connector;  The type of process is: DeploymentManager WASX7029I: For help, enter: "$Help help" wsadmin>s...

Heap Dump :-  Heap dump is basically snapshot of the all live object which is living in the heap memory and provide the details of memory which is consume by each and every object in the memory pool What is the use of heap dump :- With the help of heap-dump we can find the issue of out of memory and memory leakage issue and ensure the better performance of the jvm. We can generate the Heap dump two type. 1. Generate heap dump through wsadmin tool Step :-  Go to the profile bin of the respected server for Example:- Step1 . cd /opt/IBM/WebSpeher/AppServer/Profiles/AppSrv01/bin ./wasadmin   -user wasadmin -password wasadmin Step 2. set the parameter <wsadmin> set jvm [$AdminControl completeObjectName type =JVM, process=<servername>,*] Step 3. Invoke the command. <wsadmin>$AdminControl invoke $objectName generateHeapDump Execute this command three times in the interval of the atleast 3 or 4  second . See The Real Example:- ...

                              Cluster cluster is a logical name and  group of application server act as a single unit to perform the task and provide the  workload balance , high availability , fail over and scalability in Network deployment. There is two type cluster in websphere application server 1. Horizontal Cluster 2. Vertical Cluster Horizontal cluster :-    in horizontal cluster all nodes should be  in different physical machine and all nodes are federated with Dmgr cell . in this type of cluster if in case any nodes  hardware has  failed   then request will route to another nodes server to process. Vertical Cluster - In vertical cluster all configuration exist in the same physical machine or node in this type of clustering there is lot of chance for failure the system but thi...

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...

Execute the below command . Command :- [root@localhost bin]# pwd /opt/IBM/WebSphere/AppServer/profiles/AdminAgent01/bin [root@localhost bin]# ./deregisterNode.sh -profilePath /opt/IBM/WebSphere/AppServer/profiles/AppSrv04 ADMU0116I: Tool information is being logged in file            /opt/IBM/WebSphere/AppServer/profiles/AdminAgent01/logs/deregisterNode.log ADMU0128I: Starting tool with the AdminAgent01 profile ADMU8053I: Successfully connected to AdminAgent Server: localhost:8877 ADMU0505I: Servers found in configuration: ADMU0506I: Server name: server1 ADMU2010I: Stopping all server processes for node AppSrv04Node1 ADMU0512I: Server server1 cannot be reached. It appears to be stopped. ADMU8052I: Removing signers exchanged during node registration. ADMU8051I: Removed signers successfully. ADMU8009I: Begin deregistration of Application Server with path            /opt/IBM/WebSphere/AppServer/profiles/AppSrv0...

First we should know about what is admin agent profile. why its need. Basically admin agent profile is a management profile that provide the capabilities to manage multiple standalone profile from a single point administration from its admin console. after registration  stand alone profile with admin agent user will directly access the node.also user can access standalone console . Here see the example :- 1. First i will show you admin agent login window before stand alone profile registration. we have seen it showing only one node now that is itself node Registration of the stand alone with admin agent profile Command:-  [root@localhost bin]# pwd /opt/IBM/WebSphere/AppServer/profiles/AdminAgent01/bin [root@localhost bin]# ./registerNode.sh -profilePath /opt/IBM/WebSphere/AppServer/profiles/AppSrv04 ADMU0116I: Tool information is being logged in file            /opt/IBM/WebSphere/AppServer/profiles/AdminAgent01/logs/r...

Run the below command. 1. Start the Job Manager [root@localhost bin]# pwd /opt/IBM/WebSphere/AppServer/profiles/JobMgr01/bin [root@localhost bin]# ./startServer.sh jobmgr ADMU0116I: Tool information is being logged in file            /opt/IBM/WebSphere/AppServer/profiles/JobMgr01/logs/jobmgr/startServer.log ADMU0128I: Starting tool with the JobMgr01 profile ADMU3100I: Reading configuration for server: jobmgr ADMU3200I: Server launched. Waiting for initialization status. ADMU3000I: Server jobmgr open for e-business; process id is 4919 2. Stop the Job Manager [root@localhost bin]# pwd /opt/IBM/WebSphere/AppServer/profiles/JobMgr01/bin [root@localhost bin]# ./stopServer.sh jobmgr ADMU0116I: Tool information is being logged in file            /opt/IBM/WebSphere/AppServer/profiles/JobMgr01/logs/jobmgr/stopServer.log ADMU0128I: Starting tool with the JobMgr01 profile ADMU3100I: Reading configuration for s...

Run the below command. 1. Start the admin agent [root@localhost bin]# pwd /opt/IBM/WebSphere/AppServer/profiles/AdminAgent01/bin [root@localhost bin]# ./startServer.sh adminagent ADMU0116I: Tool information is being logged in file            /opt/IBM/WebSphere/AppServer/profiles/AdminAgent01/logs/adminagent/startServer.log ADMU0128I: Starting tool with the AdminAgent01 profile ADMU3100I: Reading configuration for server: adminagent ADMU3200I: Server launched. Waiting for initialization status. ADMU3000I: Server adminagent open for e-business; process id is 4707 2. Stop the admin agent  [root@localhost bin]# pwd /opt/IBM/WebSphere/AppServer/profiles/AdminAgent01/bin [root@localhost bin]# ./stopServer.sh adminagent ADMU0116I: Tool information is being logged in file            /opt/IBM/WebSphere/AppServer/profiles/AdminAgent01/logs/adminagent/stopServer.log ADMU0128I: Starting tool with the AdminAg...

Follow some basic steps to create the application server profile through manageprofiles command. 1. Open the shell and cmd tool 2. Go to the was_bin location 3. Execute the below command Exmpale :- '[root@localhost bin]# pwd /opt/IBM/WebSphere/AppServer/bin [root@localhost bin]# ./manageprofiles.sh -create -prfoileName Jobmgr01 -templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/management/ -serverType JOB_MANAGER  -cellName Jobmgr01Cell01 -nodeName JobmgrNode01 -enableAdminSecurity -userName wasadmin -password wasadmin INSTCONFSUCCESS: Success: Profile JobMgr01 now exists. Please consult /opt/IBM/WebSphere/AppServer/profiles/JobMgr01/logs/AboutThisProfile.txt for more information about this profile. For more information about the profile to see the log inside the profile log directory  Path:-  /opt/IBM/WebSphere/AppServer/profiles/JobMgr01/logs/ [root@localhost logs]# cat AboutThisProfile.txt  Application server environment to create: Ma...

Follow some basic steps to create the application server profile through manageprofiles command. 1. Open the shell and cmd tool 2. Go to the was_bin location 3. Execute the below command Exmpale :- '[root@localhost bin]# pwd /opt/IBM/WebSphere/AppServer/bin [root@localhost bin]# ./manageprofiles.sh -create -profileName AdminAgent01 -templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/management/ -serverType ADMIN_AGENT -cellName Adminagent01Cell01 -nodeName AdminagentNode01 -enableAdminSecurity -userName wasadmin -password wasadmin INSTCONFSUCCESS: Success: Profile AdminAgent01 now exists. Please consult /opt/IBM/WebSphere/AppServer/profiles/AdminAgent01/logs/AboutThisProfile.txt for more information about this profile. For more information about the profile to see the log inside the profile log directory  Path:-  /opt/IBM/WebSphere/AppServer/profiles/AdminAgent01/logs [root@localhost logs]# cat AboutThisProfile.txt  Application server...

Follow some basic steps to create the application server profile through manageprofiles command. 1. Open the shell and cmd tool 2. Go to the was_bin location 3. Execute the below command Exmpale :- '[root@localhost bin]# pwd /opt/IBM/WebSphere/AppServer/bin [root@localhost bin]# ./manageprofiles.sh -create -profileName Dmgr02 -templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/management/ -cellName Dmgr02Cell -nodeName Dmgr02Node1 -enableAdminSecurity -userName wasadmin -password wasadmin    INSTCONFSUCCESS: Success: Profile Dmgr02 now exists. Please consult /opt/IBM/WebSphere/AppServer/profiles/Dmgr02/logs/AboutThisProfile.txt for more information about this profile. For more information about the profile to see the log inside the profile log directory  Path:-  /opt/IBM/WebSphere/AppServer/profiles/Dmgr02/logs [root@localhost logs]# cat AboutThisProfile.txt  Application server environment to create: Management Location: /opt/IBM...

Follow some basic steps to create the application server profile through manageprofiles command. 1. Open the shell and cmd tool 2. Go to the was_bin location 3. Execute the below command Exmpale :- '[root@localhost bin]# pwd /opt/IBM/WebSphere/AppServer/bin [root@localhost bin]# ./manageprofiles.sh -create -profileName AppSrv04 -templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/default/ -cellName AppSrv04Cell -nodeName AppSrv04Node1 -enableAdminSecurity -userName wasadmin -password wasadmin INSTCONFSUCCESS: Success: Profile AppSrv04 now exists. Please consult /opt/IBM/WebSphere/AppServer/profiles/AppSrv04/logs/AboutThisProfile.txt for more information about this profile. For more information about the profile to see the log file Path :-  /opt/IBM/WebSphere/AppServer/profiles/AppSrv04/logs [root@localhost logs]# cat AboutThisProfile.txt  Application server environment to create: Application server Location: /opt/IBM/WebSphere/AppServer/profil...

Synchronization:- Synchronization is process to update  all changes from master configuration to local configuration. Why Synchronization Need :-  After federation of the AppSrv or Custom node with the dmgr its own administrative console has disabled . Dmgr has manage the multiple node from a single point of administration .if any changes are require for AppSrv or Custom node then those changes are done from the dmgr console for corresponding node. first changes are update in dmgr master config for that node after that those changes are update in local config of that node .changes are not working until local config has not update. Master Configuration :-   Basically Deployment  Manager configuration is called master configuration  . whenever make any change in the federated node then first it update in the master repositories and after that changes fill update in local node configuration. Local Configuration :-   Federated node configuration ...

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...

I am explaining how to do  cell start and stop Cell Start:- 1.   ./startManager.sh       ./startNode.sh       ./startServer.sh Cell Stop :- 2.  ./stopServer.sh      ./stopNode.sh      ./stopManager.sh This is the way.