How To Start/Stop Weblogic AdminServer Using WLST?

Summary

1) Start NodeManager
2) Connect To NodeManager
3) Start AdminServer
4) Stop AdminServer

       a) Connect To AdminServer
       b) Stop The AdminServer

 

1.Start NodeManager

wls:/offline> startNodeManager(verbose='true',NodeManagerHome='/oracle/Middleware/user_projects/domains/prod_domain/nodemanager',ListenPort='5556',ListenAddress='192.168.145.128',jvmArgs='-Xms24m,-Xmx64m')

2.Connect To NodeManager

wls:/offline> nmConnect('weblogic','welcome1','192.168.145.128','5556','prod_domain','/oracle/Middleware/user_projects/domains/prod_domain','plain')
Connecting to Node Manager ...
Successfully Connected to Node Manager.
wls:/nm/prod_domain>

3.Start AdminServer

wls:/nm/prod_domain> nmStart('AdminServer')

4.Stop AdminServer

    a) Connect To AdminServer

wls:/nm/prod_domain> connect('weblogic','welcome1','t3://192.168.145.128:7001')

   b) Stop The AdminServer

wls:/prod_domain/serverConfig> shutdown('AdminServer')

How To Start/Stop NodeManager Using WLST?

1) Starting NodeManager using WLST

Syntax:

startNodeManager([verbose], [jvmArgs], [nmProperties])
- verbose = Optional. Boolean value specifying whether WLST starts
 Node Manager in verbose mode. This argument defaults to false, disabling
 verbose mode.

- jvmArgs = Optional. JVM arguments to pass to the NodeManager process.
 Multiple arguments can be specified, separated by commas.

- nmProperties = Optional. Comma-separated list of Node Manager properties,
 specified as name-value pairs. Node Manager properties include, but are not
 limited to, the following: NodeManagerHome, ListenAddress, ListenPort, and
 PropertiesFile.

NOTE: In order to stop the Node Manager process,
you must have either started Node Manager with startNodeManager or
Node Manager must have been started with the property QuitEnabled=true.
You can configure this property in
$DOMAIN_HOME/nodemanager/nodemanager.properties file.
This allows you to connect to the Node Manager and shut it down.

Example: 

startNodeManager(verbose='true',NodeManagerHome='/oracle/Middleware/user_projects/domains/prod_domain/nodemanager',ListenPort='5556',ListenAddress='192.168.145.128',jvmArgs='-Xms24m,-Xmx64m')

2) Stopping NodeManager Using WLST

     a) Connecting To NodeManager

wls:/offline> nmConnect('weblogic','welcome1','192.168.145.128','5556','prod_domain','/oracle/Middleware/user_projects/domains/prod_domain','plain')

    b) Stopping NodeManager

wls:/nm/prod_domain> stopNodeManager()

How To Get WLST prompt?

There Are Two Methods To Get WLST Prompt

Method 1) Execute below commands 

cd $MW_HOME/wlserver/common/bin

cd /oracle/Middleware/wlserver/common/bin
sh wlst.sh

Method 2) Execute below commands.

cd $DOMAIN_HOME/bin

cd /oracle/Middleware/user_projects/domains/prod_domain/bin
. ./setDomainEnv.sh
java weblogic.WLST

How To Apply/Install Patch Using Opatch Utility

How To Apply Patch To WebLogic 12C Home Using Opatch Utility?

From WebLogic 12.1.2 bsu utility was deprecated and opatch utility is used for patching.

Summary

1. Shut Down All Weblogic Services Before Applying Patch
2. Check Compatibility Of Opatch Utility Version and OUI
3. Export ORACLE_HOME and PATH
4. Determining What is Installed On Your System
5. Ensuring Patch Application Prerequisites are Met Using -report
6. Applying a Patch
7. Verify The Applied Patch Using lsinventory

1.Shut Down All Weblogic Services Before Applying Patch

   a) Stop Admin And Managed servers using Weblogic Admin Console

   b) Shut Down Nodemanager using stopNodeManager.sh OR Kill command

     cd /oracle/Middleware/user_projects/domains/prod_domain/bin
     ./stopNodeManager.sh

2. Check Compatibility Of Opatch Utility Version and OUI

     a) Checking opatch version

        cd /oracle/Middleware/OPatch
        ./opatch version

   b) Checking OUI Version

      cd /oracle/Middleware/oui
      cat oraparam.ini |grep -i oui_version

   Conclusion: Opatch and OUI versions are same so both are compatible to each other

   Note: To Apply Patch Using opatch Utility, the condition is OPatch version >=  OUI Version

