InfoCenter Home > 6.6.1: Administering applications (overview)Formally, an enterprise application can contain the following resources:
Therefore, the WebSphere administrator must represent servlets, JSP files, and HTML files as "Web applications" and "Web resources" in order to add them to enterprise applications:
When Web applications alone are sufficientSuppose a developer application contains only a servlet and an HTML file, or perhaps just a JSP file. The WebSphere administrator has gathered these resources into a Web application. The administrator might then wonder if it is necessary to add such a Web application to an enterprise application. Because the Web application seems complete by itself, why perform the extra step of configuring an enterprise application that contains only the Web application? The WebSphere administrator should include a Web application, or any resource, in an enterprise application when he or she needs to
Put another way, creating an enterprise application is unnecessary if:
Imagine a developer application comprised of multiple Web applications. In such a case, an enterprise application is required to give an identity to the group of Web applications. Without its own administrative identity, the enterprise application cannot be secured as a whole. The enterprise application also allows the group of resources in it to be managed (for example, to be made available to users, or stopped) as a unit. Enterprise applications transcend hostsUnlike the resources they contain, enterprise applications transcend particular application servers and host machines. Therefore, an Advanced Edition administrator can build a distributed enterprise application from resources that run in different application servers on various machines. The same resource can belong to multiple enterprise applications. It can also exist independently of an enterprise application. For example, by including the Web application in the enterprise application, MyServlet can exist alone, as part of a Web application and as part of an enterprise application. In any case, a resource must already exist in the administrative domain before being added to an enterprise application. For most resource types, when adding the resource to the administrative domain, the administrator must associate the resource with a particular application server and host machine. The administrative task for creating an enterprise application lets you build applications from resources existing before you started the task. You can also add new resources to the administrative domain as you create the enterprise application to which the resources will belong. To perform the above activities, the administrator can choose from among a few WebSphere Application Server administrative clients. Though the clients differ somewhat in terminology and the scope of activities they support, the concepts and procedures are the same as described above. See the Related information for considerations and instructions specific to each client. |
| ||
|