4.1 Install Guide · 2018-07-31 · This document describes how to install and setup the new...

4.1 Install Guide

Document Release Date: June 14 2018 (The 3rd Edition)

Copyright© 2018 APPRESSO K.K. All rights reserved.

DataSpider Servista 4.1 Install Guide

Copyright© 2018 APPRESSO K.K. All rights reserved. 2

Table of Contents

1. Before Use ........................................................................................................... 11

Precautions.......................................................................................................... 12 1.1.

Copyright Notice ........................................................................................ 12 1.1.1.

Trademarks ............................................................................................... 12 1.1.2.

About the mark of this document ........................................................................... 13 1.2.

About the Icons Used in This Guide ........................................................................ 14 1.3.

2. About end of sales and support ............................................................................... 15

Supported OS ...................................................................................................... 15 2.1.

Repository DB ...................................................................................................... 16 2.2.

Adapter ............................................................................................................... 18 2.3.

3. About DataSpider Servista...................................................................................... 21

Composition of DataSpider Servista ........................................................................ 21 3.1.

4. OS supporting DataSpider Servista .......................................................................... 22

Server and Client for Execution .............................................................................. 22 4.1.

Client for Development ......................................................................................... 23 4.2.

Language in Support Platform ................................................................................ 24 4.3.

About Windows language packs (Multilingual User Interface Pack)................... 25 4.3.1.

Specification Limits / Precautions ........................................................................... 26 4.4.

Specification Limits / Precautions for language settings .................................. 26 4.4.1.

Restriction for timezone in platform ............................................................. 27 4.4.2.

Supported virtualization system ............................................................................. 28 4.5.

5. System requirements ............................................................................................ 29



Both Server and Client .......................................................................................... 29 5.1.

Server ................................................................................................................. 29 5.2.

Client for development .......................................................................................... 30 5.3.

Client for Execution .............................................................................................. 30 5.4.

6. About Java Runtime Environment ........................................................................... 31

7. Repository DB settings ........................................................................................... 32

What is a Repository DB? ...................................................................................... 32 7.1.

Repository DB settings ............................................................................... 32 7.1.1.

Creating a Repository DB ............................................................................ 32 7.1.2.

Operation with / without a Repository DB ..................................................... 33 7.1.3.

Databases supported as Repository DB ................................................................... 34 7.2.

Setting up each database ...................................................................................... 36 7.3.

When using DB2 for Linux, UNIX, and Windows ............................................ 36 7.3.1.

When using MySQL .................................................................................... 37 7.3.2.

When using Oracle Database....................................................................... 38 7.3.3.

When using PostgreSQL ............................................................................. 39 7.3.4.

When using Microsoft SQL Server ................................................................ 40 7.3.5.

When using MySQL on Amazon RDS ............................................................ 42 7.3.6.

When using Oracle Database on Amazon RDS ............................................... 43 7.3.7.

When using PostgreSQL on Amazon RDS ...................................................... 44 7.3.8.

When using Microsoft SQL Server on Amazon RDS ........................................ 45 7.3.9.

When using Azure SQL Database .............................................................. 46 7.3.10.

When using Oracle Database Cloud Service(Oracle Database 12c Release 7.3.11.

2(12.2)) 47

8. Specifications and Limitations at Installation ............................................................. 48



General ............................................................................................................... 48 8.1.

Installer .............................................................................................................. 49 8.2.

Select Component ................................................................................................ 49 8.3.

Select Repository DB ............................................................................................ 49 8.4.

Register Windows Service ..................................................................................... 50 8.5.

Installation Directory Settings ................................................................................ 50 8.6.

Installation Complete ............................................................................................ 50 8.7.

9. Notes concerning Windows ..................................................................................... 51

Notes when Installing DataSpider Servista .............................................................. 51 9.1.

10. Installation of DataSpider Servista ........................................................................... 52

Start Installation ................................................................................................ 52 10.1.

File name and Supported OS of Each Installer ............................................ 52 10.1.1.

Description of each screen of Installer ................................................................... 53 10.2.

Start Installer ......................................................................................... 53 10.2.1.

Select Language ..................................................................................... 53 10.2.2.

Introduction Screen ................................................................................ 53 10.2.3.

Select Package ....................................................................................... 53 10.2.4.

Software License Agreement .................................................................... 53 10.2.5.

Select Component................................................................................... 54 10.2.6.

Select Client Environment ........................................................................ 55 10.2.7.

Administrator Password Settings .............................................................. 55 10.2.8.

Repository Database Settings ................................................................... 56 10.2.9.

Select Database Product .......................................................................... 56 10.2.10.

For DB2 ................................................................................................. 57 10.2.11.

For MySQL ............................................................................................. 57 10.2.12.



For Oracle .............................................................................................. 57 10.2.13.

For PostgreSQL ....................................................................................... 58 10.2.14.

For SQL Server ....................................................................................... 58 10.2.15.

Register Windows Service ........................................................................ 59 10.2.16.

DataSpider Server Settings ...................................................................... 59 10.2.17.

Installation Directory Settings .................................................................. 60 10.2.18.

Select License File ................................................................................... 60 10.2.19.

Heap Size Settings .................................................................................. 60 10.2.20.

Summary of Installation .......................................................................... 61 10.2.21.

Installing DataSpider Servista 4.1 ............................................................. 61 10.2.22.

Install completed .................................................................................... 61 10.2.23.

Installation of License File .................................................................................... 62 10.3.

About Windows Start Menu.................................................................................. 63 10.4.

11. Pre-setting of Adapters .......................................................................................... 65

Access adapter ................................................................................................... 65 11.1.

11.1.1. Access 2013/2010 adapter ...................................................................... 65

DB2 adapter ...................................................................................................... 66 11.2.

DB2 V11.1 adapter ................................................................................. 66 11.2.1.

DB2 V10.5 adapter ................................................................................. 66 11.2.2.

DB2 for i 7.3 / 7.2 / 7.1 adapter ............................................................... 68 11.2.3.

MySQL adapter ................................................................................................... 69 11.3.

MySQL 5.7 adapter ................................................................................. 69 11.3.1.

MySQL 5.6 adapter ................................................................................. 69 11.3.2.

MySQL 5.5 adapter ................................................................................. 70 11.3.3.

Oracle adapter ................................................................................................... 71 11.4.



Oracle 12c adapter ................................................................................. 71 11.4.1.

Oracle 11gR2 adapter ............................................................................. 71 11.4.2.

Oracle OCI adapter ................................................................................. 72 11.4.3.

PostgreSQL adapter ............................................................................................ 73 11.5.

SQL Server adapter ............................................................................................ 74 11.6.

SQL Server 2016 adapter ........................................................................ 74 11.6.1.

SQL Server 2014 adapter ........................................................................ 74 11.6.2.

SQL Server 2012 JDBC adapter ................................................................ 75 11.6.3.

SQL Server 2008 R2 JDBC adapter ........................................................... 75 11.6.4.

SQL Server 2008 JDBC adapter ................................................................ 76 11.6.5.

SQL Server 2008 ODBC adapter ............................................................... 77 11.6.6.

JDBC adapter ..................................................................................................... 78 11.7.

ODBC adapter .................................................................................................... 78 11.8.

NeoCore adapter ................................................................................................ 79 11.9.

NeoCore 3.1 adapter ............................................................................... 79 11.9.1.

NeoCore 3.0 adapter ............................................................................... 79 11.9.2.

NeoCore 2.9 adapter ............................................................................... 80 11.9.3.

Shunsaku adapter ............................................................................................. 81 11.10.

Shunsaku 7.0 adapter ............................................................................. 81 11.10.1.

DataSpider BPM adapter .................................................................................... 82 11.11.

Dr.Sum EA adapter ........................................................................................... 82 11.12.

IBM Domino adapter ......................................................................................... 83 11.13.

IBM Domino 9.0 adapter ......................................................................... 83 11.13.1.

Lotus Domino 8.5 adapter ....................................................................... 83 11.13.2.

IBM Notes adapter ............................................................................................ 85 11.14.



IBM Notes 9.0 adapter and Lotus Notes 8.5 adapter ................................... 85 11.14.1.

SAP adapter ..................................................................................................... 86 11.15.

SAP BC adapter ................................................................................................ 86 11.16.

Sedue adapter .................................................................................................. 86 11.17.

Universal Connect/X adapter .............................................................................. 86 11.18.

Report Director Enterprise adapter ...................................................................... 86 11.19.

List Creator adapter .......................................................................................... 87 11.20.

List Creator V9.1 adapter......................................................................... 87 11.20.1.

Xuras inicio adapter .......................................................................................... 89 11.21.

Xuras inicio 1.7 adapter ........................................................................... 89 11.21.1.

Xuras inicio 1.5 adapter ........................................................................... 90 11.21.2.

Mainframe adapter ............................................................................................ 91 11.22.

FTP adapter ..................................................................................................... 91 11.23.

JMS adapter ..................................................................................................... 91 11.24.

REST adapter ................................................................................................... 91 11.25.

Web adapter .................................................................................................... 91 11.26.

Web Services adapter ........................................................................................ 92 11.27.

Mail adapter ..................................................................................................... 92 11.28.

Active Directory adapter .................................................................................... 92 11.29.

Amazon Web Services adapter ........................................................................... 93 11.30.

Amazon DynamoDB adapter .................................................................... 93 11.30.1.

Amazon EC2 adapter ............................................................................... 93 11.30.2.

Amazon RDS for MySQL 5.7 adapter ......................................................... 93 11.30.3.

Amazon RDS for MySQL 5.6 adapter ......................................................... 93 11.30.4.

Amazon RDS for Oracle 12c adapter ......................................................... 94 11.30.5.



Amazon RDS for Oracle 11g R2 adapter .................................................... 94 11.30.6.

Amazon RDS for PostgreSQL 9.5 / 9.4 / 9.3 adapter ................................... 95 11.30.7.

Amazon RDS for SQL Server 2014 adapter ................................................ 95 11.30.8.

Amazon RDS for SQL Server 2012 adapter ................................................ 96 11.30.9.

Amazon Redshift adapter ........................................................................ 96 11.30.10.

Amazon S3 adapter ................................................................................ 96 11.30.11.

Amazon SimpleDB adapter ...................................................................... 96 11.30.12.

Amazon SQS adapter ............................................................................. 96 11.30.13.

Cloudn adapter ................................................................................................. 96 11.31.

Google Apps adapter ......................................................................................... 97 11.32.

Gmail adapter ........................................................................................ 97 11.32.1.

Google Drive Adapter .............................................................................. 97 11.32.2.

Google Sheets Adapter ............................................................................ 97 11.32.3.

kintone adapter ................................................................................................ 97 11.33.

Microsoft Azure adapter ..................................................................................... 98 11.34.

Azure SQL Database Adapter ................................................................... 98 11.34.1.

