Exporting applications using scripting

You can export your applications before you update installed applications or before you migrate to a different version of the WebSphere Application Server product.

Before starting this task, the wsadmin tool must be running. See the Starting the wsadmin scripting client article for more information.

Exporting applications enables you to back them up and preserve their binding information.

(dependent on configuration)

Export an enterprise application to a location of your choice, for example:

Using Jacl:

$AdminApp export app1 C:/mystuff/exported.ear

Using Jython:

AdminApp.export('app1', 'C:/mystuff/exported.ear')

where:

$ is a Jacl operator for substituting a variable name with its value
AdminApp is an object allowing application objects management
export is an AdminApp command
app1 is the name of the application that will be exported
/mystuff/exported.ear is the name of the file where the exported application will be stored

Export Data Definition Language (DDL) files in the enterprise bean module of an application to a destination directory, for example:

Using Jacl:
```
$AdminApp exportDDL app1 C:/mystuff
```

Using Jython:

AdminApp.exportDDL('app1', 'C:/mystuff')

where:

$ 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

Related concepts
AdminApp object for scripted administration

Related reference
Commands for the AdminApp object

$	is a Jacl operator for substituting a variable name with its value
AdminApp	is an object allowing application objects management
export	is an AdminApp command
app1	is the name of the application that will be exported
/mystuff/exported.ear	is the name of the file where the exported application will be stored