4.2 Install Guide€¦ · This document describes how to install and setup the new version of HULFT Integrate 4.2. Refer “HULFT Integrate Upgrade Guide” for the upgrade from the

4.2 Install Guide

Document Release Date: April 3 2019 (The 2nd Edition)

Copyright© 2019 HULFT, Inc. All rights reserved.

HULFT Integrate 4.2 Install Guide

Copyright© 2019 HULFT INC All rights reserved.

2

Table of Contents

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

1.1. Precautions.......................................................................................................... 11

1.1.1. Copyright Notice ..................................................................................... 11

1.1.2. Trademarks ............................................................................................ 11

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

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

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

2.1. Supported OS ...................................................................................................... 14

2.2. Repository DB ...................................................................................................... 15

2.3. Adapter ............................................................................................................... 16

3. About HULFT Integrate .......................................................................................... 20

3.1. Composition of HULFT Integrate ............................................................................ 20

4. OS supporting HULFT Integrate .............................................................................. 21

4.1. Server and Client for Execution .............................................................................. 21

4.2. Client for Development ......................................................................................... 22

4.3. Language in Support Platform ................................................................................ 23

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

4.4. Specification Limits / Precautions ........................................................................... 25

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

4.4.2. Restriction for timezone in platform .......................................................... 25

4.5. Supported virtualization system ............................................................................. 27

5. System requirements ............................................................................................ 28



3

5.1. Both Server and Client .......................................................................................... 28

5.2. Server ................................................................................................................. 28

5.3. Client for development .......................................................................................... 29

5.4. Client for Execution .............................................................................................. 29

6. About Java Runtime Environment ........................................................................... 30

7. Repository DB settings ........................................................................................... 31

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

7.1.1. Repository DB settings ............................................................................ 31

7.1.2. Creating a Repository DB ......................................................................... 31

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

7.2. Databases supported as Repository DB ................................................................... 33

7.3. Setting up each database ...................................................................................... 34

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

7.3.2. When using MySQL ................................................................................. 34

7.3.3. When using Oracle Database .................................................................... 36

7.3.4. When using PostgreSQL .......................................................................... 37

7.3.5. When using Microsoft SQL Server ............................................................. 38

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

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

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

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

7.3.10. When using Azure SQL Database .............................................................. 44

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

2(12.2)) 44



4

8. Specifications and Limitations at Installation ............................................................. 46

8.1. General ............................................................................................................... 46

8.2. Installer .............................................................................................................. 47

8.3. Select Component ................................................................................................ 47

8.4. Select Repository DB ............................................................................................ 47

8.5. Register Windows Service ..................................................................................... 48

8.6. Installation Directory Settings ................................................................................ 48

8.7. Installation Complete ............................................................................................ 48

9. Notes concerning Windows ..................................................................................... 49

9.1. Notes when Installing HULFT Integrate ................................................................... 49

10. Installation of HULFT Integrate ............................................................................... 50

10.1. Installation ........................................................................................................ 50

10.1.1. Select Language ..................................................................................... 50

10.1.2. Introduction ........................................................................................... 51

10.1.3. Select Package ....................................................................................... 51

10.1.4. Select Component................................................................................... 51

10.1.5. Select Client Environment ........................................................................ 52

10.1.6. Administrator Password Settings .............................................................. 53

10.1.7. Select Repository Database ...................................................................... 53

10.1.8. Select Database Product .......................................................................... 54

10.1.9. Register Windows Service ........................................................................ 55

10.1.10. Connection Information Settings ............................................................... 56

10.1.11. Installation Directory Settings .................................................................. 56

10.1.12. Select License File ................................................................................... 56



5

10.1.13. Heap Size Settings .................................................................................. 57

10.1.14. Summary of Installation .......................................................................... 57

10.1.15. Installation Complete .............................................................................. 57

10.2. Work after Installation ......................................................................................... 58

10.2.1. License file settings ................................................................................. 58

10.2.2. Setting the font file for UNIX/Linux version ................................................ 58

10.2.3. Application Log Output Settings ................................................................ 58

10.2.4. About Windows start menu ...................................................................... 59

11. Pre-setting of Adapters .......................................................................................... 61

11.1. Access Adapter................................................................................................... 61

11.1.1. Access 2013/2010 adapter ...................................................................... 61

11.2. DB2 Adapter ...................................................................................................... 62

11.2.1. DB2 V11.1 adapter ................................................................................. 62

11.2.2. DB2 V10.5 adapter ................................................................................. 62

11.2.3. DB2 for i 7.3 / 7.2 adapter....................................................................... 63

11.3. MySQL Adapter .................................................................................................. 64

11.3.1. MySQL 8.0 adapter ................................................................................. 64

11.3.2. MySQL 5.7 adapter ................................................................................. 64

11.3.3. MySQL 5.6 adapter ................................................................................. 65

11.4. Oracle Adapter ................................................................................................... 66

11.4.1. Oracle 18c Adapter ................................................................................. 66

11.4.2. Oracle 12cR2 Adapter ............................................................................. 66

11.4.3. Oracle 12c Adapter ................................................................................. 67

11.4.4. Oracle 11gR2 Adapter ............................................................................. 67



6

11.4.5. Oracle OCI Adapter ................................................................................. 68

11.5. PostgreSQL Adapter ............................................................................................ 69

11.6. SQL Server Adapter ............................................................................................ 69

11.6.1. SQL Server 2017 Adapter ........................................................................ 69



11.6.4. SQL Server 2012 JDBC Adapter ................................................................ 71

11.6.5. SQL Server 2008 R2 JDBC Adapter ........................................................... 71

11.6.6. SQL Server 2008 JDBC Adapter ................................................................ 72

11.6.7. SQL Server 2008 ODBC Adapter ............................................................... 73

11.7. JDBC Adapter ..................................................................................................... 73

11.8. ODBC Adapter .................................................................................................... 73

11.9. NeoCore Adapter ................................................................................................ 73

11.9.1. NeoCore 3.1 adapter ............................................................................... 73

11.9.2. NeoCore 3.0 adapter ............................................................................... 74

11.9.3. NeoCore 2.9 adapter ............................................................................... 74

11.10. Thunderbus DB Agent Adapter ........................................................................... 75

11.11. Dr.Sum EA Adapter ........................................................................................... 75

11.12. Dynamics CRM Adapter ..................................................................................... 75

11.13. IBM Domino Adapter ......................................................................................... 75

11.13.1. IBM Domino 9.0 Adapter ......................................................................... 75

11.14. IBM Notes Adapter ............................................................................................ 76

11.14.1. IBM Notes 9.0 Adapter ............................................................................ 76

11.15. SAP Adapter ..................................................................................................... 76



7

11.16. SAP BC Adapter ................................................................................................ 77

11.17. Tableau Adapter ............................................................................................... 77

11.17.1. Output Hyper File ................................................................................... 77

11.17.2. Output TDE File ...................................................................................... 79

11.18. Universal Connect/X Adapter ............................................................................. 79

11.19. Report Director Enterprise Adapter ..................................................................... 79

11.20. List Creator Adapter .......................................................................................... 80

11.20.1. List Creator V9.1 Adapter ........................................................................ 80

11.21. FTP Adapter ..................................................................................................... 81

11.22. JMS Adapter ..................................................................................................... 81

11.23. Rest Adapter .................................................................................................... 81

11.24. Web Adapter .................................................................................................... 81

11.25. Web Services Adapter ....................................................................................... 81

11.26. Mail adapter ..................................................................................................... 82

11.27. Amazon Web Services Adapter ........................................................................... 82

11.27.1. Amazon Aurora for MySQL 5.7 Adapter ..................................................... 82

11.27.2. Amazon Aurora for MySQL 5.6 Adapter ..................................................... 82

