| Download Docs | Site Map | Glossary | |
|
|
|||
| bea.com | products | dev2dev | support | askBEA |
|
|
|
|||||||
 |
| e-docs > Liquid Data for WebLogic > Installation and Migration > Post-Installation Tasks |
|
Installation and Migration
|
After you install BEA Liquid Data for WebLogicTM, we suggest that you do the following:
For convenience, this topic also describes Liquid Data Windows Shortcuts and UNIX Paths. Finally, if you need to uninstall Liquid Data for any reason, follow the instructions in Uninstalling Liquid Data.
Verify the Installation by Running the Samples and Starting Data View Builder
After you install Liquid Data, you can verify that your installation was successful by populating the Samples database and starting the Sample server. We suggest that you also take the time to bring up the Data View Builder and connect to the running Samples server. These sections walk you through both tasks:
To set up and run the Samples do the following:
WL_HOME/liquiddata/samples/config/ld_samples/command/
WL_HOME/liquiddata/samples/config/ld_samples
http://localhost:7001/ldsample/index.htm
We suggest that you take some time to tour the Samples a bit and try running the Sample queries. You can learn more about the Samples and associated Quick Start Steps in the Samples documentation.
Start Data View Builder and Connect to the Samples Server
Once you have the Samples server running, be sure to test the Data View Builder client connection by bringing up the Data View Builder and connecting to the running Samples server. In this way, you can make sure the data sources and views used in the Samples are showing up in the Builder client. This also gives you a chance to tinker with the Data View Builder and get familiar with how it works together with the Liquid Data server.
Note: If you have a client-only installation of the Data View Builder you will need to modify the Data View Builder start script to point to weblogic.jar before you can start the Builder. For instructions on how to do this, see For Client-Only Installations Modify Data View Builder Start Script.
To start the Data View Builder and connect to the Samples server, do the following:
t3://localhost:7001
The Data View Builder desktop and tools are displayed. Relational Databases (RDBMS) is selected on the left navigation panel. Three RDBMS data sources are shown: PB-BB, PB-CR, PB-WL. These are the PointBase RDBMS data sources used by the Samples. You can double-click on each of these data sources in the left panel to display their source XML schemas in the Data View Builder workspace.
For Client-Only Installations Modify Data View Builder Start Script
Data View Builder startup requires the following:
In a Liquid Data "Client-Only" installation that includes only Data View Builder, the user must specify these settings manually. (Whereas for install set options that include the Liquid Data server, these are taken care of automatically at install time.)
To configure a Client-Only system for Data View Builder startup, do the following after install.
Ensure that weblogic.jar is Available on Client System
If you have not already done so, copy WebLogic Server 7.0 weblogic.jar file onto the system where you installed Data View Builder or make a remote instance of this file available to your local machine by mapping a drive to its location and path.
Modify Data View Builder Start Script for weblogic.jar
To modify the start script as needed, do the following:
The following code listing (Listing 4-1) shows the "User Configuration" section of the Data View Builder start script. (The lines you need to modify are shown in bold.).
Modify the setting for the CLASSPATH variable so that it points to the local instance of weblogic.jar. (The default value provided for CLASSPATH will not work for your Client-Only install because WLS_HOME probably does not exist.)
Listing 4-1 Data View Builder Start Script: User Configuration Section
: ---------------------------------------------------------------------------
: User configuration
: ---------------------------------------------------------------------------
: JAVA runtime environment
: If the default configuration does not work on your system set the local
: variable JAVA to point to the location of the Java interpreter (java.exe)
: Example:
: set JAVA=c:\jdk1.3\bin\java
: JAVA classpath
: Use the local variable CLASSPATH to add custom entries (e.g. JDBC drivers) to
: the classpath. Separate multiple paths with ";". Adding additional files
: or locations on separate lines makes things clearer.
:
: Example:
:
: Set the CLASSPATH to a jar file and a directory. Note that
: "classes dir" is a directory of class files with a space in the name.
:
: SET CLASSPATH=C:\Product1\lib\product.jar
: SET CLASSPATH=%CLASSPATH%;C:\MyProject\classes dir
: set WLS_HOME=C:\bea\weblogic700 //remove or comment out this line
set CLASSPATH=C:\weblogic.jar //edit this line to point to the correct version of
//weblogic.jar
: JVM parameters
: If you want to modify the default parameters (e.g. maximum heap size -Xmx)
: for the Java virtual machine set the local variable JVM_PARAMETERS below
: Example:
: SET JVM_PARAMETERS=-Xms100M -Xmx200M
: ---------------------------------------------------------------------------
: Default configuration. Do not modify below this line.
: ---------------------------------------------------------------------------
You are now ready to start the Data View Builder on the Client-Only system. (See Start Data View Builder and Connect to the Samples Server.) Remember that you must have the Liquid Data server running before you start the Data View Builder.
Verify Client is Using Same Version of JDK as Server
Please note that apart from the requirement for the JDK for use by installer (as detailed in Client Installation Prerequisites), 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. An entry for the JDK or JRE 1.3.1 bin directory (for example BEA_HOME/jdk131_06/bin) must be included in your PATH environment variable setting before any other JDK bin directories.
You can also set the a local JDK home for the Data View Builder in the Data View Builder start script (see Listing 4-1) by uncommenting the line set JAVA=c:\jdk1.3\bin\java and setting it to the appropriate JDK Home; however, this should not be necessary if the right JDK Home is in your PATH.
Work Through the Quick Start Steps
Work through the Samples and Getting Started steps which show you how to do the following basic tasks:
Start Developing Your Own Data Integration Solution
Developing your own data integration solution consists of a design phase and an implementation phase. If you want help stepping through the end-to-end process, including design of a business solution, configuration, query construction, JSP presentation, deployment, and using Liquid Data with other BEA products, refer to the Liquid Data Product Overview for an in-depth look at the data integration process and features.
Liquid Data Windows Shortcuts and UNIX Paths
When installing Liquid Data on a Windows system, the installer program uses BEA WebLogic Platform as the parent folder for WebLogic Server and BEA Liquid Data. However, on the Start menu BEA Liquid Data shows up under "Programs" as follows:
Start—>Programs—>BEA WebLogic Platform 7.0—>Liquid Data for WebLogic 1.0
The Liquid Data folder contains the following shortcut files:
http://localhost:7001/ldsample/index.htm
Provides information about how to run the Avitek Sample queries and where to find more query examples with readme files.
Removing Liquid Data requires you to run the Liquid Data uninstaller and then manually remove the Liquid Data directory containing the extra files not removed by the uninstaller. In cases where you have added Liquid Data to another domain, when you uninstall you must also undeploy before you uninstall. For information on undeploying, see the topic Undeploying Deployed Applications in the WebLogic Server documentation.
For a successful installation of Liquid Data, the WL_HOME directory into which you install a new version of Liquid Data must not contain any files from a previously installed version. Extra files or folders left in place from an old install can cause a defective installation of a new version of Liquid Data.
WL_HOME\liquiddata\uninstaller\uninstall.cmd
WL_HOME/liquiddata/uninstaller/uninstall
(Use this uninstall option if you installed via GUI mode as described in Installing Liquid Data Using GUI Mode.)
WL_HOME/liquiddata/uninstaller/uninstall -i CONSOLE
(Use this uninstall option with "-i CONSOLE" if you installed via Console mode as described in Installing Liquid Data Using Console or Silent Mode.)
Note: When the uninstall is completed it will notify you that there are some files that could not be removed by the automated uninstall. This could be a result of new files that were generated or user-created after Liquid Data was installed. For example if you added new target schemas, stored queries, Web services, and so on to the Repository, the uninstaller will not remove these files. If you need these files, be sure to save them elsewhere before proceeding to the next step.
|
|
|
|
||
 |
|
|
 |
 |
 |
|
||
