1 person found this helpful
1). Export the transfer and respective source and targets. These will be saved as .zip files
2). Export the configuration file for each transfer.
3). create individual configuration files specific to each environment , update the folder paths, FTP host,port, usernames and passwords.
4). Import the zip files into new environment and select the respective configuration file.
I don't think we have a deployment tools to move to the higher environments as the code artifacts are not generating any build.xml and build.properties.
Many thanks for this Dasaradha. Much appreciated!!
Instead of exporting individual source, target and transfer to generate individual zip files, we can just export the transfer and it will internally, bind the required source and target configuration into a single zip
Inorder to incorporate this as part of the Jenkins or so,
- write a utility that can replace the file/FTP path according to target system
- use the WLST command in Jenkins to import and deploy the transfer - https://docs.oracle.com/middleware/12213/soasuite/SOACR/GUID-D15EC622-A20E-4191-AE92-1A6EDE083D15.htm#SOACR504
alternatively, You may also want to look at the out-of-the box feature of T2P (Test-to-Production) option