WebSphere Process Server and WebSphere Enterprise Service Bus deployment patterns, Part 1, Selecting your deployment pattern
Finding the topology that is right for you requires an analysis of application properties and of non-functional requirements.
From the developerWorks archives
Date archived: January 4, 2017 | First published: November 08, 2006
Sorting through all of the deployment options that are available with WebSphere Process Server and WebSphere Enterprise Service Bus can be a daunting task. If you have a topology that accommodates any possible application, you can end up with more configuration than you require. However, if you customize the environment so that you have exactly what you need, you may need to spend more effort to gain knowledge than you can afford to spend. This article identifies deployment patterns that fall between these two extremes. These patterns may not be fully optimized to your needs, but they require much less analysis than a fully customized environment. In this article, we identify the application properties and availability expectations that you can use to select a specific deployment pattern. This article includes a downloadable reference guide that describes these deployment patterns and how the requirements map to them. You can use future articles in this series to guide you through the steps to create a deployment environment.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.