About Me.

My self Adinarayana working as Implementation Application DBA with advanced technologies like RAC/PCP,OID/SSO,DMZ,Exadata and Fusion Middleware i.e Demantra,Application Server,SOA,FMW,BPEL and UPK. Created this blog to share the useful information related to DBA and Application DBA Your comments and suggestions are most welcome. Disclaimer: Please note all the views and opinions expressed in this site are my own. It's not recommend to use the fixes/suggestions provided in this site directly in production instance, please test them before implementing.
Showing posts with label Weblogic. Show all posts
Showing posts with label Weblogic. Show all posts

Saturday, January 4, 2014

Weblogic Patching

1.Command-line interface:

1.This is the syntax for the command to view the downloaded patches as below:
./bsu.sh -prod_dir=<weblogic_home> -patch_download_dir=<download dir of patch> -status=downloaded -view -verbose

For example:
./bsu.sh -prod_dir=/opt/bea/weblogic92 -patch_download_dir=/opt/bea/utils/bsu/cache_dir -status=downloaded -view -verbose

2.This is the syntax for the command to install a patch:
./bsu.sh -prod_dir=<weblogic_home> -patchlist=<patchID> -verbose -install

For example:
./bsu.sh -prod_dir=/opt/bea/weblogic92 -patchlist=E5W8 -verbose -install
./bsu.sh -prod_dir=/opt/bea/weblogic92 -patchlist=E5W8,WGQJ -verbose -install

3.This is the syntax for the command to check if the patch is installed:
./bsu.sh -prod_dir=<weblogic_home> -patch_download_dir=<download dir of patch> -status=applied -verbose -view

For example:
./bsu.sh -prod_dir=/opt/bea/weblogic92 -status=applied -verbose -view

Patch Verification:

Run following to verify patch application

$ ./bsu.sh -view -status=applied -prod_dir=$WL_HOME -verbose | grep PSU

OR

$ ./bsu.sh -view -status=applied -prod_dir=$WL_HOME -verbose | grep D33T


2. Applying the patch to the classpath manually:


You can apply the patch to the system manually by extracting the actual patch and adding it to the classpath on the system:

1.Extract the actual patch jar file. It will be in the form <patch_id>.jar (for example: E5W8.jar).
Inside this jar file is the actual patch jar file, which will be of the form CR326566_92mp3.jar. Extract the latter file for the following steps.

2.Add the extracted jar file as the first element of the classpath of the Admin server as well as the managed servers in the domain.

3.If you are starting servers using the WebLogic Server startup script, update the classpath in the startup script like this:

set CLASSPATH=<PATCH_DIR>\jars\CR326566_92mp3.jar;%CLASSPATH% (Windows)
CLASSPATH=<PATCH_DIR>/jars/CR326566_92mp3.jar:$CLASSPATH (UNIX)

where PATCH_DIR is the directory on the machine where you extracted/saved the patch file.

4.Similarly, if you are starting servers using Node Manager, add the patch jar to the beginning of the Class Path argument in the Server Start
tab for the server(s).

NOTE: Applying the patch to the classpath manually (approach 2) is recommended only for releases prior to WLS 9.1. Smart Update should be used when it is available as it provides patch conflict and dependency checking.

Patch Report:

The bug numbers were obtained by running a report against the current installation, looking for the patch IDs, and then checking the JAR file names:

cd $MW_HOME/utils/bsu
./bsu.sh -report

Sample Patch output:

[oracle@weblogic bsu]$ pwd
/oracle/Middleware/utils/bsu

[oracle@weblogic bsu]$ ./bsu.sh -prod_dir=/oracle/Middleware/wlserver_10.3 -patchlist=L51R -verbose -install
Checking for conflicts..
No conflict(s) detected

