Technical library

IBM Tivoli Service Automation Manager (TSAM) V7.2.2 introduces the extension: A set of TSAM software components that can implement a new IT service automation solution (known as a service definition) or add capabilities to existing service definitions. In this article, the authors explain how to tune the load balancer policy to your system's needs; how to add and remove application servers as the workload of the business application changes; and how to modify the firewall rules and why you might need to do that.

Discover best practices and tools for creating continuous improvement for transaction response times, as well as, initial hardware procurement performance evaluations for IBM WebSphere Application Server 7 and POWER7 architectures with IBM Tivoli Monitoring.

How can your company experiment with new technology without spending too much on IT resources? The answer is open source sandboxes that allow small pilot deployments of different applications for testing and evaluation. In this first part of a two-part series, we will show you how open source tools and IBM Tivoli Provisioning Manager can be used to construct a sandbox for testing pilot deployments of applications. No prior sandbox experience is necessary.

회사에서 어떻게 IT 자원에 너무 많은 비용을 지출하지 않고 신기술을 실험할 수 있을까요? 그 해답은 테스트와 평가를 위해 서로 다른 애플리케이션들을 작은 규모로 파일럿 배치할 수 있게 해주는 오픈 소스 샌드박스입니다. 2편 시리즈 기사 중 첫 번째인 본 기사에서는, 오픈 소스 도구와 IBM Tivoli Provisioning Manager를 사용하여 애플리케이션의 파일럿 배치를 테스트하기 위한 샌드박스를 생성할 수 있는 방법을 설명할 것입니다. 이전에 샌드박스 관련 경험이 없어도 상관없습니다.

The LDAP wrapper is a pure Java package that is based on InfoSphere Federation Server Java wrapper SDK technology. By providing read-only access to LDAP directory servers in an SQL environment, the LDAP wrapper facilitates the integration and connectivity between business data in a relational database and human resource data in the LDAP directory server.

This demo explores how a SaaS service provider can meter and bill usage of multi-tenant Web services and related resources like databases, portals and LDAP directory server, by users belonging to multiple tenants. A scenario is shown where IBM Tivoli Usage and Accounting Manager (ITUAM) and a Java Management eXtension (JMX) based usage logging component is used to meter the usage of Web services and its resources. IBM Tivoli Usage and Accounting Manager job files and report server is used to generate billing invoices, usage metrics, and graphs for tenants.

TFIM 6.2 provides an OSGi (Open Services Gateway Initiative) extension point for custom plug-ins for STS modules. In this tutorial, we will walk through the complete development process for creating a custom STS plug-in for Tivoli Federated Identity Manager (TFIM) 6.2. Customers might develop their own STS plug-ins for a variety of reasons including advanced user mapping and attribute gathering capabilities, or to support validation or issuing of proprietary security token types. This tutorial will use as a working example a simple mapping module which adds a configurable name/value parameter pair as an attribute to the TFIM Trust Service's STSUniversalUser.

Web applications providing gateway access to LDAP services, such as an enterprise-wide phone and mail directory, are usually designed to authenticate using an LDAP "superuser" account. As a result, the user reads and updates the directory according to the rights of that high-privileged account instead of his/her own LDAP privileges. IBM Tivoli Directory Server offers a powerful feature, known as proxied authorization (RFC 4370), which enables programmers to write applications that authenticates themselves using a specific account but operates on behalf of the real user, thus delegating all privilege enforcements to the LDAP server.

Get the most out of the Log and Trace Analyzer for Java Desktop (LTA-JD) using this four-part series as an overview, installation, and configuration usage guide. This series explains how your data can be more consumable from start to finish, as well as how to reduce your problem determination and maintenance costs. The series includes an installation/configuration/customization/usage/troubleshooting guide, performance-enhancing tips, integration and hands-on scenarios, and data on the IBM Tivoli Monitoring 6.1 Events Tool. This article, the series finale, explains how to run the LTA-JD from the IBM Tivoli Monitoring 6.1.

This four-part series is a comprehensive usage guide that gives you an overview of the Log and Trace Analyzer for Java Desktop, instructs you in the installation process and teaches you to configure the tool correctly. The series includes performance-enhancing tips, integration and hands-on scenarios, as well as data on the IBM Tivoli Monitoring 6.1 Events Tool. Discover how your data can be more consumable from start to finish and learn how to reduce your problem determination and maintenance costs. In part three, go on a visual tour of the technology (a screenshot is worth a thousand words), gain troubleshooting tips, and learn how to get the best performance out of the LTA-JD.

