This is the third post in a series about leveraging virtualization for the purpose of hosting an Agile PLM environment. I am basing the series on a development instance of Agile PLM 9.3.0.2 that I need for testing. Thus far we have looked at:

• "Going Virtual with Agile PLM… Don’t Be Scared (Part 1)" which provided a series overview and included the first screen cast on how to create a virtual machine template of Windows Server 2008 SP1
• "Going Virtual with Agile PLM… Provisioning and Preparing the VM (Part 2)"which created our working virtual machine and got the operating system all ready for the installation of the Oracle stack

This post walks you through the actual installation of the Oracle products and Agile PLM.

Keep in mind I am installing this virtual machine for testing and development purposes. We do a lot of Agile Engineering Collaboration work as well as custom development against Agile. The settings I choose may not be appropriate for your environment.

Installing the Oracle Database

Installing the database is very straightforward. All I really needed to do was to verify that it was going to install on the additional data volume I created. Also the screen cast does not show it, but I created a snapshot of the virtual machine after the installation was complete!

Installing & Patching OAS

Installing and Patching OAS is a fairly straight forward process, here are the highlights:

1. Modify the <installer_home>installoraparam.ini file to add server 2008 as a certified version (6.0)
2. Notice that the install path is different than the database installer (product rather than oracleproduct). Be sure to change it now if you want them in the same directory tree
3. Watch the Oracle home directories on the installer and patch installer and select the correct ones
4. Take a snapshot

Installing the Agile database is straightforward. Here are some things to take note of:

1. Install the version you need. We are doing a fresh install so we are going for the gold with 9.3.0.2 out of the box. There is no need to install 9.3 and then run AUT to bring it up to the patch level (we have no data).
2. Check the capacity planning guide to help you decide on the correct size. We are doing a development environment and will have <10 users on it so I chose small
3. If you just need the scripts and do not need the schema installed check the "Generate database scripts only" on the screen where you are prompted for the Oracle SID
4. Again, just because you can change passwords doesn't mean you should. I leave these alone
5. Depending on your resolution the tablespace dialog may extend beyond your screen as it does in our screencast. Just hit enter as the next button is the default
6. A trip to Starbucks is often a good play when executing the database scripts as these can take a while depending on the performance of the machine. Be patient
7. After the install, open the Oracle Net Configuration Assistant to create a listener
8. Use the Net Manager to create a service name
9. Take a snapshot (not shown in the video)

Installing the Agile 9.3 application. Notes:

1. Install Agile 9.3
   1. Copy the <disk 2>platforms directory to the <disk 1>Disk1_Windows directory
   2. Run setup_win.exe
   3. Since I had OAS installed, I selected Advanced Mode
   4. Chained the install drive to my data drive
   5. I selected my existing OAS home directory
   6. We are doing a standalone installation
   7. On the database details dialog box, you will need to scroll down and enter the password for the database.
   8. I do NOT run configure
   9. I do NOT run deployagileplm once complete
   10. I also never start Tomcat
   11. I took a snapshot
2. Install the Agile 9.3.0.2 Patch
   1. Extract the patch
   2. Extract the platforms zip file
   3. Copy the extracted platforms directory contents to the <patch>windows folder
   4. Launch the agile9302_win.exe inside of the <patch>windows folder. Since nothing was deployed and we are in a standalone environment, we have a light work load

AutoVue installation notes:

1. Thus far we have not started Tomcat (File Manager) therefore we do not need to "upgrade" the file manger web application. If we did, we would need to stop Tomcat and move the FileMgr directory out of the <catalina_home>webapps directory. This would cause the modified war to be redeployed on startup
2. You will need to have OAS running and undeployagileplm and redeployagileplm after installation to deploy the modified application
3. Make sure to start both Tomcat and the AutoVue server

Can you tell that I think snapshots are important?