This chapter describes how to provision WebLogic Server, including a fronting load balancer, on the Oracle Database Appliance using the Oracle WebLogic Server Configuration for Oracle Database Appliance utility (configuration utility).
The following sections are included in this chapter:
Oracle WebLogic Server on Oracle Database Appliance is available in different versions.
2.7.0.0.0 - supports both Oracle Database Appliance versions X3-2 and V1.
2.6.0.0.0 - supports both Oracle Database Appliance versions X3-2 and V1.
2.5.0.0.0 - supports only Oracle Database Appliance version V1.
The following procedures are primarly applicable to 2.7.0.0.0 and 2.6.0.0.0 versions. The details for the 2.5.0.0.0 version are explicitly mentioned where necessary.
WebLogic Server support is provided via Oracle Virtual Machine (OVM) template bundles which are pre-configured for the Oracle Database Appliance environment. Each bundle corresponds to a WebLogic version, either 11g (10.3.6) or 12c (12.1.1 and 12.1.2). Each of these bundles include:
Oracle Linux 5 Update 8
Oracle WebLogic Server
Oracle Traffic Director 11g (Oracle WebLogic Server on Oracle Database Appliance 2.7.0.0.0 and 2.6.0.0.0 releases include 11.1.1.7 and Oracle WebLogic Server on Oracle Database Appliance 2.5.0.0.0 release includes 11.1.1.6)
Oracle WebLogic Server Configuration for Oracle Database Appliance utility
After completing the prerequisite setup steps, perform the following steps to download the Oracle Database Appliance Kit for WebLogic Server.
To download the Oracle Database Appliance Kit for WebLogic Server from the Oracle Software Delivery Cloud, do the following:
Go to https://edelivery.oracle.com..
Sign in by using your Oracle account.
Read and accept the Oracle Software Delivery Cloud Trial License Agreement and the Export Restrictions.
Click Continue.
In the Select a Product Pack field, select Oracle Fusion Middleware.
In the Platform field, select Linux x86-64.
Click Go.
In the results displayed, select Oracle Fusion Middleware 11g Media Pack for Linux x86-64, and click Continue.
Select the appropriate file and click the Download button:
V43086-01.zip for WebLogic Server 12.1.2
V43085-01.zip for WebLogic Server 12.1.1
V43084-01.zip for WebLogic Server 10.3.6
The following procedures are primarly applicable to 2.7.0.0.0 and 2.6.0.0.0 versions. The details for the 2.5.0.0.0 version are explicitly mentioned where necessary.
After completing the download, perform the following steps to install the WebLogic Server and Oracle Traffic Director OVM templates:
Extract the downloaded ZIP files to any location on the local client. After extraction, the following files are located in the directory, where version is either 1036, 1211, or 1212:
Table 2-1 Contents of the Zip File
| Release | List of Files |
|---|---|
|
Oracle WebLogic Server on Oracle Database Appliance 2.7.0.0.0 |
|
|
Oracle WebLogic Server on Oracle Database Appliance 2.6.0.0.0 |
|
|
Oracle WebLogic Server on Oracle Database Appliance 2.5.0.0.0 |
|
Note:
You cannot upgrade from one version of Oracle WebLogic Server to another without re-provisioning. If you begin provisioning using Oracle WebLogic Server 12.1.1, you cannot automatically upgrade to Oracle WebLogic Server 12.1.1 without re-provisioning. You must download the 12.1.2 template and re-provision using the 12.1.2 template. Make sure you download the template with the appropriate Oracle WebLogic Server version.
From the directory in which the extracted files are located, execute the following command to combine the two WebLogic Server (WLS) files:
cat WLS_version_VMT.tar.gz_aa WLS_version_VMT.tar.gz_ab > WLS_version_VMT.tar.gz
Delete the two original WLS files:
rm WLS_version_VMT.tar.gz_aa
rm WLS_version_VMT.tar.gz_ab
Use scp to transfer the two template archives from the client to the /OVS/staging directory of Domain-0 on Node 0 and Domain-0 on Node 1.
scp WLS_version_VMT.tar.gz root@ip_address:/OVS/staging
scp OTD_11116_VMT_tar.gz root@ip_address:/OVS/staging
Replace ip_address with the IP address of Domain-0 on Node 0, then do the same with the IP address of Domain-0 on Node 1.
Note:
For information about the architecture of the Oracle Database Appliance virtualized platform, see "Deploying Oracle Software on Oracle Database Appliance Virtualized Platform" in Oracle Database Appliance Getting Started Guide.
Do not extract the WLS and OTD tar.gz files.
Transfer the configuration utility file wls_configurator_2.5.0.0.0.tar.gz/wls_oda_configurator_2.6.0.0.0.tar.gz to any location on the ODA_BASE domain on Node 0:
Table 2-2 Command to Transfer the Configuration Utility File
| Release | Command |
|---|---|
|
Oralce WebLogic Server on Oracle Database Appliance 2.7.0.0.0 |
|
|
Oracle WebLogic Server on Oracle Database Appliance 2.6.0.0.0 |
|
|
Oracle WebLogic Server on Oracle Database Appliance 2.5.0.0.0 |
|
Replace ip_address with the IP address of the ODA_BASE domain on Node 0. Replace dest_dir with the destination directory.
Use ssh to log in as the root user to the ODA_BASE domain on Node 0, switch to the directory where you stored the configuration utility file, and extract the configuration utility file to any directory on the ODA_BASE domain of Node 0.
See "Using the Configuration Utility" for information on how to run the configuration utility.
Note:
If you want to run the configuration utility to create a configuration file on the local client, extract wls_configurator_version.tar.gz to any directory on the local client.
The configuration utility provides an easy way to create and configure a single WebLogic domain with a cluster to serve your business applications, and configure Oracle Traffic Director, a software load balancer that can efficiently balance incoming requests to one of the WebLogic clusters.
Use the following procedure to download the configuration utility and run it on a local Windows, MacOS, or Linux client to create and save the configuration file for later use.
To download and install an updated configuration utility on a Windows or Linux client and on the Oracle Database Appliance:
Open a Web browser and access the following URL:
http://www.oracle.com/technetwork/middleware/weblogic-oda/downloads/index.html
In the Oracle Database Appliance Manager Configurator section, right-click on the Oracle WebLogic Server Configuration for Oracle Database Appliance link and save the file to any location on your Windows or Linux client machine.
Extract the file to any location on the client machine.
Copy the downloaded tar.gz file from the client to any location on the ODA_BASE domain of Node 0 using the following scp command:
scp filename root@ip_address:dest_dir
Replace filename with the name of the downloaded file, and replace ip_address with the IP address of ODA_BASE of Node 0 and replace dest_dir with the destination directory.
Extract the file to any directory on ODA_BASE.
Note:
When downloading an updated configuration utility to replace an existing one, Oracle recommends that you extract the updated files to the same directory as the original to avoid having multiple versions of the utility on the system.
For information on how to run the configuration utility, see "Using the Configuration Utility."
You can use either of the following methods to create a WebLogic domain configuration using configuration utility:
Download the configuration utility to a Windows, MacOS, or Linux client, and run the configuration utility on the client to create a configuration file. You can then copy the Configuration file to the Oracle Database Appliance at a later time, and run the configuration utility again to load the file and provision WebLogic Server after you have downloaded the WebLogic Server and Oracle Traffic Directory software to the appliance.
After you have downloaded the WebLogic Server OVM template to the Oracle Database Appliance, run the configuration utility directly on the Oracle Database Appliance to create a new configuration file (or load an existing configuration file) and provision WebLogic on Oracle Database Appliance.
Prior to running the configuration utility, collect the following network configuration information:
Hostname and IP address to use for the WebLogic Server Administration Server VM.
Hostname and IP address to use for each WebLogic Server Managed Server VM. Depending on the cluster size you choose, you will need two, four, or eight of each.
Virtual IP address to use for the OTD load balancer.
Hostname and IP address to use for the OTD Administration Server VM.
Two hostnames and IP addresses to use for the two OTD Admin VMs.
If you need to create an additional data source for use by your application, you need the following information. The data source must be for an Oracle database that is running on this Oracle Database Appliance.
The JNDI name (data source name) for the data source
The Oracle database service name
The schema username and password to be used to connect the database
Before provisioning the WebLogic domain, you must ensure that you have enough CPU and memory resources available for the size of the cluster that you want to create (two, four, or eight Managed Servers in the cluster). Note that the database that you create on Oracle Database Appliance uses some of the available machine resources. If the database is large, the machine resources that are available for your Managed Server cluster will be significantly smaller, thus impacting performance. For information about sizing the ODA_BASE virtual machine that is used for the database, see "Sizing ODA_BASE on Oracle Database Appliance Virtualized Platform" in Oracle Database Appliance Getting Started Guide.
The following table shows the resource requirements for each available WebLogic cluster size.
To create a configuration file on a Windows or Linux client for later use on Oracle Database Appliance:
Change to the directory where you downloaded and extracted the configuration utility files.
Enter the following command to start the configuration utility:
config.bat (Windows)
./config.sh (Linux or Mac OSX)
If you want to load an existing configuration file, include the path to the file name in the command, for example:
./config.sh /config/myconfig.properties
Configure the WebLogic Server domain as described in "Configuration Utility Screens." On the Summary screen, click Save to save the configuration to a file.
When you are ready to create the new WebLogic domain on Oracle Database Appliance, copy the configuration file to the same directory on Node 0 where you extracted the configuration utility.
Prior to running configuration utility on Oracle Database Appliance:
ensure that the Java bin directory is set in the classpath. JDK 1.6 is the minimum required JDK.
either launch XWindows or redirect the display on ODA_BASE of Node 0.
If you have already created a configuration file on a client as described in the previous section and you want to use that file to provision the WebLogic Server domain, ensure that you have already copied the file to the Oracle Database Appliance.
To run the configuration utility on the Oracle Database Appliance:
Use SSH to log in as root to ODA_BASE of Node 0 of the Oracle Database Appliance:
ssh root@ip_address
Replace ip_address with the IP address of ODA_BASE of Node 0.
Change to the directory where you extracted the configuration utility files.
Enter the following command:
./config.sh config_file
Replace property_file with the path and filename of the saved configuration file. Alternatively, you can omit this parameter and browse to the file from the Welcome screen.
Select the Oracle Database Application version on which you want to run the configuration utility. Enter 1 to select Oracle Database Appliance V1 or 2 to select Oracle Database Appliance X3-2.
To continue, refer to the next section, "Configuration Utility Screens."
After starting the configuration utility:
On the Welcome screen that appears, perform the following tasks:
click Next to continue if you have already loaded a configuration file from the command line or if you want to create a new configuration file.
click Browse to select and load an existing configuration file, which will be used to populate all fields on the subsequent screens.
If you created a configuration file on a remote client and then transferred the file to Oracle Database Appliance, navigate to the directory where you stored the file and select it.
After loading the configuration file, click Next to continue.
On the WebLogic Domain Configuration screen that appears, configure the following settings, and click Next to continue.
| Setting | Description |
|---|---|
|
WebLogic Version |
Select the appropriate Oracle WebLogic Server version to provision on the Oracle Database Appliance. The Oracle VM Template archive corresponding to the selected version must be present in the /OVM/staging directory of You cannot upgrade from one version of Oracle WebLogic Server to another without re-provisioning. If you begin provisioning using Oracle WebLogic Server 12.1.1, you cannot automatically upgrade to Oracle WebLogic Server 12.1.1 without re-provisioning. You must download the 12.1.2 template and re-provision using the 12.1.2 template. |
|
Domain Name |
Enter the name for the Oracle WebLogic Server Domain. Domain names can consist of only alphanumeric characters, underscores (_), and hyphens (-). The domain name must contain at least one alphabetic character and cannot start with a number, and can be a maximum of 100 characters long. |
|
Cluster Name |
Enter the name for the Oracle WebLogic Server cluster. Cluster names can consist of only alphanumeric characters, underscores (_), and hyphens (-) and can be a maximum of 100 characters long. |
|
Cluster Size |
Select the number of Managed Servers that you want to create in the cluster. Note that once the domain is created, you will not be able to add additional Managed Server instances. |
|
Listen Port |
Enter the value to use for the listen port of the Oracle WebLogic Server instances. A network channel that can handle t3s and https will be created on each Oracle WebLogic Server instance listening on this port number. |
|
Password Confirm Password |
Enter the password to use for the Oracle WebLogic Server administration user ( Re-enter the password in the Confirm Password field. |
|
JMS Distributed Destinations |
Select this option to configure JMS Distributed Destinations. If selected, sample JMS Distributed Queue and Topic backed by a highly available persistent store are created and targeted to the Oracle WebLogic Server cluster. You can customize the JMS configuration further post provisioning via the Oracle WebLogic Server Administration Console or using WLST. |
|
JDBC Data Source |
Select this option to create a Data Source that can be used by applications deployed to the WebLogic Server cluster. The Data Source must be for an Oracle Database that is running on the same Oracle Database Appliance machine. If selected, a screen for collecting Data Source configuration is displayed. |
On the WebLogic VM Information screen that appears, configure the following settings, and click Next to continue.
| Setting | Description |
|---|---|
|
Network Interface |
Select the network interface that you want to use for the Oracle WebLogic Server virtual machines. Note that the same network interface cannot be mapped to multiple sub networks, so care must be taken while providing the network information for Oracle WebLogic Server, Oracle Traffic Director, and Oracle Database tiers on the machine.
Ensure that your network switch and cables can support the GbE speed that you select. All network addresses are bonded to ensure redundancy and throughput. For more information, see "Oracle VM Network Infrastructure" in Oracle Database Appliance Getting Started Guide. |
|
Admin Server VM |
Specify the hostname[1] and IP address[2] for the Oracle WebLogic Server Administration Server. |
|
Managed Server n VM |
The number of Managed Server VM rows depends on the value you selected for the cluster size (2, 4, or 8) on the WebLogic Domain Information screen in Step 0 For each of the Managed Server virtual machines, specify the Hostname[1] and IP Address[2]. |
|
Netmask |
Provide the netmask for the subnet to which the IP addresses belong. |
|
Gateway |
Provide the IP address for the gateway to your network. |
[1]: All hostnames must conform to the RFC 952 standard. The network domain that is configured for database provisioning is used to form the fully qualified domain names (FQDN) for the hostnames.
[2]: Only IPV4 format addresses are supported.
On the Load Balancer Information screen that appears, configure the following settings, and click Next to continue.
| Setting | Description |
|---|---|
|
Provision Load Balancer |
Select whether you want to provision a load balancer. By default, the Provision Load Balancer check box is selected. Deselect the check box if you choose not to provision a fronting load balancer for the Oracle Weblogic Server cluster instances. Click Next to continue. If you uncheck the Provision Load Balancer, the details that are loaded from the properties file will be removed. Later, if you need to retrieve the Load Balancer details again, click Back to navigate to the Load Balancer Information screen and select the Provision Load Balancer check box. This option is not available in Oracle WebLogic Server on Oracle Database Appliance Release 2.5.0.0.0. You have to provision a load balancer by default. |
|
Network Interface |
Select the network interface that you want to use for the Oracle Traffic Director (OTD) virtual machines.
Ensure that your network switch and cables can support the GbE speed that you select. All network addresses are bonded to ensure redundancy and throughput. For more information, see "Oracle VM Network Infrastructure" in Oracle Database Appliance Getting Started Guide. |
|
Virtual IP |
Enter the public IP address[2] for the OTD instances. OTD instances will be configured in an Active-Passive configuration to ensure high availability of this IP address. OTD has the ability to fail over on this virtual IP, thus providing high availability of the back-end applications that are deployed on Oracle WebLogic clusters. |
|
Listen Port |
This is the listen port for the OTD instances. Clients can connect using the virtual IP address on this port. |
|
Password Confirm Password |
Enter the password to use for OTD administrator user ( Re-enter the password in the Confirm Password field. |
|
Admin Server VM |
Specify the Hostname[1] and IP Address[2] for the OTD Administration Server virtual machine. |
|
Admin Node n VM |
For each of the Admin Node virtual machines, specify the Hostname[1] and IP Address[2]. |
|
Netmask |
Provide the netmask for the subnet to which the IP addresses belong. |
|
Gateway |
Provide the IP address for the gateway to your network. |
[1]: All hostnames must conform to the RFC 952 standard. The network domain that is configured for database provisioning is used to form the fully qualified domain names (FQDN) for the hostnames.
[2]: Only IPV4 format addresses are supported.
For information about administering and using OTD, refer to the OTD online documentation library at http://docs.oracle.com/cd/E23389_01/index.htm.
If you selected the JDBC Data Source option on the WebLogic VM Information screen, the Data Source Configuration screen is displayed; otherwise, skip to the next step.
Configure the following settings, and then click Next to continue. Note that the data source is only for connecting to the database running on the ODA machine.
| Setting | Description |
|---|---|
|
Select Data Source Type |
Select whether the data source is a WebLogic multi data source, GridLink data source, or Generic data source. For RAC database, you can select either GridLink or Multi Data Source. For RACOne node, you can use only GridLink Data Source. For Enterprise Edition database, you can use only a Generic Data Source. |
|
JNDI Name |
Enter the JNDI name that you want to use for the data source. This name will also be used as the data source name. |
|
Service Name |
Enter the Oracle Database service name. |
|
Database User Name Password |
Enter a valid user name for accessing the database schema. Enter the password for the specified user name. |
|
Support Global Transactions |
Select this option to enable global transactions on the data source. For more information about global transactions, see:
|
On the Summary screen that appears, review the configuration summary to ensure that it is accurate.
If you are running the utility on a local machine to generate a configuration file, or if you are running on the Oracle Database Appliance and you intend to use this configuration file to provision later, click Save and save the configuration file before exiting the utility. If you need to change the configuration, click Back to return to earlier screens.
Click Cancel to close without provisioning Oracle WebLogic Server or saving a configuration file.
If you are running Oracle Database Appliance Configuration Utility for WebLogic Server on an Oracle Database Appliance, and you want to proceed immediately with the provisioning, click Install. See "Domain Creation and Startup."
The Licensed Core Count dialog box is displayed. From the drop-down list, select the number of licensed cores and click OK. Once the selection is made, the provisioning will begin.
After completing the configuration, clicking Install initiates the domain creation process.
The domain creation process clones, configures, and starts the needed virtual machines and the corresponding servers within them.
When the creation process is complete, the Oracle WebLogic Administration Server and Managed Servers (along with Node Managers) are up and running. If a load balancer is configured, Oracle Traffic Director Administration Server and instances are also ready for use.
To avoid a single point of failure with a physical node, the virtual machines are spread across the both physical nodes (Node 0 and Node 1).
Notes:
At initial provisioning, the domain is configured for Development mode. When you change the domain to Production mode, you must restart the WebLogic servers.
Once provisioning is complete, you must allocate CPUs to each node based on the number of CPUs you have licensed. Refer to the next section, "CPU Allocation," for more information.
For Oracle WebLogic Server configured on Oracle Database Appliance V3-2, cores are already created during the provisioning process.
You must allocate cores for nodes using the following procedure if it is an Oracle WebLogic Server configuration on Oracle Database Appliance V1.
After creating the domain, all VMs are using the CPUs from the default-unpinned-pool. Based on the number of cores you have licensed, you must configure the virtual machines to ensure that only the licensed number cores are used by the provisioned WebLogic Server and OTD VMs. The simplest approach is to allocate half of the available cores to each node and configure the WebLogic Server and OTD VMs on a given node to use the cores from that node's CPU pool. See the example later in this section.
Note:
There are many ways to allocate the available CPU resources. For example, you could create a separate CPU pool for each VM. You could also allocate the CPU resources unevenly, for example, if you have 10 licensed cores, allocate one to be shared by both Administration Servers, one for each OTD VMs, and seven for the WebLogic Managed Server VMs. The example in this section describes the simplest approach.
For example, if you have licensed 8 cores, perform the following steps to allocate six cores to each node and configure the VMs on each node to use these CPU pools:
Use the following command to create CPU pools on each node (in this example, wlsCpuPool is the pool name; you can substitute any pool name you want to use):
oakcli create cpupool wlsCpuPool -numcpu 8 -node 0
oakcli create cpupool wlsCpuPool -numcpu 8 -node 1
For each WebLogic Server and OTD VM, enter the following command to configure the VM to use the CPU pool.
oakcli configure vm vm_name -cpupool wlsCpuPool
After executing this command, you need to restart each VM for the change to take effect.
For each VM, enter the following commands to restart the VMs:
oakcli stop vm vm_name
oakcli start vm vm_name
For more information about CPU licensing, see "Core Count and Pay-As-You-Grow" in Oracle Database Appliance Getting Started Guide.
For more information about OAKCLI commands, see "Oracle Database Appliance Command Line Interface (OAKCLI) Utility Reference" in Oracle Database Appliance Getting Started Guide.
This section describes the virtual machine (VM) configuration of the WebLogic domain. It contains the following sections:
The WebLogic Administration Server and Managed Server VM names, as well as the Oracle Traffic Director (OTD) VM names, are based on the physical host number on which the VM resides, the domain name, the cluster name, and in the case of Managed Servers, the Managed Server number. WebLogic Server VM names are prefixed by WLS_, while the OTD VM names are prefixed by OTD_.
The VM name of the WebLogic Administration Server is as follows:
WLS_domainname_AdminServer
The VM name of each Managed Server is as follows, where # is the number of the VM with regard to the cluster:
WLS_domainname_ManagedServer_#
The VM name of the OTD Administration Server is as follows:
OTD_domainname_AdminServer
The VM name of each OTD server is as follows, where # is the number of the VM with regard to the cluster:
OTD_domainname_AdminNode_#
Table 2-4 shows the VM names for the Administration Server and Managed Servers in a domain called mydomain with four WebLogic Managed Servers.
Note:
If the domain name is longer than 13 characters, it will be truncated in each VM name.
Table 2-4 Example Virtual Machine Names
| VM | Physical Host | VM Name |
|---|---|---|
|
WebLogic Administration Server |
1 |
WLS_mydomain_AdminServer |
|
WebLogic Managed Server 1 |
1 |
WLS_mydomain_ManagedServer_1 |
|
WebLogic Managed Server 2 |
2 |
WLS_mydomain_ManagedServer_2 |
|
WebLogic Managed Server 3 |
1 |
WLS_mydomain_ManagedServer_3 |
|
WebLogic Managed Server 4 |
2 |
WLS_mydomain_ManagedServer_4 |
|
OTD Administration Server |
2 |
OTD_mydomain_AdminServer |
|
OTD AdminNode 1 |
1 |
OTD_mydomain_AdminNode_1 |
|
OTD AdminNode 2 |
2 |
OTD_mydomain_AdminNode_2 |
Each VM hosts its own Oracle Enterprise Linux operating system in addition to any installed applications, such as WebLogic Server.
Table 2-5 shows the resources that are provided for each VM.
Each VM has an operating system disk (4GB total space). In addition to this, there are two additional virtual disks mounted at /u01 and /opt/oracle. The /u01 mounted disk contains the WebLogic Server domain configuration and OTD instance home, with 7.5GB total space. The /opt/oracle mounted disk contains the WebLogic Server and OTD installations
Table 2-6 shows key directory locations.
Table 2-6 Key Directory Locations
| Directory or File | Location |
|---|---|
|
WebLogic Server home |
/opt/oracle/middleware/wlserver_version |
|
WebLogic Server domain location |
/u01/domain_name |
|
WebLogic Server domain log file |
/u01/domain_name/servers/admin_server_name/logs/domain_name.log |
|
WebLogic Server server log |
/u01/domain_name/servers/server_name/logs/server_name.log |
|
Middleware home |
/opt/oracle/middleware |
|
Oracle Traffic Director home |
/opt/oracle/trafficdirector |
|
Oracle Traffic Director server instances |
/u01/OTDInstanceHome |
Once provisioning is complete, the individual VMs can be accessed via ssh.
The operating system password of each WebLogic Server VM for root is set to the WebLogic Server password that was specified in the Password field of the WebLogic VM Information screen of the configuration utility.
The operating system password of each OTD VM for root is set to the OTD administrator password that was specified in the Password field of the Load Balancer Configuration screen of the configuration utility.
You have the option to change these passwords afterwards.
When using the configuration utility to create a domain, the domain configuration includes preselected defaults in addition to the settings that are manually defined in a configuration utility session. The preselected defaults are intended to take advantage of the unique capabilities of Oracle Database Appliance and to maximize high availability.
Refer to the following sections for information about the domain configuration that results from the supplied values and preselected settings.
The cluster name is what was specified in the Cluster Name field of the WebLogic VM Information screen.
Table 2-7 lists the settings for the domain Administration Server.
Table 2-7 Administration Server Settings
| Setting | Notes |
|---|---|
|
Name |
Automatically set to AdminServer. |
|
Listen Address |
The listen channel of the default channel is the internal IP address. |
|
External Listen Port |
The Listen Port that was specified in the Listen Port field of the WebLogic VM Information screen, used for https and t3s traffic on the external network. The default is 7001. |
|
Internal Listen Port |
Automatically set to 7001. |
|
Internal Secure Listen Port |
Automatically set to 7002. |
Table 2-8 lists the settings for the Managed Servers in the domain.
Table 2-8 Managed Server Settings
| Setting | Notes |
|---|---|
|
Name |
Automatically set to |
|
Listen Address |
The listen channel of the default channel is the internal IP address. |
|
External Listen Port |
The Listen Port that was specified in the Listen Port field of the WebLogic VM Information screen, used for https and t3s traffic on the external network. The default is 7001. |
|
Internal Listen Port |
Automatically set to 7001. |
|
Internal Secure Listen Port |
Automatically set to 7002. |
|
Machine |
Automatically set to |
|
Cluster |
Automatically set to the cluster name that was specified in the Cluster Name field of the WebLogic VM Information screen. |
|
Transaction Log JDBC Store |
Automatically set to allow for cluster-wide JTA recovery. |
|
Replication Group |
Automatically set to ensure that the secondary server is on a different physical machine. |
|
Preferred Secondary Group |
Automatically set to ensure that the secondary server is on a different physical machine. |
|
JTA Automatic Migration |
Automatically enabled. |
Table 2-9 lists the machine and Node Manager settings for the domain. To support Node Manager, a machine is created for each WebLogic Server virtual machine in the domain.
A non-XA data source is automatically created for transaction log store for high availability. If you selected the JMS Distributed Destinations option on the WebLogic Domain Information screen, a JDBC persistent store for JMS persistence will use this non-XA data source.
If the JMS Distributed Destinations check box was selected on the WebLogic VM Information screen, WebLogic JMS is pre-configured to be highly available and to leverage the Oracle database for persistent messaging. A JMS server, distributed topic, and distributed queue are created and targeted to each WebLogic Managed Server (see Table 2-10), and a JMS module with both a sample queue and topic is targeted to the cluster (see Table 2-11).
Table 2-10 JMS Server Settings
| Setting | Notes |
|---|---|
|
Name |
Automatically set to |
|
Persistent store |
Automatically set to the persistent store that was created specifically for JMS persistence. |
|
Target |
Automatically set to the migratable target instance. |