There are two different types of installations you can perform with Enterprise Portal 6.0 – typical and custom. There are slight variations in the procedures for the different types of installations.
These instructions are for performing a typical installation.
If you are performing a custom installation, go to “Custom installation”.
Performing a typical installation
of Enterprise Portal 6.0
Insert the Enterprise Portal CD, and change to the CD directory.
Launch the installer from the command line by entering:
./EPLinuxSetup
Once the installer launches, in the first window, click “Here” to view the Enterprise Portal 6.0 Release Bulletin. Click Next to continue.
In the End-user License Agreement window, from the drop-down menu, select the geographical location where the software is being installed.
The license agreement appears in the window.
Read the license agreement, and select “I agree to the terms of the Sybase license for the install location specified,” and click Next.
In the next window, accept the default installation directory, enter the name of the root directory where you want to install Enterprise Portal, or use the Browse button to select the installation location.
If you enter a directory that has not yet been created, the installer creates the directory automatically. Click Next.
In the next window, select Typical, and Click Next.
In the next window, the machine name and domain of the Enterprise Portal installation appear.
If the information is incorrect, enter the machine name and domain of the Enterprise Portal installation machine. For example, if your computer is named “mycomputer” and your domain is “sybase.com,” enter:
mycomputer.sybase.com
If your computer is on an Internet subdomain, enter that information as well. For example, if your computer is on an Internet subdomain named “legal,” enter:
mycomputer.legal.sybase.com
Click Next.
The pre-installation summary window appears and shows:
Components to be installed
Size of components to be installed
The space estimate shown in the pre-installation summary
is off by 60MB because the size of the uninstaller is not yet determined
by the installer.
Installation location
Database settings:
Type – the type of database installed. For example, Adaptive Server Anywhere.
Host – the name of the machine where the database is installed.
Port – the port used to connect to the database.
Application server settings:
Type – the type of application server installed. For example, EAServer.
Host – the name of the machine where the application server is installed.
Port – the port used to connect to the application server.
Portal settings
Connection URL – the URL used to access Portal Interface.
Click Next.
You see a series of progress bars that show the status of the installation. The status windows you see depend on the type of installation you are performing.
A message appears saying, “Installing Sybase Enterprise Portal. Please wait.”
The Installer Events Report window appears. In the Installer Event box, the installer events are listed. Select the event title to view an expanded description in the Event Description box.
The Log File Location box shows the location of the installation log file.
Click Next.
If the installation is successful, you see the Installation Successful window.
Click Finish to exit the installer.
The custom installation allows you to utilize a pre-installed Adaptive Server Enterprise database and EAServer.
If you install EAServer 4.2.2 from the Enterprise Portal
6.0 CD, when you uninstall Enterprise Portal 6.0, EAServer is also
uninstalled by the Enterprise Portal uninstaller.
If you do not want to uninstall EAServer when you uninstall Enterprise Portal, you must install EAServer from the EAServer CD before installing Enterprise Portal. Then you must perform a custom installation and select the installed EAServer.
You must have the target computer’s name and the fully qualified domain name.
When performing a custom installation that utilizes a preexisting Adaptive Server Enterprise:
Adaptive Server Enterprise must be running before beginning the installation.
You must create four database devices before beginning the installation:
Device name |
Size |
|---|---|
portalData |
300MB |
portalLog |
100MB |
acdbData |
100MB |
acdbLog |
25MB |
For example, to create the portalData device, open an isql session and at the isql 1> prompt, enter, on one line:
disk init NAME="portalData", PHYSNAME="software/sybase/data/portalData.dat", VDEVNO=2, SIZE="300M"
where /software/sybase is the $SYBASE directory in your environment. Repeat this command for each device you create.
You must increment the VDEVNO value for each device
you create; the device number must be unique in the database system.
Using a text editor, open /etc/sysctl.conf and set the value for fs.aio-max-size to 1MB.
To keep this value at 1MB through restarts, enter:
/sbin/sysctl -p
When performing a custom installation that utilizes a preexisting EAServer:
Install Enterprise Portal on the same machine on which EAServer is installed.
The shared directory for EAServer must reside in the $SYBASE directory. If you are installing into an existing EAServer, and the shared directory is under $JAGUAR, the Enterprise Security installation fails.
If the EAServer you are using is located on a different
machine from the Adaptive Server Enterprise, you must verify the
network file system is set to “on.” Log in and
enter su so that you are logged
in as ‘root.’
Then enter:
/sbin/chkconfig nfs on
EAServer must be running on jdk14 for Linux before you can install Security, Portal Interface, and Portal Studio.
Verify that you have JAVA_HOME in your path by entering:
JAVA_HOME = $SYBASE/_jvm; export JAVA_HOME
If the JDK version is not specified in serverstart.sh, you must specify the JDK version. by editing the serverstart.sh file. In the “Set Default Options” section, enter:
JDK_VERSION=jdk14
Install EAServer 4.2.2 with the proper patch level installed (EBF 11860).
Installing the EAServer patch
Shut down EAServer and close Jaguar Manager. See “Starting Jaguar Manager”.
Back up these files, located in $JAGUAR:
bin/jagsrv
devbin/jagsrv
devlib/libjcc.so
devlib/libjcm.so
devlib/libjjdk12.so
devlib/libjjdk13.so
devlib/libjjdk14.so
devlib/libjeasproxyeapi_mod.so
devlib/libjeas_httpd40.so
devlib/libjhttp.so
devlib/libjeaseapi_mod.so
devlib/libjeas_mod.so
devlib/libjeasproxy_mod.so
devlib/libjeas2_mod.so
devlib/libjeas2eapi_mod.so
devlib/libjdispatch.so
easmgr/jagplugin.jar
easmgr/jagplugin.jar
java/lib/
java/lib/easserver.jar
java/lib/easclient.jar
lib/libjcc.so
lib/libjcm.so
lib/libjjdk12.so
lib/libjjdk13.so
lib/libjjdk14.so
lib/libjeasproxyeapi_mod.so
lib/libjeas_httpd40.so
lib/libjhttp.so
lib/libjeaseapi_mod.so
lib/libjeas_mod.so
lib/libjeasproxy_mod.so
lib/libjeas2_mod.so
lib/libjeas2eapi_mod.so
lib/libjdispatch.so
The EAServer 4.2.2 patch is located in the EASPatch directory on the Enterprise Portal CD. Read EASpatch.txt for the instructions for applying the EAServer patch.
Restart EAServer and Jaguar Manager.
SSL is not enabled after installing into an existing
EAServer. Refer to the Enterprise Security Administration
Guide for instructions on enabling SSL.
Performing a custom installation
Insert the Enterprise Portal CD, and change to the CD directory.
Launch the installer from the command line by entering:
./EPLinuxSetup
Once the installer launches, in the first window, click “Here” to view the Enterprise Portal 6.0 Release Bulletin. Click Next.
In the End-user License Agreement window, from the drop-down menu, select the geographical location where the software is being installed.
The license agreement appears in the window.
Read the license agreement, and select “I agree to the terms of the Sybase license for the installation location specified.” Click Next.
In the next window, accept the default installation directory, enter the name of the root directory where you want to install Enterprise Portal, or use the Browse button to select the installation location.
If you enter a directory that has not yet been created, the installer creates the directory automatically. Click Next.
In the installation type window, select Custom, and click Next.
In the Enterprise Portal Custom Install Overview window, read the information, and click Next.
In the Select the EAServer window, select either:
Install a New EAServer – installs a new EAServer with the default settings.
Choose an Existing EAServer – allows you to select a preexisting, installed EAServer on your system.
Click Next.
If you are installing a new EAServer, go to the next step.
If you are using a preexisting EAServer, in the next window, select the installation location of the EAServer you want to use. Verify the EAServer you are using is running.
If your EAServer is not named Jaguar, the EAServer information window
does not populate the server drop-down with your EAServer name and
associated information.
You must enter the information manually and click Verify.
Or, you can select “Specify Manually” to enter the installation location of EAServer manually.
Once you select the EAServer, these fields are filled in automatically:
Server – the name of the existing EAServer. By default, this is “Jaguar.”
Host Name or IP Address – the name of the machine where EAServer is installed.
Port Number – the port number of the existing EAServer. By default, this is 9000.
Login Name – the user name used to log in to EAServer. By default, this is “jagadmin.”
Manually enter:
Login Password – the password for the user name used to log in to EAServer. By default, this is blank.
Click Validate to verify the information entered is correct. If it is not, you receive an error message.
Click Next if all the information entered is correct.
In the next window, the machine name and domain of the Enterprise Portal installation are filled in. If the information is not correct, enter the machine name and domain of the Enterprise Portal installation machine. For example, if your computer is named “mycomputer” and your domain is “sybase.com,” enter:
mycomputer.sybase.com
If your computer is on an Internet subdomain, enter that information as well. For example, if your computer is on an Internet subdomain named “legal,” enter:
mycomputer.legal.sybase.com
Click Next.
In Select the Database window, select either:
Existing Sybase Adaptive Server Enterprise Database – allows you to use a preexisting Adaptive Server Enterprise. If you select this option, you must know the connection information for the selected Adaptive Server Enterprise.
Sybase Adaptive Server Anywhere Database – installs Adaptive Server Anywhere.
Click Next.
If you are using an existing Adaptive Server Enterprise, go to the next step.
If you are installing Adaptive Server Anywhere, in the next window, enter the port number for Adaptive Server Anywhere. The default is 6100.
If you are using an existing Adaptive Server Enterprise database, in the next window, enter the connection information for that database:
Database Type – the type of database being used. For example, if you are using Adaptive Server Enterprise, this is “ASE.” This is filled in automatically by the installer and cannot be changed.
Host Name or IP Address – the default is the name of the machine where the database is installed.
Port Number – the port number used to connect to the database. The default is 4100.
Database Administrator Login Name – the administrator user name used to log in to the database. The default is “sa” if you are using Adaptive Server Enterprise, “dba” if you are using Adaptive Server Anywhere.
Database Administrator Password – the password of the database administrator. The default is blank if you are using Adaptive Server Enterprise, “SQL” if you are using Adaptive Serve Anywhere.
Click Next.
In the next window, provide the security information for your organization:
Root Organization Name – the name of your company.
Security Database Owner Login Information:
Login – the default is “acdbdbo” for Enterprise Portal 6.0, “entldbdbo” for earlier versions of Enterprise Portal.
Password – the default is blank. You must set the password you want to use for the database owner.
Validate password – enter the same password again to validate.
Portal Security Officer Login Information:
Login – the default is “pso.”
Password – the default is blank. You must set the password you want to use for the Portal Security Officer. The password must be at least six characters long.
Validate password – enter the same password again to validate.
Make note of the login and password combinations you
enter, as you need them to log in to Enterprise Portal, or to uninstall
Enterprise Portal.
Select Advanced to enter:
Portal Security Officer e-mail address
Portal Security Officer phone number
Root organization contact information:
Contact – name of the contact person.
Address – address of the root organization.
City
State
Zip
Description
Click Next.
The next window shows the pre-installation summary:
Components to be installed
Size of components to be installed
Install location
Database settings:
Database Type – the type of database installed. For example, Adaptive Server Anywhere.
Host – the name of the machine where the database is installed.
Port – the port used to connect to the database.
Application server settings:
Type – the type of application server installed. For example, EAServer.
Host – the name of the machine where the application server is installed.
Port – the port used to connect to the application server.
Portal settings
Connection URL – the URL used to access Portal Interface.
Click Next.
The progress bar shows the status of the installation. A message appears: “Installing Sybase Enterprise Portal. Please wait.”
The Installer Events Report window appears. In the Installer Event box, the installer events are listed. Select the event title to view an expanded description in the Event Description box.
The Log File Location box shows the location of the installation log file.
Click Next.
The Installation Successful window displays.
See “Verifying the installation”.
Click Finish to exit the installer.
After installation, temporary files from the installation
may remain in $SYBASE/EAServer/bin. Or,
they may be in a different location if you ran ./Setup with
the redirect temporary space flag (for example, ./EPSetupLinux is:
tempdir/tmp).
Remove these files:
jagtool.err.configure
jagtool.err.create
jagtool.err.deploy
jagtool.err.install
jagtool.err.restart
jagtool.err.set_props
jagtool.err.shutdown
jagtool.log.configure
jagtool.log.create
jagtool.log.deploy
jagtool.log.install
jagtool.log.restart
jagtool.log.set_props
jagtool.log.shutdown
