WebLogic Portal Domain Template

The WLP Domain template is used by the Configuration Wizard to create a WebLogic Portal domain. The domain that is created is a foundation upon which you build portals. The domain includes the configuration files, database, and scripts that define and run your server environment, provides a default security realm and predefined system administrators, and provides a set of WebLogic Portal administration tools. The template also creates supporting files and services for building portals and developing personalization and commerce functionality.

The template, which is made up of a central template file and many directories and files, is located in a JAR file in the following directory:

Inside the portal.jar file, the central template file, template.xml, is located in the META-INF subdirectory.

Other files and directories used by the template, but not included in portal.jar, are located in <BEA_HOME>/weblogic700/common/templates/shared.

Use the WLP Domain template in the Configuration Wizard to create a new domain that lets you build portals, take advantage of portal functionality, and implement WebLogic Portal's standard set of powerful personalization and commerce services.

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

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

Task	Refer to...
1. Initiate the Configuration Wizard to create a new domain.	Using the Configuration Wizard at the following URL: http://edocs.bea.com/platform/docs70/confgwiz/index.html
2. Select the WLP Domain template and respond to the prompts to create a new domain.	Using the Configuration Wizard at the following URL: http://edocs.bea.com/platform/docs70/confgwiz/index.html
3. If you set created a clustered domain, additional steps are required.	Completing the Configuration of a Clustered Domain.
4. Start WebLogic Server.	"Starting and Stopping the Server" in the "System Administration" section of the BEA WebLogic Portal Administration Guide at the following URL: http://edocs.bea.com/wlp/docs70/admin/sysadmin.htm

When running a clustered WebLogic Portal domain, data that is synchronized from the E-Business Control Center to the admin server must be properly replicated across all managed servers. Perform the following steps to ensure a sound synchronization process.

Also, if you are using WebLogic Portal's default content management services, you must perform additional setup tasks.

You can deploy a Web application with the HttpClusterServlet for your cluster to the admin server of the cluster and make it the admin server's default Web application. In this situation, be sure to map only the Web applications that are available through the cluster (for example, the WebLogic Portal Administration Tools at /portalAppTools/* and any portals or Web applications you add). In particular, be sure that /p13nConsole/* and /portalAppDataSync/* are not mapped by the HttpClusterServlet (if datasync is configured for the cluster).

If you use WebLogic Portal's standard content management services, do one of the following:

The WLP Domain template will create various directories and scripts under the new domain. The following table is a list of some of the directories and files that are installed with the domain.

Note: The following table is not a complete list of all directories and files.

Directory	Files	Purpose
<domain>	config.xml	Defines your server configuration.
	create_db*, db_settings.properties	Database creation script and properties file (for storing database server name, location, and so on).
	loadads, loaddocs	Scripts for loading content metadata into the database when using WebLogic Portal's standard content management services.
	start, stop	Scripts for starting and stopping the server(s).
	demokey.pem, democert.pem	Provide sample SSL protocol support for servers in the domain.
<domain>/beaApps		Contains the directories of all enterprise applications and enterprise-level services in the domain, as explained in the following rows.
<domain>/beaApps/ paymentWSApp	payment.jar	Provides services for creating or connecting to a third-party payment Web service for commerce transactions.
<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	The default portal enterprise application under which you can build portals. 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.
<domain>/beaApps/ portalApp-project	portalApp-project.eaprj	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/).
<domain>/beaApps/ taxWSApp	tax.jar	Provides services for creating or connecting to a third-party tax Web service for commerce transactions.
<domain>/dmsBase		Contains placeholder directories for WebLogic Portal's standard content management services. Contains the following: /Ads - Placeholder directory for storing Web content and its metadata that is loaded into the database with the loadads script. /doc-schemas - Placeholder directory for storing metadata schemas. Schemas provide drop-down list functionality for defining queries against the content in the E-Business Control Center.
<domain>/pointbase	pointbase.ini, wlportal.dbn, wlportal$1.wal	pointbase.ini contains the default configuration for the PointBase database to run when the server is started. wlportal.dbn is the database node file used to store the actual data and metadata associated with the database. wlportal$1.wal is a write ahead log file and is used to maintain a record of all transactions against the database. If the system were to crash, this file aids in the recovery of information by performing a rollback to the last consistent state.

You can see examples of the pieces in a domain by viewing the WebLogic Portal examples, especially the Example Portal. The Example Portal domain is in <BEA_HOME>/weblogic700/samples/portal/sampleportalDomain.