This chapter describes the WebLogic domain and extension templates that are used to configure WebLogic domains for various Fusion Middleware product installations. For most of these templates, you can create or extend domains by selecting the template on the Templates screen of the Oracle Fusion Middleware Configuration Wizard. You can also use the WebLogic Scripting Tool (WLST) in offline mode to create or extend domains using these templates. See Template Tools, for more information.
Your product installation includes only those templates that are relevant to your product. Some templates in this chapter, such as the Oracle JRF template, apply to domains for multiple Fusion Middleware products. Other templates apply only to domains for a single Fusion Middleware product, and are therefore not included with any other Fusion Middleware product installations.
This chapter contains the following sections:
Each template section contains the following template information:
Template type—A template can be either a domain or an extension template.
A domain template defines the full set of resources within a WebLogic domain, including the Administration Server, clusters, servers, applications, services, security options, and other options. A given product installation is based on one domain template.
An extension template adds resources, such as applications, libraries, services, and other options, to an existing domain. A given product installation may require one or more extension templates to complete the domain.
A group template is a special XML file that is a collection of template dependencies. It simplifies the process of pulling in multiple dependent templates by the template that requires them.
When creating your product domain using the Configuration Wizard, you can select the domain and extension templates concurrently for the products you want to install.
Category—The category in which the template is listed on the Templates screen of the Configuration Wizard.
Template name and version—The template (product) name and template version. If the template is selectable on the Templates screen of the Configuration Wizard, this is the name as it is listed in the Configuration Wizard.
Template dependencies—Prerequisite templates that provide resources required by the template being described in a given section, in the order in which they must be added to the domain. For more information on template dependencies, see Template Dependencies.
Template JAR file and location—The JAR filename and its location in the Oracle home directory. You need this information only if you plan to use WLST scripts to set up a product domain.
This section describes templates that add necessary resources to many of the Fusion Middleware product domains. The following templates are described here:
Note:
The templates described in this section must be used as provided. Do not modify them in any way. Doing so can cause issues in your domain.
The Oracle Java Required Files (JRF) template configures components that are not included in the WebLogic Server installation. These components provide common functionality for Oracle business applications and application frameworks. The SOA Suite and WebCenter are examples of applications and frameworks that depend on the JRF template.
The JRF template is also used independently to configure domains that contain applications that are developed using Oracle ADF and other core components.
The following table provides key information about this template.
Table 3-1 Oracle JRF Template Details
| Template Detail | Information |
|---|---|
|
Template type |
Extension |
|
Category |
Oracle |
|
Template name and version |
Oracle JRF - 12.1.2.0 |
|
Template Dependencies |
|
|
Template JAR file and location |
ORACLE_HOME/oracle_common/common/templates/wls/oracle.jrf_template_12.1.2.jar |
The Oracle JRF Asynchronous Web Services template creates default JMS resources that are required for JRF Asynchronous Web Services running on a WebLogic Server domain. This template does not create the JMS UDDs (Uniform Distributed Destinations) required for clusters in the domain. To create the default JMS UDDs, a separate WLST script, jrfws-async-createUDDs.py, is provided.
This template must be targeted to non-clustered servers in the domain.
The following table provides key information about this template.
Table 3-2 Oracle JRF Asynchronous Web Services Template Details
| Template Detail | Information |
|---|---|
|
Template type |
Extension |
|
Category |
Oracle |
|
Template name and version |
Oracle JRF Web Services Asynchronous Services - 12.1.2.0 |
|
Template Dependencies |
Oracle JRF - 12.1.2.0 |
|
Template JAR file and location |
ORACLE_HOME/oracle_common/common/templates/wls/oracle.jrf.ws.async_template_12.1.2.jar |
This template creates JMS queues for JRF SOAP/JMS Web services.
Table 3-3 Oracle JRF Asynchronous Web Services Template Details
| Template Detail | Information |
|---|---|
|
Template type |
Extension |
|
Category |
Oracle |
|
Template name and version |
Oracle JRF SOAP/JMS Web Services - 12.1.2.0 |
|
Template Dependencies |
Oracle JRF - 12.1.2.0 |
|
Template JAR file and location |
ORACLE_HOME/oracle_common/common/templates/wls/oracle.jrf.ws.soapjms_template_12.1.2.jar |
This template is required for Fusion Middleware components and applications that were built using Oracle Application Development Framework.
The following table provides key information about this template.
Table 3-4 Oracle OPSS Extensions for JRF Template Details
| Template Detail | Information |
|---|---|
|
Template type |
Extension |
|
Template name and version |
Oracle OPSS Extensions for JRF - 12.1.2.0 |
|
Template Dependencies |
Oracle JRF - 12.1.2.0 |
|
Template JAR file and location |
ORACLE_HOME/oracle_common/common/templates/wls/oracle.opss_template_12.1.2.jar |
This template is included if Oracle JDeveloper is installed. It provides development mode logging for Oracle ADF. Fine logging for oracle.jbo is exposed.
The following table provides key information about this template.
Table 3-5 Oracle ADF Development Mode Logging Template Details
| Template Detail | Information |
|---|---|
|
Template type |
Extension |
|
Template name and version |
Oracle ADF Development Mode Logging - 12.1.2.0.0 |
|
Template Dependencies |
None |
|
Template JAR file and location |
ORACLE_HOME/jdeveloper/common/templates/jdeveloper/adf.fine.logging_12.1.2.jar |
This section describes the Enterprise Manager templates that are used to add Enterprise Manager resources to the WebLogic domains for various Fusion Middleware products. There are currently three Enterprise Manager JAR files, all of which are installed when you select the product on the Templates screen of the Fusion Middleware Configuration Wizard.
This template adds Oracle Enterprise Manager Fusion Middleware Control to your domain. Fusion Middleware Control is a Web browser-based, graphical user interface that you can use to monitor and administer Oracle Fusion Middleware.
Together with the Oracle WebLogic Server Administration Console, Fusion Middleware Control provides tools to help you manage the Oracle Fusion Middleware environment, including the Oracle WebLogic Server domain, the Oracle Fusion Middleware components you have installed and configured, and the applications you deploy.
For more complete information about Oracle Enterprise Manager Fusion Middleware Control, see "Getting Started Using Oracle Enterprise Manager Fusion Middleware Control" in the Administering Oracle Fusion Middleware.
Note:
This template must be used as provided. Do not modify it in any way. Doing so can cause issues in your domain.
The following table provides key information about this template.
Table 3-6 Oracle Enterprise Manager Template Details
| Template Detail | Information |
|---|---|
|
Template type |
Extension |
|
Template name and version |
Oracle Enterprise Manager - 12.1.2.0 |
|
Template Dependencies |
|
|
Template JAR file and location |
This template consists of multiple template JAR files. These JAR files are located in the following directory after you install Oracle Fusion Middleware: ORACLE_HOME/em/common/templates/wls The template consists of the following JAR files in the templates directory:
|
This section describes the Coherence template that is provided when Coherence is installed with WebLogic Server.
This template adds a default Coherence cluster, defaultCoherenceCluster, to the WebLogic domain and sets the listen port for the cluster to 8088.
Table 3-7 WebLogic Coherence Cluster Extension Template Details
| Template Detail | Information |
|---|---|
|
Template type |
Extension Template |
|
Template name and version |
WebLogic Coherence Cluster Extension - 12.1.2.0 |
|
Template Dependencies |
|
|
Template JAR file and location |
WL_HOME/common/templates/applications/wls_coherence.jar |
This section describes the OWSM template that is provided for adding OWSM resources to various Fusion Middleware product domains. There is currently one OWSM template available, as described in Oracle WSM Policy Manager Template.
Note:
The templates described in this section must be used as provided. Do not modify them in any way. Doing so can cause issues in your domain.
The WSM PM template is used to deploy and configure the WSM Policy Manager Java EE application.
The following table provides key information about this template.
Table 3-8 Oracle WSM Policy Manager Template Details
| Template Detail | Information |
|---|---|
|
Template type |
Extension |
|
Template name and version |
Oracle WSM Policy Manager - 12.1.2.0 |
|
Template Dependencies |
|
|
Template JAR file and location |
ORACLE_HOME/oracle_common/common/templates/wls/oracle.wsmpm_template_12.1.2.jar |
This section describes the following Oracle Identity Management (IDM) templates:
With the expanded domain topology profile, this template provides a domain type that supports the Oracle Virtual Assembly Builder Deployer cluster service, and allows you to configure an Oracle WebLogic Server cluster and a Coherence cluster and target the Oracle WebLogic Server cluster to use the Coherence cluster.
You can configure the Coherence cluster with either Well Known Addresses (WKA) or multicast communication. If you do not specify a communication type, WKA is set as for cluster communication.
Oracle Virtual Assembly Builder Deployer uses Coherence cluster data partitioning to distribute work. The deployerId is used as a key association, where all data specific to a particular deployment id is guaranteed to exists on the same node. When you initiate an asynchronous request (such as a deploy, undeploy, or scale operation), the request is handled by the node on which the data is partitioned at that time. The same node handles the request even if data gets repartitioned to another node.
If a node with running requests goes down or crashes, the requests are cancelled, because none of the Deployer asynchronous operations are idempotent. That is, if a request is initiated, it cannot be rolled back because the work is distributed amongst multiple tiers.
You must re-initiate such requests by cleaning up the previous state. For example: if a deploy operation gets cancelled, the corresponding deployment object is marked as 'Failed' with the reason as 'cancelled'. You must invoke an explicit cleanup operation by the to cleanup the deployment, then create another deployment object and start the deploy operation.
With the compact domain topology profile, this template provides for a standalone Oracle Virtual Assembly Builder Deployer.
The following table provides key information about this template.
Table 3-9 Oracle Virtual Assembly Builder Template Details
| Template Detail | Information |
|---|---|
|
Template type |
Extension |
|
Category |
Uncategorized |
|
Template name and version |
Oracle Virtual Assembly Builder Deployer - 12.1.2.0 |
|
Template Dependencies |
Oracle JRF - 12.1.2.0 |
|
Template JAR file and location |
OVAB_HOME/common/templates/wls/oracle.ovab.deployer.template_12.1.2.jar |
|
Domain topology profiles |
Compact and Expanded |
This section describes the following Oracle Data Integrator templates:
Note:
The ODI Master Datasource template, the ODI Base template, and the ODI Work Datatsource template, which are listed as dependencies for other Oracle Data Integrator templates, are internal templates. They are automatically called when you select other ODI templates in Configuration Wizard, or specify an ODI template in a WLST script. Therefore, they are not displayed as selectable components in Configuration Wizard, and you do not have to specify them in your WLST scripts.
Use the Oracle Data Integrator Standalone Agent when your ODI installation is not being managed by WebLogic Server.
The following table provides key information about this template.
Table 3-10 Oracle Data Integrator Standalone Agent Template Details
| Template Detail | Information |
|---|---|
|
Template type |
Extension |
|
Category |
Oracle Data Integrator |
|
Template name and version |
Oracle Data Integrator Collocated Agent - 12.1.2.0 |
|
Template Dependencies |
|
|
Template JAR file and location |
ORACLE_HOME/odi/common/templates/wls/odi_cam_unmanaged_template_12.1.2.jar |
Use the Oracle Data Integrator Standalone Collocated Agent template when you install ODI collocated with WebLogic Server.
The following table provides key information about this template.
Table 3-11 Oracle Data Integrator Standalone Collocated Agent Template Details
| Template Detail | Information |
|---|---|
|
Template type |
Extension |
|
Category |
Oracle Data Integrator |
|
Template name and version |
Oracle Data Integrator Standalone Collocated Agent - 12.1.2.0 |
|
Template Dependencies |
|
|
Template JAR file and location |
ORACLE_HOME/odi/common/templates/wls/odi_cam_managed_template_12.1.2.jar |
The Oracle Data Integrator Agent template deploys the ODI Agent application, required libraries and the ODI Master repository data source.
The following table provides key information about this template.
Table 3-12 Oracle Data Integrator Agent Template Details
| Template Detail | Information |
|---|---|
|
Template type |
Extension |
|
Category |
Oracle Data Integrator |
|
Template name and version |
Oracle Data Integrator Agent - 12.1.2.0 |
|
Template Dependencies |
|
|
Template JAR file and location |
ORACLE_HOME/odi/common/templates/wls/odi_agent_template_12.1.2.jar |
The Oracle Data Integrator Agent Libraries template deploys shared libraries required for the ODI Agent.
The following table provides key information about this template.
Table 3-13 Oracle Data Integrator Agent Libraries Template Details
| Template Detail | Information |
|---|---|
|
Template type |
Extension |
|
Category |
Oracle Data Integrator |
|
Template name and version |
Oracle Data Integrator Agent Libraries - 12.1.2.0 |
|
Template Dependencies |
|
|
Template JAR file and location |
ORACLE_HOME/odi/common/templates/wls/odi_agent_libraries_template_12.1.2.jar |
The Oracle Data Integrator Console template deploys the ODI Console application.
The following table provides key information about this template.
Table 3-14 Oracle Data Integrator Console Template Details
| Template Detail | Information |
|---|---|
|
Template type |
Extension |
|
Category |
Oracle Data Integrator |
|
Template name and version |
Oracle Data Integrator Console - 12.1.2.0 |
|
Template Dependencies |
|
|
Template JAR file and location |
ORACLE_HOME/odi/common/templates/wls/odi_repository_explorer_template_12.1.2.jar |
The Oracle Enterprise Manager Plugin for ODI template deploys the ODI Plugin for Oracle Enterprise Manager.
The following table provides key information about this template.
Table 3-15 Oracle Enterprise Manager Plugin for ODI Template Details
| Template Detail | Information |
|---|---|
|
Template type |
Extension |
|
Category |
Oracle |
|
Template name and version |
Oracle Enterprise Manager Plugin for ODI - 12.1.2.0 |
|
Template Dependencies |
|
|
Template JAR file and location |
ORACLE_HOME/em/common/templates/wls/oracle.em_odi_template_12.1.2.jar |
The Oracle HTTP Server (OHS) domain templates are extension templates used to add OHS resources and services to a Basic WebLogic Server domain. OHS is the Web server component for Oracle Fusion Middleware. It provides a listener for Oracle WebLogic Server and the framework for hosting static pages, dynamic pages, and applications over the Web. The specific OHS template you will use depends on whether you are implementing OHS in a collocated or standalone environment.
This chapter contains these sections:
Use the Oracle HTTP Server (Collocated) domain template when you want your OHS implementation to serve one or more FMW domains (for example, when you want OHS to front requests for a SOA domain) or when you want to take advantage of the advanced management capabilities provided by FMW Control.
Table 3-16 Oracle HTTP Server (Collocated) Domain Template Details
| Template Detail | Information |
|---|---|
|
Template type |
Extension |
|
Category |
Uncategorized |
|
Template name and version |
Oracle HTTP Server (Collocated)—12.1.2.0 |
|
Template Dependencies |
Oracle Enterprise Manager for WEBTIER—12.1.2.0 |
|
Template JAR file and location |
MW_HOME/ohs/common/templates/wls/ohs_managed_template_12.1.2.jar |
|
Domain topology profiles |
Compact and Expanded. |
|
Category |
Undefined |
Use the Oracle HTTP Server (Standalone) domain template when you do not want your OHS implementation to front an FMW domain and do not need the management functionality provided by FMW Control or when you want to keep OHS in a DMZ and you do not want to open management ports used by the Node Manager.
Table 3-17 Oracle HTTP Server (Standalone) Domain Template Details
| Template Detail | Information |
|---|---|
|
Template type |
Extension |
|
Category |
Oracle HTTP Server |
|
Template name and version |
Oracle HTTP Server (Standalone)—12.1.2.0 |
|
Template Dependencies |
None |
|
Template JAR file and location |
MW_HOME/ohs/common/templates/wls/ohs_standalone_template_12.1.2.jar |
|
Domain topology profiles |
None defined. |
|
Server groups |
Undefined |