| Oracle® Communications Services Gatekeeper Installation Guide Release 5.1 E37539-02 |
|
|
PDF · Mobi · ePub |
| Oracle® Communications Services Gatekeeper Installation Guide Release 5.1 E37539-02 |
|
|
PDF · Mobi · ePub |
This chapter describes how to use the Oracle Communications Services Gatekeeper installers. You must perform the installation on every server in the system.
You can install Services Gatekeeper using the following platform-specific installers for the specified 32-bit platforms:
ocsg510_linux.bin
ocsg510_solaris_sparc.bin
ocsg510_win.exe
These installers bundle the JRockit SDK and Sun JDK for Linux and Windows and the Sun JDK for Solaris.
A generic installer is provided, primarily for 64-bit platforms. There is also a version of the generic installer for 32-bit platforms. Unlike the platform-specific installers listed above, the generic installer does not include a bundled JDK. The JDK must already be installed when you use the generic installer.
The generic installer is contained in:
ocsg510_generic.jar
You can run all the installers in GUI, console, or silent mode.
Silent mode is for creating duplicate installations on multiple machines without responding to prompts.
To create an installation log, add the following option to any of the commands that invoke the installer:
-log=logfilename
where logfilename is a name that you assign to the log file.
For example, the following command runs the console Linux32 Services Gatekeeper installer and creates a log file named install_log containing the installation's output.
ocsg510_linux.bin -mode=console -log=install_log
This section contains instructions for using the GUI-based installer to install Services Gatekeeper.
If you want to use the GUI-based installer, the console attached to the machine on which you are installing the software must support a Java-based GUI. All consoles for Windows systems support Java-based GUIs, but not all consoles for UNIX/Linux systems do. If you attempt to start the installation program in GUI mode on a system that cannot support a graphical display, the installation program automatically starts console-mode installation.
GUI mode is the default mode, so it is not necessary to specify the mode on the command line to install in this mode.
The Windows version of Services Gatekeeper is supported only for development and test environments. It is not supported for production.
To run the GUI-based Windows installer:
Log in to the Windows system.
If you are going to use this machine as an Administration Server and you wish to install the Node Manager as a Windows service, you must log in as an administrator. Node Manager is used to monitor, start, and stop server instances in a domain.
Change to the directory where you have copied the installation program.
You acquire this program from the Oracle Software Delivery Cloud.
To start the Windows installer, double-click ocsg510_win.exe or enter the following in a command window:
ocsg510_win.exe [-log=logfilename]
After the installer, starts, the Welcome window appears.
You can cancel the installation at any time by clicking Exit.
In the Welcome window, click Next to proceed with the installation.
The Choose Middleware Home Directory window appears.
The Middleware Home directory is the central support directory for all Oracle middleware products installed on the target system.
Do one of the following:
To install into an existing Middleware home:
Select Use an existing Middleware Home.
From the list of existing Middleware home directories, select a directory.
Caution:
Make sure that the Middleware home installation you select is running WebLogic Server version 10.3.6.Click Next.
The Choose Products and Components window appears.
To create a new Middleware home:
Select Create a new Middleware Home.
In the Middleware Home Directory field, enter the path for the new Middleware home directory.
Click Next.
The Choose Products and Components window appears.
In the Choose Products and Components window, clear the checkbox for any component you do not wish to install.
Note that you cannot install the Platform Development Studio without WebLogic Server and Services Gatekeeper.
Click Next.
The JDK Selection window appears.
In the JDK Selection window, do one of the following:
To install a bundled JDK:
Select the check box next to the bundled JDK that you want Services Gatekeeper to use.
Click Next.
To use a local JDK already installed on the system:
Click Browse.
Navigate to the home directory of your local JDK.
Select the local JDK directory.
The selected directory appears checked in the Local JDK field.
Click Next.
If you are including the Platform Development Studio in the installation, the Platform Development Studio Eclipse Plugin Path window appears.
In the Eclipse Plug-ins Directory field, enter the full path to the directory of your Eclipse installation plugins directory or use the Browse button to locate the directory.
Click Next.
The Choose Product Installation Directories window appears.
In the Product Installation Directories fields, enter the directories in which you want to install the Services Gatekeeper and WebLogic Server software.
Click Next.
If you are installing on Windows, the Install Windows Service window appears.
In the Install Windows Service window, do one of the following:
To install the Node Manager as a Windows Service:
Choose Yes.
In the Node Manager Listen Port field, enter a Node Manager listen port.
To skip installing the Node Manager as a Windows Service, choose No.
The Node Manager Service allows you to stop and start Managed Servers remotely. On Windows, the Node Manager can be installed as a Windows Service.
Click Next.
If you are installing on Windows, the Choose Shortcut Location window appears.
This window lets you specify the Start menu folder for the Services Gatekeeper Start menu shortcuts.
Do one of the following:
To provide all Windows system users with access to the installed software, choose All Users Start Menu folder.
Only users with Administrator privileges can create shortcuts in the All Users folder. Therefore, if a user without Administrator privileges uses the Configuration Wizard to create domains, Start menu shortcuts to the domains are not created. In this case, users can manually create shortcuts in their local Start menu folders, if desired.
To ensure that other users registered on this machine will not have access to the Start menu entries for this installation, choose Local user's Start Menu folder.
Click Next.
The Installation Summary window appears.
Make sure that the Installation Summary reflects all the products and JDKs that you have chosen to install.
If the list is not correct, you can use the Previous button to navigate back so you can make corrections.
Click Next to start the installation.
A progress bar indicates the status of the installation process.
When the Installation Complete window appears, do one of the following:
On Windows, you have the option of running QuickStart now to configure domains. If you want to do this:
Check the Run Quickstart checkbox.
The installer exits.
The QuickStart menu appears.
Choose an action from the QuickStart menu. For information on configuring domains, see "Configuring the Domain for Oracle Communications Services Gatekeeper"
If do not want to run QuickStart now:
Clear the Run Quickstart checkbox.
Click Done.
The installer exits.
To use the GUI-based platform-specific UNIX/Linux installer:
Access the UNIX system with a shell connection.
Change to the directory where you have copied the installation program.
You acquire this program either from the Oracle Software Delivery Cloud.
Change the mode of the installation program file to executable if it is not already set.
To start the UNIX installer, do one of the following:
To start the Linux32 installer, enter:
ocsg510_linux.bin [-log=logfilename]
To start the Solaris_Sparc32 installer, enter:
ocsg510_solaris_sparc.bin [-log=logfilename]
After the installer, starts, the Welcome window appears.
You can cancel the installation at any time by clicking Exit.
In the Welcome window, click Next to proceed with the installation.
The Choose Middleware Home Directory window appears.
The Middleware Home directory is the central support directory for all Oracle middleware products installed on the target system.
Do one of the following:
To install into an existing Middleware home:
Select Use an existing Middleware Home.
From the list of existing Middleware home directories, select a directory.
Caution:
Make sure that the Middleware home installation you select is running WebLogic Server version 10.3.6.Click Next.
The Choose Products and Components window appears.
To create a new Middleware home:
Select Create a new Middleware Home.
In the Middleware Home Directory field, enter the path for the new Middleware home directory.
Click Next.
The Choose Products and Components window appears.
In the Choose Products and Components window, clear the checkbox for any component you do not wish to install.
Note that you cannot install the Platform Development Studio without WebLogic Server and Oracle Communications Services Gatekeeper.
Click Next.
The JDK Selection window appears.
In the JDK Selection window, do one of the following:
To install a bundled JDK:
Select the check box next to the bundled JDK that you want Services Gatekeeper to use.
Click Next.
To use an existing JDK already installed on the system:
Click Browse.
Navigate to the home directory of your local JDK.
Select the local JDK directory.
The selected directory appears checked in the Local JDK field.
Click Next.
If you are including the Platform Development Studio in the installation, the Platform Development Studio Eclipse Plugin Path window appears.
In the Eclipse Plug-ins Directory field, enter the full path to the plugins directory of your Eclipse installation or use the Browse button to locate the directory.
Click Next.
The Choose Product Installation Directories window appears.
In the Product Installation Directories fields, enter the directories in which you want to install the Services Gatekeeper and WebLogic Server software.
Click Next.
The Installation Summary window appears.
Make sure that the Installation Summary reflects all the products and JDKs that you have chosen to install.
If the list is not correct, you can use the Previous button to navigate back so you can make corrections.
Click Next to start the installation.
A progress bar indicates the status of the installation process.
When the Installation Complete window appears, click Done.
The installer exits.
To run the generic GUI-based installer:
Log into the target system.
If you are installing on a 64-bit system, ensure that a 64-bit JDK, or a hybrid 32/64-bit JDK, is installed on the target machine.
If it is not installed, install one. See "Supported Configurations" for information about supported JDK versions.
Run the java -version command, or java -d64 -version command on platforms using a 32/64-bit hybrid JDK to ensure that the JAVA_HOME variable is set to a 64- bit JDK.
If the JAVA_HOME environment variable is not correctly set, set it to point to the correct JDK.
Add the bin directory of the appropriate JDK (which you have installed separately) 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 JDK directory.
Change to the directory where you downloaded the installation program.
To start the generic installer, do one of the following:
To start the generic installer on a system that uses a 32/64-bit hybrid JDK, such as the HP-PA, HPIA, and Solaris64 platforms, enter:
java -d64 -jar ocsg510_generic.jar [-log=logfilename]
To start the generic installer on a system that uses the Solaris_SPARC 64-bit JDK, enter:
java -d64 -Xms256m –Xmx2048m -XX:PermSize=512m -XX:MaxNewSize=256m -jar ocsg510_generic.jar [-log=logfilename]
To start the generic installer on a 32-bit system, enter:
java -jar ocsg510_generic.jar [-log=logfilename]
After the installer, starts, the Welcome window appears.
Note:
You can cancel the installation at any time by clicking Exit.In the Welcome window, click Next to proceed with the installation.
The Choose Middleware Home Directory window appears.
The Middleware Home directory is the central support directory for all Oracle middleware products installed on the target system.
Do one of the following:
To install into an existing Middleware home:
Select Use an existing Middleware Home.
From the list of existing Middleware home directories, select a directory.
Caution:
Make sure that the Middleware home installation you select is running WebLogic Server version 10.3.6.Click Next.
The Choose Products and Components window appears.
To create a new Middleware home:
Select Create a new Middleware Home.
In the Middleware Home Directory field, enter the path for the new Middleware home directory.
Click Next.
The Choose Products and Components window appears.
In the Choose Products and Components window, clear the checkbox for any component you do not wish to install.
Note that you cannot install the Platform Development Studio without WebLogic Server and Services Gatekeeper.
Click Next.
The JDK Selection window appears.
In the JDK Selection window, click Browse to navigate to a local JDK that is already installed on your system.
Select the local JDK directory.
The selected directory appears checked in the Local JDK field.
Click Next.
If you are including the Platform Development Studio in the installation, the Platform Development Studio Eclipse Plugin Path window appears.
In the Eclipse Plug-ins Directory field, enter the full path to the plugins directory of your Eclipse installation or use the Browse button to locate the directory. The Eclipse directory must be created prior to the installation of Service Gatekeeper.
Click Next.
The Choose Product Installation Directories window appears.
In the Product Installation Directories fields, enter the directories in which you want to install the Services Gatekeeper and WebLogic Server software.
Click Next.
The Installation Summary window appears.
Make sure that the Installation Summary reflects all the products that you have chosen to install.
If the list is not correct, you can use the Previous button to navigate back so you can make corrections.
Click Next to start the installation.
A progress bar indicates the status of the installation process.
When the Installation Complete window appears, click Done.
The installer exits.
After installation is complete, set the WL_HOME environment variable to the product installation directory you indicated for WebLogic Server in step 16.
Export WL_HOME. For example:
export WL_HOME=your_installation_directory/wlserver_10.3
cd $WL_HOME/server/native/hpux11/IPF32/
This section contains instructions for using the console installer to install Services Gatekeeper.
To run the console-based Windows installer:
Log in to the target Windows system.
Change to the directory where you have copied the installation program. You acquire this program from the Oracle Software Delivery Cloud.
To start the Windows installer in console mode, enter:
ocsg510_win.exe -mode=console [-log=logfilename]
The Welcome screen appears in the console.
Enter Next to continue with the installation.
In the Middleware Home Directory screen any existing Middleware home directories are displayed. Do one of the following:
To use an existing Middleware Home directory:
Enter the number associated with the directory in the console display.
Caution:
Make sure that the Middleware home installation you select is running WebLogic Server version 10.3.6.Press Enter.
To create a new Middleware Home directory:
Enter 1.
Press Enter.
Enter the full path of the new MIddleware Home directory or Next to accept the default.
When prompted to confirm your choice, press Enter to confirm or Previous to change your selection.
In the Release screen, specify the components that you wish to install:
To remove components from the planned installation, enter the number in brackets following any components that you do not wish to install.
The screen refreshes, and the check mark next to that component is removed.
Note that you cannot install the Platform Development Studio without WebLogic Server and Services Gatekeeper.
Enter Next to continue.
In the JDK Selection screen do one of the following:
Select the number of the JDK you wish to install.
Enter 1 to add the path to an existing local JDK on your system.
Enter Next to continue.
If you are including the Platform Development Studio in the installation, the Platform Development Studio Eclipse Plugin Path screen appears.
In the Platform Development Studio Eclipse Plugin Path screen, enter 1.
Enter the full path of the Eclipse plugins directory.
The screen refreshes, and the path is displayed.
Enter Next to continue.
In the Choose Product Directories screen, specify the directories in which you want to install the Services Gatekeeper and WebLogic software. Do one of the following:
To accept the default product directories, enter Next.
To create one or more new product directories:
Enter the product index number to specify the product to be installed in the directory.
Enter the full path to the directory you are creating.
Enter Next.
When prompted, confirm your choice.
Enter Next.
In the Install Node Manager as a Windows Service screen, do one of the following:
To install the Node Manager as a Windows Service:
Enter Yes.
Enter a Node Manager listen port at the prompt.
To skip installing the Node Manager as a Windows Service, enter No.
The Windows installer displays the Choose Shortcut Location screen if you have Administrator privileges and are performing an initial Services Gatekeeper installation. This screen is used to specify the Start menu folder for the Services Gatekeeper Start menu shortcuts.
Do one of the following:
Enter 1 to select the All Users Start menu folder.
Only users with Administrator privileges can create shortcuts in the All Users folder. Therefore, if a user without Administrator privileges uses the Configuration Wizard to create domains, Start menu shortcuts to the domains are not created. In this case, users can manually create shortcuts in their local Start menu folders, if desired
Enter 2 to select the Local user's Start menu folder.
This option ensures that other users registered on this machine will not have access to the Start menu entries for this installation.
When prompted, confirm your choice.
Enter Next to continue.
In the Installation Summary window, make sure the list reflects all the products and JDKs you have chosen to install.
Enter Next to begin the installation.
When the installation is complete, press Enter to exit the installer.
To run the platform-specific console-based UNIX/Linux installer:
Log into the target system.
Change to the directory where you have copied the installation program.
You acquire this program either from the Oracle Software Delivery Cloud.
To start the installer in console mode, do one of the following:
To start the Linux32 installer, enter:
ocsg510_linux.bin -mode=console [-log=logfilename]
To start the Solaris_Sparc32 installer, enter:
ocsg510_solaris_sparc.bin -mode=console [-log=logfilename]
The Welcome screen appears in the console.
Enter Next to continue with the installation.
In the Middleware Home Directory screen, if you have any existing Middleware home directories they are displayed. Do one of the following:
To use an existing Middleware Home directory:
Enter the number associated with the directory in the console display.
Caution:
Make sure that the Middleware home installation you select is running WebLogic Server version 10.3.6.Press Enter.
To create a new Middleware Home directory:
Enter 1.
Press Enter.
Enter the full path of the new MIddleware Home directory or Next to accept the default.
When prompted to confirm your choice, press Enter to confirm or Previous to change your selection.
In the Release screen, specify the components that you wish to install:
To remove components from the planned installation, enter the number in brackets following any components that you do not wish to install.
The screen refreshes, and the check mark next to that component is removed.
Note that you cannot install the Platform Development Studio without WebLogic Server and Services Gatekeeper.
Enter Next to continue.
In the JDK Selection screen do one of the following:
Select the number of the JDK you wish to install.
Enter 1 to add the path an existing local JDK on your system.
Enter Next to continue.
If you are including the Platform Development Studio in the installation, the Platform Development Studio Eclipse Plugin Path screen appears.
In the Platform Development Studio Eclipse Plugin Path screen, enter 1.
Enter the full path of the Eclipse plugins directory.
The screen refreshes, and the path is displayed.
Enter Next to continue.
In the Choose Product Directories screen, specify the directories in which you want to install the Services Gatekeeper and WebLogic software. Do one of the following:
To accept the default product directories, enter Next.
To create one or more new product directories:
Enter the product index number to specify the product to be installed in the directory.
Enter the full path to the directory you are creating.
Enter Next.
When prompted, confirm your choice.
Enter Next.
In the Installation Summary window, make sure the list reflects all the products and JDKs you have chosen to install.
Enter Next to begin the installation.
When the installation is complete, press Enter to exit the installer.
To run the generic console installer:
Log into the target system.
If you are installing on a 64-bit system, ensure that a 64-bit JDK, or a hybrid 32/64-bit hybrid JDK, is installed on the target machine.
If it is not installed, install one. See the certification matrix in "Supported Configurations" for information about supported JDK versions.
Run the java -version command, or java -d64 -version command on platforms using a 32/64-bit hybrid JDK to ensure that the JAVA_HOME environment variable is set to a 64- bit JDK.
If JAVA_HOME is not correctly set, set it to point to the correct JDK.
Add the bin directory of the appropriate JDK (which you have installed separately) to the beginning of the PATH variable definition on the target system. For example:
PATH=$1.5 GB1.5 GBJAVA_HOME/bin:$PATH export PATH
Here JAVA_HOME represents the full path to the JDK directory.
Change to the directory where you downloaded the installation program.
To start the generic installer in console mode, do one of the following:
To start the 32-bit generic installer, enter:
java -jar ocsg510_generic.jar -mode=console [-log=logfilename]
To start the 32/64-bit hybrid generic installer, enter:
java -d64 -jar ocsg510_generic.jar -mode=console [-log=logfilename]
To start the 64-bit hybrid generic installer on Solaris-SPARC, enter:
java -Xmx1024m -jar ocsg510_generic.jar -mode=console [-log=logfilename]
The Welcome screen appears in the console.
Enter Next to continue with the installation.
In the Middleware Home Directory screen, if you have any existing Middleware home directories they are displayed. Do one of the following:
To use an existing Middleware Home directory:
Enter the number associated with the directory in the console display.
Caution:
Make sure that the Middleware home installation you select is running WebLogic Server version 10.3.6.Press Enter.
To create a new Middleware Home directory:
Enter 1.
Press Enter.
Enter the full path of the new Middleware Home directory or Next to accept the default.
When prompted to confirm your choice, press Enter to confirm or Previous to change your selection.
In the Release screen, specify the components that you wish to install:
To remove components from the planned installation, enter the number in brackets following any components that you do not wish to install.
The screen refreshes, and the check mark next to that component is removed.
Note that you cannot install the Platform Development Studio without WebLogic Server and Oracle Communications Services Gatekeeper.
Enter Next to continue.
In the JDK Selection screen, add the path to your local JDK.
Enter Next to continue.
If you are including the Platform Development Studio in the installation, the Platform Development Studio Eclipse Plugin Path screen appears.
In the Platform Development Studio Eclipse Plugin Path screen, enter 1.
Enter the full path of the Eclipse plugins directory.
The screen refreshes, and the path is displayed.
Enter Next to continue.
In the Choose Product Directories screen, specify the directories in which you want to install the Services Gatekeeper and WebLogic software. Do one of the following:
To accept the default product directories, enter Next.
To create one or more new product directories:
Enter the product index number to specify the product to be installed in the directory.
Enter the full path to the directory you are creating.
Enter Next.
When prompted, confirm your choice.
Enter Next.
If you are using the generic installer on Windows, the Install Node Manager as a Windows Service appears.
Do one of the following:
If you are not installing on Windows, skip to step 20.
If you are installing on Windows, in the Install Node Manager as a Windows Service screen, do one of the following:
To install the Node Manager as a Windows Service, enter Yes and then the Node Manager listen port at the prompt.
To skip installing the Node Manager as a Windows Service, enter No.
The Windows installer displays the Choose Shortcut Location screen if you have Administrator privileges and are performing an initial Services Gatekeeper installation. This screen is used to specify the Start menu folder for the Services Gatekeeper Start menu shortcuts.
Do one of the following:
Enter 1 to select the All Users Start menu folder.
Only users with Administrator privileges can create shortcuts in the All Users folder. Therefore, if a user without Administrator privileges uses the Configuration Wizard to create domains, Start menu shortcuts to the domains are not created. In this case, users can manually create shortcuts in their local Start menu folders, if desired
Enter 2 to select the Local user's Start menu folder.
This option ensures that other users registered on this machine will not have access to the Start menu entries for this installation.
When prompted, confirm your choice.
Enter Next to continue.
In the Installation Summary window, make sure the list reflects all the products and JDKs you have chosen to install.
Enter Next to begin the installation.
When the installation is complete, press Enter to exit the installer.
After installation is complete, set the WL_HOME environment variable to the product installation directory that you designated for WebLogic Server.
Export WL_HOME. For example:
export WL_HOME=your_installation_directory/wlserver_10.3 cd $WL_HOME/server/native/hpux11/IPF32/
Silent-mode installation is a way of choosing installation settings once and then using those settings to duplicate the installation on many machines. During installation in silent mode, the installation program reads your settings from an XML file that you create prior to beginning the installation. The installation program does not display any options during the installation process. Silent-mode installation works on both Windows and UNIX/Linux systems.
For general information on silent-mode installation on WebLogic Server see the discussion on running the installation program in silent mode in Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server at:
http://download.oracle.com/docs/cd/E15523_01/doc.1111/e14142/silent.htm
The entries in the silent.xml file correspond to the prompts that you would see if you used one of the interactive modes.
Incorrect entries in the silent.xml file can cause installation failures. To help you determine the cause of a failure, we recommend that you create a log file when you start the installation
The following is a sample version of a silent.xml file. Your input may be slightly different, depending on your installation.
<?xml version="1.0" encoding="UTF-8" ?>
<bea-installer>
<input-fields>
<data-value name="BEAHOME" value="d:/ocsg" />
<data-value name="INSTALL_NODE_MANAGER_SERVICE" value="no" />
<data-value name="WLNGEclipseConfig.dir" value="d:/eclipse/plugin"/>
<data-value name="LOCAL_JVMS" value="C:\oracle\java\jdk160_18">
</input-fields>
</bea-installer>
The following error can be ignored:
com.bea.plateng.domain.script.ScriptException: The template to read must be a jar file containing a valid domain configuration
See Oracle WebLogic Server Installation Guide for more information on using silent installation.
When run in silent mode, the installation program generates exit codes that indicate the success or failure of the installation. Table 4-1 describes these exit codes:
Table 4-1 Installation Program Exit Codes
| Code | Description |
|---|---|
|
0 |
Installation completed successfully. |
|
-1 |
Installation failed due to a fatal error. |
|
-2 |
Installation failed due to an internal XML parsing error. |
If you are launching the silent-mode installation process from a script, you can choose to have these exit codes displayed to the console. The following is a sample command file that invokes the WebLogic Platform installation in silent mode and echoes the exit codes to the console from which the script is executed.
rem Execute the installer in silent mode
@echo off
ocsg510_win.exe -mode=silent -silent_xml=silent.xml -log=logfilename
@rem Return an exit code to indicate success or failure of installation
set exit_code=%ERRORLEVEL%
@echo.
@echo Exitcode=%exit_code%
@echo.
@echo Exit Code Key
@echo ---------------
@echo 0=Installation completed successfully
@echo -1=Installation failed due to a fatal error
@echo -2=Installation failed due to an internal XML parsing error
@echo.
To run the silent mode installer:
Create a silent.xml file, as described in "About the silent.xml File".
To run the silent installer, do one of the following:
To start the platform-specific Windows32 installer in silent mode, enter:
ocsg510_win.exe -mode=silent -silent_xml=silent.xml [-log=logfilename]
To start the platform-specific Linux32 installer in silent mode, enter:
ocsg510_linux.bin -mode=silent -silent_xml=silent.xml [-log=logfilename]
To start the platform-specific Solaris-Sparc32 installer in silent mode, enter:
ocsg510_solaris_sparc.bin -mode=silent -silent_xml=silent.xml [-log=logfilename]
To start the generic 32-bit installer in silent mode, enter:
java -jar ocsg510_generic.jar -mode=silent -silent_xml=silent.xml [-log=logfilename]
To start the generic 32/64 -bit hybrid installer in silent mode, enter:
java -d64 -jar ocsg510_generic.jar -mode=silent -silent_xml=silent.xml [-log=logfilename]
To start the generic /64 -bit hybrid installer in silent mode, enter:
java -Xmx1024m -jar ocsg510_generic.jar -mode=silent -silent_xml=silent.xml [-log=logfilename]
The installation proceeds with no prompts.
If you wish to configure support for Services Gatekeeper portal and reporting functionality, see "Installing Services Gatekeeper Reporting and Portal Support".
After installing Services Gatekeeper, you must configure the Services Gatekeeper's Administrative Domain. See "Configuring the Domain for Oracle Communications Services Gatekeeper".
If you wish to be able to start and stop servers remotely, for example by using the Administration Console, you must set up Node Manager on each server. If you installed in Windows, the installer provided an option to install the Node Manager as a Windows service. For information on setting up and configuring the Node Manager on other platforms, see Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server at:
http://download.oracle.com/docs/cd/E15523_01/web.1111/e13740/toc.htm
|
 Copyright © 2007, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|