IS 483 Information Systems Management James Nowotarski 24 April 2003.

IS 483Information Systems Management

James Nowotarski

24 April 2003

• Recap Assignment 1• Finish distributed architectures/infrastructures• Understand fundamentals of network management• Review logistics for Assignments 2, 3

Today’s Objectives

Topic Duration

• Recap Assignment 1 & Quiz 10 minutes

• Recap distributed architectures 10 minutes

• Network management basics 45 minutes

*** Break 10 minutes

• Guest speaker: IT planning/arch 45 minutes

*** Break 5 minutes

• Service level agreements 30 minutes

• Quiz 15 minutes

• Assignments 2,3 15 minutes

Today’s agenda

Topic Duration






*** Break 5 minutes


• Quiz 15 minutes


Today’s agenda

Topic Duration






*** Break 5 minutes


• Quiz 15 minutes


Today’s agenda

IT Architecture and IT Infrastructure

Applications and Data

Reusable Technical Architecture

Hardware/Network

System SoftwareIT Architecture

IT Infrastructure

• Presentation logic• Application logic• Data management

IT Architecture vs. IT Infrastructure

IT Architecture IT Infrastructure

Level of Abstraction

Scope• Tech architecture• System software• Hardware/Network

IT Architecture + IT roles, organization+ IT processes

• Blueprint• Policies, rules

Implemented capabilities

Benefits of Architecture

• Productivity• Consistency• Quality• Rapid delivery• Maintainability• Interoperability• Reduces complexity• Leverages scarce skills

Where Does Internet Fit?

DataManagement

ApplicationLogic

Presentation

Presentation

Presentation

DataManagement

ApplicationLogic

DataManagement

ApplicationLogic

DataManagement

DataManagement

ApplicationLogic

Presentation

ApplicationLogic

Presentation

DataManagement

ApplicationLogic

Presentation

Network

DistributedPresentation

RemotePresentation

DistributedFunction

Remote DataManagement

DistributedDatabase

Thickness of Client

Thin Thick

3-Tier Distributed Architecture

WorkstationEnterpriseServer

WAN

WorkgroupServer

LAN

• Presentation • Application logic • Data management

n-Tier Example

BankCustomers

Internet

InternetFirewall

WebServer

ApplicationFirewall

AppServer

DBServer

LegacyMainframe

Comparison of n-tier relative to 3-tier

Advantages• Better load balancing on different servers• More scalable

Disadvantages• Potentially greater load on network• More complex to implement• More hardware and network components ($$$)

Solution “Stack”

Applications and Data

Reusable Technical Architecture

Hardware/Network

System Software

Examples

Dell, HP, Sun, EMC, CiscoAT&T, Sprint, WorldComPublic Internet

MiddlewareWebSphere, CICS TSApacheJ2EEDB2, Oracle, SQL Server Linux, Unix, Windows, z/OS

Claims, Payroll, CRM, ERP

Component-Based Architecture for Microsoft (Accenture)

overlap

Middleware

Types of Middleware

• Network middleware

– Procedure calls over a network

– Example: Remote Procedure Calls (RPCs), ORBs

• Conversational middleware

– Transparent conversion of text, graphics, data

– Example: Electronic Data Interchange (EDI)

• Transaction Processing

– Transaction management services to support processing of high volumes of transactions

– Example: CICS TS

Middleware

Types of Middleware (cont.)

• SQL and Database Middleware

– Applications can connect to several different databases using one programming interface

– Example: Open Database Connectivity (ODBC)

• GUI Middleware

– Applications can support multiple GUIs across a network

– Example: X Windows

• Messaging Middleware

– Distributing data and control through synchronous or asynchronous messages

– Example: IBM MQSeries

IT Management Issues Associated with Distributed Architectures

• Migrating from legacy (mainframe) to distributed architecture:

Three major business issues1. Cost2. Resources3. Risk

Five typical alternatives1. Replatforming2. Screen scraping3. Replace with package4. Build from scratch5. #4 plus business process reengineering

• Support and maintenance issues– Training and standards– Robust, fault tolerant components (lack thereof)– Service level monitoring and troubleshooting

Topic Duration






*** Break 5 minutes


• Quiz 15 minutes


Today’s agenda

Network Management

Definition

The set of activities required to plan, install, monitor and maintain all network components in order to achieve specified service levels reliably, at an acceptable and agreed cost

