November 5, 2001

1
November 5, 2001

• E-Business
• ERP
• Internet Architecture

2
Agenda

• Previous class coverage
• Coleman project update
• Senge project update
• Lecture
• Next class
• OO Design and Modeling
• UML
• Java XML PERL

3
What is E-Business?

• New business paradigm
• Loosening dependence on paper
• Evolution of thought, actions, and business
  philosophy regarding using computers to share
  information
• Sharing data electronically with partners
• Sharing information electronically with customers

4
What is E-Business?

• Centrally managing and sharing resources
• Key component of ERP

5
Why E-Business?

• Customers demand and expect it
• Customers deserve it
• Customers need it
• It will save you money quick payback
• It will save you headaches

6
Why E-Business?

• It's the norm in the 21st century
• It's todays business reality
• Its not going away anytime soon

7
A Few Internet Facts

• 104 million adults online
• 16 million new users online in the last six
  months
• 80 million online shoppers
• 28 billion in sales last year
• 42 of Americans check email daily
• 9 of Americans check email hourly

8
A Few More Internet Facts

• 50 of Internet users have purchased goods online
• 5 are responsible for 31 of sales
• 28 of consumers online purchases failed
• Most common problem online long load time of
  web pages
• Second most common problem confusing website

9
Online Population Makeup

• 23 million have been online 3 years or more
  Pioneers
• 40 million have been online 1-3 years Early
  Followers
• 41 million have been online less than 1 year
  First of The Masses

10
ERP

• ERP, ES, MRP
• Bolt-on sytems
• Internet, Intranets, Extranets
• Common DB
• Reengineering business processes
• Work with mission-critical systems

11
Benefits

• Cycle time reduction
• Faster information transaction
• Better financial management
• Basis of E-Commerce
• Makes tacit knowledge explicit
• Globalization Euro
• Change

12
ERP Questions

• What is a customer?
• Who sold what? When? Where?
• How do we share data?
• Who defines data?
• Who manages data?
• Who owns data?
• Who updates data?

13
ERP What is it?

• Set of modules that are designed to work in
  certain mission-critical systems within an
  organization
• HR, FIN, CRM, SCM
• Need not install all modules
• Technical vs Strategic implementation

14
Criticisms

• Inflexible
• Long Implementation
• Overly hierarchical organization
• Antiquated technology

15
ERP Prerequisites

• What shape is your data in?
• How strong are your employees in ES?
• What is the shape of your IT infrastructure?
• What are your key strategies?
• How much can you afford to spend?
• How do executives feel about ES?
• Any major organizational changes coming?

16
ERP Factors

• Cost/Benefit analysis?
• Costs
• Software
• Hardware
• Training
• People

17

• Benefits
• Savings from new work flows
• Savings from dumping legacy systems
• Revenue enhancement benefits
• Business Case Process?
• SWOT Analysis

18
Vendor Selection

• Cost
• Your beliefs about vendors truthfulness
• Financing and payment alternatives
• Does vendor have a viable business future
• Customer support
• Technical and implementation support

19
PeopleSoft

• Founded in 1987 by Dave Duffield Ken Morris
• Current President Craig Conway
• 8,000 employees
• 5,000 customers world-wide
• Started primarily as Human Resource Management
  provider
• Today, modules include
• SCM, CRM, FIN, HR
• Competitors include SAP, Oracle, Microsoft

20
Internet Architecture
21
Browser as Client

• 1980 Dumb terminals
• 1985 Network file servers
• 1990 Client/server computing
• GUI
• Workstations did some work
• 1995 Three-tier client/server
• Application server added
• Performed processing and communication work

22

• Worked well on WAN and Internet
• Used Tuxedo to communicate
• Tuxedo 3rd party software
• Tuxedo replaced SQL statements
• One Tuxedo command replaced 200 500 SQL
  statements
• DB only use SQL statements
• 2000 Internet
• Web Server to connect to end user using Java

23

• JOLT runs on Web Server
• HTTP/JOLT
• Web Server talks to AS
• AS talks to DB
• DB is most often Oracle
• 1 connection to DB vs hundreds
• Faster and scalable
• Need Oracle for bath processing

24
Java JOLT - Tuxedo

• Java runs in JVM of browser
• JOLT is Tuxedo wrapped in Java
• Not all browsers support Java
• Java applets can take a long time to download

25
Tuxedo / Jolt

• Tuxedo works with AS
• Manages connections to AS
• Spawns and decays internal processes
• Jolt is Java subset of Tuxedo
• Performs identical functions
• All communication between AS and WS are managed
  by Jolt

26
PIA

• Easy Access
• Platform Independence
• Look and Feel
• Low Bandwidth Access
• Maintenance/Deployment
• Works on any Java enabled browser
• Explorer is recommended

27
PIA

• Firewall can exist between WS and AS
• Can house WS/AS and DB on same box (NT)

28
PIA
Web Server
Application Server
Web Services
AP
HTML HTTP
SQL
Servlet Engine
Tuxedo Jolt
29
Request Pathing
Web Server
Web Server
Application Server Server
1
6
12
13
5
8
7
4
9
11
2
3
10
30
Database
System Catalog
People Tools
Application Data
31
Batch Server

• Runs batch programs against DB
• COBOL
• SQR
• Directly tied to DB
• Install BS on DB

32
Development Environment

• Developers need connectivity
• Developers need tools
• System Administrators need connectivity
• System Administrators need tools
• Both work in two or three-tier environment

33
Two/Three-Tier

• Two-tier connect directly to DB
• Most functionality
• Slow performance on networks
• Three-tier uses Tuxedo and the AS to manage
  connection to DB