Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML DA: Is it possible to pass the Maven Source Config Type Group ID and Artifact ID values as part of the process?
Is it possible to pass the Maven Source Config Type Group ID and Artifact ID values as part of the component process? The documentation only mentions ${p:component.id} and ${p:component.name}.
CMS-XML Deployment Automation 6.1.5: Supporting files for Creating Custom Source Configuration Types
This solution is for DA 6.1.5 only. If you are using DA version 6.2 or later, see the KB item S142533 .
CMS-XML Deployment Automation 6.2: Supporting files for Creating Custom External Source Configuration Types
You can create your own external source configuration types to use for your components in DA 6.1.5 and later. This KB item is for DA 6.2. If you are using DA 6.1.5, see the related KB item, S142231 .
CMS-XML Cannot see Source Configuration Type values from Template while edit a component
Cannot see Source Configuration Type values from Template while edit a component
CMS-XML DA: Changing component template value does not change URL
Two component templates, A and B, were defined using source config type "Maven". The repository URL is different for each of them.
CMS-XML DA: Manual import of component version creates incorrect version if incorrect version number is supplied
If a component is configured with source type Maven and a user specifies a non-existent version number during a manual import request, DA would create an empty component version with this non-existent version number. Request that this be changed to log this as a non-existent version and do not create a version if none exists in Maven/Artifactory.
CMS-XML DA: Using curl for DA commands when DA is configured for SSO authentication
The attached example shell script is provided as an example only. This assumes that the SSO source is from SBM.
PDF 11019235233eed01603902280f007a42#CM 14.4 Install DA Demo App on PostGreSQL.pdf
Step 6: Configure and add a component version 1. Select Home Menu | Management | Components and DemoComponent now appears 2. Click DemoComponent 3. Click Details then Edit 4. From the Source Config Type drop down, select File System (Versioned) 5. Supply a value for Base Path e.g. c:\ da \democomp1 and click Save 6. Create the Base path on the DA server machine, along with a version subdirectory: e.g.
PDF Deployment Automation Artifactory Tutorial (DA 6.1.4)
 In DA go to Management | Components click on Create Component  Specify the following values for: o Name: ArtComp1 o Source Config Type : Artifactory – Folder Based o Server URL: http://localhost:8081/artifactory o Username: admin o Password: password o Repository: example-repo-local SDA 6.14 Artifactory Tutorial Page 9
CMS-XML SDA: Unable to import versions from PVCS Version Manager
A component was created in SDA with Source Config Type of PVCS. When an attempt was made to import versions from PVCS nothing happened, there were no messages on screen to indicate failure or warnings as to what the problems were that prevented the versions from being imported.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs