Migration Guide

Migrating from Liquid Data 1.0 to 8.1

The basic migration of Liquid Data 1.0 to 8.1 is straightforward. This section provides instructions for such a migration which includes:

• Platform Installation and Configuration
• Liquid Data 8.1 Installation and Deployment
• Liquid Data Migration Steps

 

---

Platform Installation and Configuration

Before installing Liquid Data 8.1, the WebLogic platform and domains you will be using with Liquid Data 8.1 must be installed and configured properly. Specifically:

• WebLogic Server 8.1 is successfully installed in a fresh location (not over an existing WebLogic Server 7.0 SP2 installation).
• The appropriate Liquid Data domain(s) is deployed to the same WL_HOME used by WebLogic Platform 8.1.

Note: If you are using Liquid Data with more than one domain, you must follow these procedures for each domain that you want to migrate to Liquid Data 8.1.

 

---

Liquid Data 8.1 Installation and Deployment

In order to migrate from Liquid Data 1.0 to 8.1 you must create a new Liquid Data installation. In a production environment, that installation must be completed for each WebLogic Server 8.1 domain that you are using with Liquid Data.

Liquid Data 8.1 Installation

Follow the appropriate preparation, installation, and post-installation steps described in the Liquid Data Installation Guide.

Liquid Data 8.1 Deployment

If you are using Liquid Data in a production environment, deploy Liquid Data to the appropriate WebLogic Platform 8.1 domain. Liquid Data 8.1 supports deployment through the WebLogic Domain Wizard.

Through this wizard you can select the appropriate Liquid Data WebLogic deployment such as WebLogic Portal (WLP), WebLogic Integration (WLI), WebLogic Server (WLS), and WebLogic Workshop. For details see Deployment Guide.

 

---

Liquid Data Migration Steps

Perform the following steps in the order presented to migrate your 1.0 Liquid Data repository and any Liquid Data applications you have created to Liquid Data 8.1.

• Step 1: Export Liquid Data 1.0 Data Sources
• Step 2: Copy the 1.0 Liquid Data Repository to 8.1
• Step 3: Re-create JDBC Connections and JDBC Data Sources
• Step 4: Migrate Liquid Data-related Project Files, Applications, Custom Functions, and Web Services Not Generated by Liquid Data
• Step 5: Migrating Existing Liquid Data-generated Web Services
• Step 6: Import Liquid Data 1.0 Data Sources
• Step 7: Migrate 1.0 Stored Queries and Data Views
• Step 8: Test Your Migration Under Liquid Data 8.1

See also What Liquid Data Does Not Import or Export in the Administration Guide.

Example directories

Examples used in this chapter assume that the Liquid Data 1.0 directory is located at:

/opt/prod/bea_70SP2/user_domains/ld_domain

where <bea70SP2> is the location of the WebLogic Server 7.0 SP2 server and <LD_DOMAIN> is the location of the Liquid Data 1.0 domain you want to migrate to Liquid Data 8.1.

These examples also assume that the new Liquid Data 8.1 installation is location at:

/opt/prod/bea_81/user_domains/ld_domain

where <bea_81> is the location of the WebLogic Platform 8.1 server and <LD_DOMAIN> is the location of the new Liquid Data 8.1 installation.

When the discussion relates to the WebLogic Server 7.0 SP2 installation, <WL_HOME_70SP2> is used. Similarly, <WL_HOME_81> represents the WebLogic Server 8.1 installation.

The symbolic name <LD_REPOSITORY> represents the Liquid Data repository and its contents.

Step 1: Export Liquid Data 1.0 Data Sources

This section describes prerequisites and provides specific instructions for migrating Liquid Data 1.0 data sources to Liquid Data 8.1.

Note: Security settings and cache policies are automatically transferred along with data sources.

Prerequisites

Item	Status
WebLogic Server 7.0 SP2 and Liquid Data 1.0	Installed
WebLogic Server 8.1 and Liquid Data 8.1	Installed
Liquid Data 1.0 Server	Running
Liquid Data 8.1 Server	Not running

