Have you ever had the need to move production Agile PLM content into a development or QA environment for testing purposes, but didn’t know how? If so, this blogs for you! It is a straight forward task so follow along and learn how. Given that most of my customer’s environments are Windows based, I will be using the same for the example.
Please note: these instructions are for an out of the box implementation. If you have modified the par files or performed some other customization, like running in a federated environment, then you will need to do your due diligence to ensure the proper migration of your data!
1. Capture your current QA URLs which you will need later by opening a browser to http://<qa-machine>:8080/Filemgr/Configuration and save a screenshot
2. Get your current file vault location for both environments
a. Open the Java Client, logging in as an administrator
b. Navigate to the Admin tab | Server Settings | Locations
c. Click the File Manager tab
d. Double click the row that has Primary File manager set to Yes
e. Note the Base Storage Directory (our is E:AgileVault)
3. Stop the production application server.
a. Open the Services console by navigating to Start | Control Panel | Administrative Tools | Services
b. Stop the service named “Oracle-<name>Process Manager
c. Also stop Apache Tomcat tomcat6 (though it’s not really required)
4. Take a database dump on the production database server
a. Open a command window, on the database server, to <oracle_home>adminagile9createagile
b. If agile9exp.dmp exists in the directory, rename it in case you need to revert to that point in time
c. Some people prefer data pump; however, I use the regular export unless the data set is known to be very large. Execute the command: agile9exp.bat
d. Once the export is complete you will have a new file named agile9exp.dmp
5. On the QA application server machine, stop the application server and Tomcat. This is the same as step 3 above only it is performed on the machine you are copying to.
6. Copy the vault files from the production file manager (application server) to the QA file manager
a. Open windows explorer in QA to your vault location. Ours is E:AgileVault
b. Move the current subdirectories in the vault location to another directory, or delete them, depending on your needs
c. On the QA machine open another windows explorer browser to the vault location on your production server. Ours is \vm-agile9302e$AgileVault
d. Highlight the 000 and purge folders on the production server and drag them (or copy them) to the QA windows explorer window.
7. Restart the production environment
a. Open the Services console by navigating to Start | Control Panel | Administrative Tools | Services if it is not still open from earlier
b. Start the service named “Oracle-<name>Process Manager
c. Start the service named Apache Tomcat tomcat6 if you stopped it above
d. Open a browser to http://<production-machine>:8080/Filemgr/Configuration and verify that everything has a status of “success”
8. Copy the database dump file from the production database server to the QA database server
a. Open windows explorer in QA to your dump location. Ours is
b. If agile9exp.dmp exists, rename it or move it to another directory
c. On the QA machine open another windows explorer browser to the dump location on your production server. Ours is \vm-agile9302e$oracleadminagile9createagile
d. Highlight the agile9exp.dmp file and copy it from production to QA
9. Import the dump file in QA
a. Open a command window, on the QA database server, to <oracle_home>adminagile9createagile
b. Recreate the agile schema by executing: recreateagile.bat
c. Above we did not use data pump, therefore we will execute the command: agile9imp.bat
10. Restart the application server in the QA environment
a. Open the Services console by navigating to Start | Control Panel | Administrative Tools | Services if it is not still open from earlier
b. Start the service named “Oracle-<name>Process Manager"
11. Set the Server Locations in QA using the URLs seen in step 1 above
a. Open the Java Client, logging in as an administrator
b. Navigate to the Admin tab | Server Settings | Locations
i. Set the Web Server URL to the URL save earlier: http://vm-rmccabe:80/Agile/PLMServlet
ii. Set the Java Client URL: http://vm-rmccabe:80/JavaClient/start.jsp
iii. Click the save button
c. Click the File Manager tab
d. Double click the row that has Primary File manager set to Yes
i. Set the File Manager URL: http://vm-rmccabe:8080/Filemgr/AttachmentServlet
ii. Click the “Advanced >>” button and the configuration should propagate
iii. If the vault location is in a different directory in QA, set the vault location
iv. Click the ok button
12. Restart the QA environment
a. Start the service named Apache Tomcat tomcat6 if you stopped it above
b. Open a browser to http://<qa-machine>:8080/Filemgr/Configuration and verify that everything has a status of “success”
While this seems like a lot of steps, it really is fairly straight forward. As always, please comment if you have questions.