Automating Oracle Weblogic Startup for JD Edwards on Linux

Looking around on the web, I have seen many different methods of starting Weblogic and its components on Linux.  Like most technical problems, there are many different ways to automate Weblogic startup.  Some methods involve more complexity than many companies need or want, so I decided to share a simple and reliable approach I have been using.

The method can be broken into three parts:

1) Configure the Linux Operating System
2) Configure the Weblogic AdminServer
3) Configure Weblogic NodeManger

1) Configuring the Linux Operating System

We will put our commands in the Linux rc.local file, which is executed in a sub-shell near the end of the Linux boot sequence.  Edit the /etc/rc.d/rc.local and add the following commands, adjusting the username and paths according to your environment.


2) Configure the Weblogic AdminServer

If you have not already done this, you should create a boot.properties file to enable the AdminServer to start without prompting for credentials.  Create this file in the security folder for your AdminServer.  For example, put the file in: /u01/jdedwards/Oracle/Middleware/user_projects/domains/WLSJDE/servers/AdminServer/security

It should contain the Weblogic admin user and its password as shown below:


3) Configure Weblogic NodeManager

Edit the nodemanager.properties file, typically located under the WLS Home directory under the /common/nodemanager/ subfolder, and change the values for CrashRecoveryEnabled and StartScriptEnabled from false to true. These settings tell NodeManager to restart the instances back to a running state using the default Weblogic startup script (startWeblogic.sh).

Good luck!