Notes
When you perform the following after the Integrate service is started or restarted, Metaspace in the JVM Non-Heap Memory area managed by Java is consumed.
-
Execute a script of any project version from Designer for the first time
-
Edit and then execute a script
-
Execute a job for the first time
-
The JVM Non-Heap Memory is refreshed after the Integrate service is restarted. When you execute scripts that have been executed before a restart, they are treated as first-time executions, and the above is applicable.
-
The amount of JVM Non-Heap Memory space consumed is proportional to the number of scripts and components in the project.
JVM Non-Heap Memory isn't consumed in the following cases:
-
A script in the same version of a project is executed repeatedly
-
The same job is executed repeatedly
When the JVM Non-Heap Memory area is insufficient, a script may fail to be executed correctly due to the error "Failed to load script." When this phenomenon occurs, restart the service.
Designer
-
When you run a script while the script is being saved, saving may fail.
Don't run a script when the script is being saved.
-
If you click Finish in a properties dialog when you are typing something in an input field, the input may not be reflected. Press the Enter key to complete the input, and then click Finish.
-
When you paste a character string with a newline in a field that can only take a single line, only the data before the newline is pasted.
Project explorer
-
When you delete scripts, folders, or script variables, the project explorer becomes inactive and you can't save the project.
If this happens, reselect Project explorer and save the project.
Property inspector
-
When you have entered a value in properties, be sure to press the Enter key to complete input.
-
When you open the settings dialog of a Raise Exception operation or Memo operation from Property inspector, the input isn't reflected even if you click OK. Select a view or canvas outside the Property inspector, and complete the input.
Related to connectors/script components
Script component
-
In flow operations (such as Loop or Conditional Branch), the last component icon located between the start icon and the end icon is connected internally to the end icon by a supplemental process flow.
In the same way, the process flow between the start icon and the end icon are also complemented. Therefore, even if no component icon is placed between the start icon and the end icon, a compile error doesn't occur.
-
In Loop, Conditional Loop, and Loop by Amount of Data operations, the component variable count is added at the end of each loop.