Getting started in the morning is one of those daily battles that feels harder than it should. The alarm goes off, and for a moment, it’s tempting to just stay buried in blankets, ignoring the responsibilities waiting outside that warm cocoon. The body’s sluggish, the mind’s foggy, and the day ahead looms like a mountain. But still—you get up. That first step might be slow, but it sets everything in motion.
Contents
Identify these installation parameters:
| Parameter | Example |
|---|---|
| MW_HOME | /opt/oracle/occas/8.1 |
AdminServer
Let's create a startup script for the Admin Console.
Create a file called "/etc/systemd/system/weblogic.service".
[Unit]
Description=WebLogic Admin Console Service
[Service]
Type=simple
# Note that the following three parameters should be changed to the correct paths
# on your own system
WorkingDirectory=/opt/oracle/occas/8.1/user_projects/domains/replicated
ExecStart=/opt/oracle/occas/8.1/user_projects/domains/replicated/bin/startWebLogic.sh
ExecStop=/opt/oracle/occas/8.1/user_projects/domains/replicated/bin/stopWebLogic.sh
User=oracle
Group=oinstall
KillMode=process
LimitNOFILE=65535
Restart=always
[Install]
WantedBy=multi-user.target
You can now use the following commands to start / stop WebLogic:
$ sudo systemctl daemon-reload
$ sudo systemctl enable weblogic
$ sudo systemctl start weblogic
Node Manager
Node Manager starts and stops WebLogic, but who watches the watcher? You, that's who!
Create a file called /etc/systemd/system/nodemanager.service, changing the paths to fit your environment.
You can now use the following commands to start / stop nodemanager:
sudo systemctl daemon-reload
sudo systemctl enable nodemanager
sudo systemctl start nodemanager
Do this for all servers, both managed and admin.
Congratulations! You are now ready to move on to Security.