Scripts

dmk-run.ps1

This script is used to call the dmk-run.pl perl script. The following list shows all arguments that can be passed to this script. Aliases are available to short cut the command lines.

Node Manager Windows service scripts

The Windows Node Manager Service exit in two types: default Node Manager and WebLogic Domain dedicated Node Manager.

Windows Service for Default Node Manager

The Default Node Manager is to be used if several WebLogic Domains have to be managed from a unique Node Manager. It requires that the nodemanager.properties and nodemanager.domains configuration files exist in the %MW_HOME%\oracle_common\common\nodemanager directory. If they do not exist, they have to be created.

The WebLogicNodeManager windows service can be installed as follow:

  1. As windows administrator, open a CMD window and set the following environment variable JAVA_HOME: must point to the JAVA installation directory. NODEMGR_HOST: point by default to localhost, change it if needed. NODEMGR_PORT: Node manager listening port.

  2. Move to the WebLogic server bin directory cd D:\app\weblogic\product\Middleware\wlserver\server\bin

  3. Run the command file to install the Windows Service installNodeMgrSvc.cmd

Windows Service for Domain dedicated Node Manager

The WebLogic Domain Node Manager is dedicated to one specific domain. The Node Manager configuration files are created automatically at WebLogic Domain creation time.

The WebLogicNodeManager windows service can be installed as:

  1. As windows administrator, open a CMD window and set the following environment variable:

    • JAVA_HOME: must point to the JAVA installation directory.

    • NODEMGR_HOST: point by default to localhost, change it if needed.

    • NODEMGR_HOME Must point to the nodemanager directory in the Domain configuration home. e.g.: E:\app\weblogic\config\domains\basic_domain\nodemanager

    • NODEMGR_PORT: Node manager listening port.

  2. Move to the WebLogic server bin directory

cd D:\app\weblogic\product\Middleware\wlserver\server\bin
  1. Run the command file to install the Windows Service

installNodeMgrSvc.cmd

Un-installing the Node Manager Windows Service

  1. Move to the WebLogic server bin directory

cd D:\app\weblogic\product\Middleware\wlserver\server\bin
  1. Run the command file to uninstall the Windows Service

uninstallNodeMgrSvc.cmd

WebLogic domain automatic start and shutdown on Windows Boot

In this chapter, the WebLogic domain name SampleDomain is to be replaced with the name of the WebLogic Domain you want to configure.

Install the files

The files to be used are part of the DMK distribution. They can be found in the %DMK_HOME%\templates\etc\Automatic_startup. They need to be installed simply copying the full directory in the WebLogic Domain DMK administration directory (D:\app\weblogic\local\etc\SampleDomain for a domain named SampleDOmain).

WebLogic Domain automatic start on Windows boot

This task will automatically start the WebLogic domain on boot of the machine

Generality:

Actions:

Actions details:

Settings:\

Windows - Group Policy for Shutdown

This chapter describes how to create a group policy to properly shutdown the domain at Windows server stop or reboot.

This is achieved by adding the stop.cmd script at the shutdown. Open startmenu and type gpedit.msc

Full path: e:\app\weblogic\local\etc\SampleDomain\Automatic_startup\start.cmd

Important note: To avoid having issues with the Windows Shutdown killing WebLogic processes and coming in conflict with the node manager service, the “-Xrs” java option needs to be added in the WebLogic JVM start parameters. This is done using the setUserOverrides.cmd file:

@REM  Global - Java Options
set JAVA_OPTIONS=%JAVA_OPTIONS% -Xrs -Dweblogic.security.SSL.hostnameVerifier=weblogic.security.utils.SSLWLSWildcardHostnameVerifier

Last updated