InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Client Config

IP.com Disclosure Number: IPCOM000238207D
Publication Date: 2014-Aug-08
Document File: 3 page(s) / 42K

Publishing Venue

The IP.com Prior Art Database


Disclosed is a method for Client Config (CC), which simplifies the process of building server environments with multi-user applications. CC allows users to push a self-chosen computer platform to a server and provides an application to track, manage, and perform the various tasks that are usually performed by developers, server administrators, and integration specialists.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 38% of the total text.

Page 01 of 3

Client Config

Building server environments with multi-user applications is complicated, time consuming, and expensive.

The novel contribution is a method for Client Config (CC). CC reduces the problem of developing, deploying, and integrating (i.e. configuring) application components by providing an application to track, manage, and perform the various tasks that are usually performed by developers, server administrators, and integration specialists. The 'client' (aka the user of CC) is provided with an interface that allows the user to compile and manage a simple browser application (or a complicated, enterprise class, multifaceted information system) from a very high level. Client Config merges high-level collaboration/document management systems with low-level system scripting interfaces.

On the simplest level, Client Config allows users to push a self-chosen computer platform (i.e. custom application and its environment) to a server. The user decides which forms and functionality to include in the application. Users are not bound by

what the designers of an existing application have deployed. With Client Config, the logic of an application does not necessarily have to exist on the server. The Hypertext Markup Language (HTML) files (and other types of files) with which the'users' interact are not generated by a server process but were pushed by the client. The users of CC no longer work in isolation with a collaboration platform. With the novel method, users can interact with an org that does not have access to the collaboration platform.

One of the core components of Client Config (CC) is a method to merge a development/collaboration platform with a Secure Shell (SSH) client Application Programming Interface (API). A development/collaboration platform allows an organization to work together on custom forms and views. An example of a development/collaboration platform is one in which an org can develop custom forms and notifications to be used to build online processes (e.g., a ticketing system). An SSH client API is a set of methods that a programmer can use to log in to and send commands to a Linux */UNIX** server and then process the response. This is needed to push/pull information to the customer's environment.

For the sake of this submission, the example development/collaboration platform is email software and the SSH API is Java*** 2 Platform SSH (J2SSH). Both components are installed on a client workstation, and the environment is pushed/pulled.

Client Config Mechanics:

1. Publishing (Push). Browser applications and content created in the collaboration platform can be pushed to the customer 's environment. A vendor content creator edits and saves a document (e.g., a contact list). The content is automatically


Page 02 of 3

pushed to the customer's Hypertext Transfer Protocol (HTTP) server in the background. This task takes place on a vendor

workstation. Only a vendor employee having credentials to log into the HTTP se...