Contents Now Platform Custom Business Applications Previous Topic Next Topic Define a remote instance Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Share Define a remote instance For each instance, define other instances in the hierarchy as remote instances. About this task For example, to set up remote instances for Sub-Dev 1: Procedure If IP address access control is enabled, log in to the remote instance and add Sub-Dev 1 as an exception. On Sub-Dev 1, navigate to Team Development > Remote Instances. Click New. Define the remote instance, such as Dev-Parent, by completing the form (see table). Click Submit. Repeat step 1 through step 5 for each instance in the hierarchy that this instance needs to push and pull with (for example, Sub-Dev 2 and Sub-Dev 3). Table 1. Remote instance form Field Description Name Enter a unique name describing the instance. Type Specify whether the remote instance is a development, test, or UAT instance. Active Specify whether the local instance communicates with the remote instance as a member of Team Development. Team Development operations such as comparing changes between instances or selecting a parent instance are only available for active remote instances. URL Specify the URL of the remote instance using the appropriate transfer protocol. Each remote instance record should have a unique URL. Creating duplicate records with the same URL can cause errors. Username Enter the user on the remote instance who authorizes Team Development operations on the instance. This user account must have an appropriate role on the remote instance. Password Enter the password of the authorizing user. Short description [Optional] Enter any other relevant information about the remote instance. Related TasksCreate an exclusion policyEnable a code reviewSelect the parent instanceSet up an instance hierarchyRelated ReferenceAccess rights for developers On this page Send Feedback Previous Topic Next Topic
Define a remote instance For each instance, define other instances in the hierarchy as remote instances. About this task For example, to set up remote instances for Sub-Dev 1: Procedure If IP address access control is enabled, log in to the remote instance and add Sub-Dev 1 as an exception. On Sub-Dev 1, navigate to Team Development > Remote Instances. Click New. Define the remote instance, such as Dev-Parent, by completing the form (see table). Click Submit. Repeat step 1 through step 5 for each instance in the hierarchy that this instance needs to push and pull with (for example, Sub-Dev 2 and Sub-Dev 3). Table 1. Remote instance form Field Description Name Enter a unique name describing the instance. Type Specify whether the remote instance is a development, test, or UAT instance. Active Specify whether the local instance communicates with the remote instance as a member of Team Development. Team Development operations such as comparing changes between instances or selecting a parent instance are only available for active remote instances. URL Specify the URL of the remote instance using the appropriate transfer protocol. Each remote instance record should have a unique URL. Creating duplicate records with the same URL can cause errors. Username Enter the user on the remote instance who authorizes Team Development operations on the instance. This user account must have an appropriate role on the remote instance. Password Enter the password of the authorizing user. Short description [Optional] Enter any other relevant information about the remote instance. Related TasksCreate an exclusion policyEnable a code reviewSelect the parent instanceSet up an instance hierarchyRelated ReferenceAccess rights for developers
Define a remote instance For each instance, define other instances in the hierarchy as remote instances. About this task For example, to set up remote instances for Sub-Dev 1: Procedure If IP address access control is enabled, log in to the remote instance and add Sub-Dev 1 as an exception. On Sub-Dev 1, navigate to Team Development > Remote Instances. Click New. Define the remote instance, such as Dev-Parent, by completing the form (see table). Click Submit. Repeat step 1 through step 5 for each instance in the hierarchy that this instance needs to push and pull with (for example, Sub-Dev 2 and Sub-Dev 3). Table 1. Remote instance form Field Description Name Enter a unique name describing the instance. Type Specify whether the remote instance is a development, test, or UAT instance. Active Specify whether the local instance communicates with the remote instance as a member of Team Development. Team Development operations such as comparing changes between instances or selecting a parent instance are only available for active remote instances. URL Specify the URL of the remote instance using the appropriate transfer protocol. Each remote instance record should have a unique URL. Creating duplicate records with the same URL can cause errors. Username Enter the user on the remote instance who authorizes Team Development operations on the instance. This user account must have an appropriate role on the remote instance. Password Enter the password of the authorizing user. Short description [Optional] Enter any other relevant information about the remote instance. Related TasksCreate an exclusion policyEnable a code reviewSelect the parent instanceSet up an instance hierarchyRelated ReferenceAccess rights for developers