03.05.2015 Views

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

As a next step, the following list of steps will explain how to configure a data<br />

source with J2C authentication in <strong>WebSphere</strong> Application Server V5 using the<br />

Administrative Console. This uses the J2C Authentication Data Entry created in<br />

the previous step.<br />

1. In the Administrative Console navigate to Resources -> JDBC Providers.<br />

2. Select the scope for the new provider, in our case Server, then click Apply.<br />

3. Click New to create a new JDBC provider.<br />

4. Choose DB2 JDBC Provider XA from the drop-down list provided and click<br />

OK.<br />

5. In the DB2 JDBC Configuration page, make sure the classpath has the<br />

correct path for db2java.zip file.<br />

6. Click Apply.<br />

7. Open this panel once again, at the bottom of the page in the Additional<br />

Properties section, click Data Sources.<br />

Click New, and fill out the fields as indicated in Figure 7-28 on page 173.<br />

Container Manager Persistence: if you want this data source to be used for<br />

the container managed persistence of EJBs, then select this checkbox. This<br />

will create a corresponding CMP connection factory which corresponds to this<br />

datasource to be created for the relational resource adapter.<br />

Component-managed Authentication Alias: in this drop-down list, you<br />

should see the J2C Authentication Data Entry that we created, which is<br />

itsobankds_auth. Select itsobankds_auth from the list.<br />

Component-managed Authentication Alias: select itsobankds_auth from<br />

the list again.<br />

172 <strong>IBM</strong> <strong>WebSphere</strong> <strong>V5.0</strong> <strong>Security</strong> Handbook

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!