DataSpider Servista Tutorial Guide - HULFT Support · 2019. 6. 20. · Sample data used in this guide and the completed sample project. ... Insert sample data into PostgreSQL as follows.

Tutorial Guide

Document Release Date: January 8 2019 (The 1st Edition)

Copyright© 2019 HULFT, Inc. All rights reserved.

HULFT Integrate Tutorial Guide


2

Table of Contents 1. Before Use ............................................................................................................. 4

1.1. Precautions ....................................................................................................... 5

1.1.1. Copyright Notice .......................................................................................... 5

1.1.2. Trademarks ................................................................................................. 5

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

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

2. Composition of tutorial ............................................................................................. 8

3. Preparation .......................................................................................................... 11

3.1. How to prepare sample data ............................................................................. 11

3.2. Inserting sample data into PostgreSQL ............................................................... 11

4. Developing with HULFT Integrate ............................................................................ 13

4.1. Development Procedure ................................................................................... 13

5. Exercise using Scenarios ........................................................................................ 14

5.1. Scenario1 “DB to CSV” ..................................................................................... 14

5.1.1. Scenario Description .................................................................................. 14

5.1.2. Launching HULFT Integrate ........................................................................ 15

5.1.3. Creating a project and script ....................................................................... 17

5.1.4. Reading data from PostgreSQL Database ...................................................... 19

5.1.5. Writing Records to a CSV file ....................................................................... 24

5.1.6. Completion of script ................................................................................... 27

5.1.7. Saving the project ..................................................................................... 28

5.1.8. Executing script ......................................................................................... 29



3

5.1.9. Registering the project to the server ............................................................ 32

5.1.10. Configuring a file trigger .......................................................................... 34

5.1.11. Firing the file trigger ............................................................................... 38

5.2. Scenario 2 “Excel to DB” .................................................................................. 40

5.2.1. Scenario Description .................................................................................. 40

5.2.2. Creating a project and a script .................................................................... 41

5.2.3. Extracting Excel data .................................................................................. 41

5.2.4. Writing data to PostgreSQL database ........................................................... 44

5.2.5. Adding a Mapper ....................................................................................... 47

5.2.6. Calculation in a Mapper .............................................................................. 49

5.2.7. Extracting data by condition in Mapper ......................................................... 51

5.2.8. Completion of script ................................................................................... 57

5.2.9. Executing script ......................................................................................... 57

5.2.10. Registering the project to the server ......................................................... 59

5.2.11. Configuring a Schedule Trigger ................................................................. 59

5.2.12. Confirming firing schedule for trigger and execution result ........................... 64

5.2.13. Holiday Settings ..................................................................................... 64

6. Log management .................................................................................................. 68

6.1. Configuring Logs ............................................................................................. 68

6.1.1. Configuring My Logs .................................................................................. 68

6.1.2. Configuring the server log .......................................................................... 71



4

1. Before Use

HULFT Integrate Tutorial aims at introducing the basic usages of HULFT Integrate to those

developers who need to develop services using HULFT Integrate.

Please note that product images found in this document may not be the same, depending on

the product version used.



5

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 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 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 conversion of information, such as trademarks, shown on the pages of this

document is strictly prohibited.



6

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



7

1.3. About the Icons Used in This Guide

This Guide uses the following icons in its explanation.

Icon Description

Indicates that there are hints about operations or configurations.

Indicates that there are warnings about operations or configurations.

Indicates that there are detailed descriptions in other resources.



8

2. Composition of tutorial

Below files are located in “IntegrateTutorial” directory which is in the same hierarchy as product

installer.

● HULFT_INTEGRATE_42_TutorialGuide_en.pdf

This guide.

● HULFT_INTEGRATE_42_TUTORIAL_en.zip

Sample data used in this guide and the completed sample project.

If you expand HULFT_INTEGRATE_42_TUTORIAL_en.zip, you can find

“HULFT_INTEGRATE_TUTORIAL” folder.

Folder structure is as follows.

● Samples

This directory contains sample data used in this guide. For details on usage, refer to “How

