13.07.2015 Views

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

SHOW MORE
SHOW LESS
  • No tags were found...

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 datasource with J2C authentication in <strong>WebSphere</strong> Application Server V5 using theAdministrative Console. This uses the J2C Authentication Data Entry created inthe previous step.1. In the Administrative Console navigate to Resources -> JDBC Providers.2. Select the scope for the new provider, in our case Server, then click Apply.3. Click New to create a new JDBC provider.4. Choose DB2 JDBC Provider XA from the drop-down list provided and clickOK.5. In the DB2 JDBC Configuration page, make sure the classpath has thecorrect path for db2java.zip file.6. Click Apply.7. Open this panel once again, at the bottom of the page in the AdditionalProperties section, click Data Sources.Click New, and fill out the fields as indicated in Figure 7-28 on page 173.Container Manager Persistence: if you want this data source to be used forthe container managed persistence of EJBs, then select this checkbox. Thiswill create a corresponding CMP connection factory which corresponds to thisdatasource to be created for the relational resource adapter.Component-managed Authentication Alias: in this drop-down list, youshould see the J2C Authentication Data Entry that we created, which isitsobankds_auth. Select itsobankds_auth from the list.Component-managed Authentication Alias: select itsobankds_auth fromthe list again.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!