The system has the ability to launch the application in context via a URL. You are directed to the information for specific jobs or devices, based on the parameters of the URL. This is especially useful in integrations.
One example is where an external system receives an event or SNMP trap about a network device. Users in the external system can click a URL that launches into the Network Configuration Manager system directly to the device for detailed information.
Another example is where job warnings or failures are issued. A URL can launch you directly to the offending job for a detailed description of the problem.
The URL is constructed as follows:
where <server-ip> is the IP Address of the machine where the server is installed.
Check Section “List of allowed query strings” on page 219 for a list of allowed param_names. For example, a URL to launch to job number 10005 would be as follows:
Many parameters are available as query strings. In the case where multiple entities could be returned from the query, you can select the entity in which they are interested.
The URL query can also further restrict the scope of the launch by including a network parameter. It must be used in conjunction with one of the above parameters. For example, to launch to any device that contains an IP address of 192.168.1.1 in a network called MyNetwork, the URL would be as follows:
The contextual launch capability was specifically designed to give the integration developer a great deal of flexibility. It is intended to allow tighter integrations between disparate systems with less effort.