11.27.3. Amazon DynamoDB Adapter .................................................................... 82

11.27.4. Amazon EC2 Adapter .............................................................................. 82

11.27.5. Amazon RDS for MySQL 8.0 Adapter ......................................................... 82



11.27.8. Amazon RDS for Oracle 12c Adapter ......................................................... 84

11.27.9. Amazon RDS for Oracle 11g R2 Adapter .................................................... 84



8

11.27.10. Amazon RDS for PostgreSQL 10 / 9.5 / 9.4 Adapter .................................... 85

11.27.11. Amazon RDS for SQL Server 2017 Adapter ................................................ 85




11.27.15. Amazon Redshift Adapter ........................................................................ 87

11.27.16. Amazon S3 Adapter ................................................................................ 88

11.27.17. Amazon SimpleDB Adapter ...................................................................... 88

11.27.18. Amazon SQS Adapter .............................................................................. 88

11.28. Cloudn Adapter ................................................................................................ 88

11.29. G Suite Adapter ................................................................................................ 88

11.29.1. Gmail Adapter ........................................................................................ 88

11.29.2. Google Drive Adapter .............................................................................. 88

11.29.3. Google Sheets Adapter ............................................................................ 88

11.30. kintone Adapter ................................................................................................ 88

11.31. Nifty Cloud Adapter ........................................................................................... 89

11.31.1. Nifty Cloud Adapter ................................................................................. 89

11.31.2. Nifty Cloud Storage Adapter ..................................................................... 89

11.32. Hadoop HDFS Adapter ....................................................................................... 89

11.33. HULFT Adapter ................................................................................................. 89

11.33.1. HULFT8 / HULFT7 Adapter....................................................................... 89

12. About the port used by HULFT Integrate .................................................................. 90

13. Start and Shutdown of IntegrateServer ................................................................... 91

13.1. Start IntegrateServer .......................................................................................... 91



9

13.2. Restart IntegrateServer ....................................................................................... 92

13.3. Stop IntegrateServer .......................................................................................... 92

14. Launch and Exit Integrate Studio ............................................................................ 93

14.1. Launch Integrate Studio ...................................................................................... 93

14.1.1. Login ..................................................................................................... 93

14.1.2. Edit Server List ....................................................................................... 93

14.1.3. When Failed to Connect to Server ............................................................. 94

14.2. Exit Integrate Studio ........................................................................................... 95

15. Launch and Exit Integrate Studio for Web ................................................................ 96

15.1. Execution environment of Integrate for Web .......................................................... 96

15.2. Launch Integrate Studio for Web .......................................................................... 96

15.2.1. Login ..................................................................................................... 97

15.3. Exit Integrate Studio for Web ............................................................................... 97

16. Start HULFT Integrate Help .................................................................................... 98

17. Service Development ............................................................................................. 99

18. Specifications and Limitations at Uninstallation ........................................................100

18.1. General ............................................................................................................100

19. Uninstall HULFT Integrate .....................................................................................101

19.1. Uninstallation procedure of HULFT Integrate .........................................................101

19.2. Uninstallation procedure of HULFT Integrate Studio Launcher .................................102

20. Troubleshooting ...................................................................................................103

20.1. Junk character in installer ...................................................................................103

20.2. Installing or uninstalling HULFT Integrate by using CUI installer fails .......................104

20.3. IntegrateServer cannot be started .......................................................................105



10

20.3.1. The "License file could not be found" error occurs and IntegrateServer cannot

be started 105

20.3.2. When restarting IntegrateServer, "LifecycleException: Protocol handler

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

20.4. Integrate Studio cannot be connected ..................................................................107

20.4.1. Integrate Studio cannot be connected to IntegrateServer (1) ......................107



20.5. It takes long time to open My Project ...................................................................109

20.5.1. My project takes too long to start up in Integrate Studio (1) .......................109

20.5.2. My project takes too long to start up in Integrate Studio (2) .......................109



11

1. Before Use

This document describes how to install and setup the new version of HULFT Integrate 4.2.

Refer “HULFT Integrate Upgrade Guide” for the upgrade from the existing version.

1.1. Precautions

1.1.1. Copyright Notice

The copyright of this software is owned by HULFT, Inc. 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 HULFT, Inc. or its licensors, and it is

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

use of HULFT, Inc. or the licenser's software and this manual is subject to compensation

and criminal proceedings.

1.1.2. Trademarks

HULFT, HULFT logo, Integrate, Integrate mark, IntegrateServer, IntegrateServer logo, and

HULFT Inc. are trademarks or registered trademarks of HULFT, Inc.

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.



12

1.2. About the mark of this document

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.

“$INTEGRATE_HOME” shows the directory where HULFT Integrate is installed. In default, it

is "C:\Program Files\hulft\integrate" for Windows version and "<HOME>/hulft/integrate"

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: $INTEGRATE_HOME/server/logs/<Date directory>

URLs of the Web sites shown in this document are as of September, 2018, and are subject

to change without notice due to reasons of the Web site.

“Studio" means "Integrate Studio", and "Studio for Web" means "Integrate Studio for Web".

The descriptions of the Windows and UNIX/Linux versions of IntegrateServer 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.

1.3. About the Icons Used in This Guide

This Guide uses the following icons in its explanation.

Icon Description



13

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.



14

2. About end of sales and support

As on 2019/1/8, the sales and support for the following Operating systems, databases for

Repository DB, and Adapters have ended. Note it during HULFT Integrate installation.

2.1. Supported OS

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



15

2.2. Repository DB

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

5.5 2018/12/31

Oracle 8.1.6 2010/7/31

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



16

Repository DB Version End of Support


8.4 2014/7/31

9.0 2015/9/30

9.1 2016/10/31

9.2 2017/9/30

9.3 2018/9/30

SQL Server 2000 2013/5/31

2005 2016/4/30

MySQL on Amazon RDS 5.1 2016/8/31

Amazon RDS for PostgreSQL 9.3 2018/9/30

2.3. Adapter

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



17


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

7.1 2018/4/30

MySQL 5.0 2012/1/31

5.1 2015/10/31

5.5 2018/12/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

10g R1 2012/6/30

10g R2 2013/7/31

11g 2015/10/31


8.1 2012/1/31

8.2 2013/7/31



18


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

9.3 2018/9/30

SQL Server 2000 2013/5/31

2005 2016/4/30

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

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



19


8.0 2015/5/31

8.5 2018/9/30

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

8.5 2018/9/30

SAP From 3.1H to 4.7 2016/12/31

SAP BC 4.6 2016/10/31

Universal Connect/X 5.3 2015/7/31

BIGLOBE Cloud Hosting 2016/3/31

StraForm-X Ver 1.5 2017/5/31



20

3. About HULFT Integrate

HULFT Integrate 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.

HULFT Integrate 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.

3.1. Composition of HULFT Integrate

HULFT Integrate consists of the following application.

Name Description

Integrate Studio GUI based IDE for designing, developing and operating the services.

IntegrateServer Service execution environment.

ScriptRunner Application interface for the external invocation of service.

CLI Console Application for operating and managing services, which is used by

command line.

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

Name Description

Integrate Studio for

Web

GUI based IDE for designing, developing and operating the services.

Browser Help Referable help by using browser.



21

4. OS supporting HULFT Integrate

4.1. Server and Client for Execution

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)

(*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)

➢ Amazon Linux AMI



22

➢ Amazon Linux 2

(*4) For kernel, "Unbreakable Enterprise Kernel" is supported.

4.2. Client for Development

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)

(*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 “Integrate Studio for Web” page of help for the supported OS of Integrate

Studio for Web.



23

4.3. Language in Support Platform

The language in support platform varies by existence of language setting of HULFT Integrate.

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 HULFT

Integrate

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 HULFT Integrate

User is Japanese.

When "English" is set for HULFT Integrate language, to use Japanese at configurable /

inputtable fields on HULFT Integrate, the HULFT Integrate operating OS should be "OS of

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

4.3.1. About Windows language packs (Multilingual User

Interface Pack)

Environment with Japanese user interface is supported to use HULFT Integrate 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



24

➢ 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 IntegrateServer in Windows services, the user setting that starts the

service should be in Japanese.



25

4.4. Specification Limits / Precautions

4.4.1. Specification Limits / Precautions for language settings

In HULFT Integrate 4.2, 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

➢ WebConsole is not available. (DSS-14415)

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

NeoCore, ListCreator

➢ 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)

The specification of Studio for Web is output in English. (DSS-22930)

➢ 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)

The specification of Studio for Web is output in Japanese. (DSS-22930)

4.4.2. Restriction for timezone in platform

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



26

set, the setting is prior.)

The server timezone can be checked by the following procedure.

1. Select [IntegrateServer Settings] in Control Panel of Integrate Studio.

2. Select [General] tab and click [System properties] button.

3. Confirm the value of "user.timezone".

Setting way of timezone for client is as follows.

1. Stop each application in HULFT Integrate.

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

3. Delete "#" in "#user.timezone=Asia/Tokyo" and specify timezone of IntegrateServer

operating OS after "=" and save it.

4. Start IntegrateServer and Integrate Studio.

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

HULFT Integrate.

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 IntegrateServer operating OS.



27

4.5. Supported virtualization system

If you use HULFT Integrate in a virtual environment, all of the following conditions must be

satisfied.

OS where HULFT Integrate is running is included in "Supported Platforms" in this

document.

OS where HULFT Integrate is running supports virtual environment.

The virtual environment is host-based type or hypervisor-based type.

If all of the above conditions are satisfied, it is supported.

However, if the problem that depends on the specific virtual environment occurs, not only

HULFT Integrate but also the virtual environment may need to be changed.



28

5. System requirements

System requirements is the minimum configuration which allows HULFT Integrate 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.

5.1. Both Server and Client

Color: 24 bit color

Resolution: 1024x768 pixels or more

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

Studio for Web.

5.2. Server

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




29

5.3. Client for development


Windows x86 version

➢ CPU: Processor that meets system requirement that OS recommends



Windows x64 version




5.4. Client for Execution



➢ CPU: Processor that meets system requirement that OS recommends


➢ HDD: Free space of 500MB or more




➢ HDD: Free space of 500MB or more



30

6. About Java Runtime Environment

Since Java Runtime Environment (JRE) is bundled in each installer of HULFT Integrate 4.2, no

need to install JRE.

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

Windows version, Linux version

➢ 1.8.0_181

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

to operating system for details.



31

7. Repository DB settings

7.1. What is a Repository DB?

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, HULFT Integrate 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.

7.1.1. Repository DB settings

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 IntegrateServer. More than one IntegrateServer

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.

7.1.2. Creating a Repository DB

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 IntegrateServer. If a dedicated table already

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



32

7.1.3. Operation with / without a Repository DB

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.



33

7.2. Databases supported as Repository DB

HULFT Integrate supports the following databases as Repository DB.

DB2 for Linux, UNIX, and Windows

➢ Supported versions: V11.1 / V10.5

MySQL

➢ Supported versions: 8.0 / 5.7 / 5.6

Oracle Database

➢ Supported versions: 18c / Oracle Database Cloud Service(Oracle Database 12c Release

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

PostgreSQL

➢ Supported versions: 11 / 10 / 9.6 / 9.5 / 9.4

Microsoft SQL Server

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

MySQL on Amazon RDS

➢ Supported versions: 8.0 / 5.7 / 5.6

Oracle Database on Amazon RDS

➢ Supported versions: 12c / 11g Release 2

PostgreSQL on Amazon RDS

➢ Supported versions: 10 / 9.5 / 9.4

Microsoft SQL Server on Amazon RDS

➢ Supported versions: 2017 / 2016 / 2014 / 2012

Azure SQL Database

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

installing HULFT Integrate.



34

7.3. Setting up each database

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

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


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 HULFT Integrate, ensure that you can access it externally using these setting values.

7.3.2. When using MySQL

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

Host name or IP address of MySQL




35


Path of the supported JDBC drive

Supported JDBC driver

8.0

➢ Required library: mysql-connector-java-8.0.<Version>.jar

➢ Version of the driver: MySQL Connector/J 8.0.<Version>

5.7

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

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

5.6



<version> indicates the latest version.

User settings




Specification restrictions / Precautions

When you use MySQL, configure by the following procedure without setting

during installation.

➢ Setting procedure

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

Launch Integrate Studio.

Set from [Connection Wizard] in [Repository DB Management]-[Connection

Settings] tab in the Control Panel.



36

For details, refer to "Repository DB Management" in HULFT Integrate Help.

"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.

You must set the transaction isolation level of database as "READ-COMMITTED".

When HULFT Integrate communicates large data with the repository database

(*), you must set a large number to "max_allowed_packed" of the database.

* The following shows examples.

➢ Creation of a project with many icons

➢ Uploading large files

7.3.3. When using Oracle Database

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

Host name or IP address of Oracle Database


System identifier (SID)



18c

➢ Required library: ojdbc8.jar

➢ Version of the driver: Oracle JDBC Driver 18.3.0

12c Release 2



12c



37



11g Release 2



User settings




7.3.4. When using PostgreSQL

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

Host name or IP address of PostgreSQL





11

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

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

10


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

9.6

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



38

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

9.5



9.4

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



User settings




7.3.5. When using Microsoft SQL Server

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



39


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 installing HULFT Integrate, ensure that you can access it externally using these setting

values.

Specification restrictions/Precautions

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

casesensitive.

Connecting using Windows Integrated Authentication is impossible.

7.3.6. When using MySQL on Amazon RDS

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



40

Host name of MySQL on Amazon RDS

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




8.0

➢ Required library: mysql-connector-java-8.0.<Version>.jar

➢ Version of the driver: MySQL Connector/J 8.0.<Version>

5.7



5.6




User settings





When you use MySQL on Amazon RDS, configure by the following procedure

without setting during installation.

➢ Setting procedure

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



41

Launch Integrate Studio.

Set from [Connection Wizard] in [Repository DB Management]-[Connection

Settings] tab in the Control Panel.

For details, refer to "Repository DB Management" in HULFT Integrate Help.

"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.

7.3.7. When using Oracle Database on Amazon RDS

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


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




42

7.3.8. When using PostgreSQL on Amazon RDS

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

Host name of PostgreSQL on Amazon RDS





10


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

9.5



9.4




User settings




7.3.9. When using Microsoft SQL Server on Amazon RDS

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

needed.



43

Host name of Microsoft SQL Server on Amazon RDS





2017



2016



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.


values.



casesensitive.



44

Connecting using Windows Integrated Authentication is impossible.

7.3.10. When using Azure SQL Database

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.


values.



casesensitive.

7.3.11. When using Oracle Database Cloud Service(Oracle

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.



45

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.

Setting procedure

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

2. Launch Integrate Studio.

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

Example: "jdbc:oracle:thin:@<Host name>:<Port number>/<Service name>"



46

8. Specifications and Limitations at Installation

8.1. General

You cannot install multiple HULFT Integrate of different versions on the same platform.

You cannot install multiple HULFT Integrate 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

$INTEGRATE_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 HULFT Integrate

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

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

The uninstaller should be run by selecting

INTEGRATE_HOME/Uninstall/Uninstall.exe

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

the same platform.

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

installation. (DSS-22577)



47

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 Integrate, assign the general user

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

8.2. Installer

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

8.3. Select Component

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 [Integrate Studio for Web],

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

Configure the proper URL through the properties on the [Integrate Studio for Web], [Help]

menu of Windows start menu.

8.4. Select Repository DB

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 “%”,

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

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



48

8.5. Register Windows Service

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

conditions, the service of IntegrateServer 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 IntegrateServer in Windows Service name, multi byte characters are not

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

8.6. Installation Directory Settings

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 (only for UNIX/Linux version)

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

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

8.7. Installation Complete

Folder name (HULFT Integrate installation directory) cannot be changed after

installation.(DSS-7463)



49

9. Notes concerning Windows

If you install HULFT Integrate on Windows OS, read the following notes.

9.1. Notes when Installing HULFT Integrate

If you install HULFT Integrate in C drive (installation drive of Windows OS), the following

issues may occur.

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

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

from Integrate Studio and command prompt.

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

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

If you install HULFT Integrate in D drive in which Windows OS is not installed, the following

issues may occur.

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

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

from Integrate 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.



50

10. Installation of HULFT Integrate

This chapter explains the installation procedure of HULFT Integrate. The installer file that

supports each platform is used for installation.

10.1. Installation

Run the installer file that supports each platform, and start the installer.

The following table shows the file name of each installer and the supported Platforms.

Windows

File name Supported Platforms

hulft-integrate-42SP1-windows_x64.exe Windows x64 version

hulft-integrate-42SP1-windows_X86.exe Windows x86 version

UNIX/Linux

File name Supported Platforms Installation

method

hulft-integrate-42SP1-linux_x64.bin UNIX/Linux x64 version GUI method

hulft-integrate-42SP1-linux_X86.bin UNIX/Linux x86 version GUI method

hulft-integrate-42SP1-linux_X64_CUI.bin UNIX/Linux x64 version CUI method

To install HULFT Integrate by using GUI method, start X Windows System in advance.

The installer contains both the server and the client. The installation target is selected

during the installation process.

10.1.1. Select Language

Select a language by which operate the product.



51

IntegrateServer and Server CLI Console will start by the language you select here. You

cannot change the language after completing the installation.

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

selected language. The language can be changed after.

10.1.2. Introduction

In the introduction screen, read through the displayed content, and proceed to the next step.

10.1.3. Select Package

Select the package you purchased and proceed to the next step. Available packages are as

follows.

[Advanced Server Package]

[Basic Server Package]

[Select]

The product configurations between above packages and the terms and conditions of

their contracts are different. Be sure to select the correct one you purchased.

10.1.4. Select Component

Select component to install. Select component and proceed to the next step.

[Server and Client]: Both server and client are installed.

[Server only]: Only server is installed.

[Client only]: Only client is installed.

The following table shows the installation target components for server and client.



52

Installed application Server Client (*)

Clients for

development

Clients for execution

Integrate Studio for Web Yes Yes Yes

Help Document Yes Yes Yes

IntegrateServer Yes No No

ScriptRunner Yes No No

Server CLI Console Yes No No

Integrate Studio No Yes No

Client ScriptRunner No Yes Yes

Client CLI Console No Yes Yes

Yes: It is installed.

No: It is not installed.

*: 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 HULFT Integrate".

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

the same platform, when you independently install a server and a client of the same

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

10.1.5. Select Client Environment

Select the client environment to install. Select component and proceed to the next step.

Client for development

Client for execution

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

Component] screen.



53

For details on the applications to be installed, refer to the section "Select Component".

Notes on the clients for development

➢ Cannot be installed on UNIX/Linux environment.

➢ For Windows environment, use the installer with "exe" extension to install.

10.1.6. Administrator Password Settings

Enter the password of administrator (root user), and proceed to the next step.

[Administrator Password Settings] screen is not available when you select [Client only] on

the [Select Component] screen.

If omitted, "password" is set.

After installation, you can change administrator password from [User Accounts] of Control

Panel of Integrate Studio.

10.1.7. Select Repository Database

[Select Repository Database] screen is not available when you select [Client only] on the

[Select Component] screen.

Select whether to use Repository DB or not. Select component and proceed to the next step.

[Use repository]: It builds a Integrate file system on the database.

[Do not use repository]: It builds a Integrate file system on the file system of the OS

where IntegrateServer is running.

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

the next "Select Database Product" and after the section. Refer to "Register Windows Service"

for details.

If you use one of the following database as a repository DB, you cannot configure by

using the installer. Select [Do not use repository] and configure the settings after

installation.

・MySQL



54

・MySQL on Amazon RDS

・Oracle Database Cloud Service(Oracle Database 12c Release2(12.2))

For more details, refer to the following.

・"When using MySQL"

・"When using MySQL on Amazon RDS"

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

10.1.8. Select Database Product

[Select Database Product] screen is not available when you select [Do not use repository]

at [Select Repository Database] screen.

Select database products to use as repository DB. Select component and proceed to the next

step.

Available database products are as follows.

[DB2]: Selects when DB2 for Linux, UNIX, and Windows is used in repository DB.

[MySQL]: When you use MySQL or MySQL on Amazon RDS, do not select [MySQL],

but select [Do not use repository] after getting back to [Select Repository Database]

screen.

For more details, refer to "Specification restrictions / Precautions" in "When using

MySQL" and "When using MySQL on Amazon RDS".

[Oracle]: Selects when Oracle Database or Oracle Database on Amazon RDS is used

in repository DB.

[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.

After selecting database product, by the following procedure, select a JDBC driver and set

database connection information.

1. Specify file path of JDBC driver and proceed to the next step.

2. Enter connection information of database and proceed to the next step.

For more details about the supported versions of each database and JDBC driver, refer to the



55

following table.

Database, JDBC driver Referred to

DB2 Database "Supported versions of DB2 for Linux, UNIX, and Windows"

JDBC driver "Supported JDBC driver of DB2"

MySQL Database "Supported versions of MySQL"

"Supported versions of MySQL on Amazon RDS"

JDBC driver "Supported JDBC driver of MySQL"

"Supported JDBC driver of MySQL on Amazon RDS"

Oracle Database "Supported versions of Oracle Database"

"Supported versions of Oracle Database on Amazon RDS"

JDBC driver "Supported JDBC driver of Oracle Database"

"Supported JDBC driver of Oracle Database on Amazon RDS"

"Supported JDBC driver of Oracle Database Cloud Service(Oracle

Database 12c Release 2(12.2))"

PostgreS

QL

Database "Supported versions of PostgreSQL"

"Supported versions of PostgreSQL on Amazon RDS"

JDBC driver "Supported JDBC driver of PostgreSQL"

"Supported JDBC driver of PostgreSQL on Amazon RDS"

SQL

Server

Database "Supported versions of Microsoft SQL Server"

"Supported versions of SQL Server on Amazon RDS"

"Supported versions of Azure SQL Database"

JDBC driver "Supported JDBC driver of Microsoft SQL Server"

"Supported JDBC driver of SQL Server on Amazon RDS"

"Supported JDBC driver of Azure SQL Database"

10.1.9. Register Windows Service

For Windows version, select whether to register HULFT Integrate as the Windows service, and

proceed to the next step.



56

In the installer for UNIX/Linux version, this screen is not displayed.

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

Component] screen.

After checking [Register the server as Windows Service], if you omit the service name, it

is not registered as the Windows Service.

Precautions when you register a IntegrateServer with a repository DB on a Windows

service

If both the IntegrateServer with a repository DB and the repository DB are started from a

Windows service, repository DB may not yet be started when IntegrateServer is started.

In such case, you should set the appropriate times and cycles of Test connect count in

[Repository DB Management] - [Reconnection settings] tab in control panel of Integrate Studio.

