Execute POST

Operation Name

Execute POST

Function Overview

Executes the request with POST method of HTTP.

Data Model

Data model of this component is XML type.

For details on the in-outputting schema, please refer to "Schema".

Properties

For information about using variables, refer to "Variables".

Basic Settings

Item name	Required/Optional	Use of Variables	Description	Remarks
Name	Required	Not available	Enter the name to show on the script canvas.
Input data	Optional	Not available	Select the component on the script canvas.	If you specify [File] in [Input source], you do not need to specify [Input data], and it will be ignored if you specify.

Required Settings

Item name	Required/Optional	Use of Variables	Description	Remarks
Destination	Required	Not available	Select a global resource. For how to set a global resource, please refer to "Global resource property"." [Add]: Adds a new global resource. [Edit list]: Enables to edit the global resource settings in the "Edit resource list" screen.
Path	Optional	Available	Specify the relative path from the URL entered in [URL] of [Destination].	URL Encoding is applied with the encode selected or entered in [Encoding].
Encoding	Optional	Available	Select or enter the encodes to use in URL Encoding. Specify the encodes supported by Java SE Runtime Environment 8 when inputting. For details, please refer to "Supported Encodings"(http://docs.oracle.com/javase/8/docs/technotes/guides/intl/encoding.doc.html).	Default value is "UTF-8". If you omit the option, "UTF-8" will be set automatically.
Query parameters	Optional	-	Specify the name and the value of a parameter linking to the URL. Each parameter can be operated with the following. [Add]: Adds a query parameter. [Up]: Moves the order of the selected query parameter upwards by one. [Down]: Moves the order of the selected query parameter downwards by one. [Delete]: Deletes the selected query parameter.	URL Encoding is applied with the encode selected or entered in [Encoding].
Query parameters/ Name	Optional	Available	Enter the name of a query parameter.	If you omit the name, the query parameter will not be linked to the URL.
Query parameters/ Value	Optional	Available	Enter the value of a query parameter.

Request Settings

Item name	Required/Optional	Use of Variables	Description	Remarks
Input source	Required	Not available	Select the input source of the request body. [Data]:(default) Regards input data as input source. [File]: Regards the specified file in [File path] as input source
Data type	Required	Not available	Select the data type of the request body. [XML]:(default) Processes with XML format. MIME type of the Content-Type header becomes "application/xml". [JSON]: Processes with JSON format. MIME type of the Content-Type header becomes "application/json". [Form]: Processes with Form format. MIME type of the Content-Type header becomes "application/x-www-form-urlencoded". [Multipart form]: Processes with Multipart form format. MIME type of the Content-Type header becomes "multipart/form-data".	Displayed if you select [Data] in [Input source]. Input schema differs depending on the selected data type. For details on input schema, please refer to "Input schema".
File path	Required	Available	Select or enter the file path that outputs request body. Click [Browse] button to activate the file Selectr and Select the file.	Displayed if you select [File] in [Input source]. MINE type of the Content-Type header is set automatically by distinguishing the extension of file names. If distinguishing fails, then become "application/octet-stream". Specify the absolute path of DataSpider file system for the file path. Constrained Characters of DataSpider File System cannot be used, except for the path separator "/".
Form parameters	Optional	-	Specify the parameter of Form that becomes the request body. Each parameter can be operated with the following. [Add]: Adds a parameter. [Up]: Moves the order of the selected parameter upwards by one. [Down]: Moves the order of the selected parameter downwards by one. [Delete]: Deletes the selected parameter.	Displayed if you select [Form] in [Data type].
Form parameters/ Name	Optional	Only environment variable is available	Enter the form name.
Mutlipart form parameters	Optional	-	Specify the multipart that becomes the request body. Each part can be operated with the following. [Add]: Adds a part. [Up]: Moves the order of the selected part upwards by one. [Down]: Moves the order of the selected part downwards by one. [Delete]: Deletes the selected part.	Displayed if you select [Mutlipart form] in [Data type].
Multipart form parameters/ Name	Optional	Only environment variable is available	Enter the name of a part on multipart.
Multipart form parameters/ Type	Optional	Not available	Select the type of part on multipart. [Character string]:(default) Regards the character string specified in the input data as body of the part. [File]: Regards the data loaded from the file specified in the input data as the body of the part.
If type is file, grand Content-Length header to Part header	Optional	Not available	If [File] is set at [Multipart form parameters/ Type], select whether to give Content-Length header, with the size of file specified in input data as value, to part header. [Checked]: Gives Content-Length header. [Not checked]:(default) Does not give Content-Length header.	Displayed if you select [Multipart form] in [Data type].

Property Action

Item name	Description	Remarks
Configure input schema from JSON file	Specify JSON file and set schema of input source.	Displayed if you select [JSON] in [Data type].

Response Settings

Item name	Required/Optional	Use of Variables	Description	Remarks
Data output source	Required	Not available	Select the output destination of response body. [Data]:(default) Outputs into the result data. Outputs with the format selected in [Data type]. [File]: Outputs into the file specified in [File path].
Data type	Required	Not available	Select the data type of response body. [XML]:(default) Processes with XML format. [JSON]: Processes with JSON format. [Other]: Processes with TEXT format or BINARY format.	Displayed if you select [Data] in [Data output destination]. Output schemas vary depending on the selected data type. For details on output schema, please refer to "Output schema".
File path	Required	Available	Select or enter the file path which outputs the response body. Click [Browse] button to activate the file Selectr and Select the file.	Displayed if you select [File] in [Data output destination]. Please specify the absolute path of the DataSpider file system as the file path. Constrained Characters of DataSpider File System cannot be used, except for the path separator "/".
Delete invalid XML characters	Optional	Not available	Select whether to delete invalid XML characters automatically if found any during analysis of JSON data. [Checked]: Deletes invalid XML characters. [Not Checked]:(default) Leaves invalid XML characters intact.	Displayed if you select [JSON] in [Data type].
Redirect automatically	Optional	Not available	Select whether to redirect automatically if the redirecting destination is included in the response. [Checked]: Redirects automatically. [Not checked]:(default) Does not redirect automatically.	For details on redirect, please refer to "Automatic Redirect".
Errors occur when the status code of response is 4xx or 5xx	Optional	Not available	Select whether to make the process an error if the status code of response is 4xx or 5xx. [Checked]: Make the process an error. [Not checked]:(default) Does not make the process an error.

Property Action

Item name	Description	Remarks
Set schema specifying the JSON file	Specify JSON file and set the schema of the output destination.	Displayed if you select [JSON] in [Data type].

Header Settings

Item name	Required/Optional	Use of variables	Description	Remarks
Request headers	Optional	-	Specify HTTP header to include in the request. Each request header can be operated with the following. [Add]: Adds a request header. [Up]: Moves the order of the selected request header upwards by one. [Down]: Moves the order of the selected request header downwards by one. [Delete]: Deletes the selected request header.
Request headers/ Name	Optional	Available	Enter the request header name.	If you omit the name, request header will not be included in the request.
Request headers/ Value	Optional	Available	Enter the request header value.
Response headers	Optional	-	Specify the header name to retrieve from the HTTP header included in the response. Each response header can be operated with the following. [Add]: Adds a response header. [Up]: Moves the order of the selected response header upwards by one. [Down]: Moves the order of the selected response header downwards by one. [Delete]: Deletes the selected response header.	The response header is defined as the component variable of the name entered in [Name].
Response headers/Name	Optional	Only environmental variables are available.	Enter the response header name.	Upper/lower case is not distinguished. If you omit the name, the response header will not be defined as the component variable. Trim and define as the component variable, if there's any spaces, tabs, or enters before and behind the name.

Authentication Settings

Item name	Required/Optional	Use of variables	Description	Remarks
Authentication	Required	Not available	Select how to authenticate when sending requests. [None]:(default) Does not operate authentication. [Basic authentication]: Operates basic authentication. [Digest authentication]: Operates digest authentication [WSSE authentication]: Operates WSSE authentication.
User name	Optional	Available	Enter the user name to use on the authentication.	Displayed if you select [Basic authentication], [Digest authentication] or [WSSE authentication] in [Authentication].
Password	Optional	Available	Enter the password to use on authentication.	Displayed if you select [Basic authentication], [Digest authentication] or [WSSE authentication] in [Authentication].

Data processing method

Item name	Required/Optional	Use of Variables	Description	Remarks
Mass data processing	Required	Not available	Select a data processing method. [Use script settings]: (default) Applies mass data processing settings of script property to adapter. [Disable]: Mass data processing is not performed. [Enable]: Mass data processing is performed.

Comment

Item name	Required/Optional	Use of variables	Description	Remarks
Comment	Optional	Not available	You can write a short description of this adapter. The description will be reflected in the specifications.

Schema

Input schema

Varies depending on the setting of [Data type] in [Request settings].

In case of [XML]

Differs depending on the request body of XML data.

In case of [JSON]

If the request body is JSON format data, processed converting the input data from XML format to JSON format.
Schemas with XML format to convert into JSON format data are the following.

<--In case the root is JSON object of object type -->
<?xml version="1.0"?>
<root type="object">
  <JSON member name type="Attribute value showing JSON type">value</JSON member name>
    :
</root>

<-- In case the root is JSON object of array type -->
<?xml version="1.0"?>
<root type="array">
  <element type="Attribute value showing JSON type">value</element>
    :
</root>

<-- In case the JSON member name is false as XML element name -->
<?xml version="1.0"?>
<root type="object">
  <member type="Attribute value showing JSON type" name="JSON member name">value</member>
    :
</root>

Element name

Attribute name

Description

Remarks

root

This is a root element that wraps JSON object.

type

Specifies the attribute value that shows JSON type.

Attribute value

Description

object

Shows the JSON object type.

Ex: XML data with type attribute of root element is "object".

<root type="object">
  <name type="string">Suzuki</name>
</root>

JSON object in the above example is output with conversion into the XML data.

{"name":"Suzuki"}

array

Shows JSON array type.

Ex: JSON object consists of array type.

["apple","grape","orange"]

JSON object in the above example is output with conversion into the XML data below.

<root type="array">
  <element type="string">apple</element>
  <element type="string">grape</element>
  <element type="string">orange</element>
</root>

The above examples of XML data are converted into the JSON object of the array type below.

["apple","grape","orange"]

If the type attribute does not exist, or the attribute value is empty, then becomes object type.

JSON member name

This is the element that shows JSON member.

type

Sets the attribute value that shows JSON type.

Attribute value	Description
string	Shows the JSON character string type. Ex: JSON member that has character string type value. {"name":"Suzuki"} JSON member in the above example is output with conversion into the XML data below. <name type="string">Suzuki</name>
number	Shows JSON numeric type. Ex: XML data with the type attribute value "number". <age type="number">37</age> The XML data in the above example will be converted into the JSON member which has the numeric type value as follows. {"age":37}
boolean	Shows JSON boolean type value. Ex: XML data with the type attribute value "boolean". <success type="boolean">true</success> The XML data in the above example will be converted into the JSON which has the boolean type value as follows. {"success":true}
object	Shows JSON object type. Ex: XML data with the type attribute "object". <name type="object"> <first type="string">Ichiro</first> <last type="string">Suzuki</last> </name> The XML data in the above example will be converted into the JSON member which has the object type value as follows. {"name":{"first":"Ichiro","last":Suzuki"}}
array	Shows JSON array type. Ex: Specifies XML "element" element of the JSON array type. If the element type of JSON array type is object type, specifies the XML data with schemas showing JSON object in the child element of "element" element. In case of other types, specifies values in the element contents of "element" element. JSON array type schema is as follows. <JSON member name type="array"> <element type="Attribute value showing JSON type">value</element> : </JSON member name> Ex: XML data with the type attribute value "array". <fruits type="array"> <element type="string">apple</element> <element type="string">grape</element> <element type="string">orange</element> </fruits> The XML data in the above example will be converted into the JSON member which has the array type value as follows. {"fruits":["apple","grape","orange"]}
null	Shows JSON null type. Ex: XML data with the type attribute "null" <name type="null"/> The XML data in the above example will be converted into the JSON member which has the null type value as follows. {"name":null}

Becomes character string type if type attribute does not exist, or the attribute value is empty.
Element contents are ignored, if the type attribute is "null".

element

Element showing the array element.

type

Specifies the character string showing JSON type.
Specifies the same attribute value as the type attribute of JSON member name.

If type attribute does not exist or attribute value is empty, then becomes character string type.

member

This is the element alternatively specifying, in case the JSON member name is false as the element name.

type

Outputs the character string that shows JSON type.
Specifies the same attribute value as JSON member name type attribute.

If type attribute does not exist or attribute value is empty, then becomes character string type.

name

Specifies the JSON member name.

Ex: XML data Specifying the JSON member name into the name attribute value specifying member element.

<member type="string" name="1name">Suzuki</member>

The XML data in the above example will be converted into the JSON member as follows.

{"1name":"Suzuki"}

If type attribute does not exist or attribute value is empty, then becomes character string type.

In case of [form]

<?xml version="1.0"?>
<request>
  <body>
    <form>
      <form parameter name>
        <value>Form parameter value</value>
      </Form parameter name>
        :
      <-- in case form parameter name is false as the XML element name -->
      <parameter name="form parameter name">
        <value>form parameter value</value>
      </parameter>
        :
    </form>
  </body>
</request>

Element name	Attribute name	Description	Remarks
request	-
body	-
form	-
form parameter name	-	Elements showing form parameter name.	URL encoded with the encodes specified in [Encoding].
parameter	-	Elements when form parameter name is false as XML element name.	When form parameter name is false as XML element name, then sets the Form parameter name as parameter element.
parameter	name	Enter the form parameter name.	URL encoded with the encodes specified in [Encode].
value	-	Enter the form parameter value.	URL encoded with the encodes specified in [Encode].

Ex: In case the input data is as follows

<?xml version="1.0"?>
<request>
  <body>
    <form>
      <firstname>
        <value>Ichiro</value>
      </firstname>
      <lastname>
        <value>Suzuki</value>
      </lastname>
    </form>
  </body>
</request>

Upon the above XML data, the form data stored in the request body will be as follows.

Content-Type: application/x-www-form-urlencoded; charset="UTF-8"

firstname=%E4%B8%80%E6%9C%97&lastname=%E9%88%B4%E6%9C%A8

In case of [Multipart form]

<?xml version="1.0"?>
<request>
  <body>
    <multipart>
      <-- If the type is "Character string". -->
      <part name>
        <value>form value</value>
      </part name>
        :
      <-- If the type is "File". -->
      <part name>
        <file>
          <path>file path</path>
        </file>
      </part name>
        :
      <-- If the part name is false as the XML element name. -->
      <part name="part name">
        <value>part value</value>
      </part>
        :
    </multipart>
  </body>
</request>

Element name	Attribute name	Description	Remarks
request	-
body	-
multipart	-
part name	-	Element describing part name.	Encoded with the encodes specified in [Encode].
part	-	Element when the part name is false as XML element name.	When the part name is false as XML element name, set the part as part element.
part	name	Enter the part name.	Encoded with the encodes specified in [Encode].
value	-	Enter the character string that becomes part body.	Encoded with the encodes specified in [Encode].
file	-
file	mimeType	Enter the MIME type that appears in the part Content-Type header.	If mimeType attribute does not exist, or the attribute value is empty, the MIME type of Content-Type header will be input automatically distinguished from the extensions of the file name included in the path entered in path. Once it's not available to distinguish, then becomes "application/octet-stream".
path	-	Enter the file path that becomes the part body.	Please specify the absolute path of the DataSpider file system as the file path. Constrained Characters of DataSpider File System cannot be used, except for the path separator "/". The file name included in the path will be encoded with the encode specified in [Encode].

Ex: If the input data is as follows.

<?xml version="1.0"?>
<request>
  <body>
    <multipart>
      <firstname>
        <value>Ichiro</value>
      </firstname>
      <lastname>
        <value>Suzuki</value>
      </lastname>
      <attachment>
        <file>
          <path>/data/profile.jpg</path>
        </file>
      </attachment>
    </multipart>
  </body>
</request>

Upon the above XML data, the multipart form data stored in the request body will be as follows.

Content-Type: multipart/form-data; boundary=<boundary>

--<boundary>
Content-Disposition: form-data; name="firstname"

Ichiro

--<boundary>
Content-Disposition: form-data; name="lastname"

Suzuki

--<boundary>
Content-Disposition: form-data; name="attachment"; filename="profile.jpg"
Content-Type: image/jpeg

<data of /data/profile.jpg>

--<boundary>--

Output schema

Schema differs depending on the setting of [Data type] of [Response settings]

In case of [XML]

Differs depending on the XML data of the response body.

In case of [JSON]

If the response body is JSON format data, then output to the result data by converting into XML format.
The schema in the case of converting from JSON format to XML format is as follows.

<--In case the root is JSON object of object type. -->
<?xml version="1.0"?>
<root type="object">
  <JSON member name type="attribute showing JSON type">value</JSON member name>
    :
</root>

<-- In case the root is the JSON object of array type -->
<?xml version="1.0"?>
<root type="array">
  <element type="attribute showing JSON type">value</element>
    :
</root>

<-- In case the JSON member name is false as the XML element name -->
<?xml version="1.0"?>
<root type="object">
  <member type="attribute name showing JSON type" name="JSON member name">value</member>
    :
</root>

Element name

Attribute name

Description

Remarks

root

Element that wraps the JSON object.

type

Attribute value showing JSON type will be set.

Attribute value

Description

object

Shows JSON object type.

Ex: JSON object consist of object type.

{"name":"Suzuki"}

JSON object of the above example will be output with conversion into the following XML data.

<root type="object">
  <name type="string">Suzuki</name>
</root>

array

Shows JSON array type.

Ex: JSON object consist of the array type.

["apple","grape","orange"]

JSON object of the above example will be output with conversion into the following XML data.

<root type="array">
  <element type="string">apple</element>
  <element type="string">grape</element>
  <element type="string">orange</element>
</root>

JSON member name

Element showing JSON member.

type

Attribute value showing JSON type will be set.

Attribute value	Description
string	Shows the JSON character string type. Ex: JSON member having character string type value. {"name":"Suzuki"} JSON object of the above example will be output with conversion into the following XML data. <name type="string">Suzuki</name>
number	Shows the JSON numeric type. Ex: JSON member having numeric type value. {"age":37} JSON object of the above example will be output with conversion into the following XML data. <age type="number">37</age>
boolean	Shows the JSON boolean type. Ex: JSON member having boolean type. {"success":true} JSON object of the above example will be output with conversion into the following XML data. <success type="boolean">true</success>
object	Shows the JSON object type. Ex: JSON member having object type value. {"name":{"first":"Ichiro","last":Suzuki"}} JSON object of the above example will be output with conversion into the following XML data. <name type="object"> <first type="string">Ichiro</first> <last type="string">Suzuki</last> </name>
array	Shows the JSON array type. The element of JSON array type will be shown as "element" element. If the element of the JSON array type element is the object type, XML data having schemas showing the JSON object will be output into the child element of the "element". Other types will be output into the element contents in which the value is "element" element. Schemas are as follows. <JSON member name type="array"> <element type="Attribute value showing JSON type">value</element> : </JSON member name> Ex: JSON member having array type value. {"fruits":["apple","grape","orange"]} JSON object of the above example will be output with conversion into the following XML data. <fruits type="array"> <element type="string">apple</element> <element type="string">grape</element> <element type="string">orange</element> </fruits>
null	Shows JSON null type. Ex: JSON member having null type value. {"name":null} JSON object of the above example will be output with conversion into the following XML data. <name type="null"/>

element

Element name showing the array element.

type

Character string showing JSON type will be output.
The same attribute value as the JSON member name type attribute will be set.

member

Element name used if the JSON member name is false as the XML element name.

type

Character string showing JSON type will be output.
The same attribute value as JSON membe name type attribute will be set.

name

JSON member name will be output.

Ex: JSON member having the name that is false as the XML element name.

{"1name":"Suzuki"}

JSON object of the above example will be output with conversion into the following XML data.

<member type="string" name="1name">Suzuki</member>

In case of [Other]

<?xml version="1.0"?>
<response>
  <body>
    <content>Data of response body</content>
  </body>
</response>

Element name	Attribute name	Description	Remarks
response	-
body	-
content	-	This is the data of response body.	Data differs depending on the value of Content-Type header of the response. If it matches the condition below, response body is recognized as text data and output character string encoded by value of charset parameter Content-Type header. Content-Type header type is "text". Content-Type header subtype ends with "xml" or "json". If it does not match the condition above, character string will be output, in which the recognized the response body as binary and converted data of byte column created based on value of charset parameter of Content-Type header into Base64 format. If Content-Type header or charset parameter does not exist, then becomes "ISO-8859-1" by default.

Loading Input Schema in Mapper

Depending on the setting of [Data type] in [Request settings], the loading of input schema differs.

In case of [XML]

The schema needs to be read manually.
Specify the schema of the targeted reading data.

In case of [JSON]

If you set [Configure input schema from JSON file], schema will automatically be read.

In case of [Form]

Schema is automatically read.

In case of [Multipart form]

Schema is automatically read.
lightbulb

Schemas automatically loaded can be edited.

For more details, please refer to "Edit schema".

Loading Output Schema in Mapper

Depending on the setting of [Data type] in [Request settings], the loading of output schema differs.

In case of [XML]

The schema needs to be read manually.
Specify the schema of the targeted reading data.

In case of [JSON]

If you set [Configure input schema from JSON file], schema will automatically be read.

In case of [Other]

Schema is automatically read.
lightbulb

Schemas automatically loaded can be edited.

For more details, please refer to "Edit schema".

Mass Data Processing

Mass data processing is supported.

Transaction

Transaction is not supported.

PSP Usage

PSP is not supported.

Available Component Variables

Component variable name	Description	Remarks
status_code	Stores HTTP status code of responses.	The value defaults to null.
reason_phrase	Stores the text phrase related to the HTTP status code of responses.	The value defaults to null.
error_response_body	Stores the response body in the case the response status code is "4xx" or "5xx".	The value defaults to null.
message_category	When errors occur, stores the message code category corresponding to the error.	The value defaults to null.
message_code	When errors occur, stores the codes of message code corresponding to the error.	The value defaults to null.
message_level	When errors occur, stores the message code severity corresponding to the error.	The value defaults to null.
error_type	When errors occur, stores the error type corresponding to the error.	The value defaults to null. Error types take the following formats. Ex: "java.io.FileNotFoundException" Depending on the versions of DataSpider Servista, the storing contents may vary.
error_message	When errors occur, stores the error message.	The value defaults to null. Depending on the versions of DataSpider Servista, the storing contents may vary.
error_trace	When errors occur, stores the trace information of the error occurred.	The value defaults to null. Depending on the versions of DataSpider Servista or the executing client application, the storing contents may vary.

Automatic Redirect

The operations if you put check in [Redirect automatically] are as follows.

If the status code of the responses accord to the following, Resends the request to the URI shown in "Location" header of responses.
- 301:(Moved Permanently)
- 302:(Found)
- 303:(See Other)
- 307:(Temporary Redirect)

About result data when the status code of response is above 400

When the status code of response is above 400, outputs the response body to the result data.
Then, the schema of result data differs depending on the Content-Type header value of the response.

If the sub-type of Content-Type header ends with "xml".
Differs depending on the XML data of the response body.

If the sub-type of Content-Type header ends with "json".
Becomes "JSON format schema".

If any of the above does not apply.
Becomes "Schema of other data type"
content element contents follow the below provisions and encoded response body will be output.
- Encoded with the charset parameter value in Content-Type header, if there is Content-Type header in response header.
- Encoded as "ISO-8859-1", if there is no Content-Type header in response header, or no charset parameter in Content-Type header.

Specification Limits

HTTP version of request is 1.1.

It will be ignored, if you specify a query parameter or URL fragment in [Path].

If [Data type] is [XML] or [JSON], it will be encoded by UTF-8 and sent.

If the response body is not in the format selected in [Data type], errors occur in the analysis process of response body.

If you select [Errors occur if status code of response is 4xx or 5xx], the process will be recognized as an error, whereas the result data will be output if there is the response body.

You cannot specify the following headers into [Request headers].
- Content-Length
- Content-Transfer-Encoding
You cannot input 2-byte characters into [Name] and [Value] of [Request headers].

You cannot input the name defined in "Component variable" into the [Name] of [Response headers].

You cannot multiply specify the same name header into [Response headers].

Cookie will be passed down within the script. However, Cookie is assigned to a thread, which means that thread generated by the thread process will not be passed down.

Main Exceptions

Exception name	Causes	Solution
ResourceNotFoundException Resource definition could not be found. Name:[]	[Destination] is not specified.	Please specify [Destination] .
ResourceNotFoundException Resource definition could not be found.Name: [<name of Global Resources>]	Resource definition selected in [Destination] is not found.	Please check the global resource specified in [Destination]
InvalidPropertyConfigurationException Required item of resource is not specified. :<Property name>	[<Property name>] of [Destination] is not specified.	Please specify [<Property name>] in [Destination].
InvalidPropertyConfigurationException <Property name> is not specified.	[<Property name>] is not specified.	Specify [<Property name>].
FileIsDirectoryException	Path input in [File path] is directory.	Input file path in [File path].
PathIsNotAbsoluteException	Relative path is the path entered in [Path] or [File path].	Enter the absolute path in [Path] or [File path].
PathIsRequiredException	While sending multipart form data, path that shows the data of file storing in a body part is not set in the input data.	Please check whether the path is set in the path element of the input data.
RestServerException	Response with the status code "5xx" is returned from HTTP Server.	Please check the conditions of HTTP server and contents of request specified in [Destination] by referring to the contents of error messages.
RestClientException	Response with the status code "4xx" is returned from HTTP Server.	Please check the entered path and the contents of request in [Path] by referring to the contents of error messages.
org.apache.http.client.ClientProtocolException	Error occurred wile sending the request.	Please check the content of the error message.
org.apache.http.conn.HttpHostConnectException	Could not connect to HTTP server or Proxy server.	Please check whether connection is available to the destined HTTP server or Proxy server or not.
org.apache.http.conn.ConnectTimeoutException	Connection timeout occurred when connecting with HTTP server or Proxy server.	Please check the setting of [Connection timeout] in [Destination].
java.net.SocketTimeoutException	After connecting to HTTP server, timout occurred during the reply of sending the request and receiving the response.	Please check the setting of [Receive timeout] in [Destination].
javax.json.stream.JsonParsingException	Error occurred during processing the response body as JSON format.	Please check the setting and the response contents of [Response settings] referring to the error message.
javax.json.stream.JsonGenerationException	Error occurred during the JSON conversion process of the input data.	Please check the input data contents.

Notes

About failure to SSL connection
You might fail to connect when you SSL connect to the Web server without having certifications not imported to the key store that DataSpiderServer refers to. You may also see "javax.net.ssl.SSLHandshakeException" errors occurring upon the failure.
For more details on how to import to the key store, please refer to "Import of certificate".
Certifications can also be retrieved from Internet Explorer. For more details, please refer to "Download certification using Internet Explorer".