| |
Home |
![[Table of Contents]](/dwicons/b_toc.gif)
|
Enterprise Event Broker Installation Guide |
![[-]](/dwicons/i_colpse.gif)
| Chapter 2 Installation Instructions |
Chapter 2
Before you install EAServer and Enterprise Event Broker, you must:
Have the Sybase System Asset Management (SySAM) certificate available. The printed SySAM certificate is included with your Enterprise Event Broker package.
See Appendix A, "Sybase System Asset Management (SySAM)" for information about SySAM. This is especially important if you plan to use SySAM in a networked configuration, or if you plan to install a redundant server system as part of a failover plan or a load-balancing system.
Identify or create a Sybase installation directory.
Check the following environment settings:
On UNIX, verify that a "." (dot) is in the PATH environment variable.
On Windows NT, verify that "WINNT" and "system32" are in your PATH (for example, c:\WINNT\system32). Also, make sure that JAVA_HOME is not set. Sybase Central includes its own JRE, which is not compatible with other virtual machines. If JAVA_HOME is set on your machine, Sybase Central does not work.
Verify that you have installed and configured components such as Adaptive Server Enterprise, Replication Server, TIB/Rendezvous Professional, and IBM MQSeries.
Verify that you meet the system requirements identified in the Enterprise Event Broker release bulletin.
Verify that you have the appropriate operating system patches installed as described in the Enterprise Event Broker release bulletin.
If you plan to develop custom Enterprise Event Broker objects, install JDK 1.2.2.
If you are upgrading from SEEB 1.0 to SEEB 2.0, SEEB 2.0 will be installed in a separate directory from SEEB 1.0. Keep in mind the following if you plan to use flowspaces developed under SEEB 1.0 in SEEB 2.0:
You will need to copy the flowspaces from the SEEB 1.0 directory to the SEEB 2.0 directory as a post-installation step, so do not remove the SEEB 1.0 directory.
Before you start the installation, it is a good idea to back up the contents of the SEEB 1.0 data directory, which contains flowspaces associated with a SEEB server.
Use the Studio Installer on the Enterprise Event Broker CD to create the target directory (if necessary), set Sybase environment variables, collect licensing certificate information, and perform the basic configuration.
The configuration utility gathers information for the configuration of EAServer and Enterprise Event Broker. All of the requested information has an appropriate default value automatically supplied by the installer. Accept the default unless you are certain you need to change it.
Start the EAServer and Enterprise Event Broker installation. On Windows NT:
Log in to your Windows NT computer using an account with administrator privileges.
Close any open applications or utilities.
Insert the CD in the CD-ROM drive.
The Studio Installer should start automatically. If it does not:
Select Start | Run, and type:
x:\setup.exe
where x: is your CD-ROM drive.
Or, choose the Windows Explorer, select the CD-ROM drive, and double-click setup.exe.
On UNIX:
Log on using an account with full permission for the directory in which you are installing (or log in as a user with "root" privileges).
Sybase recommends against remote installation of EAServer and Enterprise Event Broker components.
Insert the CD in the CD-ROM drive. Solaris automatically mounts the CD. If you get CD-reading errors, check your operating system kernel to make sure the ISO 9660 option is turned on.
At the UNIX prompt, start the Studio Installer:
cd /cdrom/cdrom0
./installwhere cdrom/cdrom0 is your CD-ROM drive.
Select the type of installation to be performed and click Next. For this release, the same files are installed for each type, so select Full.
Standard Install - installs the default components a user needs.
Full Install - installs every component on the CD.
The Studio Installer displays the default installation directory (%SYBASE% on Windows NT or $SYBASE on UNIX). Accept the default, or enter a different directory, then click Next.
A Summary screen displays a list of components and services that will be installed, the disk space required, and the disk space available. If the target directory does not have enough free space, the information appears in red.
At this point, you can optionally click Save to save this installation configuration to a file for reference. To do so:
Click Save.
Click OK to accept the default file location, or modify the location and click OK. Supply a fully qualified directory path. The default file location is %SYBASE%\cmdfile (Windows NT) or $SYBASE/cmdfile (UNIX).
Click OK to return to the Summary screen.
Click Next to exit the Summary screen and begin the installation.
Warning!
If you have insufficient disk space and click Next, an error occurs that stops the installation.
If the target installation directory does not already exist, the Studio Installer prompts: "OK to create directory?"
Click Yes.
Warning!
On Windows NT, if you are prompted to overwrite any DLLs, select Yes only if the DLL version provided on the Sybase Enterprise Event Broker CD is more recent than the one currently installed on the system. The greater number is the most recent version.
A status bar shows the progress of the installation. This step may take five to fifteen minutes, depending on the size and speed of the machine.
If you encounter problems during the installation, see Chapter 3, "Troubleshooting" and the installation log file to see a record of the installation process. On Windows NT, the log file location is:
%SYBASE%\Installer.log
On UNIX:
$SYBASE/Installer.log
After you install Enterprise Event Broker components, the Studio Installer prompts: "Do you have a Sybase Software Asset Management Certificate to register?"
Click Yes if this installation is on the primary server, which is also called the license host. Components installed on secondary servers must access the license host to enable certain features.
See Appendix A, "Sybase System Asset Management (SySAM)" for information about SySAM.
The License Manager screen appears. Enter the information that is provided on a printed Sybase Software Asset Management (SySAM) certificate in your Enterprise Event Broker package:
Order Number
Feature Name
Feature Count
Software Version
Authorization Code
On Windows NT, if you do not register the SySAM certificate during the installation, SySAM is not installed as a Windows NT service. See "Post-installation tasks" for instructions on starting SySAM manually.
Click Continue Install.
On Windows NT, when prompted to reboot the computer, leave the CD in the CD-ROM drive and click Yes. After rebooting, the computer accesses the CD for additional data. For this reason, the CD must remain in the CD-ROM drive during reboot, and the CD-ROM drive must be on the installation machine.
The installer prompts: "Do you wish to configure the newly installed product?"
Click Yes.
During the configuration, a series of screens prompt for configuration information for a variety of Enterprise Event Broker components and services. Most screens are automatically populated with default values.
Warning!
Unless you are certain that a default value needs to be changed, Sybase recommends that you accept the defaults for every component.
A tooltip provides information about each input field in the configuration process. Activate tooltips by placing your cursor over the field for which you require more information. You can also click the Help button on each screen for general information about the information being requested.
The series of screens are:
Sybase installation directory for this configuration. This is the directory you specified during the installation.
Accept the default, and click Next. A series of dialog boxes displays showing the progress of several automatic activities.
Sybase Enterprise Event Broker.
Accept the defaults, and click Next. A series of dialog boxes displays showing the progress of several automatic configuration activities.
The message, "Configuration of installed products is complete" displays when the process completes.
Click OK.
The message, "Install complete" displays.
Click OK to exit Studio Installer.
You have successfully installed and configured EAServer and Enterprise Event Broker.
Do not stop or remove a component unless you are absolutely sure that you need to do so. Stopping or removing any component can have serious implications to your environment.
Complete the post-installation tasks in this section to finish the installation. If you encounter problems performing any of these tasks, it may be due to a problem introduced during installation. See Chapter 3, "Troubleshooting". Additional troubleshooting and problem handling information is included in the Enterprise Event Broker User's Guide.
Sybase Central provides a graphical user interface for performing EAServer and Enterprise Event Broker administrative tasks.
To start Sybase Central on Windows NT, select from the Windows task bar Start | Programs | Sybase | Sybase Central Java Edition.
To start Sybase Central on UNIX:
From a command line, enter:
source $SYBASE/SYBASE.csh
Then enter:
$SYBASE/sybcent32/java/scjview
If JAVA_HOME is set, you receive a message similar to:
Error Loading the Java VM. Sybase Central could not be started.
Unset JAVA_HOME to start Sybase Central successfully. You can "unset" JAVA_HOME temporarily (
unsetenv JAVA_HOME).
For additional information, refer to the online help:
Sybase Central - select Help | Sybase Central Help.
SEEB Manager - right-click the SEEB Manager icon in the left pane of Sybase Central, and select Online Help.
For Jaguar Manager help, see the Technical Library CD.
The Studio Installer installs SySAM and configures it to start automatically any time EAServer is restarted. To restart SySAM manually on Windows NT, go to %SYBASE%\SYBASE_SYSAM-1_0\bin, and run:
lmgrd.exe
To restart SySAM manually on UNIX, go to $SYBASE/SYBASE_SYSAM-1_0/bin, and run:
startd.sh $SYBASE/SYBASE_SYSAM-1_0
When the lmgrd daemon starts, it automatically starts the SYBASE daemon. After restarting SySAM manually, verify that the license management software is actually running on the system. On Windows NT, from a command line, enter:
%SYBASE%\SYSAM-1_0\bin\lmutil lmstat -c
On UNIX:
$SYBASE/SYSAM-1_0/bin/lmutil lmstat -c
Make sure that both the lmgrd and SYBASE daemons are running before you attempt to register secondary servers with the license host.
jConnect 5.2, and the Java utilities jisql and Ribo use JDK 1.2 or JRE 1.2. You can download the JDK or JRE from Sun's Java Software Web site at:
http://java.sun.com/products/index.htmlInstall it using the JDK or JRE installation instructions, and set the JAVA_HOME environment variable to point to your Java installation.
If you do not want to install and configure your own Java environment, but would like to use jConnect 5.2 or Java-based utilities, set JAVA_HOME to %SYBASE%\shared-1_0\jre1.2.2 (Windows NT) or $SYBASE/shared-1_0/jre1.2.2 (UNIX), where $SYBASE is the installation directory.
To develop applications for jConnect 5.2, you must use JDK 1.2, not JRE 1.2.
See Chapter 2, "Getting Started" of the Enterprise Event Broker User's Guide for additional post-installation tasks. (The user's guide is available in HTML and PDF formats in the docs subdirectory under %SYBASE%\SEEB-2_0 or $SYBASE/SEEB-2_0).
The Enterprise Event Broker User's Guide includes instructions for configuring SEEB as an EAServer component in standalone mode, and as part of Enterprise Portal. For this release, follow the instructions for establishing SEEB as an EAServer component in standalone mode.
You will need to:
Set up the SEEB environment.
Verify that SEEB/EASService was established as an EAServer component.
Finish configuring SEEB/EASService properties.
If SEEB server does not start when EAServer starts, the SySAM license for SEEB might not be set correctly. See Table 3-2 in Chapter 3, "Troubleshooting" for information.
Note that config.log, which is created during the configuration process, provides a text copy of all input supplied during configuration, including user name and password. To keep the information secure, Sybase recommends you either delete the file or take steps to protect it after installation.
Keep in mind these fundamental changes when you upgrade from SEEB 1.0 to SEEB 2.0:
The SEEB 1.0 scripts seebserverstart and run_sample are not used when you run SEEB 2.0 in EAServer.
The license.dat file used for licensing in SEEB 1.0 has been replaced by the SySAM in SEEB 2.0. SySAM also uses a license.dat file, but it is not compatible with the older version.
In SEEB 2.0, EAServer properties have replaced seebserverstart usage settings. EAServer properties are set through Jaguar Manager. Table 2-1 lists the EAServer properties and the seebserverstart usage equivalents from SEEB 1.0.
EAServer property | seebserverstart usage equivalent | Description |
com.sybase.seeb.LogFile | -e error_log | The name of the file to which SEEB server logs messages. The default value is seeb.log. |
com.sybase.seeb.LogDir | -l log_directory | The directory location of SEEB's error files, log files, and debugging output files. On Windows NT, if you specify an absolute path, such as C:\Program Files\Sybase\SEEB, that is the directory's location. If you specify only a directory name, such as SeebLogDir, the directory location is relative to the %JAGUAR%\bin location. For example, if %JAGUAR% is e:\jaguar and you set com.sybase.seeb.LogDir to SeebLogDir, the resulting log file directory is e:\jaguar\bin\SeebLogDir. On UNIX, the directory location is not relative to the $JAGUAR location. |
com.sybase.seeb.LicensePath | -L license_file | Specifies the license file for the license daemon to which you are connecting. The default location is:
The Studio Installer puts the appropriate licenses, such as for TIBCO Adapter and MQSeries Adapter, in this location. Access the license file through the SYSAM license daemon. |
com.sybase.seeb.ServerDataDirectory | -d data_directory | The directory location of SEEB runtime files. During installation, Studio Installer sets the location using the SEEB_HOME location: %SEEB_HOME%\data (Windows NT) or $SEEB_HOME/data (UNIX). |
com.sybase.seeb.ServerDtdDirectory | -t dtd_directory | The directory location of document type definition (DTD) files. During installation, Studio Installer sets the location using the SEEB_HOME location: %SEEB_HOME%\dtd (Windows NT) or $SEEB_HOME/dtd (UNIX). |
com.sybase.seeb.ServerName | -n server_name | The SEEB server name associated with SEEB/EASService.
|
com.sybase.seeb.DebugClasses | -D class_list | Enables debugging output for all SEEB classes or the classes you specify. Enter ALLto include all classes, or enter a list of classes to include only specific classes, for example: SEEBMain:SEEBManager:SQLAdapter Use colons to separate class names in a list. The default value is "ALL." |
com.sybase.seeb.DebugOutputFile | -o debug_log | The name of the file to which SEEB server sends debugging output if you set debugging mode and specify debugging output files instead of terminal output. If you do not provide an alternative output file name, the debugging information is sent to debug.out. |
com.sybase.seeb.Verbose | -v | Indicates that the server status is sent to EAServer's log file, srv.log, during SEEB server start-up and shutdown, and that all errors are sent to STDERR. The default value is "false." |
If you have been using SEEB 1.0, you can copy flowspaces you developed with SEEB 1.0 to SEEB 2.0. However, SEEB 1.0 flowspaces are limited to 1.0 functionality.
Make sure you have installed and configured SEEB 2.0 successfully.
Create a subdirectory for the SEEB 1.0 SEEB server name under the SEEB 2.0 data directory. For example, if your SEEB 1.0 server name is "purchase_processes", you can create the subdirectory %SYBASE%\SEEB-2_0\data\purchase_processes (Windows NT).
Copy the contents of the version 1.0 SEEB server data directory to the newly created version 2.0 subdirectory. For example, copy everything from %SYBASE%\SEEB-1_0\data\purchase_processes to %SYBASE%\SEEB-2_0\data\purchase_processes.
Modify the EAServer properties for the new server. For example, set the EAServer property com.sybase.seeb.ServerName to "purchase_processes" instead of "Unnamed_Server." See Chapter 2, "Getting Started" of the Enterprise Event Broker User's Guide for information about modifying the EAServer properties.
The other EAServer properties should already be set correctly to the SEEB-2_0 location.
If you created any new class files (or FactoryExtensions) with SEEB 1.0, copy them to the EAServer directory structure. The EAServer directory location is %JAGUAR%\java\classes (Windows NT) or $JAGUAR/java/classes (UNIX). This location is included in EAServer's BOOTCLASSPATH. When EAServer restarts, any classes included in the directory location are compiled in EAServer's virtual machine (VM). The JAGUAR environment variable points to the installation location of Jaguar CTS 3.5.
In addition, copy your custom SEEB 1.0 classes into the SEEB-2_0 directory structure: %SYBASE%\SEEB-2_0\lib (Windows NT) or $SYBASE/SEEB-2_0/lib (UNIX).
Restart EAServer to initialize the changes.
Once you feel confident that Enterprise Event Broker is working satisfactorily, you can remove the SEEB-1_0 installation directory.
This section describes how to remove EAServer and Enterprise Event Broker components. This is usually needed only if you experienced problems during installation or configuration. Removing components can render your installation useless.
If you decide to uninstall EAServer, Sybase recommends that you first remove Adaptive Server Enterprise (if installed), then remove EAServer.
To remove components from Sun Solaris:Before removing a component, use the Jaguar Manager plug-in to Sybase Central Java to stop the component:
Right-click the component that you want to uninstall.
Select Stop.
Repeat these steps for each component that you want to uninstall.
Start the Studio Installer. From the $SYBASE/Installer/bin directory, run:
uninstall
If you have a "." (dot) in the PATH, omit the "./" before the script at the command line. Otherwise, set your current directory to $SYBASE and execute the command Installer/bin/uninstall.
This starts the Studio Installer and launches the Uninstall screen.
The Studio Installer prompts: "Uninstall components now?"
Click Yes.
A component selection screen appears. Select individual components by clicking the check box to the left of the component, or by clicking Select All.
Click Next.
The Uninstall summary screen displays the components selected for removal.
Click Next.
The Studio Installer begins removing the selected components from the system. A progress indicator notifies you when the components have been successfully removed.
Click OK to exit the application.
Before removing a component, use the Jaguar Manager plug-in to Sybase Central Java to stop the component:
Right-click the component that you want to uninstall.
Select Stop.
Repeat these steps for each component that you want to uninstall.
From the Windows task bar, select Start | Programs | Sybase | Uninstall.
This starts the Studio Installer and launches the Uninstall screen.
The Studio Installer prompts: "Do you wish to proceed with uninstall now?"
Click Yes.
A component selection screen appears. Select individual components by clicking the check box to the left of the component, or click Select All.
Click Next.
The Uninstall summary screen displays the components selected for removal.
Click Next.
The Studio Installer begins removing the selected components from the system. A progress indicator notifies you when the components have been successfully removed.
You may need to reboot to update the system registry.
The Studio Installer removes:
All files installed from the Enterprise Event Broker CD's Archives directory
All directories it created, unless the directory is not empty
All shortcuts
Registry entries and values
After running the uninstall utility, a message displays stating that you should remove the remaining directories and files. The uninstall utility cannot remove the Studio Installer itself, or the JRE used by the installer as these are required to run the uninstall utility. Remove these directories and files after you finish running the utility and have confirmed that it was successful.
Also, the Studio Installer does not remove registry keys or system DLLs. To remove registry keys and DLLs, see the Microsoft Windows NT documentation.
|
|