bea.com | products | dev2dev | support | askBEA |
|
e-docs > Liquid Data for WebLogic > Installation and Migration > Preparing to Install Liquid Data |
Installation and Migration |
Preparing to Install Liquid Data
Note: If you are upgrading from Liquid Data 1.0 to 1.1, please review Migrating from Liquid Data 1.0 to 1.1 prior to installing Liquid Data 1.1.
Before you install the BEA Liquid Data for WebLogicTM software, make sure your system meets the requirements for it. This section provides information about supported platforms, system hardware and software requirements, how to install all needed software in the proper order, how to get up-to-date product licenses, and an overview of what gets installed.
The following sections are included here:
Supported Platforms and Databases
For the latest information about platform support, see also the Liquid Data Release Notes.
Note: Support for HP UX, IBM AIX, and SuSE Linux for IBM is new in BEA Liquid Data for WebLogic version 1.0.1.
For more information, see Supported Databases and Drivers in the WebLogic Platform documentation. |
|||
---|---|---|---|
Microsoft Windows 2000 Professional Edition with Service Pack 2 or later |
|
|
|
Microsoft Windows 2000 Advanced Server with Service Pack 2 or later |
|
|
|
Microsoft Windows NT (Server) 4.0 with Service Pack 6 or later |
|
|
|
|
|
|
|
|
|
|
|
|
|||
SuSE Linux for IBM zSeries/S3906, 7 Also required: SuSE Linux Enterprise Server 7 for S/390 updated to Kernel 2.4.7 (dated 05/21/02 or later) |
Accessing Information from Enterprise Information Systems or Custom Applications
Liquid Data supports use of several Enterprise Information Systems (EIS) and custom applications as Application View data sources. Liquid Data interoperates with the BEA WebLogic Integration Application Integration (AI) layer through the Liquid Data Application View interface. Liquid Data can retrieve information through commercial application-specific adapters such as SAP, Siebel, PeopleSoft, Oracle Financial and so on which are certified to work with BEA WebLogic Integration.
The Liquid Data server and Data View Builder are internationalized and support multi-byte data from the underlying data sources. For this release, the user interface is in English only; it is ready for translation, but has not yet been translated into other languages.
Liquid data has been tested with Japanese character sets, where the underlying databases are running in Japanese locales. In accordance with the XML specification, target schema element names must be composed of single-byte characters. For any specific internationalization issues, see the Release Notes.
Client systems and Server systems have slightly different installation prerequisites—the main difference being that Server systems require that WebLogic Platform 7.0 SP2 is installed before installing the Liquid Data Server. Client systems where you plan to install only the Data View Builder do not require an installation of WebLogic Platform.
Server Installation Prerequisites
This section lists the prerequisites for installing the Liquid Data server.
You must have WebLogic Platform version 7.0 installed on the system where you plan to install the Liquid Data Server, and have a valid license.
Application Integration for Application Views Data Sources
Liquid Data works with WebLogic Integration to support the use of application views as data sources. If you want to use application views as Liquid Data data sources, you must have completed the following:
WebLogic Integration and the Application Integration console are part of the WebLogic Platform 7.0 SP2.
For complete information on how to use Application Integration—including application views, refer to Application Integration in the BEA WebLogic Integration documentation. A good place to start is Introduction to Using Application Integration.
For convenience, the Liquid Data Administration Guide provides information on the final prerequisite step on how to define application views (see Configuring Access to Application Views). But this information is also in the WebLogic Integration documentation.
Memory, JDK, System Requirements, and Other Prerequisites
The 256-MB RAM recommendation is minimal for one instance of WebLogic Server on which Liquid Data is running. You may need more memory if you run two or more instances of WebLogic Server and/or Liquid Data.
When you install WebLogic Server, JDK 1.3.1 is installed directly under the BEA Home directory in the jdk131 directory, as follows:
where BEA_HOME is the path to your BEA home; that is, where you installed WebLogic Platform. By default, BEA_HOME is c:/bea.
Note: jdk131_06 is automatically installed with BEA WebLogic Platform 7.0 SP2, which is a prerequisite for Liquid Data server installation. So, if you are installing the Liquid Data server you will already have the correct JDK installation as a part of the application. However, if you are installing the Data View Builder client only you do need to ensure that you have an installation of at least JRE 1.3.1 (or JDK 1.3.1 which includes the JRE). Some problems have been reported running Data View Builder with jdk131_02, therefore we recommend using jdk131_03 or higher.
Server Performance Considerations
For information on factors relevant to Liquid Data server performance, see Platform Performance Factors under "Tuning Performance" in Deploying Liquid Data. For larger development projects and for most production environments, it is useful to consider these issues at or before installation time.
Client Installation Prerequisites
Note: Please note that apart from the requirement for the JDK for use by installer (as detailed above), once it is installed the Data View Builder must use the same version of the JDK that the Liquid Data server uses. For the current release, the Liquid Data server uses JDK 1.3.1_06. For example if Liquid Data server is using C:/BEA_HOME/jdk131_06/, then the Data View Builder must use this same Java home.
Note that, unlike the previous JDK/JRE PATH prerequisite, weblogic.jar is not required for the installation itself but will be required after installation to start the Data View Builder client. For details, see For Client-Only Installations Modify Data View Builder Start Script in "Post-Installation Tasks."
Note: You can use Liquid Data in a team development environment with multiple clients accessing a shared Liquid Data server Repository for resources such as schema files, XML files, local WSDL definitions for Web services, and so on. For more information on various deployment and development scenarios and environments, see the Deployment Tasks topic in the Deployment Guide.
Required Order of Installation Tasks
To ensure a valid Liquid Data installation, you must install products and components in the following order:
C:\>path
PATH=C:\bea\jdk131_06\bin;C:\WINNT\system32;C:\WINNT;
About Licensing for Liquid Data
When you install Liquid Data, a valid evaluation license is automatically included with the installation. You do not need to take any extra steps for Liquid Data licensing.
Before you install Liquid Data, you must install the WebLogic Server.
The full install of Liquid Data results in the installation of the following key components on the system:
For more information about the software, refer to the Liquid Data Product Overview.
For information on how to configure Liquid Data once you have installed it, refer to the BEA WebLogic Server Administration Guide.
The full Liquid Data with Samples option provides a preconfigured samples domain as shown in the following table. You can create more domains and add Liquid Data to them.
For a detailed explanation of domains, see the topic Creating and Configuring WebLogic Server Domains in the WebLogic Server documentation.
Note: WL_HOME is the home location of your WebLogic installation, by default, WL_HOME is c:/bea/weblogic700.
Considerations for Adding Liquid Data to a WebLogic Server Domain
For information about adding Liquid Data to a WebLogic Server domain (including preconfigured domains for BEA WebLogic Integration, BEA WebLogic Portal, or WebLogic Workshop), see the Deployment Tasks topic in the Deployment Guide. The information provided in the Deployment Guide about adding Liquid Data to a domain as well as setting up clustered environments is relevant to both deployed systems and development environments.