My favorite WordPress plugins

Plugins to administrate your site

Read More »

Meet & Greet the Eclipse Research Project Community Primary tabs

Our session was accepted for the second time at EclipseCon France. We will present the progress of our various research projects. Each project representative will be able to present their project to provide an overview of their progress.

I can not wait to meet you at EclipseCon France

Upgrading from CLM 4.0.2/DB2 9.7 to CLM 5.0.2/DB2 10.5

Have you had the opportunity to do an upgrade certainly of a Jazz platform? I did several of them these last years and generally I had to either upgrade the database or migrate the application server and it worked pretty smoothly…

For this one, we have to go thru 2 migrations and 1 upgrade. Actually, CLM 4.x supports DB2 9.7, CLM 5.0 does not and CLM 5.0 supports DB2 10.5. CLM 4.x does not. So we have to upgrade first against an intermediate version of DB2 (10.1) supported by both CLMs to be able to do the full migration.

So this upgrade will run in 3 main steps:

  1. Migrate your CLM 4.0.6 from DB 9.7 to DB2 10.1
  2. Upgrade your CLM 4.0.6/DB2 10.1 to CLM 5.0.2/DB2 10.1
  3. Migrate your CLM 5.0.2/DB2 10.1 to CLM 5.0.2/DB2 10.5

Read More »

Rational Team Concert for IBMi teams

arcad If you missed our Webinar serie about RTC for IBMi teams, here are recordings for each Webinar in the series:

If you have any questions about the Webinar series and solutions, just email, we look forward to hearing back from you!

Add Time Tracking to your Work Items

TimeTracking It took me few time to figure out and retrieve how to add Time Tracking to my own work items so I decided to share this useful page with the community.

In the Help page, Adding formal project management features to a process template, you will find:

  • How to add snapshot capabilities to your plans,
  • How to add Time Tracking capabilities to your work items,
  • Add the Risk Action work item type for risk management

Quite useful if you have to add some formal features to your Agile developments…


ClearConcert or How to browse your Work Items from your Mobile or Tablet

clearconcertToday, Christophe, an ARCAD Software colleague of mine mentioned he had some issues when he was trying to browse our RTC from his iPhone. He also mentioned that he tested once an app on his iPad and could never make it work.

I knew it is not easy to make work RTC on an iPhone but I was not aware that a dedicated client was available on such mobile. So I decided to test it by myself. Actually, Christophe was not providing the correct URL. Once I told him to provide the same URL as the one that we use in the reach client  (http://my.jazz.server:9443/ccm) immediately he could reach our server and browse our work items…

The name of this application is ClearConcert. You can download it:

photo 5 photo 3 photo 4 photo 1 photo 7 photo 6

Enjoy and share your feedback in comments…

CRUD RTC work items using cURL (Part 2: Create)

I hope you enjoy my first post on the subject: CRUD RTC work items using cURL (Part 1: Read)

At this point we should have all the inputs to create a new work item using the OSLC APIs. It is time to retrieve the OSLC factory service used to create a work item. Actually, by calling the REST API answering the list of services provides by a project area:

rem Authentication
rem Request the url using the authentication
curl.exe -k -b %COOKIES%

you can retrieve the Work Item creation service. Actually, you will retrieve for each of your Work Item type a corresponding “factory” service.

So, if you want to create a task, retrieve the factory title “Location for creation of Task change requests”, the associate oslc_cm:url element provides the REST API to create a Task.

<oslc_cm:factory calm:id="requirementChangeRequest">
	<dc:title>Location for creation of Task change requests </dc:title>

Now to create a work item you can run the following code:

rem Authentication
curl.exe -k -b %COOKIES% -H "Content-Type: application/x-oslc-cm-change-request+xml" -H "Accept: text/xml" -X POST -d @newtask.xml

The cURL instruction references several important parameters:

  • The “-H” parameters specify the format of the body request (“Content-Type: application/x-oslc-cm-change-request+xml”) as well as the answer format (“Accept: text/xml”).
  • The “-X” parameter specifies the HTTP method to use: a POST method to create a new work item.
  • The “-d” parameter designates the content of the request body. You can either provide a string with the XML code of your new work item or you can use the character @ and reference a file containing the XML code of your new work item.

In our case we decided to use a separate file named “newtask.xml” containing the following XML code:


        <rtc_cm:filedAgainst rdf:resource=""/>
        <oslc_cm:priority <span="" class="hiddenSpellError" pre="priority " data-mce-bogus="1">rdf:resource=""/>
        <oslc_cm:severity <span="" class="hiddenSpellError" pre="severity " data-mce-bogus="1">rdf:resource=""/>
        <dc:title>New PK Task</dc:title>
        <rtc_cm:plannedFor rdf:resource=""/>

As you can see this file doesn’t mention the work-item ID, it will be provided by the JTS during the creation of the work item and it will be returned in the request answer.


The answer has the same format as the one returned when we access to a work item.

The second post was easy to write once the first one is posted.

The third one will be more complex because it will talk about ETag which is concept I’m discovering.

In mid time, I hope this one will help you…