Neurons for ITSM Deployment Overview

hardware considerations docid\ sqqzuvltkztpfuupckd8rdemonstration or proof of concept deployment docid\ og5jz8st0ni2e q5nxpdwminimum production deployment docid\ fqapqyzkylgs3uctcvhnnenterprise production deployment docid\ kbcwcoxa3psvd frmvsjmsecurity enterprise production deployment docid\ u8ooubnobop5etm3km9u0database deployment options docid\ ftnlmendkoje7cj72dzmtoperations console deployment options docid 3hv3oblc u4pkqxpp5vmlreporting services deployment options docid\ z sugcxvlpusr b413ocnvoice deployment options docid\ ugyhuoerghjibwlazvku9 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