Stop server

Operation Name

Stop server

Function Overveiw

Stops specified server.

Data Model

XML type.

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.  
Required settings
Item name Required/Optional Use of variables Description Remarks
Destination Required Not available Select a global resource.
  • [Add]:
    Adds a new global resource.
  • [Edit list]:
    Enables to edit the global resource settings in the "Edit resource list".
 
Server name list Required
-
Specify multiple server names to terminate.

Each column can be operated by following buttons.
  • [Add]:
    Adds a column.
  • [Up]:
    Moves the order of the selected column upwards by one.
  • [Down]:
    Moves the order of the selected column downwards by one.
  • [Delete]:
    Deletes a column.
 
Server name list/server name Required Available Select or enter terminateping server name.
  • During initial display, nothing will be displayed in item selection.
  • If push down [Obtain server name list], server name created in [Destination] will be displated in item selection.
Stand by until server stops Optional Not available Select whether to stand by until server terminate is completed.
  • [Checked]:(Default)
    Stands by until server completes termination.
  • [Not checked]:
    If terminate request is sent to server, it will not stand by and proceed to following process.
  • If [Checked], it will continue to confirm server status until the value entered in [Timeout] of the global resource specified in [Destination] after process launched.
    After confirming that server terminate is completed, it will proceed to following process.
    If server's terminate completion cannot be confirmed by milliseconds enter in [Timeout], an error will occure.
Property action
Item name Description Remarks
Retrieve server name list Obtains server name created in [Destination] in order to select it from [Server name list/server name].  
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

None.

Output schema

<?xml version="1.0"?>
<instances>
  <instance currentState="" name="" previousState="" />
</instances>
Element name Attribute name Description Remarks
instances -    
instance - It will appear in every server specified in [Server name list/server name].  
currentState Outputs current server status.
  • [running]: Server is launched.
  • [pending]: Server is in the process of being launched/terminateped.
  • [terminateped]: Server is terminated.
 
name Outputs server name.  
previousState Outputs precede server status.
  • [running]: Server is launched.
  • [pending]: Server is in the process of being launched/terminateped.
  • [terminateped]: Server is terminated.
 

Loading Schema on Mapper

Schema is loaded automatically.
For more details, refer to "Edit schema".

Mass Data Processing

Mass Data Processing is not supported.

Transaction

Transaction is not supported.

PSP Usage

Transaction is not supported.

Available Component Variables

Component variable name Description Remarks
message_category Stores the category of message code corresponding to the occured error.
  • Default value is null.
message_code Stores the code of message code corresponding to the occured error.
  • Default value is null.
message_level Stores the severity of message code corresponding to the occured error.
  • Default value is null.
error_type Stores the error type of occured error.
  • Default value is null.
  • Error is represented in the format depicted below.
    Example:"java.io.FileNotFoundException"
  • The message may vary depending on the DataSpider Servista version.
error_message Stores the error message of occured error.
  • Default value is null.
  • The message may vary depending on the DataSpider Servista version.
error_trace Stores the trace information of occured error.
  • Default value is null.
  • The message may vary depending on the DataSpider Servista version or the client application used.

Specification Limits

Main Exceptions

Exception name Cause Solution
ResourceNotFoundException
Resource definition could not be found. Name:[]
[Destination] is not specified. Specify [Destination].
ResourceNotFoundException
Resource definition could not be found. Name:[<Name of global resources>]
Resource definition selected in [Destination] cannot not be found. Confirm the global resource specified in [Destination].
InvalidPropertyConfigurationException
<Property name> is not set up.
[<Property name>] is not set up. Set up [<Property name>].
InvalidPropertyConfigurationException
Timeout must be larger than 0.
A numerical value greater than 0 is entered in [Timeout] of the global resource specifed in [Destination]. Enter numerical value greater than 0 in [Timeout] of the global resource specified in [Destination].
InvalidPropertyConfigurationException
Enter intergers or variables in a timeout.
A value other than numerical value is entered in [Timeout] of the global resource specifed in [Destination]. Enter numerical value in [Timeout] of the global resource specified in [Destination].
BiglobeCloudhostingClientException
Code=AuthFailure, Message='AccessKeyId' does not exist.
There is an error in [API access key] of the global resource specified in [Destination]. Confirm global resouce setting specifed in [Destination].
BiglobeCloudhostingClientException
Code=AuthFailure, Message=Incorrect value 'Signature' .
There is an error in [Encryption key ] of the global resource specified in [Destination]. Confirm global resouce setting specifed in [Destination].
BiglobeCloudhostingClientException
Code=InvalidInstanceID.NotFound, Message='InstanceId.1' does not exist.
Server entered in [Server name list/server name] does not exist. Enter the correct server name in [Server name list/server name].
BiglobeCloudhostingTimeoutException
<Timeout>Server's status did not change within millisecond.
After terminate request transmission completed, server terminate did not complete within [Timeout] of the global resource specified in [Destination]. Confirm [Timeout] of the global resource specified in [Destination].
BiglobeCloudhostingTimeoutException
org.apache.http.conn.ConnectTimeoutException: Connect to <Host> timed out
Timeout occured during while connecting to the host. Confirm the network status. Or confirm [Timeout] of the global resource specified in [Destination].
BiglobeCloudhostingTimeoutException
java.net.SocketTimeoutException: Read timed out
Timeout occured after connecting the host, but before response from the host. Confirm the host status. Or confirm [Timeout] of the global resource specified in [Destination].

Note