1. A limited user interface (UI) device, comprising:
a network interface; and
a processing device coupled to the network interface and storing instructions that, when executed, cause the limited UI device to:
enter a network setup mode to enable a secure wireless connection with a full-feature device;
establish the secure wireless connection with the full-feature device, wherein establishing the secure wireless connection includes the full-feature device using an encryption key to communicate with the first limited UI device and the limited UI device using the encryption key to authenticate the full-feature device;
receive, from the wirelessly-connected full-feature device, network setup information to enable the limited UI device to establish a wireless connection to a network access point; and
establish the wireless connection to the network access point using the received network setup information.
2. The limited user interface (UI) device of claim 1, wherein the encryption key is scanned or read by the full-feature device from the limited UI device to establish the secure wireless connection with the limited UI device.
3. The limited user interface (UI) device of claim 1, lacks one or both of an input interface and a display interface.
4. The limited user interface (UI) device of claim 1, wherein entering the network setup mode includes the limited UI device broadcasting a network identifier for the limited UI device.
5. The limited user interface (UI) device of claim 1, wherein the limited UI device enters the network setup mode in response to a power up of the limited UI device, determining that the limited UI device is not connected to a network, or a near field communication with the full-feature device.
6. The limited user interface (UI) device of claim 1, wherein the network setup information includes an identifier for the network access point and a security key for the network access point.
7. The limited user interface (UI) device of claim 1, wherein the network setup information includes a network address for the full-feature device, the full-feature device established a wireless connection to the network access point, and the instructions further cause the limited UI device to:
transmit an indication of successfully establishing the wireless connection to the network access point to the full-feature device over a network connection provided by the network access point and using the received network address for the full-feature device.
8. A computer-implemented method, comprising:
entering a network setup mode within a limited user interface (UI) device to enable a secure wireless connection with a full-feature device;
establishing the secure wireless connection with the full-feature device, wherein establishing the secure wireless connection includes the full-feature device using an encryption key to communicate with the first limited UI device and the limited UI device using the encryption key to authenticate the full-feature device;
receiving, from the wirelessly-connected full-feature device, network setup information to enable the limited UI device to establish a wireless connection to a network access point; and
establishing, by the limited UI device, the wireless connection to the network access point using the received network setup information.
9. The computer-implemented method of claim 8, wherein the encryption key is scanned or read by the full-feature device from the limited UI device to establish the secure wireless connection with the limited UI device.
10. The computer-implemented method of claim 8, wherein the limited UI device lacks one or both of an input interface and a display interface.
11. The computer-implemented method of claim 8, wherein entering the network setup mode includes the limited UI device broadcasting a network identifier for the limited UI device.
12. The computer-implemented method of claim 8, wherein the limited UI device enters the network setup mode in response to a power up of the limited UI device, determining that the limited UI device is not connected to a network, or a near field communication with the full-feature device.
13. The computer-implemented method of claim 8, wherein the network setup information includes an identifier for the network access point and a security key for the network access point.
14. The computer-implemented method of claim 8, wherein the network setup information includes a network address for the full-feature device and the full-feature device established a wireless connection to the network access point, the method further comprising:
transmitting, by the limited UI device, an indication of successfully establishing the wireless connection to the network access point to the full-feature device over a network connection provided by the network access point and using the received network address for the full-feature device.
15-21. (canceled)
22. A non-transitory computer-readable medium storing instructions, which when executed by a processing device, cause the processing device to perform a method comprising:
receiving, by a full-feature device, user input including network setup information to establish a wireless connection with a network access point;
receiving, by the full-feature device, input to establish a first secure wireless connection with a first limited user interface (UI) device;
establishing, by the full-feature device, the first secure wireless connection with the first limited UI device in response to the received user input to establish the connection, wherein establishing the first secure wireless connection includes the full-feature device using a first encryption key to communicate with the first limited UI device and the limited UI device using the first encryption key to authenticate the full-feature device; and
transmitting, by the full-feature device to the first limited UI device, the received network setup information to enable the first limited UI device to establish the wireless connection with the network access point.
23. The non-transitory computer-readable medium of claim 22, the method further comprising:
establishing, by the full-feature device, a wireless connection with the network access point using the received network setup information prior to transmitting the network setup information to the first limited UI device to verify that the received network setup information is correct.
24. The non-transitory computer-readable medium of claim 22, wherein receiving input to establish the first secure wireless connection includes the full-feature device scanning or reading an access point identifier for the first limited UI device or the first encryption key from the first limited UI device.
25. The non-transitory computer-readable medium of claim 24, wherein the full-feature device scans a barcode or quick response (QR) code on the first limited UI device to obtain the access point identifier for the first limited UI device or the first encryption key.
26. The non-transitory computer-readable medium of claim 24, wherein the full-feature device reads a radio frequency identification (RFID) tag or near field communication (NFC) tag within the first limited UI device to obtain the access point identifier for the first limited UI device or the first encryption key.
27. The non-transitory computer-readable medium of claim 22, the method further comprising:
receiving, by the full-feature device, input to establish a second secure wireless connection with a second limited user interface (UI) device;
establishing, by the full-feature device, the second secure wireless connection with the second limited UI device in response to the received user input to establish the second secure wireless connection, wherein establishing the second secure wireless connection includes the full-feature device using a second encryption key to communicate with the second limited UI device and the second limited UI device using the second encryption key to authenticate the full-feature device; and
transmitting, by the full-feature device to the second limited UI device, the received network setup information to enable the second limited UI device to establish a wireless connection with the network access point.
28. The non-transitory computer-readable medium of claim 27, the method further comprising:
transmitting, by the full-feature device to each of the first limited UI device and the second limited UI device, a shared network identifier and shared encryption key to enable the full-feature device to establish secure wireless connections with each of the first limited UI device and the second limited UI device using the shared network identifier and shared encryption key.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A system for acquiring execution information of a process executed in a computer, comprising:
a client part for issuing an execution request for a process; and
a server part including an application execution part for executing a process according to an execution request from the client part and an execution information acquirement control part for controlling acquirement of execution information,
wherein the client part receives and stores a request to start acquiring execution information,
wherein the client part transmits a request to acquire execution information to the server part together with an execution request based on the stored request to start acquiring execution information upon receiving the execution request for the application execution part after receiving the request to start acquiring execution information,
wherein the application execution part executes a process based on the execution request, and
wherein the execution information acquirement control part stores execution information of the process executed by the application execution part in a storage device based on the request to acquire execution information.
2. The system according to claim 1,
wherein the client part receives and stores a request to stop acquiring execution information,
wherein the client part transmits information indicating no need to acquire execution information to the server part together with an execution request based on the request to stop acquiring execution information upon receiving each execution request for the application execution part after receiving the request to stop acquiring execution information,
wherein the application execution part executes a process based on the execution request, and
wherein the execution information acquirement control part performs control not to store execution information of the process executed by the application execution part in the storage device based on the information indicating no need to acquire execution information.
3. The system according to claim 1,
wherein the client part stores an ID identifying the request to start acquiring execution information upon receiving the request to start acquiring execution information, and
wherein the client part transmits a request to acquire execution information and the ID identifying the request to start acquiring to the server part together with an execution request upon receiving each execution request for the application execution part after receiving the request to start acquiring execution information.
4. The system according to claim 1,
wherein the server part includes a plurality of application execution parts for executing different processes, and
wherein the client part displays an interface for designating whether or not to acquire execution information for each of the plurality of application execution parts.
5. The system according to claim 1,
wherein the server part includes a plurality of application execution parts for executing different processes,
wherein a request to start acquiring execution information received by the client part includes identification information of an application execution part, and
wherein the execution information acquirement control part stores, based on identification information of an application execution part included in a request to acquire execution information received from the client part, execution information of the application execution part indicated by the identification information in the storage device.
6. The system according to claim 1,
wherein the execution information acquirement control part attaches an ID identifying an execution request for the application execution part received from the client part and stores only execution information of the application execution part related to the execution request identified by the ID in the storage device.
7. The system according to claim 1,
wherein the server part further includes a display control part for displaying the execution information stored in the storage device by the execution information acquirement control part on a display, and
wherein the display control part displays the execution information of the process executed by the application execution part on the display upon receiving a request to display the execution information stored in the storage device.
8. A recording medium storing program codes for causing a computer system to perform processes, the computer system including a client part for issuing an execution request for a process and a server part including an application execution part for executing a process according to an execution request from the client and an execution information acquirement control part for controlling acquirement of execution information, the program codes causing:
the client part to receive and store a request to start acquiring execution information;
the client part to transmit a request to acquire execution information to the server part together with an execution request based on the stored request to start acquiring execution information upon receiving the execution request for the application execution part after receiving the request to start acquiring execution information;
the application execution part to execute a process based on the execution request; and
the execution information acquirement control part to store execution information of the process executed by the application execution part in a storage device based on the request to acquire execution information.
9. The recording medium according to claim 8,
wherein the program codes causes the client part to receives a request to stop acquiring execution information,
wherein the program codes causes the client part to store the request to stop acquiring execution information,
wherein the program codes causes the client part to transmit information indicating no need to acquire execution information to the server part together with an execution request based on the request to stop acquiring execution information upon receiving each execution request for the application execution part after receiving the request to stop acquiring execution information,
wherein the program codes causes the application execution part to execute a process based on the execution request, and
wherein the program codes causes the execution information acquirement control part to perform control not to store execution information of the process executed by the application execution part in the storage device based on the information indicating no need to acquire execution information.
10. The recording medium according to claim 8,
wherein the program codes causes the client part to store an ID identifying the request to start acquiring execution information upon receiving the request to start acquiring execution information, and
wherein the program codes causes the client part to transmit a request to acquire execution information and the ID identifying the request to start acquiring to the server part together with an execution request upon receiving each execution request for the application execution part after receiving the request to start acquiring execution information.
11. The recording medium according to claim 8,
wherein the server part includes a plurality of application execution parts for executing different processes, and
wherein the program codes causes the client part to display an interface for designating whether or not to acquire execution information for each of the plurality of application execution parts on the computer system.
12. The recording medium according to claim 8,
wherein the server part includes a plurality of application execution parts for executing different processes,
wherein a request to start acquiring execution information received by the client part includes identification information of an application execution part, and
wherein the program codes causes the execution information acquirement control part to store, based on identification information of an application execution part included in a request to acquire execution information received from the client part, execution information of the application execution part indicated by the identification information in the storage device.
13. The recording medium according to claim 8,
wherein the program codes causes the execution information acquirement control part to attach an ID identifying an execution request for the application execution part received from the client part and store only execution information of the application execution part related to the execution request identified by the ID in the storage device.
14. The recording medium according to claim 8,
wherein the server part further includes a display control part for displaying the execution information stored in the storage device by the execution information acquirement control part on a display, and
wherein the program codes causes the display control part to display the execution information of the process executed by the application execution part on the display upon receiving a request to display the execution information stored in the storage device.
15. A maintenance support system for supporting maintenance by visualizing history information of a target web system, comprising:
a history information tracking key extracting part; and
a history information relationship display data acquiring part for extracting information on all call-related objects from a history of a program execution environment based on the history information tracking key.
16. The maintenance support system according to claim 15, further comprising:
request information extracted from a history of request information based on the history information tracking key; and
a history information relationship display part for displaying information on all the call-related objects extracted from the history of the program execution environment based on the history information tracking key.
17. The maintenance support system according to claim 15,
wherein the history information relationship display data acquiring part extracts information on accesses to a database from a history of a database connection API set for object-oriented language based on the history information tracking key.
18. The maintenance support system according to claim 15, further comprising a history information relationship display part for displaying, based on the history information tracking key, information relating to clientsystem operations and extracted from a history of the clientsystem operations, information relating to all call-related objects starting from a specific object and extracted from the history of the program execution environment, and information relating to accesses to a database and extracted from a history of a database connection API set for object-oriented language.