|
|
The following sections describe how to install WebLogic SIP Server using a graphical user interface:
Before you start installing WebLogic SIP Server, please review the following information:
http://e-docs.bea.com/platform/suppconfigs/index.html.If you are adding components to an existing installation of WebLogic Platform, you should shut down any running servers before starting the installation.
/bea/sipserver31) must be at the same version level. If you attempt to install additional components at a higher version than those that are already installed in that directory, the installation program prompts you to upgrade your existing components before you can proceed with the installation. For details on upgrading your installation, see
Upgrading a WebLogic SIP Server 2.2 Configuration to Version 3.1 in the Configuration Guide.
| Note: | If you are installing WebLogic Platform on a Windows system that supports more than one monitor, you must disable all but one monitor before starting the installation program. |
To start the installation in graphical mode on a Windows system:
wlssXXX_win32.exe (WebLogic Server package installer)
In these filenames, XXX represents the version number of the software you are installing.
The installation program begins to install WebLogic SIP Server.
Proceed to Running the Installation Program.
wlssXXX_win32.exe (package installer)
In this filename, XXX represents the version number of the software you are installing.
The installation program begins to install WebLogic SIP Server.
The WebLogic Platform installation program requires a Java run-time environment (JRE) to run. A JRE is bundled in the Windows installation program, and in some UNIX installation programs (those with filenames ending in .bin). For other UNIX platforms, the WebLogic SIP Server installation program does not include a JRE. Filenames for these installation programs end in .jar. To run the .jar installation programs, you must have an appropriate version of a Java 2 SDK installed on your system, and include the bin directory of the Java 2 SDK at the beginning of your PATH system variable.
| Notes: | It is important that you use an SDK because the installation process sets the JAVA_HOME and related variables to point to this directory. All scripts installed with WebLogic Platform use this SDK by default, including scripts to start sample applications, the Configuration Wizard, and other WebLogic development tools. |
| Note: | To run graphical-mode installation, your console must support a Java-based GUI. If the installation program determines that your system cannot support a Java-based GUI, it automatically starts running in console-mode. For details, see Installing WebLogic SIP Server Using Console-Mode Installation. |
If you have an installation program for UNIX platforms with a filename that ends in .bin, complete the following steps to start the installation in graphical mode:
chmod a+x filename.bin
./filename.bin
Here filename.bin is the name of the WebLogic SIP Server installation program specific to your platform.
| Note: | You can also include the -log=full_path_to_log_file option in the command line to create a verbose installation log. For example: |
| Note: | java -jar pj_platformXXX_generic.jar |
| Note: | For more information, see Generating a Verbose Installation Log. |
The installation program begins to install WebLogic SIP Server.
Here filename.bin is the name of the WebLogic SIP Server installation program specific to your platform, for example platformXXX_solaris.bin, where XXX represents the version number of the software you are installing.
| Note: | You can also include the -log=full_path_to_log_file option in the command line to create a verbose installation log. For example: |
| Note: | java -jar pj_platformXXX_generic.jar |
| Note: | For more information, see Generating a Verbose Installation Log. |
If you have an installation program for UNIX platforms with a filename that ends in .jar, follow these steps to start the installation in graphical mode:
bin directory of the appropriate SDK to the beginning of the PATH variable definition on the target system. For example:
PATH=JAVA_HOME/bin:$PATH
export PATH
Here JAVA_HOME represents the full path to the SDK directory.
Here, filename.jar is the name of the WebLogic SIP Server installation file, for example pj_platformXXX_generic.jar.
The installation program prompts you to enter specific information about your system and configuration. For instructions on responding to the prompts during installation, see the following table.
Specify the BEA Home directory that will serve as the central support directory for all BEA products installed on the target system. If you already have a BEA Home directory on your system, you can select that directory (recommended) or create a new BEA Home directory. If you choose to create a new directory, the WebLogic SIP Server installation program automatically creates the directory for you. For details about the BEA Home directory, see Choosing a BEA Home Directory.
|
|
Specify the directory in which you want to install the WebLogic Platform software and click Next. You can accept the default product directory (
sipserver31) or create a new product directory.
For additional information, see Choosing a Product Installation Directory.
|
|
You can start using the product immediately after installing it for the first time. For additional information, see Configuring a WebLogic SIP Server Domain.
|