Operations Console Overview

this section contains the following a brief description of the operations console features see about the operations console docid\ t7qelrq0 dn nuamfc3da instructions for navigating the operations console interface see operations console interface docid\ ay7 esiqbyibct2dgixuy a summary of the actions that you can perform from each area of the operations console see about the different workspaces in the operations console docid\ ay7 esiqbyibct2dgixuy terminology used in this guide, including definitions of data types see terminology docid srybeqnhr2outxjfw8z instructions for installing and logging in to the operations console see installing the operations console docid\ fyh4m3bh2ryxhomzmhohu and accessing the operations console docid\ fyh4m3bh2ryxhomzmhohu about the operations console the operations console provides an interface in which you can make changes to your ivanti service manager system (usually in the staging instance of the tenant), test the changes (usually in the uat instance of the tenant), and then deploy them (to the production instance of the tenant) you can manage tenant instances in the production (live system), staging (development system where initial changes are made), uat (preproduction system where changes are tested), pilot, and other landscapes for example, in any landscape you can create tenant instances edit the properties of tenant instances lock a tenant instance so that its metadata cannot be modified deactivate and delete tenant instances update tenant instances by migrating data from one tenant instance to another control the timing of tenant development and deployment the operations console supports these capabilities by connecting to the ivanti service manager configuration server in each landscape the operations console has its own login credentials and database, which provide logging and other tenant management history capabilities the operations console also provides you with a direct connection to the ivanti service manager configuration database in each landscape, allowing you to manage the ivanti service manager configuration database for that landscape without going through the ivanti service manager configuration server the operations console requires a database connection to the ivanti service manager configuration database, a database connection to the ivanti service manager application database, and a web services connection to the ivanti service manager application database