Azure Storage BLOB Adapter .................................................................... 98 11.34.2.

Nifty Cloud Adapter ........................................................................................... 98 11.35.

Nifty Cloud Adapter ................................................................................. 98 11.35.1.

Nifty Cloud Storage Adapter ..................................................................... 98 11.35.2.

Log Manager for Salesforce adapter .................................................................... 99 11.36.

Salesforce adapter ............................................................................................ 99 11.37.

Salesforce adapter .................................................................................. 99 11.37.1.

Salesforce Bulk adapter ........................................................................... 99 11.37.2.

Salesforce Metadata adapter .................................................................... 99 11.37.3.



Hadoop HDFS adapter ......................................................................................100 11.38.

HULFT adapter ................................................................................................100 11.39.

HULFT8 / HULFT7 Adapter......................................................................100 11.39.1.

12. About the port used by DataSpider Servista ............................................................101

13. Start and Shutdown of DataSpiderServer ................................................................102

Start DataSpiderServer ......................................................................................102 13.1.

Restart DataSpiderServer ...................................................................................103 13.2.

Stop DataSpiderServer .......................................................................................103 13.3.

14. Start and Exit of DataSpider Studio ........................................................................104

Start DataSpider Studio ......................................................................................104 14.1.

Login ....................................................................................................104 14.1.1.

Edit Server List ......................................................................................104 14.1.2.

When Failed to Connect to Server ............................................................105 14.1.3.

Exit DataSpider Studio .......................................................................................105 14.2.

15. Start DataSpider Servista Help ...............................................................................106

16. Service Development ............................................................................................107

17. Specifications and Limitations at Uninstallation ........................................................108

General ............................................................................................................108 17.1.

18. Uninstall DataSpider Servista .................................................................................109

Start Uninstaller ................................................................................................109 18.1.

Start Uninstall ...................................................................................................109 18.2.

Uninstall Completed ...........................................................................................110 18.3.

19. Troubleshooting ...................................................................................................111

DataSpiderServer cannot be started ....................................................................111 19.1.

The "License file could not be found" error occurs and DataSpiderServer cannot 19.1.1.



be started 111

When restarting DataSpiderServer, "LifecycleException: Protocol handler 19.1.2.

initialization failed" error occurs and it fails to restart ..................................................112

DataSpider Studio cannot be connected ...............................................................113 19.2.

DataSpider Studio cannot be connected to DataSpiderServer (1) .................113 19.2.1.



Junk character in installer ...................................................................................115 19.3.

It takes long time to open My Project ...................................................................116 19.4.

My project takes too long to start up in DataSpider Studio (1) ....................116 19.4.1.

My project takes too long to start up in DataSpider Studio (2) ....................116 19.4.2.



1. Before Use

This document describes how to install and setup the new version of DataSpider Servista 4.1.

Refer “DataSpider Servista Upgrade Guide” for the upgrade from the existing version.



Precautions 1.1.

Copyright Notice 1.1.1.

The copyright of this software is owned by Appresso K.K. or its licensors.

Unauthorized copy, reprinting of this software and this manual is prohibited.

While preparing this manual every effort has been taken to ensure its correctness but in case

of any mistakes, mismatch, and suggestions please contact us.

Please use this software by user's responsibility. As a result, with regard to any trouble and the

lawsuit, etc. occurs by any chance, damage or loss caused directly or indirectly, our company

doesn’t at all assume any responsibilities. This is for your information beforehand.

The contents described in this manual and software specifications are subject to change for

betterment, without prior notification.

The software licensing agreement is necessary for the use of this software, which includes

trade secrets and proprietary information critical to Appresso K.K. or its licensors, and it is

protected by the Copyright Law of the Japanese national administration. The unauthorized use

of Appresso K.K. or the licenser's software and this manual is subject to compensation and

criminal proceedings.

Trademarks 1.1.2.

APPRESSO, APPRESSO logo, DataSpider, DataSpider mark, Servista, Servista logo, and

Appresso are trademarks or registered trademarks of Appresso Corporation.

Additionally, company name, brand name and service name described in this manual are

registered trademarks of each company.

The duplication or diversion of information, such as trademarks, shown on the pages of this

document is strictly prohibited.



About the mark of this document 1.2.

The rules of the notations in this document are as follows.

Menu name, tab name, property item name, value, and button name displayed on screen are

enclosed with [] and in bold letters. Moreover, the one without title of screens and other

function names are enclosed with "" and distinguished from the former.

“$DATASPIDER_HOME” shows the directory where DataSpider Servista is installed. In default,

it is "C:\Program Files\DataSpiderServista" for Windows version and

"<HOME>/DataSpiderServista" for UNIX/Linux version.

“x86 version” means 32bit OS.

“x64 version” means 64bit OS of 64bit CPU (Intel 64/AMD64).

Name enclosed with < > is variable value.

Example: $DATASPIDER_HOME/server/logs/<Date directory>

URLs of the Web sites shown in this document are as of April, 2017, and are subject to change

without notice due to reasons of the Web site.

“Studio" means "DataSpider Studio", and "Studio for Web" means "DataSpider Studio for

Web".

The descriptions of the Windows and UNIX/Linux versions of DataSpiderServer have been

standardized.

Please replace descriptions of operating system dependent items (such as path delimiter

characters) as necessary.

The numbers beginning with "DSS -" are unique IDs for controlling each corresponding

problem.



About the Icons Used in This Guide 1.3.

This Guide uses the following icons in its explanation.

Icon Description

Indicates that there are hints about operations or configurations.

Indicates that there are warnings about operations or configurations.

Indicates that there are detailed descriptions in other resources.



2. About end of sales and support

As on 2018/2/2, the sales and support for the following Operating systems, databases for

Repository DB, and Adapters have ended. Note it during DataSpider Servista installation.

Refer to https://www.appresso.com/servista/eol/ for recent information.

Supported OS 2.1.

OS End of support

Red Hat Enterprise Linux 2.1 2009/12/29

Solaris 8 2009/12/29

Windows 2000 2010/7/31

Red Hat Enterprise Linux 3 2012/1/31

AIX 5L V5.3 2013/10/31

Windows XP 2014/5/31

Windows Server 2003 2015/7/31

Windows Server 2003 R2 2015/7/31

Windows 8 2016/8/31

Red Hat Enterprise Linux 4 2017/3/31

Windows Vista 2017/4/30

CentOS 5 2017/4/30

https://www.appresso.com/servista/eol/



Repository DB 2.2.

Repository DB Version End of Support

DB2 UDB V7.2 2010/7/31

UDB V8.2 2012/1/31

V9.1 2013/7/31

V9.5 2015/4/30

V9.7 2017/9/30

V10.1 2017/9/30

MySQL 5.0 2012/1/31

5.1 2015/10/31

Oracle 8.1.7 2010/7/31

9.0.1 2010/7/31

9.2.0 2012/1/31

10g R1 2013/5/31

10g R2 2013/7/31

11g 2015/10/31

PostgreSQL 8.0 2010/7/31

8.1 2012/1/31

8.2 2013/7/31

8.3 2013/5/31

8.4 2014/7/31



Repository DB Version End of Support


9.1 2016/10/31

9.2 2017/9/30

SQL Server 2000 2013/5/31

2005 2016/4/30

MySQL on Amazon RDS 5.1 2016/8/31



Adapter 2.3.

Adapter Version End of Support

Access 2000 2012/1/31

2002 2012/1/31

2003 2014/5/31

DB2 UDB V7.2 2009/12/29

UDB V8.2 2012/1/31

V9.1 2013/7/31

V9.5 2015/4/30

V9.7 2017/9/30

V10.1 2017/9/30

DB2 for i 5.1 2009/12/29

5.2 2010/7/31

5.3 2012/1/31

5.4 2013/10/31

6.1 2016/2/29

MySQL 5.0 2012/1/31

5.1 2015/10/31

Oracle 8.1.6 2010/7/31

8.1.7 2012/1/31

9.0.1 2012/1/31

9.2.0 2012/1/31




Oracle 10g R1 2012/6/30

10g R2 2013/7/31

11g 2015/10/31


8.1 2012/1/31

8.2 2013/7/31

8.3 2013/5/31

8.4 2014/7/31

9.0 2015/9/30

9.1 2016/10/31

9.2 2017/9/30

SQL Server 2000 2013/5/31

2005 2016/4/30

Amazon RDS for MySQL 5.1 2016/8/31

Excel 97 2009/12/29

2000 2012/1/31

XP 2012/1/31

2003 2014/5/31

2007 2017/10/31

Calc 2015/12/31

Dr.Sum EA 2.2 a 2009/12/29




Dr.Sum EA 2.4 2012/1/31

2.5 2013/10/31

IBM Domino 5.0 2010/7/31

6.0 2012/1/31

6.5 2012/1/31

7.0 2012/1/31

8.0 2015/5/31

IBM Notes 4.6 2012/1/31

5.0 2012/1/31

6.0 2012/1/31

6.5 2012/1/31

7.0 2012/1/31

8.0 2015/5/31

Universal Connect/X 5.3 2015/7/31

Active Directory 2000 2012/1/31

2003 2015/7/31

SAP 3.1H～4.7 2016/12/31

SAP BC 4.6 2016/10/31

BIGLOBE Cloud Hosting 2016/3/31



3. About DataSpider Servista

DataSpider Servista is a data linkage middleware that allows you to create processes for

transferring data between different kinds of systems or applications easily with a GUI base, which

are normally done by developing programs or by manually inputting or transferring the data.

This middleware expresses the linkages with various data sources as batches of transactions, and

describes the entire operation graphically by tying these batches with flows. You can publish a flow

of a series of processes as a service and run it from tools such as Trigger.

DataSpider Servista provides not only data linkage functions but also development assisting

functions for users or groups, and management functions such as log output and various triggers.

Composition of DataSpider Servista 3.1.

DataSpider Servista consists of the following application.

Name Description

DataSpider Studio Studio is an integrated development environment designed to maximize

developer productivity and to simplify service deployment and

administrative tasks.

DataSpiderServer Service execution environment.

ScriptRunner Application interface for the external invocation of service.

CLI Console Command line and web accessible server management console.

The following applications can be used on web browser after DataSpiderServer is installed.

Name Description

DataSpider Studio for

Web

Studio for Web is an integrated development environment for the design,

operation, and management of services on web browser.

WebConsole WebConsole is a tool for the operation and management of services on

web browser.

Browser Help Browser Help



4. OS supporting DataSpider Servista

Server and Client for Execution 4.1.

Following OS of both Japanese and English version are supported. For more details, refer to

“Language in Support Platform”.

Windows

Microsoft Windows Server 2008 Standard/Enterprise/Datacenter SP2 (x86 version, x64

version) (*1)

Microsoft Windows Server 2008 R2 Standard/Enterprise/Datacenter SP1 (x64 version)

(*1)

