> For the complete documentation index, see [llms.txt](https://dbi-services.gitbook.io/dmk-oracle-weblogic/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dbi-services.gitbook.io/dmk-oracle-weblogic/windows/scripts.md).
# 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.
| Name | Description |
| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| listDomains | Prints the list of WebLogic domains declared on this machine |
| domainStatus | Prints the status of WebLogic domain selected |
| domainQuickStatus | Prints the status of WebLogic domain selected (fast version) |
| domainInfo | Prints runtime information of WebLogic domain selected |
| allDomainsStatus | Prints the status of all WebLogic domains declared on this machine |
| allDomainsQuickStatus | Prints the status of all WebLogic domains declared on this machine (fast version) |
| startDomain | Starts the WebLogic domain selected |
| stopDomain | Stops the WebLogic domain selected |
| startAdmin | Starts the WebLogic Admin Server for domain selected |
| stopAdmin | Stops the WebLogic Admin Server for domain selected |
| startCluster | Starts the WebLogic Cluster given in parameter for domain selected |
| stopCluster | Stops the WebLogic Cluster given in parameter for domain selected |
| startServer | Starts the WebLogic Server given in parameter for domain selected |
| stopServer | Stops the WebLogic Server given in parameter for domain selected |
| startComponent | Start the system component given in parameter |
| stopComponent | Stop the system component given in parameter |
| startNM | Starts the WebLogic Domain associated Node Manager using the command line |
| stopNM | Stops the WebLogic Domain associated Node Manager (Kill NM process) |
| showDomainConfig | Displays the WebLogic domain configuration declared in properties file |
| packWebLogicDomain | Pack the WebLogic Domain Selected and create the unpack scripts to unpack on remote machine |
| wlsVersion | Displays the version of the WebLogic Server. Complete information adding –verbose argument |
| wlst | Start the WLST scripting shell |
| wlsDo | DMK wrapper command – Displays the help |
| createDomain | Create a WeLogic Domain based on the domain.properties file given in parameter |
| createWLSAdminSecurityFiles | Creates the WebLogic Domain Administrator user security files for the domain selected in the environment |
| createNMSecurityFiles | Creates the Node Manager Administrator user security files for the node manager declared in the select WebLogic Domain domain.properties file. |
## 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
```
3. 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
```
2. 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:**
| Environment | Task name | State |
| ----------- | --------------------- | ------- |
| DEV | « domainName »-OnBoot | Enabled |
**Triggers:**\
**Actions:**
**Actions details:**
\
Full path: e:\app\weblogic\local\etc\SampleDomain\Automatic\_startup\start.cmd
**Finish:**\
**Settings:**\\
**Verify the security Option**\
**Verify the condition** as well as the network which should be available before executing the start of the Domain\
### 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
Add a shutdown script\
Define the shutdown script\
Full path: e:\app\weblogic\local\etc\SampleDomain\Automatic\_startup\start.cmd
Then apply the changes\
**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
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://dbi-services.gitbook.io/dmk-oracle-weblogic/windows/scripts.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.