to prepare sample data”.

● Sample project

This directory contains completed sample project files. It has 2 projects (Scenario 1 and

Scenario 2) on scenario basis and upload the project with the below procedure to view the

completed project.

1. Open “My Projects” by double clicking the icon which is located on the desktop of

Integrate Studio.



9

2. In “My Projects” menu, select [Upload from local] found under [File].

3. Select the project to upload and click [Open]. Here the selected file is Scenario 1.

4. Click [OK] as such in the “Upload project” dialog displayed.



10

5. Project uploaded is displayed in the right window pane of My Project.

Also, upload Scenario 2 as well. Double click the project uploaded in “My Projects” to open

designer, and the project contents are displayed here.



11

3. Preparation

This document requires the installation of the following softwares.

⚫ HULFT Integrate 4.2

⚫ Microsoft Office Excel

As a database, PostgreSQL 9.6 is used in this document. Download it from the download page and

install it.

If you use a database other than PostgreSQL, you need not install it. In that case, replace your

database with it in this document.

3.1. How to prepare sample data

“HULFT_INTEGRATE_42_TUTORIAL_en.zip” contains the sample data used through this tutorial.

“HULFT_INTEGRATE_42_TUTORIAL_en.zip” is found in “IntegrateTutorial” directory which is in

the same hierarchy as product installer.

Please follow the instruction below to copy the sample data to the proper location.

⚫ Copy from

➢ “Samples” - “tutorial” folder which is found in the “HULFT_INTEGRATE_TUTORIAL” folder

when HULFT_INTEGRATE_42_TUTORIAL_en.zip is expanded.

⚫ Copy to

➢ $INTEGRATE_HOME/server/samples

3.2. Inserting sample data into PostgreSQL

Insert sample data into PostgreSQL as follows.

1. Start pgAdmin 4.

2. Double click “PostgreSQL 9.6” in the object browser tree.

“Connect to Server” dialog will open. Then enter the database administrator’s password and

https://www.postgresql.org/download/



12

press [OK] button.

3. “Databases” will be displayed under “PostgreSQL 9.6” in the object browser tree. Then select

“Create” – “Database...” from the right-click menu.

“Create – Database” windows will open, and configure as follows.

* [Database] : “dataspider_tutorial”

* [Owner] : “postgres”

Press [Save] button after configuration.

4. “dataspider_tutorial” will be displayed under “Databases” in the tree, and select “Query Tool...”

from the right-click menu.

5. Open $INTEGRATE_HOME/server/samples/tutorial.sql with a editor, copy the whole contents

and paste it at the query input field in pgAdmin 4.

6. Press button.

7. SQL will be executed, and confirm two tables are added.



13

4. Developing with HULFT Integrate

4.1. Development Procedure

The following diagram illustrates the iterative development procedure practiced when developing

services for HULFT Integrate.

This tutorial will guide you through the steps to create Integrate services and their deployment.

Refer to HULFT Integrate Help to know the environment settings.

From the next chapter onwards, development procedure will be explained using the tutorial

scenarios.



14

5. Exercise using Scenarios

Using the scenarios prepared, this chapter will explain procedures, methods and tips to remember

when developing services.

5.1. Scenario1 “DB to CSV”

5.1.1. Scenario Description

In scenario1, you will create a service that polls a directory for a new file, and when it is detected,

database records are extracted from PostgreSQL database which are then written to a file in CSV

format.

Process flow and process details are as follows.

•Fire trigger file when "/samples/tutorial/trigger/triggerFile" is newly created.

Read

•Read the data from table [Products] of PostgreSQL database

"dataspider_tutorial".

Write

•Output the read data to CSV file

"$INTEGRATE_HOME/server/samples/tutorial/products.csv".

•Add header to .CSV.

Fire

trigger



15

5.1.2. Launching HULFT Integrate

1. Launch IntegrateServer.

The server process can be started from Windows “Start” menu “HULFT Integrate 4.2” –

“IntegrateServer”.

In case service is not registered, a message, “Integrate Server started successfully” can be

confirmed in the console outputs when the service is successfully launched. In case service is

registered, make sure it is “Started” in IntegrateServer Services in Windows service list.

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

(continue)

--- |INFO|Starting service of module [ScriptRunner Container]...

--- |INFO|Starting service of module [DataProcessingComponent Manager]...

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



16

2. Launching Integrate Studio.

Select “HULFT Integrate 4.2” – “Integrate Studio” from Windows Start menu.

When Studio is launched initially, module synchronization is done with IntegrateServer.

Restart the studio after the completion of synchronization.

When the login dialog prompts and asks for the [User] and [Password], specify “root” and

“password” respectively, and click [Login] to enter the Integrate Studio.

When logged in successfully, Studio window is displayed as shown below.



17

5.1.3. Creating a project and script

A project can be created in Integrate Studio.

A project is a manageable unit consists of HULFT Integrate scripts. In HULFT Integrate, processes

can be grouped into two manageable tiers, namely projects and scripts. Multiple scripts are

managed together in one project.

1. To create a new project, double click on “New project” icon.

2. In [New Project] screen, specify [Scenario1] for [Project Name].

Check the check box [Create script] and click [Next >] to proceed.



18

3. For [Script name], specify [DB2CSV] and click [Finish].

Designer launches, project [Scenario1] and the script [DB2CSV] just created is displayed.



19

5.1.4. Reading data from PostgreSQL Database

1. In the Tool palette, expand the [Database] stack menu and drag the [Read Table] component

found in [PostgreSQL] category and drop it on the canvas area.

2. Configure the settings to read the data from table in the [New Read Table Operation] property

window displayed.

Specify [DB Read Process] for [Name].



20

3. Configure connection settings for your PostgreSQL database.

Click [Add] in [Destination] list.

New PostgreSQL Connection Setting dialog will open, and select ”PostgreSQL 9.6 connection

settings” at [Type]. After that, configure as follows.

● [Name] : “Tutorial Connection Setting”

● [Host name] : The host name or IP address of the environment in which PostgreSQL 9.6 has

been installed.

● [Port number] : The port number of your PostgreSQL 9.6

● [Database name] : “dataspider_tutorial”

● [User name] : “postgres”

● [Password] : The password of PostgreSQL user “postgres”



21

Click [Connection test] and confirm the connectivity.

Click [OK] when [Connection success] dialog prompts.

If the connection test failed, error contents can be checked by clicking [Details].

Check the following conditions.

* The values of [Host name], [Port number], [Database name], [User name], and [Password],

are correct.

* PostgreSQL 9.6 is running.

* The port of PostgreSQL 9.6 is not blocked by a firewall.

And, click [Finish] button in [New PostgreSQL 9.6 Connection Setting] screen.

4. Select [products] for [Table name].

Column names and types defined in its schema are presented in the table at the bottom.



22

[Table Browser] screen is displayed by clicking [Launch table browser].

In table browser, number of data within the table and table information is displayed.

SELECT statement is issued for the specified table by clicking [Extraction test]. As a result,

the number of data obtained is displayed.



23

5. If [Finish] is clicked, property window closes and [DB Read Process] icon is deployed on the

script canvas.

With this, the configuration for reading data from PostgreSQL gets completed.



24

5.1.5. Writing Records to a CSV file

1. In Tool palette, expand the [File] stack menu and drag the [Write CSV File] component found

in [CSV] category and drop it on the canvas area.



25

2. Configure the settings in the [New Write CSV File Operation] property window displayed, as

follows.

●[Name] : [CSV Write Process]

●[Input data] : [DB Read Process]

●[File] : “/sample/tutorial/Products.csv”

Among the components which are deployed in the script canvas, those which can be used

as input are presented in [Input Data] list.

Moreover, if [Update column list] is clicked, [Column list] is generated by obtaining the column

name from the 1st row of Products.csv.

Now, select [Write settings] tab.

Check [Insert column names into first row].



26

If [Insert column names into first row] is checked on, [Column name] of [Column list] is

written to the 1st line of CSV file.