10.1.10. Connection Information Settings

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

port number of IntegrateServer, and then proceed to the next step.

If [Host name/IP address] is omitted, "localhost" will be set.

If [Port number] is omitted, "7700" will be set.

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

"1023" or less. Specify the number other than "0" to "1023" for starting IntegrateServer as a

general user.

10.1.11. Installation Directory Settings

Set the installation directory of HULFT Integrate and proceed to the next step.

If HULFT Integrate already exists in the destination directory specified in destination folder,

a warning dialog appears. Do not overwrite the existing HULFT Integrate.

10.1.12. Select License File

Specify file path of HULFT Integrate license (license.lic), and proceed to the next step.



57

This screen is displayed when you select [Server and Client] or [Server only] on the


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

You can also apply license file even after installation.

10.1.13. Heap Size Settings

Specify a heap size of IntegrateServer and proceed to the next step.

This screen is displayed when you select [Server and Client] or [Server only] on the


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

version

256M 512M

10.1.14. Summary of Installation

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

button for GUI method, or press [Enter] button for CUI method, and then installation begins.

10.1.15. Installation Complete

When installation executed successfully, "Installation Complete" screen is displayed. Press

[Done] button for GUI method, or press [Enter] button for CUI method to end installer.

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

➢ $INTEGRATE_HOME/server/conf/dsserver.xml

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



58

connected repository DB, you can modify the settings through [Repository DB Management] in

the Integrate Studio's Control Panel.

10.2. Work after Installation

This chapter explains the procedure necessary to perform after installation.

10.2.1. License file settings

If you did not configure the license file (license.lic) in installer, copy the license file to the

license file storage directory manually.

License file storage directory

$INTEGRATE_HOME/server/lic

Notes on the license file

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

➢ Only one license file can be placed in the license file storage directory. If it is required

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

the following procedure.

1. Save the existing license file to another directory.

2. Store the new license file to the license file storage directory.

10.2.2. Setting the font file for UNIX/Linux version

In UNIX/Linux version, if the font file used to operate the product by the language in use is not

installed in the OS, store the font file of the language in use in

$INTEGRATE_HOME/jre/lib/fonts/fallback directory.

10.2.3. Application Log Output Settings

To add the application log to the NT event log system, store the following library file to the

directory where it is included in the environment variable "PATH" of Windows system.

Library file



59

$INTEGRATE_HOME/server/lib/NTEventLogAppender.dll

For more details, refer to the page "Application Log Output Settings" of HULFT Integrate

help.

10.2.4. About Windows start menu

In Windows version, start menus created at installation differ according to the settings in the

[Select Component] screen and the [Select Client Environment] screen during installation.

The settings of the screen during installation and created start menus are as follows.

[Select

Component]

screen

[Server and Client] [Server

only]

[Client only]

[Select client

environment]

screen

[Clients for

development]

[Clients

for

execution]

(*) [Clients for

development]

[Clients

for

execution]

Client CLI Console Yes Yes No Yes Yes

Integrate Studio Yes No No Yes No

Integrate Studio

for Web

Yes Yes Yes Yes Yes

IntegrateServer Yes Yes Yes No No

Help Document Yes Yes Yes Yes Yes

Server CLI Console Yes Yes Yes No No

Shutdown Yes Yes Yes No No

Uninstall Yes Yes Yes Yes Yes

Yes: Start menu item is created

No: Start menu item is not created

*: If [Server only] is selected on the [Select Component] screen, the [Select Client

Environment] screen is not displayed.



60



61

11. Pre-setting of Adapters

For using each adapter, pre-setting might be necessary such as installation of the library etc.

For more details, refer to the following descriptions or HULFT Integrate Help.

11.1. Access Adapter

11.1.1. Access 2013/2010 adapter

Library installation is not necessary in Access adapter.



62

11.2. DB2 Adapter

11.2.1. DB2 V11.1 adapter

Required library

➢ db2jcc4.jar

Supported driver version


How to get library

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

below DB2 installation directory.

Installation procedure

1. Stop HULFT Integrate and various client applications.

2. Copy the required libraries under

$INTEGRATE_HOME/server/plugin/data_processing/modules/db2_111_adapter

directory.


11.2.2. DB2 V10.5 adapter

Required library

➢ db2jcc4.jar



How to get library

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

below DB2 installation directory.




63



$INTEGRATE_HOME/server/plugin/data_processing/modules/db2_105_adapter

directory.


11.2.3. DB2 for i 7.3 / 7.2 adapter

Required library

➢ jt400.jar

How to get library

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



2. Copy required library group under the directory

$INTEGRATE_HOME/server/plugin/data_processing/modules/db2udb_iseries<version

>_adapter.

<version> indicates the version of DB2 for i. 72 for 7.2 and 73 for 7.3.




64

11.3. MySQL Adapter

<version> shows the latest version.

11.3.1. MySQL 8.0 adapter

Required library

➢ mysql-connector-java-8.0.<Version>.jar

Supported Version of the driver

➢ MySQL Connector/J 8.0.<Version>

How to get library

➢ Download JDBC driver from MySQL Connector/J 8.0 Downloads site.




$INTEGRATE_HOME/server/plugin/data_processing/modules/mysql80_adapter

directory.

3. Launch IntegrateServer and Integrate Studio.


Required library

➢ mysql-connector-java-5.1.<Version>-bin.jar



How to get library



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




65




directory.



Required library




How to get library






directory.





66

11.4. Oracle Adapter

11.4.1. Oracle 18c Adapter

Required library

➢ ojdbc8.jar


➢ Oracle JDBC Driver 18.3.0

How to get library

➢ Download JDBC driver for version 18c from Oracle Software Downloads site.




$INTEGRATE_HOME/server/plugin/data_processing/modules/oracle18c_adapter

directory and

$INTEGRATE_HOME/server/plugin/data_processing/modules/xa_oracle18c_adapter

directory.

3. Launch IntegrateServer and Integrate Studio.

11.4.2. Oracle 12cR2 Adapter

Required library

➢ ojdbc8.jar



How to get library

➢ Download JDBC driver for version 12cR2 from Oracle Software Downloads site.


https://www.oracle.com/database/technologies/appdev/jdbc.html




67



$INTEGRATE_HOME/server/plugin/data_processing/modules/oracle12cr2_adapter

directory and

$INTEGRATE_HOME/server/plugin/data_processing/modules/xa_oracle12cr2_adapter

directory.


11.4.3. Oracle 12c Adapter

Required library

➢ ojdbc7.jar



How to get library

➢ Download JDBC driver for version 12.1 from Oracle Software Downloads site.




$INTEGRATE_HOME/server/plugin/data_processing/modules/oracle12c_adapter

directory and

$INTEGRATE_HOME/server/plugin/data_processing/modules/xa_oracle12c_adapter

directory.


11.4.4. Oracle 11gR2 Adapter

Required library

➢ ojdbc6.jar





68


How to get library





$INTEGRATE_HOME/server/plugin/data_processing/modules/oracle11gr2_adapter

directory and

$INTEGRATE_HOME/server/plugin/data_processing/modules/xa_oracle11gr2_adapter

directory.


11.4.5. Oracle OCI Adapter

Required library

Oracle Database Client JDBC driver

11g Release 2(11.2) ojdbc6.jar


➢ It depends on the Oracle client version to use.

How to get library

➢ It is usually placed in jdbc\lib directory under the directory where your client tool is

installed.

In the case of Oracle 11g Release 2, it is placed at

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




$INTEGRATE_HOME/server/plugin/data_processing/modules/oracle_oci_adapter

directory.




69


11.5. PostgreSQL Adapter

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

11.6. SQL Server Adapter

11.6.1. SQL Server 2017 Adapter

Required library

