User guide

17
Although servers can be registered in the system manually, we recommend they are configured using the
Scan for New feature (see next section).
5. Select the server owner from the Owner dropdown.
6. Select the IP Address Type; either Server or Gateway. This will allow release management to recognize
the deployment agent based on its DNS Name and the IP Address that it communicates.
IP Address Type
There are two ways a deployment agent can indicate its uniqueness in a network.
Server – indicates that the IP Address is that of the Server within its local network. This is the actual
server’s IP address and it is usually considered internal to the network to which the server belongs.
Gateway – indicates that the IP Address is that of the Gateway behind which the Server resides. This is
commonly used when servers are behind firewalls or are using Network Address Translation (NAT) .
The IP Address Type is most used when dealing with “cloned” environments where the servers may be
exact images but appear to be different to the outside world.
Select the IP Address Type that uniquely identifies your server configurations within your deployment
agent network.
7. Select the Drop Location Access mechanism.
Drop Location Access
There are two mechanisms for a Deployment Agent to obtain files from the drop location.
The first one – Directly using UNC Path – is by accessing directly the drop location server via a UNC path.
The account running the deployment agent must be granted security access to the drop location. Using this
mechanism makes the file transfer very fast.
The second one – Through Release Management Server over HTTP – permits the deployment agent to be
on a separate domain than the server where the drop location is. It is the responsibility of the release
management server to get the files from the drop location (using a UNC path). The files are then transferred
to the deployment agent over HTTP. This means that the account running the ReleaseManagementAppPool
application pool used by the web services of the release management server needs to be granted security
access to the drop location. The file transfer rates will be slower in this scenario.
8. Go to the Supported Technology Types tab and select all technologies that are supported by the server.
9. Choose the Save and Close button in the Server form title bar. The new server will now appear in the list
of servers.
10. Repeat step 6 to 11 to associate more servers to the environment.
11. Choose the Save & Close button in the Environment form title bar to persist your changes. The new
environment will now appear in the list of environments.