Actions Required

Perform the following steps to export Liquid Data 1.0 data sources:

Start WebLogic Server 7.0 SP2 and Liquid Data 1.0.
Open the Administration Console.
Export the Liquid Data data sources following the procedure described in the 1.0 Liquid Data Administration Guide:

http://download.oracle.com/docs/cd/E13190_01/liquiddata/docs10/admin/impexp.html#1044952

For example, suppose your Liquid Data 1.0 domain is located at:

/opt/prod/bea_70SP2/user_domains/ld_domain

and the Liquid Data 8.1 domain is located at:

/opt/prod/bea_81/user_domains/ld_domain

then if you export to the filename myDataSource.xml, your file will be create in the following directory:

/opt/prod/bea_70SP2/user_domains/ld_domain/ld_repository/import_export

Step 2: Copy the 1.0 Liquid Data Repository to 8.1

This section describes prerequisites and provides specific instructions for copying the Liquid Data 1.0 repository to Liquid Data 8.1

Prerequisites

Item	Status
Migration Step 1	Completed
Liquid Data 1.0 Server	Not running
Liquid Data 8.1 Server	Not running

Actions Required

Perform the following steps to migrate your Liquid Data repository:

Make sure no instance of the WebLogic Platform or Liquid Data is running.

Copy the Liquid Data 1.0 repository directory structure to the new repository location.

You can use the Administration Console to determine the name and location of your 1.0 Liquid Data repository. For details see Configuring Liquid Data Server Settings in the Administration Guide.

Using the example directory structure you would copy:

/opt/prod/bea_70SP2/user_domains/ld_domain/ld_repository

to the directory:

/opt/prod/bea_81/user_domains/ld_domain

Start the Liquid Data 8.1 server in <WL_HOME_81>.
Open the Administration Console.
Set the Liquid Data repository location to the newly copied repository directory. For details see discussions in the Liquid Data Administration Guide on Configuring Liquid Data Server Settings and Managing the Liquid Data Server Repository.

Step 3: Re-create JDBC Connections and JDBC Data Sources

This section describes prerequisites and provides links to instructions for recreating Liquid Data 1.0 JDBC connections and data sources under Liquid Data 8.1.

Prerequisites

Item	Status
Migration Steps 1 and 2	Completed
Liquid Data 1.0 Server	Not running
Liquid Data 8.1 Server	Running

Actions Required

To migrate your Liquid Data JDBC connectivity to relational databases, first determine the directory location of the 1.0 Liquid Data domain you are migrating from, as follows:

Click the Home icon at the upper-right of the WebLogic Server 7.0 SP2 Administration Console.
Under Domain Configuration, click Domains.
Note the appropriate Liquid Data domain. The config.xml file for a particular domain is in a directory of the same name. For example the <WL_HOME_70SP2> config.xml file would be found in the following directory:

/opt/prod/bea_70SP2/user_domains/ld_domain/config/ld_domain

Inspect config.xml for your JDBC configuration information.
Start WebLogic Server 8.1 and Liquid Data 8.1.
Recreate the JDBC connections and JDBC data sources in the new Liquid Data 8.1 domain.

For detailed information on managing JDBC data sources and connections, see Managing JDBC Connectivity in the WebLogic Server Administration Guide and Migrating Domains Using the Configuration Wizard in the WebLogic Platform Release Notes: 7.0 Service Pack 2.

Step 4: Migrate Liquid Data-related Project Files, Applications, Custom Functions, and Web Services Not Generated by Liquid Data

This section describes prerequisites and provides specific instructions for moving Liquid Data-related project files, applications, custom functions, and web services not generated by Liquid Data from Liquid Data 1.0 to 8.1.

Prerequisites

Item	Status
Migration Steps 1-3	Completed
Liquid Data 1.0 Server	Not running
Liquid Data 8.1 Server	Running

Actions Required

Move and deploy any Liquid Data 1.0-related project files, applications, custom functions, and web services not in the repository.

