Web Services in Finance / Edition 1

Web Services in Finance / Edition 1

4.0 2
by Paul A. Watters
     
 

ISBN-10: 1590594355

ISBN-13: 9781590594353

Pub. Date: 11/04/2004

Publisher: Apress

Many times, web services standards do not explicitly address core issues specific to the financial industrywhich makes it difficult to implement standards-compliant systems. But Web Services in Finance will bridge the gap in standards awareness. And you will acquire the skills to develop secure applications quickly.

If you are a .NET or J2EE developer

Overview

Many times, web services standards do not explicitly address core issues specific to the financial industrywhich makes it difficult to implement standards-compliant systems. But Web Services in Finance will bridge the gap in standards awareness. And you will acquire the skills to develop secure applications quickly.

If you are a .NET or J2EE developer working in the financial industry, currently migrating applications to become Web services, or writing new Web services, then this book is your ideal companion! The authors thoroughly discuss crucial topics like data representation, messaging, security, privacy, management, monitoring, and more. What’s more: the provided examples and API reviews will help you swiftly reach your goals.

Table of Contents

  1. Introduction to Web Services
  2. Enterprise Systems
  3. Data Representation
  4. Messaging
  5. Description and Data Format
  6. Discovery and Advertising
  7. Alternative Transports
  8. Security
  9. Quality of Service
  10. Conversations,Workflows, and Transactions

Product Details

ISBN-13:
9781590594353
Publisher:
Apress
Publication date:
11/04/2004
Series:
Lecture Notes in Computer Science Series
Edition description:
2005
Pages:
256
Product dimensions:
7.00(w) x 9.25(h) x 0.63(d)

Table of Contents

About the Authorxiii
About the Technical Reviewersxv
Acknowledgmentsxvii
Introductionxix
Chapter 1Introduction to Web Services1
Business Drivers5
Consumer Drivers8
Technology Developments9
Technology Problems11
Future Business for Finance14
Systemwide Integration in Finance15
Web Services Technology Requirements16
Mature Standards19
Simple Object Access Protocol (SOAP)19
Web Services Description Language (WSDL)20
Universal Description, Discovery, and Integration (UDDI) Registry22
Immature Standards23
Security23
Reliable Messaging24
Routing24
Orchestration and Workflow24
Activity Coordination24
Distributed Transactions25
Summary25
Chapter 2Enterprise Systems27
Monoliths28
Middleware29
CORBA30
Messaging34
Enterprise Architectures38
J2EE and WWW41
.NET and WWW46
Enterprise Operating Systems47
ERP Systems48
Summary49
Chapter 3Data Representation51
Data Standardization51
XML Files and Relational Data53
XML DTD54
DTD Elements55
XML Metadata56
Attribute Rules57
XML Schemas57
Namespace Definitions58
Schemas and DTDs59
Simple Types60
Separating Simple and Complex Types61
Creating New Types62
Groups63
Generating Objects Using XML64
SAX65
Generating Schema Code65
Sample Application68
Project70
Advanced Protocols/Languages70
Summary72
Chapter 4Messaging73
Simple Example73
SOAP Overview76
Message Envelope77
Message Header78
Message Body78
Message Fault79
SOAP Encoding79
Handles80
Structs81
Compound Variables82
Arrays83
Document/Literal Encoding86
SOAP with Attachments86
HTTP Binding87
RPC Example89
Software91
Project93
Summary93
Chapter 5Description and Data Format95
WSDL Overview95
WSDL Format96
Building Web Services99
Systems Integration108
FedEx Tracking108
Exchange Rate Conversion109
Software Packages113
Existing Interfaces115
Project115
Summary115
Chapter 6Discovery and Advertising117
Theory and Practice117
API Review121
White Pages121
Yellow Pages123
Green Pages124
Inquiry API126
Publisher API126
Schemas and APIs127
Commands128
Sample Clients128
Searching132
Case Study137
Project139
Summary140
Chapter 7Alternative Transports141
SMTP141
SMTP Commands143
Sample SMTP Session144
SMTP Headers146
POP147
IMAP148
MIME149
Subscription Example149
JavaMail151
Project158
Summary158
Chapter 8Security159
Security Requirements159
Integrity160
Authenticity161
Authentication163
Authorization164
Secrecy165
Trust166
Standards167
WS-Security168
The Specification169
Two-Factor Authentication171
Digital Signatures172
Data Confidentiality173
SAML174
Project179
Summary179
Chapter 9Quality of Service181
Theory and Practice181
System Status182
CPU182
Memory184
Storage185
Case Study186
Project201
Summary201
Chapter 10Conversations, Workflows, and Transactions203
Conversations203
Linking Services204
Structuring Conversations206
WSCL and WSDL207
WSCL Patterns208
Data Structures209
Grouping Interactions210
Transitions211
Conversations212
Business Process Execution213
Virtual Enterprises213
Web Services and Virtual Enterprises214
Automation216
Workflow Management Systems217
Transactions218
Summary220
Index223

