Manage administrative console applications

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

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

• 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 lower than 2.1. The system automatically creates and uses an activation specification when specified 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.

     • Jython:

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

     • Jacl:

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

  3. Save the configuration changes.

     Use the following command example to save the configuration changes:

     AdminConfig.save()

• Remove a portlet-based WAR file.

  1. Start the wsadmin scripting tool.
     

  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.

     Use the following command example to save the configuration changes:

     AdminConfig.save()

Related tasks

Administer applications

Update enterprise applications with the console

Use the wsadmin scripting AdminApp object for scripted administration

Commands for the AdminApp object