3. If [Finish] is clicked, property setting dialog closes and [CSV Write Process] icon is deployed in

the script canvas.

[DB Read Process] and [CSV Write Process] icons are connected by data flow (dotted yellow

line).

With this, the configuration for writing CSV file gets completed.



27

5.1.6. Completion of script

To configure the order of the execution, connect each component by the process flow line drawn as

an icon is dropped on to another on the script canvas.

1. First click the [DB Read Process] icon and drag it till [CSV Write Process] icon. Then release the

mouse button when the icon is surrounded in a blue dotted rectangle.

2. In the same manner, complete the drawing of the process flow from [Start], [DB Read

Process] via [CSV Write Process] to the [End].

All of the components are connected with lines as shown in the diagram when completed.

Notice that icon has an asterisk (*) on its right top corner. The asterisks indicate that the

Script Editor has unsaved changes.



28

5.1.7. Saving the project

Save the project and script.

From designer menu, it is possible to select [File] - [Save project] or click [Save project] icon.

When a script is saved and it is compilable, then the script is built simultaneously. When a

script is saved but it is not compilable, then the script is saved in editing state.

Run [Build script] to just perform compiling a script.

If only build is executed, script will not be saved.

If it cannot be built, a compile error will occur.

Check the [Build errors] view and resolve the problem.



29

5.1.8. Executing script

1. Created script can be debugged by clicking [Start/restart debug the script].

When debug script is executed, the script’s processing time and execution result will be

displayed in the [Execution history] and [Execution log] respectively.



30

2. Now, to confirm expected output in the CSV file, open the property window of [CSV_ Write]

component icon and click the [Preview].

Written contents are displayed in the [File Previewer] screen.



31

The same can be confirmed by opening the file from Studio Explorer.

Select [Explorer] from start menu of Studio.

Open the /samples/tutorial folder and double click ”Products.csv”. A text editor will open and

the written contents will be displayed.



32

5.1.9. Registering the project to the server

To invoke the script from trigger, project with the script you wish to call should be registered as

service.

1. Select [Register project as service] from [File] menu.

The same can be achieved by right clicking [Project explorer] menu.



33

2. Click [Finish] without changing the value of [Service name].

3. Click [OK] in [Register service] dialog displayed.



34

5.1.10. Configuring a file trigger

File trigger is used to execute the script when file is newly created.

1. Select [My Triggers] from the start menu of Studio.

In [My Triggers task], click [Create new File trigger].



35

2. Perform the configuration in [File Trigger] property window displayed as follows and click

[Next].

● [Trigger name] : [DB2CSV]

●[Watch file] : “/samples/tutorial/trigger/triggerFile”

●[End option] : [Delete watch file]



36

3. Provide the name of the script that is executed when the file trigger is fired. Select [DB2CSV]

in [Script] and [root@scenrio1] which is just registered as service in [Service] and click

[Finish].

Click [Yes] in the [Trigger enabling confirmation] dialog displayed.

If [No] is clicked, trigger is registered in disabling state.

If you do not want the trigger to fire immediately, register the trigger as disabled by clicking

[No]. Also, it is possible to change the state later to enable.



37

4. The file trigger set in My Trigger will be displayed.



38

5.1.11. Firing the file trigger

Create the watch file set in file trigger newly and fire the trigger.

1. Open the directory” /samples/tutorial/trigger” in explorer.

Go to [File] - [New] and select [Text file].

Change the file name to “triggerFile” as “New file.txt” is displayed in editing state.



39

The file is created in the same path as [Watch file] which is just created in file trigger. As trigger

criteria is met, it is fired.

File trigger executes the script [DB2CSV] of service [root@Scenario1] and outputs the execution

result as “Products.csv” below the directory /samples/tutorial.

As [Delete watch file] is selected in file trigger, “/samples/tutorial/trigger/triggerFile” will be

deleted.



40

5.2. Scenario 2 “Excel to DB”

5.2.1. Scenario Description

In scenario2, Excel database records are read at the time which is set in the schedule trigger,

