Set Up Automatic Startup
It is possible to configure any Windows service to restart itself upon failure. These are standard options available when configuring a Windows service in the context of Windows Services Manager.
However, it is important to understand that Windows Services Manager only monitors the service's JVM process. If the JVM process fails (shuts down), then Windows Services Manager will attempt to restart it. But there are some scenarios where the WebLogic Admin Server or Managed Server may go into an unhealthy or failed state while the JVM is still running. The Windows Service Manager will not know to restart the process in these cases, whereas if the Admin Server and Managed Server had been started using the WebLogic Node Manager, Node Manager would recognize such a state and restart the process.
Oracle recommends starting the Admin and Managed Servers through the Node Manager using python scripts and then configuring the Windows server to execute the python scripts at startup.
To start servers manually, see Start Servers Manually.
In this section:
- Create boot.properties
- Increase the Delay for Auto Start OPADomain and FRDomain
- Set Up Scripts to Execute Automatically at Machine Startup
- Test Autostart
Parent topic: Upgrade the Oracle Clinical Front End
Create boot.properties
Check if the boot.properties file exists in Oracle_Home\user_projects\domains\FRDomain\servers\AdminServer\security.
If not, create it as a plain text file with the following contents:
username = weblogic_username password = weblogic_user_password
By default, the WebLogic username is weblogic
. This username and password will get encrypted after all services are started.
Parent topic: Set Up Automatic Startup
Increase the Delay for Auto Start OPADomain and FRDomain
For the OPADomain and FRDomain to start successfully, depending on the performance in your environment, you may want to increase the delay by which OPADomain and FRDomain start to allow time for Node Manager to start first.
- Go to OPA_HOME\config\opa_setup_scripts\ directory.
- Open the autostartfrdomain.cmd and autostartopadomain.cmd files.
- In each file, find the line
PING 127.0.0.1 -n x
and change the value of x to 300. - Save and close the files.
Parent topic: Set Up Automatic Startup
Set Up Scripts to Execute Automatically at Machine Startup
Create a task and set up the Task Scheduler to run the job on bootup:
Parent topic: Set Up Automatic Startup