Microsoft Windows Server 2012 Essentials/Standard/Datacenter (x64 version) (*2)

Microsoft Windows Server 2012 R2 Essentials/Standard/Datacenter (x64 version) (*2)


(*1) Supports only when the Windows Server installation option is fully installed.

(*2) Supports full installation, minimum server interface, and Server Core.

(*3) Supports Server Core and Server with Desktop Experience.

UNIX/Linux

Red Hat Enterprise Linux Server 5.5+ (x86 version, x64 version)

Red Hat Enterprise Linux Server 6.x (x86 version, x64 version)

Red Hat Enterprise Linux Server 7.x (x64 version)

CentOS 6.x (x86 version, x64 version)

CentOS 7.x (x64 version)

Oracle Linux 6.x (x86 version, x64 version) (*4)

Oracle Linux 7.x (x64 version) (*4)

(*4) Kernel supports "Unbreakable Enterprise Kernel."



Client for Development 4.2.

Following OS of both Japanese and English version are supported. For more details, refer to

“Language in Support Platform”.

Windows

Microsoft Windows Server 2008 Standard/Enterprise/Datacenter SP2 (x86 version, x64

version) (*1)

Microsoft Windows Server 2008 R2 Standard/Enterprise/Datacenter SP1 (x64 version)

(*1)


Microsoft Windows Server 2012 R2 Essentials/Standard/Datacenter (x64 version) (*2)


Microsoft Windows 7 Professional/Enterprise/Ultimate SP1 (x86 version, x64 version)

Microsoft Windows 8.1 Pro/Enterprise (x86 version, x64 version)

Microsoft Windows 10 Pro/Enterprise (x86 version, x64 version)

(*1) Supports only when the Windows Server installation option is fully installed.

(*2) Supports full installation, minimum server interface, and Server Core.

(*3) Supports Server Core and Server with Desktop Experience.

Refer to “DataSpider Studio for Web” page of help for the supported OS of DataSpider

Studio for Web.



Language in Support Platform 4.3.

The language in support platform varies by existence of language setting of DataSpider Servista.

Set the language with platform which is subject to support.

platform which is subject to support

OS of Japanese

version

OS of English

version

The state is ”possible to

show Japanese” in OS of

English version

Language in

DataSpider

Servista

Japanese ○ × ○

English ○ ○ ○

“○” means “supported” and “×” means ”not supported” in above table.

”possible to show Japanese” means environment to which language packs (Multilingual User

Interface Pack) is applied and user interface is changed into Japanese for Windows. For Linux, it

means environment in which OS can show Japanese and language setting of DataSpider Servista

User is Japanese.

When "English" is set for DataSpider Servista language, to use Japanese at configurable /

inputtable fields on DataSpider Servista, the DataSpider Servista operating OS should be "OS of

Japanese version" or "The state is” possible to show Japanese” in OS of English version".



About Windows language packs (Multilingual User 4.3.1.

Interface Pack)

Environment with Japanese user interface is supported to use DataSpider Servista in Japanese in

an environment for which Windows language pack (Multilingual User Interface Pack) is applied.

" Environment with Japanese user interface " indicates the environment with the following settings.

(In the case of Windows Server 2012 R2)

In "All Control Panel Items" – "Region” of Windows

Select "Japanese(Japan)" in “Format” of "Formats" tab

Select “Japan in “Home location” of "Location" tab

Select "Japanese (Japan) " in "Administrative" – "Current language for non-Unicode

programs"

In "All Control Panel Items" – "Language" of Windows

Select “Japanese(Japan)” in "Advanced settings" – "Override for Windows display

language"

To register DataSpiderServer in Windows services, the user setting that starts the

service should be in Japanese.



Specification Limits / Precautions 4.4.

Specification Limits / Precautions for language settings 4.4.1.

In DataSpider Servista 4.1, language can be set in server and client respectively. In that case,

following specification limits and precautions exist when “English” is set for server language and

when different languages are selected between the server and the client.

When “English” is set for server language

Mainframe adapter is not available. (DSS-23066)

Active Directory adapter is not available. (DSS-22585)

WebConsole is not available. (DSS-14415)

Help pages of following adapters are not able to open. (DSS-23034)

NeoCore、Shunsaku、Sedue、ListCreator、Xuras inicio、Mainframe

Following help pages do not exist. (DSS-23067)

Reverse lookup reference, SAP adapter tutorial

When different languages are set between server and client

When the language is “English” in server and “Japanese” in client

Part of XML log is output in Japanese. (DSS-22573)

Part of error message might be output in English. (DSS-22811、DSS-22515)

When the language is “Japanese” in server and “English” in client

Part of XML log is output in English. (DSS-22573)

Part of error message might be output in Japanese. (DSS-22811、DSS-22515)



Restriction for timezone in platform 4.4.2.

Timezone in server and client are different, the timezone in client is required to be synchronized

with the timezone in server.

( Usually, timezone is gotten from operating OS, but if user.timezone of system.properties is set,

the setting is prior.)

To see the server timezone, select “system properties” in “All” tab of “control panel” –

“DataSpider Studio Setting” on DataSpider Studio, then check the value of “user.timezone”.

Setting way of timezone for client is as follows.

1. Stop each application in DataSpider Servista.

2. Open system.properties in text editor under $DATASPIDER_HOME/client/conf.

3. Delete “#” in “#user.timezone=Asia/Tokyo” and specify timezone of DataSpiderServer

operating OS after “=” and save it.

4. Start DataSpiderServer and DataSpider Studio.

For more details of user.timezone properties, refer to page “Property reference” in help of

DataSpider Servista.

In the case of Studio for Web, timezone setting of Studio for Web operating OS is required to

be set to the same setting as the timezone of DataSpiderServer operating OS.



Supported virtualization system 4.5.

Virtualization system that DataSpider Servista supports is as follows.

VMware

Citrix XenServer

Hyper-V

Kernel-based Virtual Machine

DataSpider Servista supports guest OS on virtualization system which is described in “Supported

OS” in this document.

Guest OS should be supported by virtualization system.



5. System requirements

System requirements is the minimum configuration which allows DataSpider Servista to operate.

The optimal configuration varies depending on number and contents of operations, number of

concurrent processings, size of data to be handled, and so on. Determine your configuration in

accordance with requirements and operations of the service to be developed.

Both Server and Client 5.1.

Monitor: 17 inch or more

Color: 24 bit color

Resolution: 1024x768 pixels or more

Refer to “DataSpider Studio for Web” page of help for the system requirements of DataSpider

Studio for Web.

Server 5.2.

The described system requirements are product independent.

Windows x86 version/Linux x86 version

CPU: processor that meets system requirement that OS recommends

Memory: 512MB or more

HDD: Free space of 2GB or more


CPU: Processor that meets 64bit(x64) system requirement that OS recommends

Memory: 2GB or more




Client for development 5.3.


Windows x86 version

CPU: Processor that meets system requirement that OS recommends



Windows x64 version




Client for Execution 5.4.



CPU: Processor that meets system requirement that OS recommends


HDD: Free space of 500MB or more




HDD: Free space of 500MB or more



6. About Java Runtime Environment

Since Java Runtime Environment (JRE) is bundled in each installer of DataSpider Servista 4.1, no

need to install JRE.

And, JRE version bundled in each installer is as given below.

Windows version, Linux version

1.8.0_121

To operate JRE on each platform, the patch to the operating system might be necessary. Refer to

operating system for details.



7. Repository DB settings

What is a Repository DB? 7.1.

A Repository DB is a system which manages services, user information, and various setting data in

the repository area configured in a RDB (relational data base). Until a Repository DB is set up, you

cannot use the user management system or the file access control functions.

However, DataSpider Servista can be installed even if a Repository DB has not been set up.

Depending on your development requirements, determine whether you should set up a Repository

DB or not.

Repository DB settings 7.1.1.

Repository DB is set up during installation. You can modify the settings through the Control Panel.

Refer to this document for the settings during installation, and refer to the [Repository DB

Management] page of Help for the settings after installation.

Repository DB specification restrictions and precautions

Set up one Repository DB per DataSpiderServer. More than one DataSpiderServer

cannot be connected to the same Repository DB.

The database instances should be used only for Repository DB and not for any other

system.

The database instances specified for Repository DB should have an encoding system

allowing multibyte characters. For example, a database instance encoded with US-ASCII

cannot be used as a Repository DB.

Creating a Repository DB 7.1.2.

Repository DB create a dedicated table in which the repository area is configured, and save data

into it. This table is created during startup of DataSpiderServer. If a dedicated table already exists,

a new table is not created and the existing table is used.



Operation with / without a Repository DB 7.1.3.

Operation with or without a Repository DB is as follows.

If using a Repository DB (If a repository exists)

You can create multiple user groups and control their access privileges.

You can hold Meta information of various files in the repository.

You can save various settings in the repository.

If not using a Repository DB (If a Repository DB does not exist)

You can use only one type of user group.

The Meta information of various files and various settings are held in the file system of

the OS.



Databases supported as Repository DB 7.2.

DataSpider Servista supports the following databases as Repository DB.

DB2 for Linux, UNIX, and Windows

Supported versions: V11.1 / V10.5

MySQL

Supported versions: 5.7 / 5.6 / 5.5

Oracle Database

Supported versions: Oracle Database Cloud Service(Oracle Database 12c Release

2(12.2)) /12c Release 2 /12c / 11g Release 2

PostgreSQL

Supported versions: 10 / 9.6 / 9.5 / 9.4 / 9.3

Microsoft SQL Server

Supported versions: 2017 / 2016 / 2014 / 2012 / 2008 R2 / 2008

MySQL on Amazon RDS

Supported versions: 5.7 / 5.6

Oracle Database on Amazon RDS

Supported versions: 12c / 11g Release 2

PostgreSQL on Amazon RDS

Supported versions: 9.5 / 9.4 / 9.3

Microsoft SQL Server on Amazon RDS

Supported versions: 2014 / 2012

Azure SQL Database

When you use a Repository DB, ensure that one of the above databases is running before installing



DataSpider Servista.



Setting up each database 7.3.

When using DB2 for Linux, UNIX, and Windows 7.3.1.

To use DB2 for Linux, UNIX, and Windows as a Repository DB, the following information is needed.

Host name or IP address of DB2 for Linux, UNIX, and Windows

Port number used for providing services (Default port is "50000")

Name of the database

Path of the supported JDBC driver

Supported JDBC drivers

V11.1

Required library: db2jcc4.jar

Version of the driver: IBM Data Server Driver for JDBC and SQLJ (for V11.1)

V10.5

Required library: db2jcc4.jar

Version of the driver: IBM Data Server Driver for JDBC and SQLJ (for V10.5)

User settings

You should add a new user in the database and set up a DBA role for the user. Settings of the user

name and the password defined here are used when setting up the Repository DB. Before

