AcdntlPoet 2700019V2G Visits (596)
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 (1290)
Ralph Schoon (Unleash The Labs, Leading Technical Sales Professional ) provides two great no-nonsense views into starting up with projects in IBM BlueMix on his external blog rsja
Getting started with BlueMix - Ralph blogs about his experiences with BlueMix and provides some detailed information to help you get started as well: "Recently everyone has their heads in the clouds and I decided to have a peek to find out what it is all about. So I started looking into it. This post is a summary of my first experiences with the IBM BlueMix Cloud Computing offering and how I got started with developing my first applications for it..."
Using RTC to Work with DevOps Services and With Bluemix - Ralph blogs again with a deeper dive into BlueMix and Eclipse that builds upon the post above: "I recently had a look into Bluemix and how to use it with Eclipse to develop cloud applications. The blog post also mentions that there is an integration to DevOps Services that enables to use work items for planning. It also allows to use GIT or Jazz SCM to manage the source code. Recently I had a look into how that works and I would like to share here what I learned. This post assumes you have performed the first steps to setup your environment following the Getting started With Bluemix post already...."
Arun K Sriramaiah 2700076GE8 Visits (931)
CLM License Server idle standby deployment with CLM Licenses on 2 servers (Primary and Backup).
Saurabh.Tyagi 270005CY2K Visits (3948)
IBM Rational Jazz token license configuration on Jazz team server
Token based licensing is an option, along with floating and authorized user licensing, within the Rational portfolio. Technically, the basis of token licensing is on the traditional floating license mechanism and process. However, when it comes to how the license check out (consumption) works, it has a different behavior.
In a token environment, each product consumes a predefined token value, not a predefined quantity as it does in a traditional floating licensing environment. The license key has a pool of tokens from which the license server automatically calculates the tokens being checked in and out across users and products.
Lets discuss how a token based licensing model can be implemented for Jazz-based products.
Jazz-based products use IBM Rational Common Licensing (RCL) token service provider, which is an extension of the Jazz Team Server (JTS) that forwards token requests to an IBM Rational License Key Server (RLKS). Jazz-based products and non Jazz-based products can share tokens from same pool of tokens.
How to generate Jazz tokens?
Log into the Rational license key center and follow the below steps to get the required Jazz tokens
You can also refer to the technote links below which will guide you in accomplishing this task:
To configure these Jazz based licenses, from a licensing perspective pre-requisites are:
The following picture shows a high level single server topology deployment of RTC using token licensing.
Once you have successfully configured your flexlm license server with token file, you downloaded from IBM Rational license key center (license.dat), Import the Jazz Keys (Jazz.Token.zip file) on the Jazz team server.
Post successful import of Jazz keys on the Jazz team server you will find an entry very similar to the below diagram
The above screen confirms that the Jazz tokens are successfully imported on the Jazz team server and we can now proceed to configure this Jazz Team Server to communicate with the Rational License Key Server that you installed and configured earlier.
In the Floating License Server section of the License Key Management page of your Jazz team server click the radio button next to IBM Rational Common Licensing Token Service to enable the service.
Hover over the icon in the Actions column until you see the edit hover. Click the icon to view the Server Configuration dialogs shown in following picture.
Configure the following two properties in the above dialog:
If the Jazz Team Server is able to connect to the Rational License Key Server, you'll see a green checkmark on the IBM Rational Common Licensing Token Service line as shown in following picture.
AcdntlPoet 2700019V2G Visits (1810)
Learn how to set up an IBM Rational Team Concert main build that performs an IBM Rational Developer for System z code review. Based on the result of the code review, the process either submits the build to compile, or stops and reports the code review errors. Apply the tested, documented sample described in this article to implement a similar solution on your own platform. The steps focus on the Rational Team Concert administrator who writes an Ant task to compile COBOL programs, depending on other previous tasks, such as quality control.
Set up a Jazz Build Engine to run an Ant script: Part 1. Setup build definitions- The initial Part 1 article describes the technical and functional context of the scenario, and the Jazz Build Engine configuration.
Set up a Jazz Build Engine to run an Ant script: Part 2. Setup build scripts to perform preview build- In this Part 2 article, we introduce the Ant-based build script, build.xml, that defines tasks for the build to run.
Set up a Jazz Build Engine to run an Ant script: Part 3. Setup build scripts to coordinate code review and build- In the final article, Part 3 describes how to run the RPP synchronize task, how to implement a code review, how to parse, convert, and publish the code review results, and how to run the build.
Figure 1. Technical context for the sample scenario: