Managing administrative console applications using wsadmin scripting

Use the Jython or Jacl scripting languages to deploy or remove portlet-based administrative console applications.

• Deploy a portlet-based console application into the EAR file.
  1. Start the wsadmin scripting tool.
  2. Deploy a portlet-based console application into the EAR file.

     To use the existing listener port instead of using or creating a new activation specification, determine whether the EJB JAR version is earlier than 2.1. The system automatically creates and uses an activation specification when you specify the -usedefaultbindings option to deploy an application. If an activation specification exists, the system ignores the listener port, and instead uses the activation specification. To deploy an application with an EJB JAR version greater than or equal to 2.1 using the defined listener ports instead of a new activation specification, set the com.ibm.websphere.management.application.dfltbndng.mdb.preferexisting system property to true in the wsadmin.properties file in the properties directory of the profile of interest.

     • Using Jython:

       AdminApp.update('isclite', 'modulefile', '[-operation add -contents 
       /WebSphere/AppServer/systemApps/isclite.ear/upzippedWarName 
       -contenturi upzippedWARName -usedefaultbindings -contextroot contextroot]')

     • Using Jacl:

       $AdminApp update isclite modulefile {-operation add -contents 
       /WebSphere/AppServer/systemApps/isclite.ear/upzippedWarName 
       -contenturi upzippedWARName -usedefaultbindings -contextroot contextroot}

  3. Save your configuration changes.
     Use the following command example to save your configuration changes:

     AdminConfig.save()

• Remove a portlet-based web application archive (WAR) file.
  1. Start the wsadmin scripting tool.
  2. Remove the portlet-based WAR file, as the following examples demonstrate:

     • Using Jython:

       AdminApp.update('isclite', 'modulefile', '[-operation delete -contenturi WarName]')

     • Using Jacl:

       $AdminApp update isclite modulefile {-operation delete -contenturi WarName}

  3. Save your configuration changes.
     Use the following command example to save your configuration changes:

     AdminConfig.save()