...
Using the Table Lookup Service instead of adding tableCreate in each workflow instance will increase the throughput with fewer duplicated tables, fewer lookups, and reduced memory consumption.
...
The Shared Table profile is loaded when you start a workflow that depends on it. Changes to the profile become effective when you restart the workflow each time you save the profile.
Memory Allocation
There are three different ways to allocate memory for the created tables. By default, the tables are kept as Java objects in memory. The shared tables can also be configured to keep the tables as raw data either on or off the heap. By using raw data, the overhead of java objects is removed and less memory is required.
...
For further information about memory allocation, see the System Administration Guide.
Shared Table Profile Configuration
The Shared Table profile configuration is opened by clicking on the New Configuration button in Desktop and selecting the Shared Table Profile option.
...
| Note | ||
|---|---|---|
| ||
Some Database Management systems provide character column types so that you are not required to specify the column width (e g |
APL
The following functions are included for the Table Lookup Service:
tableCreateSharedtableRefreshShared
tableCreateShared
This function returns a shared table that holds the result of the database query entered in the Shared Table profile.
...
| Info | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
This creates a shared table called myTable with the columns returned by the SQL query in the mySharedProfile Shared Table profile.
|
tableRefreshShared
This function can be used for refreshing the data for a shared table configured with a Shared Table profile. The table will be updated for all workflow instances that are using the table and are running on the same EC.
...
| Returned Value | Description | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Name of the Shared Table profile you want to refresh data for. | |||||||||||||||||||||
| disableCommit | An optional parameter to disable the commit statement from being performed at the end of every SQL transaction for this particular function. Setting this parameter to false will result in the commit statement to be performed at the end of every SQL transaction for this particular function. By default, the system will have the disableCommit set to true unless otherwise changed via this parameter.
| |||||||||||||||||||||
Returns | A refreshed shared table. |
...
| Info | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
This returns the shared table called myTable, which uses the mySharedProfile, with refreshed data.
|
Additional Performance Tuning
The Oracle JDBC driver includes a feature built that allows you to set the number of rows that are prefetched while the full result set is being formulated. At the time of writing, the default number of prefetched rows is 10. You can increase this value by setting the Execution Context property oracle.jdbc.defaultRowPrefetch in the relevant pico Pico configuration file.
| Scroll ignore | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||