Before installing Enterprise Portal 6.0, you must perform some pre-installation tasks, and make sure the WebLogic Server and Oracle environments are set up correctly.
Before you install Enterprise Portal, you must:
Verify that there is a “.” (dot) in the PATH environment variable.
Verify that you have write permission on your login home directory, the directory where you install the software, and the /tmp/logs directory.
Verify that you have 928MB free space in your temporary directory, otherwise the installation fails.
If you do not have enough space in the default temporary directory set by the installer, set the environment variable to redirect to a temporary directory set by you.
The temporary directory to which you are redirecting
must exist before you set the environment variable.
To redirect your temporary directory when using EPSetup, enter:
./EPSetup -is:tempdir /work/tmp
where /work/tmp is the directory of your choice.
Before installation, you should know the domain name of the machine where you are installing Enterprise Portal. This information is required during the installation. To find your domain name, contact your system administrator, or at a command prompt, enter:
domainname
Use the following information to create and configure the WebLogic Server and domain, during the pre-installation phase. See your WebLogic documentation for more information about setting up WebLogic Server.
If you already have a WebLogic Server and domain installed
and configured, you need not configure a new WebLogic Server or
define a new domain.
If you create a new WebLogic Server, make these selections:
Choose a complete installation.
Use default initial listener properties, with the server listener entry left blank.
Choose a standalone single server.
To deploy Enterprise Portal 6.0 on WebLogic Server, you need a WebLogic Server domain. If you create a new domain, use these parameters:
Select New Domain.
Select WebLogic Basic Domain.
Select either Express or Custom. If you choose Custom, use the WebLogic documentation to make the appropriate configuration settings.
Select Development mode or Production mode, depending on your requirements.
The WebLogic Server startup script must be named startWebLogic.sh, or the Enterprise Portal installation reports a File Not found error.
If you are using the sample file startExamplesServer.sh as a base to create your WebLogic startup script, be sure to rename it startWebLogic.sh. The sample file is located in:
$SYBASE/$BEA/weblogic81/sample/domain/examples
Before you start the WebLogic Server, execute the following command from the console or terminal to increase the number of open file descriptors available to a process:
unlimit descriptors
You need to issue the unlimit command
from the console or terminal every time you start the WebLogic server.
Start the WebLogic Server, and verify it is running.
Verify that the boot.properties file exists in the user’s server domain directory, for example in $BEA/user_projects/domain/mydomain. If it does not, you must create one prior to installation. See the WebLogic documentation for information about creating the file (using WebLogic samples), and modifying the file for your WebLogic account.
Verify that the server is SSL enabled.
If you plan to implement an Oracle database for the portal database, rather than Adaptive Server Anywhere, use the following information to create and configure the Oracle database. See your Oracle documentation for more information about setting up Oracle databases.
Verify your Oracle installation and access to the Oracle client software.
Copy the classes12.jar file (or classes12.zip) from $ORACLE_HOME/jdbc/lib to $BEA/weblogic81/server/lib. You must stop and start the WebLogic server for the change to take effect.
You must create the following Oracle tablespaces:
Tablespace name |
Size |
|---|---|
OP_PORTAL_DATA |
50MB |
OP_PORTAL_IDX |
50MB |
ACDB_DATA |
100MB |
ACDB_IDX |
30MB |
Verify that you have access to the Oracle system password and ORACLE_SID. In a single-instance database system, the instance name is usually the same as the database name. ORACLE_SID can be on a different machine than the Enterprise Portal installation.
Verify the Oracle LISTENER is running.
