Table of Contents
・Points to check when you want to isolate the problem
・If you want to know the reasons why double check is required
・If you still cannot determine the cause or recover from the problem even after reading this document

Also, if you would like more information related to this inquiry, please check "Reference Information."  

 

 

*In this document, we will refer to the server where DataSpiderServer is installed as "Server" and the client where DataSpider Studio is installed as "Client."
 

 

1.  DataSpider Studio Communication Settings

　Please make sure that the following settings key in the settings file is not commented out with a "#", and that it has been assigned a value.

・Settings File
　$DATASPIDER_HOME/server/conf/system.properties

・Settings Key
　java.rmi.server.hostname
　ds.rmi.port

　If it has been commented out with a "#", please take the following measures to handle it.

Workaround:
　Assign the proper host name for "java.rmi.server.hostname", and a port which can communicate between the "server" and "client" for "ds.rmi.port".

　Please refer to FAQ No.24460 for how to configure the settings.

 

 

2.  “Server”-“Client” Communications Environment

　Check to see if communication is possible by executing the following command on the server where DataSpiderServer is installed.

　telnet ＜Value of java.rmi.server.hostname confirmed in 1. ＞ ＜Value of ds.rmi.port confirmed in 1. ＞

　If proper communication is not possible, a communication error such as "Connection refused," etc. will occur.
　If proper communication is possible, nothing will be displayed on the screen.
　If this is the case, please terminate telnet by pressing Ctrl + [.

　If an error occurs, please handle it with the following workaround.

Workaround:
　Make changes to your communications environment so that communications from the "server" to the "client" are possible via the "java.rmi.server.hostname" and "ds.rmi.port" assigned in section 1.

 

3. Repository DB Usage ad Communication Environment

Please check whether or not you are using a repository DB, and if you are using one, check whether it is installed on the same server as DataSpiderServer, or in a place that could have an effect on communications such as on a separate segment, in the cloud, etc..

　In past cases, issues involving unresponsiveness have occurred in situations such as the following.
　- "Server" and repository DB are on separate segments    
　- Communication path between "Server" and repository DB goes through VPN

Workaround:
　Use the database installed on the same server or same segment as DataSpiderServer

　To migrate settings, please use the server migration function.
　Please refer to the following for details on the server migration function.
　https://www.hulft.com/help/en-us/DataSpider/latest/help/en/servista/service_production.html#import_export

 

4. “Server”-“Client” Communications Environment

　Please check to see if there are any bandwidth or speed limitations on the communications between your "Server" and "Client."

　In past cases, issues involving unresponsiveness have occurred in situations such as the following.
　- "Server" and "Client" are on separate segments
　- Communication path between "Server" and "Client" goes through VPN
　- "Server" and "Client" are physically separated by large distances

Workaround:
　Please consider one of the following measures. 。
　- Install DataSpider Studio on a device in the same segment as the "Server," and use DataSpider Studio by logging into that device with remote desktop
　- Use Data Spider Studio for Web

　DataSpider Studio for Web requires a different license from DataSpider Studio. 。
　For testing in an environment where a license has not been purchased, please apply for a Trial version     license.
 

 

 

　Upon expanding my project or designer in DataSpider Studio, strictly for the first after your initial login, connection verification （CALLBACK） from DataSpiderServer is received

　DataSpider studio is on connection verification standby from the host name and port assigned in the settings file in Points to Check 1, and will not proceed to the next process (displaying the screen) until it is received.

　This is why it appears to be unresponsive.
　In order to determine whether or not the above is happening, the following must be checked.
 

1. Confirmation of the environment using DataSpider Studio
 

2. “Server” – “Client” Communications Environment

If you are using repository DB, in order to obtain various information settings to display in DataSpider Studio, inquiry will be issued from DataSpiderServer to repository DB.

Therefore, if it takes time to obtain information from repository DB, it is possible to experience response delay. In order to determine whether or not this is the case, the following must be checked.
 

3. Repository DB Usage and Communication Environment

Even if you're not experiencing issues communicating between DataSpiderServer and repository DB or when you're not using repository DB at all, if it takes time to communicate between DataSpiderServer and DataSpider Studio, it may still take time to display due to response delay which causes more time to obtain necessary information.
It is for this reason that checking the following is necessary.
 

4. “Server” – “Client”Communications Environment

Communication (RMI communication) used between DataSpiderServer and DataSpider Studio has a higher communication rate compared to other communication method (such as FTP), thus it has a tendency to be affected greatly depending on the physical distance and the zone location.

For the reason mentioned above, even if you are not experiencing a slow down in response due to other working processes, in order to isolate the cause, please consider trying remote desktop or DataSpider Studio for Web.

 

 

 

If your issue is not resolved even after executing all of the contents described in "Points to Check and Troubleshooting Measures," then it is possible that some error is preventing a process from successfully ending.

In order to confirm the situation, please make an inquiry at the support center after
checking the following information.

 

(1) What triggered the issue
Check to see if the issue started to occur just after installation of DataSpiderServer, or if the issue occurs due to a sudden response delay on an environment with no response issue until then.

And in the case that responsiveness suddenly became sluggish, please check the date when you noticed the decrease in performance. Also check any settings that were changed or work that was done before or after that date.

 

(2) Detailed situation
　Please check the following information in relation to the unresponsiveness.
　・Screens or functions being displayed
　・Number of seconds until the display is completed
　・Characteristics (only one group of icons is displayed quickly, stuck on loading, etc.)

 

(3) Log files and time of operation
　Please send details of the time when you noticed the unresponsiveness, and any log files that were updated at that time.
　Necessary log files are as follows.

・Server End
　$DATASPIDER_HOME/server/logs/server.log
　$DATASPIDER_HOME/server/logs/server.error.log
　$DATASPIDER_HOME/server/logs/${execution date}/exec.log

・Client End
　$DATASPIDER_HOME/client/logs/client.log
　$DATASPIDER_HOME/client/logs/client.error.log
　$DATASPIDER_HOME/client/logs/studio.log

 

(4) Communication Settings File
　Please send us the current setting files so that we can reference it to verify log files.

・Settings File
　$DATASPIDER_HOME/server/conf/system.properties
 

 

[Reference Information]

 

・About Server Migration
https://www.hulft.com/help/en-us/DataSpider/latest/help/en/servista/service_production.html#import_export

・Countermeasure for if a problem exists in the communication setting of DataSpider Studio
FAQ No.24460