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 DS2DIM migration - Steps to properly configure the Item Types in Dimensions
For example, if one of the file types you are migrating has an extension of .java, the file matching pattern %.java will result in items of type SRC being created for those files.
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 KM-Dim7: How to configure Process Modeller to control Power Builder items
PCMS Process Modeller (one time setup per base database): 1. In PCMS Modeller, add item type called Project, attribute = ide_validset (#4), attach valid set = ide_project (this valid set is created by ide setup (start > program > pcms > ide setup)), attach lifecycle for source to item type project. 2. Be sure you have the role of Developer in PCMS Modeller.
CMS-XML Single Source Login and Firefox
To allow Firefox to pass-thru login credentials, you have to modify the about:config preferences for Firefox. To see these preferences, type about: config in the URL/Address line. Two preferences provide the pass-thru behavior:
CMS-XML VM: How to fix errors of the type "The access control database does not contain the privilege <[LoginSource(PrivilegeName)]>."
The user getting this error does not exist in the Access Control Database (ACDB) file for the project, and Version Manager is attempting to automatically add it with the default privilege that was configured for the login source indicated in the error. Unfortunately the ACDB file does not contain the default privilege specified by the administrator, so the user creation step fails with the error indicated above.
CMS-XML Perforce Connector will not load if missing required DLLs
The Perforce Connector will not appear in the Type dropdown when trying to add a defect tracking source in Perforce Defect Tracking Gateway (P4DTG) Configuration Editor if required DLLs are missing on the server. Many of these DLLs are installed with Serena Business Mashups so this problem can occur if P4DTG is installed on a server that does not have SBM installed.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs