I am working with our IT team to plan a windchill implementation. I have been trying to research information regarding architecture strategies for implementing development and test environments along-side a production environment of Windcill. Coming up short, I have some questions regarding best practices. Any advice, or links to documentation, would be appreciated.
1) With SQL as the database server, should 1 SQL instance with a DB for each environment be used? Or should there be a separate instance of SQL for each environment?
2) Use VM for the dev/test environments on the production application server? OR use a separate application server for each instance of Windchill?
Thanks in advance for any support!
With the DB you can it either way and there should not be any noticeable difference. I use Oracle and have done it both ways.
Do not run your VM test/Dev environment on your production server. You can run test/Dev on VM on another physical box, but let the physical production do its thing alone.
We run all of our servers as VMs. I would suggest running your database on a completely different VM from production so you can test OS and database patches and updates without impacting the production system. I also prefer having the database running on a different VM than the Windchill application, but there are plenty of people who run them together. Keep in mind that you shouldn't need to purchase expensive processor licenses for the test SQL system. You should be able to just run SQL developer edition.
To answer your questions (and in agreement with Ben and Tom):
One common implementation strategy I have seen:
That's my two cents.
A lot of these questions do depend on your user count and the level of "depth" to which Windchill will be used. Will it be used for the full-fledged PLM capabilities (EPMDocs, WTParts, WTDocs, workflows, representations, publishing, etc)? Or just for document control? Or somewhere in between?
Can you comment on that?
Thanks for feedback Bob, very insightful. We intend to use full PLM Capabilities and will have about 100 active users.
No problem, Anthony.
We'd be happy to help in any stages of the implementation, whether it be the technical, systemic implementation or, after installation, the use of and adoption by the business through optimal setup of the Windchill business elements (ACLs, OIRs, object types, contexts, teams, life cycles, workflows, modules, etc).
Feel free to contact me directly via e-mail if you are ever interested in some assistance with your implementation.