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.

Use this DataSource in container managed persistence (CMP): Yes. Thiswill create a CMP_Connection_Factory for the <strong>WebSphere</strong> RelationalResource Adapter with the name: itsobankds_CF, and with the JNDIname: eis/jdbc/itsobankds_CMP.Description: ITSOBank data sourceCategory: itsobankContainer-managed Authentication Alias: itsobankds_auth (select fromthe list).Component-managed Authentication Alias: itsobankds_auth (select fromthe list).k. Click OK to add the new datasource, then you will see the list of availabledatasources.l. Click the itsobankds link to open the configuration.m. Go down in the page and click the Custom Properties link. You will see alist of properties set for the data source.n. Change the databaseName property with the value: SAMPLE; click the link,then change the value to ITSOBANK. Click OK when done.o. Delete the portNumber properties.12.Set up the JMS resources QueueConnectionFactory and Queue; selectResources -> <strong>WebSphere</strong> JMS Provider.a. Select the Server, server1 radio button, then click Apply; this will switchthe scope to the server level.b. Click the <strong>WebSphere</strong> Queue Connection Factories link, this will bring upthe list of the queue connection factories.c. Click New to add a new factory. The configuration page will appear, thenfill out the fields with the following values:Name: itsobankQCFJNDI Name: jms/itsobankQCFContainer-managed Authentication alias: itsobankjms_authComponent-managed Authentication alias: itsobankjms_authSet the connection factory to use transactions: XA Enabled.Leave the rest of the settings as they are.d. Click OK to submit the configuration.e. Select Resources -> <strong>WebSphere</strong> JMS Provider again, and create a<strong>WebSphere</strong> Queue Destination for the server1 server. Configure thequeue with the following values:456 <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!