For more information, see Boot Identity Files.
With a boot identity file, you can change the login credentials without needing to modify the Windows service. Instead of this method, you can use a boot identity file.
The disadvantage to this method is that changing the user name or password for the server instance requires you to delete the Windows service and set up a new one with the new user name and password. This is one of two possible methods for avoiding the user name/password prompt when a server instance starts. The wlsvc utility encrypts the login credentials and stores them in the Windows registry. Where username is the name of an existing user with privileges to start a server instance and password is the user's password. Where server-name is the name of an existing server instance that you want set up as a Windows service.Īdd the following optional batch commands to the text file. See " Specifying a Server Root Directory" in Understanding Domain Configuration for Oracle WebLogic Server.
Where absolute-pathname is the absolute pathname of the Administration Server's root directory (the directory that contains the domain's configuration file). Where domain-name is the name of your WebLogic Server domain. This is a batch command that begins the localization of environment variables in a batch file.
In the root directory for the domain's Administration Server create a text file.Īdd the following, required batch commands to the text file, each command on a separate line: To see an example of a server-specific script, refer to Example 3-1. For more information, refer to Run the Server-Specific Script.įor more information about wlsvc, enter the following command at a command prompt: WL_HOME \server\bin\wlsvc -help, where WL_HOME is the directory in which you installed WebLogic Server. For more information, refer to Adding Classes to the Classpath. If you have created additional Java classes that you want the WebLogic Server instance to invoke, add them to the server's classpath. For more information, refer to Redirecting Standard Out and Standard Error to a File. If you want to see the messages that a server instance prints to standard out and standard error (including stack traces and thread dumps), redirect standard out and standard error to a file. For more information, refer to Enabling Graceful Shutdowns. If you want a server instance to shut down gracefully when you stop the Windows service, create a Java class and modify the master script so that the Microsoft Management Console will invoke the class. For more information, refer to Requiring Managed Servers to Start After Administration Servers. If you set up both an Administration Server and a Managed Server to run as Windows services on the same computer, modify the WebLogic Server master script so that the Managed Server starts only after the Administration Server finishes its startup cycle. For more information, refer to Configuring a Connection to the Administration Server. If you are installing a Managed Server as a Windows service, add a variable to the server specific script that specifies the location of the domain's Administration Server. For more information, refer to Creating a Server-Specific Script. Using the Services Window to Stop or Restart a Server InstanceĬhanging Startup Credentials for a Server Set Up as a Windows ServiceĬreate a script that sets values for server-specific variables and then calls a WebLogic Server master script.
The following tasks set up and manage WebLogic Server instances that run as Windows services: The MMC cannot be configured to use Node Manager to start Managed Servers, therefore the Node Manager's monitoring and automatic restart features cannot be used for servers that run as a Windows service.
When you start the Windows host, the Microsoft Management Console uses the information in the Windows Registry key to invoke the weblogic.Server main class. The registry entry contains such information as the name of the server and other startup arguments. In Windows, the Microsoft Management Console (MMC), specifically Services, is where you start, stop, and configure Windows services.įor each server instance that you set up as a Windows service, WebLogic Server creates a key in the Windows Registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.
This chapter describes how to set up a WebLogic Server instance as a Windows service so that it starts automatically when you boot up a Windows host computer. 6/9 3 Setting Up a WebLogic Server Instance as a Windows Service