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
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 SDA6: How to set up a manual task that requires approval from a different person depending on the environment it is running against
In the process editor, add the manual task and in the property labeled "Environment Role" add the name of this role created in above step. Save the process.
CMS-XML SDA: Configuring Unauthenticated Mode for HTTP Communications
The installed. properties file contains the properties that were set during installation.
CMS-XML Unknown object property -- ERR #8 when using Keys or Items method of the Scripting.Dictionary object
next Call Shell.Item.SetFieldValue(" DESCRIPTION ",s) set d=nothing
CMS-XML SDA: How to configure tomcat to start a new logfile when the current log file becomes a certain size
To change settings for the log files associated with the serena_ra web application, open the file: <tomcat-root>\webapps\serena_ra\WEB-INF\init\conf\log4j.properties For each file for which you wish to restrict the size, add a MaxFilesSize property , such as: log4j.appender.console.MaxFilesSize=10MB
PDF 11019202a0ae7e6015d7a836d3a00701d#SDA 6.1.4 WebServices DA Tutorial.pdf
http://<hostname>:8080/da/rest/deploy/application/allPaged?inactive=false&orderField=c reated&pageNumber=1&rowsPerPage=10&searchQuery=&sortType=desc&userType=currentUser Note: <hostname> change to reflect the hostname of the DA server  Request method: GET  Destination: Step properties  Join the steps together
CMS-XML How to configure SDA to send completion notifications to Release Control
Attached to this article is an export of a generic process example: send notification to RLC.json. Also attached are several screenshots showing generic and component process and property setting examples. You can import the json file and use the example screenshots to help you configure the SDA process and properties as needed to use the Release Control.
CMS-XML SDA: Agent does not appear in the UI - run mode does not start but hangs at: 2014-10-22 08:08:45,065 - Agent version: 5.1.2.85
2. Value of “External Agent URL” system property (can be found at SDA Server UI, Administration->System->System Settings) is referencing value that is resolvable from agent side. 3. All files within the Agent installation are owned by the user that is running the agent, to do this run: chown -R <user> <path to SRA agent> e.g. chown -R serena "/opt/serena/Deployment Automation Agent"
PDF SDA Jenkins plugin getting started tutorial
Step 5: Add a Get build status step This step, will obtain the success status of a Jenkins Job execution, and store it in a property . Below Available Plugin Steps, under Integration | Jenkins select Get build status and drag the new step below the Submit step.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs