About the Storage Elements
You use the elements in the storage folder to create, close, and delete data stores in the Integration Server short-term store. Integration Server uses the short-term store for information that needs to persist across server restarts. For example, if the Integration Server on which your flow service is executing becomes unavailable and then restarts, the flow service can check the state information in the short-term store and begin processing at the point where the flow service was interrupted. The short-term store exists as the IS_DATASTORE table in an external database identified to Integration Server through the ISInternal functional alias.
When using the pub.storage services, keep in mind that the short-term store is not intended to be used as a general-purpose storage engine. Rather, it is primarily provided to support shared storage of application resources and transient data in an Integration Server clustered environment. Consequently, Software AG recommends that you do not use the short-term store to process high volumes, large data records, or to permanently archive records.
Important:
These services are a tool for maintaining state information in the short-term store. It is up to the developer of the flow service to make sure the flow service keeps track of its state and correctly handles restarts.
In Release 7.1, the Integration Server 6.1 Repository Server was replaced by a set of database tables collectively called IS Internal. During Integration Server installation, you can choose to use the embedded IS Internal database, or you can choose to use an external RDBMS in which you have created or will create the IS Internal database component. If you choose the external RDBMS, data associated with the pub.storage services will be stored in the IS_DATASTORE table in the IS Internal database component. For DB2, the size of a BLOB column is defined when the table is created; you might find that the VALUE column in the IS_DATASTORE table is not wide enough to accommodate your pub.storage data. If you have not yet created the IS Internal database component, open the appropriate table creation script below in a text editor and modify the width of the VALUE column in the IS_DATASTORE table:
Software AG_directory \common\db\scripts\db2\isinternal\
version\create\db2_isi _c_ddl.sql
Software AG_directory \common\db\scripts\db2as400\isinternal\
version\create\db2as400_isi_c_ddl.sql
Where version is the directory that contains the latest version of the external RDBMS.
Tip:
The directory with the highest number corresponds to the latest version of the external RDBMS.
If you have already created the IS Internal database component and the VALUE column is not wide enough to accommodate your pub.storage data, use DB2 commands to modify the width of the VALUE column in the IS_DATASTORE table.