2.1 Instance Configuration Flashcards
A baseline implementation
is a set of installed applications on a ServiceNow instance, before any configuration or customization has been done.
A ServiceNow instance
is a copy of a ServiceNow environment that is specific to a customer.
There are Prod and Non-prod environments:
PRODUCTION: * Prod - where employees do their work and support their organizations
NON-PRODUCTION: * Development – where personas such as admins and implementers configure and build applications
* Test – where personas such as implementers test their changes before moving into production
=> independent, changeable, highly configurable
=> each instance has applications
Personal Developer Instance (PDI)
is an independent instance where developers and others may install, configure, develop, and learn.
A load-balanced instance
is located (hosted) in one of the ServiceNow Data Centers around the world, or for a very, very small percent age of our customers, an instance can be implemented onsite at the customer’s location. Each ServiceNow instance has a unique URL that uses a format similar to https://<instance>. service-now.com</instance>
ServiceNow utilizes an advanced, multi-instance, single-tenant architecture as the default offering for customers
instance features an individually isolated database containing data, applications, and customizations.
Each customer organization receives a minimum of two instances of ServiceNow:
production and non-product ion (sub -production). They have the ability to obtain additional non-production instances to be used for User Acceptance Testing (UAT), Review , Development , or Quality Assurance (QA).
single-tenant
not shared with other ServiceNow customers
Each instance has customer data that can be exchanged between instances
it is easy to migrate data from Dev to QA to test to stage to production
Upgrades are made on individual instances
Upgrade a non-production instance to complete testing before upgrading production
Configuration of a ServiceNow instance.
This primarily consists of things that can be done without code.
Examples:
* Update list of categories on a form
* Add baseline fields to form
* Configure list views
* Create a service catalog and catalog items
* Extend a table for a new hardware class
Customization of a ServiceNow instance.
is done when a customer requires additional functionality that does not exist in the platform, and they want to add features.
Examples:
* Enhance a portal widget to display lists with complex access controls
* Add a table for special billing requirements
Update sets
If you are making changes to an instance, these changes must be packaged to be moved into the production environments. Update sets allow you to do this.
NOTE: Update sets will be covered in more detail later in Module 7: Package Enhancement s for Testing.
The ServiceNow Platform offers many ways in which you can configure and augment your instance.
For example:
* Reflect a company image or brand
* Label instance tabs to easily identify your instance
* Enable system properties
* Install applications and plugins
obr str 60
Application scopes
Applications are installed in application scopes.
Application scoping protect s applications by identifying and restricting access to application files and data. Administrators can specify what parts of an application are accessible to other applications.