Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Manage applications through programming
Update an application through programming
We can update an existing application through the administrative console, wsadmin.sh, or programming. Use this example to completely update an application through programming.
This task assumes a basic familiarity with MBean programming. For information on MBean programming, see MBean Java application programming interface (API) documentation. In this information center, click Reference > Mbean interfaces.
Before you can update an application on WAS, install the application.
Perform the following tasks to completely update an application through programming.
Procedure
- Connect to WAS.
- Create the application management proxy.
- Create the notification filter for listening to events.
- Add the listener.
- Prepare the enterprise archive (EAR) file by populating it with binding information.
- Update the application.
- Wait for some timeout so that the program does not end.
- Listen to Java Management Extensions (JMX) notifications to understand completion of the operation.
- After you update the application, remove the listener and quit.
Results
After you successfully run the code, the application is updated.
Example
The following example shows how to update an application based on the previous steps. Some statements are split on multiple lines for printing purposes.
import java.lang.*; import java.io.*; import java.util.*; import java.lang.reflect.*; import com.ibm.websphere.management.application.*; import com.ibm.websphere.management.application.client.*; import com.ibm.websphere.management.*; import javax.management.*; public class aa { public static void main (String [] args) { try { // Connect to WAS. String host = "localhost"; String port = "8880"; String target = "WebSphere:cell=cellName,node=nodeName,server=server1"; Properties config = new Properties(); config.put (AdminClient.CONNECTOR_HOST, host); config.put (AdminClient.CONNECTOR_PORT, port); config.put (AdminClient.CONNECTOR_TYPE, AdminClient.CONNECTOR_TYPE_SOAP); .println ("Config: " + config); AdminClient _soapClient = AdminClientFactory.createAdminClient(config); // Create the application management proxy, AppManagement. AppManagement proxy = AppManagementProxy.getJMXProxyForClient (_soapClient); String appName = "MyApp";(Windows)String fileContents = "C:\test\test.ear";(Solaris) (AIX)String fileContents = "/test/test.ear";// Create the notification filter. NotificationFilterSupport myFilter = new NotificationFilterSupport(); myFilter.enableType (NotificationConstants.TYPE_APPMANAGEMENT); //Add the listener. NotificationListener listener = new AListener(_soapClient, myFilter, "Install: " + appName, AppNotification.INSTALL); // Refer to the installation example to see how you can prepare the EAR // file by populating it with binding information. // If code for the preparation phase has started, then you already have the options table. // If not, create a new table and add the module-to-server relationship to it by uncommenting // the next statement. //Hashtable options = new Hashtable(); options.put (AppConstants.APPDEPL_LOCALE, Locale.getDefault()); options.put ((AppConstants.APPUPDATE_CONTENTTYPE, AppConstants.APPUPDATE_CONTENT_APP); // Uncomment the following statements to add the module to the server relationship table if // the preparation phase does not collect it //Hashtable module2server = new Hashtable(); //module2server.put ("*", target); //options.put (AppConstants.APPDEPL_MODULE_TO_SERVER, module2server); // Update the application. proxy.updateApplication (appName, null, fileContents, AppConstants.APPUPDATE_UPDATE, options, null); // Wait for some timeout. The installation API is // asynchronous and so returns immediately. // If the program does not wait here, the program ends. Thread.sleep(300000); // Wait so that the program does not end. } catch (Exception e) { e.printStackTrace(); } } } // Specify the Java Management Extensions (JMX) notification listener for JMX events. class AListener implements NotificationListener { AdminClient _soapClient; NotificationFilterSupport myFilter; Object handback; ObjectName on; String eventTypeToCheck; public AListener(AdminClient cl, NotificationFilterSupport fl, Object h, String eType) throws Exception { _soapClient = cl; myFilter = fl; handback = h; eventTypeToCheck = eType; Iterator iter = _soapClient.queryNames (new ObjectName( "WebSphere:type=AppManagement,*"), null).iterator(); on = (ObjectName)iter.next(); .println ("ObjectName: " + on); _soapClient.addNotificationListener (on, this, myFilter, handback); } public void handleNotification (Notification notf, Object handback) { AppNotification ev = (AppNotification) notf.getUserData(); .println ("!! JMX event Recd: (handback obj= " + handback+ "): " + ev); //When the installation is done, remove the listener and quit if (ev.taskName.equals (eventTypeToCheck) && (ev.taskStatus.equals (AppNotification.STATUS_COMPLETED) || ev.taskStatus.equals (AppNotification.STATUS_FAILED))) { try { _soapClient.removeNotificationListener (on, this); } catch (Throwable th) { .println ("Error removing listener: " + th); } System.exit (0); } } }
Install an application through programming
Uninstall an application through programming
Add to, updating, or deleting part of an application through programming
Prepare a module and adding it to an existing application through programming
Prepare and updating a module through programming
Delete a module through programming
Add a file through programming
Update a file through programming
Delete a file through programming