WSDLPlugin Reference/en - Versionsgeschichte

Cg: /* Step1: Import the WSDL */

2023-07-08T06:44:01Z

Step1: Import the WSDL

← Nächstältere Version		Version vom 8. Juli 2023, 06:44 Uhr
Zeile 20:		Zeile 20:
	* Enter the above URL ("https://www.w3schools.com/xml/tempconvert.asmx?WSDL") into the dialog.		* Enter the above URL ("https://www.w3schools.com/xml/tempconvert.asmx?WSDL") into the dialog.
	* Next, a dialog asks how those definitions should be imported.		* Next, a dialog asks how those definitions should be imported.
	:You can either import the definitions into the current project (i.e. as actions directly in the current project),		:You can either import the definitions into the current project (i.e. as actions directly in the current project), or alternatively into an imported sub-library.
	: or alternatively into an imported sub-library.
	* Click on "''Import''".		* Click on "''Import''".
	* Next, a dialog asks if additional actions for packing/unpacking the response containers should be generated.		* Next, a dialog asks if additional actions for packing/unpacking the response containers should be generated.

Sv am 17. April 2023 um 12:35 Uhr

2023-04-17T12:35:52Z

← Nächstältere Version		Version vom 17. April 2023, 12:35 Uhr
Zeile 67:		Zeile 67:
	Open a new project, and import the saved "TemperatureConvert.ets".		Open a new project, and import the saved "TemperatureConvert.ets".
	Then use the actions from "Service API" just like any other action.		Then use the actions from "Service API" just like any other action.

			= Authentication =
			If a web service requires authentication, user name and password values can be passed either by:
			* defining environment variables named "SOAP_USER" and "SOAP_PASSWORD", which are visible and present at the time the low-level SOAP action is executed.
			These variables can be created either locally inside the calling action's compound action, or inside the imported service library, or as globals in the suite's top environment. The type of these variable are String.
			* <span id="SOAP user and password pins">(only in 21.2 and later)</span> adding pins named "__user__" and "__password__" to the low-level operation,
			and providing these pins with user and password string values in the step.<br>Support for a user and password pins is new with version 21.2.

			Currently only HTTP Basic Authentication is supported.

	= SOAP Timeouts =		= SOAP Timeouts =
Zeile 74:		Zeile 83:
	The timeout can be changed either by:		The timeout can be changed either by:
	* defining an environment variable named "SOAP_TIMEOUT", which is visible and present at the time the low-level SOAP action is executed. This variable can be created either locally inside the calling action's compound action, or inside the imported service library, or as global in the suite's top environment. The type of the variable can be TimeDuration or Number. If numeric, it will be the number of seconds. If it has a value of nil, no timeout is effective, and the operation will wait forever (unless there is a timeout on the step in the diagram)		* defining an environment variable named "SOAP_TIMEOUT", which is visible and present at the time the low-level SOAP action is executed. This variable can be created either locally inside the calling action's compound action, or inside the imported service library, or as global in the suite's top environment. The type of the variable can be TimeDuration or Number. If numeric, it will be the number of seconds. If it has a value of nil, no timeout is effective, and the operation will wait forever (unless there is a timeout on the step in the diagram)
	* <span id="SOAP timeout pin">(only in 21.2)</span> adding pin named "__timeout__" to the low-level operation, and provide a timeDuration or number of seconds or nil to it. With nil, no timeout is effective and the action waits internally "forever". However, you may of course add a timeout to the step (in the diagram where the SOAP action is present).<br>Support for a timeout pin is new with version 21.2.		* <span id="SOAP timeout pin">(only in 21.2 and later)</span> adding pin named "__timeout__" to the low-level operation, and provide a timeDuration or number of seconds or nil to it. With nil, no timeout is effective and the action waits internally "forever". However, you may of course add a timeout to the step (in the diagram where the SOAP action is present).<br>Support for a timeout pin is new with version 21.2.

	By providing different SOAP_TIMEOUT values in the compound action which uses those SOAP actions, these times can be adjusted to the need of individual operations.		By providing different SOAP_TIMEOUT values in the compound action which uses those SOAP actions, these times can be adjusted to the need of individual operations.