Starting installation of Patch ID: L51R
Installing /oracle/Middleware/utils/bsu/cache_dir/L51R.jar
Extracting /oracle/Middleware/patch_wls1036/patch_jars/BUG16619891_1036.jar
Extracting /oracle/Middleware/patch_wls1036/patch_jars/com.bea.core.stax2_2.0.0.0_3-0-3.jar
Updating /oracle/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar
Old manifest value: Class-Path=
New manifest value: Class-Path=../../../patch_jars/BUG16619891_1036.jar ../../../patch_jars/com.bea.core.stax2_2.0.0.0_3-0-3.jar
Backing up /oracle/Middleware/wlserver_10.3/server/lib/jms-xa-adp.rar into /oracle/Middleware/patch_wls1036/backup/backup.jar
Backing up /oracle/Middleware/wlserver_10.3/server/lib/jdbcdrivers.xml into /oracle/Middleware/patch_wls1036/backup/backup.jar
Backing up /oracle/Middleware/wlserver_10.3/server/lib/wlclient.jar into /oracle/Middleware/patch_wls1036/backup/backup.jar
Backing up /oracle/Middleware/wlserver_10.3/server/lib/schema/weblogic-domain-binding.jar into /oracle/Middleware/patch_wls1036/backup/backup.jar
Backing up /oracle/Middleware/wlserver_10.3/server/lib/jms-notran-adp.rar into /oracle/Middleware/patch_wls1036/backup/backup.jar
Backing up /oracle/Middleware/wlserver_10.3/server/lib/webserviceclient+ssl.jar into /oracle/Middleware/patch_wls1036/backup/backup.jar
Backing up /oracle/Middleware/wlserver_10.3/common/bin/wlsifconfig.sh into /oracle/Middleware/patch_wls1036/backup/backup.jar
Backing up /oracle/Middleware/wlserver_10.3/server/lib/wseeclient.jar into /oracle/Middleware/patch_wls1036/backup/backup.jar
Backing up /oracle/Middleware/modules/com.bea.core.descriptor.wl.binding_1.4.0.0.jar into /oracle/Middleware/patch_wls1036/backup/backup.jar
Backing up /oracle/Middleware/wlserver_10.3/server/lib/consoleapp/webapp/WEB-INF/lib/console.jar into /oracle/Middleware/patch_wls1036/backup/backup.jar
Extracting /oracle/Middleware/wlserver_10.3/server/lib/jms-xa-adp.rar
Extracting /oracle/Middleware/wlserver_10.3/server/lib/jdbcdrivers.xml
Extracting /oracle/Middleware/wlserver_10.3/bugsfixed/WLS-PSU-bugsfixed.txt
Extracting /oracle/Middleware/wlserver_10.3/server/lib/wlclient.jar
Extracting /oracle/Middleware/modules/com.bea.core.stax2_2.0.0.0_3-0-3.jar
Extracting /oracle/Middleware/wlserver_10.3/server/lib/schema/weblogic-domain-binding.jar
Extracting /oracle/Middleware/wlserver_10.3/server/lib/jms-notran-adp.rar
Extracting /oracle/Middleware/wlserver_10.3/server/lib/webserviceclient+ssl.jar
Extracting /oracle/Middleware/wlserver_10.3/common/bin/wlsifconfig.sh
Extracting /oracle/Middleware/wlserver_10.3/server/lib/wseeclient.jar
Extracting /oracle/Middleware/modules/com.bea.core.descriptor.wl.binding_1.4.0.0.jar
Extracting /oracle/Middleware/wlserver_10.3/bugsfixed/16619891-WLS-10.3.6.0.5_PSU_WebServices-ClientSide-Configuration-README.txt
Extracting /oracle/Middleware/wlserver_10.3/server/lib/consoleapp/webapp/WEB-INF/lib/console.jar
Backing up /oracle/Middleware/wlserver_10.3/server/lib/wls-api.jar into /oracle/Middleware/patch_wls1036/backup/backup.jar
Backing up /oracle/Middleware/modules/com.bea.core.bea.opensaml_1.0.0.0_6-2-0-0.jar into /oracle/Middleware/patch_wls1036/backup/backup.jar
Backing up /oracle/Middleware/modules/com.bea.core.bea.opensaml2_1.0.0.0_6-2-0-0.jar into /oracle/Middleware/patch_wls1036/backup/backup.jar
Backing up /oracle/Middleware/wlserver_10.3/server/lib/wljmsclient.jar into /oracle/Middleware/patch_wls1036/backup/backup.jar
Backing up /oracle/Middleware/wlserver_10.3/server/lib/wseeclient.zip into /oracle/Middleware/patch_wls1036/backup/backup.jar
Backing up /oracle/Middleware/wlserver_10.3/server/lib/webserviceclient.jar into /oracle/Middleware/patch_wls1036/backup/backup.jar
Backing up /oracle/Middleware/wlserver_10.3/server/lib/wlsaft3client.jar into /oracle/Middleware/patch_wls1036/backup/backup.jar
Backing up /oracle/Middleware/wlserver_10.3/server/lib/wlthint3client.jar into /oracle/Middleware/patch_wls1036/backup/backup.jar
Backing up /oracle/Middleware/wlserver_10.3/server/lib/wlsafclient.jar into /oracle/Middleware/patch_wls1036/backup/backup.jar
Extracting /oracle/Middleware/wlserver_10.3/server/lib/wls-api.jar47002.tmp
Merging /oracle/Middleware/wlserver_10.3/server/lib/wls-api.jar47002.tmp with /oracle/Middleware/wlserver_10.3/server/lib/wls-api.jar
Extracting /oracle/Middleware/modules/com.bea.core.bea.opensaml_1.0.0.0_6-2-0-0.jar45141.tmp
Merging /oracle/Middleware/modules/com.bea.core.bea.opensaml_1.0.0.0_6-2-0-0.jar45141.tmp with /oracle/Middleware/modules/com.bea.core.bea.opensaml_1.0.0.0_6-2-0-0.jar
Extracting /oracle/Middleware/modules/com.bea.core.bea.opensaml2_1.0.0.0_6-2-0-0.jar55283.tmp
Merging /oracle/Middleware/modules/com.bea.core.bea.opensaml2_1.0.0.0_6-2-0-0.jar55283.tmp with /oracle/Middleware/modules/com.bea.core.bea.opensaml2_1.0.0.0_6-2-0-0.jar
Extracting /oracle/Middleware/wlserver_10.3/server/lib/wljmsclient.jar63219.tmp
Merging /oracle/Middleware/wlserver_10.3/server/lib/wljmsclient.jar63219.tmp with /oracle/Middleware/wlserver_10.3/server/lib/wljmsclient.jar
Extracting /oracle/Middleware/wlserver_10.3/server/lib/wseeclient.zip32371.tmp
Merging /oracle/Middleware/wlserver_10.3/server/lib/wseeclient.zip32371.tmp with /oracle/Middleware/wlserver_10.3/server/lib/wseeclient.zip
Extracting /oracle/Middleware/wlserver_10.3/server/lib/webserviceclient.jar65040.tmp
Merging /oracle/Middleware/wlserver_10.3/server/lib/webserviceclient.jar65040.tmp with /oracle/Middleware/wlserver_10.3/server/lib/webserviceclient.jar
Extracting /oracle/Middleware/wlserver_10.3/server/lib/wlsaft3client.jar2476.tmp
Merging /oracle/Middleware/wlserver_10.3/server/lib/wlsaft3client.jar2476.tmp with /oracle/Middleware/wlserver_10.3/server/lib/wlsaft3client.jar
Extracting /oracle/Middleware/wlserver_10.3/server/lib/wlthint3client.jar51953.tmp
Merging /oracle/Middleware/wlserver_10.3/server/lib/wlthint3client.jar51953.tmp with /oracle/Middleware/wlserver_10.3/server/lib/wlthint3client.jar
Extracting /oracle/Middleware/wlserver_10.3/server/lib/wlsafclient.jar47059.tmp
Merging /oracle/Middleware/wlserver_10.3/server/lib/wlsafclient.jar47059.tmp with /oracle/Middleware/wlserver_10.3/server/lib/wlsafclient.jar
Result: Success

