Hi @MakotoHorioka ,
To begin with, let's understand why do we need Sub-prod instance :
Sub-production is any non-=production instance. Typically a ServiceNow customer will purchase a subscription and with that they are entitled to one or more sub-production instances. Production is where the subscriptions are actually used to support their organization. The sub-production instance(s) can be used for testing, development, training, etc. A key difference is that sub-production instances do not include the full Advanced High Availability (AHA) architecture that production instances include.
Now, to why do we need to connect the sub-prod instances , it's because we need to move the update sets between the instances ,
An update set is a group of configuration that can be moved from one instance to another instance.
By using the update sources, we can able to fetch the update set in our instance directly by specifying the URL of servicenow target instance and credentials of that URL in Update Source.
Since you already have the their passwords/username and have the authority to change them, you can create Remote Instances .
All your sub-prod instances can be configured as Remote instance to import update sets.
You need to configure sub-prod instance details from which you want to import update sets using OOB integration/automation. They call it Remote Instance.
Follow these steps :
1. Enter Update sources in the Filter Navigator :
2. Click on "Update Sources "
3. Hit "New"
4. fill all the fields mentioned below :
5. Save.
6. Click on "Test Connection"
You are all set with the connections for sub- prod instances.
Now once you are done with your update sets , you acn retrieve, preview and commit in other sub-prod then prod instances.
