This guide is intended for Oracle WebLogic Portal users who install WebLogic Portlets for Groupware Integration. The following sections explain the necessary prerequisites and documentation conventions for successfully installing this product on the various supported platforms:
Perform the following tasks before you install the WebLogic Portlets for Groupware Integration:
Note: | Refer to the WebLogic Portlets for Groupware Integration Supported Configurations Guide for information on supported versions of Microsoft Exchange and Lotus Domino. |
The Windows convention of “\” as a path separator is used wherever necessary. UNIX users and users of other operating systems should translate these paths and variables accordingly.
Also, because system software and configurations can vary from one system to another, portions of the command syntax displayed in this document may include sample parameters or variables that represent the actual command syntax you would need to enter.
This chapter explains the necessary procedures to successfully install the WebLogic Portlets for Groupware Integration on the various supported platforms. For standard installation procedures, refer to the following sections:
The following sections specify the installation prerequisites for a WebLogic Portlets for Groupware Integration installation.
The system requirements for WebLogic Platform are given in the following table.
A configuration of hardware, operating system, SDK, and database that is supported by WebLogic Platform 10.x is required. See WebLogic Platform Supported Configurations at
http://edocs.bea.com/platform/suppconfigs/index.html.
|
|
The Oracle Products installation program requires a Java runtime 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 installation program does not install a JDK. Filenames for these installation programs end in .jar . To run the .jar installation programs, you must have the appropriate version of the JDK installed on your system and include the bin directory of the JDK at the beginning of the PATH variable definition. It is important that you use a JDK because the installation process assigns values to JAVA_HOME and related variables to point to the JDK directory.
|
The installation program supports the following methods for installing the WebLogic Portlets for Groupware Integration software:
Graphical-mode installation is an interactive, GUI-based method for installing WebLogic Portlets for Groupware Integration. For instructions for using this method, see “Installing Using Graphical-Mode Installation” on page 4.
Note: | If you want to run graphical-mode installation, 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 systems do. If you attempt to start the installation program in graphical mode on a system that cannot support a graphical display, the installation program automatically starts console-mode installation. |
Console-mode installation is an interactive, text-based method for installing WebLogic Portlets for Groupware Integration, from the command line, on either a UNIX system or a Windows system. For instructions for using this method, see “Installing Using Console-Mode Installation” on page 7.
Perform the following steps to install the WebLogic Portlets for Groupware Integration using the Graphical-Mode Installation. To install on Windows, Solaris, or UNIX, see the following sections:
To start the installation in graphical mode on a Windows system:
wl_groupware_portlets_oracle103-XXX_win32.exe
Note: | In this filename, XXX represents the version number of the software you are installing. |
The installation program begins to install WebLogic Portlets for Groupware Integration.
The WebLogic Portlets for Groupware Integration 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 Portlets for Groupware Integration 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.
Note: | It is important that you use an SDK because the installation process sets the JAVA_HOME and related variables to point to this directory. |
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 Using Console-Mode Installation” on page 7.
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 Portlets for Groupware Integration installation program, for example: wl_groupware_portlets_oracle103-XXX_solaris32.bin
.
Note: | In this filename, XXX represents the version number of the software you are installing. |
The installation program begins to install WebLogic Portlets for Groupware Integration
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:
PATH=JAVA_HOME/bin:$PATH
export PATH
Note: | Here JAVA_HOME represents the full path to the SDK directory. |
Here, filename.jar
is the name of the WebLogic Portlets for Groupware Integration installation file, for example wl_groupware_portlets_oracle103-XXX_generic.jar.
Note: | In this filename, XXX represents the version number of the software you are installing. |
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:
|
|||
Perform the following steps to install the WebLogic Portlets for Groupware Integration using the Console-Mode Installation. You can install on Windows, Solaris, or UNIX.
To start the installation in console mode on a Windows system:
java -jar wl_domino_service_setup-43.jar -mode=console
The installation program begins to install WebLogic Portlets for Groupware Integration.
The WebLogic Portlets for Groupware Integration 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 Portlets for Groupware Integration 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.
Note: | It is important that you use an SDK because the installation process sets the JAVA_HOME and related variables to point to this directory. |
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 console mode:
chmod a+x filename.bin
./filename.bin – mode=console
Here filename.bin
is the name of the WebLogic Portlets for Groupware Integration installation program, for example wl_groupware_portlets_oracle103-XXX_solaris32.bin
.
Note: | In this filename, XXX represents the version number of the software you are installing. |
The installation program begins to install WebLogic Portlets for Groupware Integration.
If you have an installation program for UNIX platforms with a filename that ends in .jar
, follow these steps to start the installation in console mode:
PATH=JAVA_HOME/bin:$PATH
export PATH
Here JAVA_HOME
represents the full path to the SDK directory.
java -jar filename.jar – mode=console
Here, filename.jar
is the name of the WebLogic Portlets for Groupware Integration installation file, for example wl_groupware_portlets_oracle103-XXX_generic32.jar
. In this filename, XXX
represents the version number of the software you are installing.
To complete the console-mode installation process, respond to the prompts in each section by entering the number associated with your choice or by pressing Enter to accept the default. To exit the installation process, type exit (or x, for short) in response to any prompt. To review or change your selection, enter previous (or p, for short) at the prompt. To proceed to the following window, type next (or n, for short).
Note: | The sample console text and directory pathnames in this section use Windows conventions (backslashes) for pathnames, for example C:\bea\wlpgwi_10.3 . When entering pathnames on a UNIX system, use the UNIX convention (forward slashes) in pathnames, for example, /home1/bea/wlpgwi_10.3 . |
The following procedure steps you through the installation program. Use this procedure after you have started the installation program in console mode as described in the previous sections.
The Choose BEA Home directory prompt is displayed.
The installation program displays the following prompt:
->1¦*Create a new BEA Home [C:\bea]
Enter index number to select OR [Exit][Previous][Next]>
Note: | Instead of typing complete words when you want to enter [Exit], [Previous], and [Next], you can use the following one-letter shortcuts: x, p, and n, respectively. |
->1¦Yes, Use this BEA home directory [C:\bea]
2¦No, return to BEA home directory selection
Enter index number to select OR [Exit][Previous][Next]>
Note: | After you have selected your BEA Home directory and confirmed your selection, the Choose Install Type prompt is displayed. |
Note: | Specify the components as specified in the following text: |
+----WebLogic Portlets for Groupware Integration [1] v
+----WebLogic Services [1.5] v
Enter number exactly as it appears in brackets to toggle selection OR [Exit][Previous][Next]>
The choices displayed in this section are as follows:
Product Installation Directory= [C:\bea\wlpgwi_10.3]
Input new Product Installation Directory OR [Exit][Previous][Next]>
Choose Product Installation Directory:
->1| Yes, use this product directory [C:\bea\wlpgwi_10.3]
2| No, select another product directory
Enter index number to select OR [Exit][Previous][Next]>\
The no install option lets you bypass using an automated installer to install WebLogic Portlets for Groupware Integration. This option lets you manually copy the required files to the appropriate location under your BEA_HOME
directory. This section explains how to perform this manual installation procedure.
wl_groupware_portlets_bea103-10-noinstall.zip
. wl_groupware_portlets_bea103-10-noinstall.zip
to the BEA_HOME
directory and unzip it there. @USER_INSTALL_DIR
with the directory where the zip file was extracted. For example, if you unzipped the file in C:/bea
, then replace @USER_INSTALL_DIR
with C:/bea
.
BEA_HOME\wlpgwi_10\eclipse\links\com.bea.wlpgwi.link
BEA_HOME\wlpgwi_10\eclipse\plugins\
com.bea.wlpgwi.eclipse.groupware_10.0.0\plugin.xml
BEA_HOME\wlpgwi_10\eclipse\plugins\
com.bea.wlpgwi.eclipse.groupware_10.2.0\plugin.xml
BEA_HOME\wlpgwi_10\service\exchange_service\
wl_exchange_service_setup.cmd
BEA_HOME\wlpgwi_10.3\service\domino_service\wl_domino_service_setup.cmd
BEA_HOME\wlpgwi_10\eclipse\plugins\
com.bea.wlpgwi.eclipse.groupware_10.3.0\plugin.xml
BEA_HOME
\wlpgwi_10\eclipse\links\com.bea.wlpgwi.link
to