IBM WebSphere V5.0 Security - CGISecurity

6. To have the embedded messaging running, you have to stop then restart theapplication server.7. Create a J2C Authentication entry; select: Security -> JAAS Configuration-> J2C Authentication Data.8. Click New to create a new entry, fill out the fields with the following values:– Alias: itsobankds_auth– User ID: dbuser– Password: password9. Create the following J2C authentication alias.Table A-2 J2C Authentication aliasAlias name username passworditsobankjms_auth jmsuser password10.Save the configuration changes.11.Set up a the JDBC provider and the DataSource; select: Resources ->Manage JDBC Providersa. Select the Server, server1 radio button, then click Apply; this will switchthe scope to the server level.b. Click New.c. Select DB2 JDBC Provider (XA) for JDBC Provider. You will need to usethe XA version of the driver to support the transactions in the application.d. Click OK; the JDBC provider configuration panel appears.e. Set the classpath to the correct value to reach the db2java.zip library, forexample: c:/sqllib/java/db2java.zip, or set the{$MQ_INSTALL_ROOT} WebSphere variable.f. Click OK, and the list of the JDBC providers appears on the page.g. To create the datasource, select the DB2 JDBC Provider (XA) item youhave just created.h. Go down in the Configuration page and click the Data Sources link.i. Click New to create a new Data source.j. Fill out the fields with the following values:Name: itsobankdsJNDI Name: jdbc/itsobankdsAppendix A. Sample application 455