Enterprise Event Broker Installation Guide

Log file

Log file location

Studio Installer

On Windows NT: %SYBASE%\Installer.log

On UNIX: $SYBASE/Installer.log

Configuration utility

On Windows NT: %SYBASE%\Config.log

On UNIX: $SYBASE/Config.log

Jaguar installation log

On Windows NT: %SYBASE%\JaguarCTS35\JaguarCTS35.log

On UNIX: $SYBASE/JaguarCTS35/JaguarCTS35.log

Jaguar error log

On Windows NT: %JAGUAR%\bin\srv.log

On UNIX: $JAGUAR/bin/srv.log

SEEB error log

On Windows NT: %SYBASE%\SEEB-2_0\logs\seeb.log

On UNIX: $SYBASE/SEEB-2_0/logs/seeb.log

The SEEB error log is located in %SYBASE%\SEEB-2_0\logs\seeb.log (Windows NT) or $SYBASE/SEEB-2_0/logs/seeb.log (UNIX) by default. You can change the directory name using the EAServer property com.sybase.seeb.LogDir, and the log file name using the EAServer property com.sybase.seeb.LogFile.

SySAM log

On Windows NT: %SYBASE%\SYSAM-1_0\log\lmgrd.log

On UNIX: $SYBASE/SYSAM-1_0/log/lmgrd.log

Platform

Problem description

Action

UNIX

Power outage - need to reboot EAServer.

• Go to $SYBASE/SYSAM-1_0/bin and enter this command to start the license manager:

  startd.sh $SYBASE/SYSAM-1_0

• Go to $JAGUAR/bin and enter this command to start EAServer:

  srvstart.jdk12

• Start Adaptive Server Enterprise (if appropriate).

  If you have configured Adaptive Server Enterprise to use Distributed Transaction Management (DTM), and EAServer is configured to use connection pooling for DTM, start Adaptive Server Enterprise before you start EAServer.

• Go to $SYBASE/sybcent32/java and enter this command to start Sybase Central:

  scjview

• Once Sybase Central is active, connect to Jaguar Manager to restart each service or module.

UNIX

Cannot eject the CD from the drive.

If you cannot eject the CD from the drive:

• Check to see whether the CD drive path is the current directory (pwd) in a UNIX terminal window. If it is, change (cd) to another directory.

• Check for sybhelp processes. If these processes exist, kill them using the UNIX kill command.

UNIX

DISPLAY environment variable not set correctly.

If you run Studio Installer and you get this error message:

The DISPLAY environment  variable is not set correctly. 

it means that the DISPLAY environment variable on the remote machine is not set correctly to display the Studio Installer user interface to your local machine.

To correct the problem, enter the following command at the UNIX prompt of the remote machine: For C shell:

setenv DISPLAY host_name:0.0

DISPLAY=host_name:0.0;  export DISPLAY

where host_name is the name of the machine where you want the Studio Installer interface to appear (that is, on your local machine).

UNIX

Windows NT

Jaguar Manager, create directory Yes/No buttons do not work.

Jaguar Manager does not accept invalid directory paths while exporting packages. Jaguar Manager asks you to create the directory, but neither the Yes nor the No buttons work. Select Cancel to back up one screen, then reenter the correct path.

UNIX

Windows NT

Sybase Central Java edition displays error message indicating a failed startup.

You may receive an error message stating that the product has failed to start when it has, indeed, started. Use the Refresh button to update the screen.

UNIX Windows NT

Valid SEEB license not found, or

SEEB server does not start

Check the error logs for related messages, and check to make sure the license file exists and that the license manager is running.

• Check the EAServer error log (%JAGUAR%\bin\srv.log on Windows NT, or $JAGUAR/bin/srv.log on UNIX) for license-related messages.

• Check the license daemon log (%SYBASE%\SYSAM-1_0\log\lmgrd.log on Windows NT or $SYBASE/SYSAM-1_0/log/lmgrd.log on UNIX) for license-related messages.

  Also, check the lmgrd.log file to see if the SySAM license manager is running. To do so, check the messages to make sure the license manager (lmgrd) and vendor daemon (SYBASE) started properly.

• Verify that the EAServer property com.sybase.seeb.LicensePath is set to the correct license.dat file. See "Modifying SEEB/EASService settings" in Chapter 2, "Getting Started" for information about SEEB/EASService properties.

  Also, verify that the license.dat file exists in the specified location.

UNIX

Windows NT

License Manager: Authorization code input error.

When you purchase EAServer and Enterprise Event Broker, you are issued a Sybase System Asset Management (SySAM) certificate, which includes the following information for each product:

• Order Number

• Feature Name

• Feature Count

• Software Version

• Authorization Code

This information is used by SySAM to build the license file. The license file is located in %SYBASE%\SYSAM-1_0\licenses\license.dat (Windows NT) and $SYBASE/SYSAM-1_0/licenses/license.dat (UNIX).

Here is a sample license file for Windows NT:

SERVER server1 ANY 4100VENDOR  SYBASE d:\sybase\SYSAM-1_0\bin

USE_SERVER

FEATURE  EAS_AE SYBASE 2.0 permanent xxxx 123456789123  ck=x

FEATURE  EEB_SERVER SYBASE 2.0 permanent xxxx 123456789123  ck=x

FEATURE  EEB_TIBCO SYBASE 2.0 permanent xxxx 123456789123  ck=x

FEATURE  EEB_MQSERIES SYBASE 2.0 permanent xxxx 123456789123  ck=x

• FEATURE NAME_NAME is the module or feature name, such as EAS_AE, EEB_SERVER, or EEB_TIBCO.

• 2.0 is the version number.

• The license type, permanent in the above example, is immediately followed by the Order Number, xxxx.

• 123456789123 is a 12-digit number representing the authorization code.

• ck is the maximum number of licenses that can be checked out.

If you make a mistake entering information, you can use a text editor to change the host name on the SERVER line and the daemon path on the VENDOR line.

If you make a mistake while entering any other information, do not edit the file, or you will invalidate the certificate and disable EAServer and Enterprise Event Broker services and components.

UNIX

Windows NT

Cannot connect to SEEB server,

Cannot log into SEEB server through SEEB Manager

Check the %JAGUAR%\bin\srv.log (Windows NT) or $JAGUAR/bin/srv.log (UNIX) to see if the SEEB/EASService started successfully and is running.

If SEEB/EASService stopped unexpectedly, it could indicate that the environment is not set up correctly or that the configuration failed. Review srv.log for possible errors encountered during start-up.