Administration Guide
This section describes how to start and stop the BEA Liquid Data for WebLogic server. It includes the following sections:
Before you can configure or manage Liquid Data, you must start the Liquid Data server, which runs as an application in a WebLogic domain. Starting the WebLogic Server in the appropriate WebLogic domain automatically starts Liquid Data.
When you run the startWebLogic.cmd
(Windows) or startWebLogic.sh
(UNIX) command for a domain, WebLogic Server is started, and the Liquid Data applications and resources specified in the configuration file for the domain are automatically deployed on the server. The Liquid Data pre-configured domains are shown in Start the Server in the Appropriate WebLogic Domain along with quick summary of Windows menu paths and UNIX command line paths for starting the server.
Note: The instructions that follow are tailored for starting the WebLogic Server in conjunction with Liquid Data. For general information on starting the WebLogic Server, see Starting and Stopping WebLogic Servers in the WebLogic Server documentation.
You must start the Liquid Data server in the appropriate WebLogic domain. A pre-configured domain is provided for the Samples server. To create new Liquid Data servers of your own, you need to use the WebLogic Platform Configuration Wizard. For more information, see Deployment Tasks in the Deployment Guide and Creating Domains Using the Configuration Wizard in the WebLogic Platform documentation.
Note: Make sure you run the First-Time Samples Configuration before running the Samples server for the first time.
Windows and UNIX Paths to Start Samples Server in Each Domain |
|
---|---|
Which server you start depends upon whether you want to use the Samples server which comes with preconfigured data sources, or one of your own servers in a new domain you create with the WebLogic Platform Configuration Wizard.
The instructions in this section describe how to start WebLogic Server in a standalone WebLogic domain. For multi-node or clustered domains, see the instructions in Deployment Tasks in the Deployment Guide.
Note: If you are already running an instance of WebLogic Server that uses the same listen port as the one to be used by the server you are starting, you must stop the first server before starting the second server.
You can stop your entire Liquid Data system—WebLogic Server (WLS), the Liquid Data server, and its resources deployed in a pre-configured domain—from the WLS Administration Console.
The instructions in this section describe how to stop WebLogic Server in a standalone WebLogic domain. For multi-node or clustered domains, see the instructions in Deployment Tasks in the Deployment Guide.
Note: We recommend using the Administration Console to shut down the server gracefully rather than shutting down from a DOS window or UNIX shell.
To stop the WLS server using the Administration Console:
http://
HostName
:Port
/console
For example, to start the Administration Console for a local instance of WebLogic Server (running on your own machine), type the following URL in a Web browser address field:
http://localhost:7001/console/
Note: For complete details on how to start the Administration Console see Starting the Administration Console in Starting and Stopping the Server.
Note: On Unix, you must also manually kill the running Pointbase instance.
Once you have the server started, you need to start the WLS Administration Console. You can use the WLS Administration Console to perform all Liquid Data configuration, management, and monitoring tasks. For information on how to start the console and find the Liquid Data node on the console, see Using the WLS Administration Console.