[oracle@weblogic bsu]$  ./bsu.sh -view -status=applied -prod_dir=$WL_HOME -verbose | grep L51R
Patch ID:          L51R
PatchContainer:    L51R.jar

Post Verification:

[oracle@weblogic bsu]$ . $WL_HOME/server/bin/setWLSEnv.sh
CLASSPATH=/oracle/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/oracle/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/oracle/middleware/jdk1.7.0_25/lib/tools.jar:/oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/oracle/Middleware/modules/features/weblogic.server.modules_10.3.6.0.jar:/oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/oracle/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/oracle/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/oracle/middleware/jdk1.7.0_25/lib/tools.jar:/oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/oracle/Middleware/modules/features/weblogic.server.modules_10.3.6.0.jar:/oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar

PATH=/oracle/Middleware/wlserver_10.3/server/bin:/oracle/Middleware/modules/org.apache.ant_1.7.1/bin:/oracle/middleware/jdk1.7.0_25/jre/bin:/oracle/middleware/jdk1.7.0_25/bin:/oracle/Middleware/wlserver_10.3/server/bin:/oracle/Middleware/modules/org.apache.ant_1.7.1/bin:/oracle/middleware/jdk1.7.0_25/jre/bin:/oracle/middleware/jdk1.7.0_25/bin:/oracle/Middleware/jdk1.7.0_25/bin:/oracle/Middleware/jdk1.7.0_25/bin:/oracle/Middleware/jdk1.7.0_25/bin:/oracle/Middleware/jdk1.7.0_25/bin:/oracle/Middleware/jdk1.7.0_25/bin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/oracle/bin:/home/oracle/bin:/home/oracle/bin:/home/oracle/bin:/home/oracle/bin

