Neurons for ITSM Deployment Overview

hardware considerations docid\ ijnqbvda6wi1gvunpm5pidemonstration or proof of concept deployment docid\ g8olkisyshsvioayypcucminimum production deployment docid 4c60s2zyg3bmxq48g88szenterprise production deployment docid\ bhapgl 9cpnjelwecs8llsecurity enterprise production deployment docid\ urs3gfpijajxqf78o5lhwdatabase deployment options docid\ h8xefagya8j 286x6q747operations console deployment options docid\ mqkjufzjjfg607d5u6l7xreporting services deployment options docid\ s8cbrq485ram2mpethssqvoice deployment options docid\ nyvwcf6u nfkixnlrkqdd hardware considerations the following factors drive the hardware requirements for a new deployment supports separate landscapes development (also called staging), test (also called uat), and production you can run these landscapes on the same server or isolate them on separate servers if you choose to run them on separate servers, you must provide additional hardware except for the demonstration or proof of concept deployment, we do not recommend putting all of the landscapes on one server you can adjust the amount of hardware used after you deploy your system, after you have collected usage data the software is horizontally and vertically scalable, allowing you to add more hardware to increase performance without license changes