J2EE (EAR) Project
Update, as necessary, Module list in Deployment Descriptor. In particular, check the Project Utilities (and add, if they are not present) jar files for EJB Session and Entity client projects as well as DataBean and ModelDomain projects
Add DataSource for the application, under the Deployment tab.
As a preliminary, create a JAAS Authetication Alias, by expanding the Authentication heading (you will need this when creating the actual DataSource)
Verify and add, if necessary, the desired JDBC Provider (e.g., DB2 Universal JDBC Driver Provider)
Select the desired JDBC Prover and add a Data source. Be sure to give it a valid jndi name, such as jdbc/xxx where xxx is an arbitrary but memorable identifier for the project. Select your JAAS alias from the dropdown list for both component- and container managed authentication
Specify the name of your database under Resource properties.
Add Shared Libraries that may be needed by various projects but not be included as part of WebSphere. Struts' jar file and the gesjen.jar files are examples. Expand the Shared Library tab and add each jar file. Include the full name of the jar, such as gesgen.jar as the name and then add the path down to the directory that holds that jar in the class path section.
Add the application to the server.
In the Server view, right click on the desired ser (i.e., WebSphere application Server v6.1)
Select Add and Remove Projects and add the project.
All Projects
In accord with the modules noted in step 1 of the J2EE (EAR) Project, above, update as necessary the Manifest files for each project in the application. In each, drill down to the META-INF directory and then open the MANIFEST.MF file. These directories can be found under several different project directories, including ejbModule for EJB projects, src for Java projects, and Web-Content for Web projects.
Entity EJB Project
Edit Relationships and save (to generate navigation methods in beans) in the Deployment Descriptor. If no relationships, remove relationships tag in Deployment Description
Edit the Queries and save for each Entity EJB
Generate EJB to RDB mapping.
Right click on the project, selct Java EE > EJB to RDB Mapping > Generate Map
Be sure to specify Target DataBase, DataBase Name, and Scheme Name
[In the Mapping Editor, you should be able to set DB column lengths and names as desired, but we haven't discovered how to do this in RAD]
Export mapping to DB Server:
Select the WebSphere server (e.g., 6.1) for the application and
Select create tables and data sources
Define Connection, if necessary
Generate Deployment and RMIC Code. Select Java EE > Prepare for Deployment
Domain Model Project
Implement any non-CRUDS methods, such as Login verifyPassword.
Session EJB Project
Define References (to generate JNDI bindings).
Generate Factory: add Access Bean (Java Bean Wrapper) to Deployment Descriptor
Generate Deployment and RMIC Code
(Similar to Entity EJB process)Web Project
Update Struts mappings, if needed.
Implement any additional views, as needed.
Implement non-CRUDS methods in any layers where needed, e.g., ModelDomain.
Select a Server for testing and development. The current RAD 7.5 plugin is configured to work with WebSphere 6.1. Start the server and republish the application.