The Biggest Agile Installation Mistake Has Nothing to Do With Agile
By Terri Hiskey-Oracle on Jan 23, 2014
Domain Systems is one of our PLM Preferred Sponsors of the 2014 Oracle Value Chain Summit. Attending the Summit? Be sure to visit Domain at Pod 117 and learn more about their expertise in the guest blog below.
Oracle Agile PLM is designed to be an out of the box solution insofar as setting up the infrastructure is concerned, which is why Agile is so popular with the world’s most successful brands. Installing or upgrading Agile PLM can be a very stressful project though--a lot is on the line. One of the biggest downfalls companies make when installing Agile PLM is mistaking the installation recommendations as not being part of out of the box functionality and flexibility Agile offers. In order to find the functional agility you are looking for, it is critical that you establish the best foundation possible for Agile PLM, and that is achieved by following the installation instructions. Where most companies deviate from the installation instructions:
1. Shared Server. Agile PLM prefers to have a stand-alone instance, or be on its own server. Most companies, who install Agile onto a shared server, won’t install the example software that drives the search functionality. This is just one technical reason why you need your own server. There are many other reasons.
2. Violating or Modifying Out of the Box Oracle Security Policies. We've seen some instances where customers modify out of the box security policies, and it prevents some accounts from having certain privileges. This can prevent Agile from starting or operating at an optimal level because Agile is designed to have a specific security level, but when installed, the accounts did not have the security levels that were required.
3. Poor Database Structure. Everyone wants to do things better. In this case, trust the recommendations when installing Oracle Database. This is critical to maintaining a solid data structure.
4. Overriding the Schema Installer. Let the schema installer do its job. Don't change what the schema installer wants to do. Our experience is that the companies that try to change this part of the process never end up having a good installation experience.
Follow these four in-the-box guidelines for installing Agile PLM, and you'll be much more likely to enjoy the out-of-the-box experience you are expecting.
Heading to the 2014 Oracle Value Chain Summit? Join Domain Systems for an after-hours party on Tuesday, February 4. Enjoy networking with other PLM professionals over craft beer, gourmet sausages and grilled cheese sandwiches and much more! Send an email to James Keddington to request an invitation.