AcdntlPoet 2700019V2G Visits (578)
Learn the main guidelines to build an automated development and testing framework using scripts. In the following blog post, Aya Elgebeely (Application Developer, IBM) highlights how using scripts to automate your development workflow can have a magical effect on your work quality and performance:
Streamline development efforts with scripts- There are quite a few steps to set up an environment or modify and build a substantial amount of files. If you use scripts, one command can do all the work at once. That's a big difference (and savings in time and energy) from doing the steps one-by-one. This gives you the time to focus on the important and innovative tasks and let the script do the mundane tasks.
With scripts you can combine various technologies under one custom framework. As if you are playing with Lego parts; scripts are the connectors between the different building blocks of your build and test environment. With scripting capabilities the intended workflow runs automatically with minimal user intervention.
AcdntlPoet 2700019V2G Visits (483)
Deep Dive Data Warehouse Reporting using the Jazz Reporting Service- The Jazz Reporting Service is the new reporting solution from IBM Rational Software developed on top of the Jazz integration platform and is intended to support the authoring of custom reports for the Collaborative Lifecycle Management (CLM) solution. A previous articles around Jazz Reporting Service covered reporting using the build in query builder [Haumer 2014], which allows end users to create their own reports almost right away with simple drag-and-drop gestures and selections. Another article [Shaw 2014] went one step further and demonstrated how to use theStructured Query Language (SQL) editor to modify and refine the underlying SQL statement that were generated by the query builder introducing some more advanced features.
AcdntlPoet 2700019V2G Visits (457)
From the Jazz team blog: IBM Rational Publishing Engine 2.0 M5 Beta – Improved document styling. We’re glad to announce that the Rational Publishing Engine (RPE) 2.0 Beta on Bluemix has been updated to the M5 build!
There is no registration or special process required in order to access the beta. Aside from announcing this update, the intention of this post is to provide a little extra help to those looking for guidance on getting started using the RPE 2.0 M5 Beta via some helpful resources. We’ll also touch on what’s new in this build of the beta.
Read the full blog post for the goals of the beta and more from the Jazz team here: http
Help Guide: IBM Rational Publishing Engine 2 M5 Help
AcdntlPoet 2700019V2G Visits (725)
If you've not been to the Global Rational User Community (GRUC) recently, here's what you've been missing out on when it comes to DevOps conversations... below you will find a series of blog posts from the GRUC site that cover varying topics around DevOps strategies. We hope you find these as beneficial as we have!
Blog Post: Defining Disciplined DevOps - This posting, the first in a series, overviews a disciplined approach to DevOps. It begins by defining DevOps, no small task given the continued debate within the DevOps community, and then described a disciplined approach to DevOps. Defining DevOps For our purposes we propose the following definition: DevOps is the streamlining of the activities surrounding IT solution development […]
Blog Post: DevOps Strategies: General - In a previous blog posting we overviewed the concept of Disciplined DevOps, which is the streamlining of IT solution development and IT operations activities, as well as supporting enterprise activities. In this blog posting we begin to overview strategies that support DevOps. This posting overviews general strategies, and future postings will desc
Blog Post: DevOps Strategies: Development - In addition to the general stra
Blog Post: DevOps Strategies: Release Management Part 1 - In this blog posting we describe four general release management strategies that support DevOps. These strategies, from least effective to most effective, are: Release windows (slow cadence). A release window is a period of time during which one or more teams may release into production. A release slot is subset within that release window (and […]
Blog Post: DevOps Strategies: Release Management Part 2 - In addition to the general release management strategies described previously, the general DevOps strategies, and the cons
Blog Post: DevOps Strategies: Operations - In addition to the general DevOps strategies and development-focused DevOps strategies we’ve described previously, there are also several technical strategies that support the operations-aspects of DevOps: Solution monitoring. As the name suggests, this is the operational practice of monitoring running solutions and applications once they are in production. Technology infrastructure platforms such as operating systems, […]
Blog Post: DevOps: Strategies for Organizing Release Management - In this blog posting we describe two issues for organizing your release management strategy: How to scope release management and how to organize the team. There are two fundamental issues to consider when scoping your release management efforts: Paradigm support. Will your release management process focus on supporting one paradigm, such as agile/lean teams or […]
Blog Post: DevOps Strategies: Data Management - In the Disciplined Agile Delivery (DAD) framework data management is a Run (operational) activity that focuses on the execution of data-oriented architectures, policies, and processes. Note that the long-term planning efforts around data-oriented aspects of your organization are part of your Enterprise Architecture efforts. Similarly, development of the data-oriented aspects of your organizational eco-system is […]
Blog Post: DevOps Strategies: Enterprise Architecture - The Disciplined Agile Delivery (DAD) framework explicitly includes arch
Blog Post: DevOps: Operational Disaster Strategies - There are several disaster mitigation strategies that IT departments may choose to adopt: Disaster planning. Disciplined organizations will plan for operational disasters. Potential disasters include servers going down, network connectivity going down, power outages, failed solution deployments, failed infrastructure deployments, natural disasters such as fires and floods, terrorist attacks, and many more. This planning will […]
Blog Post: DevOps Teaming Strategies - There are several teaming strategies that you can choose to adopt when it comes to getting development professionals and operations professionals to work together. Starting with the least effective and working our way to the most effective, they are: Production hand-off. When a development team releases a solution into production the operations team takes on […]
Blog Post: DevOps Strategies: Support - In this blog posting, part of our continuing series on DevOps, we explore solution support strategies. There are several solution support (help desk) strategies, which can be combined, that you may choose to adopt. These options are: Online information. A very common “self serve” support strategy is to develop and maintain online assets such as […]
AcdntlPoet 2700019V2G Visits (543)
Back in January we posted about Ralph Schoon's RTC command line... since then he has continued his work and made a few updated revisions to the tool! Check out the two blog posts below noting the deprecation of version one, and the most recently updated version 2.2!
An RTC WorkItem Command Line V1.0 – Deprecated- Version 1.0 is now Deprecated. Please refer to the new Version 2.2 of the RTC WorkItem Command Line . The code has been enhanced and received a lot of testing and will be the basis for future efforts.
An RTC WorkItem Command Line Version 2.2- Creating links is not easy. Many things can go wrong. Testing by a user showed that there was an issue with links between work items and build results. I found that I got the link direction wrong. I fixed that. Here is the updated source code.
License and Getting Started
The post contains published code, so our lawyers reminded me to state that the code in this post is derived from examples from Jazz.net as well as the RTC SDK. The usage of code from that example source code is governed by this license. Therefore this code is governed by this license. I found a section relevant to source code at the and of the license.