installing DataSpider Servista, ensure that you can access it externally using these setting values.



When using MySQL 7.3.2.

To use MySQL as a Repository DB, the following information is needed

Host name or IP address of MySQL



Path of the supported JDBC drive

Supported JDBC driver

5.7

Required library: mysql-connector-java-5.1.<version>-bin.jar

Version of the driver: MySQL Connector/J 5.1.<version>

5.6



5.5



<version> indicates the latest version.

User settings




Specification restrictions / Precautions

”1” should be configured as default [lower_case_table_names] of the database.

"utf8" should be configured as the [default-character-server] for the database.



When using Oracle Database 7.3.3.

To use Oracle Database as a Repository DB, the following information is needed.

Host name or IP address of Oracle Database


System identifier (SID)



12c Release 2

Required library: ojdbc8.jar

Version of the driver: Oracle JDBC Driver 12.2.0

12c



11g Release 2



User settings






When using PostgreSQL 7.3.4.

To use PostgreSQL as a Repository DB, the following information is needed.

Host name or IP address of PostgreSQL





10

Required library: postgresql-42.<version>.jar

Version of the driver: PostgreSQL JDBC 4.2 (<version>)

9.6

Required library: postgresql-9.4-<version>.jar

Version of the driver: PostgreSQL 9.4 JDBC4.2 (build <version>)

9.5



9.4

Required library: postgresql-9.4-<version>.jdbc41.jar


9.3






User settings




When using Microsoft SQL Server 7.3.5.

To use Microsoft SQL Server as a Repository DB, the following information is needed.

Host name or IP address of SQL Server





2017

Required library: mssql-jdbc-6.2.2.jre8.jar

Version of the driver: Microsoft JDBC Driver 6.2 for SQL Server

2016

Required library: sqljdbc42.jar


2014



2012



2008 R2





2008



User settings

You should add a new user in the database and set the db_owner role for the user. Settings of the

user name and the password defined here are used during setting up the Repository DB. Before


Specification restrictions/Precautions

The collating sequence in the database should be configured to be not

casesensitive.

Connecting using Windows Integrated Authentication is impossible.



When using MySQL on Amazon RDS 7.3.6.

To use MySQL on Amazon RDS as a Repository DB, the following information is needed.

Host name of MySQL on Amazon RDS

Port number used for providing services (Default port is “3306”)




5.7



5.6




User settings





”1” should be configured as default [lower_case_table_names] of the database

"utf8" should be configured as the [default-character-server] for the database.



When using Oracle Database on Amazon RDS 7.3.7.

To use Oracle Database on Amazon RDS as a Repository DB, the following information is needed.

Host name of Oracle Database on Amazon RDS

Port number used for providing services (Default port is “1521”)

System identifier (SID)



12c



11g Release 2



User settings


name and the password defined here are used during setting up the Repository DB. Before




When using PostgreSQL on Amazon RDS 7.3.8.

To use PostgreSQL on Amazon RDS as a Repository DB, the following information is needed.

Host name of PostgreSQL on Amazon RDS





9.5



9.4



9.3




User settings






When using Microsoft SQL Server on Amazon RDS 7.3.9.

To use Microsoft SQL Server on Amazon RDS as a Repository DB, the following information is

needed.

Host name of Microsoft SQL Server on Amazon RDS





2014



2012



User settings

You should add a new user in the database and set up a db_owner role for the user. Settings of the

user name and the password defined here are used when setting up the Repository DB. Before




casesensitive.

Connecting using Windows Integrated Authentication is impossible.



When using Azure SQL Database 7.3.10.

To use Azure SQL Database as a Repository DB, the following information is needed.

Host name of Azure SQL Database




Supported JDBC driver

Azure SQL Database



User settings

You should add a new user in the database and set up a db_owner role for the user. Settings of the

user name and the password defined here are used when setting up the Repository DB. Before




casesensitive.



When using Oracle Database Cloud Service(Oracle 7.3.11.

Database 12c Release 2(12.2))

To use Oracle Database Cloud Service(Oracle Database 12c Release 2(12.2)) as a Repository DB,

the following information is needed.

Host name or IP address of Oracle Database Cloud Service(Oracle Database 12c Release

2(12.2))


Service name



Oracle Database Cloud Service(Oracle Database 12c Release 2(12.2))



User settings





When using Oracle Database Cloud Service(Oracle Database 12c Release 2(12.2)),

the service name cannot be set in the installer. Configure the setting by the following

procedure.

1. Select "Do not use repository" in the installer and perform the installation.

2. Start DataSpider Studio.

3. Directly specify the URL in [Repository DB Management] in the Control Panel.



8. Specifications and Limitations at Installation

General 8.1.

You cannot install multiple DataSpider Servista of different versions on the same platform.

You cannot install multiple DataSpider Servista of the same version on the same platform.

However, exclude the following cases.

It is possible to install a server and a client of the same version independently (select

[Client only] or [Server only] on the [Select Component] screen). However, the

limitations are given below.

The uninstaller should be run by selecting

$DATASPIDER_HOME/Uninstall/Uninstall.exe.

When you uninstall them, be sure to uninstall all servers and clients installed on the

same platform

It is possible to install multiple clients for same version of DataSpider Servista

development in the same platform. However, the limitations are given below.

Run the exe file under $DATASPIDER_HOME/client/bin for each client application.

The uninstaller should be run by selecting

DATASPIDER_HOME/Uninstall/Uninstall.exe

When you uninstall them, be sure to uninstall all servers and clients installed on the

same platform.

Language of DataSpiderServer is set when installing. It is not able to change after installation.

(DSS-22577)



For Windows version, install them as an administrator user.

When installed as the user without administrator rights, it is not registered as the

application in Windows [Add or Remove Programs]. (DSS-6271)

After installing, when the general user starts the DataSpider, assign the general user

rights for all the directories under the installation directory. (DSS-7217)

For Linux version, to start the installer, start X Window System on Linux.

Installer 8.2.

For all installer screens, input field cannot be scrolled sideways. (DSS-896)

Select Component 8.3.

When you select [Client only] or [Server only] on the [Select Component] screen and install

them, the value may not be reflected in the URL of [DataSpider Studio for Web] [WebConsole]

[Help] menu of Windows start menu. (DSS-11359)

Configure the proper URL through the properties on the [DataSpider Studio for Web] -

[WebConsole] - [Help] menu of Windows start menu.

Select Repository DB 8.4.

On "Select JDBC driver" screen of installer, if you press [Choose] button and Specify long path,

[Restore Default] button and [Choose] button might disappear. (DSS-1539)

On "Select JDBC driver" screen of installer, if JDBC driver path contains “#” or “%”,

DataSpiderServer is unable to load the driver at starting. (DSS-4635)

Don’t use “#” and “%” for JDBC driver path.



Register Windows Service 8.5.

If DataSpiderServer is registered as Windows service by the user account of following

conditions, the service of DataSpiderServer is not displayed in Windows service list.

(DSS-1356)

The user is not belonging to Administrators group.

The user doesn’t have full control permission of C: drive.

When registering DataSpiderServer in Windows Service name, multi byte characters are not

allowed in the Windows Service name of the DataSpiderServer. (DSS-11335)

Installation Directory Settings 8.6.

Following characters are not available for install directory. (DSS-22963、DSS-12834、

DSS-9044, DSS-8718)

multi byte

equals sign、percent sign, single byte space

In UNIX/Linux version, after installing as root user, the user and group belonging to

$DATASPIDER_HOME/jre directory are displayed as “500”. (DSS-7952)

Installation Complete 8.7.

Folder name (DataSpider Servista installation directory) cannot be changed after

installation.(DSS-7463)



9. Notes concerning Windows

If you install DataSpider Servista on Windows OS, read the following notes.

Notes when Installing DataSpider Servista 9.1.

If you install DataSpider Servista in C drive (installation drive of Windows OS), the following

issues may occur.

DataSpiderServer: When starting as unauthorized user, if you don't start

DataSpiderServer by "Run as administrator", DataSpiderServer might not be restarted

from DataSpider Studio and command prompt.

DataSpider Studio: When starting as unauthorized user, if you don't start DataSpider

Studio by "Run as administrator", it might be unable to connect with DataSpiderServer.

If you install DataSpider Servista in D drive in which Windows OS is not installed, the following

issues may occur.

DataSpiderServer: When starting as unauthorized user, if you don't start

DataSpiderServer by "Run as administrator", DataSpiderServer might not be restarted

from DataSpider Studio and command prompt.

Above-mentioned "Unauthorized user" refers to users other than built-in Administrator

account when UAC is valid and when UAC is invalid, it refers to the general user.



10. Installation of DataSpider Servista

Start Installation 10.1.

Execute an arbitrary installer file, and start installer.

File name and Supported OS of Each Installer 10.1.1.

File name and Supported OS of each installer is as given below.

File Name Supported OS

DSS41_LNX_X64.bin Linux x64 version

DSS41_LNX_X86.bin Linux x86 version

DSS41_WIN_X64.exe Windows x64 version

DSS41_WIN_X86.exe Windows x86 version

Installer contains both DataSpiderServer module and DataSpiderClient module. Select Server

or Client (or both) in the installation process when you install.

When installing in Windows Server 2008 x64, be sure to use the dedicated installer

“DSS41_WIN2K8_X64.exe” placed under the “InstallerForWindowsServer2008x64” directory.



Description of each screen of Installer 10.2.

Start Installer 10.2.1.

First of all, when installer is started, the introduction screen will be displayed automatically.

Select Language 10.2.2.

Select a language.

DataSpiderServer and Server CLI Console start in selected language. The language is not able

to be changed after installation.

Client (DataSpider Studio, DataSpider Studio for Web, Client CLI Console) execute first boot in

selected language. The language is able to be changed after.

Introduction Screen 10.2.3.

In the introduction screen, read through the displayed content, then press [Next] button.

Select Package 10.2.4.

Select the package you purchased and press [Next] button.

Available packages are as follows.

[Advanced Server Package]

[Basic Server Package]

[Select]

There is no difference in product configurations between these packages but the

terms and conditions of their contracts are different. Be sure to select the correct one you

purchased.

Software License Agreement 10.2.5.

Installation and use of DataSpiderServer requires displayed software license agreement. Read

carefully content of the agreement, select [I agree to the provisions of the License Agreement] and

press [Next] button.



Select Component 10.2.6.

Select component to install and Press [Next] button.

Available components are as follows.

[Server and Client]

Applications to be installed

DataSpider Studio for Web, DataSpiderServer, Help Document, ScriptRunner,

Server CLI Console, WebConsole

Client( It depends on the settings on the [Select Client Environment] screen)

[Server only]


DataSpider Studio for Web, DataSpiderServer, Help Document, ScriptRunner,

Server CLI Console, WebConsole

[Client only]


Client ( It depends on the settings on the [Select Client Environment] screen).

The server and the client are supported by different platforms.

For more details, refer to“ OS supporting DataSpider Servista”.

To install a server and a client on the same platform, select [Server and Client].

When you have independently installed a server and a client of the same version, and if

you uninstall one of them, all Windows menus will be deleted.



Select Client Environment 10.2.7.

Select installed client environment, and press [Next] button.

It is displayed when you select [Server and Client] or [Client only] on the [Select

Component] screen.

Available client environments are as follows.

[Client for development]


DataSpider Studio, Client ScriptRunner, and Client CLI Console

WebConsole, DataSpider Studio for Web, and Help

[Client for execution]


Client ScriptRunner, Client CLI Console

WebConsole, DataSpider Studio for Web, and Help

Client for development cannot be installed in UNIX/ Linux environment.

When UNIX/Linux version is purchased, install in a separate Windows environment. Use the

installer with "exe" extension for installing development client.

Administrator Password Settings 10.2.8.

Enter password of administrator (root user) that manages DataSpiderServer and press [Next]

button.

This setting is available only when you select [Server and Client] or [Server only] at [Select

Component] screen.

If empty, sets “password”.

After installation, you can change administrator's password from "User account" of Control

Panel of DataSpider Studio and WebConsole.



Repository Database Settings 10.2.9.

Select whether to use Repository DB and press [Next] button.


Component] screen.

[Use Repository DB]: It builds a DataSpider filesystem on the database.

[Do not use Repository DB]: It builds a DataSpider filesystem on the file system of the OS

where DataSpiderServer is running.

If you select [Do not use Repository DB], it is not necessary to make the settings described

in the next "Select Database Product" section and the following sections. Please refer to the

"Register Windows Service" section.

If you use Oracle Database Cloud Service(Oracle Database 12c Release 2(12.2)) in

repository DB, you can not configure it with installer. Select [Do not use repository] and

configure the settings after installation. For details, refer to "When using Oracle Database

Cloud Service(Oracle Database 12c Release 2(12.2)) ".

Select Database Product 10.2.10.

Select database products to use as Repository DB, and press [Next] button.

This setting is available only when you select [Use Repository DB] at [Repository Database

Settings] screen.

Available database products are as follows.

[DB2]

Selects when DB2 for Linux, UNIX, and Windows is used in Repository DB.

[MySQL]

Selects when MySQL or MySQL on Amazon RDS is used in Repository DB.

[Oracle]

Selects when Oracle Database or Oracle Database on Amazon RDS is used in Repository

DB.



For more details, refer to“ When using Oracle Database Cloud Service”.

[PostgreSQL]

Selects when PostgreSQL or PostgreSQL on Amazon RDS is used in Repository DB.

[SQL Server]

Selects when Microsoft SQL Server, Microsoft SQL Server on Amazon RDS or Azure SQL

Database is used in Repository DB.

For DB2 10.2.11.

Refer to “Supported DB2 for Linux, UNIX, and Windows” for supported versions.

Select JDBC Driver

Specify file path of JDBC driver and press [Next] button.

Refer to “Supported JDBC drivers” for supported JDBC drivers.

Database Connection Information

Enter connection information of Database and press [Next] button.

For MySQL 10.2.12.

Refer to “Supported MySQL” or “Supported MySQL on Amazon RDS” for supported versions.

Select JDBC Driver


Refer to “MySQL supported JDBC drivers” or “MySQL on Amazon RDS supported JDBC

drivers” for supported JDBC drivers.



For Oracle 10.2.13.

Refer to “Supported Oracle Database” or “Supported Oracle Database on Amazon RDS” for



supported versions.

Select JDBC Driver


Refer to “Oracle Database Supported JDBC drivers” or “Oracle Database on Amazon RDS

Supported JDBC drivers” for supported JDBC drivers.



For PostgreSQL 10.2.14.

Refer to “Supported PostgreSQL” or “Supported PostgreSQL on Amazon RDS” for supported

versions.

Select JDBC Driver


Refer to “PostgreSQL Supported JDBC drivers” or “PostgreSQL on Amazon RDS Supported

JDBC drivers” for supported JDBC drivers.



For SQL Server 10.2.15.

Refer to “Supported Microsoft SQL Server”, “Supported Server SQL on Amazon RDS” or

“Supported Azure SQL Database” for supported versions.

Select JDBC Driver


Refer to “Microsoft SQL Server Supported JDBC drivers”, “SQL Server on Amazon RDS

Supported JDBC drivers” or “Azure SQL Database Supported JDBC driver” for supported JDBC

drivers.





Register Windows Service 10.2.16.

Select whether to register DataSpiderServer as Windows service and press [Next] button.

This screen will not be displayed in UNIX/Linux version installer.


Component] screen.

After inserting check in [Register the Server in Windows Service], if you omit the

service name, it is not registered in Windows Service.

Precautions when you register a DataSpiderServer with a Repository DB on a

Windows service

If both the DataSpiderServer with a Repository DB and the Repository DB are started from a

Windows service, there are chances that Repository DB is not started when DataSpiderServer is

started.

In such case, you should configure the appropriate number and cycles in Test connect count of

DataSpider Studio’s Control panel [Repository DB Management] – [Reconnection Setting] tab.

DataSpider Server Settings 10.2.17.

Enter the host name and the IP address of the OS where DataSpiderServer is running and the port

number of DataSpiderServer, and then press the [Next] button.

By default, “localhost” will be set to [Host name/IP address].

By default, “7700” will be set to [Port number]

In the UNIX/Linux version, administrative rights are necessary for the numerical value below

"1023". Specify the settings other than “0” to “1023” for starting DataSpiderServer as a general

user.



Installation Directory Settings 10.2.18.

Specify installation directory of DataSpider Servista and press [Next] button.

For Windows version, default value is "C:\Program Files\DataSpiderServista" and for UNIX/Linux

version, it is installed in “<HOME>/DataSpiderServista”.

If you want to install DataSpiderServer in another directory, start directory chooser by pressing

[Choose] button and select target directory. You can restore default directory path by pressing

[Restore Default Folder] button after another directory is selected.

If DataSpider Servista already exists in the destination directory specified in [Destination

folder], a warning dialog appears. Do not overwrite the existing DataSpiderServer.

Select License File 10.2.19.

Specify file path of DataSpider Servista license (license.lic), and press [Next] button.


Component] screen.

The license file specified is copied under the directory $DATASPIDER_HOME/server/lic.

You can apply license file after installation.

Heap Size Settings 10.2.20.

Specify a heap size of DataSpiderServer and press [Next] button.


Component] screen.

The unit of megabytes is specified as “m” or “M”, and gigabytes is specified as “g” or “G”.

If you omit this setting, the following value is set.

Install target platform [Initial(bytes)] [Maximum(bytes)]

Windows x64/Linux x64

version

1G 2G

Windows x86/Linux x86 256M 512M



version

Summary of Installation 10.2.21.

The summary of installation is displayed. Confirm a displayed content of settings. Press [Install]

button and installation begins.

Installing DataSpider Servista 4.1 10.2.22.

DataSpider Servista is being installed.

Install completed 10.2.23.

When installation executed successfully, [Installation Complete] screen is displayed. Press [Done]

button and finish installation.

Setting data for DataSpiderServer and the Repository DB are written into the below location.

$DATASPIDER_HOME/server/conf/dsserver.xml

When there are mistakes in the settings of the Repository DB or you want to change the connected

Repository DB, you can modify the settings through [Repository DB management] in the

DataSpider Studio's Control Panel or through the [Setup Repository] menu in WebConsole.



Installation of License File 10.3.

If you did not copy license file “license.lic” with installer, copy the license file onto

$DATASPIDER_HOME/server/lic directory manually.

In addition, notes related to license files are as follows.

License file name

License file name should be "license.lic" or "LICENSE.LIC".

License file number

Only one license file can be placed in $DATASPIDER_HOME/server/lic directory. If it is

required to overwrite the license file such as the case of purchasing additional adapter,

save the existing license file to another directory and store the new license here.



About Windows Start Menu 10.4.

In Windows version, following start menus are created after installation.

When you select [Server and Client] in the [Select Component] screen

Client CLI Console

DataSpider Studio

DataSpider Studio for Web

DataSpiderServer

Help Document

Server CLI Console

Shutdown

Uninstall

WebConsole

When you select [Server only] in the [Select Component] screen


DataSpiderServer

Help Document

Server CLI Console

Shutdown

Uninstall

WebConsole



When you select [Client only] in the [Select Component] screen and [Client for

development] in the [Select Client Environment] screen

Client CLI Console

DataSpider Studio


Help Document

Uninstall

WebConsole

When you select [Client only] in the [Select Component] screen and [Client for execution]

in the [Select Client Environment] screen

Client CLI Console


Help Document

Uninstall

WebConsole



11. Pre-setting of Adapters

Pre-setting of installation of the library etc. might be necessary in use of each adapter.

For more details, refer to DataSpider Servista Help.

Access adapter 11.1.

11.1.1. Access 2013/2010 adapter

Library installation is not necessary in Access adapter.



DB2 adapter 11.2.

DB2 V11.1 adapter 11.2.1.

Required library

db2jcc4.jar

Supported driver version

IBM Data Server Driver for JDBC and SQLJ (for v11.1)

To get a library

If you installed DB2 at default directory, they are placed under sqllib/java directory

below DB2 installation directory.

Installation procedure

1. Stop DataSpiderServer and client applications.

2. Copy required library group under the directory

$DATASPIDER_HOME/server/plugin/data_processing/modules/db2_111_adapter.


DB2 V10.5 adapter 11.2.2.

Required library

db2jcc4.jar


IBM Data Server Driver for JDBC and SQLJ (for v10.5)

To get a library

If you installed DB2 at default directory, they are placed under sqllib/java directory

below DB2 installation directory.






$DATASPIDER_HOME/server/plugin/data_processing/modules/db2_105_adapter.




DB2 for i 7.3 / 7.2 / 7.1 adapter 11.2.3.

Required library

jt400.jar

To get a library

In default settings, it is placed under /QIBM/ProdData/HTTP/Public/jt400/lib directory.




$DATASPIDER_HOME/server/plugin/data_processing/modules/db2udb_iseries<versio

n>_adapter.

<version> indicates DB2 for the version of iSeries and will be "71" for "7.1", "72" for

7.2 and "73" for 7.3.




MySQL adapter 11.3.

The <Version> represents the latest version.

MySQL 5.7 adapter 11.3.1.

Required library

mysql-connector-java-5.1.<version>-bin.jar


MySQL Connector/J 5.1.<version>

To get a library

Download JDBC driver from MySQL Connector/J 5.1 download site.




$DATASPIDER_HOME/server/plugin/data_processing/modules/mysql57_adapter.



Required library




To get a library




http://dev.mysql.com/downloads/connector/j/5.1.html








Required library




To get a library




2. Copy required library under the directory






