Manage admin console applications using scripting

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

Verify that the admin console EAR file is not archived before installation.

 

• Deploy a portlet-based console application into the EAR file.
  1. Launch the wsadmin scripting tool using Jython.

  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 lower than 2.1. The system automatically creates and uses an activation spec when specify the -usedefaultbindings option to deploy an application. If an activation spec 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.

     • Jython...

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

     • Jacl...

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

  3. Save the configuration changes...

     AdminConfig.save()

• Remove a portlet-based WAR file.
  1. Launch the wsadmin scripting tool using Jython.

  2. Remove the portlet-based WAR file, as the following examples demonstrate:
     • Jython...

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

     • Jacl...

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

  3. Save the configuration changes...

     AdminConfig.save()

 

Related tasks

Administer applications using scripting
Updating enterprise apps with the console
Use AdminApp for scripted administration

 

Related

Commands for AdminApp