IBM is one of the most dominant players in the push for Web services. It's
therefore not surprising that much of the Web services work done by the
company has been incorporated into their flagship product - the WebSphere
Application Server.
As of version 4, support for Web services is incorporated into every level of
WebSphere. This means that a few of the Web services libraries come with the
WebSphere Application Server. Specifically, support for SOAP and UDDI4J are
both an integral part of the WebSphere Application Server and used for
implementing Web services, servicing calls made using SOAP, making calls to
other Web services, and allowing applications deployed over WebSphere to
interact with UDDI registries - both for discovering and publishing services.
The support provided for Web services within WebSphere focuses on the
deployment aspects only. The focus on ... (more)
There are a number of skeletons in the closets of today's telecommunication
service providers. One of the scariest is that most service providers cannot
successfully deliver on the promises they make as service-level commitments
to their customers. Not do not or will not. Cannot. For many reasons,
successful service-level management in the competitive telecom arena remains
a theory - full of unfulfilled potential and many broken promises.
The OSS
When I was younger I had a sign on my monitor that read "to err is human; to
really make a mess requires a computer." This is a bit misl... (more)
In my last article (WSDJ, Vol. 1, issue 4) I showed you how to use WebSphere
Studio Application Developer (WSAD) to develop and publish a Web service. You
saw how to use the Web services wizard to wrap an existing Java method as a
Web service and expose the metadata required for invoking the service. You
also saw how the UDDI Explorer is used to publish your service on a public
registry so others can find and use it. This month's focus is on discovering
the service and building a client that invokes the Web service. You'll learn
more about how WSAD hides the complexity and mechan... (more)
Every computer science undergraduate program in the world has two important
foundation courses: data structures and algorithms. Open any book on these
subjects and you'll see immediately that almost a third of it is devoted to
graphs. Graphs are used to model a very large number of real-world problems:
the traveling salesman problem, efficient routing of a package, network
flows, and more - all are modeled as graphs and often solved by graph-based
algorithms.
A common use of a graph-based representation is that of a computation graph.
Simply put, it's a graph that models a set o... (more)
In my previous article (WSDJ, Vol. 1, issue 7), I gave you a glimpse of the
Web Services Object Runtime Framework (WORF), a set of tools for implementing
Web services with DB2 and WebSphere. WORF is deployed on WebSphere
Application Server (WAS) and uses Apache SOAP 2.2. It implements a layer that
runs on WAS and is responsible for taking database access definitions and
translating them on-the-fly to Web services constructs supporting SOAP
messages and WSDL documents.
The mapping between the database definitions and the Web service is done in a
Document Access Definition eXtensi... (more)
Ron Ben-Natan is Chief Technology Officer at ViryaNet Inc. Prior to that he worked for companies such as Intel, AT&T Bell Laboratories, Merrill Lynch and as a consultant at J.P. Morgan. He has a Ph.D. in Computer Science in the field of distributed computing and has been architecting and developing distributed applications for over 15 years. His hobby is writing about how technology is used to solve real problems and he has authored numerous books including “IBM WebSphere Application Server: The Complete Reference” published by Osborne/McGraw. He can be reached at
David Lucas
Shaul Efraim
Terence Martin Breslin
Cory Marchand
David Hughes
James Carlini
John Iffert
Dan Stolts
Joe Zeto
