How is RAAS Configured?
The RAAS administrator will configure up to eight criteria your organization wishes to track for each change requests. for example, you may choose “Release Number”, “Customer”, “Release Date”, “Bug Tracking Number”, etc. Anything you wish. (Requester and Approver logins, as well as request date, are captured by default). Once a request is entered, these configured fields may be used to search for changes waiting approval, and then used as criteria to generate SQL release scripts. For example, using the fields listed above, a script may be generated for “Release Number = 2.5” and “Customer = Base”. RAAS Security is also configurable, allowing you to control who may submit changes, approve changes, create scripts, etc. See the below for additional information on RAAS Security.
Related Questions
- When I have a static route and RIP configured on a router, why is it that the static route with an administrative distance of 1 is preferred over RIP routes with an administrative distance of 120?
- I have caches configured with asynchronous replication or distribution, but these caches appear to be behaving synchronously (waiting for responses), what is going on?
- Webserver 6.1 is configured for HTTP compression on demand. Why do I see that requests going through the weblogics proxy plugin (wl_proxy) are not being compressed?
