3 Administering WebLogic Server and Oracle Traffic Director

This chapter describes how to administer WebLogic domains on Oracle Database Appliance. It also describes restrictions on domains that are running on Oracle Database Appliance.

The initial configuration and provisioning process described in Chapter 2, "Installation and Configuration," is intended only to provide a starting point for the WebLogic domain. Once provisioned, you can customize the domain as needed and administer the VMs as you would any other Linux VM. This means that you can transfer configuration and log files to and from the machine as needed, and use the WebLogic Scripting Tool (WLST) and the WebLogic Server Administration Console to customize the domain. Note that there are some restrictions on domain customization, as described in "Restrictions on Modifying Domains".

Customizing a WebLogic Domain

After provisioning the domain, you can further customize and manage the domain using WLST or the Administration Console.

WebLogic Server Administration Console

To access the WebLogic Server Administration Console, open a Web browser and enter the following URL, where admin-server-ip and listen-port are the IP Address and Listen Port that were configured for the Administration Server on the WebLogic Domain Information screen of the configuration utility:


Log in with the username system. The password is the password that was specified on the WebLogic Cluster Settings screen of the configuration utility when you created the domain.

For more information on the Administration Console, reference the following documentation or press F1 while in the Administration Console to access help:


You can use WLST in online or offline mode to manage the domain. There are some restrictions, however, on the modifications you can make to the domain. See "Restrictions on Modifying Domains" for more information.

For online mode, simply connect to the domain's Administration Server using the appropriate public network IP address.

To run WLST scripts in offline mode, ssh to the VM that is hosting the Administration Server.

For information about using WLST on WebLogic Server 10.3.6, refer to the following documents:

For information about using WLST on WebLogic Server 12.1.1, refer to the following documents:

For information about using WLST on WebLogic Server 12.1.2, refer to the following documents:

Starting and Stopping Servers

The Administration Server and all Managed Servers are automatically started as part of the provisioning process. Afterwards, you can use standard WebLogic Server procedures to shut down or restart the Administration Server and Managed Server instances.

For more information, see:

Restrictions on Modifying Domains

Because the WebLogic domain is hosted in a managed, virtualized environment, there are several restrictions that apply when modifying the domain. There is no mechanism in place to enforce these restrictions, and therefore, you must use caution when modifying a WebLogic domain on Oracle Database Appliance.

In general, you should not modify WebLogic Server configuration settings that were initially set during the domain provisioning process unless you know what those settings are doing and you are certain that modifying them will not have any adverse effects on the domain.

The following sections describe specific configuration areas in which you should avoid modifications:

Domain Name

Some Oracle Database Appliance scripts rely on the ability to identify the associated WebLogic Server domain from the name of a given VM instance. You should therefore not change the name of a domain once the VMs in the domain have been provisioned.

Cluster Size

Currently, there is no support for adding WebLogic Server server instances to a cluster that has already been provisioned on Oracle Database Appliance.

VMs can, however, be deactivated from a provisioned domain by using the OAKCLI shutdown command. After shutting down a VM, you can permanently delete its state using the OAKCLI delete command. Deleting a VM results in a permanent loss of that VM from the domain. Note that you must also modify the cluster configuration to remove the server instance cleanly.

For example, to permanently delete a VM named WLS_mydomain_ManagedServer_8, enter the following commands:

cd /opt/oracle/oak/bin

./oakcli stop vm WLS_mydomain_ManagedServer_8

./oakcli delete vm WLS_mydomain_ManagedServer_8

For more information about OAKCLI commands, refer to "Oracle Database Appliance Command Line Interface (OAKCLI) Utility Reference" in Oracle Database Appliance Getting Started Guide.


If you want to delete all VMs, use the cleanup.sh command instead. See "Deleting the WebLogic Domain."

Node Manager

In this configuration, Node Manager runs inside of each VM. If a VM shuts down, Node Manager will not be available until the VM comes back up again.

Node Manager is initially configured to use the WebLogic Server demo certificates.

