1.5

3 Respond to the wizard prompts with information specific to your deployment.
Option Action
Respond to the IPv6 prompt.
Type y if you have an IPv6 network. If you do not have an IPv6 network,
accept the default response of n.
Respond to the DHCPv4 prompt.
NOTE The recommended practice is to use a static IP address.
If you have a static IP address, type n. Continue responding to the
subprompts related to a static IP address.
If you have a DHCPv4 address, accept the default response y and continue
responding to the subprompts related to DHCP and a proxy server.
If you respond with n, continue responding to the subprompts related to a
static IP address, including subprompts about IPv4 address, netmask,
gateway, DNS servers, and proxy server.
Respond to the hostname prompt.
Type a unique hostname with at least three parts, a.b.c.
IMPORTANT Be aware that the name you enter, such as
Temp.MyDomain.com, is also used for initial access to the Operator Web
interface. For example: http://Temp.MyDomain.com. The first part of the
hostname, "Temp" in this example, is later replaced with the first
organization you create in the Operator Web interface. If you name the first
organization Org1, http://Org1.MyDomain.com can be used to reach
Application Manger in the future. The URL http://Temp.MyDomain.com
continues to provide access to Application Manager, too. To avoid having
two URLs that access the same interface, the best practice is to enter a
hostname where the first part of the name, such as Org1, matches the first
organization name that you plan to create. This practice allows one URL,
http://Org1.MyDomain.com, to continuously provide access to Application
Manager.
When you are finished configuring the network settings, the main screen of the Application Manager
virtual appliance interface appears.
4 If necessary, configure a Network Time Protocol server.
By default, the Application Manager Appliance points to specific external NTP servers, as listed in
the /etc/ntp.conf file. However, networking or DNS issues might prevent the virtual appliance from
reaching the external NTP servers. Also, you might want to use NTP servers other than the default settings.
When you properly configure the Application Manager deployment, the time for all systems is maintained
within a range of one minute.
CAUTION Failure to follow the NTP recommendations can prevent user access to the Application Manager
Web interface since both the SAML and Kerberos protocols rely on an accurate system clock. The protocols
used between Application Manager and the Connector and between the Connector and Active Directory
require that the time synchronization of these systems falls within a narrow range.
a Select Login and log in to the Linux operating system with root credentials.
b Using Linux commands configure Application Manager's time settings.
See Timekeeping best practices for Linux guests (KB 1006427) for information about time settings for
SLES 11. Consult the section on NTP recommendations.
c Exit the command line to return to the main page of the Application Manager virtual appliance
interface.
5 Confirm the Network Time Protocol configuration.
You should check this screen in the following situations:
n
When you first install the Application Manager Appliance.
n
Any time in the future when you modify the networking environment that can affect the ability to
contact the NTP server or when you change the NTP configuration.
Chapter 5 Installing Application Manager
VMware, Inc. 29