Lecture Business management information system - Lecture 22: Interorganizational system development

This chapter presents the following content: Interorganizational system development, discussion case – interorganizational systems development, internet-based systems, application servers, java development platform, web service advantages for e-business, web services terminology, web service model, tradıtıonal web-based systems, web server clusters.

Interorganizational System

Development Lecture 22

™ HONG KONG EXCHANGES & CLEARING

Case Study — Interorganizational Systems Development

= Internet-Based Systems

Application Servers Java Development Platform

Web Service Model

TRADITIONAL WEB-BASED SYSTEMS WEB SERVER CLUSTERS

Case Example — Web Services

# BUILDING A WEB SERVICE

Preparing for On-The-Fly Web Services Development

m — ltt

Interorganizational System Development

= One of the main business trends Is the appearance of

business ecosystems — “groupings” of businesses that work closely together

Supply Chain Management systems integrate supply chains

= These are now a major trend as they compete against one another on their ability to reduce costs and time across their entire chains

= Development of such inter-organizational systems

requires teams from the different organizations to work

together

SS 5

Supply Chain Example

Figure 4: The Multiple Enterprises of the Supply Chain

Acquire ————*»> Convert ——— Distribute

mẻ _D_D_—` nh

Interorganizational System Development

cont

Another type of Inter-organizational system

is a platform, which provides the

infrastructure for the operation of a business ecosystem, a region, or an industry

Sabre Video game industry

TTS ằ-

Interorganizational System Development

cont

= Platform development Is a major trend In an

Increasing number of industries

= Following 2 cases

Exxonmobil - Yet to become a platform

HKEx — points out the types of coordination needed

to develop an interorganizational system for a business ecosystem

EXXONMOBIL Discussion Case — Interorganizational

S Developm

= Mobil create) ster pass, a svstEm II uses a 1.5-

Inch-long wand that motorists can attach to their key

chain and “wave” at an electronic reader on a Mobil gas pump to pay for gas

= Mobil’s goal was to speed motorists in and out of Its

Stations

= ExxonMobil now has five million Soeedpass holders

They buy more Mobil gas than non-Speedpass customers, they visit Mobil stations one more time per month, and they spend 2-3 percent more

money

EXXONMOBIL Discussion Case — Interorganizational Systems

Development cont

= To leverage this technology, it has teamed up with

McDonald’s restaurants in Chicago to test use of

Speedpass to pay for food

™ How should Mobil leverage this platform even more?

HONG KONG EXCHANGES & CLEARING Case Study — Interorganizational Systems

Development

™ HKEx Is Asia’s second largest stock market

= To extend its reach beyond Hong Kong, It decided to

embed its business processes in an open trading

architecture by building a third-generation automatic

order matching and execution system

= HKEx’s goal is integrated end-to-end computerized

trading processes, from investors through brokers to

markets

HONG KONG EXCHANGES & CLEARING Case Study — Interorganizational Systems

Development cont

= The project was daunting, involving both

internal and external people

4O staff members from varying departments

150 consultants, and

500 brokerage firms

HONG KONG EXCHANGES & CLEARING Case Study — Interorganizational Systems

Development cont

MI Development took two years, and ended with

three levels of testing

One level involved testing the systems that some 100

brokerage firms built to interface with the open

gateway

M Rollout was phased so that Hong Kong's stock

market was not disrupted

HONG KONG EXCHANGES & CLEARING Case Study — Interorganizational Systems

Development cont

M@ HKEx has built its processes into an open architecture

and coordinated the construction of an inter-

organizational system — with components from

numerous sources and participants of many kinds

MI \t is now the foundation for its industry ecosystem

mề ` na

Internet-Based Systems

M@ HKEx’s system is not Internet based but it allows ©

Internet access for online trading as well as other actions

The Internet has opened up the options HKEx can offer

M Internet users have become so sophisticated that

Internet-based systems must be:

Scalable Reliable, and Integrated both internally and externally with systems

of customers or business partners

