Managing pre-provisioning and post-provisioning script files

Pre-provisioning and post-provisioning scripts are managed by using the Actions Repository. See Managing Actions. Entries appear on the Custom Scripts Configuration page in provisioning wizards.

You can use the following XML template in either the editable or non-editable section of your template to pre-define or lock down entries.

Note

Entries listed have the pre-provisioning or post-provisioning option selected in the Actions repository.

Scripts are run in the order they are listed in the template.

Example

<!-- Provisioning Scripts Configuration -->
<preprovisioning_scripts>
<!--
Name: Pre-provisioning scripts
Description: List of pre-provisioning scripts to be run.
Required: This is not a required field.
Requirements: The fully qualified name of the Action, as it appears in the Repository, to be run as a pre-script.
<script>/domain_a/db_archivelog_mode_disable</script>
<script>/domain_a/subdomain/check_env_variables</script>
-->
</preprovisioning_scripts>
<postprovisioning_scripts>
<!--
Name: Post-provisioning scripts
Description: The name of the Action to be run as a post-script.
Required: This is not a required field.
Requirements: The fully qualified name of the Action, as it appears in the Repository, to be run as a post-script.
<script>/domain_a/db_archivelog_mode_enable</script>
<script>/domain_a/subdomain/qa_script</script>
-->
</postprovisioning_scripts>

Page tree

Managing pre-provisioning and post-provisioning script files