 |
|
|
|
|
|
Ajax in a network: Security and topology challenges of aggregating content from multiple sites
in an Ajax architecture
There can be challenges when introducing Asynchronous JavaScript and XML
(Ajax) programming techniques into a network environment. This article looks
at security and topology scenarios that you might be trying to solve when
creating Ajax style architectures that aggregate content from multiple sites.
This article explores these scenarios using the IBM Tivoli Access Manager
WebSEAL product in conjunction with the IBM WebSphere Application Server
Feature Pack for Web 2.0 for developing Ajax style architectures for WebSphere
Application Server.
|
|
Articles |
|
30 Sep 2009 |
|
| |
IBM SOA Foundation product integration: A complete ESB Gateway solution featuring WebSphere DataPower, Tivoli Access
Manager, and WebSphere Service Registry and Repository
Leveraging the concept of a service-oriented architecture usually brings
with it the ability to connect an increasing number of systems within an enterprise
-- but also across enterprises. While enabling a higher degree of automation and
reduced processing time, this also leads to growing concern about managing and
securing the underlying connections between heterogeneous IT systems. This article
describes how to address these concerns by implementing an ESB gateway using three
of the products within the IBM SOA Foundation platform, beginning with integrating
a IBM WebSphere DataPower SOA Appliance with IBM Tivoli Access Manager for security,
and then adding IBM WebSphere Service Registry and Repository for endpoint address
management.
|
|
Articles |
|
10 Dec 2008 |
|
| |
Software as a service: Usage based metering and billing for multi-tenant Web service resources using IBM Tivoli Usage and Accounting Manager
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.
|
|
Demos |
|
12 Sep 2008 |
|
| |
IBM SOA Foundation product integration: Managing your WebSphere-based SOA solution
As more companies are putting service oriented solutions -- including a portfolio of services -- into production, the role of managing of these solutions becomes increasingly important. This ranges from monitoring individual services with respect to their associated service level agreements and the discovery of ”rogue” services that do not follow established protocols, all the way to the active management of an entire environment of applications, servers, and the networks that connect them. This part of our series on integrating products of the IBM SOA Foundation looks at how to manage a WebSphere-based SOA solution with IBM Tivoli Composite Application Manager for SOA.
|
|
Articles |
|
18 Jun 2008 |
|
| |
Use ARM to monitor SCA invocations in IBM WebSphere Process Server
V6.1, Part 2: Understand SCA invocation patterns and debug asynchronous scenarios
In Part 1 of this series, you learned about Application Response Measurement
(ARM) and debugging synchronous scenarios using IBM Tivoli Composite Management for
Response Time Tracking. Now get an introduction to the multiple Service Component
Architecture (SCA) invocation patterns and the related ARM observation points to
better understand the relationship between the ARM transaction and SCA invocation.
This article, Part 2 of the series, also shows some examples of how to debug
asynchronous scenarios using Tivoli Composite Management for Response Time Tracking.
|
|
Articles |
|
05 Jun 2008 |
|
| |
Use ARM to monitor SCA invocations in IBM WebSphere Process Server
V6.1, Part 1: Debug SCA invocations using IBM Tivoli Composite Application Manager for
Response Time Tracking
This two-part series shows you how to monitor Service Component Architecture
(SCA) invocations using the Application Response Measurement (ARM) standard in IBM
WebSphere Process Server V6.1. You can use an ARM implementation, such as IBM Tivoli
Composite Application Manager for Response Time Tracking, to generate a graphic view
of SCA invocations. This article, Part 1 of the series, starts by describing ARM and
showing you how to debug synchronous scenarios using Tivoli Composite Application
Manager for Response Time Tracking. In Part 2, you get an introduction to SCA
invocation patterns and learn how to debug asynchronous scenarios.
|
|
Articles |
|
29 May 2008 |
|
| |
Software as a Service: Web service mediation patterns for dynamic routing of multiple tenant requests using WebSphere DataPower SOA Appliances
Explore one of three IBM middleware based mediation patterns for rapid
enablement of multi-tenancy for existing Web services implementations. This first
pattern demo uses WebSphere DataPower Appliances.
$@!LessThan!@$!--
The remaining two patterns will show the
use of WebSphere Business Services Fabric and WebSphere Enterprise Services Bus.--$@!GreaterThan!@$
In this demo, a scenario shows where multi-tenancy is enabled for a existing single tenant credit
check service by introducing a WebSphere DataPower Appliance based mediation pattern layer. This pattern layer uses a WebSphere DataPower Appliance Web service proxy and simple XSL routing policies to route service invocations from a tenant bank's user to endpoints dedicated to that tenant. The proxy also authenticates and authorizes users against policies configured in Tivoli Access Manager.
|
|
Demos |
|
16 May 2008 |
|
| |
Software as a Service: Simplified tenant provisioning using IBM entry level middleware
This demo focuses on the ease of provisioning new tenant banks in a sample
banking application through the use of Apache ANT scripts and a few portlets for the
administrator roles. A new WebSphere Application Server Community Edition virtual
host and security realm are provisioned through ANT scripts invoked from a new
service provider administrator portlet. A new openLDAP user database is created and
new LDAP Data Interchange Format (LDIF) files imported through another ANT script. The portal for the new tenant bank is customized through a tenant administrator portlet by modifying style sheets, providing tenant specific images and uploading and deploying these to the running application. Custom fields are added to other portlets which use XML columns defined in DB2 Express-C V9 through simple configuration steps in a tenant administrator portlet.
|
|
Demos |
|
16 May 2008 |
|
| |
Integrating IT monitoring and business activity monitoring
Learn how you can monitor IT and business activities on a single dashboard
by converting ITCAM for SOA events for display and processing by WebSphere Business
Monitor. Three sample scenarios illustrate how to define monitor models to configure
WebSphere Business Monitor.
|
|
Articles |
|
16 May 2008 |
|
| |
Build a custom static parser plugin for LTA-JD
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.
|
|
Articles |
|
17 Jul 2007 |
|
| |
Designing manageable resources with Apache 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.
|
|
Tutorials |
|
10 Jul 2007 |
|
| |
Designing manageable resources with Apache Muse
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.
|
|
Articles |
|
03 Jul 2007 |
|
| |
Craft custom query dialects with Apache Muse
The Apache Muse project provides an implementation of WS-ResourceProperties
(WSRP) that includes support for QueryResourceProperties and XPath queries. The
project also has an API that allows you to add support for your own query languages.
Learn how to add this support using just a little Java code. In addition, review all
of the different filtering options available with the project and see how you can
leverage them in your Muse-based Web-service endpoints.
|
|
Articles |
|
26 Jun 2007 |
|
| |
Enabling WSDM Advertisement with Apache Muse
One of the most powerful features of the WS-DistributedManagement (WSDM) standard is the Advertisement capability -- it defines a standard for notifications describing the life cycle of a manageable resource. When combined with WS-Notification (WSN), WSDM Advertisement can help solve one of the trickiest problems in a self-managing IT system -- how to "bootstrap" the system by alerting management clients to the manageable resources they should be monitoring. Today this configuration can be done with manual intervention and the hardcoding of resource information, but this does not make for a very adaptable system. In this article, the author will show how manageable resources that are implemented with Apache Muse can take advantage of its WSDM Advertisement features to make startup and discovery a more dynamic and flexible process.
|
|
Articles |
|
12 Jun 2007 |
|
| |
Three keys to enable a WSDM/Apache Muse metrics reporting system
WS-DistributedManagement (WSDM) is an OASIS standard that defines Web service
interfaces for the most fundamental parts of a manageable resource. Part of the WSDM specification is about metrics, or resource properties whose values are collected over a period of time; examples of Web service metrics might be the number of requests handled per minute, the amount of disk space consumed per day, or the percentage of transactions that failed due to server timeouts. This article explains three important tasks associated with using WSDM metrics -- deciding which of your resource properties should be metrics, leveraging Apache Muse to create metrics, and evaluating metric values from a Web service client.
|
|
Articles |
|
05 Jun 2007 |
|
| |
Define, configure, and process topics for notification producers
WS-Notification (WSN) is an OASIS standard that describes, among other things, a
system for categorizing the types of notifications that are emitted from a manageable
resource. By grouping notifications into categories, the designer of a resource's Web
service interface makes it much easier for clients to find the data they need while
ignoring data that is irrelevant. The Apache Muse project contains an implementation of
WS-Notification, including all of the topic data structures and processing logic described
in the specification. This article reviews how to define and configure topics for your notification producers, as well as how to process topic-based notifications in your notification consumers.
|
|
Articles |
|
29 May 2007 |
|
| |
Monitor a WSDM resource with Tivoli Monitoring Universal Agent
Discover how you can use the IBM Tivoli Monitoring (ITM) Universal Agent to
consume and monitor a Web Services for Distributed Management (WSDM)-compliant interface for a manageable resource. Learn how to download, install, and configure the ITM Universal Agent to monitor the Apache HTTP Server.
|
|
Tutorials |
|
22 May 2007 |
|
| |
Optimal message processing with WS-Notification filters
WS-Notification (WSN) is an OASIS standard that describes a system for subscribing to and receiving notifications from a manageable resource; these notifications may reference changes in state, fatal errors, status updates, and more. The standard also describes a way of filtering notifications so that clients can specify a subset of a resource's notifications that they are truly interested in. The Apache Muse project contains an implementation of WS-Notification that includes all of the filtering options. This article reviews all of the different filtering options, the positives and negatives of each, and shows you how you can leverage them in your Muse-based Web service endpoints.
|
|
Articles |
|
08 May 2007 |
|
| |
Autonomic computing tip: So you're building a WSDM interface
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.
|
|
Articles |
|
24 Apr 2007 |
|
| |
Enforce resource property semantics with metadata
The WS-ResourceProperties specification defines a standard for declaring strongly-typed properties as part of a Web service interface, but it does not say anything about permissions, validation, and other important topics. Fortunately, the WS-ResourceFramework authors have provided a new specification, WS-ResourceMetadata, that can help you deal with these issues in a standard way. The Apache Muse project provides implementations of both of these specs and lets you associate metadata with your resource properties with just a small XML file. This article describes how to use metadata to secure and validate your properties and how to test different metadata settings.
|
|
Articles |
|
24 Apr 2007 |
|
| |
Muse and WEF eases event reporting
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.
|
|
Articles |
|
03 Apr 2007 |
|
| |
Autonomic computing tip: So you are building a WSDM interface
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).
|
|
Articles |
|
20 Mar 2007 |
|
| |
Put Muse and Eclipse TPTP WSDM tools to work
Learn how to install Apache Muse, the stable release of the Web Services Distributed Management (WSDM) Tooling in Eclipse TPTP 4.3, and the latest development builds of WSDM Tooling in TPTP 4.4. With this tutorial, a stand-alone "prequel" to the tutorial on crafting a WSDM endpoint using the Eclipse TPTP Build to Manage tooling, you'll be a master of installation.
|
|
Tutorials |
|
13 Mar 2007 |
|
| |
Meet the specs: WS-RT 1.0 operations, Part 3
Meet the WS-ResourceTransfer 1.0 initial draft specification, a proposed
open standard that extends certain operations by allowing fragments of XML code in a
single resource to be addressed instead of having to affect the entire resource. This
article provides a closer look at how the WS-ResourceTransfer 1.0 specification handles faults.
|
|
Articles |
|
06 Mar 2007 |
|
| |
Create a WSDM endpoint using Build to Manage tooling from the Eclipse TPTP project
Build a Web Services Distributed Management (WSDM) interface for the Apache HTTP server without having to worry about Web services artifacts like Web Services Description Language (WSDL) and schema files, using refreshed tooling for WSDM in the Eclipse open source project. In a previous tutorial, you learned how to accomplish this task by hand coding the artifacts required by the Apache Muse run time and using the command-line utilities in Muse. In this tutorial, you do the same but in a faster, easier way. By the end of this tutorial, you will be accomplished at using the tooling integrated into Eclipse to model, generate, and test WSDM interfaces.
|
|
Tutorials |
|
13 Feb 2007 |
|
| |
Why open source for the WSDM open standard?
Get an overview of the run time and tooling for Web Services Distributed Management (WSDM) available in the Apache Muse and Eclipse TPTP (Test and Performance Tools Platform) projects. This article is a companion to the tutorial on creating a WSDM interface and also describes the motivation of building this in open source. Learn how you can influence both the development of the run time and the tooling. In this article, I share with you my personal views on why open source is the best avenue to develop implementations of the WSDM open standard.
|
|
Articles |
|
13 Feb 2007 |
|
| |
Meet the specs: WS-RT 1.0 operations, Part 2
Meet the WS-ResourceTransfer 1.0 initial draft specification, a proposed open standard that extends certain operations by allowing fragments of XML code in a single resource to be addressed instead of having to affect the entire resource. This article provides a closer look at how the WS-ResourceTransfer 1.0 specification extends the Create operation.
|
|
Articles |
|
06 Feb 2007 |
|
| |
Hit the ground running with AIDE, Part 7: Better IT 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.
|
|
Tutorials |
|
19 Dec 2006 |
|
| |
Keep your WSDM endpoints trim with Apache Muse
Learn how to use Apache Muse 2.0 to create WS-DistributedManagement (WSDM) interfaces for resource types that have hundreds or thousands of instances. First, this article shows how to create a WSDM interface to represent Java Platform, Enterprise Edition (Java EE) application resources (which can be quite numerous in any given application server). Second, it shows how to create a "factory" resource that in turn creates the Web application resources as they are installed on the server. Finally, you'll see how to minimize the footprint needed to support a large number of resources so the WSDM endpoint doesn't burden its host.
|
|
Articles |
|
12 Dec 2006 |
|
| |
Meet the specs: WS-RT 1.0 operations, Part One
Meet the WS-ResourceTransfer 1.0 initial draft specification, a proposed open standard that extends certain operations by allowing fragments of XML code in a single resource to be addressed instead of having to affect the entire resource. This article provides a closer look at how the WS-ResourceTransfer 1.0 specification extends the Get operation.
|
|
Articles |
|
29 Nov 2006 |
|
| |
Create a WSDM interface for an HTTP server using Apache Muse
Learn how you can use Apache Muse to create a WS-DistributedManagement (WSDM)-compliant interface for a manageable resource. In this tutorial, you'll see how to design the Web service interface for the resource, generate code for the implementation, and deploy the code as a Web application. The manageable resource focus of this tutorial is the ubiquitous Apache HTTP Server, commonly-referred to as "httpd." After completing this tutorial, you should have a Muse-based application that lets any WSDM-compliant management client manipulate the httpd resource.
|
|
Tutorials |
|
21 Nov 2006 |
|
| |
Architecture in practice, Part 1: Realizing Service-Oriented Architecture
IBM architect Tilak Mitra provides practical guidance about IBM tools you can use to build a Service-Oriented Architecture (SOA) solution. In this first installment of his column, you get an overview about the IBM SOA Foundation as well as IBM Rational, WebSphere, and Tivoli software tools and other resources you can use to make your SOA designs a reality.
|
|
Articles |
|
21 Nov 2006 |
|
| |
Hit the ground running with AIDE, Part 6: Build an autonomic computing system
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.
|
|
Tutorials |
|
14 Nov 2006 |
|
| |
Meet the specs: Intro to WS-ResourceTransfer 1.0
Meet the WS-ResourceTransfer 1.0 initial draft specification (WS-RT), a proposed open standard that extends certain operations by allowing fragments of XML code in a single resource to be addressed instead of having to affect the entire resource. This introduction provides an overview of the specification, examines its heritage, and starts climbing the learning curve by uncovering the definition of fragments and discovering the three expression dialects employed in WS-RT.
|
|
Articles |
|
19 Sep 2006 |
|
| |
Hit the ground running with AIDE, Part 5: Build an autonomic computing system
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 IBM Autonomic Integrated Development Environment (AIDE) resource browser and
a Derby Java client program.
|
|
Tutorials |
|
05 Sep 2006 |
|
| |
Hit the ground running with AIDE, Part 4: Touchpoint notifications and a simple manager
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.
|
|
Tutorials |
|
18 Jul 2006 |
|
| |
Hit the ground running with AIDE, Part 3: Touchpoint and managed resource integration
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.
|
|
Tutorials |
|
27 Jun 2006 |
|
| |
Hit the ground running with AIDE, Part 2: Build a real-world touchpoint
This tutorial -- the second in series on AIDE -- moves beyond the basics of building touchpoints using the IBM Autonomic Integrated Development Environment (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.
|
|
Tutorials |
|
23 May 2006 |
|
| |
Hit the ground running with AIDE, Part 1: Building a touchpoint
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.
|
|
Tutorials |
|
18 Apr 2006 |
|
| |
Combine autonomic computing and SOA to improve IT management
For architects and designers who want to know how to apply autonomic computing and Service-Oriented Architecture (SOA) to management systems, this article introduces key concepts in autonomic computing and SOA and shows you how they combine to deliver autonomic management systems that address the challenging complexities within the IT organization. Learn how to incrementally automate IT management processes that might span organizational boundaries, and how to integrate an independent autonomic manager into IT management processes.
|
|
Articles |
|
04 Apr 2006 |
|
| |
WSDM for J2EE provides next-generation management
Can the standards for Java 2 Platform, Enterprise Edition (J2EE) management (JSR 077) and general IT management (WS-Distributed Management) work together to create robust manageability interfaces? In this article, you'll learn how the IBM Autonomic Integrated Development Environment (AIDE) component, the IBM Manageability Endpoint Builder, and the JSR 077 API can be used to build a Web Services Distributed Management (WSDM)-compliant manageability endpoint for Java application servers. The final product is a Web application that you can deploy on any J2EE-compliant application server.
|
|
Articles |
|
28 Mar 2006 |
|
| |
Book review: Autonomic Computing
Join me as I troll through Richard Murch's book from IBM Press, "Autonomic Computing," and find tools and resources for the system designer, administrator, and developer.
|
|
Articles |
|
25 Oct 2005 |
|
| |
Architecting on demand solutions, Part 10: Monitor business IT services using IBM Tivoli Monitoring for Transaction Performance
Business performance management (BPM) software can help you better manage your business operations. IBM Tivoli Monitoring for Transaction Performance provides the ability to manage IT services as part of a business performance management capability. These services can be exposed as Web services as part of a service-oriented architecture (SOA) or as components of a process model that leverage Java 2 Platform, Enterprise Edition (J2EE) components. Tivoli Monitoring for Transaction Performance uses the Application Response Measurement (ARM) standard for data collection. In this tenth article in the series, you learn about the Tivoli Monitoring for Transaction Performance management cycle and how to monitor a Web service deployed on IBM WebSphere Business Integration Server Foundation Version 5.1.1.
|
|
Articles |
|
28 Jun 2005 |
|
| |
Autonomic computing and Web Services Distributed Management
The Organization for the Advancement of Structured Information Standards (OASIS) has just approved a new standard: Web Services Distributed Management (WSDM) 1.0. This article discusses the relationship and value that this new standard brings to autonomic computing technology. The article does not provide the technical detail necessary to build autonomic computing-compliant interfaces using WSDM because other articles and specifications will provide these as they are developed.
|
|
Articles |
|
02 Jun 2005 |
|
| |