Importance of business focus in network solutions

• Network is critical to lifeline of the business, must meet business needs

• A complete solution involves managing the network and all its components, which includes the business processes and user’s needs

• Administrators will need to proactively manage the network instead of reacting to user’s complaints

Importance of business focus in network solutions

What business requirements are driving business network needs today?

Business Driver Network Impact

Reduce operational costs Consolidate network infrastructure

Outsource

Network management architecture

Source: Cisco

Elements of Network Management Architecture

• End stations (managed devices)– send alerts when problem is recognized– examples: routers, access servers, switches,

bridges, hubs, computer hosts, printers

• Management entities– gather information from managed devices (via

agents)– log and react to network events– present status info and alerts to network operator– perform tests

• Agents– software modules that reside within managed

devices and gather and store information

Elements of Network Management Architecture (cont.)

• Network management protocol– protocol used by agent and management entity to

exchange information– Simple Network Management Protocol (SNMP) is

near universal standard for private networks– Telecommunications Management Network (TMN)

is gaining popularity in the more heterogeneous world of public networks

• Proxies– represent network managed devices

• Management database– repository of information collected by agent (alarms

outstanding, performance data, etc.)– complex and high-volume information (oo

databases being used)

Network Management Functions

• Fault management

• Configuration management

• Accounting management

• Performance management

• Security management

Source: International Standards Organization (ISO)


Fault Management

• Detection• Isolation• Diagnosis• Correction


Configuration Management

• Analyzing impact of changes• Installing changes• Controlling changes


Accounting Management

• Track network usage (no abuse of privileges)• Monitor operating costs


Performance management

• Establish performance goals• Collect and analyze performance data• Assess actual performance relative to goals• Identify areas for improvement (capacity, network

design, etc.)


Security Management

• Control access to network• Report, diagnose, and correct security breaches

• Annual cost of owning and operating a network

16% - cost of network equipment

84% - ongoing operating expenses, most of this is the support organization

Network Management Costs

Topic Duration






*** Break 5 minutes


• Quiz 15 minutes


Today’s agenda

Topic Duration






*** Break 5 minutes


• Quiz 15 minutes


Today’s agenda

Service Level Agreements

Definition

Contract that details the level of service required from a service provider to the user of those services

2 Types of SLA’s

• Internal • External

Management of Systems Environments

Users

Service Management

SLA

Vendors Developers

SystemsManagement• Network Mgmt• Server Mgmt• etc.

Internal SLAExternal SLA


Service ServiceType of SLA Provider User

Internal IT network End user group group (i.e., business unit)

External Vendor End user group-- IT network group coordinates


• Clearly articulate and document the level of service that users of the computing environment expect to receive

• Should be used to drive out the requirements for the service provider organization

• Clarifies the business objectives and constraints for an application system

• Require an accurate way of measuring the service levels achieved


Table of Contents

• Dates (start, expiration)

• Types of services provided

• Service measures

• Roles/Responsibilities (provider, consumer)

• Resources needed and/or costs charged

• Reporting mechanism

• Signatures


Table of Contents

• Dates (start, expiration)

• Types of services provided

• Service measures

• Roles/Responsibilities (provider, consumer)

• Resources needed and/or costs charged

• Reporting mechanism

• Signatures


Disciplines

Performance Management

Configuration Management

Availability

Reliability

Response time

Application versions & enhancements

Accounting Management Reporting procedure

Fault Management Incident management, e.g., • database failure• workstation failure

Security Management

Recovery ManagementBackup

Recovery

Capacity Planning

Online Systems

Batch SystemsOutput handling

Schedule execution

Service Types


• How many are needed?

• Do they contain primarily business or technical language?

• How are they used?

• What are consequences if SLA not met?

– To the service provider

– To the service user (i.e., the business)

• In an internet environment, what are challenges experienced in the creation of effective SLAs?

Topic Duration






*** Break 5 minutes


• Quiz 15 minutes


Today’s agenda

Topic Duration






*** Break 5 minutes


• Quiz 15 minutes


Today’s agenda

• Operations Management

• See web site for reading

• Quiz on Operations Management

• End user training (start)

Topics for May 1

End of slides

Date post:	21-Dec-2015
Category:	Documents
View:	219 times
Download:	0 times

IS 483 Information Systems Management James Nowotarski 24 April 2003.

Documents