Studio:Transport Configuration File - Revision history

Timd: Text replace - 'Category:Reference' to 'Category:Studio:Reference'

2009-08-21T15:56:11Z

Text replace - 'Category:Reference' to 'Category:Studio:Reference'

← Older revision		Revision as of 15:56, 21 August 2009
Line 42:		Line 42:
	Each of these sections contain property settings that are specific to a particular transport DLL. By default, two transports are provided for - settings for the '''Socket''' and '''Serial''' transports that are installed with STRIDE. If a custom transport is added, make sure that the appropriate transport property names and values are represented in a new section, with the section name matching the custom transport name. Refer to the [[Media:s2sTransport.pdf\|STRIDE Host Runtime Transport Specification]] document for more information on adding a custom transport DLL.		Each of these sections contain property settings that are specific to a particular transport DLL. By default, two transports are provided for - settings for the '''Socket''' and '''Serial''' transports that are installed with STRIDE. If a custom transport is added, make sure that the appropriate transport property names and values are represented in a new section, with the section name matching the custom transport name. Refer to the [[Media:s2sTransport.pdf\|STRIDE Host Runtime Transport Specification]] document for more information on adding a custom transport DLL.

	[[Category:Reference]]		[[Category:Studio:Reference]]
	[[Category:Studio:Configuration]]		[[Category:Studio:Configuration]]

Timd at 15:44, 21 August 2009

2009-08-21T15:44:23Z

← Older revision		Revision as of 15:44, 21 August 2009
Line 43:		Line 43:

	[[Category:Reference]]		[[Category:Reference]]
	[[Category:Configuration]]		[[Category:Studio:Configuration]]

Timd: Transport Configuration File moved to Studio:Transport Configuration File

2009-08-19T16:35:39Z

Transport Configuration File moved to Studio:Transport Configuration File

← Older revision	Revision as of 16:35, 19 August 2009
(No difference)

Timd: /* Prerequisites */

2009-04-06T17:37:17Z

Prerequisites

← Older revision		Revision as of 17:37, 6 April 2009
Line 3:		Line 3:
	=== Prerequisites ===		=== Prerequisites ===

	The Config::IniFiles package must be installed for perl scripts to read this formatted file. If using an ActiveState perl distribution, the command '<b>ppm install config-inifiles</b>' will ~~insure~~ that it is installed.		The Config::IniFiles package must be installed for perl scripts to read this formatted file. If using an ActiveState perl distribution, the command '<b>ppm install config-inifiles</b>' will ensure that it is installed.

	=== Sample configuration file ===		=== Sample configuration file ===

Timd: /* The '''Keep Alive''' section */

2009-04-01T21:14:10Z

The '''Keep Alive''' section

← Older revision		Revision as of 21:14, 1 April 2009
Line 37:		Line 37:
	* The '''Interval''' property sets the time interval in milliseconds between pings.		* The '''Interval''' property sets the time interval in milliseconds between pings.
	* The '''RetryCount''' property sets the allowable number of ping failures. Once this number is exceeded, the connection to the target will be automatically closed.		* The '''RetryCount''' property sets the allowable number of ping failures. Once this number is exceeded, the connection to the target will be automatically closed.
	* The '''Timeout'''property sets the ping timeout value in milliseconds. This controls the time that the Transport Server waits for a response to a ping message. If a response is not received within this time, it is considered a ping failure; once the number of ping failures specified in the Retry Count field is exceeded, the connection to the target is closed.		* The '''Timeout''' property sets the ping timeout value in milliseconds. This controls the time that the Transport Server waits for a response to a ping message. If a response is not received within this time, it is considered a ping failure; once the number of ping failures specified in the Retry Count field is exceeded, the connection to the target is closed.

	=== The '''Transport Properties''' section ===		=== The '''Transport Properties''' section ===

Stevel at 19:24, 20 March 2009

2009-03-20T19:24:43Z

