You can download a PDF or an EPUB file of an article or content area for offline use. You can choose what you want to download— a page. your use of the CA software to which the Documentation relates; or (ii) a VB record length Action Option field on the CA Endevor Quick-Edit Option panel. Welcome to the CA Endevor Software Change Manager Version bookshelf. Use the Search field on this bookshelf to search the product documentation.
|Published (Last):||22 June 2006|
|PDF File Size:||20.4 Mb|
|ePub File Size:||14.35 Mb|
|Price:||Free* [*Free Regsitration Required]|
I am new to Endevor. This allows for the users of Endevor, such as developers, to be separated from the control of the objects which they modify using Endevor functions.
The ADD function invokes a generate processor which then executes all actions required to register or update the element metadata and process outputs. Access to Endevor Environments is defined by a single security table per Endevor environment.
Could you please provide me the link of Study Material for the same? This ensures that the only way to generate and promote code is via Endevor and provides an audit trail of all changes. Endevor maintains configuration control for each element registered in the system.
The first userid in an approver group is generally always set to be the Endevor internal system userid “NDVR” which grants the Endevor batch system the authority to execute package actions. Endevor provides control of source and related code objects as individual elements.
Each approver in an approver group can be defined as being a mandatory or optional approver by specifying a flag in the approver group definition. As such, control of source happens internally to Endevor and source control actions are separate from changes to objects in the output libraries which includes load modules and copies of processed code. Endevor native security is a built in security option which allows Endevor Administrators to define approver groups per Endevor Environment, approver group relationships per Endevor Environment and security tables per Endevor Environment and for specific Endevor functions.
Unsupported SSL/TLS Version
Endevor administrators can modify Endevor functions and capture information using exits. Your local Endevor administrators should have documentation to get help you started and visualise the system configuration.
The Endevor application executes system actions using two dedicated system accounts for which have the access to write to Endevor controlled libraries. All Endevor element functions are described using a propriety Software Control Language. Many functions executed in interactive mode are completed in batch mode.
Every type has at least one processor defined for which lists the name of the processor that performs the action required. Views Read Edit View history. The Endevor user guide will help you get started.
Retrieved 15 May Email Required, but never shown.
Endevor – Wikipedia
This is due to the security model within Endevor for which requires explicit security access. You can also find this documentation via google.
Much of what you really need to actually use Endevor will be dependant on how Endevor is customised at your shop. An Endevor exit program has access to most of the information relevant to the action being performed, for example name of the package, package action, package contents, etc. The same functionality for source control and release management functions are provided by several other products. As Endevor provides an interface for creating, modifying, moving, deleting and transferring elements via pre-defined lifecycles there is no need for any end user to have alter or update access to libraries controlled by Endevor.
As an example, an exit could fail the generate action where the CCID is invalid. The system uses these values to determine the source and target locations. Generally, there is one security table per Endevor environment, however a single security da-endevor can be referenced by multiple environments.
This article needs additional citations for verification. Articles needing additional references from August All articles needing additional references. This means for every system referenced in the package there will be at least one approval required.
Supported Releases of CA Endevor® SCM
An exit is generally used to determine when and to whom to send emails to, for example to notify Endevor approvers that a package is waiting to be reviewed or that a package has been reset. The SCL manaual is ftp: As an example, an exit could be written to trigger “before package cast” to link an additional approver group to the package being cast.
I did not attempt to register so have not gained further access to their documentation from this site. August Learn how and when to remove this template message. This means that if the internal Endevor system userid is not linked into one of the approver groups when a package is cast then the Endevor batch system can not execute commands against that package. Each security group specifies a list of users authorised to act for that group with a set quorum per group.
Each approver group has a set quorum for which can be set to 0 to I found the following documents “floating” around but they provide a very limited view of the product: The reference “element” is used to define the smallest object for which Endevor controls. An approver group quorum ca-endfvor zero is used for approver groups where the users either need to be informed of package actions or users require the ability to DENY a package but are not explicitly required to approve.
Endevor supports release management in the form of package control. Moves an element from any source stage to any target stage. Systems with names in italics are no longer maintained or have planned end-of-life dates.