Active Console - Passing Arguments from Knowledge Base
Related to Copied
The Geneos Knowledge Base only supports passing parameters/arguments when using the HTTP/HTTPS protocol. Using the file:/// protocol or other local pathing methods prevents the passing of query strings (e.g., ?key1=aaa). To successfully pass arguments from the Gateway Setup Editor to an external resource, the article must be hosted on a web server and accessed via a standard web URL.
Problem Copied
When a user attempts to launch a Knowledge Base article using a local file path (e.g., file:///Z:/scripts/knowledge.vbs?key=123), the ActiveConsole fails to pass the specified arguments to the target application. From the user’s perspective, the file may open but without the necessary context, or the OS may return an “Invalid Path” error because it treats the query string as part of the literal filename. In the backend, the ActiveConsole does not parse URL parameters for non-HTTP schemes.
Possible cause(s) Copied
- Root Cause 1: The
file:///protocol is being used, which does not support the transmission of arguments via query strings. - Root Cause 2: Limitations within the ActiveConsole’s internal URL handler, which only enables parameter passing for HTTP/HTTPS requests.
- Root Cause 3: Security restrictions at the OS level that prevent local file URIs from executing scripts with external command-line arguments via a browser-style call.
Possible solution(s) Copied
-
Solution Root Cause 1: Migrate the Knowledge Base documentation or scripts to a central web server. By using
http://orhttps://, the ActiveConsole can properly append and transmit arguments to the destination.
-
Solution Root Cause 2: Ensure the URL configured in the Knowledge Base section of the Gateway Setup Editor starts with a web-based protocol. If local script execution with arguments is required, consider using “User Commands” instead of “Knowledge Base” entries, as User Commands are designed for local execution.
-
Solution Root Cause 3: Use a web wrapper or redirector. If the file must remain local, host a tiny local web service that accepts the HTTP request with arguments and subsequently triggers the local
.vbsor.batfile on the client machine.