Issue:
Customers and partners may inadvertently build or develop around components that they are not licensed for in IFS Cloud. This issue arises due to the following:
- Initial Provisioning Includes Most Components: Upon initial IFS Cloud provisioning, nearly all components are deployed to the Workspace/BuildHome file structure, even if they are not activated in the customer's solution set.
- Solution Set Activation: Only components explicitly marked as active in the solution set file (solutionset.yaml) are truly enabled for use.
- Developer Confusion: The presence of inactive components can lead to confusion, potentially resulting in development work on components that are not licensed.
Solution:
To prevent development on unlicensed components, it is strongly recommended to deploy the initial delivery to each Use Place environment before development work begins. This proactive deployment ensures that environments contain only the components that are licensed and activated, eliminating potential confusion.
Steps:
- Configure Build Place Mode of Implementation:
- This step must be performed by a Build Place Technician User.
- Refer to the official documentation for detailed instructions: https://docs.ifs.com/techdocs/ale/020_lifecycle/020_getting_started/010_rmode_of_implementation/#configuring_mode_of_implementation
- Deploy Initial Delivery to Use Place Environments:
- Initiate the deployment process to ensure that each Use Place environment reflects the licensed components accurately.
- Log on to https://support.ifs.com > Request a Service > Request a Cloud Service > select the IFS Cloud Lifecycle Experience Use Place Management form.
- This process will need to be repeated for each Use Place environment; by default, IFS Cloud comes with three Use Place environments: PRD, UAT, and CFG.
Additional Information:
- Workspace/BuildHome Structure: In IFS Cloud, this structure always contains all components provided by IFS, regardless of activation status. This differs from previous IFS Applications versions where only installed components were physically present.
- Solution Set Configuration: The solutionset.yaml file dictates which components are enabled and installed. See Working with Solution Sets - Technical Documentation For IFS Cloud for more details.
By following these guidelines, you can effectively prevent development work on unlicensed components and ensure that development efforts align with your IFS Cloud license entitlements.