256 DB2 for z/OS and WebSphere: The Perfect Couple
Figure 11-15 EJB project after import
In the project tree we notice the additional sub folders that have been created
In the J2EE perspective, in the top left Project Navigator view, under the sub folder
META-INF/backends/DB2UDBOS390_v7_1, we find metafiles *.tblxmi for the three imported
tables. These files will be the sources for the Entity EJB’s mapping. The “backends” notion
indicates already that we can have tables from several backends in the same EJB project.
Before we can do the mapping, we will have a look at those files and verify that all required
ingredients are present. One important requirement is that each table, which will be mapped
to an entity Bean, must have a
primary key. We can open the *.tblxmi files with the table
editor. We start with the NULLID.DEPT table. Double-clicking the file NULLID_DEPT.tblxmi
opens up a first pane (see Figure 11-16 on page 257), which is the overview pane. At the
bottom, we have a menu with thumbnails that allows us to walk through different panes. All
this information has been picked up from the metadata imported from DB2 into the project.
Note: The usage of the DB2UDBOS390_v7_1 directory may be confusing. We indeed
work with a DB2 V8 system, but the DB2 V8 labeling was not yet supported in WSAD V5.1
at the time of writing.