This four-part series is a comprehensive usage guide that gives you an overview of the Log and Trace Analyzer for Java Desktop, instructs you in the installation process and teaches you to configure the tool correctly. The series includes performance-enhancing tips, integration and hands-on scenarios, as well as data on the IBM Tivoli Monitoring 6.1 Events Tool. Discover how your data can be more consumable from start to finish and learn how to reduce your problem determination and maintenance costs. In part two, get an overview of the LTA-JD, discover an installation and configuration guide for the tool, and view a table of the main functions of the tool.

The huge amount of data to analyze after system failures poses the initial difficulty in problem determination -- this is especially true when the failures are related to concurrent usage and stress. The Log Trace Analyzer for Java Desktop (LTA-JD) is a powerful tool for problem determination and analysis once the text logs are properly extracted as Common Base Events. But what's the easiest way to extract, say, Java Virtual Machine (JVM) logs from the WebSphere Application Server (WAS) so they can be used by the LTA-JD? This article introduces the design of a custom static parser as a plugin for LTA-JD to construct a meaningful, common language from the plain text WebSphere Application Server JVM logs.

Do you want to evolve from creating WSDM-compliant projects with Apache Muse to creating WSDM-optimized projects? Any new user can use Apache Muse to design the Web services interface for a manageable resource, generate the necessary Java code, and build a deployable artifact with little thought towards the underpinnings of the Apache Muse runtime. But if you are creating Web services to expose a large number of manageable resources or even just a single resource that is fairly complex, it pays to understand the core concepts behind the Muse programming model. Read this article, and the following tutorial, to discover the core concepts that will take you from creating WSDM-compliant projects with Muse to creating WSDM-optimized projects with Muse.

Learn to design and develop a system with multiple manageable resources without resorting to lots of cut-and-paste hacks. With the help of WSDLMerge, an overlooked tool in the Apache Muse project arsenal, you can discover best practices for creating manageability interfaces that are optimized for reuse.

This four-part series is a comprehensive usage guide that gives you an overview of the Log and Trace Analyzer for Java Desktop, instructs you in the installation process and teaches you to configure the tool correctly. The series includes performance-enhancing tips, integration and hands-on scenarios, as well as data on the IBM Tivoli Monitoring 6.1 Events Tool. Discover how your data can be more consumable from start to finish and learn how to reduce your problem determination and maintenance costs. In part one, identify the challenges in data collection and see how a common event format and a symptom repository help address those challenges.

As a workload manager (and not a capacity planning tool), the IBM Enterprise Workload Manager focuses on real-time data and, thus, only retains performance data covering the past 24 hours. There was a customer requirement, however, to have this data available for later analysis. And so, the Data Hardening plug-in was added. This plug-in allows on-the-fly dumping of performance data onto the file system. But, the dumped data can't be directly exploited: Enter EWLM Report Data Analyzer.

This article introduces readers to the world of extended operations in IBM Tivoli Directory Server (ITDS). The article makes users aware of extended operations using examples in the Java Naming and Directory Interface (JNDI).

When you've built your Web Services Description Language (WSDL), this quick tip will remind you to how to map your interface to httpd-specific commands and settings using the Muse code-generation tool, WSDL2Java.

The Web Services Distributed Management (WSDM) Event Format (WEF) is an OASIS standard that describes how to serialize events related to systems management in XML. The standard goes into detail about required values, optional values, and the semantics of both, but it offers no instruction for actually implementing the system. Fortunately, the Apache Muse project has an implementation of WEF that lets you create, send, and receive WEF events using a simple Java API. This article shows you how to handle these tasks from within an Apache Muse application.

When you're building a Web Services Distributed Management (WSDM)-compliant interface for a manageable resource with Apache Muse, these four simple steps will guide you in designing the necessary Web Services Description Language (WSDL).

Achieve data security over open communications channels with Secure Sockets Layer (SSL), which provides encryption, certificate-based authentication, and security negotiations. This article, part one of a three-part series, describes SSL and explains why you should implement it on your Integrated Solutions Console. In parts two and three, follow a step-by-step guide to learn how to implement SSL on the Integrated Solutions Console versions 5.1 and 6.0.1, respectively.

Explore a sample symptom catalog and related events that illustrate how the IBM Log and Trace Analyzer (LTA) can help you diagnose software problems when they span multiple systems. This article introduces the LTA and illuminates its problem determination features; discusses symptoms, symptom definitions, events, and the event-symptom relationship; and explains the complexities of multievent symptom management.

The IBM Autonomic Integrated Development Environment (AIDE) facilitates a model-driven approach to touchpoint development, which is a useful, factory-style, wizard-assisted pattern for producing generic touchpoints. However, at some point in the AIDE-driven workflow, the touchpoint must be made specific to a given application. You can do this either at the model design stage or manually through hard-coding. In this tutorial -- the seventh in the series -- discover techniques for creating both generic and specific touchpoints, and learn how to produce touchpoints that have the right mixture for a given management application.

This tutorial -- the sixth in the series -- introduces two key elements of the IBM Autonomic Integrated Development Environment (AIDE): Apache Tomcat and Axis. Discover tooling-related gaps that the AIDE online help doesn't cover so that you can become more comfortable with the way the toolkit uses the standard open source components.

This tutorial -- the fifth in the series -- illustrates the management of Apache Derby databases using touchpoint technology. Learn how to use a touchpoint that contains a working instance of Derby, and work through a management interface to a Derby database instance as a Web service-based managed object. You interact with this touchpoint using the Autonomic Integrated Development Environment (AIDE) resource browser and a Derby Java client program.

This tutorial, the fourth in the series, describes how to create a touchpoint that maps instrumented notifications into their touchpoint equivalent. The previous tutorial in this series described how to implement simple GET and SET operations in the touchpoint. This tutorial completes the picture by adding notification handling and paves the way for more complete interaction between your touchpoints and the underlying managed resources. You also learn how to programmatically manipulate a set of touchpoints which lays the foundation for creating a simple autonomic manager.

This tutorial, the third in a series on the IBM Autonomic Integrated Development Environment (AIDE), describes a basic touchpoint interface for a managed resource. Discover how Eclipse supports the workflows for such development with TODO items and learn how to provide a touchpoint-based platform for arbitrary managed resource management -- a topic that has dogged the telecom and enterprise management arenas for decades.

This tutorial -- the second in series on AIDE -- moves beyond the basics of building touchpoints using the IBM AIDE toolkit and covers the use of events and IT management technologies (specifically the Java Management Extensions) and demonstrates how to connect external value-added Java tools to autonomic computing touchpoints. I'll focus on how to tackle the problem of linking autonomic computing touchpoints with external JMX-instrumented software.

This tutorial, the first in a series on the IBM Autonomic Integrated Development Environment (AIDE), shows how you can get up and running quickly with the IBM AIDE toolkit. Discover touchpoint creation, modification, and deployment and learn about the internals of the touchpoint in relation to the underlying model.

The kind of consideration you give to maintaining your Web site after it is launched is just as important as the effort you put into developing it in the first place. Here are some monitoring strategies that you can use them to keep your investment healthy and your venture successful.

Autonomic computing and an array of unprecedented operational features make IBM WebSphere Extended Deployment a revolutionary product. Even more impressive, WebSphere XD and its intelligent new routing engine, the On Demand Router, offer network designers amazing new topology options that were previously unavailable. This article describes how WebSphere XD exceeds the current expectations of a highly available environment.

The advanced authentication features in IBM WebSphere Application Server V6 support a more flexible authentication model with a new, highly customizable authentication framework that is based upon -- and extends -- Java Authentication and Authorization Service (JAAS).

Write and run simple business rules or complex inferencing rules using the Agent Building and Learning Environment (ABLE) and its ABLE Rule Language (ARL). Example rulesets show ARL's syntax and capabilities, how to work with Java objects from ARL, how to write and debug rules in Eclipse, how to run rulesets from Java applications, demonstrate procedural and inferencing rule engines, and see the benefits of using rules written for inferencing rule engines.

Learn how the Generic Log Adapter lets you embed class callouts. Using these callouts you can customize the parsing component of the Generic Log Adapter. The article discusses how class callouts work and develops some examples with the correct rules to invoke them.

The Autonomic Management Engine, a primary component of the IBM Autonomic Computing Toolkit, allows the use of JavaScript to define decision tree scripts that can be used for analysis, planning, and so on. Given that Java code is more powerful than JavaScript, it might be preferable to use Java code for creating the analysis components, whereas JavaScript might be suitable when simpler functionality is required. This article shows you how to call Java classes from the decision tree scripts as well as the associated setup. It also provides some guidance on issues that can potentially cause your decision tree scripts to fail and hints on what you can do to smoothly integrate Java code with the decision tree script.

Cross-site scripting is a potentially dangerous security exposure that should be considered when designing a secure Web-based application. In this article, Paul describes the nature of the exposure, how it works, and has an overview of some recommended remediation strategies.