Customer Reviews

Average Review:

Write a Review

and post it to your social network

     

Most Helpful Customer Reviews

See all customer reviews >

4 out of 5 based on 0 ratings. 2 reviews.
Guest More than 1 year ago
Dr. Watters takes a practical approach at developing Web Services application ¿ rather than theoretical conceptual approach to the topic. He approached the topic from both the J2EE and .NET programmer¿s point of view, and provides examples throughout the text that demonstrates both A) strengths and weaknesses of each platform for developing Web services, B) broad and yet finance-industry focused application of Web services. Examples demonstrated throughout the text are easy to follow and relate to. One example that is referred to often in the text related to checking balance of a band account and a more complicated stock trading application which the author used to demonstrate WDSL and UDDI examples. I had read a number of books on SOA and Web services in general, but I found the ¿how-to¿ approach of this book very helpful. Not that the author does not cover the basics of Web services, but he does so with demonstrating the concepts thru code samples and workable programs throughout the chapters. Background information on how and why Web services fit into the finance industry start the book ¿ followed by an introduction to why the current systems such as CORBA and various MOM¿s are not doing the job right now. He follows up with the basics of data representation: XML, DTD and XML Schema. These topics are covered very briefly, and can be skipped over. Messaging with SOAP is an essential part of Web services. All other protocols and layers rest atop of SOAP ¿ and messaging. Two subtopics are worth highlighting: SOAP binding with HTTP and the available software packages in .NET and Java. Later in the text, the author discusses other SOAP binding protocols such as SMTP, POP, JavaMail and IMAP. WSDL is needed to define the endpoints that represent services. Examples from the SOAP chapter are expanded to take into account WSDL and UDDI, in the chapter that follows. Security is an important topic and much more so in the finance industry. Authentication, Authorization, Secrecy and trust are some of the requirements that Web services security protocols need to fulfill. The problem with security standard is that there are too many of them: 7 protocols that cover the security aspects of Web services to be exact. The author covers these topics as they pertain to the finance industry and follows each discussion with the appropriate example. In about 200 or so pages, Paul covers the topic of Web services quite well. His examples are applicable to the finance industry and are very easy to follow. Even if you have read other books on Wed services, I highly recommend this book to you as it will make a very good edition to your book collection.
Guest More than 1 year ago
Watters suggests that developers should build applications that use relatively less CPU and relatively more bandwidth, to keep the network busy. He gives an example where a task takes 10 minutes to compute 1Gb of data and then takes 1 second to transmit it. So that CPU only uses its network for 1 second out of 600 seconds. He sees this as undesirable. On the contrary. the example shows an excellent optimisation of computation versus bandwidth. You WANT this situation. Also, if you are coding that application, and you can change it so that out of every 10 minutes of computation, it takes only 0.5 seconds to transmit that data, then you should do so. That is an improvement. In the example cited, the network is only using 0.16% of its capacity. 'Idleness of 99.84% is not effective resource utilisation'. He is quite correct about that. But wrong to suggest that therefore there is something wrong with that application. Rather, this lets many other computers, running instances of this application or other applications, share the network. In fact, purely from the vantage point of this application, it is good, because it helps the application scale to many instances of it on the same network. Plus, there is also the issue of latency. Even if the application puts out data at 1Gb/s, that data takes time to reach its destination. Even at the speed of light, this gives rise to times that are often long compared to those times for onboard computation on modern CPUs. Notice also that in many realistic caases, the data has to pass through switches and routers. Adds to the latency. Furthermore, the application would typically expect a reply from whereever it is sending the data so. More latency. Watters gives his example in the context of quoting George Gilder's law about bandwidth tripling every year. Gilder is (in)famous for saying this, and also saying that bandwidth is effectively free and infinite (or words to that effect). But this is often misunderstood by others, who ignore latency. All this goes to the core of the book. Web Services are fundamentally a distributed computation, often on machines at different companies, possibly separated by large distances. If you use this book to design a Web Service, it still behooves you to minimise the sizes of packets going on the net, between the different parties. And also to minimise the occasions (frequencies) on which these packets need to be sent. Both factors reduce the overall bandwidth usage and latency. Helps the scaling of your application.