The following considerations apply to using the iSeries™ Access for Web database functions in a portal environment.
iSeries Access for Web is tested using the IBM® Toolbox for Java™ JDBC driver. Using a different driver will likely work, but this is an untested and unsupported environment. The database table is created in a schema named QUSRIWA2. If this schema does not exist, it is created. If this schema exists, the user identified by the data source authentication alias must have read and write access to the schema.
The default table name is QIWADTA. It might be necessary to override this value if, for example, multiple WebSphere Portal instances target the same back-end database server. The iSeries Access for Web web Module (iwawps.war) defines the dataTable parameter to configure the table name. The WebSphere Portal administration interface provides a way to modify this parameter value. See the WebSphere Portal documentation for more information.
Ensure there are no active users of the iSeries Access for Web Data Store or the iSeries SQL Requests portlets while the dataTable parameter is being modified.
If the configured table does not exist, it is created. If it does exist, the user identified by the data source authentication alias must have read and write access to the table.
It is possible to share database requests among multiple WebSphere Portal instances. This is done by configuring the jdbc/iwads data source for each instance to the same back-end database server and by using the same database table name for each instance. The authentication settings for the database requests must also be configured to facilitate sharing among multiple WebSphere portal instances as follows: