Ramesh Challa -Middleware /Devops Technology Blog

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

 Monitoring Policy on Websphere Application Server       When ever JVM goes down or unreachable or JVM ran into OOM( Out of Memory ) ,explicitly user will be notified by Application team or monitoring team till that time Application will be un reachable or down. This will be potentially an impact and this need to have a manual efforts or intervention to start the JVM or Services .                                                   To avoid this Websphere has a feature called monitoring policy which will monitor the health of the JVM process by nodeagent and start it when ever JVM goes down or un reachable or ran into OOM. We don't need any manual intervention needed until and unless if Nodeagent also fails to restart the JVM process.  In order for the Nodeagent to intervene and automatically restart a failed ap...

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

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

                     Websphere Commands Here is a quick guide about how to Start and Stop Application Server, Node Agent and Deployment Manager in WebSphere Application Server. Stop Application Server: Go to the /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin folder and run: ./stopServer.sh <Server Name or JVM Name> -user <username> -password <password> Stop Node Agent: Go to the respective profile bin /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin folder and run: ./stopNode.sh -user <username> -password <password> Stop Deployment Manager: Go to the /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin folder and run: ./stopManager.sh -user <username> -password <password> or ./stopServer.sh <DMGR Server Name> -user <username> -password <password> Start Deployment Manager Go to the /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin folder and run: ./startManager.sh or ...

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 Product Binaries Configuration Files    1. Product Binaries: P roduct 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 ...