mề ` na

Internet-Based Systems

Mi To do this companies recognize they must negotiate

‘language differences’

E.g asystem may have to port old COBOL

applications to Java, reconcile interface discrepancies and interface with back-end legacy applications, often without documentation or past experience with those

systems

= Tools are available to help

"= Open systems etc

m _DÖD nh

Internet-Based Systems: Application

Servers

@ Originally conceived as a piece of middleware to link a Web

server to applications on other company systems

The application server has grown into a framework for developing Internet-based applications

Mi Figure 9-6 shows the basic application server architecture The virtual server takes requests from clients and Web servers (on the left), runs the necessary business logic & provides

connectivity to the entire range of back-end systems (on the

right)

Internet-Based Systems: Application Servers

Mi The goal of the application server:

"' mm =

FIGURE 9-6 An Application Server Architecture

Virtual Application Server

Internet-Based Systems:

Java Development Platform

= Java has been in many cases the starting point for the

development of Internet-based systems with an open

system architecture

Originally — developed to provide applets that run

on Web clients

= Goal = Platform for independent language

that could run on any system

= Promise applications portability: “write once, run

anywhere”

# Didn't live up to promise = evolved into a standard

platform for developing server-side applications

ava Software Development

* Java Code Export v1.0.0 - [G:\Projects\Code Convertor\Java\Jim- v 2 (src)\JIM\source\jim\Jim java]

kage jim; net DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional/}

rt Beat ‹ “http://www w3.org/TR xhtml /DTD/chbmil transitional, dtd” >

9 Y* Copyright, 2007 Jason Dominczak 6 <bitle >G:\Projects\Code Convertor Javal.im- v.2 (src)

10 |* \JIM\source\jim\ Jim java <jtitle>

Ll | * Ae Me & part of JM - The Java Instant Messenger { 95

12 | *atfader is free software; you can redistrbute & bnd/or modiy 10 | <style type="text/css">

13 | *# uncer the terms of the GAU General Public License ar lt /"x1CDA FAƒ*

published by ‹Â span,c7 {color: #008090}

14 | “the Free Software Foundation; ether version 2, or fat your | | span.c6 {color: #800000}

option, |) span.cS {color: #000000; font-family: Tahoma; font-size:

15 | * any fater versun 70%

L7 | *_JJM w distributed in the Aope that & wil be useful, but ‘> | span.c3 {color:; #000000}

18 | * WITHOUT ANY WARRANTY; without even the implied warrant) |” | span.c2 (font-family; Tahoma; font-size; 70%}

oF ‘> | b.c1 {color: #O000FF}

19 | * MERCHANTABILITY or FITNESS FOR A PAR TICULAR PURPOSE 19) /ib*+

See the GIL 20 | <style>

20 | * General Public License for more cetails 2! | <fhead>

ican 24 | <span class="c2"> <b class="cl" >package</b></span><span

23 | “along meth etader; see the file COPYING JF not, write to ie class="c3" >&nbsp; jm; <br />

24 | *Frae Software Foundation, Inc., 59 Temple Place - Sutte 330, 25 </span> <br />

Boston, | 26 | <span dass="c2"><b class="c1" >inport<[b><Jspan><span v

Internet-Based Systems:

Java Development Platform cont

= Major components in Java server-side platform

Enterprise Java Beans (EJB)

=" Preconfigured pieces of code that IS staff no longer have to build from scratch

Java 2 Enterprise Edition (J2EE)

=" Defines a standard for developing Internet-based

enterprise applications

m _DÖD nh

Internet-Based Systems:

Java Development Platform cont

Provide an alternative to building online business

systems from scratch or buying packaged online

business systems because of their multi-vendor

platform capability and pre-built, reusable components

= Microsoft competes with its own versions:

Component Object Model (COM)

Distributed Component Object Model (DCOM)

" m=a.VvgỢ

Web Service

Web Service:

“Web-based applications that dynamically interact

with other Web applications using open standards that include XML, UDDI and SOAP”

Universal Description Discovery Integration

Simple Object Access Protocol

Service-Oriented Architecture (SOA):

“Development of applications from distributed

collections of smaller loosely coupled service

providers”

“A collection of services or software agents that communicate freely with each other”

SS

UDDI

= UDDI (Universal Description, Discovery,

and Integration) is an XML-based registry for businesses worldwide to list

themselves on the Internet

# its ultimate goal is to streamline online

transactions by enabling companies to find one another on the Web and make their

systems interoperable for e-commerce.

TSS tts

Web Service Advantages for E-Business

= Allow companies to reduce the cost of doing e-business,

to deploy solutions faster

Need a common program-to-program communications model

= Allow heterogeneous applications to be integrated more rapidly, easily and less expensively

= Facilitate deploying and providing access to business functions over the Web

""MX =.ƯGƯGC =

Web Services Terminology

= SOAP (Simple Object Access Protocol)

exchanging XML messages on a network

Like RPC, it provides a way to communicate between

applications

Unlike RPC, it communicates over HTTP

Web Services Terminology

Because HTTP Is supported by all Internet browsers

and servers, SOAP can run on different operating

systems, with different technologies and programming

languages

describing interfaces of Web services

= UDDI (Universal Description, Discovery and Integration)

managing registries of Web services

SS = Web Service Model (2/3)

# holes ¡n a Web Service Architecture

Service provider

= Owner of the service

= Platform that hosts access to the service

mà D,ÀÀÌ

Web Service Model (3/3)

# Operations in a Web Service Architecture

mề ` na

