|
|
This chapter includes the following topics:
Settings for your server should go in the command line or start-up scripts. To localize the default overrides and make it easier to share the changes with your team, add them to the startWebLogic scripts:
To edit the startWebLogic script in Workshop for WebLogic:
Common environment variables you might want to set are:
When creating a domain in the Domain Configuration Wizard, you set the default JVM, as described in Creating a Domain and Server. If you need to change or override the default JVM, in the startWebLogic script, set JAVA_VENDOR to either BEA for JRockit, or Sun for Hotspot. This triggers the domain to use the specified JVM as supplied by the WebLogic Portal installer and any JVM-specific settings for memory and other options.
The default memory settings for WebLogic Portal are:
To override these, set USER_MEM_ARGS in the startWebLogic script. This is useful for gaining more heap or PermSize.
In general, JRockit requires more heap than the same server run on Hotspot. This is probably because Hotspot separates some objects out into Permanent Generation, while JRockit uses heap for these objects.
Servers running either JVM startup and perform initial application deploys faster if you provide enough initial memory (Xms and PermSize) so that server startup does not require extra allocations and the associated garbage collection passes. Generally, set the initial and maximum sizes the same.
For more information, see Tuning the Memory Management System in the JRockit Diagnostics Guide
The two ways to deploy into the Java classpath are:
You can set other Java options in the startWebLogic script using the JAVA_OPTIONS setting. This setting is additive; it does not override anything else. This is a good place to put things like system properties.
The startup of the PointBase database server is controlled in the startWebLogic script by the command line argument nopointbase. There is not an environment variable to control this setting.
To start the server without PointBase, run the command:
startWebLogic nopointbase
To permanently set nopointbase for a domain, add this argument to where DOMAIN_HOME/startWebLogic.sh or DOMAIN_HOME/startWebLogic.cmd calls the DOMAIN_HOME/bin/startWebLogic script.
This is useful when you are using an external database, such as Oracle or SQL Server.
For information about using databases, see the Database Administration Guide.
The startup of Autonomy is controlled by the CONTENT_SEARCH_OPTION in the startWebLogic script. To turn off Autonomy startup, set this option to none. Use this option when you do not need to run Autonomy or when it is already running as an external daemon.
For information about using Autonomy, see Integrating Search.
For production mode servers, the default is nodebug. However, for development environments, although the startWebLogic script accepts a nodebug command line argument, it is not advisable to try to override this setting with your scripts because it confuses Workshop for WebLogic. Instead use the Server or Debug buttons in the Server view.
If you are not using Workshop for WebLogic, you can use the nodebug argument. The debug mode sets the following arguments in the JVM:
-Xdebug -Xnoagent
-Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n
-Djava.compiler=NONE
If you have complex requirements, such as starting external processes or significant changes to server settings, you should create your own domain template to capture and replay these changes. A domain template facilitates sharing complex domain configurations with the rest of your team. For information about creating your own domain templates, see:
|