In Liquid Data 1.0, locate the files you want to move to Liquid Data 8.1
Copy the files to the same relative location in Liquid Data 8.1
For custom functions only, recompile any custom functions under JDK 1.41. For details, see Using Custom Functions.
Use the deployments node of the Liquid Data Administration Console to (re)deploy applications, EJBs, web applications, web services, connectors, and so forth.

For additional information on such migrations see discussions in the Liquid Data Administration Guide on:

• Configuring Access to Web Services
• Configuring Access to Custom Functions
• Configuring Access to Application Views

Step 5: Migrating Existing Liquid Data-generated Web Services

This section describes prerequisites and provides specific instructions for migrating Liquid Data-generated web services from Liquid Data 1.0 to 8.1

Prerequisites

Item	Status
Migration Steps 1-4	Completed
Liquid Data 1.0 Server	Not running
Liquid Data 8.1 Server	Running

Note: The LDWSMigrate script will function properly only if the referenced data sources are properly configured in WebLogic Server 8.1. See Step 3: Re-create JDBC Connections and JDBC Data Sources for details.

Actions Required

Use the LDWSMigrate script to convert Liquid Data 1.0 Liquid Data-generated web services to 8.1-level. The script is installed to the following location:

/opt/prod/bea_81/user_domains/ld_domain/migration/LDWSMigrate

where <LD_DOMAIN> is the root location of your newly installed version of Liquid Data.

Syntax

LDWSMigrate <inputDirectory> [ <outputDirectory> ]

Description

The LDWSMigrate script generates appropriate XML namespace declarations for Liquid Data generated web services during the conversion process.

The LDWSMigrate script requires two parameters.

<inputDirectory>

This parameter specifies the full path to the directory containing the web services ear files generated using Liquid Data 1.0.

In the case of the sample migration described in this document, the 1.0-level Liquid Data-generated Web queries are located in the following directory:

/opt/prod/bea_70SP2/user_domains/ld_domain/ld_repository/web_services_gen

[ <outputDirectory> ]

This parameter specifies the target path for the converted ear files.

In the case of the sample migration described in this document, the 1.0-level web services ear files will be integrated to the following directory:

/opt/prod/bea_81/user_domains/ld_domain/ld_repository/web_services_gen/scratch

If an outputDirectory parameter is not supplied, the converted files with a prefix of new_ are placed in a newly-created directory called scratch under web_services_gen:

/opt/prod/bea_70SP2/user_domains/ld_domain/ld_repository/web_services_gen/scratch

Example

LDWSMigrate c:/opt/prod/bea_70SP2/user_domains/ld_domain/ldrepository/web_services_gen c:/opt/prod/bea_81/user_domains/ld_domain/ldrepository/web_services_gen

The respective domain of each Liquid Data installation is represented by <LD_DOMAIN>.

Step 6: Import Liquid Data 1.0 Data Sources

This section describes prerequisites and provides specific instructions for importing Liquid Data 1.0 data sources into Liquid Data 8.1.

Prerequisites

Item	Status
Migration Steps 1-5	Completed
Liquid Data 1.0 Server	Not running
Liquid Data 8.1 Server	Running

Actions Required

If you have followed instructions in Step 2: Copy the 1.0 Liquid Data Repository to 8.1, your 8.1 data source file myDataSource.xml is available under <WL_HOME_81> in the following location:

/opt/prod/bea_81/user_domains/ld_domain/ld_repository/import_export

To import the Liquid Data data sources follow the procedure described in the Liquid Data 1.0 Administration Guide:

http://download.oracle.com/docs/cd/E13190_01/liquiddata/docs10/admin/impexp.html#1044952

Figure 3-1 Importing a Data Source Through the Administration Console

 

Step 7: Migrate 1.0 Stored Queries and Data Views

This section describes prerequisites and provides specific instructions for migrating Liquid Data 1.0 stored queries and dataviews to Liquid Data 8.1.

Prerequisites

