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 SRA: SDA property to obtain the agent hostname
SRA: SDA property to obtain the agent hostname
CMS-XML SDA: Set an environment property from the shell plugin
Is it possible to set an environment property from the shell plugin? We have a shell plugin that will execute some windows commands. We want an output of the shell script to be used later on in other steps of the process.
CMS-XML SDA: How to increment component properties in a process
SDA has the ability to increment component properties in a process using the Set Property utility and the <property name> + 1 as the value. As an example, we have a component property named "number" with an initial value of 1.
CMS-XML SDA: Output properties from the previous step do not have any value when referenced
Within an SDA process, one process step may create output properties with values and a later step may reference these properties. Sometimes the process step creating the property is immediately before the process step that references the new value. In rare circumstances, the 2nd process step may reference the property and the property either does not exist or has no value.
PDF SDA: Getting started with the Commandline client
{ "entityType": "Component", "name": "newComp", " description ": " ... ", " properties ": [ ... ", " description ": "", "secure": false }] }, { "name": "custom", " properties ": [] }, { "name": "template", " properties ": [] } ]}, "processes": [], "taskDefs": [], "configTemplates" ...
CMS-XML SDA: log4j.properties values for debugging LDAP connection issues in SDA
SDA : log4j. properties values for debugging LDAP connection issues in SDA
PDF SDA: Post Processing Script Quick Start Tutorial
A post processing script can be used as a mechanism for collecting output from a particular process step and storing it as a property to be referenced in another step. A typical use case for post processing scripts would be to detect errors or abnormalities in the process step output.
CMS-XML SDA: Post Processing Script Evaluation Getting Started
A post processing script can be used as a mechanism for collecting output from a particular process step and storing it as a property to be referenced in another step. The tutorial describes how you can set up a simple but effective process and post processing script, it assumes that an agent is already connected to the SDA server.
CMS-XML SDA: Escaping certain characters when performing a string comparison in a Switch step
A Component Property is defined called install.dir which needs to be validated in a Switch step so that it doesn't contain a location that shouldn't be used such as C:\. If this string is used the Switch will fail even though you can see that C:\ is being passed via the install.dir property.
CMS-XML SDA: How to edit or change component source type parameters when a template is in use
When a component template is referenced for a component, those properties or parameters that are provided in the template will appear grey in the component and these are not available for change within the component itself. These can only be changed by editing the template.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs