Abstract: Connectivity between remote networks is managed by a central engine that collects and stores network data such as network addresses, URLs, hostnames, and/or other information. The engine creates a tunnel proxy, as well as separate respective tunnels with the remote networks. Based upon network data, the engine references the tunnel proxy to create a logical link joining the respective tunnels. Data can then flow between the remote networks through the logical link. The logical link may exist for only a limited time, e.g., as determined by a timer. Certain embodiments may be particularly suited to empower a customer network to manage connectivity with the remote network of a support provider. The customer can initiate connectivity changes without the manual involvement of the support provider. The customer can also authorize the support provider to manage connectivity and initiate changes under prescribed conditions.

Abstract: Methods and systems are disclosed for providing third party connectivity to installed software at a customer site through a broker infrastructure. A uniform facility for powerful and secure third party access to customer software installations is provided. Multiple TCP-based session types including source code debug and database sessions are supported. A target backend and session type are selected by an authorized agent logged into the broker infrastructure. A communication session is established between environments of the agent's frontend tool and the backend. The agent can perform maintenance or troubleshooting on the backend using the full capabilities of the frontend tool. Data exchange between frontend and backend utilizes TCP connections within the communication session, and is mediated by a connectivity framework within the broker infrastructure. Customer control over access to target backends is supported.

Abstract: Methods and systems are disclosed for providing third party connectivity to installed software at a customer site through a broker infrastructure. A uniform facility for powerful and secure third party access to customer software installations is provided. Multiple TCP-based session types including source code debug and database sessions are supported. A target backend and session type are selected by an authorized agent logged into the broker infrastructure. A communication session is established between environments of the agent's frontend tool and the backend. The agent can perform maintenance or troubleshooting on the backend using the full capabilities of the frontend tool. Data exchange between frontend and backend utilizes TCP connections within the communication session, and is mediated by a connectivity framework within the broker infrastructure. Customer control over access to target backends is supported.