Oracle adapter 11.4.

Oracle 12c adapter 11.4.1.

Required library

ojdbc7.jar


Oracle JDBC Driver 12.1.0

To get a library

Download JDBC driver for version 12.1 from “JDBC Drivers” link page of Oracle

Software Downloads site.



2. Copy required library group directly under the directory

$DATASPIDER_HOME/server/plugin/data_processing/modules/oracle12c_adapter and

the directory

$DATASPIDER_HOME/server/plugin/data_processing/modules/xa_oracle12c_adapter


Oracle 11gR2 adapter 11.4.2.

Required library

ojdbc6.jar



To get a library

Download JDBC driver for version 11.2 from “JDBC Drivers” link page of Oracle

Software Downloads site.


http://www.oracle.com/technetwork/indexes/downloads/index.html







5. Copy required library group directly under the directory

$DATASPIDER_HOME/server/plugin/data_processing/modules/oracle11gr2_adapter

and the directory

$DATASPIDER_HOME/server/plugin/data_processing/modules/xa_oracle11gr2_adapte

r.


Oracle OCI adapter 11.4.3.

Required library

Oracle Database Client JDBC drivers

11g Release 2 (11.2) ojdbc6.jar


Depends on the Oracle client version used.

To get a library

Usually locatable under jdbc\lib directory within the installation directory of the client

tool.

In case of Oracle11g Release 2, it is locatable in

Oracle\product\11.2.0\Client_1\jdbc\lib\ojdbc6.jar.




$DATASPIDER_HOME/server/plugin/data_processing/modules/oracle_oci_adapter.




PostgreSQL adapter 11.5.

In PostgreSQL adapter, it is not necessary to install library.



SQL Server adapter 11.6.

SQL Server 2016 adapter 11.6.1.

Required libraries

sqljdbc42.jar

sqljdbc_auth.dll(when using Integrated Windows Authentication)


Microsoft JDBC Driver 6.0 for SQL Server

To get a library

Download Microsoft JDBC Driver 6.0 for SQL Server from Microsoft Download Center.



2. Copy sqljdbc42.jar directly under the directory

$DATASPIDER_HOME/server/plugin/data_processing/modules/sqlserver2016_adapter

3. When using Integrated Windows Authentication, copy sqljdbc_auth.dll to the directory on the

Windows system path of the computer on which JDBC driver is installed.


SQL Server 2014 adapter 11.6.2.

Required libraries

sqljdbc42.jar




To get a library


http://www.microsoft.com/en-us/download/details.aspx?id=11774








3. When using Integrated Windows Authentication, copy sqljdbc_auth.dll to the directory

on the Windows system path of the computer on which JDBC driver is installed.


SQL Server 2012 JDBC adapter 11.6.3.

Required libraries

sqljdbc42.jar




To get a library









SQL Server 2008 R2 JDBC adapter 11.6.4.

Required libraries

sqljdbc42.jar







To get a library





$DATASPIDER_HOME/server/plugin/data_processing/modules/sqlserver2008r2_adapt

er.




SQL Server 2008 JDBC adapter 11.6.5.

Required libraries

sqljdbc42.jar




To get a library





$DATASPIDER_HOME/server/plugin/data_processing/modules/sqlserver2008_adapter.








SQL Server 2008 ODBC adapter 11.6.6.

In SQL Server 2008 ODBC adapter, it is not necessary to install library.



JDBC adapter 11.7.

Required library

Inquire DBMS vendor connected with JDBC adapter.

To get a library

Inquire DBMS vendor connected with JDBC adapter.




$DATASPIDER_HOME/server/plugin/data_processing/modules/jdbc_adapter


ODBC adapter 11.8.

In ODBC adapter, it is not necessary to install library.



NeoCore adapter 11.9.

NeoCore 3.1 adapter 11.9.1.

Required library

xmsclient.jar

To get a library

If NeoCore 3.1 is installed with default settings, the corresponding library is located

under the directory C:\NeoCore\API\Java\lib.



2. Copy the required library group under the directory

$DATASPIDER_HOME/server/plugin/data_processing/modules/neocore31_adapter.



Required library

xmsclient.jar

To get a library











Required library

neoHTTPConnection.jar

To get a library










Shunsaku adapter 11.10.

Shunsaku 7.0 adapter 11.10.1.

Required libraries

shunapi.jar

xercesImpl.jar

xml-apis.jar

xmlconv.jar

f3hyshun.dll

To get a library

If Shunsaku is installed with default settings, f3hyshun.dll is located under the directory

the C:\Program Files\Interstage Shunsaku\Shunsaku\bin and other corresponding

libraries are located under the directory C:\Program Files\Interstage

Shunsaku\Shunsaku\lib.



2. Copy f3hyshun.dll under the directory C:\WINDOWS\system32.

3. Copy shunapi.jar, xercesImpl.jar, xml-apis.jar and, xmlconv.jar under the directory

$DATASPIDER_HOME/server/plugin/data_processing/modules/shunsaku70_adapter.




DataSpider BPM adapter 11.11.

In DataSpider BPM adapter, it is not necessary to install library.

Dr.Sum EA adapter 11.12.

In Dr.Sum EA adapter, it is not necessary to install library



IBM Domino adapter 11.13.

You cannot use multiple versions of Lotus Domino adapter at the same time.

IBM Domino 9.0 adapter 11.13.1.

Required libraries

NCSO.jar

Notes.jar

To get a library

If IBM Domino 9.0 is installed with default settings in Windows environment, the

corresponding library is located under the directories below.

<Installation directory of Domino>/data/domino/java/NCSO.jar

<Installation directory of Domino>/jvm/lib/ext/Notes.jar




$DATASPIDER_HOME/server/plugin/data_processing/share/lib.


Lotus Domino 8.5 adapter 11.13.2.

Required library

NCSO.jar

Notes.jar

To get a library

If Lotus Domino 8.5 is installed with default settings in Windows environment, the

corresponding library is located under the directories below.

<Installation directory of Domino>/data/domino/java/NCSO.jar



<Installation directory of Domino>/jvm/lib/ext/Notes.jar








IBM Notes adapter 11.14.

IBM Notes 9.0 adapter and Lotus Notes 8.5 adapter 11.14.1.

Required software

To use IBM Notes adapter, IBM Notes (below Notes client) must be installed on system

that DataSpiderServer running.

Setting Up System Environment Variables

Add path of Notes client installation directory on system variable "PATH" that is system

running DataSpiderServer.

Notes Port Configuration

To connect from IBM Notes adapter to Notes client, Notes port is required. If the

connection setting has been made from Notes client to Domino server, the Notes port

setting is not necessary. If Notes port does not exist, add the TCP or NETBIOS port.

The user access from IBM Notes adapter to the database of Domino server is fixed as the user

set in Notes client. Moreover, as the user's password needs to be cleared, clear the password from

Notes client.

Notes users who are configured on the client, "Password quality scale" please allow the setting

without a password.



SAP adapter 11.15.

To use SAP adapter, you need to install SAP EICS.

For more details, refer to “DataSpider Servista SAP EICS Install Guide” bundled to installer.

SAP BC adapter 11.16.

In SAP BC adapter, it is not necessary to install library.

Sedue adapter 11.17.

In Sedue adapter, it is not necessary to install library.

Universal Connect/X adapter 11.18.

In Sedue adapter, it is not necessary to install library.

Report Director Enterprise adapter 11.19.

In Report Director Enterprise adapter, it is not necessary to install library.



List Creator adapter 11.20.

List Creator V9.1 adapter 11.20.1.

To output the form using List Creator adapter, settings must be configured in the property file of

DataSpiderServer “DataSpiderServer.lax”. Configure the settings with the below procedure.

Setting procedure


2. Open the text editor of $DATASPIDER_HOME/server/bin/DataSpiderServer.lax.

3. Add the library path of the following List Creator with the delimiter “;” and without a line

feed in the key “lax.class.path”.

Use “/” for file delimiter.

4. Save changes of DataSpiderServer.lax.


Settings during remote connection

Below connector must be installed in the OS that runs DataSpiderServer in order to output the

form from the form output server from a different OS apart from the one that runs

DataSpiderServer.

Interstage List Creator Connector

<ListCreator installation directory >/classes/fjoajif.jar

<ListCreator installation directory>/classes/fjoaweb.jar

<ListCreator installation directory>/remoteprint/requester/lib/ardus.jar

<ListCreator installation directory>/remoteprint/requester/lib/ardusobj.jar

<ListCreator installation directory >/remoteprint/requester/lib/ArdusRepository.jar

<ListCreator installation directory>/remoteprint/requester/lib/jomcli.jar

<ListCreator installation directory>/remoteprint/requester/lib/jomrequester.jar



Also, environment settings must be done so that the connector link function of the above

connector is used in DataSpiderServer operating OS.

For more details on the environment settings of connector link function, refer to “Environment

settings/Edit form” in the Interstage List Creator Manual.



Xuras inicio adapter 11.21.

You cannot use multiple versions of Xuras inicio adapter at the same time.

If the library of Xuras Inicio adapter is installed, the Web Services adapter cannot be used.

For more details, refer to “Web Services adapter”

If the library of Xuras Inicio adapter is installed, the Salesforce adapter cannot be used. For

more details, refer to “Salesforce adapter”

Xuras inicio 1.7 adapter 11.21.1.

Required libraries

axis.jar

commons-collections.jar

commons-discovery.jar

commons-logging.jar

inicio-client.jar

jaxrpc.jar

saaj.jar

wsdl4j.jar

xmlParserAPIs.jar

To get a library

If Xuras inicio 1.7 server is installed with default settings, required library is stored in

C:\Program

Files\BeaconIT\inicio\server\jakarta-tomcat\webapps\inicio\WEB-INF\lib.



2. Copy required library group right under the directory





Xuras inicio 1.5 adapter 11.21.2.

Required libraries

axis.jar

commons-collections.jar

commons-discovery.jar

commons-logging.jar

inicio-client.jar

jaxrpc.jar

saaj.jar

wsdl4j.jar

xmlParserAPIs.jar

To get a library

If Xuras inicio 1.5 server is installed with default settings, required library is stored in

C:\Program

Files\BeaconIT\inicio\server\jakarta-tomcat\webapps\inicio\WEB-INF\lib.



2. Copy required library right under the directory





Mainframe adapter 11.22.

To use mainframe adapter, DataSpider mainframe connection server must be installed separately.

For more details, refer to “Mainframe Adapter User Guide” bundled to the product.

FTP adapter 11.23.

In FTP adapter, it is not necessary to install library.

JMS adapter 11.24.

It is necessary to install the class library provided by each JMS provider in

$DATASPIDER_HOME/server/plugin/data_processing/modules/jms_adapter.

Location directory of the class library provided by each JMS provider varies depending on each JMS

provider.

REST adapter 11.25.

In REST adapter, it is not necessary to install library.

