Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

A Mechanism for Determining the Deployment Model for n-Tiered Applications

IP.com Disclosure Number: IPCOM000041647D
Original Publication Date: 2005-Feb-02
Included in the Prior Art Database: 2005-Feb-02
Document File: 5 page(s) / 112K

Publishing Venue

IBM

Abstract

The evolving challenges of N-tier distributed e-business applications require a fundamentally different approach to performance optimization. Rather than adding more hardware and increasing the speed of the networks, e-business companies should focus on maximizing the performance of their existing systems by better understanding how the different components of a distributed e-business application interact together and what is the impact of the modification of some critical component parameters on the overall system. Disclosed is the starting point for understanding application performance. In order to apply any optimization techniques to our application, we must first determine the application’s deployment model. Our invention describes a method for determining the deployment model.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 44% of the total text.

Page 1 of 5

A Mechanism for Determining the Deployment Model for n -Tiered Applications

Every application has a deployment model. The simplest deployment model is a deployment where all of the application's components run on the same machine i.e. single tier deployment. For large commercial applications, the application's components tend to be distributed across multiple systems i.e. multi-tiered or N-tiered deployment. A deployment model is a description of each application component and where the component is running.

Agregation

Formatter

 e-business Deployment

 Models Analyzer

Parser

Business Model

DB

Predefined Business Models

DB

Configuration File

Installed Software

Information Extraction Rules

Software/Configuration Files repository

Running Software

Configuration File Matcher

DB

Installed/Running Middleware

Probe

Remote Configuration

Figure 1

Figure 1 describes the mechanism to determine the deployment model. The starting point for determining the deployment model is the Installed/Running Middleware Probe component.

1

[This page contains 1 picture or other non-text object]

Page 2 of 5

admin.config:com.ibm.ejs.sm.adminServer.dbserverName=isvlab014

WebSphere Application Server Configuration File = admin.config

Parser

admin.config

Information Extraction Rules

For WebSphere Conf File search for Admin Server location.

Determine configuration on isvlab014

DB

Configuration File

Configuration File Matcher

DB

Installed/Running Middleware

Probe

   Remote Installed/Running Middleware

Probe

ps -ef command returns WebSphere Application Process lslpp -l command returns installed WebSphere components

Software/Configuration Files repository

Figure 2

The Installed/Running Middleware Probe's job is to identify middleware running on the given tier. The probe is installed on each tier of the deployment. The probe's output is a list of middleware running or installed on the machine. A simple implementation might use the command "ps -ef" to list all of the processes running on a machine running AIX. Additionally, the command "lslpp -l" could be used to list software installed on the machine. Combining the output from these two commands provides a list of all possible middleware on this machine whether currently running or just installed.

The middleware list is passed to the Configuration File Matcher component. The Configuration File Matcher's role is to process the middleware list and determine the set of configuration files used by the middleware. For any given middleware component, a configuration file is generally used to describe how the middleware is configured and where if any of its dependent middleware are installed. A database is used to store the relationship between a given middleware and its associated configuration file. For example, if the middleware list indicated that WebSphere Application Server was installed, then the Configuration File Matcher component would determine the configuration file for WebSphere Application Server was admin.config by...