Bassem Jamaleddine

Subscribe to Bassem Jamaleddine: eMailAlertsEmail Alerts
Get Bassem Jamaleddine: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by Bassem Jamaleddine

In this article, the first part of a two-part series, I will present WASLED/WASMON, a WebSphere monitoring application, and show you how you can use it to monitor WebSphere Application Server and to plan a WebSphere risk management procedure. I will discuss some of the system resources that need to be made available to ensure the operability of WebSphere Application Server. You will learn how to configure WASMON to ensure that these resources are available and up and running. I will show you how to prepare the essential recovery scripts and make them available within the WASMON repository so you can trigger specific actions upon failure notification. You will then learn how to communicate with WASMON via the Internet to initialize an administrative action. In this article I use the example Web application WASDG, which was used throughout my book, IBM WebSphere Appli... (more)

WebSphere Risk Management

In part one of this series on risk management (WSDJ, Vol. 2, issue 4), I introduced the WASLED/WASMON application. In this article I will discuss how to initiate the takeover of a failing WebSphere server by a redundant server, and how to compile and deploy a Web application on this redundant server automatically. Recall the WebSphere region setup shown in Figure 1. The failing server, node1.tcnd.com, has been detected as malfunctioning by the WASMON supervisor and is to be replaced by node2.tcnd.com. WASMON will notify the roaming operator; for example, it will send an e-mail t... (more)