Cg: /* Best Practice Timeout Handling */

2021-11-27T17:40:29Z

Best Practice Timeout Handling

← Nächstältere Version		Version vom 27. November 2021, 17:40 Uhr
Zeile 81:		Zeile 81:

	== Best Practice Timeout Handling ==		== Best Practice Timeout Handling ==
	If operations have a wide variation in timing, it is probably best to set the global timeout to nil (i.e. no timeout at the low level), and instead set individual timelimits at the steps which call those operations. Place those into separate variables (i.e. SOAP_TIME_FOR_OPERATION1, SOAP_TIME_FOR_OPERATION2, etc.) and freeze the timeLimits to those variables. Then it is easy to change individual times, and it is also easy to initialize those values automatically (eg. by reading them from a CSV attachment, or by adding an action which multiplies all values by a factor).		If operations have a wide variation in timing, it is probably best to set the global timeout to nil (i.e. no timeout at the low level), and instead set individual timelimits at the steps which call those operations.

			Place those into separate variables (i.e. SOAP_TIME_FOR_OPERATION1, SOAP_TIME_FOR_OPERATION2, etc.) and freeze the timeLimits to those variables. Then it is easy to change individual times, and it is also easy to initialize those values automatically (eg. by reading them from a CSV attachment, or by adding an action which multiplies all values by a factor).

	= SOAP Protocol Traces =		= SOAP Protocol Traces =

Cg: /* Step2: Test the Operations */

2021-11-27T17:37:53Z

Step2: Test the Operations

← Nächstältere Version		Version vom 27. November 2021, 17:37 Uhr
Zeile 55:		Zeile 55:
	Now select the generated "CelsusToFahrenheit" action's "Test/Demo" page,		Now select the generated "CelsusToFahrenheit" action's "Test/Demo" page,
	give the "Celsius_in" pin some value (say: "100") and test-run it.		give the "Celsius_in" pin some value (say: "100") and test-run it.
⚫	If all goes well, the execution should pass and there should be the value of "212" at the output pin. Notice, that the action takes roughly 0.5 seconds to execute (on a slow DSL-connected home network) - after all it is a remote call to a server somewhere in the world.

	[[Datei:SOAPrun1.png\|mini]]		[[Datei:SOAPrun1.png\|mini]]
		⚫	If all goes well, the execution should pass and there should be the value of "212" at the output pin. Notice, that the action takes roughly 0.5 seconds to execute (on a slow DSL-connected home network) - after all it is a remote call to a server somewhere in the world.

	=== Step3: Save the Library ===		=== Step3: Save the Library ===

Cg: /* Step2: Test the Operations */

2021-11-27T17:36:54Z

Step2: Test the Operations

← Nächstältere Version		Version vom 27. November 2021, 17:36 Uhr
Zeile 56:		Zeile 56:
	give the "Celsius_in" pin some value (say: "100") and test-run it.		give the "Celsius_in" pin some value (say: "100") and test-run it.
	If all goes well, the execution should pass and there should be the value of "212" at the output pin. Notice, that the action takes roughly 0.5 seconds to execute (on a slow DSL-connected home network) - after all it is a remote call to a server somewhere in the world.		If all goes well, the execution should pass and there should be the value of "212" at the output pin. Notice, that the action takes roughly 0.5 seconds to execute (on a slow DSL-connected home network) - after all it is a remote call to a server somewhere in the world.

			[[Datei:SOAPrun1.png\|mini]]

	=== Step3: Save the Library ===		=== Step3: Save the Library ===

Cg: /* Step1: Import the WSDL */

2021-11-27T17:31:07Z

Step1: Import the WSDL

← Nächstältere Version		Version vom 27. November 2021, 17:31 Uhr
Zeile 28:		Zeile 28:

	After the import, you'll find the following elements in your suite:		After the import, you'll find the following elements in your suite:
	[[Datei:~~SOAP temperatureService~~.png\|mini]]		[[Datei:SOAP_temperatureService.png\|mini]]
	* Service API		* Service API
	: contains action blocks to call the operations (in this case, the two convert operations).		: contains action blocks to call the operations (in this case, the two convert operations).