Web adapter 11.26.

In Web adapter, it is not necessary to install library.



Web Services adapter 11.27.

In Web Services adapter, it is not necessary to install library.

When using both Web Services adapter and SAP adapter in the same environment, SOAP

requests of Web Services adapter are sent through HTTP 1.0.

If SOAP request is sent through HTTP 1.1 in SAP EICS installed environment, perform back up for

eics-client.jar which is found under $DATASPIDER_HOME/server/system/common/lib, save it and

then, restart DataSpiderServer.

You cannot use Web Services adapter and Xuras Inicio adapter at the same time.

If Web Services adapter is used in an environment with the library for Xuras inicio adapter, perform

back up for axis.jar which is found under $DATASPIDER_HOME/server/plugin/data_processing

/share/lib, save it and then, restart DataSpiderServer.

(To use Xuras inicio adapter, restore axis.jar from the back-up)

Mail adapter 11.28.

In Mail adapter, it is not necessary to install library.

Active Directory adapter 11.29.

In Active Directory adapter, it is not necessary to install library.



Amazon Web Services adapter 11.30.

Amazon DynamoDB adapter 11.30.1.

In Amazon DynamoDB adapter, it is not necessary to install library.

Amazon EC2 adapter 11.30.2.

In Amazon EC2 adapter, it is not necessary to install library.

Amazon RDS for MySQL 5.7 adapter 11.30.3.

Required library




To get a library

Download JDBC drivers from MySQL Connector/J 5.1 download site.




$DATASPIDER_HOME/server/plugin/data_processing/modules/amazon_rds57_adapter

.


Amazon RDS for MySQL 5.6 adapter 11.30.4.

Required library







To get a library

Download JDBC drivers from MySQL Connector/J 5.1 download site.




$DATASPIDER_HOME/server/plugin/data_processing/modules/amazon_rds56_adapter

.


Amazon RDS for Oracle 12c adapter 11.30.5.

Required library

ojdbc7.jar



To get a library

Download JDBC driver for version 12.1 from “JDBC Drivers” link page of Oracle Software

Downloads site.




$DATASPIDER_HOME/server/plugin/data_processing/modules/amazon_rds_oracle12c

_adapter.


Amazon RDS for Oracle 11g R2 adapter 11.30.6.

Required library

ojdbc6.jar








To get a library

Download JDBC driver for version 11.2 from “JDBC Drivers” link page of Oracle Software

Downloads site.




$DATASPIDER_HOME/server/plugin/data_processing/modules/amazon_rds_oracle11g

r2_adapter.


Amazon RDS for PostgreSQL 9.5 / 9.4 / 9.3 adapter 11.30.7.

In Amazon RDS for PostgreSQL adapter, it is not necessary to install library.

Amazon RDS for SQL Server 2014 adapter 11.30.8.

Required library

sqljdbc42.jar



To get a library

Download Microsoft JDBC Driver 6.0 for SQL Server from Microsoft Downloads Center.



2. Copy sqljdbc42.jar right under the directory

$DATASPIDER_HOME/server/plugin/data_processing/modules/amazon_rds_sqlserver

2014_adapter.







Amazon RDS for SQL Server 2012 adapter 11.30.9.

Required library

sqljdbc42.jar



To get a library

Download Microsoft JDBC Driver 6.0 for SQL Server from Microsoft Downloads Center.



5. Copy sqljdbc42.jar right under the directory

$DATASPIDER_HOME/server/plugin/data_processing/modules/amazon_rds_sqlserver

2012_adapter.


Amazon Redshift adapter 11.30.10.

In Amazon Redshift adapter, it is not necessary to install library.

Amazon S3 adapter 11.30.11.

In Amazon S3 adapter, it is not necessary to install library.

Amazon SimpleDB adapter 11.30.12.

In Amazon SimpleDB adapter, it is not necessary to install library.

Amazon SQS adapter 11.30.13.

In Amazon SQS adapter, it is not necessary to install library.

Cloudn adapter 11.31.

In Cloudn adapter, it is not necessary to install library.




Google Apps adapter 11.32.

Gmail adapter 11.32.1.

In Gmail adapter, it is not necessary to install library.

Google Drive Adapter 11.32.2.

In Google Drive adapter, it is not necessary to install library.

Google Sheets Adapter 11.32.3.

In Google Sheets adapter, it is not necessary to install library.

kintone adapter 11.33.

In kintone adapter, it is not necessary to install library.



Microsoft Azure adapter 11.34.

Azure SQL Database Adapter 11.34.1.

Required library

sqljdbc42.jar


Microsoft SQL Server JDBC Driver 6.0

To get a library

Download Microsoft SQL Server JDBC Driver 6.0 from Microsoft Download Center.



2. Copy sqljdbc42.jar to directory

$DATASPIDER_HOME/server/plugin/data_processing/modules/sqlazure_adapter.


Azure Storage BLOB Adapter 11.34.2.

In Azure Storage BLOB adapter, it is not necessary to install library.

Nifty Cloud Adapter 11.35.

Nifty Cloud Adapter 11.35.1.

In Nifty Cloud adapter, it is not necessary to install library.

Nifty Cloud Storage Adapter 11.35.2.

In Nifty Cloud Storage adapter, it is not necessary to install library.




Log Manager for Salesforce adapter 11.36.

In Log Manager for Salesforce adapter, it is not necessary to install library.

Salesforce adapter 11.37.

Salesforce adapter 11.37.1.

In Salesforce adapter, it is not necessary to install library.

You cannot use Salesforce adapter and Xuras Inicio adapter at the same time.

If Salesforce adapter is used in an environment with the library for Xuras inicio adapter, perform

back up for axis.jar which is found under $DATASPIDER_HOME/server/plugin/data_processing

/share/lib, save it and then, restart DataSpiderServer.

(To use Xuras inicio adapter, restore axis.jar from the back-up)

Salesforce Bulk adapter 11.37.2.

In Salesforce Bulk adapter, it is not necessary to install library.

Salesforce Metadata adapter 11.37.3.

In Salesforce Metadata adapter, it is not necessary to install library.



Hadoop HDFS adapter 11.38.

In Hadoop HDFS adapter, it is not necessary to install library.

HULFT adapter 11.39.

HULFT8 / HULFT7 Adapter 11.39.1.

In HULFT adapter, it is not necessary to install library.



12. About the port used by DataSpider Servista

DataSpider Servista uses a port for RMI communication (RMI port) as well as a port for HTTP

communication (HTTP port) configured during installation.

These ports are used for communication between the DataSpiderServer and the DataSpider

Studio.

Usually, a RMI port uses multiple ports randomly, but when a firewall or port filtering functions is

configured, the RMI port should be static.

See also: ”DataSpider Studio cannot be connected to DataSpiderServer (3)” “My project

takes too long to start up in DataSpider Studio(2)”

A RMI port is specified as follows.

Config file

Server side

$DATASPIDER_HOME/server/conf/system.properties

Client side

$DATASPIDER_HOME/client/conf/system.properties

Property key

ds.rmi.port

Description of the values

Specify the TCP port number used by each server/client

Setting example

ds.rmi.port=7001

The firewall and/or the filtering functions corresponding to the specified port number should

be configured so that the port can operate in the used environmental conditions.

Be sure to specify an unused port number



13. Start and Shutdown of DataSpiderServer

Start DataSpiderServer 13.1.

After installation of DataSpiderServer, you can start DataSpiderServer by following procedure.

1. Confirm Repository DB service is operating. (When Repository DB is enabled).

2. Start DataSpiderServer.

Windows Version

In “DataSpider Servista <Version> Select “DataSpiderServer” from "Windows start

menu".

(If DataSpiderServer is installed as Windows service) Start Windows service.

Run $DATASPIDER_HOME/server/bin/DataSpiderServer.exe.

UNIX/Linux Version

Run $DATASPIDER_HOME/server/bin/DataSpiderServer

It may take a few minutes to start the DataSpiderServer for the first time because the

Server makes the index of the help.

3. When DataSpiderServer starts successfully, following messages are output to server.log and

DataSpiderServer console.

--- |INFO| --- |INFO|***************************************************************** --- |INFO|***************************************************************** --- |INFO|*********************** DataSpider Server *********************** --- |INFO|***************************************************************** --- |INFO|***************************************************************** --- |INFO|Starting DataSpider Server... --- |INFO|Loading system. System name: [DataSpider Server] --- |INFO|System was successfully loaded. --- |INFO|Loading modules... : (...) --- |INFO|Service of module [DataProcessingComponent Manager] was successfully started. --- |INFO|Service of module [ScriptRunner Container] was successfully started. --- |INFO|System service was successfully started. --- |NOTICE|DataSpider Server was successfully started.

--- |INFO|*****************************************************************



Restart DataSpiderServer 13.2.

To restart DataSpiderServer, execute either of following procedures.

Common to Windows Version & UNIX/Linux Version

Press [Reboot] button in [Others] tab of [DataSpiderServer Settings], Control Panel,

DataSpider Studio.

Windows Version

In command prompt, move to $DATASPIDER_HOME/server/bin and run "shutdown -r".

(When registered as Windows service) Restart Windows service.

UNIX/Linux Version

In console, move to "$ DATASPIDER_HOME / server / bin" and run the command

"shutdown -r".

Stop DataSpiderServer 13.3.

To stop DataSpiderServer, execute either of following procedures.

Windows Version

In “DataSpider Servista <Version>” Select “Shutdown” from the start menu.

Press [Shutdown] button in [Others] tab of [DataSpiderServer Settings], Control Panel,

DataSpider Studio.

(When registered as Windows service) Stop Windows service.

UNIX/Linux Version

Run $DATASPIDER_HOME/server/bin/Shutdown



14. Start and Exit of DataSpider Studio

Start DataSpider Studio 14.1.

DataSpider Studio can be started with one of following methods.

In the Windows [Start] menu, select [DataSpider Studio].

Run $DATASPIDER_HOME/client/bin/DataSpiderStudio.exe directly.

When DataSpider Studio starts first time, it synchronizes modules with DataSpiderServer.

After synchronization, you need to restart DataSpider Studio.

Depending on network conditions, synchronization of modules may take much time

when DataSpider Studio is started for the first time. Do not restart DataSpider Studio until

"100%" is shown in the synchronization progress display dialog.

Login 14.1.1.

Login dialog is displayed if succeeded in starting DataSpider Studio.

Enter user name and password, and press [Login] button. If succeeded to login, desktop screen

of DataSpider Studio is displayed.

Language which is used in Studio is selected from [Language].

Edit Server List 14.1.2.

If you want to change connection destination, Select [Edit server list] from [Server list] of login

dialog and open "Edit server list" dialog.

Select connection destination to be edited in server list area, edit setting and press [Apply] button.

Return to login dialog with edit applied.

In login dialog, select server to be connected from [Server list] and login. When server that will

