Skip navigation.
Downloads | Product Documentation | Support

Deployment Guide

# Introduction

Deployment is the process of setting up BEA Liquid Data for WebLogic in a production environment. This topic introduces Liquid Data deployment. It contains the following sections:

- Liquid Data Deployment Considerations
- WebLogic Platform Configuration Wizard
- Resources to Deploy
- Resources to Configure

# Liquid Data Deployment Considerations

While Liquid Data can be adequately evaluated on a single-server system, a multiple server configuration is generally considered appropriate for a production environment.

In Planning a Liquid Data Deployment, you will find suggested Liquid Data deployment designs with cross-references to WebLogic Server deployment documentation.

When Liquid Data is used for significant numbers of queries or significantly large and resource-intensive queries, you should deploy Liquid Data into its own domain or domains. This will provide the best opportunities to analyze and tune the system. Similarly, when your needs grow, it will be easier to identify those needs if Liquid Data is established with its own set of servers.

On the other hand, when Liquid Data is playing a supportive role for another application (such as WebLogic Integration or WebLogic Workshop) it can be deployed either in a new or an existing WebLogic 8.1 domain.

Initially, you may want to install Liquid Data as a single server system or a two-node cluster (if rollover is a high priority). In this way it will not be difficult to tell if a simple configuration is adequate or if additional nodes are needed.

# WebLogic Platform Configuration Wizard

You should use the WebLogic Platform 8.1 Configuration Wizard to create and configure domains with or without Liquid Data.

Figure 1-1 Domain Configuration Wizard

## Creating New Liquid Data-enabled WebLogic Domains

After you install Liquid Data, the following deployment templates for creating a new domain become available from the Configuration Wizard:

- Basic Liquid Data and WebLogic Platform Domain
- Basic Liquid Data and WebLogic Integration Domain
- Basic Liquid Data and WebLogic Portal Domain
- Basic Liquid Data and WebLogic Server Domain

Figure 1-2 Liquid Data Templates Available in the Configuration Wizard

The Configuration Wizard provides both an Express and Custom configuration options. If you choose Custom, you can tailor your deployment for such items as:

- distribution across servers, clusters, and physical machines
- jdbc components such as connection pools, multipools, and data sources
- jms components such as stores, topics and queues
- modifying or specifying application, JDBC, and JMS component deployment servers and clusters

## Extending an Existing WebLogic Domain for Liquid Data

You can also extend any existing WebLogic Platform 8.1 domain to support Liquid Data.

For example, to create a Liquid Data + WebLogic Workshop domain you would use the Configuration Wizard to:

1. Create and configure a WebLogic Workshop domain (if you do not already have on).
2. Restart the Configuration Wizard, selecting the Extend an Existing WebLogic Configuration option
3. Check the Liquid Data Extension (samples included) checkbox.
4. Click Configure to extend the WebLogic Workshop domain to include Liquid Data.

Figure 1-3 Dialog Box for Extending a WebLogic Domain for Liquid Data

If the "samples included" option is chosen, the Liquid Data samples are installed to the selected domain.

Note: When extending a domain using the Configuration Wizard, it is highly recommended that you extend a domain one product at a time. If additional extension are needed, rerun the Configuration Wizard.

Minor script editing is needed to complete a deployment.

# Overview of Deployment Steps

The process of deploying Liquid Data involves the following basic steps:

1. Make sure that WebLogic Platform and Liquid Data are installed.
2. Determine whether to deploy to a new or an existing domain.
3. If you are deploying Liquid Data to a new domain review Defining Deployment Requirements and Designing Deployments. Such a review can help ensure that your deployment architecture best suits your long-term business requirements.
4. Install WebLogic Server and Liquid Data according to the instructions in Installing Liquid Data.
5. Using the WebLogic Platform Configuration Wizard create or extend the appropriate WebLogic Platform domains with Liquid Data, as described in Deployment Tasks.
6. Properly set up security for your newly created or extended domain. See Security in Liquid Data in the Administration Guide for detailed information and further references.
7. Start the servers in the deployment domain(s) according to the instructions in Starting and Stopping the Server in the Liquid Data Administration Guide.
8. Start the WebLogic Administration Console and configure the resources described in Resources to Configure as applicable to your deployment.
9. Monitor the ongoing operation of the Liquid Data server according to the instructions in Monitoring the Server in the Liquid Data Administration Guide.
10. Tune performance on the Liquid Data server, as necessary, according to the instructions in Tuning Liquid Data Performance.

These steps provide only a summary of the steps required to deploy Liquid Data in a production environment.

Note: If your domain will include applications that use the Liquid Data Control, you need to update the ldcontrol.properties file. For details, see "Moving Your Liquid Data Control Applications to Production" in the Application Developer's Guide.

>     http://download.oracle.com/docs/cd/E13190_01/liquiddata/docs81/program/ld_control.html#deployControl

## Deployment References in WebLogic Platform Documentation

In addition to this document, BEA WebLogic Platform documentation provides a comprehensive deployment page at the following URL: http://download.oracle.com/docs/cd/E13196_01/platform/docs81/confgwiz/index.html

# Resources to Deploy

The following table summarizes the primary resources involved in a Liquid Data deployment:

Table 1-4 Resources to Deploy in a Liquid Data Deployment

Resource | Description
--- | ---
WebLogic Platform | The complete WebLogic Platform includes the following components: WebLogic Server WebLogic Workshop WebLogic Integration WebLogic Portal Note: At a minimum, the WebLogic Server must be deployed. Other components are deployed as needed.
Liquid Data software | Liquid Data is deployed in an enterprise archive (`LDS.ear`) file format on a single WebLogic Server instance or, in a clustered deployment, across all servers in the cluster.
Data sources | Data sources used in Liquid Data queries must be accessible to the Liquid Data server.

# Resources to Configure

Through the Configuration Wizard, you can configure the following resources as applicable for your deployment:

Table 1-5 Liquid Data Resources to Configure

Resource | Description
--- | ---
Liquid Data server settings and server repository | You need to configure server settings on the General tab in the Liquid Data node of the WebLogic Administration Console, especially the Liquid Data repository location. If you are creating a production implementation from a test deployment, you will probably want to use the Liquid Data Import/Export options to recreate your data source descriptions to new server locations. For instructions, see Configuring Liquid Data Server Settings and Managing the Liquid Data Server Repository in the Liquid Data Administration Guide.
Data source descriptions | For each data source accessed in a Liquid Data query, you need to add a data source description using the Data Sources tab in the Liquid Data node of the WebLogic Administration Console. Additional configuration tasks are required for certain data source types. For instructions, see the following topics in the Liquid Data Administration Guide: Configuring Access to Relational Databases Configuring Access to XML Files Configuring Access to Web Services Configuring Access to Application Views Configuring Access to Data ViewsConfiguring Access to Custom Functions Configuring Access to Delimited Files
Results caching | If you want to cache results for stored queries in this deployment, you must explicitly enable results caching on the General tab in the Liquid Data node of the WebLogic Administration Console. In addition, for each stored query that you want cached, you need to explicitly configure the caching policy. For instructions, see Configuring the Query Results Cache in the Liquid Data Administration Guide.
Custom functions | If custom functions are used in this deployment, you need to create a custom function description for each custom function and add certain files to the server repository. For instructions, see Configuring Access to Custom Functions in the Liquid Data Administration Guide.

Note: You can copy a Liquid Data repository and configuration information from another, fully configured Liquid Data server according to the instructions in Copying a Liquid Data Configuration From Server to Server.