← Older revision		Revision as of 19:24, 20 March 2009
Line 1:		Line 1:
	The Transport configuration file contains default settings for the STRIDE [[Transport_Server_Component\|Transport Server]], an out-of-process COM server that manages connections between host and target processes, and also provides loopback and diagnostic features. The configuration file is located under the STRIDE installation directory, in the ''bin''' folder, in the "transport.cfg" file. Users may edit this file to change configuration settings, but the file must not be moved or renamed.		The Transport configuration file contains default settings for the STRIDE [[Transport_Server_Component\|Transport Server]], an out-of-process COM server that manages connections between host and target processes, and also provides loopback and diagnostic features. The configuration file is located under the STRIDE installation directory, in the '''bin''' folder, in the "transport.cfg" file. Users may edit this file to change configuration settings, but the file must not be moved or renamed.

	=== Prerequisites ===		=== Prerequisites ===

Stevel at 01:22, 9 October 2008

2008-10-09T01:22:22Z

← Older revision		Revision as of 01:22, 9 October 2008
Line 40:		Line 40:

	=== The '''Transport Properties''' section ===		=== The '''Transport Properties''' section ===
	Each of these sections contain property settings that are specific to a particular transport DLL. By default, two transports are provided for - settings for the '''Socket''' and '''Serial''' transports that are installed with STRIDE. If a custom transport is added, make sure that the appropriate transport property names and values are represented in a new section, with the section name matching the custom transport name. Refer to the [~~http~~:~~//www.s2technologies.com/pdf/~~s2sTransport.pdf Host Runtime Transport Specification] document for more information on adding a custom transport DLL.		Each of these sections contain property settings that are specific to a particular transport DLL. By default, two transports are provided for - settings for the '''Socket''' and '''Serial''' transports that are installed with STRIDE. If a custom transport is added, make sure that the appropriate transport property names and values are represented in a new section, with the section name matching the custom transport name. Refer to the [[Media:s2sTransport.pdf\|STRIDE Host Runtime Transport Specification]] document for more information on adding a custom transport DLL.

	[[Category:Reference]]		[[Category:Reference]]
	[[Category:Configuration]]		[[Category:Configuration]]

Ivailop: /* Sample configuration file */

2008-10-02T15:56:51Z

Sample configuration file

← Older revision		Revision as of 15:56, 2 October 2008
Line 7:		Line 7:
	=== Sample configuration file ===		=== Sample configuration file ===
	<source lang="ini">		<source lang="ini">
	;		;
	; Configuration file for STRIDE Unit runner (TestUnitRun.pl)		; Configuration file for STRIDE Unit runner (TestUnitRun.pl)
	; (standard INI/CFG file format)		; (standard INI/CFG file format)
	;		;
	[General]		[General]
	ActiveTransport = Sockets (S2)		ActiveTransport = Sockets (S2)
	[Keep Alive]		[Keep Alive]
	Active = yes		Active = yes
	Interval = 3000		Interval = 3000
	RetryCount = 2		RetryCount = 2
	Timeout = 2000		Timeout = 2000
	[Sockets (S2)]		[Sockets (S2)]
	DeviceAddress = localhost		DeviceAddress = localhost
	DevicePort = 8000		DevicePort = 8000
	[Serial (S2)]		[Serial (S2)]
	SerialPort = COM2		SerialPort = COM2
	BaudRate = 57600		BaudRate = 57600
	DataBits = 8		DataBits = 8
	StopBits = 1		StopBits = 1
	Parity = none		Parity = none
	</source>		</source>

Ivailop: /* Sample configuration file */

2008-10-02T15:56:23Z

Sample configuration file

← Older revision		Revision as of 15:56, 2 October 2008
Line 6:		Line 6:

	=== Sample configuration file ===		=== Sample configuration file ===
			<source lang="ini">
	;		;
	; Configuration file for STRIDE Unit runner (TestUnitRun.pl)		; Configuration file for STRIDE Unit runner (TestUnitRun.pl)
Line 27:		Line 27:
	StopBits = 1		StopBits = 1
	Parity = none		Parity = none
			</source>

	=== The '''General''' section ===		=== The '''General''' section ===

Ivailop: /* The '''Transport Properties''' section */

2008-10-02T15:35:01Z

The '''Transport Properties''' section

← Older revision		Revision as of 15:35, 2 October 2008
Line 39:		Line 39:

	=== The '''Transport Properties''' section ===		=== The '''Transport Properties''' section ===
	Each of these sections contain property settings that are specific to a particular transport DLL. By default, two transports are provided for - settings for the '''Socket''' and '''Serial''' transports that are installed with STRIDE. If a custom transport is added, make sure that the appropriate transport property names and values are represented in a new section, with the section name matching the custom transport name. Refer to the [[http://www.s2technologies.com/pdf/s2sTransport.pdf Host Runtime Transport Specification]] document for more information on adding a custom transport DLL.		Each of these sections contain property settings that are specific to a particular transport DLL. By default, two transports are provided for - settings for the '''Socket''' and '''Serial''' transports that are installed with STRIDE. If a custom transport is added, make sure that the appropriate transport property names and values are represented in a new section, with the section name matching the custom transport name. Refer to the [http://www.s2technologies.com/pdf/s2sTransport.pdf Host Runtime Transport Specification] document for more information on adding a custom transport DLL.

	[[Category:Reference]]		[[Category:Reference]]
	[[Category:Configuration]]		[[Category:Configuration]]