Platform Domain Template

The following Platform Domain template topics are discussed in this section:

• Template Description
• Creating a Domain Based on the Platform Domain Template
• Configuration and Supporting Files
• Applications and Resources

 

---

Template Description

The Platform Domain template is a domain template that creates a Platform domain in which all WebLogic Platform components are configured in a single JVM or clustered environment. This template is only available upon installation of all WebLogic Platform components.

Purpose

The Platform Domain template is intended for initial development and experimentation of applications that involve interoperation across WebLogic Platform components. The Platform Domain template creates the environment and start scripts necessary for starting a server in this domain.

 

---

Creating a Domain Based on the Platform Domain Template

This section describes how to create a functional domain based on the Platform Domain template. It includes the following topics:

• Process Overview
• Deploying Applications
• Security Compatibility
• Switching Databases

Process Overview

To fully use the Platform Domain template to create a domain, the following components and samples are a prerequisite:

• WebLogic Server
• WebLogic Integration
• WebLogic Portal
• WebLogic Workshop
• WebLogic Workshop Samples

The following table provides an overview of the steps required to create a domain based on the Platform Domain template.

Task	Refer to...
1. Initiate the Configuration Wizard to create a new domain.	Using the Configuration Wizard at the following URL: http://download.oracle.com/docs/cd/E13196_01/platform/docs70/confgwiz/index.html
2. Select the Platform Domain template and respond to the prompts to create a new domain.	Using the Configuration Wizard at the following URL: http://download.oracle.com/docs/cd/E13196_01/platform/docs70/confgwiz/index.html
3. Set up optional domain definitions for network connections, node manager, database connection pools, etc. Note: This is an optional step depending on your domain requirements.	Creating and Configuring WebLogic Domains at the following URL: http://download.oracle.com/docs/cd/E13222_01/wls/docs70/admin_domain/index.html
4. Set up your domain for a clustered environment. Note: This is an optional step depending on your configuration requirements.	Using WebLogic Server Clusters at the following URL: http://download.oracle.com/docs/cd/E13222_01/wls/docs70/cluster/index.html and "How Do I: Deploy a Workshop Application to a Cluster?" in the BEA WebLogic Workshop Help at the following URL: http://download.oracle.com/docs/cd/E13226_01/workshop/docs70/help/guide/deployment/howClusterDeployment.html and "Configuring a Clustered Deployment" in Deploying BEA WebLogic Integration Solutions at the following URL: http://download.oracle.com/docs/cd/E13214_01/wli/docs70/deploy/config.htm
5. Start WebLogic Server.	"Starting and Stopping WebLogic Servers" in the BEA WebLogic Server Administration Guide at the following URL: http://download.oracle.com/docs/cd/E13222_01/wls/docs70/adminguide/startstop.html

 

Deploying Applications

The mode under which the server is running will determine the method of deploying applications in this domain. The modes for deploying applications are:

• Development and Testing

This domain is intended primarily for initial development and experimentation of applications that involve interoperation across WebLogic Platform components.

• Production

For information regarding deploying applications in production mode, refer to the BEA WebLogic Server documentation at the following URL:

http://download.oracle.com/docs/cd/E13222_01/wls/docs70/webapp/deployment.html

Note: It is likely that for production WebLogic Platform applications that interoperate with all WebLogic Platform components, multiple JVMs or clusters will be used for deployment. In this case, different domain configuration requirements exist and this Platform Domain template does not offer the required configuration.Review the following considerations to continue customizing your domain.

After initiating the server, review the various component consoles to determine what applications are deployed.

To deploy runtime data to the server, you must run the datasync using the EBCC or sync.cmd available in the WebLogic Portal component. For more information, refer to the "System Administration" section of the BEA WebLogic Portal Administration Guide at the following URL:

http://download.oracle.com/docs/cd/E13218_01/wlp/docs70/admin/index.htm

Deploying Applications Automatically

One of the following actions allow applications in this domain to be deployed automatically:

• Start the server in development mode.
• Place the exploded directory structure or archive file in the domain directory.

When you deploy the applications automatically, the server automatically adds an entry for your application or module to the config.xml file for the domain. You do not need to manually edit the config.xml file.

Deploying Applications in a Cluster

After initiating the server, review the various component consoles to determine what applications are deployed. The following references provide component-specific information regarding clustering.

• WebLogic Server

Refer to Using WebLogic Server Clusters at the following URL:

http://download.oracle.com/docs/cd/E13222_01/wls/docs70/cluster/index.html

• WebLogic Workshop

WebLogic Workshop applications can easily be deployed on WebLogic Server cluster environments. For information on how to deploy these applications, refer to the BEA WebLogic Workshop documentation at the following URL:

http://download.oracle.com/docs/cd/E13226_01/workshop/docs70/index.html

In this version of WebLogic Workshop, applications that use a JMS message queue rely on the services of a single JMS server and connection factory. This includes applications that use JMS as a transport protocol, the message-buffer property, or timer controls. Future versions of WebLogic Workshop will use the distributed JMS destination capability in WebLogic Server to reduce the dependency on a single JMS server in a clustered environment.

• WebLogic Integration

