The Amplify Dashboard is arranged in two sections, CONFIG and STATS. The CONFIG portion of the Amplify dashboard is configured and managed by INXPO. The STATS section collects and captures data from STUDIO webcasts.
Amplify – CONFIG
The top section of the Amplify Dashboard is automatically populated by the clients Amplify server via a request home call with the configuration data. The proceeding section Server ID, Description and DNS Name is then configured by INXPO. The Active button is enabled by default and is available to deactivate a server if needed for maintenance or to limit the access to the server.
The Command Center within the CONFIG portion of the Amplify server is broken down into three tabs ACTIONS, LOGS and REGISRTY.
| ACTIONS | Description & Results |
|---|---|
| Reset Orgins | Resets the status of the failed origin(s) server |
| Report Unhealthy | Report unhealthy will cause the instance to reload itself on the Amplify server |
| Invalidate Cached Files | Clear cached presentation files on the Amplify server |
| LOGS | Description & Results |
|---|---|
| Upload | Uploads the current log (IACLog.txt) file from the Amplify server |
| Reset | Will truncate the IACLog.txt |
| Copy to Clipboard | Copies the current log file by date to the clipboard for easier viewing |
| REGISTRY | Description & Results |
|---|---|
| Refresh Registry | Refreshes the captured registry settings from the Amplify server |
Tenants Served are the environments assigned and configured with the clients Public IP address with a specific address, address range or CIDR Mask. These are the only tenants that will connect to the Amplify Server.
Local IP addresses served are the clients internal IP range(s) for that site where the Amplify server is located. The IP addresses can be configured with a specific address, address range or CIDR Mask.
Amplify – STATS
The Stats tab contains four customized enabled graphs, Throughput, Exceptions, Offload and Users.
Throughput graph measures the amount of data being Served, Read and Cached by the Amplify server. The data is filtered by General VTS files, Streaming, and by an Aggregate amount.
The exceptions graph tracks the number of 404, 500 and 504 log errors along with long load times and failed origin errors. Descriptions of Amplify IAC log messages can be found here.
Common Errors
404 Not Found
Possible causes:
- The file that you are trying to access was moved or does not exist.
- The URL contains a typographical error.
500 Internal Server Error
This HTTP status code may occur for many server-side reasons. Possible causes:
- This problem may occur because the ISAPIModule module is missing from the modules list for the Web site. The ISAPIModule module is in the following location: drive:\Windows\System32\inetsrv\isapi.dll
- This problem may occur because a script mapping is not valid. Make sure that the script mapping points to the ISAPI.dll file that can process the request. To do this, follow these steps:
- Click Start, click Run, type inetmgr.exe, and then click OK.
- In IIS Manager, expand server name, expand Web sites, and then click the Web site that you want to modify.
- In Features view, double-click Handler Mappings.
- Make sure that the script mapping points to the correct ISAPI.dll file.
- This problem may occur because the handler mapping for the requested resource points to a InXpoAdaptiveCache.dll file that cannot process the request. Edit the handler mapping for the requested resource to point to the InXpoAdaptiveCache.dll file that can process the request. To do this, follow these steps:
- Click Start, click Run, type inetmgr.exe, and then click OK.
- In IIS Manager, expand server name, expand Web sites, and then click the Web site that you want to modify.
- In Features view, double-click Handler Mappings.
- Right-click the script mapping (InXpoAdaptiveCache.dll) that you want to edit, and then click Edit.
- In the Edit Script Map dialog box, type the appropriate executable file and location (C:\IAC\InXpoAdaptiveCache.dll) in the Executable box, and then click OK.
Offload graph tracks the cached files being pull from the Amplify server and Bandwidth is the amount of data in MBs being pulled from the server.
