Using an export configuration, you can export an entity, such as a Web application, or specify files to be synchronized to another server or to a cluster of servers. You can create an export configuration that contains specific deployment options for a server; for example, a server without a Web container, or a server that contains only an EJB container. You can also use export configurations to create a backup of a server or parts of a server.
An export configuration includes a set of EAServer files, Java classes, and entities, which are built into a .zip file. Entities include:
Application clients
Applications
Connectors modules
EJB modules
Web applications
Export configurations can also include information about cluster synchronization and dependencies to other export configurations.
You can define an export configuration that includes specific parts (functionality) of a server, which can be reused by other export configurations. For example, you might create one export configuration that defines a Web server and another that defines an EJB server. To create a Web server and an EJB server, a third export configuration could specify the first two export configurations as dependencies.
You can add classes in an export configuration by specifying either complete directories, or individual classes, including those within JAR files.
If you include an entity in an export configuration, all the files necessary for the entity are exported, including configuration files, property files, and classes.
You can add any file on the server’s file system to an export configuration. Files are stored in the export configuration .zip file in the same location where they exist in the current file system.
An export configuration can include dependencies to one or more other export configurations, which may contain classes, entities, and files.
