When building an application using JAF, it is helpful to simplify the topology and think about the following pieces:
When building an application on the Jazz platform, there are two distinct kinds of shared implementation capabilities:
- Integration services, which can be employed for the purpose of integrating tools. These integration services should have the same loosely-coupled, protocol-driven characterstics as OSLC.
- Application frameworks, which can be used to develop Jazz-based products from the ground up. These frameworks may make use of the integration services.
- Architectural guidance for designing new Jazz products that have a common look, behavior and collaboration capabilities.
- An JAF SDK in the form of an empty OSGi application shell that provides a framework for a richer, more dynamic and layered application.
참고: https://jazz.net/wiki/bin/view/Main/JAFSdkContents - A set of reusable features packaged as OSGi bundles that can optionally be embedded in the SDK to provide a range of common functionalities, including Web UI frameworks or toolkits, process capabilities, a persistance layer with query capabilities, reporting and data warehousing, and others.
- A set of low-level common utils and libraries that can be deployed as OSGi bundles or plain JARs. For example, OAuth helpers, Jazz HTTP clients.
- A Jazz Team Server (JTS) providing common user admininistration, delegated authentication, licensing, dashboards, and data warehousing to the applications associated with it.
댓글 없음:
댓글 쓰기