BM Software Group WebSphere software Scenario: Using autoappinstall Style application and wants to test it on Web Sphere Application Server Applicati Automatica (WAR, JAR) WRD No need for Administrativ Note: Removing application scripts to install from monitored directory will date or uninstall uninstall application IBM Software Group I Web Sphere software Scenario: Using freeform Style Developer creating individual J2EE artifacts (java modules, static resources deployment descriptor, etc )and needs to construct install J2EE Application jsp, XML, static, etc) No need for eal with Enter rise complexity of Applica cage Structure Note: Combine with annotation- structure based programming12 IBM Software Group | WebSphere software WebSphere Application Server v6 23 Scenario: Using autoappinstall Style J2EE Apps (EARs) Developer creating/updating enterprise application and wants to test it on WebSphere Application Server 1 Developer generates or updates EAR or modules (WAR, JAR) 2 Developer places EAR or module file in monitored directory 3 Automatically installs / updates application on WebSphere No need for developer to use Administrative Console or wsadmin scripts to install, update or uninstall Note: Removing application from monitored directory will uninstall application EJB Jars WAR Client Jars IBM Software Group | WebSphere software WebSphere Application Server v6 24 Scenario: Using freeform Style Developer creating individual J2EE artifacts (java modules, static resources, deployment descriptor, etc.) and needs to construct/install J2EE application JSP Java Source (Servlet, EJB, Utility) Static HTML Image DD XML File 1 Developer generates individual artifacts (.java, .jsp, XML, static, etc) 2 Developer places artifacts in monitored directory 3 WRD packages up artifacts in J2EE structure, generates required artifacts and installs/updates on WebSphere J2EE Enterprise Application Structure No need for developers to deal with complexity of J2EE package Note: Combine with annotation- structure based programming