For information on how to install certificates and enable SSL for WebLogic Server, see:

Security Certificates

You must log in to each of the WebLogic Server VMs to install CA security certificates on each VM.

Data Source

Each WebLogic domain contains a data source that is used internally by WebLogic Server for transaction log and JMS storage. Do not modify or delete this data source.

Creating Multiple Domains and Expanding the Domain

Oracle does not support multiple domains and clusters on ODA. After creating the initial domain, do not run the configuration utility again to create additional domains and clusters.

Oracle also does not support creation of additional WebLogic Server and OTD instances in the domain. Oracle recommends that you do not create additional clusters or Managed Servers in this environment, and that you not add Managed Servers to the existing VMs. These scenarios are not supported.

Administering Oracle Traffic Director

Oracle Traffic Director is the fronting load balancer in the Oracle WebLogic Server on Oracle Database Appliance configuration. During configuration, you can choose to not configure Oracle Traffic Director in the and releases with X3-2 version.

On Oracle Database Appliance, the OTD Administration Server VM and Admin Node VMs are configured to start automatically at the end of the provisioning.

To administer OTD, log in to the following administration URL, where ip-address is the IP address of the OTD Administration VM:


For more information on OTD and OTD administration, see the Oracle Traffic Director 11g ( library at:


Starting and Stopping Oracle Traffic Director Server Instances

You can start and stop OTD server instances either from the OTD Administration Console or from a server instance directory in the OTD INSTANCE_HOME directory. The OTD INSTANCE_HOME on ODA is:


For information on how to start and stop OTD server instances, see "Starting, Stopping, and Restarting Oracle Traffic Director Instances" in Oracle Traffic Director Administrator's Guide.

Configuring Security

You must log in to each OTD VM to configure security and install CA security certificates. For information on configuring security and security certificates for OTD, see "Managing Security" in Oracle Traffic Director Administrator's Guide.

Modifying VM Resource Allocations

All VMs that are provisioned for a WebLogic Server domain are allocated with predetermined resources (see "VM Resource Allocation" in Chapter 2). You can use the OAKCLI to modify this resource allocation after the VMs have been provisioned and started.

To modify the resource allocation for a VM:

  1. Use the OAKCLI stop command to shut down the VM.

  2. Use the OAKCLI configure command to update the number of virtual CPUs and amount of memory that is allocated for the VM.

  3. Use the OAKCLI start command to restart the VM.

For example, to change the number of virtual CPUs to 3 and the amount of virtual memory to 4GB for a VM named WLS_1_mydomain_mycluster_1, enter the following commands:

cd /opt/oracle/oak/bin

./oakcli stop vm WLS_1_mydomain_mycluster_1

./oakcli configure vm WLS_1_mydomain_mycluster_1 -vcpu 3 -memory 4196

./oakcli start vm WLS_1_mydomain_mycluster_1

For more information about OAKCLI commands, refer to "Oracle Database Appliance Command Line Interface (OAKCLI) Utility Reference" in Oracle Database Appliance Getting Started Guide.

Managing Access Log Files

To prevent WebLogic Server HTTP access logs and Oracle Traffic Director access logs from filling up drive space, configure the access logs appropriately on each server instance. You can limit the access log file size and the number of log files to retain. For more information, see the following topics:

OTD access logs can be configured for log file rotation (based on time). You can configure the rotated log files to be automatically zipped, deleted, or moved elsewhere. For information about OTD log file locations, see "About the Oracle Traffic Director Logs" in Oracle Traffic Director Administrator's Guide. For information about configuring OTD access log rotation see "Configuring Oracle Traffic Director to Rotate Logs Automatically" in Oracle Traffic Director Administrator's Guide.

Deleting the WebLogic Domain

If you want to delete the existing WebLogic domain, perform the following steps:

  1. Access the directory where you installed the configuration utility.

  2. Enter the following command:

    ./cleanup.sh domain_name

After running this command, the domain and the associated VMs are deleted. You can then use the configuration utility to create a new domain.

For more information, see the README file in the configuration utility directory.