Code and Configuration Deployment Utility for Windchill Customization
You can use the CCD (Code and Configuration Deployment) utility to standardize customization processes for Windchill on-prem development environments before promoting them to test or production. This documentation provides a straightforward minimal workflow and guidance for leveraging CCD, focusing on the package structure and targets. Using the CCD utility ensures that the customizations align with PTC Windchill+ standards, preparing you for a potential transition to SaaS while maintaining control over your on-prem deployment.
|
|
• For the Windchill on-prem environment, the CCD process is a customer-run activity. You take full responsibility for managing your automation and deployment. For more information, see the Windchill+ Help Center. The information in this topic is intended for PTC customers who perform testing and validation of Windchill on-prem customizations. PTC does not commit to providing any unique artifact and non-artifact deliverables, SPR fixes, or upgrade support as part of this customer-run activity.
• The CCD utility is available only through the Windchill shell command-line interface. When executed, the utility automatically authenticates with site administrator privileges by using the specified site administrator username.
|
Overview
You can prepare your on-prem customizations to align with Windchill+. This process introduces a structured approach with validation steps to ensure consistency and readiness for the transition from Windchill on-prem to Windchill+, verifying that the customizations comply with PTC guidelines and guardrails.
Currently, existing on-prem customizations often lack guardrails and follow varied approaches. The CCD package structure and targets establish a standardized framework for effectively managing and validating these customizations.
Key Points
• Use CCD in your Windchill development environment.
• Create customizations according to your requirements.
• Ensure alignment with the Windchill+ CCD standard.
Benefits
• Enforces a structured approach for customization.
• Simplifies validation and reduces errors.
• Prepares your environment for a smoother transition to Windchill+.
|
|
Ensure that all customizations adhere to the provided structure before deployment. For more information, see the Windchill+ Help Center.
|
Customization and Configuration Deployment Workflow
The system follows a three-step workflow for CCD:
1. Create the Build Package
a. Develop your customizations in your development environment.
b. Structure your package according to the CCD specification.
c. Store your package in a user-defined directory.
| Use the create.package target to create an empty CCD package structure. For more information, see Targets. |
2. Test and Validate the Build Package
a. Use the provided targets to validate your customizations. For more information, see
Targets.
b. Perform pre-validation testing in your own on-prem environment.
| Do not deploy anything to production without thorough validation. |
3. Deploy to Production
a. Deploy your validated package to your production environment.
b. Use targets, such as compile, load, deploy, and test, for unit testing and deployment.
c. Repeat the process as needed for subsequent deployments.
CCD Package Structure and Targets
• While working on the CCD package, focus on the essential elements such as the package structure and targets. For more information, see
Targets.
Tutorials and Use Cases
Refer to the tutorials provided for practical examples. Treat these tutorials as references and adjust them as needed for your environment. For more information, see
Customization Examples with CCD.
Parent topic