Your environment has been set.
[oracle@weblogic bsu]$  java weblogic.version

WebLogic Server 10.3.6.0.5 PSU Patch for BUG16619891 Tue Apr 23 13:24:29 IST 2013
WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050

Use 'weblogic.version -verbose' to get subsystem information

Use 'weblogic.utils.Versions' to get version information for all modules

Removing Patch:

[oracle@weblogic bsu]$ ./bsu.sh -prod_dir=/oracle/Middleware/wlserver_10.3 -patchlist=L51R -verbose -remove
Checking for conflicts..
No conflict(s) detected

Starting removal of Patch ID: L51R
Removing /oracle/Middleware/wlserver_10.3/bugsfixed/WLS-PSU-bugsfixed.txt
Removing /oracle/Middleware/modules/com.bea.core.stax2_2.0.0.0_3-0-3.jar
Restoring /oracle/Middleware/wlserver_10.3/server/lib/wls-api.jar from /oracle/Middleware/patch_wls1036/backup/backup.jar
Restoring /oracle/Middleware/modules/com.bea.core.descriptor.wl.binding_1.4.0.0.jar from /oracle/Middleware/patch_wls1036/backup/backup.jar
Restoring /oracle/Middleware/wlserver_10.3/server/lib/jms-notran-adp.rar from /oracle/Middleware/patch_wls1036/backup/backup.jar
Restoring /oracle/Middleware/wlserver_10.3/server/lib/jms-xa-adp.rar from /oracle/Middleware/patch_wls1036/backup/backup.jar
Restoring /oracle/Middleware/wlserver_10.3/server/lib/wlthint3client.jar from /oracle/Middleware/patch_wls1036/backup/backup.jar
Restoring /oracle/Middleware/wlserver_10.3/common/bin/wlsifconfig.sh from /oracle/Middleware/patch_wls1036/backup/backup.jar
Restoring /oracle/Middleware/modules/com.bea.core.bea.opensaml_1.0.0.0_6-2-0-0.jar from /oracle/Middleware/patch_wls1036/backup/backup.jar
Restoring /oracle/Middleware/wlserver_10.3/server/lib/jdbcdrivers.xml from /oracle/Middleware/patch_wls1036/backup/backup.jar
Restoring /oracle/Middleware/wlserver_10.3/server/lib/schema/weblogic-domain-binding.jar from /oracle/Middleware/patch_wls1036/backup/backup.jar
Restoring /oracle/Middleware/wlserver_10.3/server/lib/webserviceclient+ssl.jar from /oracle/Middleware/patch_wls1036/backup/backup.jar
Restoring /oracle/Middleware/wlserver_10.3/server/lib/wljmsclient.jar from /oracle/Middleware/patch_wls1036/backup/backup.jar
Restoring /oracle/Middleware/wlserver_10.3/server/lib/wlclient.jar from /oracle/Middleware/patch_wls1036/backup/backup.jar
Restoring /oracle/Middleware/wlserver_10.3/server/lib/webserviceclient.jar from /oracle/Middleware/patch_wls1036/backup/backup.jar
Restoring /oracle/Middleware/wlserver_10.3/server/lib/wlsafclient.jar from /oracle/Middleware/patch_wls1036/backup/backup.jar
Restoring /oracle/Middleware/wlserver_10.3/server/lib/wseeclient.jar from /oracle/Middleware/patch_wls1036/backup/backup.jar
Restoring /oracle/Middleware/wlserver_10.3/server/lib/consoleapp/webapp/WEB-INF/lib/console.jar from /oracle/Middleware/patch_wls1036/backup/backup.jar
Restoring /oracle/Middleware/wlserver_10.3/server/lib/wlsaft3client.jar from /oracle/Middleware/patch_wls1036/backup/backup.jar
Restoring /oracle/Middleware/wlserver_10.3/server/lib/wseeclient.zip from /oracle/Middleware/patch_wls1036/backup/backup.jar
Restoring /oracle/Middleware/modules/com.bea.core.bea.opensaml2_1.0.0.0_6-2-0-0.jar from /oracle/Middleware/patch_wls1036/backup/backup.jar
Removing /oracle/Middleware/patch_wls1036/patch_jars/BUG16619891_1036.jar
Removing /oracle/Middleware/patch_wls1036/patch_jars/com.bea.core.stax2_2.0.0.0_3-0-3.jar
Updating /oracle/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar
Old manifest value: Class-Path= ../../../patch_jars/BUG16619891_1036.jar ../../../patch_jars/com.bea.core.stax2_2.0.0.0_3-0-3.jar
New manifest value: Class-Path=
Result: Success

