WebSphere

Subscribe to WebSphere: eMailAlertsEmail Alerts newslettersWeekly Newsletters
Get WebSphere: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories

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. De-Mystification 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)

Implementing WebSphere Security Through LDAP

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)

Implementing WebSphere Security Through LDAP

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 through LDAP. 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)

WebSphere Journal Exclusive Interview: What's Happening in WebSphere

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)

IBM Responds to Microsoft's Jabs at WebSphere 4.0

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)

Partners Compare WebLogic and WebSphere: An Exclusive Interview with Devi Gupta of Prolifics

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 Customers 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 BEA WebLogic. 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)

Leverage Existing WebSphere Application Server J2EE Resources

By accessing the IBM WebSphere Application Server JNDI tree, WebSphere Application Server Community Edition (IBM's free, lightweight J2EE application server built on Apache Geronimo technology) can interact with and reuse virtually any of the J2EE resources that are housed there. It is not uncommon for enterprises to leverage different application server flavors throughout their organization to accommodate a variety of business objectives. A case in point might be a company that primarily runs IBM WebSphere Application Server V6, but has a business need to run IBM's cost-free WebSphere Application Server Community Edition as well to power the myriad of J2EE applications running throughout the enterprise. Code reusability is a key programming principle that supports such an environment, enabling you to lower programming costs and exploit existing code assets at the ... (more)

Migration: From Here to There to WebSphere

Why migrate to WebSphere v5? Whether you are currently using WebSphere v3.5 or v4, or are using a different J2EE application server altogether, there are many reasons that justify the move. First there is the corporate choice - when choosing WebSphere you are choosing IBM. This means that you benefit from their reputation for superior support and their rather vast portfolio of software options. You also benefit from the level of investment they are putting into WebSphere, which equals more than the annual revenues of some of their competitors. Next there is the technology choice. Certainly, by moving to the latest and greatest, you can take advantage of all its advancements and new features, which should match your growing business and technical needs. Additionally, WebSphere probably averages out to a lower cost of ownership than most of its competitors. Compared t... (more)

Using the IBM WebSphere Application Server, Advanced Edition

In previous chapters, we learned how to use the IBM WebSphere Test Environment (WTE) inside VisualAge for Java to create and to test servlets. Now we need to understand how to use our servlets outside a test environment. This can be accomplished by deploying our servlets to the IBM WebSphere Application Server, Advanced Edition (WASAE). The WTE is used at development time, whereas the WASAE is used for staging or production purposes. About the Book Enterprise Javatm Programming with IBM WebSphere (with CD-ROM) By Kyle Brown, Gary Craig, Greg Hester, Jaime Niswonger, David Pitt, Russell Stinehour Addison Wesley Professional ISBN 0201616173 $44.95 You may purchase this book with a 10% discount at: www.informit.com/promo/wsdj The IBM WebSphere Application Server, Advanced Edition, provides the necessary tools to deliver J2EE-based applications. The IBM WASAE allows a ma... (more)

IBM WebSphere Application Server: The Complete Reference

Diogenes is a startup software manufacturing company that develops products to integrate applications over the Internet. We were looking for a book to help us integrate our product, iMercury, into IBM's WebSphere Application Server. iMercury is a 100% Internet-designed Java messaging product that is lightweight, self-configuring, RSA security-enabled, and provides automated installation and configuration. I stumbled onto Ron Ben-Natan and Ori Sasson's IBM WebSphere Application Server: The Complete Reference. Given my pleasant experience with their previous book, IBM WebSphere Starter Kit, I felt that this would be a good reference source for the WebSphere Application Server. But they lied! The title misrepresents the book. It's much more than a complete reference for IBM WebSphere Application Server. It covers the entire WebSphere brand and the Internet technologie... (more)

Understanding Tivoli Access Manager for WebSphere Application Server

J2EE Security provides a mechanism called EJBRoles that can be used to provide security for applications running in J2EE-compliant application servers, including WebSphere Application Server. Use of EJBRoles requires that users, or groups of users, be mapped to EJBRoles so that WebSphere can perform security checks when applications are running. It is common to find several WebSphere environments in a large organization. Management of EJBRoles across these environments can become complex and expensive. IBM's Tivoli Access Manager provides a software component that can be integrated with WebSphere Application Server to provide centralized management of EJBRoles. When WebSphere is configured with this component it relies on Tivoli to determine if access to an EJBRole is allowed. This article describes how Tivoli Access Manager (TAM) for WebSphere Application Server w... (more)