For all platforms, verify:
You can ping the data source.
The deployment properties of the application components are correct. See Chapter 9, “Importing Application Components,” in the EAServer System Administration Guide.
Java classes are loaded from the correct locations. See Chapter 10, “Configuring Java Class Loaders,” in the EAServer System Administration Guide.
You can find all occurrences of a class in BOOTCLASSPATH and CLASSPATH using the ClassSearch utility, which is described in white paper #1017251: ClassSearch Utility.
Maximum values and limits are set appropriately for the production environment:
EAServer properties (data sources, sessions, threads, and so on)
JVM
The listener ports are not already in use and that no two EAServer listeners are defined to use the same port number.
The versions of the PBVM on the server and the PowerBuilder client match. Check all files, especially libjcc.dll, which may be shipped with both PowerBuilder and EAServer releases, ESDs, and EBFs.
Multiple versions of libjcc.dll
EAServer
includes libjcc.dll in the EAServer lib directory.
PowerBuilder may include the file as well, in %SYBASE_SHARED%/PowerBuilder,
since this file is needed on PowerBuilder client installations.
Sybase recommends that you not copy the libjcc.dll that
is provided with PowerBuilder to the server as part of a PBVM setup.
Even if you have the latest PowerBuilder patch, use the EAServer libjcc.dll.
Problems can result if either the EAServer application server or the Management Console uses a different version than its own (such as the one provided with PowerBuilder). This used to be a problem when EAServer looked at the system path variable. However, now that EAServer sets up the path in the start-server script, the problem occurs only when users modify either the script or environment.
Verify that LD_LIBRARY_PATH includes:
$DJC_HOME/lib:$ASANY9/lib:$DJC_HOME/bin: $DJC_HOME/intersolv/lib:$DJC_HOME/lib/debug: $LD_LIBRARY_PATH
Add the location of the X-Window xterm utility to your PATH variable. For example:
set path = ($path /usr/local/bin/)
If you cannot start the server, verify that these environment variables are properly set:
PATH – must include $DJC_HOME/bin.
DJC_HOME – specifies the location of the EAServer installation directory.
ASANY9 – specifies the location of the Adaptive Server Anywhere directory.
If the PATH or CLASSPATH settings do not include the required directories, or if the settings are too long, you may experience problems.
Look at %DJC_HOME%\bin\djc-setenv.bat and %DJC_HOME%\bin\run-server.bat to investigate problems with either the PATH or the CLASSPATH variable.
