2.16.1 CAF Application Life Cycle Management

CAF Application Life Cycle Management

CAF application life cycle starts with activation of CAF application at NOAM and takes effect after the CAF has been administratively enabled. CAF provides the following application life cycle capabilities:

• Management of multiple versions per CAF applications.
• Supports importing/exporting of application business logic and configuration data across deployments.
• Each CAF application can be in one of the following states:
  • Development (initial state) – Allows to creation of new application or update of existing versionof CAF application.
  • Trial (at most one at a time) – Allows to run the CAF application only on configured Trial DA-MPs before actual deployment into Production environment.
  • Production (at most one at a time; if missing, the CAF app goes into „Unavailable“ operationalstate) – Allows CAF application to be deployed into production environment across DA-MP.
  • Archived – Allows archiving of older versions CAF application for later reuse.

• Provides capability to roll back the system to a previous state with minimum service interruption, in casethe new production version experiences unexpected runtime errors or performance issues.

Figure 2-66 Custom Application Framework (CAF) Application State Transition