Refer to "Configuring a Clustered Deployment" in Deploying BEA WebLogic Integration Solutions at the following URL:

http://download.oracle.com/docs/cd/E13214_01/wli/docs70/deploy/config.htm

Security Compatibility

The default security mode for the Platform Domain template is compatibility mode which is realm-based. For more information about WebLogic Platform security, refer to Introduction to WebLogic Platform 7.0 Security at the following URL:

http://download.oracle.com/docs/cd/E13196_01/platform/docs70/secintro/index.html

Switching Databases

The default database available with WebLogic Platform is Pointbase. To switch to another database, refer to the procedures described in "Customizing a Domain for a Database" in the BEA WebLogic Platform Release Notes at the following URL:

http://download.oracle.com/docs/cd/E13196_01/platform/docs70/relnotes/relnotes.html

 

---

Configuration and Supporting Files

The Platform Template will create various directories and scripts under the user_projects/domain directory, where domain is the name of the Platform domain. The scripts and files vary depending on the configuration selected (standalone or clustered). The following table is a list of some of the basic directories and files that are installed with the domain. These scripts and files must be configured properly for the server to boot in the domain.

Note: The following table is not a complete list of all directories and files. The list varies depending on the configuration selected.

Directory	Files	Purpose
user_projects/domain/applications	placeholder.txt	Allows for the create_wli scripts to recognize the existence of domain applications.
user_projects/domain/beaApps/ paymentWSApp		Standard applications for WebLogic Portal support.
user_projects/domain/beaApps/portalApp		Standard applications for WebLogic Portal support.
domain/beaApps/ portalApp	campaign.jar, catalogws.jar, commerce_campaign_bridge_ util.jar, commerce_util.jar, customer.jar, document.jar, ebusiness.jar, ejbadvisor.jar, events.jar, ldapprofile.jar, mail.jar, p13n_util.jar, payment.jar, pipeline.jar, placeholder.jar, portal.jar, portal_util.jar, property.jar, rules.jar, tax.jar, usermgmt.jar	A default portal enterprise application. These JARs enable the portal framework and provide such services as personalization, campaigns, commerce, and LDAP integration. The enterprise application also includes Web applications for: E-Business Control Center data synchronization to the server (datasync/). The WebLogic Portal Administration Tools (tools/) that let you create and manage users, manage portals, and manage commerce features.
user_projects/domain/beaApps/portalApp-project		This directory contains the infrastructure for creating and managing E-Business Control Center data for the enterprise application. The project file (portalApp-project.eaprj) manages all E-Business Control Center data and stores the information necessary to synchronize data to the server and retrieve server-side properties for defining queries. Also included are sets of predefined portal skins and layouts (/application-sync/library/ portal/).
user_projects/domain/beaApps/taxWSApp		Standard applications for WebLogic Portal support.
user_projects/domain/beaApps/workshop		Standard applications for WebLogic Portal support.
user_projects/domain/dbInfo	setdbtype setdbtype.cmd	Sets the database selection for the domain.
user_projects/domain/dbInfo/mssql		Sets basic and extended database variables for the domain.
user_projects/domain/dbInfo/oracle		Sets basic and extended database variables for the domain.
user_projects/domain/dbInfo/pointbase		Sets basic and extended database variables for the domain. By default, the domain will run using Pointbase.
user_projects/domain/dmsBase/doc- schemas	placeholder.txt	Placeholder directories for WebLogic Portals standard content management services. Contains the following: Placeholder directory for storing Web content and its metadata that will be loaded into the database (/Ads). Placeholder directory for storing metadata schemas (/doc-schemas). Schemas provide drop-down list functionality for defining queries against the content in the E-Business Control Center.
user_projects/domain/pointbase	pointbase.ini	Sets the default configuration for the Pointbase database to run when WebLogic Server is started.
user_projects/domain	config.xml	The configuration information for this WebLogic Platform domain Administration Server.
user_projects/domain	create_db.cmd, create_db.sh	These scripts create the database for WebLogic Portal and call create_wli to load the information into the database for use by WebLogic Integration.
user_projects/domain	create_wli.cmd, create_wli.sh	Loads the database information for use by WebLogic Integration.
user_projects/domain	*.properties	Various properties files to provide information for setting up your database, security, runtime configuration guidelines for WebLogic Workshop, etc.
user_projects/domain	startWebLogic.cmd, startWebLogic.sh	Starts the Administration Server for a custom domain.
user_projects/domain	stopWebLogic.cmd, stopWebLogic.sh	Stops the Administration Server for a custom domain.
user_projects/domain	startManagedWebLogic.cmd, startManagedWebLogic.sh	Starts a Managed Server in a custom domain.
user_projects/domain	demokey.pem, democert.pem	Provides sample SSL protocol support for servers in the domain.

 

 

---

Applications and Resources

The Platform Template supports a single JVM or cluster domain configuration. This template creates a shell of a configuration without sample application data provided. It supports all WebLogic Platform components and can be configured to deploy applications across each component.

By default the Platform Template deploys applications for all the WebLogic Platform components. Refer to the config.xml file to determine these applications.

After creating a domain with the Platform Domain template, you can start the server. When you start the server, a Pointbase database connection is initiated for the domain.