WLS Tips and Tricks

• Auto-start WLS:
  • with systemd
  • without console output: nohup startWebLogic.sh < /dev/null &> /dev/null &
  • NodeManager start as system service scripts (inet.d, xnet.d)
  • Start Admin Server with NM
• OHS:
  • Install Tutorial 
  • WebLogic Server 12c (12.2.1): Configuring Oracle HTTP Server as a Cluster Proxy
  • Change Node Manager Listen Port for Standalone OHS Instance:
  • Running Oracle HTTP Server (OHS) Standalone  on same host as another WLS domain could cause Node Manager Listener conflict:
    • OHS installed standalone defaults to NM listen port of 5556 (standard NM listen port) but this cannot be changed when the domain is created using Configuration Wizard. So, NM port is set to 5556.
  • Standard WLS Domain also defaults to 5556 as the Node Mgr list port – Although it can be changed in the Configuration Wizard. (And can be changed later via the Admo\in console -> Env -> <chosen machine> -> Config-> NM Listen Port.   Or WLST).
  • So: What to do?
    • Run OHS within another WLS domain (typically FMW which will include EM FMC) – then you can manage this in the EM FMC console AND get benefits of better configuration control of OHS instance via EM FMC.
    • Run OHS Standalone on another box without another domain node manager installed or one in which the domain(s) NM port(s) are specifically overridden and not set to 5556.
    • Change the default OHS NM Port after domain creation. But how? You must edit nm.properties AND change the ohs instance’s localmachine nm port. BUT, since there is no admin console for the standalone OHS, this must be done with WLST. Here’s the steps:
      1. Edit nm.properties located at <ohsdomain>/nodemanager/modemanager.properties.
      2. Set ListenPort=5557   – or whatever different port you want so it won’t conflict with any other node manager(s) on that host.
    • Use WLST to change the ohs instance’s localmachine’s node manager port:
      • cd <OHS Binaries Home>/ohs/common/bin   — ex: /u01/app/ohs/ohs/common/bin

cd /u01/app/ohs/ohs/common/bin   (or wherever you installed the binaries for OHS)
./wlst.sh
readDomain('/u01/domains/ohs_domain');   -- the ohs instance domain location
cd('Machine/localmachine/NodeManager/localmachine');
set('ListenPort', 5557);
updateDomain();
closeDomain();

• • • with thanks to  Paul Catalin Tomoiu

• Threads:
  • WebLogic Stuck Threads: Creating, Understanding and Dealing with them

Garbage Collection in Java

• Starting Servers in Particular Order:
  • Sorry, no built-in capability for this. One way to do it is to build and use custom start scripts which will delay/not start the dependent server until possible. WLST or REST script can certainly be developed to address the dependency. It would be one NM startup-script per machine, unless you place some logic into the script to distinguish the machines. WLST or REST options may be easier and not machine dependent that much.WLST and/or REST simply are scripting abilities for sending start/stop commands to respective NM instances.