+

Search Tips   |   Advanced Search

Export applications using wsadmin.sh

We can export the applications before you update installed applications or before you migrate to a different version of the product.

The application whose contents you want to export is installed on a server.

We 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:

gotcha

Exporting applications allows us to back them up and preserve their binding information.


Tasks

  1. Start the wsadmin scripting tool.
  2. Export applications.

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

      • Jacl:

        $AdminApp export app1 /mystuff/exported.ear
        
      • Jython:

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

        Element Description
        $ 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:

      • Jacl:

        $AdminApp exportDDL app1 /mystuff
        
      • Jython:

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

      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

  • Update installed applications
  • wsadmin AdminApp
  • Commands for the AdminApp object