Configuring Landscapes

for a definition of landscape and common landscape types, see landscapes docid srybeqnhr2outxjfw8z about the landscape workspace docid\ ohfv7pbfadpqn00kclhpnworking with landscape groups docid\ ohfv7pbfadpqn00kclhpnworking with landscapes docid\ ohfv7pbfadpqn00kclhpnworking with database servers docid\ ohfv7pbfadpqn00kclhpn about the landscape workspace use the landscape workspace to perform a variety of landscape management activities, including creating and configuring landscape groups, landscapes, and database servers you must create a landscape group before you can create a landscape, and you must create a landscape before you can create any tenants working with landscape groups about landscape groups docid\ ohfv7pbfadpqn00kclhpnadding a landscape group docid\ ohfv7pbfadpqn00kclhpnediting a landscape group docid\ ohfv7pbfadpqn00kclhpndeleting a landscape group docid\ ohfv7pbfadpqn00kclhpn about landscape groups a landscape group is a group comprised of different landscapes the following are examples of landscape groups independent landscapes group the production, staging, and uat landscapes all have different ivanti service manager configuration databases each landscape is on a separate server which makes it easier to independently shut down or restart the servers, if needed however, this option requires more hardware, which means you need additional licenses shared landscapes group the production landscape has its own ivanti service manager configuration database and the staging and uat landscapes share the same ivanti service manager configuration database this makes it easier to perform upgrades because you have to upgrade the staging and uat landscapes at the same time (all landscapes must use the same release of ivanti service manager in order to migrate data ) this is typically how ivanti service manager cloud systems are deployed all in one landscape group the production, staging, and uat landscapes all share the same ivanti service manager configuration database and servers this deployment is used mainly by testing and development teams or systems with limited resources we recommend using either an independent or shared landscape group however, there are advantages and disadvantages to each landscape group see the installation and deployment guide for ivanti service manager for more information about the different deployment types we highly recommend that you only install the operations console in the staging landscape, and not in any other landscape for migrating data, you only need to install the operations console in one landscape; you should not install it in more than one landscape adding a landscape group you must add a landscape group before you can add any landscapes to add a landscape group, do the following log in to the operations console click the landscape tab the system displays the landscape workspace click landscape group on the left the system displays all of the landscape groups in the system click add landscape group the system displays the add new landscape group page see add new landscape group page docid\ ohfv7pbfadpqn00kclhpn add new landscape group page enter a name for the landscape group choose the default backup type you can either select microsoft sql or litespeed note that litespeed is not supported for ivanti service manager on premise customers if you selected litespeed as the default backup type, you must check litespeed enabled otherwise, leave it empty ivanti service manager supports using litespeed for microsoft sql server for backing up your ivanti service manager databases before you can use litespeed for microsoft sql server, you must purchase it, install it on your system, and configure the operations console to support it ensure that two tier landscape is not checked with a two tier landscape group, the migration path is only between two tenant instances, usually the production instance of the tenant and the staging instance of the tenant if you do not check th is option, you have a three tier landscape group with a three tier landscape group, there are migration paths between three tenant instances, usually the production instance of the tenant, the staging instance of the tenant, and the uat instance of the tenant we recommend always using a three tier landscape group unless you have a demo environment click save editing a landscape group log in to the operations console click the landscape tab the system displays the landscape workspace click landscape group on the left the system displays all of the landscape groups in the system do one of the following click the underlined name of the landscape group in the resulting dialog box, click edit click the pencil icon to the right of the landscape group name edit the values click save deleting a landscape group log in to the operations console click the landscape tab the system displays the landscape workspace click landscape group on the left the system displays all of the landscape groups in the system click the red x to the right of the landscape group name to delete it in the resulting dialog box, click ok working with landscapes about landscapes docid\ ohfv7pbfadpqn00kclhpnadding a landscape docid\ ohfv7pbfadpqn00kclhpnediting a landscape docid\ ohfv7pbfadpqn00kclhpndeleting a landscape docid\ ohfv7pbfadpqn00kclhpn about landscapes a landscape consists of a ivanti service manager configuration database and two ivanti service manager web servers for connecting to the ivanti service manager application server after you create a landscape group, you can start creating landscapes to add to it you can have a maximum of one of the following landscape types in a landscape group production staging uat development pilot adding a landscape log in to the operations console click the landscape tab the system displays the landscape workspace click landscape on the left the system displays all of the landscapes in the landscape group (optional) to view the landscapes for a different landscape group, select a different landscape group from the drop down list and click go the system displays all of the landscapes in the landscape group click add landscape the system displays the new landscape page see new landscape page docid\ ohfv7pbfadpqn00kclhpn new landscape page select a landscape type from the drop down list select the landscape group to which this landscape will be attached enter the name of the ivanti service manager configuration database server enter the name of the ivanti service manager configuration database click test connectivity to test the connection from the operations console to the ivanti service manager configuration database if you are using windows integrated security, check windows authentication if you check window authentication, the system hides the database user id , database user password , and confirm user password fields these fields are only displayed if you do not check window authentication, which means that you are using microsoft sql authentication if you did not check window authentication, enter values into the database user id , database user password , and confirm user password fields enter a tenant id pattern this is the format in which all tenants in this landscape will be named you can optionally use the variable as a placeholder for the tenant name the following are examples for the production instance of the tenant stg for the staging instance of the tenant uat for the uat instance of the tenant for example, if the value of the parameter is demo1, then for the production landscape, the tenant id is demo1 and the url is http //demo1/heat; for the staging landscape, the tenant id is demo1 stg and the url is http //demo1 stg/heat; and for the uat landscape, the tenant id is demo1 uat and the url is http //demo1 uat/heat enter a database name pattern this is the format in which all databases in this landscape will be named you can optionally use the variable as a placeholder for the database name the following are examples for the production instance of the tenant stg for the staging instance of the tenant uat for the uat instance of the tenant for example, if the value of the parameter is training, then the database name for the production landscape is training; the database name for the staging landscape is training stg; and the database name for the uat landscape is training uat enter the url for the ivanti service manager configuration service, which is the location of the ivanti service manager configuration database the value must be in the format http[s] // central configdb hostname /centralconfig/configserviceapi asmx click test to ensure that ivanti service manager can contact the url enter the url for the multi instance service this is the web service url for connecting to a tenant the value must be in the format http[s] // app server hostname /heat/services/multiinstancemanager asmx click test to ensure that ivanti service manager can contact the url enter the email domain string for your organization check allow all backup options to allow all backup options for tenant and tenant instances that are part of this landscape see backup types docid srybeqnhr2outxjfw8z for more information about database backup types click save editing a landscape log in to the operations console click the landscape tab the system displays the landscape workspace click landscape on the left the system displays all of the landscapes in the landscape group (optional) to view the landscapes for a different landscape group, select a different landscape group from the drop down list and click go the system displays all of the landscapes in the landscape group do one of the following click the underlined name of the landscape in the resulting dialog box, click edit click the pencil icon to the right of the landscape name edit the values click ok deleting a landscape log in to the operations console click the landscape tab the system displays the landscape workspace click landscape on the left the system displays all of the landscapes in the landscape group (optional) to view the landscapes for a different landscape group, select a different landscape group from the drop down list and click go the system displays all of the landscapes in the landscape group click the red x to the right of the landscape name in the resulting dialog box, click ok working with database servers about database servers docid\ ohfv7pbfadpqn00kclhpnadding a database server docid\ ohfv7pbfadpqn00kclhpnediting a database server docid\ ohfv7pbfadpqn00kclhpndeleting a database server docid\ ohfv7pbfadpqn00kclhpn about database servers each landscape must have one or more ivanti service manager database servers associated with it to host the tenant instance databases the ivanti service manager database server is controlled by the ivanti service manager configuration database you must specify the data and backup locations for the database server before you can add a tenant using the operations console ivanti service manager database servers either use windows integrated security or by microsoft sql server authentication, in which case you must enter a user name and password you define which authentication model to use when you initially install ivanti service manager using the system configuration wizard adding a database server to add a database server, do the following log in to the operations console click the landscape tab the system displays the landscape workspace click database server on the left the system displays all of the database servers in the landscape (optional) to view the database servers for a different landscape, select a different landscape from the drop down list and click go the system displays all of the database servers in the landscape click add database server the system displays the database server screen as shown in add a database server screen docid\ ohfv7pbfadpqn00kclhpn add a database server screen enter a name for the database server this is usually the host name, ip address, or machine name enter a database login id and password the database login id must have permission to back up any tenant or tenant instance database; must have permission to restore any tenant or tenant instance database; and must become the database owner of any new databases that are created on the tenant or tenant instance the database login id must have read and write access to the data location and backup locations click test connectivity to test the connectivity between the operations console and the ivanti service manager databases if you are using windows integrated security (as opposed to microsoft sql authentication), the database login id , login password , and confirm password fields are not shown these fields are only displayed if you are using microsoft sql authentication do not check active, clustered, or mirrored these are internal settings that should not be used enter a location for the database server data do not enter a unc path change the application pool identity so that it has read access to the data location enter the location of the transaction log do not enter a unc path change the application pool identity so that it has read access to the transaction log location enter a location for the backup data for the database server this is used for the automatic transfer of the database backup files from the source microsoft sql database server to the target microsoft sql database server if you have more than one database server, each database server must have its own backup data location, but it must be a shared location that is dedicated for ivanti service manager backups use a unc path if you are using a shared location do not use the microsoft sql server default backup location if you have more than one database server change the application pool identity so that it has read and write permissions on both the sharing and security tabs in the windows explorer properties dialog box for the shared backup location the identity (user) that the database server runs must have read and write permissions on both the sharing and security tabs in the windows explorer properties dialog box for the shared folder used for the database backup location of the given database server change the application pool identity to an account that has read and write permission to the backup data location if all of the landscapes share the same database instance, you can use one backup data location to test the backup and restore function, select a database from the drop down list click test backup & restore this may take some time the drop down list is only populated if you successfully tested the connection as shown in step 8 above select a small database, such as the ivanti service manager configuration database, to quickly test the user's permission to back up and restore, to ensure that the backup location is set with the correct permissions, and to ensure that the data location for creating the database is correct click save editing a database server log in to the operations console click the landscape tab the system displays the landscape workspace click database server on the left the system displays all of the database servers in the landscape (optional) to view the database servers for a different landscape, select a different landscape from the drop down list and click go the system displays all of the database servers in the landscape do one of the following click the underlined name of the database server in the resulting dialog box, click edit click the pencil icon to the right of the database server name edit the values click save deleting a database server you cannot delete a database server that is in use log in to the operations console click the landscape tab the system displays the landscape workspace click database server on the left the system displays all of the database servers in the landscape (optional) to view the database servers for a different landscape, select a different landscape from the drop down list and click go the system displays all of the database servers in the landscape click the red x to the right of the database server name in the resulting dialog box, click ok