94 lines
6.0 KiB
HTML
94 lines
6.0 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="concept" />
|
||
|
|
<meta name="DC.Title" content="Database considerations" />
|
||
|
|
<meta name="abstract" content="The following considerations apply to using the iSeries Access for Web database functions in a portal environment." />
|
||
|
|
<meta name="description" content="The following considerations apply to using the iSeries Access for Web database functions in a portal environment." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzammdatabaseportlets.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2003, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2003, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzammdbportconsider" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Database considerations</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzammdbportconsider"><a name="rzammdbportconsider"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Database considerations</h1>
|
||
|
|
<div><p>The following considerations apply to using the iSeries™ Access
|
||
|
|
for Web database functions in a portal environment.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Cross-site scripting</h4>Statements containing greater
|
||
|
|
than (>) or less than (<) characters fail with the default configuration
|
||
|
|
of WebSphere<sup>®</sup> Portal.
|
||
|
|
See Cross-site scripting for information about how to handle this.</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">iSeries SQL
|
||
|
|
requests</h4>The SQL requests created and managed by the iSeries SQL
|
||
|
|
Requests portlet are stored in a back-end database table. A WebSphere data
|
||
|
|
source must be configured to provide access to a database server for storing
|
||
|
|
this information. This data source must meet these requirements: <ul><li>The data source cannot be version 4.</li>
|
||
|
|
<li>The data source JNDI name must be set to <samp class="codeph">jdbc/iwads</samp>.</li>
|
||
|
|
<li>The data source must have a container-managed alias set.</li>
|
||
|
|
</ul>
|
||
|
|
If any of these requirements are not met, the portlet displays a message
|
||
|
|
stating the required configuration has not been performed.<div class="note"><span class="notetitle">Note:</span> iSeries Access
|
||
|
|
for Web is tested using the IBM<sup>®</sup> Toolbox for Java™ JDBC driver. Using a different driver
|
||
|
|
will likely work, but this is an untested and unsupported environment. </div>
|
||
|
|
The
|
||
|
|
database table is created in a schema named <samp class="codeph">QUSRIWA2</samp>. 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. <div class="p">The default table name is <samp class="codeph">QIWADTA</samp>.
|
||
|
|
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 (<samp class="codeph">iwawps.war</samp>) defines the <span class="uicontrol">dataTable</span> 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. <div class="important"><span class="importanttitle">Important:</span> Ensure there are no active users
|
||
|
|
of the iSeries Access
|
||
|
|
for Web Data Store or the iSeries SQL Requests portlets while the <span class="uicontrol">dataTable</span> parameter
|
||
|
|
is being modified.</div>
|
||
|
|
</div>
|
||
|
|
<p>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. </p>
|
||
|
|
<div class="p">It is possible
|
||
|
|
to share database requests among multiple WebSphere Portal instances. This is
|
||
|
|
done by configuring the <samp class="codeph">jdbc/iwads</samp> 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: <ul><li>Use credential specific to this request: A request configured with this
|
||
|
|
authentication option can only be used from the instance where it was created.
|
||
|
|
</li>
|
||
|
|
<li>Use credential set with iSeries Credentials portlet and Use system shared
|
||
|
|
credential set by administrator: Requests created with either of these authentication
|
||
|
|
options can be used from multiple instances, provided a credential with the
|
||
|
|
selected name exists for each instance. </li>
|
||
|
|
<li>Use authenticated WebSphere credential and Use WebSphere Portal
|
||
|
|
identity: Requests created with either of these authentication options can
|
||
|
|
be used from multiple instances, provided each instance is correctly configured
|
||
|
|
for the selected environment.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzammdatabaseportlets.htm" title="The Database portlets provide support for accessing database tables on an iSeries server.">Database</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|