## 4.1.8.1.9.1  Content Deployment
SAP Business Technology Platform Cloud Foundry supports the lifecycle of all standard Cloud Foundry entities, such as applications and services. To satisfy all business requirements, SAP Business Technology Platform Cloud Foundry also supports the lifecycle of other entities that do not match 1-to-1 to CF native entities.
SAP traditionally provides its customers with complex business solutions, which work with their own entities and content. Every service might have its own content with a specific format that is developed, provided, or consumed by end customers.
SAP Workflow Management provides the possibility for SAP partners to develop their own BPM workflows (for example, Leave Request flow) and provide them to end customers. In turn, end customers can easily import and use the developed BPM workflows.
With multitarget applications, you can manage the lifecycle of content provided by different SAP applications. This way, by using one standard approach via an MTA, you can deploy various kinds of SAP application content in your accounts, normally done on the CF space level.
<!-- image -->
##  Restriction
Content deployment used with blue-green deployment will be done during the first phase when idle suffixes and temporary routes are used. The same rule is applicable for all content deployment mechanisms either with direct content deployment or with content deployers ( hdi-deploy , html5-app-deployer , portal deployer ). HTTP Destinations, created with direct content deployment, will not be updated after the validation phase, so avoid using default resolvable parameters ${default-host} , ${default-uri} , ${default-url} . Configurations that include idle suffixes and temporary routes may persist after the MTA deployment finishes. Content that was already deployed during the first phase cannot be reverted or removed. It will be necessary to trigger a new MTA deployment.
## Supported Content Deployment Mechanisms
- Using content applications - there is a dedicated SAP provisioned content deployer for each content type that communicates with the dedicated content backend
- [DEPRECATED] Deploying Content with Simulated App Execution
- Deploying Content with CF task execution
- Using direct content deployment - there is a direct communication between the SAP Cloud Deployment service and the content backends
- Deploying Content with Generic Application Content Deployment
- CPI content deployment
## Supported MTA Module Types for Content Deployment
| Module Type                       | Content Deployment Mechanism           |
|-----------------------------------|----------------------------------------|
| com.sap.portal.site-content       | Simulated App Execution                |
| com.sap.html5.application-content | Simulated App Execution                |
| com.sap.portal.content            | CF task execution                      |
| com.sap.html5.application.content | CF task execution                      |
| com.sap.xs.hdi                    | CF task execution                      |
| com.sap.application.content       | Generic Application Content Deployment |
| com.sap.integration               | CPI content deployment                 |
| com.sap.api.management            | CPI content deployment                 |
For all predefined parameters and properties for each MTA module type, see MTA Module Types [page 626].