You can export your applications before you update installed
applications or before you migrate to a different version of the product.
Before you begin
The application whose contents you want to export is installed
on a server.
Avoid trouble: You can use the com.ibm.websphere.management.application.client.EnvEntry_processBindings
JVM custom property to specify how an environment entry value is handled
during an application deployment. However:
- If an application is deployed with com.ibm.websphere.management.application.client.EnvEntry_processBindings
enabled and is then exported to be deployed on a pre-Version 8.0 environment,
the environment entry value in the XML bindings are not recognized
by both the deployment and runtime environments.
- If an application is deployed with com.ibm.websphere.management.application.client.EnvEntry_processBindings
enabled and is then exported to be deployed on a Version 8.0 or 8.0.0.1
environment, the environment entry value in XML bindings are not be
recognized by the deployment environment but are recognized by the
runtime environment.
gotcha
About this task
Exporting applications enables you to back them up and
preserve their binding information.
Procedure
- Start the wsadmin scripting tool.
- Export applications.
- Export an enterprise application to a location of your choice,
for example:
- Export Data Definition Language (DDL) files in the enterprise
bean module of an application to a destination directory, for example:
Table 2. exportDDL command elements. Run
the exportDDL command to export DDL files.Element |
Description |
$ |
is a Jacl operator for substituting a variable
name with its value |
AdminApp |
is an object allowing application objects management |
exportDDL |
is an AdminApp command |
app1 |
is the name of the application
whose DDL files will be exported |
/mystuff |
is the name of the directory where
the DDL files export from the application |