Item	Status
Migration Steps 1-6	Completed
Liquid Data 1.0 Server	Not running
Liquid Data 8.1 Server	Running

Notes:

• The QueryMigrate script will function properly only if the referenced data sources are properly configured in WebLogic Server 8.1. See Step 3: Re-create JDBC Connections and JDBC Data Sources for details.
• Some Liquid Data 1.0 queries cannot be automatically migrated to 8.1 Specifically, if you have queries that are built on top of data views starting with a numeric first character, you first need to:
• Rename and save the referenced data view.
• Resave the query after making sure that it runs correctly.

Actions Required

Convert Liquid Data 1.0 stored queries and data views to 8.1-level using the queryMigrate script. The script is installed to the following location:

/opt/prod/bea_81/user_domains/ld_domain/migration/queryMigrate

where ld_domain is the location of your newly installed Liquid Data 8.1 domain.

Syntax

queryMigrate <admin_url> <inputDirectory> [ <outputDirectory> ]

Description

The queryMigrate script generates appropriate XML namespace declarations for stored queries and data views during the conversion process. For additional information see Understanding XML Namespaces in Building Queries and Dataviews.

The queryMigrate script requires three parameters, described below.

<admin_url>

This parameter specifies the administration URL of the 8.1 Liquid Data Server. For example:

t3://localhost:7001

<inputDirectory>

This parameter specifies the location of stored queries or data views to be converted.

For the sample migration described in this document, the 1.0-level stored queries are in the following directory:

/opt/prod/bea_70SP2/user_domains/ld_domain/ld_repository/stored_queries

and 1.0-level data views are in the following directory:

/opt/prod/bea_70SP2/user_domains/ld_domain/ld_repository/data_views

[ <outputDirectory> ]

This optional parameter specifies the target location of the converted stored queries or data views.

For the sample migration described in this document, the 8.1-level stored queries will be located in the following directory:

/opt/prod/bea_81/user_domains/ld_domain/ld_repository/stored_queries

and the 1.0-level data views will be located in the following directory:

/opt/prod/bea_81/user_domains/ld_domain/ld_repository/data_views

Examples

queryMigrate t3://localhost:7001 c:/opt/prod/bea_70SP2/user_domains/ld_domain/ldrepository/stored_queries c:/opt/prod/bea_81/user_domains/ld_domain/ldrepository/stored_queries

queryMigrate t3://localhost:7001 c:/opt/prod/bea_70SP2/user_domains/ld_domain/ldrepository/data_views c:/opt/prod/bea_81/user_domains/ld_domain/ldrepository/data_views

The respective domain of each Liquid Data installation is represented by ld_domain.

If no output directory is provided, the inputDirectory location is used and the prefix new_ is prepended to the name of the generated file.

Step 8: Test Your Migration Under Liquid Data 8.1

This section describes how to test the migration from Liquid Data 1.0 to Liquid Data 8.1 by verifying hat your 1.0 metadata is available under Liquid Data 8.1.

• Using the Liquid Data node of the WebLogic Administration Console and the Data View Builder, make sure that the appropriate data sources are available to Liquid Data 8.1.
• Test your projects. Liquid Data 1.0 project files can be opened directly with Liquid Data 8.1 and will be converted to support Liquid Data 8.1 automatically when they are saved. If you created project files in the Liquid Data 1.0 directory structure, you may want to move these projects to the Liquid Data 8.1 area, but there in no requirement that you do so.
• Test your stored queries. You can do this using either an EJB API or the Data View Builder.
• EJB API. See Invoking Queries in EJB Clients in the Application Developer's Guide.
• Data View Builder. You can load a stored query using the Data View Builder File -> Open Query command. (You may need to navigate to the directory containing your stored queries.)

Once your query has been loaded, you can run it. See Testing Queries in Building Queries and Data Views.

When you are sure your migration from Liquid Data 1.0 to 8.1 has been successful, you are ready to start using Liquid Data 8.1. It is suggested that you retain your Liquid Data 1.0 installation for a reasonable time and then archive it for safekeeping.