Cg: /* Step1: Import the WSDL */

2021-11-27T17:29:51Z

Step1: Import the WSDL

← Nächstältere Version		Version vom 27. November 2021, 17:29 Uhr
Zeile 28:		Zeile 28:

	After the import, you'll find the following elements in your suite:		After the import, you'll find the following elements in your suite:
			[[Datei:SOAP temperatureService.png\|mini]]

	* Service API		* Service API
	: contains action blocks to call the operations (in this case, the two convert operations).		: contains action blocks to call the operations (in this case, the two convert operations).

Cg: /* SOAP Protocol Traces */

2021-11-27T17:06:00Z

SOAP Protocol Traces

← Nächstältere Version		Version vom 27. November 2021, 17:06 Uhr
Zeile 84:		Zeile 84:
	= SOAP Protocol Traces =		= SOAP Protocol Traces =
	To see the in and out messages, go to "''Extras ''" - "''Settings ''" - "''Execution ''" - "''Tracing ''", and check the "''Show SOAP Requests on Transcript ''" toggle.		To see the in and out messages, go to "''Extras ''" - "''Settings ''" - "''Execution ''" - "''Tracing ''", and check the "''Show SOAP Requests on Transcript ''" toggle.

			Make sure that the Logger's threshold is also set to at least "Info". Otherwise, the SOAP log messages are filtered by the logger.

Cg: /* SOAP Timeouts */

2021-11-27T16:58:14Z

SOAP Timeouts

← Nächstältere Version		Version vom 27. November 2021, 16:58 Uhr
Zeile 73:		Zeile 73:
	The timeout can be changed either by:		The timeout can be changed either by:
	* defining an environment variable named "SOAP_TIMEOUT", which is visible and present at the time the low-level SOAP action is executed. This variable can be created either locally inside the calling action's compound action, or inside the imported service library, or as global in the suite's top environment. The type of the variable can be TimeDuration or Number. If numeric, it will be the number of seconds. If it has a value of nil, no timeout is effective, and the operation will wait forever (unless there is a timeout on the step in the diagram)		* defining an environment variable named "SOAP_TIMEOUT", which is visible and present at the time the low-level SOAP action is executed. This variable can be created either locally inside the calling action's compound action, or inside the imported service library, or as global in the suite's top environment. The type of the variable can be TimeDuration or Number. If numeric, it will be the number of seconds. If it has a value of nil, no timeout is effective, and the operation will wait forever (unless there is a timeout on the step in the diagram)
	* (only in 21.2) adding pin named "__timeout__" to the low-level operation, and provide a timeDuration or number of seconds or nil to it. With nil, no timeout is effective and the action waits internally "forever". However, you may of course add a timeout to the step (in the diagram where the SOAP action is present).<br>Support for a timeout pin is new with version 21.2.		* <span id="SOAP timeout pin">(only in 21.2)</span> adding pin named "__timeout__" to the low-level operation, and provide a timeDuration or number of seconds or nil to it. With nil, no timeout is effective and the action waits internally "forever". However, you may of course add a timeout to the step (in the diagram where the SOAP action is present).<br>Support for a timeout pin is new with version 21.2.

	By providing different SOAP_TIMEOUT values in the compound action which uses those SOAP actions, these times can be adjusted to the need of individual operations.		By providing different SOAP_TIMEOUT values in the compound action which uses those SOAP actions, these times can be adjusted to the need of individual operations.

Cg: /* SOAP Protocol Traces */

2021-11-27T09:31:13Z

SOAP Protocol Traces

← Nächstältere Version		Version vom 27. November 2021, 09:31 Uhr
Zeile 83:		Zeile 83:

	= SOAP Protocol Traces =		= SOAP Protocol Traces =
	To see the in and out messages, go to "''Extras''" - "''Settings''" - "''Execution''" - "''Tracing''", and check the "''Show SOAP Requests on Transcript''" toggle.		To see the in and out messages, go to "''Extras ''" - "''Settings ''" - "''Execution ''" - "''Tracing ''", and check the "''Show SOAP Requests on Transcript ''" toggle.