Steps to generate boot.properties and startup.properties for AdminServer

If we start the AdminServer( which has never been started before using script ) from NodeManager, boot.properties and startup.properties file don’t get created by default and AdminServer fails to start. To create the boot.properties and startup.properties file we need to follow the steps below.   sed -i “s/StartScriptEnabled=true/StartScriptEnabled=false/g” nodemanager.properties connect(‘user’,’pwd!’,’t3://host:port’)

Continue reading »

AUTO RESTARTING MANAGE SERVER IN FAILED STATE USING WEBLOGIC NODEMANAGER CRASH RECOVERY FEATURE IN WEBLOGIC 12C

The nodemanager crash recovery feature enable auto restart of manage server incase of JVM failure. The Only Requirement To Use This Feature: Nodemanager should be configure to start  manage server. won’t work This feature will not work if out of box manage server start script  “startManagedWebLogic.sh”  is being use to start manage server

Continue reading »

Starting the WEBLOGIC Administration Server Using Node Manager and WLST IN 11G

GO TO WEBLOGIC HOME  AND SET THE PATH ENVIRONMENT VARIABLE      START WLST USING  java weblogic.WLST NOW START THE NODEMANAGER USING COMMAND  startNodeManager.sh    YOU WILL SEE A MESAGE STATING   “INFO: Secure socket listener started on port 5556, host localhost/127.0.0.1”    <— WHICH MEAN NODEMANAGER HAS STARTED ON LOCAL HOST 4. Connect WLST TO

Continue reading »

How to configure SSL on Nodemanager for 12c

In Weblogic Server 12.1.2, the java version of Node Manager controls all WLS instances belonging to the same domain.This allows the feasibility to have different nodemanager configurations for different domains. You can follow the steps below to use one nodemanager per domain running over SSL ( custom identity & custom

Continue reading »

Common NodeManager exceptions (UnsatisfiedLinkError)

Below are few most common issues you might run into when trying to start a NodeManager. 1. weblogic.nodemanager.common.ConfigException: Native version is enabled but NodeManager native library could not be loaded Caused by: java.lang.UnsatisfiedLinkError: no nodemanager in java.library.path Remedy: You would need to point your jmv to point to the native

Continue reading »

WebLogic Server Nodemanager

Continue reading »