Abstract: A technique determines which configuration change(s) caused an application invocation failure of a computer application without the need for a knowledge database. To determine which configuration change is the most likely cause, the cause analysis program checks other computers that have experienced the same configuration changes. The cause analysis program checks and counts the application invocation results before and after each configuration change is done. If the same configuration changes are found in the other computers, the program checks whether each configuration change caused or cured the same problem in that computer. The program counts the similar cases for all of the computers. Subsequently, the program calculates the ratio of those instances involving a change from success to failure and the ratio of those instances involving a change from failure to success out of all instances for each configuration change.

Abstract: A technique determines which configuration change(s) caused an application invocation failure of a computer application without the need for a knowledge database. To determine which configuration change is the most likely cause, the cause analysis program checks other computers that have experienced the same configuration changes. The cause analysis program checks and counts the application invocation results before and after each configuration change is done. If the same configuration changes are found in the other computers, the program checks whether each configuration change caused or cured the same problem in that computer. The program counts the similar cases for all of the computers. Subsequently, the program calculates the ratio of those instances involving a change from success to failure and the ratio of those instances involving a change from failure to success out of all instances for each configuration change.

Abstract: A technique determines which configuration change(s) caused an application invocation failure of a computer application without the need for a knowledge database. To determine which configuration change is the most likely cause, the cause analysis program checks other computers that have experienced the same configuration changes. The cause analysis program checks and counts the application invocation results before and after each configuration change is done. If the same configuration changes are found in the other computers, the program checks whether each configuration change caused or cured the same problem in that computer. The program counts the similar cases for all of the computers. Subsequently, the program calculates the ratio of those instances involving a change from success to failure and the ratio of those instances involving a change from failure to success out of all instances for each configuration change.

Abstract: In a computer system that comprises multiple target computers and an analysis computer, one or more first target computers, in which a predetermined application has been installed and invoked, send a log comprising information of multiple configuration changes that have been made prior to invoking the predetermined application to the analysis computer, and the analysis computer receives the log and computes, for each type of configuration change and based on the log, an invocation failure rate which is a percentage at which the invocation of the predetermined application fails subsequent to the configuration change. Then, a second target computer receives, from the analysis computer, first information comprising an invocation failure rate for each type of configuration change related to the predetermined application, and based on the invocation failure rate, displays the type of configuration change that is the cause of the failure of the predetermined application invocation.

Abstract: A technique determines which configuration change(s) caused an application invocation failure of a computer application without the need for a knowledge database. To determine which configuration change is the most likely cause, the cause analysis program (121) checks other computers (102) that have experienced the same configuration changes. The cause analysis program checks and counts the application invocation results before and after each configuration change is done. If the same configuration changes are found in the other computers, the program checks whether each configuration change caused or cured the same problem in that computer. The program counts the similar cases for all of the computers. Subsequently, the program calculates the ratio of those instances involving a change from success to failure and the ratio of those instances involving a change from failure to success out of all instances for each configuration change.

Abstract: A technique determines which configuration change(s) caused an application invocation failure of a computer application without the need for a knowledge database. To determine which configuration change is the most likely cause, the cause analysis program (121) checks other computers (102) that have experienced the same configuration changes. The cause analysis program checks and counts the application invocation results before and after each configuration change is done. If the same configuration changes are found in the other computers, the program checks whether each configuration change caused or cured the same problem in that computer. The program counts the similar cases for all of the computers. Subsequently, the program calculates the ratio of those instances involving a change from success to failure and the ratio of those instances involving a change from failure to success out of all instances for each configuration change.

Abstract: A technique determines which configuration change(s) caused an application invocation failure of a computer application without the need for a knowledge database. To determine which configuration change is the most likely cause, the cause analysis program (121) checks other computers (102) that have experienced the same configuration changes. The cause analysis program checks and counts the application invocation results before and after each configuration change is done. If the same configuration changes are found in the other computers, the program checks whether each configuration change caused or cured the same problem in that computer. The program counts the similar cases for all of the computers. Subsequently, the program calculates the ratio of those instances involving a change from success to failure and the ratio of those instances involving a change from failure to success out of all instances for each configuration change.

Abstract: A method of delivering and playing content includes delivering, through first-group channels, an entirety of content at a content bit rate with a time difference between each delivery commencement, delivering, through one or more second-group channels, only a start portion of the content at two or more times the content bit rate, selecting, from the first-group channels and the one or more second-group channels, a channel through which the start portion of the content is received earliest after a view request, followed by receiving and playing the start portion, and selecting, after receiving the start portion through the selected channel that is one of the one or more second-group channels, one of the first-group channels through which the remainder of the content is received for a first time after a start of the reception of the start portion, followed by receiving and playing the remainder of the content.

Abstract: A management server requests a meter installed in the network to measure traffic flow rates of transmitted data for each transmission direction of a communication line connecting routers subjected to traffic management and for each identifier included in the transmitted data. The management server aggregates the measured flow rates to create acquired flow-rate data. Then, the management server finds an average value of the measured flow rates and computes a send-out rate to be used as a flow-rate policy by multiplying the average value by a weight according to the identifier for which the flow rates have been acquired. Finally, the management server requests each of the routers to set such a flow-rate policy therein. As requested, each of the routers controls a flow rate for each identifier in accordance with the flow-rate policy set therein.