Expecco RPC Interface/en - Versionsgeschichte

Cg am 10. November 2022 um 14:16 Uhr

2022-11-10T14:16:03Z

← Nächstältere Version		Version vom 10. November 2022, 14:16 Uhr
Zeile 1:		Zeile 1:
	== Introduction ==		== Introduction ==
	This document describes how expecco itself can be controlled by other programs, not how expecco can interact with the SUT. However, all of the interfaces described below can also be used by an expecco test suite to do so.		This document describes how expecco itself can be controlled by other programs, not how expecco can interact with the [[Glossary/en#SUT_.28System_Under_Test.29\|SUT]]. However, all of the interfaces described below can also be used by an expecco test suite to do so.

	Many of the operations of expecco can be remote-controlled via [[Glossary#RPC\|RPC]] interfaces.		Many of the operations of expecco can be remote-controlled via [[Glossary#RPC\|RPC]] interfaces.

Cg: /* Introduction */

2022-03-22T19:39:07Z

Introduction

← Nächstältere Version		Version vom 22. März 2022, 19:39 Uhr
Zeile 2:		Zeile 2:
	This document describes how expecco itself can be controlled by other programs, not how expecco can interact with the SUT. However, all of the interfaces described below can also be used by an expecco test suite to do so.		This document describes how expecco itself can be controlled by other programs, not how expecco can interact with the SUT. However, all of the interfaces described below can also be used by an expecco test suite to do so.

	Many of the operations of expecco can be remote-controlled via RPC interfaces.		Many of the operations of expecco can be remote-controlled via [[Glossary#RPC\|RPC]] interfaces.
	These interfaces allow for external programs to invoke functions of an expecco running in "slave-mode",		These interfaces allow for external programs to invoke functions of an expecco running in "slave-mode",
	thereby allowing for expecco to be integrated into an existing QM infrastructure.		thereby allowing for expecco to be integrated into an existing [[Glossary#QM\|QM]]infrastructure.

	Currently, interfaces are available for:		Currently, interfaces are available for:

Mawalch am 3. Januar 2018 um 13:14 Uhr

2018-01-03T13:14:39Z

← Nächstältere Version		Version vom 3. Januar 2018, 13:14 Uhr
Zeile 9:		Zeile 9:

	== XML-RPC ==		== XML-RPC ==
	XML-RPC is a lightweight ~~xml~~-based RPC mechanism, as documented in http://www.xmlrpc.com/spec.		XML-RPC is a lightweight XML-based RPC mechanism, as documented in http://www.xmlrpc.com/spec.
	XML-RPC uses HTTP as a transport mechanism.		XML-RPC uses HTTP as a transport mechanism.
	Implementations for XML-RPC are very lightweight and available for many programming languages and systems - in contrast to SOAP, which by many is no longer considered to be "simple".		Implementations for XML-RPC are very lightweight and available for many programming languages and systems - in contrast to SOAP, which by many is no longer considered to be "simple".
Zeile 81:		Zeile 81:

	== SOAP ==		== SOAP ==
	SOAP is a not so lightweight ~~xml~~-based RPC mechanism, which is well-documented and well-supported, especially in Java enterprise and SOA environments. Specs are found in http://www.w3.org/TR/soap. Operations are described by a standard notation (WSDL), which can be parsed and used for automatic generation of service call interfaces. See http://www.w3.org/TR/wsdl for details.		SOAP is a not so lightweight XML-based RPC mechanism, which is well-documented and well-supported, especially in Java enterprise and SOA environments. Specs are found in http://www.w3.org/TR/soap. Operations are described by a standard notation (WSDL), which can be parsed and used for automatic generation of service call interfaces. See http://www.w3.org/TR/wsdl for details.

	The SOAP interface is also used by ~~expeccoNET~~ to control the execution of its remote testHosts.		The SOAP interface is also used by expecco ALM to control the execution of its remote testHosts.

	== Telnet ==		== Telnet ==
Zeile 90:		Zeile 90:
	== HTTP ==		== HTTP ==
	It is also possible to talk to expecco directly via HTTP.		It is also possible to talk to expecco directly via HTTP.
	Thus, any ~~webBrowser~~ can be used to control an expecco slave.		Thus, any web browser can be used to control an expecco slave.


			----
	<hr>
	Back to [[Online_Documentation#Remote_Control_.28RPC.29_Interface_Reference \| Online Documentation]]		Back to [[Online_Documentation#Remote_Control_.28RPC.29_Interface_Reference \| Online Documentation]]

Sv: Die Seite wurde neu angelegt: „== Introduction == This document describes how expecco itself can be controlled by other programs, not how expecco can interact with the SUT. However, all of t…“

2015-12-08T17:22:17Z

Die Seite wurde neu angelegt: „== Introduction == This document describes how expecco itself can be controlled by other programs, not how expecco can interact with the SUT. However, all of t…“

Neue Seite

== Introduction ==
This document describes how expecco itself can be controlled by other programs, not how expecco can interact with the SUT. However, all of the interfaces described below can also be used by an expecco test suite to do so.

Many of the operations of expecco can be remote-controlled via RPC interfaces.
These interfaces allow for external programs to invoke functions of an expecco running in "slave-mode",
thereby allowing for expecco to be integrated into an existing QM infrastructure.

Currently, interfaces are available for:

== XML-RPC ==
XML-RPC is a lightweight xml-based RPC mechanism, as documented in http://www.xmlrpc.com/spec.
XML-RPC uses HTTP as a transport mechanism.
Implementations for XML-RPC are very lightweight and available for many programming languages and systems - in contrast to SOAP, which by many is no longer considered to be "simple".
The XML-RPC protocol is simple enough, to be even used by humans; for example, to invoke the '''system.versionInfo''' call as described below, send the following HTTP-POST-request to the service:

<CODE><PRE>
<?xml version="1.0"?>
<methodCall>
<methodName>system.versionInfo</methodName>
<params></params>
</methodCall>
</PRE></CODE>

or, to get the list of supported rpc-calls, use:

<CODE><PRE>
<?xml version="1.0"?>
<methodCall>
<methodName>system.listMethods</methodName>
<params></params>
</methodCall>
</PRE></CODE>
and get the response:
<CODE><PRE>
<?xml version="1.0"?>
<methodResponse>
<params>
<param>
<value>
<array>
<data>
<value>system.getCapabilities</value>
<value>system.listMethods</value>
<value>system.methodHelp</value>
...
</data>
</array>
</value>
</param>
</params>
</methodResponse>
</PRE></CODE>

==== Introspection ====
The XML-RPC implementation supports the introspection interface:

*'''struct''' ''system.getCapabilities''( ) returns a structure containing info about supported RPC-interfaces and protocols

*'''struct''' ''system.versionInfo''( ) returns a structure containing version info about the RPC-service itself

*'''array''' ''system.listMethods''() returns a vector of strings, comprising the names of supported RPC-entries.

*'''array''' ''system.methodSignature''( '''string''' ) returns a vector of strings, comprising the return-type and argument types names of the given RPC-entry.

*'''string''' ''system.methodHelp''( '''string''' ) returns an informative string, describing the functionality of the given RPC-entry.

use ''system.getCapabilities'' to get up-to-date information on the supported interfaces.

 

== JSON-RPC ==
JSON-RPC a lightweight JSON-based RPC mechanism, documented in http://json-rpc.org/wiki/specification
and http://groups.google.com/group/json-rpc/web/json-rpc-2-0. JSON is a very simple encoding, which is common among
JavaScript based browser applications. JSON can therefore be used to control a running expecco from an interactive web-page.

== SOAP ==
SOAP is a not so lightweight xml-based RPC mechanism, which is well-documented and well-supported, especially in Java enterprise and SOA environments. Specs are found in http://www.w3.org/TR/soap. Operations are described by a standard notation (WSDL), which can be parsed and used for automatic generation of service call interfaces. See http://www.w3.org/TR/wsdl for details.

The SOAP interface is also used by expeccoNET to control the execution of its remote testHosts.

== Telnet ==
The Telnet protocol is a very simple, line-oriented ascii-command interface, which can also easily be entered by a human operator. Its simplicity enables even batch-files or shell scripts to communicate with expecco slaves. The telnet protocol is specified in RFC854 (http://www.ietf.org/rfc/rfc854.txt). For more information, see [[Starting_expecco_via_Command_Line/en#Scripting Example|"Scripting Example"]] and [[Starting_expecco_via_Command_Line/en#Scripting API Overview|"Scripting API Overview"|]].

== HTTP ==
It is also possible to talk to expecco directly via HTTP.
Thus, any webBrowser can be used to control an expecco slave.

<hr>
Back to [[Online_Documentation#Remote_Control_.28RPC.29_Interface_Reference | Online Documentation]]