This topic outlines current known limitations and restrictions for the EJB tooling.
In versions of WebSphere® Studio Application Developer earlier than V5.0, adding attributes of an EJB 1.1 CMP entity bean to an optimistic predicate was not supported. However, if you use V5.1 to deploy an EJB application that you developed using a version earlier than V5.0 and does not include a list of attributes for an optimistic predicate, all of the available predicates are used. EJB 2.0 CMP entity beans are treated differently. If no attributes are selected as predicates, then none are added to the overqualified update.
If a table needs to be deleted, use the Data perspective or the Project Explorer view of the J2EE perspective, then all dependent links will also be removed. Normally you should not use the Navigator view (in the Resource perspective) or the J2EE Project Navigator view for deleting J2EE resources because dependencies will not be updated.
The EJB tooling currently does not support the Unknown primary key definition described in the EJB 2.0 specification. The workaround is to define a specific primary key class.
db2 catalog TCPIP node RHOST remote LHOST server 50000 db2 catalog database MyDB as MyDBAlias db2 uncatalog db MyDB db2 catalog database MyDBAlias as MyDB at node RHOSTTo verify whether this works, issue the following command, where xxx is your password:
db2 connect to MyDB user xxx