Saturday, July 20, 2013

Important Files and their locations

1.$DomainHome/$serverName/bin
Descrition:
Contains all the shell script files which is being used to start/stop and contains configuration for Admin and Managed servers.

Important Files:
setDomainEnv.sh
startWebLogic.sh
stopWebLogic.sh

2.$DomainHome/$serverName/config
Descrition:
Contains configuration files all important components e.g.  Domain configurtaion,  JMS, JDBC etc

Important Files:
config.xml
jdbc config files
jms config files
fmwconfig files etc

3.$DomainHome/$serverName/osb/config
Description:
This directory mainly contains all the OSB artifats e.g. Proxy Services, business Services, XSD, Xquery etc, whatever we do from OSB console, most of stuff get store
here only.
All the OSB artifacts

4.$DomainHome/$serverName/osb/config/core/_static/Ref_Store
Description:
This folder contains files having reference to OSB proxy and business services which are tagged with JMS as consumer. This directory helps during cleanup process of OSB deployment. There could be multiple OSB services get tagged with queue which could cause issues, this directory contents will help to clean that.
.str files for JMS MDB artifacts

5.$DomainHome/$serverName/sbgen
Description:
This folder contains MDBs for JMS queues, which could be used for any OSB  Proxy service or JAVA application.
ear files e.g. _ALSB_1341965872872.ear

6.$DomainHome/$serverName/sbgen/alsbTempJars
Description:
This folder contains the .jar files which Proxy services are using via JAVA Callout action.
jar files  e.g. tempCreateProcess8557633063030887848.jar

7.$DomainHome/$serverName/servers/$serverName/adr
Description:
Contains all diagnostic related data, if you have configured the Weblogic Diagnostic Framework e.g. In the event of server crash a report get generated etc, in this
case a thread dumps file will generated here, also contains JMS, Datasource stats etc,  good for investigation purpose.

Important Files:
jvm_threads.txt, dms_metrics.txt

8.$DomainHome/$serverName/servers/$serverName/data/store
Description:
This directory contains the persistent file store for weblogic servers which is used for normal functionality and diagnostic functionality. Weblogic has 7 internal components e.g. JMS Messages, JTA logs, EJB Timer services, Diagnostic services etc. which uses these persistent file store.

Important Files:
_WLS_$serverName000000.DAT
_WLS_DIAGNOSTICS000000.DAT

9.$DomainHome/$serverName/servers/$serverName/data/ldap
Description:
Contains LDAP related files, contains security realm details etc.  If you delete this folder, you will lose all security realm users details exist in Weblogic Admin console.

Important Files:
EmbeddedLDAP.data
changelog.data
changelog.index etc

10.$DomainHome/$serverName/servers/$serverName/data/console
Description:
Store the Admin console preference.

Important Files:
ConsolePreferences.xml

11.$DomainHome/$serverName/servers/$serverName/security
Description:
This file contains encrypted weblogic username and password, used while starting the server.

Important Files:
boot.properties

