Installation Guide
|
 |
 |
|
 |
 |
This chapter describes tasks you can after installation of an instance of Data Services Platform (DSP), including verifying the installation, starting development of applications, and exploring Windows shortcuts and UNIX paths. The chapter also describes how to uninstall DSP, if required.
The chapter includes the following sections:
Figure 4-1 illustrates the current step in the overall installation process.
Figure 4-1 Post-Installation Step
After you have installed DSP, you can verify that the installation was successful by building the RTLApp sample application and testing a page flow using WebLogic Workshop.
Start—> All Programs—> BEA WebLogic Platform 8.1—> BEA AquaLogic Data Services Platform 2.0.1—> Examples—> RTL Demo—> Launch RTL Demo Sample Server
Note: You can go on to Step 2 while the sample domain server is starting.
RTLApp.work file located in the following directory:<WL_HOME>/samples/liquiddata/RTLApp/RTLApp.work
Right-click RTLApp in the navigation tree, and choose Build Application from the context-sensitive menu. WebLogic Workshop displays the status of the build. Confirm that the build was successful, as indicated by the build status messages.
demoPageFlowController.jpf. It is located in the following folder:RTLSelfService\Pages
Debug—> Start
The appearance of a login page in the Workshop Test Browser, as illustrated in Figure 4-2, indicates that DSP is correctly installed and running.
Figure 4-2 Login Page in the Workshop Test Browser
For an overview of the Retail Sample Application (RTLApp), including a description of data sources, queries, and other application components, see Sample Retail Application Overview.
When installing DSP on a Windows system, the installer program uses the BEA WebLogic Platform home directory (<WL_HOME>) as the parent folder for WebLogic Server and BEA DSP. It then appears in the Start menu as follows:
Start—> Programs—> BEA WebLogic Platform 8.1—> BEA AquaLogic Data Services Platform 2.0
The DSP folder contains the following shortcuts:
|
Starts the RTL Demo server by running the |
|
|
Starts the DSP Other Demo server by running the |
|
|
Launches the PointBase database console. In order to access the console, you need to enter the Samples URL, such as:
You can determine the URL in use through the WebLogic Administration Console. In the Console select Service The default user and password are both For additional information see How Do I: Administer the Default PointBase Database in WebLogic Workshop documentation. |
|
|
Starts the WebLogic Administration Console for the DSP server that is currently running. |
|
|
Launches the DSP online documentation in your default Web browser. The path to Data Services Platform documentation is: |
|
|
Uninstalls Data Services Platform. After a full installation, you may need to manually remove some of the sample files that have been placed in:
|
Developing your own data integration solution consists of a design phase and an implementation phase.
You can remove DSP from your system using an uninstaller application. Once DSP has been removed, you can manually remove any extra files, such as modified samples or other user-created files, that were not removed automatically by the uninstaller.
You should also undeploy any DSP applications before uninstalling DSP from your system. For information about undeploying, see the topic Undeploying Deployed Applications in the WebLogic Server documentation.
Note: The <WL_HOME> directory into which you plan to install a new version of DSP should not contain any files from a previously installed version of DSP.
To uninstall Data Services Platform:
Start—> Programs—> BEA WebLogic Platform 8.1—> BEA AquaLogic Data Services Platform2.0.1—> UninstallBEA AquaLogic Data Services Platform 2.0.1
<WL_HOME>/<LD_HOME>/uninstall/uninstall
Alternatively, run the following command with the "-i CONSOLE" option in cases when you installed using Console mode (as described in Installing Data Services Platform Using Console or Silent Mode)
When the uninstall is complete, you may be notified that some files could not be removed by the automated uninstall. This could be a result of new files that were either generated or user-created after DSP was installed.
For example if you added new target schemas, stored queries, Web services, and so on to the DSP 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.
You can manually delete remaining files by removing the directories specified in Table 4-2.
|
|
|
