Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 and 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 in, 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
titleNote!

Some Database Management systems provide character column types so that you are not required to specify the column width (e g TEXT in PostgreSQL). If you use shared tables with such a column type, you cannot use the types On Heap, Off Heap or Unsafe within Table Storage.

APL

The following functions are included for the Table Lookup Service:

  • tableCreateShared

  • tableRefreshShared

tableCreateShared

This function returns a shared table that holds the result of the database query entered in the Shared Table profile.

...

Returned ValueDescription

profileName

Name of the Shared Table profile you want to use.

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, Image Added will have the disableCommit set to true unless otherwise changed via this parameter.

Info

It should be noted that on recent Oracle versions, the DBLink SQL transaction behaviour has changed, where every single SQL statement for remote database transaction requires a commit or rollback statement in order to close a connection.


Returns

A table containing the columns stated with the SQL query in the stated Shared Table profile, that can be shared by several workflow instances.

...

Info
titleExample - Using the function tableCreateShared

This creates a shared table called myTable with the columns returned by the SQL query in the mySharedProfile Shared Table profile.

Code Block
languagetext
themeEclipse
initialize {
  table myTable = tableCreateShared("Folder.mySharedProfile");
  }


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 ValueDescription

profileName

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, Image Added will have the disableCommit set to true unless otherwise changed via this parameter.

Info

It should be noted that on recent Oracle versions, the DBLink SQL transaction behaviour has changed, where every single SQL statement for remote database transaction requires a commit or rollback statement in order to close a connection.


Returns

A refreshed shared table.

...

Info
titleExample - Using the function tableRefreshShared

This returns the shared table called myTable, which uses the mySharedProfile, with refreshed data.

Code Block
languagetext
themeEclipse
table myTable = tableRefreshShared("Folder.mySharedProfile");


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

Scroll ignore
scroll-viewportfalse
scroll-pdftrue
scroll-officefalse
scroll-chmtrue
scroll-docbooktrue
scroll-eclipsehelptrue
scroll-epubtrue
scroll-htmlfalse


Next:



Scroll pagebreak