Customizing Bootup Operations - AMX APWeb Instruction Manual

Customizing Bootup Operations

During bootup, APWeb discovers configuration data that is stored on the attached routing system
(does not apply to heritage systems; see page 13) and displays it. Several options are available for
customizing bootup operations from the APWeb Configuration page.
Important: Any time you perform a reboot from the APWeb site, the APWeb server reboots. The
reboot updates information between the AMX AutoPatch Routing System and the APWeb server.
The AMX AutoPatch system itself does not reboot.
To customize bootup operations:
1.
From any page in the site, click the Configuration link.
The APWeb Configuration page opens.
2.
Under Bootup Operations, select (or unselect) the options (see below) to determine which parts
(if any) of the configuration to retrieve during APWeb bootup.
3.
After all selections are made, click Apply and reboot when prompted.
Bootup Operations Options
APWeb Instruction Manual
XNNet Tunnel (not supported on all systems) – check this option to be able to open a
Tunneling Access Point (TAP) for AMX AutoPatch's proprietary XNNet configuration
protocol. With this service turned on, XNConnect configuration software can be used to
discover and configure the attached routing system over TCP/IP. When site security is turned
on, the Admin user name and password are required to log into this service. Be sure to change
the XNNet Tunnel Port number if you plan on using a different one than the default (3500).
BCS Tunnel – check this option to be able to open a Tunneling Access Point (TAP) for
entering BCS control commands. This is especially useful for third-party controllers, which
can control the attached routing system using IP connectivity.
Unlike all other access points in APWeb, the BCS tunnel is not authenticated, even if site
security is turned on.
We strongly recommend that this service be turned off when not in use. (Note that disabling this
option will also disable the Device Discovery UDP Beacon Service which allows an AMX
AutoPatch Duet control module to connect to APWeb.) Be sure to change the BCS Tunnel Port
number if you plan on using a different one than the default (3600).
Discover System Configuration:
sub-options for discovery are available. The sub-options are not dependent on each other;
any or all of them can be selected at any time. (For heritage systems, turn option off.)
The default setting for this option is on.
If the setting is off, APWeb will not make any retrieval attempts from the attached system
during a reboot; instead, it will display whatever was in memory the last time it was running.
Force VM Discovery: Check this option to force APWeb to query the attached system for
its virtual matrix (VM) definitions and to replace any existing VMs in memory.
The default setting for this option is on.
When this option is off, APWeb reuses the stored VM definitions upon bootup.
Discover Channel Names (not supported on all systems):
query the attached system for the channel names on all VMs. The custom channel names
will then be displayed in the XBar instead of the default names. This process can take a
noticeable amount of time, depending on the size of the system's configuration.
The default setting for this option is on.
Since channel names are not stored in memory, they are lost when APWeb is shut down.
Check this option if you want the custom names displayed in the XBar.
Initial APWeb Setup by Network Admin
This higher-level option must be selected before the three
Check this option for APWeb to
9