Preparation for development

Preparation

This section describes the necessary preparations for performing a data integration process.

For basic concepts and terminology of data integration, refer to the following references.

Content	Reference
Explanation of basic terminology related to Data Integration	Explore Data Integration
Projects	Projects
Scripts	Scripts
Data integration flow	ETL process creation

Setting up development standards

Before starting the development of a data integration process, it's important that you set up development standards. Development standards give uniformity to the deliverables and help to improve quality, efficiency, ease of maintenance, and so on.

It's recommended that you decide how you want to approach the following topics before you start development:

Composition of projects and scripts

The processing unit for projects
The processing partition unit for scripts
The transfer methods of values between projects and between scripts
The number of component icons within one script

When the number of scripts within a project becomes too large, it may take time to save a project or load scripts.

To prevent this problem, we recommend that you partition projects to suit specific situations.

Also, if the number of component icons within a script becomes too large, maintenance becomes more difficult because the script's readability decreases, and the operation of HULFT Square becomes slow because its memory usage increases.

It's recommended to use script call and similar functions to partition scripts for each operation. The recommended maximum number of component icons within one script is 100.

Development and production environment

Log levels used during development and after the start of actual operations
Connection resource profiles used during development and after the start of actual operations

= Reference =

For details about log levels, refer to Log levels.
For details about profiles, refer to Profiles.

File storage location

Storage location of files that are read or written to

Naming conventions

Project name
Environment variable name
Script name
Script variable name
Component name
Connection resource name
Global schema name
Profile name
Job name

Note

For details about restricted characters, refer to Restricted characters.

Designing a script

Flow layout

Decide whether you want to draw the lines to create a vertical flow, or create a horizontal flow.
Component layout

Decide what the spacing between components should be and what grid you want to display.
Logic layout in Mapping canvas

Decide what the spacing between logic should be, what grid you want to display, how to divide the layers, and so on.

Others

How to monitor exceptions, and operations when the exceptions occur
Writing conventions for comments and memos

= Hint =

Set up the appropriate development standards for your project.

Recommended minimum configuration

The recommended environment may change.

The display environment that is required to use HULFT Square Designer (hereafter Designer) is as follows:

Color: 24 bit color
Resolution: 1280 x 960 pixels or more

Execution environment for Designer

The recommended environment may change.

The following execution environment is required to use Designer. Install the following before the first launching of Designer:

Microsoft .NET Framework 4.7 or more

Download .NET Framework from the download page at Microsoft.
HULFT Square Designer.exe