You can embed XML configuration files in J2EE archives to configure EAServer properties that can not be specified by the standard deployment descriptor properties. “XML configuration files” describes the format of these files.
XML files for EAServer must be named sybase-easerver-config.xml and placed in the META-INF directory. Whenever you import a J2EE JAR, WAR, EAR, or RAR file with EAServer Manager, jagtool, or jagant, the importer looks for this file and applies the changes specified within it.
When you export a J2EE archive, an XML configuration file is created with entries to configure the entities defined within the archive, as follows:
For a Web application (WAR) archive, the XML file updates properties for the Web application, and any filters, servlets, and JSPs in the Web application.
For EJB components in a package (exported as an EJB-JAR file), the XML file updates properties for the package and each EJB component inside it.
For a J2EE connector (RAR) archive, the XML file updates properties for the connector, and creates any managed connection factories which exist for the Connector.
For an application client archive, the XML file updates properties for the application client.
For an application archive (EAR file), the XML file updates properties for the application. The EJB components, connectors, and application clients in the application are configured by separate XML files associated with the nested archives created for these entities.
To export an archive that does not contain an XML configuration file, deselect the “Export with EAServer XML Configuration File” option in the export wizard.
To create XML configuration files without exporting an archive, you can use the jagtool exportconfig command. See Chapter 12, “Using jagtool and jagant,” for details.