processed which are then written to PostgreSQL database.

The process flow and its details are as follows.

• Fired at the specified time once in 1 day

Read

• Reads "Sales" sheet of Excel book "/samples/tutorial/Sales.xls".

• Does not read as the first line of the sheet is header.

Convert

• Among the read data, extracts only the line with [DVD] for [Category].

• Multiplies each row of the read data [Order_Number] and [Unit price] to calculate the subtotal.

Write

• Writes the data to the table [DVD_Orders] of PostgreSQL database dataspider_tutorial".

• Compares the converted data & table row. When it matches to the key [Product code], it is updated. When it does not match, it is inserted.

Fire trigger



41

5.2.2. Creating a project and a script

1. Create a new project.

In scenario 1, [New project] screen is displayed by double clicking the [New project] on the

desktop. It can also be shown as below.

●[File] - [New] - [Project] in designer.

●[File] - [Create new project] in my projects.

●[Create new project] by right clicking on the blank space of the right pane in [My Projects].

2. Create a project and a script in the same manner it is created in Creating a project and a script

of scenario 1, by specifying the following names respectively in the corresponding fields.

●Project name: [Scenario2]

●Script name：[Excel2DB]

5.2.3. Extracting Excel data

1. In Designer Tool palette, select the [Read from Sheet] found under [File] - [Excel]. Drag it to

the canvas and drop to deploy.



42

2. Configure the settings in the [New Read from Sheet Operation] property window displayed, as

follows.

●[Name] : [Excel Read Process]

●[File] : “/samples/tutorial/sales.xls”

●[Sheet name] : [Sales]

If [Update column list] is clicked, column name value and type of first row in [Sales] sheet is

read and [Column list] is generated automatically.

Then, select [Read settings] tab.

Check [Do not get first row as value].

If [Do not get first row as value] is checked, first row of input data is not read. Mainly, this

is used if first row of input data is header.



43

3. If [Finish] is clicked, property window closes and icon labeled [Excel Read Process] is deployed

on the canvas.

With this, the configuration for reading data from Excel file gets completed.



44

5.2.4. Writing data to PostgreSQL database

1. In Designer Tool palette, select the [Write Table] found under [Database] - [PostgreSQL].

Drag it to the canvas and drop to deploy.



45

2. Configure the settings in the [New Write Table Operation] property window displayed, as

follows.

●[Name] : [PostgreSQL Write Process]

●[Input data] : [Excel Read Process]

●Destination] : [Tutorial Connection Setting]

●[Table name] : [dvd_orders]

Select global resource [Tutorial Connection Setting] in [Destination] same as the one

which is created in scenario 1. Once a global resource is set, various scripts can be referred

and used.



46

3. Check [Update rows with matching key] and in [Schema definition] check the [Key] box of row

for which the corresponding [Column name] is “sku”.

4. If [Finish] is clicked, property window closes and icon labeled “PostgreSQL_Write” is deployed

on the canvas.



47

5.2.5. Adding a Mapper

Mapper is a functionality used to perform data conversions. A function has been provided to set

condition for extraction and perform calculations.

Mapper has various types. However, in this scenario, the document mapper is used to extract only

the product data which is categorized in “DVD” and to calculate the unit price and the quantity of

order to obtain the order amount i.e. subtotal.

1. Right-click on the data flow and select [Add mapping] from the menu.

Document mapper is deployed between Excel Read Process and PostgreSQL Write Process.



48

2. Double click the [Mapping] icon which is just deployed to open the Mapper editor.



49

5.2.6. Calculation in a Mapper

Let’s create a mapping definition to calculate order amount. It is calculated using the multiplication

logic, Subtotal =unit price × quantity.

1. Select the [Number] - [Operation] - [Multiply] logic component in the tool palette which is in

a mapper view. Drag it to the canvas and drop to deploy.

2. Create mapping link.

The link can be connected in the same manner the process flow is connected in the script

canvas.

First click order quantity found in the input source and drag it till [Multiply] logic icon. Then

release the mouse button when the icon is surrounded in a blue dotted rectangle.



