There are some key points that you need to keep in mind when migrating EJB JAR files.
If you want to migrate an EJB 1.0 JAR file to your product and have modified the existing generated deployment code to get it to work with a specific database vendor (for example, changing the case of column names to mixed case), that change will not be preserved when you redeploy the JAR file using the product.
If you originally used VisualAge for Java to specify a mapping and generate the deployment code, then you will need to export the EJB project from VisualAge for Java as an EJB 1.1 JAR file. This will preserve your mapping metadata and the case of table and column names.