Tool Mentor: Deploying Applications Using the Systems Management End-User InterfacePurposeThere are many pieces to an enterprise application. With distributed applications, managing these pieces and making sure that they are all delivered to the right spot is challenging. Within the WebSphere Application Server Enterprise Edition (WAS EE) Component Broker (CB) environment, the Systems Management End User Interface (SMEUI) helps you do this. SMEUI manages the run-time environment in WAS EE. Using SMEUI, you can deploy application families, configure servers, and server groups; define the physical topology by associating servers to specific hardware nodes; enable security and debugging; and start, stop, and monitor servers. If your role within your organization is Systems Manager, someone who needs to know all of this in great detail, then there are Component Broker manuals and courses that will give you what you need. The purpose of this tool mentor is to help a developer or first time user deploy an application into a predetermined test environment. OverviewBefore proceeding, be sure you are familiar with the concepts of Servers, Server Groups, and Management Zone. This tool mentor provides a quick summary of each, but much more information is available in the Component Broker documentation. You can deploy and install your application into managed server groups or as a standalone application. We will be discussing the managed server group configuration. To work through this, it's helpful to have a configuration in mind. The configuration can be created before or after you load the application family into the host image. Creation of the configuration is generally a one shot deal. Once you have it set up, you keep using it. It's the shell in which your applications run. Tool StepsTo deploy an application using the SMEUI:
Assumption: You are on a CB development workstation that has Object Builder installed and you have access to the server environment via SMEUI. 1. Create the Application Family DDL
Creation of the application family is done using Object Builder, as part of another stepthat is, before you start this step in the process. When you create an application family package in Object Builder, the result of the Generate step is a DDL file that describes all elements of the application family. If you are familiar with the Enterprise JavaBeans (EJB) programming model, this is analogous to the Deployment Descriptor that's used with EJB applications. In Component Broker the directory structures used by Object Builder and SMEUI are fixed, so what you need to know at this time is the location into which the DDL file was generated. Be carefuldo not move it to another location. Everything is relative to the fixed directory structure created by Object Builder. Part of this process is to copy the run-time files from the development environment to the run-time environment, and the tools need to know where to find those files. The example application family we'll be working with is called TravelAppFam, a travel agency booking system. There is one application inside it, called TravelApp. To generate the application family DDL file, in Object Builder, select Generate from the pop-up menu of the application family, TravelAppFam. If you are using DB2 for persistence, two DDL files are generatedone with the word "specific" in the file name and one without. You'll need to load both in the host image in the next step. Once you've generated the DDL file, take note of where it is. You'll need to know this in the next step. If you are using Windows NT, it will be under the OB project directory, Working\Nt\Production\TravelAppFam. 2. Create a configuration
Next, set up a simple configuration for a Managed Server Group in a Management Zone that will be isolated from all others. A Management Zone is a grouping of configurations, each configuration being a logical-to-physical mapping of resources (servers) to host images (machine nodes). Within a given management zone it's possible to have many configurations. Only one configuration can be active a any given time. You determine which set of resources to run on a given set of nodes by activating a particular configuration. You may also define Server Groups, to manage several server processes running as clones on several different host images. You define the group, and the individual server instances that will be part of the group. Then you assign, or associate, a server instance to a particular host image (machine node). Finally assign your application family to the Server Group and it will run on all server instances that are part of the group. To create a configuration, server group, and server on HostXYZ:
3. Load the Application Family
Now, move the executables and other files over to the server environment. When you load an Application Family, you are loading it and all of its associated files onto a particular host image (node) where it, or any of its parts, will run. You're not defining or starting servers, but rather making the files available with the anticipation that a server from the given Application Family will be configured on this host.
4. Configure the server group
This step is where you actually assign (associate) the Application (server process) to a Server group. To configure a server group, from the menu, select Tasks > Configure Server. A wizard will walk you through the configuration process; select the applications, zone, configuration, and server group you want to configure. 5. Activate the configuration
A management zone can have many possible configurations, only one of which can be active at a time. The active configuration is the one that's in the Host Image. Start the servers by activating a configuration in a management zone. The Component Broker runtime will roll your new configuration in and the old one out, in an orderly and controlled manner. Depending on how you have the servers configured, the server may start immediately or it may wait until the first request comes in. To activate a configuration, select Activate from the Management Zone's pop-up menu. The time it takes CB to complete this operation will depend on the complexity of the previously active configuration, how it was being used, and the complexity of the configuration being activated. 6. Start the server
Although you may not be required to start and stop the server very often, it's valuable to know how. This will also show you where to manage the servers. The System Management model includes the Model world, where you make logical associations of resources (for example, configurations), and the Image world, which represents the physical structures and currently active entities and relationships. When you operate on an Image, you are doing it in real time; when you operate on a Model, you are doing it off-line. In the Image world, you ensure the servers are running:
This information is provided by IBM
Corporation. © Copyright IBM Corporation 1999-2000 |
|
Rational Unified
Process |