12.$DomainHome/$serverName/servers/$serverName/tmp
Description:
This folder contains all the artifacts which is been deployed in servers, alternatively can be seen from "deployment" section from Weblogic Admin Server console, included JMS MDB artifacts as well.
All the Library like this

Important Files:
adf.oracle.businesseditor
adf.oracle.domain etc
ALSB Logging
ALSB Publish
em
File Transport Provider components etc

13.$DomainHome/$serverName/servers/stage
Description:
This is stagging directory, during server startup process, JMS MDB, J2EE, War application get copied from Admin server to Managed server at this stage directory and then Managed server refer to local stage directory for deployment and things moved from Stage to 'tmp' directory. Note: for admin server you will not see this directory.

Important Files:
_ALSB_1352464196062 etc

14.$DomainHome/$serverName/servers/$serverName/logs
Description:
Contains all the logs files for troubleshooting purpose.

Important Files:
access.log,
AdminServer.log
ManagedServer.log
gc.log
domain.log
AdminServer.out
ManagedServer.out files

15.$DomainHome/$serverName/servers/sysman/log
Description:
Contains Management Service logs and trace file for troubleshooting purpose.

Important Files:
emoms.log
emoms.trc

16.$DomainHome/$serverName/servers/cache
Description:
Contains all the cached information weblogic uses directory to store cache for various components e.g. web tire related cache, JMS cache, data sources, EJB cache etc.
.class files

Weblogic Server Basic Components

Weblogic Server Basic Components

Below are the basic components of weblogic server


Domain:


Domain is a group of weblogic server resources like admin server, managed server, jms, connection pool, data sources etc or whatever the resource you know of weblogic server since domain is the basic unit you have to create after installation and everything created and configured under a domain.

It can be possible to create multiple domains from a single installation and each domain has it's own resources but this is recommended only on development environment where you may want to test different applications or different customer applications on different domain. All domains are independent of each other.


Admin Server & Admin Console

Admin server is a central unit which is used to configure and monitor a domain resources. it provides a browser or GUI based console called admin console for configuration and monitoring of the domain resources.

Admin server is also a server instance which have all the capabilities just like we have on managed servers ( see next post for managed server ) but since it's a central repository for the domain configuration so it's not recommended to used it as a managed server but you can use it as a managed server on non production environments for testing purpose.


Managed Server

A managed server is an instance of weblogic server which is used to host ( deploy in terms of weblogic ) your applications and associate other domain resources with that. For example you create and deploy jar, ear, ear etc files and deploy on managed servers and after that create connnection pools, data source and associated with your managed server to let your application connect and get connection from database.

When you start a managed server it connects to admin server to get configuration and other deployment settings.

A domain can have multiple managed servers ( no upper limit of managed servers, you can create as many as you want only considering your hardware configuration ). They all can be independent servers or can be grouped into cluster to get scalability, availability, maintainability etc ( see below for cluster ).


Machine


A machine is a logical representation of the physical machine (computer) that hosts one or more WebLogic Server instances. or in a simple word you can say Machine is a host on which your weblogic server is running. When you create and configure a machine you need to configure node manager and for that you need to define the host on which your node manager is running ( actual host or called machine ) as well as node manager port ( see below for node manager )


Node Manager

Node Manager is a Java utility or service which runs as a separate process from WebLogic Server and allows you to perform common operations tasks related with Managed Servers  regardless of its location with respect to its Administration Server.

Use of Node Manager is optional but it provides valuable benefits if your WebLogic Server environment hosts applications with high

Node manager is used to start or stop remote managed servers, remote managed servers means the servers distributed or configured on different machines or host, like In case of production where we ran multiple managed servers across different hosts in a single domain to get high availability, in that case all servers are distributed across multiple hosts however control via single admin console. make sure you have node manager running on each host and a machine configured via admin console for each host and respective managed server(s) associated with respective machine.

It provides the capability to auto health checking of managed servers and restart it automatically in case any server goes down.

Note :- Node manager is a independent java based utility which has not any dependency on weblogic or vice versa, so in case your node manager goes down there is no impact on your weblogic server running instances.


Cluster

Cluster is a group of manager servers work together to achieve high availability, scalability and for lots of other benefits. It appears to client as a single instance. All clustered servers can be on same or distributed across difference machines ( but in same cluster and domain ).  

Use of cluster provides the benefits of scalability, maintainability, high availability, load balancing, failover capabilities etc.