➢ mssql-jdbc-6.2.2.jre8.jar

➢ sqljdbc_auth.dll (when using Windows authentication)


➢ Microsoft JDBC Driver 6.2 for SQL Server

How to get library

➢ Download Microsoft JDBC Driver 6.2 for SQL Server from Microsoft Download Center.



2. Copy mssql-jdbc-6.2.2.jre8.jar directly under the directory

$INTEGRATE_HOME/server/plugin/data_processing/modules/sqlserver2017_adapter

3. When you use Windows authentication, copy sqljdbc_auth.dll to a directory included in

Windows system paths of the computer where the JDBC driver is installed.



Required library

➢ sqljdbc42.jar

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



70




How to get library




2. Copy sqljdbc42.jar to


directory.





Required library

➢ sqljdbc42.jar




How to get library










71

directory.




11.6.4. SQL Server 2012 JDBC Adapter

Required library

➢ sqljdbc42.jar




How to get library






directory.




11.6.5. SQL Server 2008 R2 JDBC Adapter

Required library

➢ sqljdbc42.jar






72


How to get library





$INTEGRATE_HOME/server/plugin/data_processing/modules/sqlserver2008r2_adapte

r directory.




11.6.6. SQL Server 2008 JDBC Adapter

Required library

➢ sqljdbc42.jar




How to get library






directory.







73


11.6.7. SQL Server 2008 ODBC Adapter

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

11.7. JDBC Adapter

Required library

➢ Inquire DBMS vendor connected with JDBC adapter.

How to get library

➢ Inquire DBMS vendor connected with JDBC adapter.



2. Copy required library group under the directory

$INTEGRATE_HOME/server/plugin/data_processing/modules/jdbc_adapter


11.8. ODBC Adapter

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

11.9. NeoCore Adapter

11.9.1. NeoCore 3.1 adapter

Required library

➢ xmsclient.jar

How to get library

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

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



74




$INTEGRATE_HOME/server/plugin/data_processing/modules/neocore31_adapter

directory.



Required library

➢ xmsclient.jar

How to get library







directory.



Required library

➢ neoHTTPConnection.jar

How to get library






75




directory.


11.10. Thunderbus DB Agent Adapter

In Thunderbus DB Agent adapter, it is not necessary to install library.

11.11. Dr.Sum EA Adapter

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

11.12. Dynamics CRM Adapter

In Dynamics CRM Adapter, it is not necessary to install library.

11.13. IBM Domino Adapter

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

11.13.1. IBM Domino 9.0 Adapter

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



76

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



2. Copy the required library group under the directory

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


11.14. IBM Notes Adapter

11.14.1. IBM Notes 9.0 Adapter

Required software

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

that IntegrateServer is running.

Setting up system environment variable "PATH"

➢ After installing Notes client, add path of Notes client installation directory to Windows

system variable.

Setting Notes port

➢ 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 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.

11.15. SAP Adapter

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



77

For more details, refer to "HULFT Integrate SAP EICS Install Guide" bundled to installer.

11.16. SAP BC Adapter

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

11.17. Tableau Adapter

Output Hyper File and Output TDE File require different libraries.

Refer to "Output Hyper File" or "Output TDE File" to install.

11.17.1. Output Hyper File

Required library

boost_chrono-vc140-mt-1_60.dll

boost_date_time-vc140-mt-1_60.dll

boost_filesystem-vc140-mt-1_60.dll

boost_system-vc140-mt-1_60.dll

boost_thread-vc140-mt-1_60.dll

concrt140.dll

icudt44.dll

icuin44.dll

icuio44.dll

icuuc44.dll

libpq.dll

metrics2.dll

msvcp140.dll

TableauCommon.dll

TableauHyperExtract.dll

tablibeay32.dll

tabssleay32.dll

tabsys.dll

tbb.dll

ucrtbase.dll

vccorlib140.dll



78

vcruntime140.dll

hyper/hyperd.exe

hyper/hyperd_sse2.exe

hyper/hyperdstarter.exe

hyper/icudt44.dll

hyper/icuin44.dll

hyper/icuio44.dll

hyper/icuuc44.dll

hyper/jemalloc.dll

hyper/tablibeay32.dll

hyper/tabssleay32.dll

hyper/tabsys.dll

hyper/tabz.dll

hyper/tbb.dll

hyper/zstd.dll

Directory where a library stored

The required libraries are stored in

$INTEGRATE_HOME/server/lib/tableau_adapter/windows_hyper/bin.


The library for Output TDE File and that for Output Hyper File cannot be used

simultaneously. If you have installed the libraries for Output TDE File, delete the libraries

stored under $INTEGRATE_HOME/server/bin directory before installing libraries for

Output Hyper File.

1. Stop IntegrateServer and Integrate Studio.

2. Download Visual C++ Redistributable Packages from Microsoft Download Center.

3. Add $INTEGRATE_HOME/server/lib/tableau_adapter/windows_hyper/bin to the en

vironment variable "PATH" of OS on which IntegrateServer is running.

Example: When $INTEGRATE_HOME is set as C:\Program Files\hulft\integrate, a

dd C:\Program Files\hulft\integrate\server\lib\tableau_adapter\windows_hyper\b

in to the environment variable "PATH".


https://www.microsoft.com/en-US/download/details.aspx?id=40784



79

11.17.2. Output TDE File

Required library

boost_chrono-vc100-mt-1_55.dll

boost_date_time-vc100-mt-1_55.dll

boost_system-vc100-mt-1_55.dll

boost_thread-vc100-mt-1_55.dll

DataExtract.dll

icudt44.dll

icuin44.dll

icuuc44.dll

metrics2.dll

msvcp100.dll

msvcr100.dll

tbb.dll

tdeserver64.exe

Directory where a library stored

The required libraries are stored in

$INTEGRATE_HOME/server/lib/tableau_adapter/windows.


1. Stop IntegrateServer and Integrate Studio.

2. Copy the required library group under the $INTEGRATE_HOME/server/bin directory.


11.18. Universal Connect/X Adapter

In Universal Connect/X adapter, it is not necessary to install library.

11.19. Report Director Enterprise Adapter

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



80

11.20. List Creator Adapter

11.20.1. List Creator V9.1 Adapter

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

IntegrateServer "IntegrateServer.lax". Configure the settings with the below procedure.

Setting procedure


2. Open $INTEGRATE_HOME/server/bin/IntegrateServer.lax in text editor.

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 IntegrateServer.lax.


Settings during remote connection

To output the form from the form output server, the following product needs to be installed

on OS that IntegrateServer operates.

<ListCreator installation directory >/classes/fjoajif.jar

<ListCreatorinstallation directory>/classes/fjoaweb.jar

<ListCreatorinstallation directory>/remoteprint/requester/lib/ardus.jar

<ListCreatorinstallation directory>/remoteprint/requester/lib/ardusobj.jar

<ListCreatorinstallation directory>/remoteprint/requester/lib/ArdusRepository.jar

<ListCreatorinstallation directory>/remoteprint/requester/lib/jomcli.jar

<ListCreatorinstallation directory>/remoteprint/requester/lib/jomrequester.jar

<ListCreatorinstallation directory>/remoteprint/requester/lib/jomrequester.jar



81

➢ Interstage List Creator Connector

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

connector is used in IntegrateServer 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.

11.21. FTP Adapter

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

11.22. JMS Adapter

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

$INTEGRATE_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.

11.23. Rest Adapter

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

11.24. Web Adapter

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

11.25. Web Services Adapter

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 $INTEGRATE_HOME/server/system/common/lib, save it



82

and then, reboot IntegrateServer.

11.26. Mail adapter

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

11.27. Amazon Web Services Adapter

11.27.1. Amazon Aurora for MySQL 5.7 Adapter

