e-docs > WebLogic Server > Installation Guide > Performing Post-Installation Tasks |
Installation Guide |
Performing Post-Installation Tasks
The following sections describe the tasks you perform after installing WebLogic Server:
Understanding the WebLogic Server Windows Shortcuts
When you install WebLogic Server on a Windows system, the installation program automatically creates shortcut files on the Start Menu. Options on the Start Menu vary according to options you select during installation. The WebLogic Platform 7.0 folder (Start
Figure 7-1 BEA WebLogic Platform Start Menu
Figure 7-2 shows the options on the WebLogic Server 7.0 menu (Start
Figure 7-2 WebLogic Server 7.0 Start Menu
Understanding the WebLogic Server Directory Structure
WebLogic Server 7.0 has a new directory structure for WebLogic Server and a new location for your applications that run on WebLogic Server. This new directory structure provides added flexibility and promotes best practices for application development.
Files and Directories Installed
During the WebLogic Server installation, you are asked to select or create a BEA Home directory and a product installation directory. For information about the BEA Home directory, see BEA Home Directory. For a typical installation, the installer program creates the following directory structure for WebLogic Platform software, which may or may not be in the BEA Home directory:
The contents of each directory are described in the following table.
Folders for files shared by all WebLogic Platform components, as well as individual folders for each installed WebLogic Platform component. |
|
Files shared by WebLogic Platform components, including template jar files used by the Configuration Wizard when creating domains. The Configuration Wizard reads the contents of this folder and displays template options based on the jar files in the directory. See Configuring Domains, Servers, and Clusters with the Configuration Wizard for more information about using the Configuration Wizard. |
|
Sample code, resources, and preconfigured domains designed to help you learn how to develop your own applications using WebLogic Platform. Samples are organized by component installed on the system. Each WebLogic Platform component has its own folder within the samples folder. The server folder in the samples folder contains the examples and petstore domains, source code for the examples and petstore sample applications, and PointBase evaluation software. |
|
WebLogic Workshop application and documentation files and files to support the Workshop sample domain. |
New Structure for Domain Directories
In previous releases of WebLogic Server, domains were created within the directory structure of the Weblogic Server installation, including application code for each domain. With WebLogic Server 7.0, you can and are encouraged to create domains in their own directory structure anywhere you choose. Scripts and applications in the domain must have access to the Weblogic Server installation and the JDK.
This new directory structure provides for greater flexibility when storing application code and configuring server systems. It also promotes best practices for application development. That is, application code should not be stored with the application server code.
For more information about domains and domain directories, see Overview of WebLogic Server Domains in Creating and Configuring WebLogic Server Domains.
Starting the Examples, Pet Store, and Workshop Examples Servers
The examples optionally installed with WebLogic Server demonstrate a variety of features using WebLogic Server and WebLogic Workshop. The source files and Javadoc files for the WebLogic Server examples are installed in SAMPLES_HOME\server\src\examples and SAMPLES_HOME\server\src\petstore. Additional information for configuring and executing the examples server and the example applications is provided in the SAMPLES_HOME\server\src\examples\examples.html file. The WebLogic Workshop Samples project source files are installed in SAMPLES_HOME\workshop\applications\samples. For information about the Samples project in WebLogic Workshop, see the WebLogic Workshop documentation.
The following sections provide instructions for starting the Examples, Pet Store, and cgServer (for the WebLogic Workshop Samples project) servers on a Windows or UNIX system.
Note: You cannot start the Examples, Pet Store, and Workshop Examples servers at the same time (as installed) because all of them are configured to use port 7001 as the non-secure listening port and 7002 as the secure listening port. To run them concurrently, you must reconfigure the listening ports as described in Setting the Listen Port in the Administration Console Online Help
Starting the Examples Server on a Windows System
To start the Examples server on a Windows system:
After the server starts, a Web browser automatically opens. Click the Go to Administration Console text link or enter the following URL in a browser window to start the Administration Console: http://hostname:7001/console.
For complete information about starting and stopping WebLogic Server, see "Starting and Stopping WebLogic Servers" in the Administration Guide.
Note: You cannot start the Examples, Pet Store, and Workshop Examples servers at the same time (as installed) because all of them are configured to use port 7001 as the non-secure listening port and 7002 as the secure listening port. To run them concurrently, you must reconfigure the listening ports as described in Setting the Listen Port in the Administration Console Online Help
Starting the Examples Server on a UNIX System
To start the examples server on a UNIX system, follow these steps:
SAMPLES_HOME/server/config/examples
startExamplesServer.sh
For complete information about starting and stopping servers, see "Starting and Stopping WebLogic Servers" in the Administration Guide.
Note: You cannot start the Examples, Pet Store, and Workshop Examples servers at the same time (as installed) because all of them are configured to use port 7001 as the non-secure listening port and 7002 as the secure listening port. To run them concurrently, you must reconfigure the listening ports as described in Setting the Listen Port in the Administration Console Online Help
Starting the Pet Store Server and Application on a Windows System
The Pet Store server runs the Pet Store application, which is provided in the WebLogic Server Pet Store Demo to demonstrate the capabilities of the J2EE platform and WebLogic Server. After the server boots, your browser should automatically launch and point to the WebLogic Server Petstore Demo running on the server. Additional information for configuring and executing the Pet Store server and the Pet Store application is provided in the WL_HOME\samples\server\src\petstore\petstore.html file.
To start the Pet Store server on a Windows system:
For complete information about starting and stopping WebLogic Server, see "Starting and Stopping WebLogic Servers" in the Administration Guide.
Note: You cannot start the Examples, Pet Store, and Workshop Examples servers at the same time (as installed) because all of them are configured to use port 7001 as the non-secure listening port and 7002 as the secure listening port. To run them concurrently, you must reconfigure the listening ports as described in Setting the Listen Port in the Administration Console Online Help
Starting the Pet Store Server and Application on a UNIX System
The Pet Store server runs the Pet Store application, which is provided in the WebLogic Server Pet Store Demo to demonstrate the capabilities of the J2EE platform and WebLogic Server. After the server boots, your browser should automatically launch and point to the WebLogic Server Pet Store Demo running on the server. Additional information for configuring and executing the Pet Store server and the Pet Store application is provided in the SAMPLES_HOME/server/src/petStore/petstore.html file.
To start the Pet Store server and application on a UNIX system, follow these steps:
SAMPLES_HOME/server/src/petStore
startPetStore.sh
For complete information about starting and stopping servers, see "Starting and Stopping WebLogic Servers" in the Administration Guide.
Note: You cannot start the Examples, Pet Store, and Workshop Examples servers at the same time (as installed) because all of them are configured to use port 7001 as the non-secure listening port and 7002 as the secure listening port. To run them concurrently, you must reconfigure the listening ports as described in Setting the Listen Port in the Administration Console Online Help
Starting the WebLogic Workshop Examples Server
WebLogic Workshop is installed with a project named Samples. The samples project contains many example web services that demonstrate specific features or capabilities of WebLogic Workshop web services. To support the Samples project, WebLogic Workshop is installed with the Workshop domain preconfigured and ready to run.
To start the Workshop Examples server on a Windows system:
Note: You cannot start the Examples, Pet Store, and Workshop Examples servers at the same time (as installed) because all of them are configured to use port 7001 as the non-secure listening port and 7002 as the secure listening port. To run them concurrently, you must reconfigure the listening ports as described in Setting the Listen Port in the Administration Console Online Help
Starting the Administration Console
The Administration Console is the Web-based administration tool for WebLogic Server. You must start the server before you can access the Administration Console for a server.
Note: For details about starting the WebLogic Server servers, see Starting the Examples, Pet Store, and Workshop Examples Servers. For more information about the Administration Console, see the Administration Guide.
To start the Administration Console, follow these steps:
http://hostname:port/console
Determining the SDK Version You Are Using
You can determine the version of the SDK you are using in either of two ways: on the command line or by examining the contents of the log file created for the server. Instructions for both methods are provided in Table 7-1.
Note: The server log file is created the first time the server is started. |