Deploying Modeled Portal Content 
Deploying modeled portal content models creates the content in the portal exactly as it was modeled in Visual Composer. If you modeled an iView into a page and then deploy the page, with its dependencies, it will appear in the portal with the iViews inside it. Similarly, if you modeled a Business Suite work center containing multiple views, each containing pages and iViews, deploying the work center, with dependencies, creates it in the portal with all its contents.
Deployment takes place on the level of the development component (DC). The deployment process compiles and deploys the models and applications you added to the development component, together with any reused models or components.
You can deploy modeled content in two ways:
Models maintained with version-control in the DTR, are deployed to the portal with each build of the central build server (CBS). This method of deployment is automatic and occurs according to the build schedule.
You can initiate deployment yourself in the Deploy task panel (fast deployment). The following procedure here describes this method of deployment.
Deployment of Development Component
Because deployment of portal content from the Visual Composer is on the development component level, there is no necessity to wrap content in transport packages (EPAs), as with other methods of deployment of content from the portal.
Including Dependencies
As mentioned in the procedure in this section, compilation and deployment of a development component can include, if desired, the dependencies of the models contained in the development component. If dependencies are contained in a different development component, that development component is also compiled and/or deployed, and so on throughout the dependency chain.
Dependencies are included in compilation by default, but for performance, it is important to consider whether or not you need to include dependencies. You may want to compile changes to certain models in one development component without having to compile another development component as well.
Note
Reused non-modeled content, must be transported using another deployment tool, such as CTS, NWDI, or the portal transport tools, if you deploy to another portal system than the one from which you obtained that content. (More information using the links below.)
Prerequisites
The model you want to deploy is open in Visual Composer.
Procedure
Open the Deploy task panel.
The name of the development component appears in the DC field.
Select the Include dependencies checkbox, if desired
(Optional) Click Compile if you want to validate and compile a model into XGL format, without deploying it.
The compilation script is read-only and is useful only to developers for validation purposes.
NoteAlthough deployment processes the entire development component, only changed components are compiled.
End of the note.Click Deploy to compile and deploy the models contained in the development component to the portal.
A progress bar appears showing that compilation and deployment are taking place.
Result
When compilation and deployment are complete, an expanded node appears, representing the development component. Under the development component name, all the deployed models are listed as links that you can use to preview them.
Content modeled in Visual Composer is now available as portal objects located in the PCD.
Deployment Locations in the Portal Catalog
Whichever deployment method you use, the process deploys models to predefined folders in the Portal Catalog, according to the vendor name. The deployment process recognizes the vendor, which is indicated in the name of the development component.
Content from SAP Vendor |
Content from Non-SAP Vendor |
|---|---|
|
|
Portal Content 
Content Provided by SAP 