Internet-Based Systems:

Web Services

#The vision of Web Services is that modules of code can

be assembled into services, which, in turn, can be linked to create a business process at the moment It is needed and run across enterprises, computing platforms, and data

models

= There are two development modes:

One is to wrap an XML wrapper around an existing piece of code that performs a specific function

Z“_ ` `

TRADITIONAL WEB-BASED SYSTEMS

= Many Web-based systems are still organized as simple client-server architectures

Web server

2 Server fetches document from local file

Z“_ ` `

TRADITIONAL WEB-BASED SYSTEMS

» The core of a Web site: a process that has access toa local file system storing documents

“—_—_ `

TRADITIONAL WEB-BASED SYSTEMS

>» How to refer to a document?

URL (Uniform Resource Locator)?

TT ts

Uniform Resource Locator

» Areference called Uniform Resource Locator (URL) Is used to refer a document

>» The DNS name of its associated server along with a file name is specified

» The URL also specifies the protocol for transferring the document across the network

> Example:

http://www.cse.unl.edu/~ylu/csce855/notes/web-

system.ppt

—_

`

TRADITIONAL WEB-BASED SYSTEMS

> Aclient interacts with Web servers through a special application known as browser

» What's the key function of a browser?

Responsible for displaying documents

Z“ _ `

WEB SERVER CLUSTERS

Front end handles

Front all incoming requests

end and outgoing responses

m"—_ `

WEB SERVER CLUSTERS

» The front end can be designed in two ways:

Transport-layer switch — simply passes data sent along the TCP connection to one of the servers, depending on some measurement of the server’s load

Content-aware request distribution — it first inspects the HTTP request and decides which server it should

forward that request to

m"—_ `

WEB SERVER CLUSTERS

4 For example, if the front end always forwards

requests for the same document to the same server, the server may cache the document resulting in better response times

Approach that combines the efficiency of transport- layer switch and the functionality of content-aware

distribution has been developed

Z"— `

WEB SERVER CLUSTERS

» Another alternative to set up a Web server cluster Is to use round-robin DNS

> With round-robin DNS a single domain name is

associated with multiple IP addresses

» When resolving a host name, a browser would receive a

list of multiple addresses, each address corresponding to

a server

» Normally, browsers choose the first address on the list,

but most DNS servers circulate the entries

» As aresult, simple distribution of requests over the

servers in the cluster is achieved

JS cœ

BUILDING A WEB SERVICE

Case Example

= The steps Involve:

Exposing the code Writing a service description Publishing the service

Finding the service, and Invoking a Web Service

Step 2: Write a Service Description

using WSDL

Currency conversion Web Service description

Step 3: Publish the Service

in a UDDI Registry UDDI Registry

Currency conversion description

Step 4: Find a Currency Conversion Web Service

using a SOAP envelope

XML wrapper | request | XML wrapper