In Amazon Aurora for MySQL 5.7 adapter, it is not necessary to install library.

11.27.2. Amazon Aurora for MySQL 5.6 Adapter

In Amazon Aurora for MySQL 5.6 adapter, it is not necessary to install library.

11.27.3. Amazon DynamoDB Adapter

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

11.27.4. Amazon EC2 Adapter

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

11.27.5. Amazon RDS for MySQL 8.0 Adapter

Required library

➢ mysql-connector-java-8.0.<Version>.jar



How to get library



1. Stop DataSpider Servista and various client applications.




83


$DATASPIDER_HOME/server/plugin/data_processing/modules/amazon_rds80_adapte

r directory.

3. Launch DataSpiderServer and DataSpider Studio.


Required library




How to get library






r directory.

3. Start DataSpiderServer and DataSpider Studio.


Required library




How to get library







84




r directory.


11.27.8. Amazon RDS for Oracle 12c Adapter

Required library

➢ ojdbc7.jar



How to get library





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

_adapter directory.


11.27.9. Amazon RDS for Oracle 11g R2 Adapter

Required library

➢ ojdbc6.jar



How to get library






85




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

r2_adapter directory.


11.27.10. Amazon RDS for PostgreSQL 10 / 9.5 / 9.4 Adapter

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

11.27.11. Amazon RDS for SQL Server 2017 Adapter

Required library




How to get library





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

2017_adapter



Required library


https://www.microsoft.com/ja-jp/download/details.aspx?id=55539



86



How to get library






2016_adapter



Required library

➢ sqljdbc42.jar



How to get library






2014_adapter directory.



Required library

https://www.microsoft.com/ja-jp/download/details.aspx?id=55539




87

➢ sqljdbc42.jar



How to get library






2012_adapter directory.


11.27.15. Amazon Redshift Adapter

Required library

➢ RedshiftJDBC42-1.<version>.jar


➢ Amazon Redshift JDBC Driver 1.<version> (JDBC 4.2-compatible driver)

To get a library

➢ Download JDBC driver from Amazon Redshift JDBC Driver Downloads site.


1. Stop DataSpiderServer and various client applications.


$DATASPIDER_HOME/server/plugin/data_processing/modules/amazon_redshift802_a

dapter directory.



https://docs.aws.amazon.com/redshift/latest/mgmt/configure-jdbc-connection.html



88

11.27.16. Amazon S3 Adapter

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

11.27.17. Amazon SimpleDB Adapter

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

11.27.18. Amazon SQS Adapter

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

11.28. Cloudn Adapter

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

11.29. G Suite Adapter

11.29.1. Gmail Adapter

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

11.29.2. Google Drive Adapter

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

11.29.3. Google Sheets Adapter

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

11.30. kintone Adapter

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



89

11.31. Nifty Cloud Adapter

11.31.1. Nifty Cloud Adapter

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

11.31.2. Nifty Cloud Storage Adapter

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

11.32. Hadoop HDFS Adapter

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

11.33. HULFT Adapter

11.33.1. HULFT8 / HULFT7 Adapter

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



90

12. About the port used by HULFT Integrate

HULFT Integrate 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 IntegrateServer and the Integrate 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: ”Integrate Studio cannot be connected to IntegrateServer (3)” “My project takes

too long to start up in Integrate Studio(2)”

A RMI port is specified as follows.

Config file

➢ Server side

$INTEGRATE_HOME/server/conf/system.properties

➢ Client side

$INTEGRATE_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.



91

13. Start and Shutdown of IntegrateServer

13.1. Start IntegrateServer

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

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

2. In UNIX/Linux version, when the environment variable CLASSPATH is set, delete it.

3. Start IntegrateServer.

➢ Windows Version

In “HULFT Integrate <Version> Select “IntegrateServer” from "Windows start

menu".

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

Run $INTEGRATE_HOME/server/bin/IntegrateServer.exe.

➢ UNIX/Linux Version

Run $INTEGRATE_HOME/server/bin/IntegrateServer

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

the Server makes the index of the help.

4. When IntegrateServer starts successfully, following messages are output to server.log and

IntegrateServer console.

--- |INFO| --- |INFO|***************************************************************** --- |INFO|***************************************************************** --- |INFO|*********************** Integrate Server *********************** --- |INFO|***************************************************************** --- |INFO|***************************************************************** --- |INFO|Starting Integrate Server... --- |INFO|Loading system. System name: [Integrate 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|Integrate Server was successfully started.

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



92

13.2. Restart IntegrateServer

To restart IntegrateServer, execute either of following procedures.

Common to Windows Version & UNIX/Linux Version

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

Integrate Studio.

Windows Version

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

➢ (When registered as Windows service) Restart Windows service.

UNIX/Linux Version

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

"shutdown -r".

13.3. Stop IntegrateServer

To stop IntegrateServer, execute either of following procedures.

Windows Version

➢ In “HULFT Integrate <Version>” Select “Shutdown” from the start menu.

➢ Press [Shutdown] button in [Others] tab of [IntegrateServer Settings], Control

Panel, Integrate Studio.

➢ (When registered as Windows service) Stop Windows service.

UNIX/Linux Version

➢ Run $INTEGRATE_HOME/server/bin/Shutdown



93

14. Launch and Exit Integrate Studio

This chapter explains how to launch and exit Integrate Studio. For details on launching and

exiting Integrate Studio for Web, refer to "Launch and Exit Integrate Studio for Web".

14.1. Launch Integrate Studio

Launch Integrate Studio by either of the following ways.

➢ Select "HULFT Integrate <version>" - "Integrate Studio" from Windows Start menu.

➢ Run $INTEGRATE_HOME/client/bin/IntegrateStudio.exe directly.

When Integrate Studio launches first time, it synchronizes modules with IntegrateServer.

After synchronization, you need to restart Integrate Studio.

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

when Integrate Studio is launched for the first time. Do not restart Integrate Studio

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

14.1.1. Login

Login dialog is displayed if succeeded in launching Integrate Studio.

Enter user name and password, then press [Login] button. If succeeded to log in, desktop

screen of Integrate Studio is displayed.

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

When the user with administrator rights tries to log in while users cannot log in because the

maximum number of licenses is exceeded, "Exceeds the maximum number of clients connected"

dialog displays. Make the user logging in to the clients for development log out, or close the

session from the displayed session list, after that, log in again.

14.1.2. Edit Server List

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

login dialog and open "Edit server list" screen.



94

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

button. Return to login dialog with applying edited contents.

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

will try to log in is different from server connected when Studio launches, you need to restart

Integrate Studio so that module may synchronize. After pressing [Login] button, exit Integrate

Studio and launch again.

Moreover, multiple connection destinations can be saved. If you add new connection destination,

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

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

as the name of connection destination, change the name of connection destination so that

[Apply] button will be enabled.

14.1.3. When Failed to Connect to Server

If Studio fails to connect to Integrate 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 Integrate Studio.

Exit Integrate Studio according to screen and launch again.

If you press [Cancel] button, Integrate Studio tries to reconnect to IntegrateServer by using

the settings before modification.

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 started 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".



95

14.2. Exit Integrate Studio

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.



96

15. Launch and Exit Integrate Studio for Web

This chapter explains how to launch and exit Integrate Studio for Web. For details on launching

and exiting Integrate Studio, refer to "Launch and Exit Integrate Studio".

15.1. Execution environment of Integrate for Web

To use Integrate Studio for Web, the following execution environments are needed. Before

launching Integrate Studio for Web for the first time, install the following.

➢ Microsoft .NET Framework later than 4.7

Download .NET Framework 4.7 from Microsoft Download Center.

➢ StudioLauncher

StudioLauncher can be downloaded from the following URL.

http://<the host name of the machine on which IntegrateServer is running or IP

address>:<the port number of IntegrateServer>/WebStudio/StudioLauncherSetup.exe

15.2. Launch Integrate Studio for Web

Launch Integrate Studio for Web by either of the following ways.

➢ Access the website of Integrate Studio for Web from the browser.

1. Access the following URL.

http://<the host name of the machine on which IntegrateServer is running or IP

address>:<the port number of IntegrateServer>/WebStudio/

2. Press [Start Studio for Web] button.

➢ Launch from Windows Start menu

1. Select "Integrate Studio for Web" from Windows Start menu.

2. Press [Start Studio for Web] button.



97

15.2.1. Login

When launching Integrate Studio for Web succeeds, displays login dialog.

Enter user name and password, then press [Login] button. When you succeed to log in, then

displays start screen of Integrate Studio for Web.

Language which is used in Integrate Studio for Web is selected from [Language].

When the user with administrator rights tries to log in while users cannot log in because the

maximum number of licenses is exceeded, "Exceeds the maximum number of clients connected"

dialog displays. Make the user logging in to the clients for development log out, or close the

session from the displayed session list, after that, log in again.

15.3. Exit Integrate Studio for Web

Exit Integrate Studio for Web by either of the following ways.

1. Press [x] button in Integrate Studio for Web.

2. In confirmation dialog, press [OK] button.



98

16. Start HULFT Integrate Help

You can refer help by a web browser.

Method of starting HULFT Integrate help is as follows.

1. Launch IntegrateServer.

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

IntegrateServer is running>:<The port number of

IntegrateServer>/integrate/doc/help/index.html".

➢ Windows Version

Select "HULFT Integrate <version>" - "Help Document" from Windows Start

menu.



99

17. Service Development

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

development and application necessary for developing the services in HULFT Integrate is

described in the below document.

Concepts, functions, terms and simple scripting procedure.

➢ In the page "Basic knowledge of the service" of HULFT Integrate Help.

Practical concepts and functions of service development.

➢ In the page "Development of Service" of HULFT Integrate Help.

Various concepts and tools of service operation.

➢ In the page "Service Operations" of HULFT Integrate Help.

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

HULFT Integrate for the first time, read the below.

➢ "HULFT Integrate tutorial guide"



100

18. Specifications and Limitations at

Uninstallation

18.1. General

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,

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

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

Delete manually. (DSS-14791)



101

19. Uninstall HULFT Integrate

Use uninstaller when you uninstall HULFT Integrate. For details, refer to "Uninstallation

procedure of HULFT Integrate".

When you uninstall Integrate Studio for Web, you must uninstall HULFT Integrate Studio

Launcher. For details, refer to "Uninstallation procedure of HULFT Integrate Studio Launcher".

Before uninstallation, ensure that the various applications of HULFT Integrate have

been stopped.

19.1. Uninstallation procedure of HULFT Integrate

1. Start uninstaller in following way.

In Windows version, start uninstaller by either of the following ways.

➢ In "HULFT Integrate <version>" Select "Uninstall" from Windows Start menu.

➢ Run $INTEGRATE_HOME/Uninstall/Uninstall.exe.

In UNIX/Linux version, start uninstaller by the following way.

➢ Run $INTEGRATE_HOME/Uninstall/Uninstall

2. On "Introduction" screen, press [Uninstall] button for GUI method or press [Enter] button

for CUI method.

3. If some directories could not be deleted, they are displayed on the screen. After completing

uninstallation, confirm the directories and files under $INTEGRATE_HOME and delete them

manually.

In Gui method, press [Done] button on "Uninstall Complete" screen to end uninstaller.

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

also delete the database instance for the Repository DB.



102

19.2. Uninstallation procedure of HULFT Integrate Studio

Launcher

1. From "Programs and Features" of Windows, select [HULFT Integrate Studio Launcher].

2. Press [Uninstall].

3. Uninstall according to the displayed dialog.

4. Confirm the contents of the following directories and deletes them manually.

%LocalAppData%/HULFT INC/HULFT Integrate

%LocalAppData/% is the environment variable of Windows system.



103

20. Troubleshooting

20.1. Junk character in installer

Phenomenon

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.

Counter-measure

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



104

20.2. Installing or uninstalling HULFT Integrate by using

CUI installer fails

Event

When you try to install or uninstall HULFT Integrate by using CUI installer, after selecting the

language, displays the following error and the operation fails.

➢ "Installer User Interface Mode Not Supported"

Possible causes

The possible cause of this error is existing both of the following packages, by the operation such

as installing JDK1.7.0.

➢ xorg-x11-fonts-Type1

➢ stix-fonts

Counter-measure

Delete one of, or both of the following packages, after that, install or uninstall HULFT Integrate

again.

➢ xorg-x11-fonts-Type1

➢ stix-fonts



105

20.3. IntegrateServer cannot be started

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

IntegrateServer cannot be started

Event

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

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

Possible causes

Following causes are possible.

➢ The license file is not in $INTEGRATE_HOME/server/lic.

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

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

Counter-measure

Place the correct license file in $INTEGRATE_HOME/server/lic and start IntegrateServer.

20.3.2. When restarting IntegrateServer, "LifecycleException:

Protocol handler initialization failed" error occurs and it fails

to restart

Event

At reboot of IntegrateServer, "LifecycleException: Protocol handler initialization failed:

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

error occurs and IntegrateServer fails to reboot.

Possible causes

IntegrateServer process may not have stopped correctly.

Counter-measure

➢ Windows version



106

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

IntegrateServer.

➢ UNIX/Linux version

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

IntegrateServer.



107

20.4. Integrate Studio cannot be connected

20.4.1. Integrate Studio cannot be connected to

IntegrateServer (1)

Event

Integrate Studio fails to connect to IntegrateServer 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 IntegrateServer and Integrate 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.

Counter-measure

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

Integrate 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



108


IntegrateServer (2)

Event

Integrate Studio fails to connect to IntegrateServer.

Possible causes

If multiple network cards are installed in the machine that IntegrateStudio operates or IP

address of the machine is allocated by DHCP, the machine in which IntegrateServer operates

might not refer to IntegrateStudio properly.

Counter-measure

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

system.properties file of Integrate Studio and reboot Studio.

If multiple network cards are installed in the machine that IntegrateServer operates, specify

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

system.properties file of IntegrateServer and reboot IntegrateServer.

For details about setting method, etc., refer to "Property Reference" page of HULFT

Integrate Help.


IntegrateServer (3)

Phenomenon

Integrate Studio fails to connect to IntegrateServer.

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 IntegrateServer is running.

Counter-measure

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

Refer to "About the port used by HULFT Integrate" for details about configurations.



109

20.5. It takes long time to open My Project

20.5.1. My project takes too long to start up in Integrate Studio

(1)

Event

If multiple network cards are installed in operating system that IntegrateClient operates, if you

start opening My Projects of Integrate Studio, it takes long time.

Possible causes

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

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

IntegrateServer.

Remedies

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

system.properties file of Integrate Studio and restart Studio.

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

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

system.properties file of IntegrateServer and restart IntegrateServer.

Refer to "Property Reference" of HULFT Integrate help for details such as setting method

etc.

20.5.2. My project takes too long to start up in Integrate Studio

(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.



110

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 IntegrateServer or

Integrate 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 HULFT Integrate”, for details about configurations.



111

HULFT Integrate 4.2 Install Guide The 2nd edition: April 3 2019 HULFT, Inc.

1820 Gateway Drive, Suite 120

San Mateo, CA 94404

www.hulftinc.com

Documents

4.2 Install Guide€¦ · This document describes how to install and setup the new version of HULFT Integrate 4.2. Refer “HULFT Integrate Upgrade Guide” for the upgrade from the