Oracle® Weblogic Server and Coherence Evaluation Virtual Assembly
Readme File
E36395-01
September 2012
This document contains the following sections:
-
Purpose and Overview of the Oracle WebLogic Server and Coherence Assembly
-
Topology Diagram for the Oracle WebLogic Server and Coherence Assembly
-
Characteristics of the Oracle WebLogic Server and Coherence Assembly
1 Purpose and Overview of the Oracle WebLogic Server and Coherence Assembly
The Oracle WebLogic Server and Coherence and Coherence assembly is designed to demonstrate how you can quickly download, deploy, and use a prepackaged, Oracle-provided assembly in your supported virtual environment.
This physical environment for this assembly was built using the standard Oracle WebLogic Server and Oracle Fusion Middleware installation and configuration tools. The physical environment was virtualized using Oracle Virtual Assembly Builder.
For more information about virtual assemblies and Oracle Virtual Assembly Builder, see "Introduction" in the Oracle Virtual Assembly Builder User's Guide.
The Oracle WebLogic Server and Coherence assembly provides a preconfigured Oracle WebLogic Server domain that you can use to view a predeployed sample application.
You can deploy your own evaluation applications on the deployed assembly environment. Use the evaluation assembly to help you test and prepare your virtual environment for more robust production-ready assemblies.
2 Roadmap of the Assembly Deployment Process
Table 1 summarizes the steps required to deploy the Oracle WebLogic Server and Coherence in your supported virtual environment.
Table 1 Overview of the Assembly Deployment Process
| Step | More Information |
|---|---|
|
Review the assembly topology and its characteristics so you understand the contents of the assembly and how it will be deployed to your virtual machines. |
Section 3, "Topology Diagram for the Oracle WebLogic Server and Coherence Assembly" Section 4, "Characteristics of the Oracle WebLogic Server and Coherence Assembly" |
|
Review the deployment prerequisites. |
Section 5, "Predeployment Requirements for the Assembly" |
|
Review your deployment options. |
Section 6, "Deployment Options for the Assembly" |
|
Consider the typical post-deployment tasks. |
Section 7, "Typical Post-Deployment Tasks for the Assembly" |
3 Topology Diagram for the Oracle WebLogic Server and Coherence Assembly
Figure 1 shows the default topology of the deployed Oracle WebLogic Server Virtual Assembly.
4 Characteristics of the Oracle WebLogic Server and Coherence Assembly
The following sections describes the characteristics of the Oracle WebLogic Server and Coherence assembly:
4.1 Summary of the Web Tier Configuration
The Web tier of this assembly consists of a single Oracle HTTP Server instance. The Oracle HTTP Server instance is associated with the Oracle WebLogic Server domain, so it can be managed by Oracle Enterprise Manager Fusion Middleware Control.
The Oracle HTTP Server system component (ohs1) can be started and stopped using Fusion Middleware Control or the Oracle Process Management and Notification (OPMN) command line.
For more information about managing and monitoring the Oracle HTTP Server instances, see the Oracle Fusion Middleware Administrator's Guide for Oracle HTTP Server.
4.2 Summary of the Domain Configuration
This virtual assembly consists of a single Oracle WebLogic Server domain called WLS_OHS_COH. The domain contains an Administration Server and two managed servers. When viewed from the Oracle WebLogic Server Administration Console, they appear as shown in Figure 2.
The two managed servers are part of an Oracle WebLogic Server cluster, called Cluster1.
In addition to the managed servers, the domain is also configured for Oracle Coherence. As a result, it contains two Oracle Coherence cache servers, which are part of a single Oracle Coherence cluster. When viewed from the Oracle WebLogic Server Administration Console, the cache servers appear as shown in Figure 3.
4.3 Directory Structure of the Assembly
The directory structure used by the assembly consists of an Oracle base directory that contains:
-
A products directory structure, which contains the product binaries
-
A config directory structure, which contains the Oracle WebLogic Server domain configuration files and Oracle HTTP Server instance configuration files
The assembly directory structure consists of the standard Oracle Fusion Middleware directories, which are referenced using the following variables:
-
ORACLE_BASE: The base directory under which Oracle products are installed.
-
MW_HOME: The Middleware home, which is the directory where the Oracle Fusion Middleware binary files are installed.
-
WL_HOME: The Oracle WebLogic Server home, which is the directory where the Oracle WebLogic Server binary files are installed. The Weblogic Server home is inside the Middleware home.
-
DOMAIN_HOME: The location of the Oracle WebLogic Server domain configuration files. These are typically stored in a separate location from the Middleware home binary files, because a single Middleware home can be used to configure multiple domains.
-
WEBTIER_INSTANCE: The location of the Oracle instance directory for the Oracle HTTP Server instance. An Oracle instance directory contains updateable files, such as configuration files, log files, and temporary files for a specific instance of Oracle HTTP Server.
-
JAVA_HOME: The location where the JDK binary files are installed.
Figure 4 shows a diagram of the basic directory structure for the Oracle WebLogic Server and Coherence assembly. Examples of the actual path values you can use for the Oracle WebLogic Server assembly are shown in Table 2.
Table 2 Example Directory Locations for the Oracle WebLogic Server Assembly
| Directory Variable | Example Value for the Oracle WebLogic Server Assembly |
|---|---|
|
ORACLE_BASE |
/u01/apps/oracle/ |
|
MW_HOME |
ORACLE_BASE/products/fmw_home/ |
|
JAVA_HOME |
MW_HOME/jrockit-jdk1.6.0_29/ |
|
WL_HOME |
MW_HOME/wlserver_10.3/ |
|
WEBTIER_HOME |
MW_HOME/webtier/ |
|
DOMAIN_HOME |
ORACLE_BASE/config/domains/WLS_OHS_COH/ |
|
WEBTIER_INSTANCE |
ORACLE_BASE/config/instances/webtier_instance/ |
4.4 Operating System Used for Appliances in the Assembly
The appliances packaged within this assembly are based on the Oracle Linux 5 operating system. As a result, when you log in to the appliance to perform any command-line functions after deployment on your virtual environment, then you will be using the Oracle Linux operating system.
5 Predeployment Requirements for the Assembly
Before you deploy the Oracle WebLogic Server and Coherence assembly, consider the following predeployment requirements:
5.1 User Requirements
Before you deploy this assembly, you should be familiar with basic Oracle WebLogic Server administration tools and tasks. For example, you should have previously deployed and managed a physical Oracle WebLogic Server environment.
5.2 Oracle Virtual Assembly Builder and Oracle VM Requirements
The deployment of this assembly has been tested using the following Oracle software products:
-
Oracle VM 3.0.3
-
Oracle Virtual Assembly Builder 11g Release 1 (11.1.1.6.0)
For the latest information on certified versions of Oracle Virtual Assembly Builder and Oracle VM, see the Oracle Fusion Middleware Supported System Configurations on the Oracle Technology Network (OTN).
Before you begin the deployment process, you should have:
-
Downloaded and installed Oracle VM Server and Oracle VM Manager.
-
Created at least one Virtual Server and one server pool; when you create the Virtual Server, note the host name and IP address of the server. You will need this in order to deploy the assembly successfully.
-
Obtained host names and IP addresses to use for the virtual machines (VMs) shown in Figure 1.
-
Downloaded and configured an instance of Oracle Virtual Assembly Builder.
5.3 Database Requirements
The Oracle WebLogic Server evaluation assembly does not require a database. There is no need to configure any schemas or database connections before deployment.
Optionally, you can create data sources to an existing database after you deploy the assembly. You create data sources for your applications using the standard Oracle WebLogic Server management tools the same way you do in a physical software installation environment.
For more information, see Section 7.1, "Accessing the Oracle WebLogic Server Administration Console and Fusion Middleware Control for the Deployed Assembly".
6 Deployment Options for the Assembly
You can deploy this assembly using Oracle Virtual Assembly Builder Studio.
|
Note: The instructions here are a summary of the deployment steps, including specific information required to deploy the Oracle WebLogic Server evaluation assembly. For general information about deploying assemblies with Oracle Virtual Assembly Builder Studio, see "Operations Related to Deployment," in the Oracle Virtual Assembly Builder User's Guide. |
For specific information on deploying the Oracle WebLogic Server evaluation assembly with Oracle Virtual Assembly Builder Studio, see the following sections:
-
Setting Deployment Plan Properties for the Oracle WebLogic Server and Coherence Assembly
-
Deploying the Assembly Using Oracle Virtual Assembly Builder Studio
6.1 Creating the Oracle WebLogic Server Assembly Deployment Plan with Oracle Virtual Assembly Builder Studio
After you download the assembly, create and modify the assembly deployment plan using Oracle Virtual Assembly Builder Studio, as follows:
-
Open Oracle Virtual Assembly Builder Studio.
-
From the File menu, select Import and import the assembly into Oracle Virtual Assembly Builder Studio.
Note that the import operation can take a few minutes to complete, depending upon the available resources and the size of the assembly.
-
Create a new deployment plan for the assembly:
-
From the View menu, select Deployment Plans to display the Deployment Plans navigator.
-
Right-click the name of the assembly in the navigator and select New Deployment Plan.
-
Enter a name for the deployment plan and click OK.
-
6.2 Viewing the Appliances in the Deployment Plan Editor
The Oracle WebLogic Server evaluation assembly consists of two appliances:
-
The Oracle HTTP Server appliance (FMW_Ohs)
-
The Oracle WebLogic Server appliance (FMW_Wls)
When you create a new deployment plan for the assembly, Oracle Virtual Assembly Builder Studio displays a graphical representation of the two appliances. You can then select an appliance to edit the properties of the appliance.
In addition, the Oracle WebLogic Server appliance (FMW_Wls) contains three components:
-
CacheCluster, which represents the Oracle Coherence cluster
-
AdminServer, which represents the Administration Server of the Oracle WebLogic Server domain
-
Cluster1, which represents the Oracle WebLogic Server cluster that contains the two Oracle WebLogic Server managed servers
To view the properties for a component, click the component name in the graphical representation of the appliance in the Deployment Plan Editor.
6.3 Setting Deployment Plan Properties for the Oracle WebLogic Server and Coherence Assembly
There are four sets of mandatory deployment plan properties that you must set before you can successfully deploy the assembly. One set is for the Oracle HTTP Server appliance, and three are for the components of the Oracle WebLogic Server appliance.
To display the property inspector for an appliance, select the appliance title bar, and then view the Inspector navigator on the right side of the main Oracle Virtual Assembly Builder Studio window.
To display the property inspector for an appliance component, select the component name, and then view the Inspector pane.
For more information, see the following:
6.3.1 FMW_Ohs Appliance Properties
Table 3 describes the mandatory deployment plan properties you must set for the Oracle HTTP Server appliance.
Table 3 Required Deployment Plan Properties for the Oracle HTTP Server Appliance
| Category | Required Properties | Description | Example Values |
|---|---|---|---|
|
deployer |
template-root-user-password |
Enter a password for the operating system |
Standard, security-approved password |
|
hardware |
resource-memory |
Enter amount of memory required for this appliance, which represents the virtual machine for the Oracle HTTP Server. For the Oracle HTTP Server appliance, Oracle recommends one gigabyte of memory. |
1024 |
|
network |
default-gateway dns-domains dns-servers hostname-n |
Enter the details about the host names and IP addresses you assigned when you set up for the virtual machine that will host the Oracle HTTP Server in the Oracle VM environment, as described in Section 5, "Predeployment Requirements for the Assembly". |
10.133.40.1 example.com 13.33.222.55 vm0042 |
|
interface-1 |
ip_address.0 netmask usedhcp |
The IP address entered here must match the IP address of the hostname you entered in the network properties for the appliance. |
10.111.44.222 255.255.248.0 false |
|
listen-n |
port |
Review the port numbers for the Oracle HTTP Server listen address. These are automatically generated, but you should make a note of them so you can easily access the Oracle HTTP Server after deployment. |
15503 |
6.3.2 FMW_Wls Appliance CacheCluster Component Properties
This section provides information on setting the properties of the CacheCluseter Component, which represents the Oracle Coherence cluster in the assembly.
Refer to the following sections for more information about setting the deployment properties for the CacheCluster appliance:
6.3.2.1 Setting the CacheCluster Appliance Deployment Properties
Table 4 describes the mandatory deployment plan properties you must set for the CacheCluster component of the Oracle WebLogic Server appliance in the assembly.
Table 4 Required Deployment Plan Properties for the CacheCluster Component of the Oracle WebLogic Server Appliance
| Component/Virtual Machine | Required Properties | Description | Example Values |
|---|---|---|---|
|
deployer |
template-root-user-password |
Enter a password for the operating system |
Standard, security-approved password |
|
hardware |
resource-cpu-number |
Enter the number of CPUs required for this component. Because the Coherence cluster (CacheCluster) requires two virtual machines, Oracle recommends you enter "2" as the value for this property. |
2 |
|
hardware |
resource-memory |
Enter the amount of memory required for this appliance, which represents the Oracle Coherence cluster. For more information, see Section 6.3.2.2, "About the Resource Memory Settings for the Oracle Coherence Appliance". |
1024 |
|
network |
default-gateway dns-domains dns-servers hostname-n |
Enter the details about the host names and addresses you assigned for the Coherence cluster virtual machines when you set up the Oracle VM environment, as described in Section 5, "Predeployment Requirements for the Assembly". |
10.133.40.1 example.com 13.33.222.55 vm0043 |
|
interface-1 |
ip_address.0 netmask usedhcp |
The IP address entered here must match the IP address of the hostname you entered in the network properties for the component. |
10.111.44.222 255.255.248.0 false |
|
listen-n |
port |
Review the port numbers for the Oracle HTTP Server listen address. These are automatically generated, but you should make a note of them so you can easily access the Oracle HTTP Server after deployment. |
15503 |
6.3.2.2 About the Resource Memory Settings for the Oracle Coherence Appliance
For production environments, Oracle typically recommends two gigabytes of memory for each Oracle Coherence virtual server. However, for this evaluation assembly, Oracle recommends one gigabyte of memory for the Coherence appliance.
6.3.3 FMW_Wls Appliance AdminServer Component Properties
Table 5 describes the mandatory deployment plan properties you must set for the AdminServer component of the Oracle WebLogic Server appliance in the assembly.
Table 5 Required Deployment Plan Properties for the CacheCluster Component of the Oracle WebLogic Server Appliance
| Component/Virtual Machine | Required Properties | Description | Example Values |
|---|---|---|---|
|
deployer |
template-root-user-password |
Enter a password for the operating system |
Standard, security-approved password |
|
hardware |
resource-cpu-number |
Enter the number of CPUs required for this component. Because the Administration Server requires only one virtual machines, Oracle recommends you enter "1" as the value for this property. |
1 |
|
hardware |
resource-memory |
Enter amount of memory required for this appliance, which represents the Administration Server virtual machine. For this appliance, Oracle recommends one gigabyte of memory. |
1024 |
|
network |
default-gateway dns-domains dns-servers hostname-n |
Enter the details about the host names and addresses you assigned for the Administration Server virtual machines when you set up the Oracle VM environment, as described in Section 5, "Predeployment Requirements for the Assembly". |
10.133.40.1 example.com 13.33.222.55 vm0043 |
|
default |
admin-password |
Enter a password, which will be required when you log in to the Oracle WebLogic Server Administration Console using the default weblogic user name. |
Enter a secure password |
|
default |
port |
Review the port numbers for the Administration Server listen address. This value is automatically generated, but you should make a note of it, so you can easily access the Administration Server Console after deployment. |
24761 |
|
interface-1 |
ip_address.0 netmask usedhcp |
The IP address entered here must match the IP address of the hostname you entered in the network properties for the component. |
10.111.44.222 255.255.248.0 false |
6.3.4 FMW_Wls Appliance Cluster1 Component Properties
Table 6 describes the mandatory deployment plan properties you must set for the Cluster1 component of the Oracle WebLogic Server appliance in the assembly.
Table 6 Required Deployment Plan Properties for the CacheCluster Component of the Oracle WebLogic Server Appliance
| Component/Virtual Machine | Required Properties | Description | Example Values |
|---|---|---|---|
|
deployer |
template-root-user-password |
Enter a password for the operating system |
Standard, security-approved password |
|
hardware |
resource-cpu-number |
Enter the number of CPUs required for this component. Because the managed server cluster (cluster1) requires two virtual machines, Oracle recommends you enter "2" as the value for this property. |
2 |
|
hardware |
resource-memory |
Enter amount of memory required for this appliance, which represents the managed server cluster. For this component, Oracle recommends one gigabyte of memory for each server. |
2048 |
|
network |
default-gateway dns-domains dns-servers hostname-n |
Enter the details about the host names and addresses you assigned for the managed server virtual machines when you set up the Oracle VM environment, as described in Section 5, "Predeployment Requirements for the Assembly". |
10.133.40.1 example.com 13.33.222.55 vm0043 |
|
interface-1 |
ip_address.0 netmask usedhcp |
The IP address entered here must match the IP address of the hostname you entered in the network properties for the component. |
10.111.44.222 255.255.248.0 false |
|
listen-n |
port |
Review the port numbers for the cluster listen address. These are automatically generated, but you should make a note of it so you can easily troubleshoot connection issues after deployment. |
17016 |
6.4 Deploying the Assembly Using Oracle Virtual Assembly Builder Studio
To deploy the assembly after you create and edit the deployment plan, you can use Oracle Virtual Assembly Builder Studio, or you can use the Oracle Virtual Assembly Builder command line (abctl).
For more information, see "Operations Related to Deployment," in the Oracle Virtual Assembly Builder User's Guide.
7 Typical Post-Deployment Tasks for the Assembly
The following sections describe some typical evaluation tasks you can perform on the Oracle WebLogic Server and Oracle Coherence assembly:
7.1 Accessing the Oracle WebLogic Server Administration Console and Fusion Middleware Control for the Deployed Assembly
After you deploy the assembly, you can use the Oracle WebLogic Server Administration Console and Fusion Middleware Control to perform typical Oracle WebLogic Server management tasks.
To access the Oracle WebLogic Server Administration Console:
admin_server_vm:port/console
To access Fusion Middleware Control:
admin_server_vm:port/em
7.2 Viewing and Using the Oracle Coherence Counter Demo Application
The Counter Web application is a simple counter implemented as a JSP. The counter is stored as an HTTP session attribute and increments each time the page is accessed. The application demonstrates how Oracle Coherence ActiveCache caches session information for Web application instances across WebLogic Server instances.
In the Oracle WebLogic Server and Oracle Coherence assembly, the counter application is pre-deployed to the two managed servers in the Oracle WebLogic Server cluster. Coherence*Web automatically serializes and replicates the attribute across both server instances. You can then access each application instance from a different browser window to demonstrate that the same session attribute is used among the instances.
|
Note: When you test the caching capabilities of Oracle Coherence, be sure to access the application using the Oracle HTTP Server host URL. |
You can also use the counter application to demonstrate the failover capabilities of the assembly topology, as follows:
-
In your Web browser, access the counter application via the HTTP Server:
http://webserverhost:port/counter/counter.jsp
-
Refresh the screen several times and watch the counter application increment each time in invoke the application.
-
In a separate browser window or tab, display the Oracle WebLogic Server Administration Console for the domain, and navigate to the Servlets page to view information about the count.jsp servlet.
For more information, see "Monitor Web applications and servlets" in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help.
-
Note the value displayed in the Invocation Total Count column for Servlet
counter.jsp.This number represents the number of times the counter application has been invoked. In this case, you will notice that the application has been invoked multiple times from only one of the managed servers (M1 or M2).
-
From the same Administration Console browser window, use the Administration Console to stop the managed server with the most counter.jsp invocations.
For more information, see "Shut down a server instance" in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help.
-
After the managed server is shut down, continue refreshing the browser window that displays the counter application, and note that the counter continues to increment.
-
In the Administration Console window, navigate back to the Servlets page and note that the invocations of counter.jsp file are now being served from the other managed server.
-
Restart the managed server that you shut down.
For more information about using the counter application, see "Verify the Example" in the Oracle Coherence Tutorial for Oracle Coherence.
8 Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Weblogic Server and Coherence Evaluation Virtual Assembly Readme,
E36395-01
Copyright © 2012, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
