In an exclusive to the WebSphere Developer's Journal News Desk, Stefan Van
Overtveldt, program director, WebSphere Technical Marketing, IBM, commented
on the IBM vs Microsoft debate that's been raging over the superiority of
their respective platforms for creating Web services. He holds that
Microsoft's original white paper belittling WebSphere 4.0 was fatally flawed
from the start due to its premise, which, in his words, "is missing the
point." Before Van Overtveldt's complete response, let's look at highlights
of the verbal battle:
Microsoft launched the initial salvo with a white paper that compared the
creation of Web services (using the PetStore.com scenario) using Visual
Studio.NET versus IBM WebSphere v4.0. To support their claim that .NET has a
significant advantage over WebSphere, Microsoft hired an independent
consulting firm to develop a Web service with... (more)
The newly released version of IBM's WebSphere infrastructure software is
squarely aimed at the requirements of on-demand e-business. IBM WebSphere
Application Server, Version 5, and its development environment, WebSphere
Studio, Version 5, provide the standards-based infrastructure to integrate
business processes across the enterprise and with partners, suppliers and
customers. IBM WebSphere Version 5 is J2EE 1.3-certified, and is J2EE
1.4-ready since it supports the majority of technologies that will be part of
future releases of J2EE.
WebSphere will serve as the underlying universal platform for all of IBM's
on-demand software, tightly integrating with DB2, Tivoli, and Lotus. Version
5 includes the industry's broadest support for Web services standards.
WebSphere enables any application in the network - from Macromedia ColdFusion
applications to new Java applicati... (more)
Eclipse and IBM's open platform are helping to shape an exciting future for
WebSphere, according to the WebSphere marketing team, headed up by Scott
Hebner, director of marketing for WebSphere infrastructure software.
The WebSphere marketing team includes Joe Anthony, program director for
WebSphere Extensions marketing; Derek Bildfell, program director for business
development; Aimee Munsell, program director for WebSphere Application
Server; Bernie Spang, program director for WebSphere Studio marketing; and
Stefan Van Overtveldt, program director for WebSphere Technical Marketing.
WebSphere Developer's Journal editor-in-chief Jack Martin recently had the
opportunity to talk with Hebner and his team in a wide-ranging and exclusive
discussion. This third installment focuses on tools for rapid application
development, the broader development community, the need to addre... (more)
Written by IBM WebSphere experts, this book details how to develop, deploy,
and manage enterprise applications for version 5.0 of IBM WebSphere
Application Server. Over the course of the book, a large-scale e-commerce
application is developed, demonstrating the use of WebSphere Application
Developer Studio. The book also addresses other enterprise-level issues such
as the functionality of the application server, deployment topology, and
server administration. The following excerpt from Chapter 2 focuses on the
WebSphere programming model.
We examine many aspects of the WebSphere programming model in this book.
However, notwithstanding the breadth of coverage included in this book, the
total WebSphere programming model is larger than we can hope to address
between a single pair of covers. Fortunately, the majority of the WebSphere
programming model is based on open ... (more)
Java Developer Magazine on Ulitzer
IBM WebSphere started its Open Beta (Managed Betas are so 'last-year') for
the WebSphere Application Server Feature Pack for OSGi Applications and JPA
2.0 today. The Open Beta site is here. I'll list some of the highlights from
the Beta site as a teaser.
Highlights of the OSGi applications support delivered in the feature pack
(from the Beta Site ):
OSGi 4.2 Blueprint component model for declarative assembly, and simplified
unit test Extensions to the Blueprint component model for declarative
transactions, container-managed JPA and resource reference configuration
Isolated enterprise applications composed of multiple, versioned bundles with
dynamic lifecycle Module sharing between applications Module versioning
within and between applications Integrated bundle repository and ability to
configure the location of external repositori... (more)
IBM Session at Cloud Expo
From a constrained viewpoint, the WebSphere CloudBurst Appliance serves as a
virtualization management solution for WebSphere application environments. In
that light, I cannot tell you how many times customers ask me to delineate
WebSphere CloudBurst from the other virtualization management solutions that
are either out on the market or currently used in their business. I love to
hear this request for two reasons:
1) It signals that many enterprises already practice or are
thinking about virtualization in the application environment space.
2) I have a good answer!
To understand the main delineation between WebSphere CloudBurst and other
virtualization management solutions, it is probably helpful to understand
what the appliance does! Put simply and shortly, the appliance enables you to
create, deploy, and manage virtualized WebSp... (more)
Some things in WebSphere PortalServer work well and are well documented.
Other things are well documented and work well in theory. Still other things
have okay documentation and will work well when all of the WebSphere stars
are aligned. Depending on your implementation, Portal Clustering can fit into
all three categories.
Given the broad range of configurations open to an infrastructure planner
when dealing with WebSphere software, it’s no wonder there’s
often a great deal of confusion when it comes to making a complex product
like Portal highly available. Naturally, there’s no “Learn
Clustering in 20 Minutes” manual, but there are general steps to follow
and some to avoid.
Let’s start with a very basic explanation of the WebSphere cell and how
the Portal fits into it. (See Figure 1.)
A basic WebSphere AppServer in... (more)
The use of Lightweight Directory Authentication Protocol (LDAP) for WebSphere
authentication and authorization offers the advantages of single sign-on
across application servers and a vendor-neutral protocol and API.
Part 1 of this two-part series showed how to set up a directory and sample
application infrastructure for demonstrating WebSphere authentication using
LDAP. In Part 2 I take you through the process of setting up LDAP
authentication for WebSphere through the following tasks:
Defining roles and constraints in the Web application deployment descriptor
Mapping roles to LDAP group entries in the enterprise application deployment
descriptor Configuring WebSphere to use an LDAP principal registry
Demonstrating the secured application features enabled by WebSphere and LDAP
Locking down the LDAP and browser transports using SSL (Secure Sockets Layer)
Defining Web ... (more)
Lightweight Directory Authentication Protocol (LDAP) is often promoted as a
means to leverage an organizational directory as a principal registry for
WebSphere authentication and authorization. Advantages include the capability
to configure single sign-on across application servers, enabling additional
organizational applications, centralized user administration, multimastered
replication across authentication sites, and flexible, extensible data
formats - not to mention that LDAP is a vendor-neutral protocol and API
backed by IETF. This begs the question of how to implement WebSphere security
This two-part series presents a simplified example of how to configure
WebSphere Application Server version 5.0 to use IBM Directory Server v5.1 as
its user registry for J2EE application user authentication and role-based
authorization. This registry enables the... (more)
Last month, Jack Martin, editor-in-chief of WebSphere Journal, and Tom Inman,
vice president of product management and marketing, IBM WebSphere Software,
talked about the differences between WebSphere and WebLogic. This month, they
look at what's happening in WebSphere now, and plans for the future.
Jack Martin: What was your background? What did you do before you did this?
Tom Inman: I joined sales and marketing right out of college and have been
here ever since.
JM: What school did you go to?
TI: I went to Michigan State University, where I earned a Bachelor of Science
in engineering and an MBA in marketing and finance. I needed money to pay for
school and I landed an internship with IBM just outside of Michigan State in
Lansing, Michigan. I hit it off with the branch manager and the sales manager
very well. They tried to hire me before I finished school and they were... (more)
Related Links How Low Does BEA Have to Go? How Long Can BEA Survive, Industry
Asks Why WebSphere? A Successful Ingredient Offers Choice A Leader with New
After talking with Tom Inman (see page 6), Jack Martin also spoke to Devi
Gupta, director of Strategic Marketing at Prolifics, about IBM WebSphere and
WJ: Devi, as Director of Strategic Marketing for Prolifics, What's a typical
day like for you?
DG: Well, have you seen the IBM commercials that are on TV? I think a lot of
companies that hear those messages feel that vision - the On Demand vision -
is perhaps beyond them. I am Prolifics' messenger. One of my key goals, and
the goals of my team, is to spread the word - let all the medium-size
businesses know that Prolifics can make their On Demand solutions a reality -
let all the larger enterprises know that Prolifics is "the" WebSphere expert... (more)