Sybase Technical Library - Product Manuals Home
[Search Forms] [Previous Section with Hits] [Next Section with Hits] [Clear Search] Expand Search

5. Configuring projects to
use EAServer services [Table of Contents] 7. Limitations

Release Bulletin EAServer Plug-in for JBuilder 10.0

[-] 6. Using a Sybase deployment descriptor file

6. Using a Sybase deployment descriptor file

EAServer allows you to set Sybase-specific properties in EJB-JAR, WAR, or EAR deployment archives. Sybase properties must be set in XML format, using the file named Sybase-easerver-config.xml. For more information on the format of this file, see the EAServer System Administration Guide.

The EAServer plug-in automatically adds an empty template version of Sybase-easerver-config.xml to every EAR, WAR, or EJB-JAR, RAR, and Application Client project that it is associated with. The template shows the correct format of the file, but sets no properties. You can edit the file in the JBuilder source editor or in the EAServer Plug-in deployment descriptor (DD) Editor.

The DD editor allows you to set the properties for each EAServer package, EJB component, Web application, and J2EE application that is created or updated in EAServer when the project is deployed. Properties are set in their raw format. For syntax information on these properties, see the appendix entitled "Repository Properties Reference" in the EAServer System Administration Guide.

After modifying the Sybase-easerver-config.xml file, you must rebuild your project before deploying to EAServer to ensure that the version in the archive file is current.


5. Configuring projects to
use EAServer services [Table of Contents] 7. Limitations