3.Export ORACLE_HOME and PATH

    cd $DOMAIN_HOME/bin
     . ./setDomainEnv.sh
    ORACLE_HOME=/oracle/Middleware
    export ORACLE_HOME
    export PATH=$ORACLE_HOME/OPatch:$PATH

4.Determining What is Installed On Your System

     opatch lsinventory

    Conclusion: Currently no patches applied to the ORACLE_HOME

5.Ensuring Patch Application Prerequisites are Met Using -report

    -report option will not apply patch but it will check pre-requisites

     opatch apply -report /oracle/setup/patch/19637454

6.Applying a Patch

    opatch apply /oracle/setup/patch/19637454

7.Verify The Applied Patch Using lsinventory

    opatch lsinventory

 
    Conclusion: Patch 19637454 Was Installed Successfully

COMPLETED.............

How To Apply/Install Patch Using BSU(bea smart update) GUI Mode?

This Demo Shows How To Apply/Install Patch Using BSU Utility GUI Mode

==> The purpose of applying patch to BEA_HOME OR WLS_HOME Is To Fix Bugs.

==> BSU Utility is shipped with weblogic product 

==> Oracle Releases PSU(Patch Set Update) OR CPU(Critical Patch Update) Patches Quarterly (January - April - July - October), As PSU patches Are Cumulative and all bug fixes are available hence it is highly recommended to apply psu quarterly   

Summary

1. Download The PSU From Oracle Support
2. Create Directory cache_dir inside $MW_HOME/utils/bsu
3. Copy The Downloaded Patch To $MW_HOME/utils/bsu/cache_dir Using WinScp
4. Unzip The Copied Zip Patch File
5. Set The Environment Using setWLSEnv.sh 
6. Run The Patch Install Command Using bsu.sh
7. Verify Whether Patch Applied To The BEA_HOME

1. Download The PSU From Oracle Support

• Login To My Oracle Support http://support.oracle.com
• Click on "Patches & Update" Tab
• Click on Search ==> Click on "Recommended Patch Advisor"
• Select Product: Oracle Weblogic Server
• Select Release 10.3.6.0 OR Any of your prefered wls version
• Platform Select Any
• Click on Search
• Result will lists latest available PSU
• Click on "Patch Name" 20780171
• Click on Download 

2. Create Directory cache_dir inside $MW_HOME/utils/bsu

      cd /oracle/Middleware1036/utils/bsu/
      mkdir cache_dir

3. Copy The Downloaded Patch To $MW_HOME/utils/bsu/cache_dir Using WinScp

4. Unzip The Copied Zip Patch File

     cd /oracle/Middleware1036/utils/bsu/cache_dir
 
      unzip p20780171_1036_Generic.zip

5. Set The Environment Using setWLSEnv.sh 

     cd /oracle/Middleware1036/wlserver_10.3/server/bin
 
     . ./setWLSEnv.sh

6. Set The Display For X11 Forwarding Using Xming/XLaunch

     Follow Below Link For Display Setting

     Link: http://blogbyjagan.blogspot.in/2015/11/setting-display-for-x-forwarding-using.html

7. Run The Patch Install Command Using bsu.sh For Launching Installation Wizard.

•  Execute below commands for launching patch installation wizard

     cd /oracle/Middleware1036/utils/bsu/

     ./bsu.sh 

Setting Display For X11 Forwarding Using Xming/XLaunch For Linux Server

Step By Step Instruction For Setting Display For X-Forwarding Using XLaunch

1. Download And Install Xming In Your Local Window Machine

http://sourceforge.net/projects/xming/

2. Double Click on XLaunch Icon 

3. Enter Any Display Number Say 9999 ==> Click On Next Next Next...Finish

4. Check The Display Number 

5. Now Open Putty And Enter IP Address 

6. Expand SSH  ==> Click on X11 ==> Check "Enable X11 Forwarding" 

==> X Display Location: Localhost:9999.0

7. Click on Open ==> Enter OS Username And Password ==> Enter Command xclock

      Expected Result is Analog Clock pop should come and that shows the display was set properly 

COMPLETED..............

How To Apply/Install Patch Using BSU (bea smart update)?

This Demo Shows How To Apply/Install Patch Using BSU Utility Command Line

==> The purpose of applying patch to BEA_HOME OR WLS_HOME Is To Fix Bugs.

==> BSU Utility is shipped with weblogic product 

==> Oracle Releases PSU(Patch Set Update) OR CPU(Critical Patch Update) Patches Quarterly (January - April - July - October), As PSU patches Are Cumulative and all bug fixes are available hence it is highly recommended to apply psu quarterly   

