End-to-End Workflow for Windchill+ Deployment with CCD Utility

Customization > Getting Started with Windchill+ > End-to-End Workflow for Windchill+ Deployment with CCD Utility

The following process describes the end-to-end workflow for Windchill+ deployment with the Code and Configuration Deployment (CCD) utility:

1. Review and understand the Windchill+ system landscape. For more information, see Windchill+ System Landscape.

2. Review and understand Windchill+ Guidelines and Guardrails and Allowed Customization.

3. Install a development Windchill PDMLink instance on a host machine of your choice. The operating system on the host machine can be Windows or Linux. The host machine is typically a virtual machine.

Alternatively, you can use the PTC provided cloud portal templates. For more information, contact your PTC partner.

The Organization Internet Domain (OID) must be set to ptcmscloud.com else deployment of the CCD package deployment fails. For more information, see Installing Windchill.

4. Install your preferred integrated development environment (IDE) on your development instance of Windchill. For example, Eclipse, NetBeans, and so on.

This workflow example considers that you are using Eclipse as the IDE. Use the following link to install Eclipse: Eclipse.

5. Setup your CCD package structure. For more information, see Deploying Code and Configuration Package.

A manifest file is required to trigger the automatic build deployment. For more information, see the Creating and Deploying a Build Package section in Deploying Code and Configuration Package.

6. Implement your customization as per the information provided in the Windchill+ Customization section.

For more information, see the following topics:

◦ Customization

◦ Use Case 1: Customizing and Loading Workflow Templates

◦ Use Case 2: Creating Custom Business Rules

7. Use the Code and Configuration Deployment (CCD) utility and test your deployment using the deploy target of the CCD. For more information, see External Targets and Deploy Your Customizations on Your Development Environment.

Depending on your CCD use case, you may find it helpful to have a second OOTB Windchill virtual machine image available as a pseudo target for testing the deployment ability of your package.

8. Submit your package to your PTC-hosted Azure Storage Account. You can use Azure BLOB storage commands such as the Azure AzCopy CLI tool or Azure Storage Explorer.

9. Test your new functionality in the provided Windchill+ integration instance. For more information, see Installing Windchill.

10. Promote your package to Windchill+ production through the release management pipeline. For more information, see Submitting and Promoting Your Package.