Configuring the Deployment on the Neurons for ITSM Operations Console

configuring the neurons for itsm operations console docid 2qq9o6hkyaotbvwdkvv4ucreating the staging and uat instances of the tenants docid 2qq9o6hkyaotbvwdkvv4umaking configuration changes to tenants docid 2qq9o6hkyaotbvwdkvv4u perform these steps from the operations console, which you installed in the staging/uat environment this section only contains brief, high level instructions for complete information about using the operations console, including how to log in, see the operations console user guide for configuring the neurons for itsm operations console to log into the operations consoles, do the following in the start menu, click the down arrow to see the apps menu, and then click heat operations console enter your user name and password and then click login the default user name is admin and the default password is manage operations console log in screen use the operations console to update the values for the application database by doing the following a click the landscape tab b click database server on the left c click add database server d enter a database login id and password and set the data and backup locations see the example values in adding a database server docid 2qq9o6hkyaotbvwdkvv4u adding a database server e for the data and backup locations, change the application pool identity so that it has read access see changing the application pool identity docid 2qq9o6hkyaotbvwdkvv4u changing the application pool identity see the working with database servers section of the operations console user guide for for complete details about editing a database server delete the application databases on the staging and uat instances of the tenant, by doing the following a click the tenants tab b click expanded view to view all the details about the tenants c find the staging instance of the tenant and click deactivate d click deactivate at the confirmation prompt e for the staging instance of the tenant, click delete f check skip backup and click delete at the confirmation prompt g repeat steps c through f for the uat instance of the tenant you now have three instances of the configuration database and a production instance of the tenant see the editing a tenant section of the operations console user guide for for complete details about deleting tenants and tenant instances creating the staging and uat instances of the tenants to create the staging and uat instances of the tenant, based on the production instance, do the following log into the operations console click the tenants tab navigate to the production instance of the tenant and click manage migration create the staging instance of the tenant, by doing the following a in the migration dashboard, click push which is located inside the arrow going from the production instance of the tenant to the staging instance of the tenant see creating a staging instance of the tenant docid 2qq9o6hkyaotbvwdkvv4u creating a staging instance of the tenant the system displays the copy production to staging dialog box b in the target db option field, select from live mssql backup see copy production instance of the tenant to the staging instance of the tenant docid 2qq9o6hkyaotbvwdkvv4u copy production instance of the tenant to the staging instance of the tenant c click execute create the uat instance of the tenant a in the migration dashboard, click push which is located inside the arrow going from the production instance of the tenant to the uat instance of the tenant see creating a staging instance of the tenant docid 2qq9o6hkyaotbvwdkvv4u the system displays the copy production to uat dialog box b in the target db option field, select from live mssql backup see copy production instance of the tenant to the staging instance of the tenant docid 2qq9o6hkyaotbvwdkvv4u c click execute you can now customize and use the operations console to push those customizations to the other instances of the tenant making configuration changes to tenants log into the operations console click the tenants tab make configuration changes in the staging instance of the tenant push the configuration changes that you made in the staging instance of the tenant to the uat instance of the tenant by doing the following a click push which is located inside the arrow going from the staging instance of the tenant to the uat instance of the tenant see creating a staging instance of the tenant docid 2qq9o6hkyaotbvwdkvv4u the system displays the copy staging to uat dialog box b you can use simple mode by leaving advanced mode unchecked, or you can use advanced mode by checking advanced mode if you use advanced mode, select copy configuration in the operation field and check your options see copy production instance of the tenant to the staging instance of the tenant docid 2qq9o6hkyaotbvwdkvv4u c click execute verify that the configuration changes that you made to the staging instance of the tenant (in step 3) were successfully migrated to the uat instance of the tenant make additional configuration changes in the staging instance of the tenant as needed after you have finished making configuration changes and have verified them, push the configuration changes from the uat instance of the tenant to the production instance of the tenant