Connection resources

Connection resources

Connection resources are connection settings for data resources such as databases, mail services, and FTP services. Connection resources can be used for all projects and scripts.

From the > HULFT INTEGRATE > Connections page, you can manage connection resources, such as registering, changing, or deleting them.

For details about the management screen for connection resources, refer to Connections.

 

For details about how to set connection resources, refer to the following tutorials:

• Create a connection to a MySQL database

• Create a connection to Amazon S3

 

Connection resources offer the following advantages:

• Separation of physical settings and logical settings

  In the script for defining business logic, the data resources of the connection destination can be defined by specifying connection resource names. The actual physical connection settings such as the host name and IP address are configured in the connection resource settings and are hidden from the script.

  Only the connection resource name is kept in the script, and the connection settings are acquired with the connection resource name as a key during script execution.

  When the host name or the IP address of a data resource of the connection destination is changed, changing the script isn't necessary, which minimizes changes in the settings.

• Centralized management of connection settings

  In the connection resource settings, users with editing permissions for connections (EditConnectionResource) are authorized to edit and delete databases.

  They can check at a glance how many connections (connection resources) are configured and how they are configured.

Connection resource names

In each component, connection resource names are used to acquire the information about the connection resources that are set as connection destinations.

When registering connection resource names, use unique names that are not seen in other components on the same HULFT Square.

These settings can also be used as follows:

1. Change a connection resource name that is used in another component.

2. Generate a new connection resource and specify the name before the change made in step 1 above.

This makes it possible to change to other connection resources without changing the scripts. For example, this setting is useful when the version of the connected database is changed in the database connector.

However, this is possible only when both of the following conditions are met:

• Connection resources of the same components are used.

• The connected database doesn't have any differences that require you to change the script (table name, column name, type information, and so on).