Jazz Application Framework Transition

https://jazz.net/wiki/bin/view/Main/JAFSdkTransition

FROM

• an application that was developed with the older Application SDK 3.x.x.x, using functional services from a shared Jazz Team Server (JTS).
• The Application SDK included a framework for defining application REST services. Application services were declared in plugin.xml files as extensions of the com.ibm.team.jfs.app.restServices extension point, and implemented as extensions of the com.ibm.team.jfs.app.RestService class.
• Fronting applications only needed to build against a few Foundation features: 
  • com.ibm.team.jfs.sdk.runtime.feature 
  • net.jazz.ajax.app.jfs.feature 
  • net.jazz.ajax.app.jfs.feature 
• 
  

TO

• use the new JAF SDK 4.x.x.x, using local functional services and data storage.
• the JAF SDK includes the Jazz OSGi services framework (see the HelloJAF tutorial for a brief introduction).
• the JAF SDK is considered to be this set of features:
  • com.ibm.team.app.server.jfs.feature
  • com.ibm.team.dashboard.server.jfs.feature
  • com.ibm.team.gateway.server.jfs.feature
  • com.ibm.team.jazz.server.feature
  • com.ibm.team.process.server.jfs.feature
  • com.ibm.team.reports.server.jfs.feature
  • com.ibm.team.repository.server.jfs.feature
  • com.ibm.team.repository.services.jfs.feature
  • net.jazz.ajax.app.jfs.feature
  • net.jazz.ajax.jfs.feature 
• 
  

https://jazz.net/wiki/bin/view/Main/JAFSdkIntroduction

Jazz Application Frameworks SDK

One of the primary deliverables of the Jazz Application Frameworks is an SDK for building applications. This SDK takes the form of an empty OSGi application shell that provides a framework for a rich, dynamic layered application. Applications embed functional services from this SDK, which they invoke locally. Some integration services, such as user management, licensing and authentication, are delegated to a Jazz Team Server (JTS) which may be shared amongst multiple applications. This SDK will be part of the Jazz Application Frameworks 4.0 release.

The history of the SDK

A brief word is required here to explain the multiple SDKs which exist, and where the JAF SDK fits in to the story.

Jazz 0.6 SDK

The "0.6 SDK" included local execution of functional services in an OSGi application. It included a repository service framework, a persistence story, process, reporting, Web UI, and dashboards. Such an application has a local database for storage. RTC and RQM are based on the Jazz 0.6 SDK.

Application SDK

The Application SDK described OSGi or pure Java "fronting applications" which rely on a shared JTS for functional services such as storage. It communicated with the JTS using REST to consume these services. RRC is a fronting application based on the Application SDK.

JAF SDK

In 2012, the preferred approach for building applications on JAF is changing. Instead of creating fronting applications that consume functional services from a shared JTS, applications will embed the functional services and invoke them locally. There are a number of advantages to this approach, including reducing the load on the JTS and unifying two SDK stories into one. The JAF SDK is essentially the 0.6 SDK, with some compatibility and transition add-ons to aid applications which are currently build on the Application SDK. Applications will continue to use the JTS for integration services.

-