50

In the same manner, connect mapping link from “Unit price” to [Multiply] logic icon. Then,

connect [Multiply] logic icon with “Subtotal” in the output data as well.

With this, mapping definition gets completed.

If the canvas is not large enough to display all of the components, it can be maximized by

double-clicking the tab.

To shrink it back to its original size, double-click the tab again.

And, when logic icons and mapping links are increased too much, mapping definitions can be

branched by adding layer (tab).



51

5.2.7. Extracting data by condition in Mapper

Now, we create mapping condition to extract only the data of product number for which the data

is categorized as “DVD”.

1. Delete the “Simple Loop” logic icon.

To delete [Simple Loop] logic icon, select [Delete] from the right click menu.

Logic icons can be deleted by pressing DELETE key.

Press [Yes] from “Delete logic” dialog displayed.



52

3. 3. Select the [Loop] - [Condition specification] - [If Loop] logic component in the tool palette

of mapper view. Drag it to the canvas and drop to deploy.

4. As the condition is evaluated against each row found in the input source data in a loop process,

connect the mapping link “row” from the “Excel_Read” to the [If Loop] logic icon and also

connect the logic icon itself to the “row” found in the “PostgreSQL_Write” in the output

destination.

5. Select the [String] - [Basic] - [Single-line String Constant] logic component in the tool palette.

Drag it to the canvas and drop to deploy.



53

6. Double click [Single-line String Constant] logic icon.

Enter [DVD] in [Single-line String] and click [Finish] in the [Single-line String Constant]

property window displayed.

7. Select the [Condition] - [String] - [Identical] logic component in the tool palette. Drag it to the

canvas and drop to deploy.



54

8. Create a condition that evaluates the value of category column equals to “DVD”. Connect

“Category” to the [Identical] logic icon and also connect the [Single-line String Constant] logic

icon to the [Identical] logic icon.

9. Connect [Identical] logic icon to [If loop] logic icon.



55

With this, mapping definition gets completed.

Created mapping definitions can be tested for its proper operation using real-time preview

function.

Select [View] from designer menu and select [Show test data view] and [Show test result

view].



56

Test data is set in [Test data view]. To configure the test data, line can be added by clicking .

Process result based on test data is displayed in the [Test result].

The product data which is categorized in “DVD” alone is extracted and we will be able to view

that the subtotal is properly calculated.

10. Return back to script canvas as operations in mapping canvas get completed.

Click [Excel2DB] tab at the upper part of canvas.



57

5.2.8. Completion of script

1. Draw the process flow in the order of process performed as follows.

[Start] - [Excel_Read] - [Mapping] - [PostgreSQL_Write] - [End].

5.2.9. Executing script

1. Run the process by clicking [Start/Restart debug the script].

2. Confirm whether the output data is written to PostgreSQL.

The result can be checked in the table browser.

It can be opened by clicking [Launch table browser] in “PostgreSQL Write Process” property

window.



58

Select [dvd_orders] in [Table list] and select [Table contents] tab on the right pane to view the

records within the table.



59

5.2.10. Registering the project to the server

Refer to “Registering the project to the server”.

5.2.11. Configuring a Schedule Trigger

Schedule trigger is used to execute the script in the set schedule.

1. Open [My Trigger].

2. [Create new schedule trigger] in [My Triggers Task].



60

3. Select [Daily] and click next to proceed in [Schedule] property window opened.



61

4. Configure the settings as follows and click [Next].

●[Trigger name]: [Excel2DB]

●[Execution start time]: Set the firing time for trigger.

In this scenario, as the desired firing time is 10:30 every day, it is set as “10:30”.

Execution timing can be confirmed as it is displayed under [Explanation of above setting].



62

5. Configure the firing schedule for trigger to run on holidays.

Perform the below settings and click [Next] to run the schedule on holidays.

[Holiday action] : [Execute on holiday]

[Holiday settings] : [Default calendar]



63

6. Configure the script to be executed while firing the trigger.

Select root@scenrio2 which is just registered as service and [Excel2DB] in [Service] and

[Script] respectively and click [Finish].

7. Click [Yes] in the [Trigger enabling confirmation] dialog opened.

8. The schedule trigger which has been configured and registered can be verified in My Trigger.



64

5.2.12. Confirming firing schedule for trigger and execution result

1. Trigger firing can be confirmed after completion of execution time set in the schedule trigger.

Select [Refresh] in [My Trigger] menu - [View].

The script has been successfully executed, if the [Last execution result] of the trigger displays

“Succeeded (0).”

5.2.13. Holiday Settings

When firing is not desired for a particular date or day even if the firing condition of schedule trigger

is met, a calendar which can be used with the firing-schedule for a schedule trigger can be created

using [Holiday settings].

When holiday setting with a calendar is used for a schedule trigger, the trigger will not be fired

on the date which has been set in that calendar.

In this scenario, let’s create a calendar for schedule trigger wherein the firing is not desired for

weekends, national holidays and 3rd Wednesday.

1. Select [Control panel] from the start menu of Studio.

2. Click [Holiday settings] in the control panel.



65

3. Double click [New calendar] in [Holiday settings] screen.

4. Perform the settings in [Calendar Settings] screen as follows.

● [Name]: [tutorial holiday].

● [Base calendar]: [2006-2030 Japanese Calendar (Saturday and Sunday, Holiday)]

5. Click [Add].



66

6. Perform the below settings and click [OK] in [Setting of regular holiday] screen.

●[Name]: [Third Wednesday Holiday Settings]

●Pattern setting]: Select [Month]/[Weekday].

[1] every month [Third] [Wednesday]

●Period]/[Start date]: Current date

●[Period]/[End date] : 1 year later from current date



67

7. Click [Finish] in [Calendar Settings] screen.

With this, calendar creation gets completed.

To set the already set calendar to the schedule trigger, configure the settings in [Holiday action

settings] of schedule trigger settings as follows. By this setting, the trigger will not be fired on

weekdays, national holiday and third Wednesday which has been set in [Tutorial holiday

settings].



68

6. Log management

Operation rules for configuring the logs are as follows.

⚫ Need to access the logs for the last 7 days.

⚫ Log retention period is 1 month (31 days) and when exceeding the period the log will be

deleted.

⚫ Logs generated within the last 12 hours can be viewed using Log viewer.

6.1. Configuring Logs

6.1.1. Configuring My Logs

1. Select [My Logs] from the start menu of Studio.



69

2. Double click [New search condition] in [My Logs] screen.

3. Configure the settings in the [New search condition] dialog displayed and click [OK].

● [Name]: [Log for the past 12 hours]

● [Filter by time]: Checked

● [Period]: Last [12] and [hour(s)]



70

4. Double click [Log for the past 12 hours] which is just created in the right pane of My Logs.

[Log search result [Log for the past 12 hours]] screen is displayed and you can now view the

logs that match the criteria.



71

6.1.2. Configuring the server log

1. Select the [Control Panel] from the start menu of Studio.

2. Click [Integrate Log Settings] in the Control Panel.

3. Configure the settings in the [Integrate Log Settings] screen displayed and click [OK].

● [Compress logs]: Select

● [Retention period to be compressed]: [7] days

● [Compress and delete logs]: Select

● [Retention period to be deleted]: [24] days

As it is given in the log operation rule that the [Log retention period is 1 month (31 days)]

in this scenario, set the Log retention period to be compressed as 7 days and set the log

retention period to be deleted as 24 days, which makes total of 31 days to retain the logs.

In order to access the log files generated before those of the most recent 7 days using the

Log viewer, you need to unzip each archived log files within the same folder.



72

HULFT Integrate Tutorial Guide The 1st edition: January 8 2019 HULFT, Inc.

1820 Gateway Drive, Suite 120

San Mateo, CA 94404

www.hulftinc.com

DataSpider Servista Tutorial Guide - HULFT Support · 2019. 6. 20. · Sample data used in this guide and the completed sample project. ... Insert sample data into PostgreSQL as follows.

Documents