Switch to standard view 
  Sybase logo
 
 
 



Document ID: DC20211-01-0630-01

Last revised: November 2009

 


Accessing current release bulletin information

A more recent version of this release bulletin may be available on the Web. To check for critical product or document information added after the product release, use the Sybase® Product Manuals Web site.

Accessing release bulletins at the Sybase Product Manuals Web site

  1. Go to Product Manuals.

  2. Select a product and language and click Go.

  3. Select a product version from the Document Set list.

  4. Select the Release Bulletins link.

  5. From the list of individual documents, select the link to the release bulletin for your platform. You can either download the PDF version or browse the document online.

 


Product summary

Enclosed is Sybase EAServer version 6.3, which is compatible with this platform and operating system configuration:


Version contents

Enclosed is Sybase EAServer version 6.3, Build 63009. You may have a later build number if you have installed ESD patches for this release. If so, the cover letters provided with each patch contain the build number and additional documentation.

The EAServer 6.3 software is provided on a DVD.

Table 1 describes the products that EAServer 6.3 supports.

Table 1: Product support

Product

Supported versions/builds

Adaptive Server® Enterprise

12.5.x and 15.0.x

C++ compiler

HP aC++ A.05.50

Eclipse

3.4.2

Java Development Kits (JDK):

1.5

1.6

Versions:

1.5.0_16

1.6.0_04

Jetty

6.1.14

Oracle client

9.2.0.1 and 10g

Apache Web server redirector plug-in

2.0.55 and 2.2.11

SQL Anywhere®

11.0

Web browsers

Internet Explorer 6.0

Firefox 3.0


Required system patches

Before installing EAServer on HP Itanium, verify that you have the required HP patches. EAServer does not function correctly if all required patches are not installed. See the HP Patch Information page.

You can run the HPjconfig tool to verify whether all required patches have been installed on your machine. HPjconfig reports what patches are required as well as the kernel settings required for Java. You can download HPjconfig from the HP Web site.

 


Special installation instructions

The EAServer 6.2 Installation Guide of your platform describes how to install the software.


Mounting the CD

You must manually mount the CD. To do so, use the HP SAM utility. See your HP documentation for more information.

 


Special upgrade instructions

You can install EAServer 6.3 as a new installation, or as an upgrade to an EAServer 6.x installation.

Before you upgrade from EAServer 6.2 to EAServer 6.3, rename _shared.properties to shared.properties in <6.2_installed_directory>/ Repository/Instance/com/sybase/djc/security/DataProtection. This ensures that the keystore, truststore, and datasource passwords are all set correctly.

The EAServer migration tool enables you to migrate a subset of entity types from a 5.x repository to the 6.3 repository, saving time by scanning only those entity types that you require. For details, see:

“Migration tool issue” in this release bulletin describes problem that is known to occur during migration.

 


New features in this version

EAServer 6.3 includes these new features:


Creating EAServer as an application server in Lomboz

Creating EAServer as an application server in Lomboz

  1. Change to $EAServer_Home/../Shared/eclipse_342/eclipse/ and execute starteclipse.sh.

  2. In Eclipse, open the Servers view:

    1. Select Window | Show View | Other.

    2. In the Show View dialog box, choose Servers under the Server category.

  3. Right-click the Servers view and select New | Server to add a new server runtime.

  4. In the New Server - Define a New Server dialog box:

    1. Enter the server’s host name. For example, zeus-desktop.

    2. Expand the Sybase folder and select EAServer 6.0 as its server type.

    3. Click Next.

  5. In the New Server - New Server 6.0 Runtime dialog box, enter:

    • EAServer6 location – EAServer_Home

    • EAServer client jar – EAServer_Home/lib/eas-client-15.jar

    • Additional client jar – EAServer_Home/lib/servlet-rt.jar

    Click Next.

  6. Complete these fields using your EAServer installation setting details:

    • HTTP port

    • IIOP host

    • IIOP port

    • User ID

    • Password

    Click Next. The Add and Remove Projects dialog box appears.

  7. Click Next in the Add and Remove Projects dialog box.

  8. Click Finish.

The EAServer 6 server runtime in Eclipse has been added successfully. Right-click the server and select Start item. In the Console view, a message will display to indicate that EAServer 6 server is able to start successfully.


Setting up BLOB messages

This section provides information about creating, sending, and receiving BLOB messages.

 


Known issues

This section describes known problems in this version of EAServer.


Upgrading of Jetty

[CR #569870] Jetty 6.1.14 has fixed an issue (JETTY-635) that may result in an EAServer test failure when you upgrade Jetty 6.1.5 to Jetty 6.1.14. If you are using jspParamForwardTest code in Jetty 6.1.14 in EAServer, update the code based on Jetty functional specification. For details, see the Jetty documentation.


Incorrect decoding of Chinese characters

[CR #566763] When you decode Chinese characters in a Java Server Page (JSP), there is a redundant “+” sign in the result.

Workaround: This is a known issue in Jetty which is scheduled to be addressed in the next release. For details, see the Jetty documentation.


Installer shortcut keys do not work

[CR #543604] After launching the installer, use the shortcut key–Alt+N to proceed with the installation. Select the country to display the license agreement. After this step, the shortcut keys do not work.

Workaround: Use the mouse to select options in the installation wizard.


Getting OracleConnection in EAServer

[CR #538605] EAServer supports OracleConnection and its update batching mechanism in a multithreaded environment with high concurrency. For example, after obtaining the container-managed data source connection, c, the API at the client side calls the getRealConnection method, as follows:

OracleConnection oc = (OracleConnection)((com.sybase.djc.sql.ConnectionWrapper)c).getRealConnection();


Cannot access the Management Console

[CR #537700] If the EAServer installed path includes Chinese characters, you cannot access the Management Console.

Workaround: Before starting the server, execute:

 $EAS63/bin/configure.sh disable-builtin-jsf


Ant configuration fails after deploying EJB file

[CR #498829] You cannot complete the Ant configuration after you have deployed an EJB-JAR file in Eclipse plug-in. No information appears when you click Details in the Progress Information window.

Workaround: Restart EAServer after deploying a new EJB-JAR file.


Server may stop responding under heavy load

[CR #479620] During stress testing on an HP-Itanium machine with low memory and with a large number of client connections, the server stops responding. For example, if you use 1GB of memory for 1,000 client connections on an HP-Itanium machine, the server may stop responding.

Workaround: Reduce the number of client connections. For example, reduce the number of client connections from 1,000 to 50.


ODBC and SQL Anywhere data source conflict

[CR #479277] If both JCM_Odbc and Sybase_ASA database driver libraries are loaded at the same time, symbol-resolution issues occur. If you must use both database types, configure the ASA data sources to use the SQL Anywhere 10 database type, which use a jConnect™ for JDBC driver™.


sun.jdbc.odbc.JdbcOdbcDriver not supported

[CR #479276] This version of EAServer does not support the sun.jdbc.odbc.JdbcOdbcDriver database driver.


Obsolete HTTP server properties

[CR #452369] Beginning in version 6.2, EAServer no longer supports these HTTP properties:

Instead, EAServer reads these HTTP header fields:

If you call any of the HttpRequest methods, getServerName, getServerPort, or getProtocol, the values are retrieved from the browser. This is the same behavior that was achieved by setting httpGetServerInfoFrom to “source” in versions of EAServer earlier than 6.3.


Security risk

[CR #434293] Do not use HTTP to connect to the Management Console; the administrative user ID and password are passed in plain-text format during the login process, thus posing a security risk.

Workaround: Use HTTPS to log in to the Management Console. To use HTTPS, you first need to obtain a certificate. If you use the sample (test) certificate that is included with EAServer, anyone with EAServer 6.0 has access to your private (test) key. Therefore, Sybase recommends that you use your own certificate.


Configuring a database type

If you specify values for both the dataSourceClass and driverClass properties when you configure a database type, the system uses the class defined by dataSourceClass, and ignores these properties:


SQL Anywhere database issues

When you upgrade to EAServer 6.3, Adaptive Server® Anywhere (ASA) version 9.0.2 is upgraded to version 11.0, and the name of the database server changes from ASA to SQL Anywhere.


ODBC driver version

[CR #470030] The ODBC driver that you use with EAServer must be either the driver packaged with EAServer or a later version.


Setting the databaseURL property

[CR #467797] If the value of the databaseURL property is “[default]” when you create a new data source for either a Sybase_ASA or SQL_Anywhere database type, attempts to ping the database fail and this message displays:

Ping failed due to exception: Use of the JIT driver
wrapper for SQL Anywhere requires use of the underlying
IAnywhere JDBC/ODBC driver - please reconfigure data
source 'asa10demo' to include the odbcDataSource property. Please see the server log file for additional details.

Workaround: Set the databaseURL property to “jdbc:odbc:driver=EAS 6.0 ASA;uid=dba;pwd=sql;eng=<asa10_db_alias>,” where <asa10_db_alias> is the value of the -n parameter that is used when starting the database.


FIPS support


Apache redirector does not support FIPS

[CR #475216] If you are using the Apache Web server redirector plug-in, FIPS is not supported.


FIPS not supported for CORBA/C++ clients

[CR #477250] FIPS is not supported for C++ client connections to EAServer.


Adaptive Server Enterprise 12.5.x

[CR #447543] If you are using Adaptive Server Enterprise (ASE) version 12.5.x with EAServer, you may see this error:

"SELECT INTO command not allowed within multi-statement transaction"

Workaround: On the machine where Adaptive Server is installed, run:

 $DJC_HOME/extras/jconnect-6.05/sp/sql_server12.5.sql


Migration tool issue

[CR #437181] When you are migrating EAServer entities from version 5.x to version 6.3, the migrate tool does not migrate sql.ini content for Open Client™ Client-Library connections.

Workaround: Manually copy Open Client Client-Library connection information from the 5.x version of sql.ini to the 6.3 version.


Web Services Toolkit issues


Refreshing Web services collection causes an OutofMemory error

[CR #494522] When you refresh a Web services collection using the Refresh button in the Eclipse plug-in, or using jagtool, you see an OutofMemory error.

Workaround: To reduce memory leakage:

  1. Log in to the Management Console.

  2. Select Servers | <name of your instance>.

  3. In the right pane, select the Module tab.

  4. Under the User Start Modules, click Select and clear the Ejbjar-datawindow check box.


Datatype mapping

[CR #449109] In EAServer 6.0, the Web services datatype-mapping version is set to 1.3, so xsd:short may be mapped to either the short or unsignedByte Java datatype. This causes some Web service tests to fail.

Workaround: Set the datatype-mapping version to 1.2, so xsd:short will always be mapped to the short datatype:

  1. Start EAServer, and connect to the server using the Management Console.

  2. Expand the Servers folder, and select the server.

  3. On the General tab, find the WebServices Type Mapping Version field. The default value is 1.3.

  4. Change the value to 1.2, and click Save.


Activating and deactivating Web services

[CR #448806] The wstool commands for activating and deactivating Web services, wstool activate and wstool deactivate, do not work.


Apache Scout

[CR #448380] The Apache Scout client method BusinessLifeCycleManager.saveAssociations fails, and a null pointer exception is returned.


Web services display in random order

[CR #422161] Selecting the Management Console options to display Web services either alphabetically or in descending order by date fail. Web services display in random order.


Miscellaneous issues


Permission required to use JIT data sources

[CR #465348] You can use a JIT (just-in-time) data source to access a database only if you have permission to create tables in the database.


SSLServiceProvider.getGlobalProperty

[CR #436638] The SSLServiceProvider method for checking the status of FIPS, SSLServiceProvider.getGlobalProperty(“fips140”), has not been implemented in EAServer 6.3.

 


Documentation updates and clarifications

This section contains updates and clarifications for the EAServer product manuals.


Automated Configuration Guide


Chapter 2, “Ant-Based Configuration”


Embedding configuration scripts in J2EE archives

[CR #574077] The text in the second paragraph of the “Embedding configuration scripts in J2EE archives” section is incorrect. The corrected text is:

Place the configuration file in the archive’s META-INF subdirectory, using the file name that matches the archive type, as listed in the second column of Table 2-3. For sybase-webapp-config.xml, place this configuration file in the WEB-INF subdirectory.


Predefined configuration scripts

[CR #581809] EAServer 6.x supports JavaServer Faces (JSF) 1.1. By default, the JSF 1.1 classes in EAServer are enabled and loaded at EAServer start-up. Table 2-4 of the “Predefined configuration scripts” in Chapter 2, “Ant-Based Configuration” in the Automated Configuration Guide does not include the two JSF predefined scripts, which allow you to enable and disable JSF classes. The two missing scripts are:

Name

Configures defaults for

disable-builtin-jsf.xml

Disables the EAServer built-in JSF versions and classes.

enable-builtin-jsf.xml

Enables the EAServer built-in JSF versions and classes.

To disable JSF 1.1 these classes, use:

 $EAS6/bin/configure.sh disable-builtin-jsf

To enable JSF 1.1 these classes, use:

 $EAS6/bin/configure.sh enable-builtin-jsf


Chapter 3, “Using Scheduled Tasks”

[CR #477285] “Predefined tasks” does not include task, which you can schedule to remove unwanted PowerBuilder® cookies from your machine.


Chapter 4, “Creating Service Components”

[CR #500334] In Table 4-1 of “Service component entity properties,” the Component property that specifies how to define the remote interface for a service component is incorrect. The corrected text is:

ejb.components.mypackage.MyComponentRemote

or, for a local interface for a service component:

ejb.components.mypackage.MyComponentLocal


Writing a Java class as a service component

This procedure shows how to write a Java class as a service component using these methods:

  1. Use a text editor to write a Java file that includes the three Java methods. For example:

    package serviceTest;
    public class oneService {
        boolean bstop = false;
        public void start()
    {
                System.out.println("oneService start!");
                bstop = false;
    }
    
        public void run()
        {
             while(!bstop)
             {
                    System.out.println("oneService runing...");
                     try {
                             Thread.sleep(1000);
                  }catch (InterruptedException e) { 
                   }
             }
        }
    
         public void stop()
         {
              bstop = true;
              System.out.println("oneService stop!");
         }
    }
    
  2. Save and compile this Java file to a class file.

  3. Create a JAR file for the class file.

  4. Place the JAR file in $EAServer/lib/ext/.

  5. Log in to the Management Console.

  6. Select the Service Components folder, right-click, and select Add.

    1. Type the name of the service component, for example, oneservice.

    2. Choose Finish.

  7. Select oneservice from the Service Components subfolders.

    1. Type the name of the component in the Component property field on the right side of the Management Console window. For example, serviceTest.oneService.

    2. Select the Start Before Binding check box.

    3. Select Apply to save the new settings.

  8. Select the Servers folder.

    1. Select the server where EAServer is running. For example, zeus-deskwxp.

    2. Select the Services tab.

    3. Select the service component that you have just created, for example, oneservice from the list.

    4. Select Apply to save the new settings.

  9. Restart EAServer.

When you run the service component, the log file or console displays these messages:

oneService start!
oneService runing...”,

If you stop EAServer, the log file or console displays this message:

oneService stop!”


Chapter 6, “Using jagtool and jagant”


Deploying applications

[CR #481055] When you use jagtool to deploy a self-contained application, you can configure the application to use all the classes from the internal class loader by setting the disableResolveFirstBySystem property to true. For example:

jagtool.sh deploy -type war -disableResolveFirstBySystem true foo.war


Obsolete jagtool commands

[CR #465796 and #447432] These jagtool commands are documented in the Automated Configuration Guide, but the commands are not supported in EAServer 6.0 and later:


Generating stubs

[CR #462838] To generate stubs for a package or component, you can use the jagtool gen_stubs command. See the Automated Configuration Guide for more information about jagtool commands.

Syntax

gen_stubs [-javastubs true|false] [-cppstubs true|false]  
[-javastubjarname file-name] [-javastubcodebase path]  
[-cppstubcodebase path] [-compilejavastubs true|false] 
[-verbose true|false] entity

Option

Description

javastubs

Whether to generate Java stubs; the default is true.

cppstubs

Whether to generate C++ stubs; the default is true.

javastubjarname

If specified, the Java stubs are placed in a JAR file of the specified name. The file name must include the full path.

If not specified, Java files are generated (the default).

javastubcodebase

The location of the code base for Java stubs; the default is $DJC_HOME/genfiles/java/stubs.

cppstubcodebase

The location of the code base for C++ stubs; the default is $DJC_HOME/include.

compilejavastubs

Whether to compile the generated Java stubs; the default is true.

verbose

Whether to produce verbose output while generating stubs; the default is false.

entity

The name of the entity for which stubs are being generated, in the form EntityType:EntityName, where EntityType is either “Package” or “Component.”

Return values

Return value

Indicates

0

The command ran successfully; the result is true/success.

2

The command did not run successfully; an exception was thrown.


CORBA Components Guide


Chapter 4, “Managing CORBA Packages and Components”

[CR #437366] You cannot use hyphens (“-”) in CORBA-component package names. CORBA-component packages are those that contain CORBA/C++, CORBA/Java, or PowerBuilder components.


Chapter 5, “Developing and Deploying PowerBuilder Components”

[CR #405138] You cannot use a hyphen (“-”) in the name of a PowerBuilder nonvisual object (NVO) method or variable. EAServer wraps NVOs as EJBs, and Java does not support method or variable names that contain hyphens.


Accessing data sources

[CR #533120] When accessing these predefined EAServer data sources from PowerBuilder components, set the default transaction object (SQLCA) to use the appropriate database type as shown in Table 2.

Table 2: Database type

Database type

Description

JCM_Sybase

For ASE database:

sqlca.dbms="SYJ"

JCM_Oracle or JCM_Oracle_Unicode

Oracle database which corresponds to the EAServer 5.x Oracle Call Interface (OCI) 9 and OCI10 native connection caches.

sqlca.dbms="O90", or

sqlca.dbms="O10"

JCM_Odbc or JCM_Odbc_Unicode

For any databases using ODBC driver:

sqlca.dbms="ODBC"

JCM_non-JCM JDBC-compliant

For any non-JCM JDBC-compliant database type:

sqlca.dbms ="JDBC"


Implementing method-level security for PowerBuilder components

[CR #488947] You can implement method-level security after deploying PowerBuilder components. To implement method-level security for a PowerBuilder component:

  1. Add two users. For example, “Pass” and “Fail”.

  2. Change the role of the user “Pass” to admin-role. You can also define and use your role.

  3. Deploy the final_test NVO into EAServer from PowerBuilder.

  4. Deploy final_test.jar into EAServer from Web console or command line.

  5. Run PowerBuilder client and click the Pass and Fail buttons.

  6. Modify the $EAServer/config/ejbjar-final_test-user.xml file, as follows:

    <setProperties component="ejb.components.final_test.n_easerver_5_componentRemote">
        <transaction retry="false"/>
           <copyValues enable="false"/>
               <accessControl 
                  type="default"
                 auditDeny="true"
                auditPermit="true" 
           />
    <permitAccess method="of_return_name(String)" roles="admin-role" ports="${ejb.allowedPorts}"/>
    </setProperties>
    
  7. Run the Ant Refresh followed by the Run Ant Recompile from the Management Console.

  8. Run the PowerBuilder client.

    If the implementation is successful, the Pass button works.

    If you click Fail, the NO_PERMISSION exception occurs.


Enterprise JavaBeans User’s Guide


Chapter 3, “Developing EJB Clients”

[CR #498818] In the “Client runtime requirements” section, includes this:

When using JDK 1.6, add this option in $JAVA_HOME/bin/java:

-Dsun.lang.ClassLoader.allowArraySyntax=true

This is because the JDK 1.6 on the client side provides the allowArraySyntax option to convert array from the server result data.

If clients run with a JRE, instead of a full JDK, you can prevent the client from trying to generate and compile stubs by setting the system property djc.allowRuntimeCompile to false for the Java command that starts the client application.


Chapter 4, “Creating Application Clients”

[CR #472302] In the section “Starting the runtime container,” this example for starting an application client’s runtime container is incorrect:

runclient.sh -client my_appclient -login true

The correct syntax is:

run-appclient.sh -client my_appclient -login true


Installation Guide


Chapter 2, “Installing EAServer”

[CR #587037] The following note should be included in step 5 of the “Adding components” procedure in “Reinstalling or adding components” in Chapter 2, “Installing EAServer:”

Note:You cannot start the license server until there is at least one valid served license installed in the licenses directory: $SYBASE/sysam-2.1/licenses.

For an unserved license, place the license file in $SYBASE/EAServer/licenses.


New Features Guide

[CR #493619] The introduction in the “.NET client support” section in the EAServer 6.1 New Features Guide is incorrect. The corrected introduction is:

EAServer 6.1 includes .NET client support, and enables IIOP/IIOPS communication between .NET and J2EE distributed objects in EAServer.


Security Administration and Programming Guide


Chapter 6, “Using TLS and FIPS”

[CR #474337] The section “SSL/TLS and FIPS Support” describes how to enable FIPS support, “Enabling FIPS using the Certicom Java libraries.” Step 2 says to set the com.sybase.ejb.fips connection property to specify FIPS usage, but fails to specify the value. To enable FIPS support, set the value of com.sybase.ejb.fips to true; to disable, set the value to false.


Chapter 11, “Managing Keys and Certificates”

[CR #535090] The “Set-certificate” section of Chapter 11, “Managing Keys and Certificates” does not provide sufficient information. You must run a setup procedure before you can use the set-certificate script.


System Administration Guide


Chapter 3, “Creating and Configuring Servers”


Hiding the default HTTP response header

[CR #546416] By default, EAServer 6.x sends the default HTTP response header to the HTTP client. For example, HTTP/1.1......Server: Jetty(EAServer/6.2.0.12 Build 62012. This may expose the Web server identity to all HTTP clients. To hide the default HTTP response header:

  1. Log in to the Management Console.

  2. Select your Server instance.

  3. Select the HTTP tab.

  4. Unselect Send the Server Version in HTTP header property.

  5. Restart EAServer.


Adding and configuring service components

[CR #500334] The configuration property name for the Component property in Table 3-7 is incorrect. The correct property name is serviceComponents, as indicated below:

Property

Description

Component

The name of the component that implements the service.

For a user-defined service component, enter either:

  • The class name of a simple Java class (must be in the server class path), or

  • The fully-qualified name of an EJB local or remote interface; for example,

    ejb.components.mypackage.MyCompLocal or

    ejb.components.mypackage.MyCompRemote.

The configuration property name is serviceComponents.


Adding and configuring listeners

[CR #549163] To prevent EAServer from trying to allocate too many Windows handles, Sybase recommends that you set the number of listener connections to a maximum of 1,000. If you are using a 64-bit JVM, EAServer can support about 5,000 connections instead of 1,000. You can set this configuration using the Management Console. On the listener’s General tab, set the Maximum Number of Threads listener property to 1,000.


Enabling password sharing

[CR #487210] By default, multiple users can start EAServer. However, to allow single user to start EAServer, configure EAServer with the shared-data-protection-off option. For example:

cd $EAServer/bin
configure.sh shared-data-protection-off

To allow multiple users to start EAServer, use the shared-data-protection-on option. For example:

cd $EAServer/bin
configure.sh shared-data-protection-on


Configuring system logging

[CR #473658] “Configuring system logging” describes how to customize the location of the system log files, but the name of the variable (DJC_JVM_ARGS) is incorrect. The correct variable is DJC_JVM_USER_ARGS; for example:

set DJC_JVM_USER_ARGS=$DJC_JVM_USER_ARGS -Ddjc.logFile=/myserver/myserver.log 
-Ddjc.logFileMaxSize=5m -Ddjc.logFileRotation=true

Note:If you customize the location of the system log files, only the HTTP log is rotated; the server log is not.


Chapter 4, “Database Access”

The section that describes how to configure a database type fails to explain that if you define both a dataSourceClass and a driverClass, EAServer uses only the dataSourceClass value—see “Configuring a database type” in this release bulletin.


Configuring data sources

[CR #531900] When using servers in a cluster, make sure these predefined data sources are all connected to the same database:

You can change the data sources using the Management Console.


Chapter 11, “Runtime Monitoring”

[CR #546885] The “Monitoring Web application and EJB statistics” section of Chapter 11, “Runtime Monitoring,” provides information about viewing statistics for Web applications and EJBs by accessing the Statistics node beneath an individual entity. However, this information is incorrect. There is no Statistics node available in the selected Web application component and EJB component.


Chapter 12, “Command Line Tools”

deploy

[CR #481055] When you deploy a self-contained application, you can configure the application to use all the classes from the internal class loader by setting the disableResolveFirstBySystem property to true. For example:

deploy.sh -disableResolveFirstBySystem foo.war

[CR #475511] EAServer 6.3 does not support the -jsr154filter option for the deploy.sh command line tool. -jsr154filter may be supported in a later version of EAServer.


Chapter 13, “JNI Compiler”

[CR #472818] Before calling a generated proxy class, standalone clients must call either:


Chapter 14, “Systems Management”

[CR #437261] EAServer supports Simple Network Management Protocol (SNMP) features that conform to the Java Specification Request JSR 77. The status of a server and its components are reported as Management Information Base objects, which can be polled, and can also be reported as SNMP traps.


Troubleshooting Guide


Chapter 1, “Monitoring Techniques”

This example shows how to configure the log4j.properties file.

Configuring Log4j

  1. Use a text editor to create a log4j.properties file.

    # Set root category priority to INFO and its only appender to CONSOLE.
    #log4j.rootCategory=FATAL, CONSOLE
    log4j.rootCategory=DEBUG, LOGFILE
    
    # Set the enterprise logger category to FATAL and its only appender to CONSOLE.
    # log4j.logger.org.apache.axis.enterprise=DEBUG, LOGFILE
    
    # CONSOLE is set to be a ConsoleAppender using a PatternLayout.
    log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
    log4j.appender.CONSOLE.Threshold=DEBUG
    log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
    log4j.appender.CONSOLE.layout.ConversionPattern=- %m%n
    
    # LOGFILE is set to be a File appender using a PatternLayout.
    log4j.appender.LOGFILE=org.apache.log4j.FileAppender
    log4j.appender.LOGFILE.File=<install_directory>/axisserver.log
    log4j.appender.LOGFILE.Append=true
    log4j.appender.LOGFILE.Threshold=DEBUG
    log4j.appender.LOGFILE.layout=org.apache.log4j.PatternLayout
    log4j.appender.LOGFILE.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n
    
  2. Put the log4j.properties file into $EAServer_Home/lib.

  3. Change to $EAServer_Home/bin and execute:

    run-server -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger
    
  4. Write a class named “Hello”:

    package sayhello;
    
    public class Hello {
    public String hello() {
          return "hello";
        }
    }
    
  5. Use Sybase Web Services Toolkit to deploy this class as a Web service and generate a client.

  6. Run Hello_ServiceTestClient.java.

  7. Find the log file in <install_directory>\aixsserver.log and view the contents which should look similar to:

    953  [main] DEBUG org.apache.axis.i18n.ProjectResourceBundle  -
    loadBundle: Ignoring MissingResourceException: Can't find bundle for
    base name org.apache.axis.resource, locale zh_CN
    953  [main] DEBUG org.apache.axis.i18n.ProjectResourceBundle  -
    Created org.apache.axis.i18n.resource, linked to parent null
    953  [main] DEBUG org.apache.axis.i18n.ProjectResourceBundle  -
    getBundle(org.apache.axis,org.apache.axis.utils,resource,null,...)
    953  [main] DEBUG org.apache.axis.i18n.ProjectResourceBundle  -
    loadBundle: Ignoring MissingResourceException: Can't find bundle for
    base name org.apache.axis.utils.resource, locale zh_CN
    953  [main] DEBUG org.apache.axis.i18n.ProjectResourceBundle  -
    loadBundle: Ignoring MissingResourceException: Can't find bundle for
    base name org.apache.axis.resource, locale zh_CN
    953  [main] DEBUG org.apache.axis.i18n.ProjectResourceBundle  - Root
    package not found, cross link to org.apache.axis.i18n.resource
    953  [main] DEBUG org.apache.axis.i18n.ProjectResourceBundle  - Root
    package not found, cross link to org.apache.axis.i18n.resource
    953  [main] DEBUG org.apache.axis.i18n.ProjectResourceBundle  -
    org.apache.axis.i18n.resource::handleGetObject(engineFactory)
    1047 [main] DEBUG org.apache.axis.i18n.ProjectResourceBundle  -
    org.apache.axis.i18n.resource::handleGetObject(attachEnabled)
    1063 [main] DEBUG org.apache.axis.i18n.ProjectResourceBundle  -
    org.apache.axis.i18n.resource::handleGetObject(oddDigits00)
    


Web Services Toolkit User’s Guide


Chapter 9, “Using wstool and wstant”

[CR #464242] The Ant build example for the exposeComponent command is incorrect:

<wst_antTask command="exposeComponent" entity="component:myPackage/myComponent"/>

The correct command is:

<wst_antTask command="exposeComponent"  entity="myPackage/myComponent"/>

 


Technical support

Each Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support. If you have any questions about this installation or if you need assistance during the installation process, ask the designated person to contact Sybase Technical Support or the Sybase subsidiary in your area.

 


Other sources of information

Use the Sybase Getting Started CD, the SyBooks™ CD, and the Sybase Product Manuals Web site to learn more about your product:


Sybase certifications on the Web

Technical documentation at the Sybase Web site is updated frequently.

Finding the latest information on product certifications

  1. Point your Web browser to Technical Documents.

  2. Click Partner Certification Report.

  3. In the Partner Certification Report filter select a product, platform, and timeframe and then click Go.

  4. Click a Partner Certification Report title to display the report.

Finding the latest information on component certifications

  1. Point your Web browser to Availability and Certification Reports.

  2. Either select the product family and product under Search by Base Product; or select the platform and product under Search by Platform.

  3. Select Search to display the availability and certification report for the selection.

Creating a personalized view of the Sybase Web site (including support pages)

Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase Web pages.

  1. Point your Web browser to Technical Documents.

  2. Click MySybase and create a MySybase profile.


Sybase EBFs and software maintenance

Finding the latest information on EBFs and software maintenance

  1. Point your Web browser to the Sybase Support Page.

  2. Select EBFs/Maintenance. If prompted, enter your MySybase user name and password.

  3. Select a product.

  4. Specify a time frame and click Go. A list of EBF/Maintenance releases is displayed.

    Padlock icons indicate that you do not have download authorization for certain EBF/Maintenance releases because you are not registered as a Technical Support Contact. If you have not registered, but have valid information provided by your Sybase representative or through your support contract, click Edit Roles to add the “Technical Support Contact” role to your MySybase profile.

  5. Click the Info icon to display the EBF/Maintenance report, or click the product description to download the software.

 


Accessibility features

This document is available in an HTML version that is specialized for accessibility. You can navigate the HTML with an adaptive technology such as a screen reader, or view it with a screen enlarger.

EAServer and the HTML documentation have been tested for compliance with U.S. government Section 508 Accessibility requirements. Documents that comply with Section 508 generally also meet non-U.S. accessibility guidelines, such as the World Wide Web Consortium (W3C) guidelines for Web sites.

The online help for this product is also provided in HTML, which you can navigate using a screen reader.

For information on using EAServer without a mouse, see “Keyboard navigation” in Chapter 2, “Management Console Overview,” in the EAServer System Administration Guide.

Note:You might need to configure your accessibility tool for optimal use. Some screen readers pronounce text based on its case; for example, they pronounce ALL UPPERCASE TEXT as initials, and MixedCase Text as words. You might find it helpful to configure your tool to announce syntax conventions. Consult the documentation for your tool.

For information about how Sybase supports accessibility, see Sybase Accessibility. The Sybase Accessibility site includes links to information on Section 508 and W3C standards.

For a Section 508 compliance statement for EAServer, go to Voluntary Product Assessments, and click the link for EAServer.



Back to Top
© Copyright 2010, Sybase Inc.