Welcome to the Jazz for Service Management Blog, where you can read the perspectives from the Jazz for SM experts. Please also join the JazzSM Group: http://smconnect.net/jazzsm
This Blog provides insights into the overall Jazz for SM solution, as
Courtesy of my colleague Chris Appleton in Netcool/OMNIbus development, there is a new video on how they designed their own OSLC Service Provider for their upcoming 7.4 FP3 release. All standard disclaimers apply about release contents not being final until formally announced, but the work is already subject to external try-outs in the Jazz for Service Management hosted beta .
This video was primarily created for systems integrators who already extend Netcool/OMNIbus and want to expand that integration to enable collaboration with other... [More]
There is currently considerable interest in DevOps . And well this might be since the goal of DevOps is increased responsiveness to your customers. One of the basic tenets of DevOps is automation of processes : have code perform what was previously painstaking manual work, which helps achieve faster and more frequent development/deployment cycles. But, you might have tens of tools installed in your environment, each with its own interface. We need to programmatically orchestrate the work done by these tools and do so in... [More]
JazzSM 220.127.116.11 milestone 3 beta driver has just been released and I am really thrilled with the introduction of support for provider record templates, brain child of our ever keen Joe Ross.
Provider record templates are a mechanism for OSLC service providers to inform Registry Services about what their records should look like without ever sending them to Registry Services. This is an ideal arrangement for service providers which have considerable amounts of data about several resources, to a point where it would be impractical to send... [More]
You need to keep your IT operations running smoothly and you want to reduce the time it takes to resolve problems. And to achieve that, you need access to detailed, real time information about your IT resources from all possible sources ( asset management, configuration management, monitoring and so on.) So great, your vendors and IT teams have implemented scenario "View assets and CI details vi UI preview" . Life is good ! But wait ! You have data coming from all sorts of providers.... [More]
A common requirement from the integration scenarios that I've been introducing to you is the need for combining data from multiple sources. For example, while scenario “Service and Application Problem Diagnosis” calls for being able to determine the impact on services and applications of supporting resources and scenario “Deployment of VM, System and Application patterns in Cloud” calls for being able to... [More]
There is beauty in visualization, there is paradise in beautiful integration, then there is a Meat Loaf-esque attempt at tying this entry’s title to the intro. For the past two years we have been focusing on consolidating and correlating data from different data providers, and during that time we also put out a rather polished Registry Services Sample UI console that allowed people to browse data stored in Registry Services. All the while we kept throwing a long look across the hallway - actually they sit on the floor above, their not... [More]
Continuing with my series of blog posts on how IBM products use scenarios in their integration work, I’d like to showcase the newly released SmartCloud Control Desk v.18.104.22.168
For a much better description, go to this page and watch the online demos or try it out on the Jazz for Service Management hosted beta . I’ll just note that, among many other features, SmartCloud Control Desk 22.214.171.124 implements scenarios
Last time , I mentioned how IBM teams use scenarios as a tool to bake in integration in our products. Eventually (or as some of you might say, at long last ... ) though, a scenario gets implemented and released. Now, since it's integration we're talking about, it's not one product that's released, it's multiple products. And, it's not multiple products being released at once, it may be one new product now working with another product that's been out for 6 months or even two products from two different vendors.... [More]
One of the guiding principles of OSLC is that everything is scenario driven . OSLC workgroups focus on satisfying real-world interoperability
scenarios and use these to agree of what is to be defined in an OSLC specification .
IBM teams follow the same principle when trying to define integration between products. A scenario allows us to define the who,what,why and how of an integration and to do it in a way that allows for disparate groups to focus on the task at hand.
We're publishing on the... [More]
The Hitchhiker’s Guide to interfacing with Registry Services two-part series introduced everything you needed to know about Registry Services’ concepts in order to write a client application. If you are already familiar with RESTful interfaces and RDF models, you probably can skip a good part of it. The Java language is certainly very popular and well-covered in the Registry Services samples, but it will not be of much help if your code runs inside a web-browser and you are not keen on suffering through the time-tested pain of mixing applets... [More]
*Co-authored and reviewed by Maristela Salvatore @soaresm
When sending Registration Records requests to Registry Services, you can find a situation where the reconciled Resource Record was not created or the Registration Record information was not part of an existing reconciled Resource Record. How to figure out why your Registration Records were not reconciled?
It might not be easy to find out what could have caused the reconciliation problem, as there is not a straightforward answer for this question. Instead, you can try to... [More]
In part 1 of this entry , I outlined the concepts and steps required to get data inside Registry Services. I also revealed Registry Services’ party trick, which lies in its ability to recognize seemingly disjoint information from different sources as representing the same entity in the outside world. It has been enough days to let you build that first application, at which point you must be wondering “How do I read that collection of reconciled resource records? Where do I start?” Collections, collections, collections… Sorry... [More]
Apparently I have eclectic interests - at least people who know me seem to think so. Arnaud LeHors from our Standards organization just published a blog entry on recent Linked Data Platform progress that brought me back to some concepts from chaos theory and power laws I was reading about recently.
A short digression into chaos theory - optional
One of the really "crazy" things about chaos theory is that you end up with very complex behaviors from incredibly simple equations like
Business partners and internal development teams often commend the simplicity of the OSLC integration model adopted in Jazz for Service Management, which is based on well-established open web standards. The openness guarantees that the knowledge is reusable in other implementations, and that vendor neutrality will ensure the stability of APIs and the simplicity of integration with other applications. At the same time, those standards do carry a handful of concepts and models on their backs, but do not panic, they are mostly harmless. The... [More]
Are you still finding answers to questions like:
"I have a product to administer on a server. I want to monitor its health, schedule health checks at a particular interval, receive alerts of the various configuration health on my dashboard, perform configuration on the product. However, I do not have sufficient knowledge to perform long steps of configuration. How do I get started to administer?"
The answer to above questions is Administration Services. All you need to do is install Jazz for Service... [More]
This demo ( OSLC and TOSCA Cloud App Lifecycle ) is about a lifecycle of a cloud application. It is not “THE END-END LIFECYCLE”, it is just one example of the many possible lifecycles you can build with your tools to manage cloud applications. The goal is to show how OSLC and TOSCA make this easy. The lifecycle is composed of the following steps: In the first step, a developer imports a TOSCA cloud application package in a definitive software library. The library is implemented with Rational Asset Manager, but any other tool implementing the... [More]
Here's a video of capabilities developed by IBM Research being demonstrated at the Pulse Integration Center. It shows a solution to tie discovered business processes to the underlying IT resources with a Jazz for Service Management OSLC registry. Come see us at pedestal 82 of the Pulse Solution Expo. Solution Overview Bridging the gap between business and IT is a common challenge. For example, when a customer's shipment is missing, knowing the application server that last processed the customer's order can help diagnose if the... [More]
While the basic agenda has been fairly stable, there are some new materials available to help sift through the 659 (!) sessions visible in SmartSite. I flagged roughly a dozen sessions that are specific to OSLC and Jazz for Service Management in the agenda below; we also have an entire Integration Center at peds 80-90 on the Expo Hall floor highlighting demonstrations in these areas, in addition to other solution-centric peds on the main floor. Cloud Open Standards: as of today, a new brochure is available for anyone looking to major on this... [More]
This is a bit of sample code I am currently working on, to illustrate how developers can query record collections from the Registry Services component of Jazz for Service Management using pagination support. In this example I will not do anything to the records, but simply show how to list all the URLs for all records for a given Service Provider.
The sample assumes dependencies on both Apache Jena and Eclipse Lyo , the later of which requires Apache Wink . I apologize for the profusion of dependencies, but Jena does a superb job of... [More]
If I have multiple products deployed in an IT environment, I can use each of them individually. However, solving a problem often requires access to information from multiple products . For example, if I have a problem with a business application, I might need information about which servers and associated hardware and software support that application. I might then want to know details about how those servers are configured, which of them are overloaded, which ones have had recent configuration changes, and if there are error events being... [More]