Summary

1. Download The PSU From Oracle Support
2. Create Directory cache_dir inside $MW_HOME/utils/bsu
3. Copy The Downloaded Patch To $MW_HOME/utils/bsu/cache_dir Using WinScp
4. Unzip The Copied Zip Patch File
5. Set The Environment Using setWLSEnv.sh 
6. Run The Patch Install Command Using bsu.sh
7. Verify Whether Patch Applied To The BEA_HOME

1. Download The PSU From Oracle Support

• Login To My Oracle Support http://support.oracle.com
• Click on "Patches & Update" Tab
• Click on Search ==> Click on "Recommended Patch Advisor"
• Select Product: Oracle Weblogic Server
• Select Release 10.3.6.0 OR Any of your prefered wls version
• Platform Select Any
• Click on Search
• Result will lists latest available PSU
• Click on "Patch Name" 20780171
• Click on Download 

2. Create Directory cache_dir inside $MW_HOME/utils/bsu

      cd /oracle/Middleware1036/utils/bsu/
      mkdir cache_dir

3. Copy The Downloaded Patch To $MW_HOME/utils/bsu/cache_dir Using WinScp

4. Unzip The Copied Zip Patch File

     cd /oracle/Middleware1036/utils/bsu/cache_dir
   
      unzip p20780171_1036_Generic.zip

5. Set The Environment Using setWLSEnv.sh 

     cd /oracle/Middleware1036/wlserver_10.3/server/bin
   
     . ./setWLSEnv.sh

6. Run The Patch Install Command Using bsu.sh

     cd /oracle/Middleware1036/utils/bsu/

     ./bsu.sh -patch_download_dir=/oracle/Middleware1036/utils/bsu/cache_dir -patchlist=EJUW -prod_dir=/oracle/Middleware1036/wlserver_10.3 -install  -log=patch_apply.log -log_priority=trace

7. Verify Whether The Patch Applied To The BEA_HOME is Successfull

      cd /oracle/Middleware1036/utils/bsu

       ./bsu.sh -report -bea_home=/oracle/Middleware1036 -output_file=bsu_report.log

     View the file bsu_report.log. Below Snap Shot Shows That The Patch ID EJUW is applied

   

    OR

    You Can Verify by Checking AdminServer Start up log 

   

COMPLETED................

Import/ Export users and groups from provider DefaultAuthenticator Using WLST

Weblogic Users And Groups Migration from Weblogic 10.3.6 To Weblogic 12.1.3 Using Admin Console

Below Demo Shows Users And Groups Migration From weblogic 10.3.6 To weblogic 12.1.3 Using Weblogic Admin Console For Specific Provider(say DefaultAuthenticator)

1. Below screen shot shows users and groups in weblogic 10.3.6.0

Login To 10.3.6  WebLogic Admin Console ==> Click on "Security Realms"==>Click on myrealm==>Click on "Users And Groups" ==>Click on Users

    Click on Groups

2. Export Users And Groups Into a .dat file Say DefaultAuthenticator.dat and locate at /oracle/Middleware1036/export/

Login To 10.3.6 WebLogic Admin Console ==> Click on "Security Realms"==>Click on myrealm==>Click on ==> Providers ==> Click on DefaultAuthenticator ==> Click on Migration ==>Click on Export ==> Export Format: DefaultATN ==> Export File on Server /oracle/Middleware1036/export/DefaultAuthenticator.dat ==> Click on Save

3. Check export file generated or not

4. Now Login To 12.1.3.0 Weblogic Admin Console And Import "Users And Groups"

• Check Current Users And Groups Settings

•    Perform import using below steps

 Login to Weblogic Admin Console 12.1.3.0 ==> Click on "Security Realms"==>Click on myrealm==>Click on ==> Providers ==> Click on DefaultAuthenticator ==> Click on Migration ==>Click on Import ==> Import Format: DefaultATN  ==> Enter the location of exported file /oracle/Middleware1036/export/DefaultAuthenticator.dat  ==> Click on Save

5. Verify Users And Groups in weblogic 12.1.3.0 

Login To 12.1.3  WebLogic Admin Console ==> Click on "Security Realms"==>Click on myrealm==>Click on "Users And Groups" ==>Click on Users

    Click on Groups

COMPLETED...................

Search Keys: wls users and groups export and imports ; wls user migration ; weblogic group migration ; weblogic users export import ; Import/ Export users and groups from provider DefaultAuthenticator ; user migration from one weblogic domain to another weblogic domain