- OSLC Home: http://open-services.net
- OSLC on Twitter: http://twitter.com/oslcNews
- OSLC-CM Home: http://open-services.net/bin/view/Main/CmHome
- Details on the RTC Implementation: https://jazz.net/wiki/bin/view/Main/ResourceOrientedWorkItemAPIv2
- Carolyn Pampino on the RQM-RTC integration: http://jazz.net/blog/index.php/2009/08/26/sprint-alignment-for-developers-and-testers/
- Scaling Agile with C/ALM eBook: http://www.infoq.com/resource/articles/scaling-agile-with-calm/en/resources/InfoQ-IBM-ScalingAgilewithCALMeBook.zip
Displaying items by tag: ibm
For completeness, the DNG public API's that are available are:
- RDNG Reportable API - extracting read only information from RDNG generally for creating custom reports to be run from DNG or RPE. As well, it can be used in a lot of custom applications interacting with RDNG. Big advantage of this API is its simplicity and great performance if you need to work with big amounts of data. Sometimes it's called as RDNG Reportable REST API.
- OSLC RM V2 API - the open standard way to programmatically integrate with DOORS Next Generation, there is an elaborate workshop to get you started here OSLC Workshop article. These programs can be from any language that supports various HTTP methods of requests, e.g. Java, C# etc. Hence these are more flexible to run and can read and update DNG data, as part of a web server, or standalone, but have some limitations set by the current OSLC standard, for example module support. In release 6.0.5 extension have been added for modules. It's very powerful tool to work with RDNG data including capabilities of data modification but can be a little bit more complex in use than other ways.
- TRS 2.0 - the OSLC Tracked Resource Set open standard REST API to hook into the stream of low level changes done to resources in the DNG application (and other Jazz apps as well); read only.
- RM API - it's realized in client extension capability that is accessible from Rational DOORS Next Generation. This is Javascript extension framework that generally can be added as widgets which you can run from the dashboard, and can be used to view and edit DNG data. The widgets are developed in accordance to OpenSocial standard (based on Google Gadget framework). It's more tailored to DNG, so has better module support, but is limited to be run in a browser/javascript environment. It's very easy to make an automation of your work in this way. You can do a lot of interesting tricks with currently open Web page based on DOM/XML standards. You can add support of many popular libraries such as JQuery and so on. But this big simplicity results in some constraint in implementation. For example, you can easily access RDNG artifacts in current module or collection as well as access any selected artifacts but there are some difficulties if you need access artifacts in current view or currently available on the page. But use RM API together with other APIs described above can allow you do stunning things with RDNG.
Helpful Links
Ord. Link Comment 1 API Landing page This is a landing page for the various API wiki pages that exist on the Jazz.net development wiki as well as a central collective page of the known APIs that are available for integrating programmatically with our CE/CLM products. It serves as a convenience for accessing API information about CE/CLM products and is not guaranteed to have up-to-the-minute information. 2 DOORS Next Generation Reportable API The DOORS Next Generation server provides REST APIs for accessing information about requirement artifacts for reporting. You can access each API by using a standard web browser, IBM Rational Publishing Engine or a third party tool can can consume the DNG reporting services responses. This document covers reporting capabilities for DNG versions 6.0 and higher. 3 Using OSLC capabilities in the Requirements Management application You can use Open Services for Lifecycle Collaboration 2.0 (OSLC) capabilities in the Requirements Management (RM) application for the Rational solution for Collaborative Lifecycle Management (CLM). This article includes examples of how to use those capabilities in an HTTP poster tool. These basic examples are described. 4 Open Services for Lifecycle Collaboration Workshop The workshop will help guide you to leverage the Open Services for Lifecycle Collaboration (OSLC) standard interfaces for interoperating with Jazz-based products including RDNG. These labs will highlight key aspects by leveraging web browser access and programmatic access via Java client programs. The final lab will illustrate by an example how to write your own server using Java servlets. This lab is based on the OSLC-CM 2.0 and OSLC-RM 2.0 Specification. After you complete these labs, you will have a good foundation by which to leverage OSLC to implement an interoperability project. 5 OSLC Requirements Management Version 2.1. Part 1: Specification This specification defines the OSLC Requirements Management domain, also known as OSLC RM. The specification supports key RESTful web service interfaces for software Requirements Management systems. 6 OSLC Requirements Management Version 2.1. Part 2: Vocabulary This specification defines a vocabulary and resource shapes for the OSLC Requirements Management resources. 7 IBM DOORS Next Generation Server API Documentation (additions from v6.0) Additions to standard OSLC API specially developed for use with RDNG. It takes into account some RDNG specifics that is out of scope of OSLC specification. 8 Getting Started with RDNG Extending Capabilities Brief video giving a quick introduction into client extending capabilities. 9 Client extension API for the Requirements Management (RM) application This document specifies the client extension API that forms part of the 6.0.5 release of the Requirements Management (RM) application. The version of this API is 1.1. 10 Client extension capability (all versions) List of links to client extension APIs for all supported versions. 11 jQuery API Useful API when developing RDNG client extensions. 12 Web APIs When writing code for the Web with JavaScript, there are a great many APIs available. Below is a list of all the interfaces (that is, types of objects) that you may be able to use while developing your Web app or site.
Useful Links
https://www.facebook.com/oslcfest/
DOORS Next Generation (v4.0.6): Adding an extension to your dashboards via URL
https://www.youtube.com/watch?v=q3DxAneAPYQ
Adding widgets to the widget catalog of IBM Rational DOORS Next Generation (V4.0.6)
https://www.youtube.com/watch?v=mXl1YcDYjVg
UrbanCode Deploy - Deployment Automation
IBM UrbanCode Deploy is a tool for automating application deployments through your environments. It is designed to facilitate rapid feedback and continuous delivery in agile development while providing the audit trails, versioning, and approvals needed in production.
IBM UrbanCode Deploy provides
- Automated, consistent deployments and rollbacks of applications
- Automated provisioning, updating, and de-provisioning of cloud environments
- Orchestration of changes across servers, tiers, and components
- Configuration and security differences across environments
- Clear visibility: what is deployed where and who changed what
- Integrated with middleware, provisioning, and service virtualization
Typical Uses
- Continuous Delivery: Integrate with the build and test tools to automatically deploy, test and promote new builds
- Production Deployments: Orchestrate a complex production deployment of applications and configuration
- Self-Service: Grant different teams rights to “push the go button” for different applications and environments
- Incremental Updates: Deploy only the changed components or missing incremental (patch) versions
Key Features
Multi-Tier Application Models
Modern applications are often made up of many components. Perhaps a three-tier application with database, app, and content components. Or A mobile application with the actual mobile application and back-end web services. Even related collections of batch programs are seen as a logical application. UrbanCode Deploy tracks which components make up an application so they can be deployed and tracked together. Snapshots offer the ability to create a version of the application encapsulating versions of each of the components. With snapshots, it is easy to ensure that components that were tested together are released together.Learn more about application modeling and snapshots.
Easy Process Designer
Deployment automation tools need to know how to deploy your applications. In UrbanCode Deploy, processes are defined in the browser using a simple, drag and drop process designer. Component processes are composed of automation steps delivered by integration plugins. Application processes are composed of component processes. Steps may be run in sequence or parallel. Transitions between steps are governed by rules. Typically, “Go this way on success, or that way on failure.” The designer makes it easy to translate a cryptic manual process into an easy-to-understand automated flow.
Deploy to Public, Private, and Hybrid Cloud
Using the blueprint designer, you can model cloud environments and how your applications are deployed to those environments in a simple graphical editor. You connect to clouds, model the virtual images in the environment, and add your application components to those images. Then, you can provision environments and deploy the application components automatically and on-demand. The blueprint designer supports public and private clouds including IBM Bluemix, IBM SoftLayer, Amazon Web Services, Microsoft Azure, VMware vCenter, and OpenStack-based clouds.Learn more about the blueprint designer.
Track What is Where: Inventory
It is critical to understand what is in each environment. Audit wants to know what is in production. Testers need to know what we just ran those tests against. And when things go wrong, we all want to know what is different between those environments? UrbanCode Deploy tracks what is where in its inventory system. The inventory system tracks the desired state of each environment, as well as what has been successfully deployed to each target resource, and provides graphical alerts when an environment is out of compliance with that desired state.Learn more about Inventory.
Scalable Distributed Automation
UrbanCode Deploy is built to support mission-critical deployments to thousands of servers in numerous data centers. Master server clustering support provides high availability and horizontal scalability of the deployment automation tool. UrbanCode Deploy uses light-weight deployments agents that provide an immediate presence on or near the target. Remote agents can be proxied through an agent relay to manage load and simplify firewall management.Learn more about UrbanCode Deploy’s Architecture
Quality Gates and Approvals
For some environments, deployments may not be allowed until some conditions are met. Perhaps the versions being deployed must have passed tests or received a blessing from a team. Or the time and date of the deployment must be approved by several people. UrbanCode Deploy provides Environment Quality Gates as well as Approval Processes to help you ensure that only the right stuff goes out at the right time. Because these rules are set per application and per environment, early test environments are likely to be set up to not require approvals.
Integrations Replace Custom Scripting
Tested integrations are provided with dozens of tools to make the deployment process easier to design and less risky. Integrations are provided for application servers, load balancers, databases, testing tools, build servers and more. Utilities to manage configuration files, registry settings and the like are also available. Teams who have great deployment scripts already can continue to use them through UrbanCode Deploy either by directly calling the scripts, or embedding them in custom plugins. Browse available plugins at the Plugins Portal.
Learn More
- Get a quick overview of UrbanCode Deploy: Video, how to get started, see how others are deploying apps.
- Evaluate UrbanCode Deploy: Resources for personalized demos, trials, and more.
- See what’s new: We are always adding more, check out what we’ve done recently.