CatalogDeployer is a content deployment and change management tool which enables service designers, catalog publishers, and organization builders to easily deploy content.
CatalogDeployer supports the migration of newScale application entities between development, test, and production sites, and provides easy access to the change management process and history.
Users of CatalogDeployer follow this process:
Create a Deployment Package. Persons granted permission to access and use CatalogDeployer can create a deployment package, select the names of the entities to be included in the package, and save the package.
Assemble the Package. When the underlying content is considered ready for deployment, the package is assembled. When you click the "Assemble Package" button, CatalogDeployer extracts the content and creates a copy saved as part of the deployment package. Until you assemble the package, you may continue to edit a service definition in ServiceDesigner until it is ready. Once the assembly has occurred, any changes to the underlying service definition are not captured unless you re-assemble the package.
Transmit the Package. The assembled package is sent to the target site for deployment. You may directly transmit the package to a target site from CatalogDeployer. However, if you do not have direct connectivity between source and target sites, you may perform this step "off-line" using the Export and Import process.
Deploy the Package. A person with permission to deploy the package selects the received package on the target site and runs the deployment process.
Re-deploy. The same package can be transmitted and deployed to another site. This is especially useful as part of a change management process. For example, once you have successfully tested the initial deployment of new content in a test environment, the identical deployment package content can be transmitted and deployed to a production environment.
This document explains the logic to develop Tidal Enterprise
Orchestrator workflow to automate the process of creating vCenter
Resource Pool* vSphere Power CLI must be installed either on the TEO
server or vCenter* vMA can also be used to achieve the same...
IntorductionCisco Process Orcehstrator (CPO) ships with the webservices
adapter that can be used to make Web Service API call to REST or SOAP
based applications. Before a sample workflow to make SOAP API calls
using CPO, lets understand some of the fundam...