WEF and WP environment — high-level release steps
To recap, the A2Z portal is successfully installed on the internally managed integration system. The A2Z development portal systems are available on the development cloud. We carefully followed best practices from the information center. Let's first look at the high-level task flow for the portal build and deploy. Then we can look how a more granular task flow can be documented, implemented, and automated. At a high level, there is a process flow for the release management of portal artifacts that has four steps to be followed. First, the source environment needs to be prepared; secondly, the release needs to be built; thirdly, the target environment needs to be prepared, and finally the business release needs to be imported into the target environment.
The following are the high-level release steps:
1. Export the A2Z source portal configuration using the XMLAccess commands.
2. Bundle the supporting files from the source A2Z portal.
3. Transfer...
