The matter of the slow response of DataSpider Studio occurs due to multiple factors such as communication line with DataSpiderServer and communication settings.

 

Please refer to the following for details:

 

Table of Contents

 

 

Also, if you would like to refer to information related to this inquiry, please check the “Reference Information.”

 

 

*In the following description, "Server" refers to a server on which DataSpiderServer is installed and "Client" refers to a client on which DataSpider Studio is installed.

Please confirm whether the setting key of the following setting file is not commented out with "#" and the value is set:

$ DATASPIDER_HOME / client / conf / system.properties

java.rmi.server.hostname

ds.rmi.port

 

If the value is commented out with "#", please proceed to the following workaround.

 

Workaround

 

Please specify a correct hostname in "java.rmi.server.hostname" and a port available for communication between “Server” and “Client” in "ds.rmi.port".

 

Please refer to the FAQ below for the setting method.

 

 

[DataSpider Servista] Explain about the problem that occurs in the terminal in which DataSpider Studio has been installed newly

Please execute the following command on the server with DataSpiderServer installed and check if the communication is possible.

 

telnet <a value of java.rmi.server.hostname confirmed in 1.> <a value of ds.rmi.port confirmed in 1.>

 

If the communication is not successful, a communication error such as Connection refused occurs. If the communication is successful, nothing is displayed on the screen. In this case, please quit the telnet by pressing Ctrl + [.

 

If the error occurs, please execute with the following workaround.

 

Workaround

 

Please change the communication environment so the communication is available from "Server" to "Client" with "java.rmi.server.hostname" and "ds.rmi.port" specified in step 1.

If you are using a repository DB, please make sure it is installed on the same server as DataSpiderServer or in a location that affects communication, such as on another segment or in the cloud.

 

In the past case, the poor response problem occurred in the following cases:

 

 

Workaround

 

Use either the same server as DataSpiderServer or a database installed on the same segment as the repository DB.

 

For the migration of settings, please use the server migration function. Please check the details about the server migration function from the following:

 

For communication between “Server” and “Client,” please make sure if there are restrictions to bandwidth or speed.

 

In past cases, the problem of poor response occurred in the following cases:

 

 

Workaround:

 

Please try one of the following methods.

 

 

DataSpider Studio for Web requires a different license than DataSpider Studio. If you want to verify in an environment where you have not purchased a license, please apply for an evaluation license.

 

 

 

When expanding My Project and Designer in DataSpider Studio, the communication confirmation (CALLBACK) is received from DataSpiderServer only when logging in and expanding for the first time.

 

DataSpider studio is waiting for this traffic confirmation with the hostname and port specified in the configuration file at point 1. It will not proceed with the next process (screen display) until it receives it

 

As a result, the response appears to be degraded. The following checks are required to isolate the situation above.

 

In addition, if you are using the repository DB, DataSpiderServer queries repository DB to obtain various setting information to be displayed in DataSpider Studio.

 

For this reason, if it takes time to acquire information from the repository DB, the overall response will be degraded. The following confirmation is necessary to separate the above.

If the communication between DataSpiderServer and DataSpider Studio is slow even though there is no problem in communication between DataSpiderServer and repository DB, and repository DB is not used, it takes time to acquire the information required for display, and overall the response is reduced. For this reason, the following confirmation is required.

Please note that the communication method (RMI communication) used between DataSpiderServer and DataSpider Studio has more communication count than other communication methods (FTP etc.) and tends to be greatly affected by the bandwidth and physical distance.

 

For this reason, please consider using Remote Desktop and DataSpider Studio for Web to check the cause separation even if the processing does not seem to be slow by other processes.

 

 

If the problem is not solved even if you execute all the methods described in "Confirmation point and workaround", some error may occur and the process may not be completed normally.

 

For confirmation of the situation, please obtain the following information and contact the support center.

 

Please check if the incident occurred immediately after installing DataSpider Studio or if the response has suddenly dropped in an environment where there was no problem with the response.

 

Also, if the response drops suddenly, please confirm the date and time when the drop was confirmed and the changed settings and the work performed before and after that.

Please check the following information regarding the poor response.

Please send the time zone where the response deterioration was confirmed and the log file updated during that time zone. The required log files are as follows.

$DATASPIDER_HOME/server/logs/server.log

 

$DATASPIDER_HOME/server/logs/server.error.log

 

$ DATASPIDER_HOME / server / logs / $ {execution date} /exec.log

$DATASPIDER_HOME/client/logs/client.log

 

$DATASPIDER_HOME/client/logs/client.error.log

 

$DATASPIDER_HOME/client/logs/studio.log

Please send the current configuration file for reference when checking the log file.

$DATASPIDER_HOME/client/conf/system.properties

 

• About server switchover

• What to do if there is a problem with the communication settings of DataSpider Studio