To configure the WebLogic admin server, edit the file bin/setDomainEnv.sh
(for Linux), bin/DomainEnv.bat
(for Windows) to set the following options:
-Xms256m –Xmx6000m –XX:MaxPermSize=256m
.
Important!: Oracle recommends setting the Java heap space for the WebLogic server to: -Xms256m –Xmx6000m –XX:MaxPermSize=256m
. SiteWand will not start if the Java heap space is not set per the recommendation.
If the WebLogic precompile option is enabled, the WebLogic console displays the following message after precompiling: “Server started in RUNNING mode” For details on how to enable precompilation, see WebLogic Server documentation.
JAVA_OPTIONS="-Djava.awt.headless=true"
Add the following line if you are installing on Windows:set JAVA_OPTIONS=-Djava.awt.headless=true
JAVA_OPTIONS="-Dweblogic.http.enableRemoteUserHeader=true -Djava.awt.headless=true"
Add the following line if you are installing on Windows:set JAVA_OPTIONS=-Dweblogic.http.enableRemoteUserHeader=true -Djava.awt.headless=true
Important: Use this option only if no one has access to the WebLogic machine, and there is an OHS web server proxy in front of the WebLogic machine.
Step 2: Configuring WebLogic for EnterpriseTrack
Starting the WebLogic Admin Server
Stopping the WebLogic Admin Server
Legal Notices
Copyright © 2000, 2016,
Oracle and/or its affiliates. All rights reserved.
Last Published Thursday, June 23, 2016