You can update a module for an existing application through the administrative console, the wsadmin tool, or programming. When you update a module, you replace the existing module with a new version. Use this example to update a module through programming.
Before you can update a module on WebSphere Application Server, you must first install the application.
Perform the following tasks to update a module through programming.
The following example shows how to add a module to an application based on the previous steps. Some statements are split on multiple lines for printing purposes.
//Inputs: //moduleName specifies the name of the module that you add to the application. //moduleURI specifies a URI that gives the target location of the module // archive contents on a file system. The URI provides the location of the new // module after installation. The URI is relative to the application URL. //uniquemoduleURI specfies the URI that gives the target location of the // deployment descriptor file. The URI is relative to the application URL. //target specifies the cell, node, and server on which the module is installed. //appName specifies the name of the application to update. String moduleName = "C:/apps/foo,jar"; String moduleURI = "Increment.jar"; String uniquemoduleURI = "Increment.jar+META-INF/ejb-jar.xml"; String target = "WebSphere:cell=cellname,node=nodename,server=servername"; String appName = "MyApp"; //Get the administrative client to connect to //WebSphere Application Server. AdminClient client = ...; AppManagement proxy = AppManagementProxy. getJMXProxyForClient (client); Vector tasks = proxy.getApplicationInfo (appName, new Hashtable(), null); //Create an application deployment controller instance, AppDeploymentController, //to populate the Java archive (JAR) file with binding information. //The binding information is WebSphere Application Server-specific deployment information. Hashtable preferences = new Hashtable(); preferences.put (AppConstants.APPDEPL_LOCALE, Locale.getDefault()); preferences.put (AppConstants.APPUPDATE_CONTENTTYPE, AppConstants.APPUPDATE_CONTENT_MODULEFILE); AppDeploymentController controller = AppManagementFactory.readArchiveForUpdate( moduleName, moduleURI, AppConstants.APPUPDATE_UPDATE, preferences, tasks);
If the module that you update for the application lacks any bindings, add the bindings so that the module update works. Collect and add the bindings by using the public APIs that are provided with WebSphere Application Server. Refer to Java documentation for the AppDeploymentController instance to learn more about how to collect and populate tasks with WebSphere Application Server-specific binding information.
//After you collect all the binding information, save it in the module. controller.saveAndClose(); //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.UPDATE); //Get the installation options. Hashtable options = controller. getAppDeploymentSavedResults(); //Update the existing application by adding the module. options.put (AppConstants.APPUPDATE_CONTENTTYPE, AppConstants. APPUPDATE_CONTENT_MODULEFILE); //Specify the target for the new module Hashtable mod2svr = new Hashtable(); options.put (AppConstants.APPDEPL_MODULE_TO_SERVER, mod2svr); mod2svr.put (uniquemoduleURI, target); proxy.updateApplication ( appName, moduleURI, moduleName, AppConstants.APPUPDATE_UPDATE, options, null); // Wait; the installation application programming interface (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(); System.out.println ("ObjectName: " + on); _soapClient.addNotificationListener (on, this, myFilter, handback); } public void handleNotification (Notification notf, Object handback) { AppNotification ev = (AppNotification) notf.getUserData(); System.out.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) { System.out.println ("Error removing listener: " + th); } System.exit (0); } } }
In this information ...Related tasks
| IBM Redbooks, demos, education, and more(Index) |