try to login is different from server connected when Studio starts, you need to restart DataSpider

Studio so that module may synchronize. After pressing [Login] button, close DataSpider Studio

and start again.

Moreover, connection destination can save multiple settings. If you add new connection



destination, press [Add] button and configure according to displayed screen.

Connection destination "Last setting" cannot be saved. If "Last setting" is in [Server list],

change the setting name and save by pressing [Apply] button.

When Failed to Connect to Server 14.1.3.

If Studio fails to connect to DataSpider Server, "Failed to connect to server" dialog is displayed.

Press [OK] and following "Edit connection destination information" screens are displayed.

If host name or IP address is wrong, change the setting and press [Save] button. If you save

setting, you need to restart DataSpider Studio.

Close DataSpider Studio according to screen and start again.

If you press [Cancel] button, Setting isn't modified and Studio try to reconnect to

DataSpiderServer.

If you switch display to other applications before the dialog is displayed, the dialog might be

hidden behind other applications. Minimize all other displayed applications or switch application by

Alt + Tab key.

Settings set on "Edit connection destination information" screen are not added to [Server

list].If the setting set on "Edit connection destination information" screen already exists, display

the setting on top of [Server list].

If the setting doesn't exist in [Server list], it is added to [Server list] by a set name "Last setting"

when being start next time. However, because the setting "Last setting" cannot be saved in

[Server list], Next, when you change Server list, you need to change connection destination name

"Last setting".

Exit DataSpider Studio 14.2.

After selecting [Exit/logoff Studio] of Studio menu, press [Exit] button or close login dialog by

pressing [x] button and press [Exit] button by displayed exit confirmation dialog, you can exit

Studio.



15. Start DataSpider Servista Help

You can refer help by a web browser.

Method of starting DataSpider Servista help is as follows.

DataSpiderServer should be started first.

1. Start DataSpiderServer.

2. Start the browser Help with one of the following methods.

Common to Windows Version & UNIX/Linux Version

In Web Browser

Access to "http://<The host name or the IP address of the OS where

DataSpiderServer is running>:<The port number of

DataSpiderServer>/dataspider/doc/help/index.html".

Windows Version

"DataSpider Servista <version>" Select “Help Document” from Windows Start

menu.



16. Service Development

The basic knowledge related to the concept are function, script creating procedures, development

and application necessary for developing the services in DataSpider Servista is described in the

below document.

Concepts, functions, terms and simple scripting procedure.

In the page "Basic knowledge of the service" of DataSpider Servista Help.

Practical concepts and functions of service development.

In the page "Development of Service" of DataSpider Servista Help.

Various concepts and tools of service operation.

In the page "Service Operations" of DataSpider Servista Help.

And, tutorial has been prepared for the user assumed to develop the services actually. If you are

using DataSpider Servista for the first time, read the below

"DataSpider Servista tutorial guide"



17. Specifications and Limitations at Uninstallation

General 17.1.

In Windows version, short cut menu might remain in Windows start menu after uninstall.

(DSS-2691)

Delete manually.

If you have uninstalled it using the x86 version uninstaller,

$DATASPIDER_HOME/server/samples directory is not deleted. (DSS-14899).

Uninstall might not be successfully executed, and file might remain.

Delete manually. (DSS-14791)



18. Uninstall DataSpider Servista

Use uninstaller when you uninstall DataSpider Servista.

Before uninstallation, ensure that the various applications of DataSpider Servista

have been stopped.

Start Uninstaller 18.1.

Start uninstaller in following way.

Windows Version

In "DataSpider Servista <version>” Select "Uninstall" from "Windows Start menu".

Run $DATASPIDER_HOME/Uninstaller/Uninstall.exe.

UNIX/Linux Version

Run $DATASPIDER_HOME/Uninstaller/Uninstall

Start Uninstall 18.2.

Press [Uninstall] and start uninstall.



Uninstall Completed 18.3.

When uninstall executed successfully, the “Uninstall Complete” screen is displayed.

List of directories that was not able to be deleted are displayed. Delete it manually after

confirmation.

Uninstaller will not delete following directories.

$DATASPIDER_HOME/server/conf

$DATASPIDER_HOME/server/data

$DATASPIDER_HOME/server/lic

$DATASPIDER_HOME/server/share

$DATASPIDER_HOME/client/conf

Directory files created after installation.

In the environment Repository DB, if you do not use the Repository DB after uninstalling,

delete even the database instance for the Repository DB.



19. Troubleshooting

DataSpiderServer cannot be started 19.1.

The "License file could not be found" error occurs and 19.1.1.

DataSpiderServer cannot be started

Event

At startup of DataSpiderServer, "com.appresso.ds.common.license.LicenseException: License file

cannot be found" error is output in server.log and DataSpiderServer fails to start.

Possible causes

Following causes are possible.

The license file is not in $DATASPIDER_HOME/server/lic.

The license file in $DATASPIDER_HOME/server/lic is not correct.

The name of the file in $DATASPIDER_HOME/server/lic is not "license.lic".

Remedies

Place the correct license file in $DATASPIDER_HOME/server/lic and start DataSpiderServer.



When restarting DataSpiderServer, "LifecycleException: 19.1.2.

Protocol handler initialization failed" error occurs and it fails

to restart

Event

At restart of DataSpiderServer, "LifecycleException: Protocol handler initialization failed:

java.net.BindException: Address already in use: JVM_Bind:<port number of DataSpiderServer>"

error occurs and DataSpiderServer fails to restart.

Possible causes

DataSpiderServer process may not have stopped correctly.

Remedies

Windows Version

Run $DATASPIDER_HOME/server/bin/Shutdown.exe first, and then start

DataSpiderServer.

UNIX/Linux Version

Run $DATASPIDER_HOME/server/bin/Shutdown first, and then start

DataSpiderServer.



DataSpider Studio cannot be connected 19.2.

DataSpider Studio cannot be connected to 19.2.1.

DataSpiderServer (1)

Event

DataSpider Studio fails to connect to DataSpiderServer that is installed in Red Hat Enterprise

Linux.

Possible causes

IP address bound with host name might be loopback address (127.0.0.1). If loopback address is

specified, RMI that is used by communication of DataSpiderServer and DataSpider Studio does not

work normally.

If you installed Red Hat Enterprise Linux by default setting, contents of /etc/hosts file is as follows.

"myserver" is specified value as host name by installer. By above-mentioned setting, host name is

bound with local loopback address.

Remedies

To the following, specify pair of IP address that can be communicated from OS that operates

DataSpider Studio and host name.

In the above example, “myserver” is bounded to the IP address “192.168.0.1”.

# Do not remove the following line, or various programs

# that require network functionality will fail.

127.0.0.1 myserver localhost.localdomain localhost

# Do not remove the following line, or various programs

# that require network functionality will fail.

127.0.0.1 localhost.localdomain localhost

192.168.0.1 myserver





Event

DataSpider Studio fails to connect to DataSpiderServer.

Possible causes

If multiple network cards are installed in operating system that DataSpiderStudio operates or if IP

address of the machine is allocated by DHCP, DataSpiderStudio might not be able to connect to

DataSpiderServer.

Remedies

Specify available IP address of client host machine by "java.rmi.server.hostname" key in

system.properties file of DataSpider Studio and restart Studio.

If multiple network cards are installed in operating system that DataSpiderClient operates, specify

available IP address of server host machine by "java.rmi.server.hostname" key in

system.properties file of DataSpiderServer and restart DataSpiderServer.

Refer to "Property Reference" of DataSpider Servista help for details such as setting method

etc.



Event

DataSpider Studio cannot be connected to DataSpiderServer.

Possible causes

The RMI port used for communications between the server and the client may be restricted by a

firewall or the port filtering functions of the OS where DataSpiderServer is running.

Remedies

Fix the RMI port in [System property] for the server side system.

Refer to “About the port used by DataSpider Servista”, for details about configurations.



Junk character in installer 19.3.

Events

Junk characters are displayed when the installer is started in the Japanese environment of Red Hat

Enterprise Linux. (It is displayed as "□")

Possible causes

The installer may not correctly refer to the font file of the OS.

Remedies

Start the installer after creating the symbolic link for the font file of the OS.

/usr/share/fonts/ja/TrueType/kochi-gothic-subst.ttf

/usr/share/fonts/ja/TrueType/kochi-mincho-subst.ttf

Creation procedure

1. Create a symbolic link as /usr/share/fonts/ja/TrueType/kochi-gothic-subst.ttf. Execute the

command in console as follows.

2. Create a symbolic link as /usr/share/fonts/ja/TrueType/kochi-mincho-subst.ttf. Execute the

command in console as follows.

# ln -s /usr/share/fonts/ja/TrueType/kochi-gothic-subst.ttf

/usr/share/fonts/ja/TrueType/kochi-gothic.ttf

# ln -s /usr/share/fonts/ja/TrueType/kochi-mincho-subst.ttf

/usr/share/fonts/ja/TrueType/kochi-mincho.ttf



It takes long time to open My Project 19.4.

My project takes too long to start up in DataSpider Studio 19.4.1.

(1)

Event

If multiple network cards are installed in operating system that DataSpiderClient operates, if you

start opening My Projects of DataSpider Studio, it takes long time.

Possible causes

If multiple network cards are installed in operating system that DataSpiderClient operates or if IP

address of the machine is allocated by DHCP, DataSpiderClient might not be able to connect to

DataSpiderServer.

Remedies

Specify available IP address of client host machine by "java.rmi.server.hostname" key in

system.properties file of DataSpider Studio and restart Studio.

If multiple network cards are installed in operating system that DataSpiderClient operates, specify

available IP address of server host machine by "java.rmi.server.hostname" key in

system.properties file of DataSpiderServer and restart DataSpiderServer.

Refer to "Property Reference" of DataSpider Servista help for details such as setting method

etc.

My project takes too long to start up in DataSpider Studio 19.4.2.

(2)

Event

The following events occur in an environment where a firewall and/or port filtering functions are

configured.

After startup of Studio, Studio is not operable when opening My Project.

No response is returned after debugging in Designer.

Possible causes



The RMI port functions used for communication between the server and the client may be

restricted by a firewall and/or port filtering functions of the OS where DataSpiderServer or

DataSpider Studio is running.

Remedies

Fix the RMI port in [System property] for the server side and the client side.

Refer to, “About the port used by DataSpider Servista”, for details about configurations.



DataSpider Servista 4.1 Install Guide The 3rd edition: June 14 2018

APPRESSO K.K. 19F Akasaka Intercity AIR 1-8-1 Akasaka, Minato-ku, Tokyo 107-0052, Japan

TEL : 81-3-4321-1111

Date post:	17-Apr-2020
Category:	Documents
Upload:	others
View:	9 times
Download:	0 times

4.1 Install Guide · 2018-07-31 · This document describes how to install and setup the new...

Documents