Network requirements
Generally speaking, AssetTrack is very straightforward from a networking standpoint. It uses HTTP/S for almost all communications and handles typical enterprise scenarios like proxy servers, firewalls, and DMZs.
Servers
Network configuration for the core AssetTrack system
AssetTrack Server is a fairly standard web application running on a Microsoft stack (ASP.NET, IIS, SQL Server, Windows Server). There are two servers, the IIS server and the SQL Server. The servers can be on different machines or be running on the same machine (as described in server requirements), but from a networking standpoint, the web application just needs to query the SQL Server.
On this page:
Network configuration for CA integrations
The following network schematic illustrates how AssetTrack communicates with the network in a scenario where it's integrated with CA APM/Service Desk/Asset Manager.
Network configuration for file integrations and HP integrations
AssetTrack supports HP Asset Center/Asset Manager versions 4.x and 5.x. The following network schematic illustrates how AssetTrack communicates with the network in a scenario where it's integrated with HP Asset Manager.
Mobile devices
Mobile devices that run the AssetTrack Mobile app need to communicate with the AssetTrack Server using HTTP/S. There are two ways for a Windows Mobile device to get network connectivity: Wireless or via USB.
Most network-related problems happen here
One of the most common support incidents that AMI receives is a mobile operator indicating "My mobile device won't connect to AssetTrack Server." The usual suspects are proxy servers, firewalls, bad SSL certificates, unreliable VPN connections, and general slow connectivity. It pays to ensure that mobile devices have robust connectivity by testing device connections as early as possible.
Windows Mobile devices connecting via USB connection to a host workstation
The most common way for AssetTrack Mobile devices to connect to the AssetTrack Server is by connecting to a workstation computer via USB. Mobile devices usually come with a cradle that doubles as a charger and a USB connection. When a Windows Mobile or Windows CE device connects to a Windows workstation via USB, its connection to the workstation is managed by a Microsoft component called Windows Mobile Device Center (WMDC). WMDB must be installed on the workstation computer in order for the mobile device to communicate to it and through it.
Mobile devices connecting wirelessly
Unlike consumer mobile devices where one wouldn't even question their WiFi/cellular capability, the ruggedized devices that run AssetTrack Mobile may or may not come with wireless radios. Wireless-capable mobile devices can connect directly to AssetTrack Server if the network configuration permits - they do not need a workstation.
AssetTrack Management Console workstations and browser access
AssetTrack Management Console desktop application
AssetTrack application administrators, asset managers, and sys admins often need to customize AssetTrack for their business needs and to review the data being collected. This requires that they run AssetTrack Console, a Windows desktop application. Although AssetTrack Console is a desktop application, it uses Microsoft ClickOnce technology to deploy itself from the AssetTrack Server over HTTP/S onto the client workstation. This means that sys admins and end users never need to worry about installing software on a workstation in the traditional sense. AssetTrack Console is signed with an Authenticode certificate, so deployment and installation typically do not cause permissions or antivirus issues on the client workstation.
Proxy servers may interfere with ClickOnce
Although AssetTrack Console (including its ClickOnce deployment) use HTTP/S exclusively, some proxy servers and firewalls can interfere with communications. One common reason for this is that the ClickOnce deployment sends an XML file with a .manifest extension which is sometimes unrecognized/unauthorized by firewall configuration. The simplest way to validate network configuration here is to try to launch and use AssetTrack Console.
Browser access
AssetTrack Server exposes a web application that administrators and data collectors may need to use. This requires standard web browser HTTP/S access.