Post Refresh Request enables an instance in an environment to be refreshed to its original state after that instance has been cloned from another environment. Post Refresh will identify all the projects that are different in the Source environment Instance combination verses the target environment Instance combination. If a project is a partial deploy project, it will also determine which files are different between the source and target. If there are files that are different, a package with be built that contain only those files. Then the original project versions (or the newly rebuilt package for partial deploy) from the target environment will be redeployed to target environment. If the project was only deployed to the target environment, then it will be deployed again.
This is needed when an EBS environment such as development is cloned from production. Once the clone is complete, you can initiate the Post Refresh requests for the target environment. Any changes that you have in that development environment that may have been lost because of the clone in the development environment will be redeployed.
| Info |
|---|
Post Refresh is not compatible with Partial Oracle Database projects, or any partial objects that are sourced from a server without source control at this time. If you require this, please create a support request. |
Viewing and Creating Post Refresh Requests
The Post Refresh Requests button is on the Environment Instance page, first select Topology from the menu, then select the Topology Overview section. Next locate the Environment and Instance to view or create Post Refresh Requests.
On Environment Instance page, click the Post Refresh Requests button on top right corner to view the Post Refresh Requests.
...
Field Name | Required | Description |
|---|---|---|
Source Instance | Yes | Short name for the Instance used as the source for the refreshName of the instance that you cloned to the target. Any projects which are not in sync between the source and the target will be redeployed. |
Source Environment | Yes | Short name for the Environment used as the source for the refreshName of the environment that you cloned to the target. Any projects which are not in sync between the source and the target will be redeployed. |
Requested Start Time | Yes | Start Time for the refresh deployments to begin. |
...
This page shows the Post Refresh status and workflow request status. Please refer refer to Build & Deploy Projects to know status for more information about the lifecycle of a workflow request and its workflow execution.
The Project Name column contains lists a list of all projects to be redeployed. Click each project to view the files under each project if they are partial deploy projects.
Viewing PostRefreshRequest Pos tRefresh Request Status
PostRefreshRequest The screen where all the projects' details and the workflow request status statuses are shown.
The possible Post Refresh Refresh Status and its description Statuses and their descriptions are shown below. This gets changed They get updated based on the workflow request status.
| Request Status | Description |
|---|---|
| Pending | When new POST refresh request is created with all the WF workflow Build requests |
| Deploying | WF Workflow requests for the post refresh request is are being submitted for DEPLOY |
| Complete | All the WF Workflow requests for the Post refresh status is are either Completed or , Failed or , Aborted, or RejecetdRejected |