Fix External Resources

Due to improvements to the way ALBPM handles integration with other external systems, you might need to do some minor changes to the External Resources of your projects.

Open your project with ALBPM Studio 6.0.
Migrate to the new JDBC drivers provided by BEA.
ALBPM now supports several SQL databases out of the box (you don't need to provide an external JDBC driver anymore). If your project integrates with any of these databases, it is recommended that you migrate to the new drivers.
1. Remove references to JDBC Java Libraries. On the Project Navigator expand External Resources and remove those Java Libraries resources holding JDBC drivers (refer to the "External Resources" section of Studio's online help for details).
2. Modify any existing SQL External Resources to use BEA's JDBC drivers
  On the Project Navigator expand External Resources and double-click on a SQL database resource. In the Edit External Resource dialog change the value of the Supported Type drop-down to the corresponding BEA driver for your database.
  For advanced JDBC URL configurations refer to the custom properties of the JDBC driver:
  - For Oracle: http://edocs.bea.com/wls/docs100/jdbc_drivers/oracle.html#
  - For Microsoft SQL Server: http://edocs.bea.com/wls/docs100/jdbc_drivers/mssqlserver.html
  - For DB2: http://edocs.bea.com/wls/docs100/jdbc_drivers/db2.html
  - For Informix: http://edocs.bea.com/wls/docs100/jdbc_drivers/informix.html
  - For Sybase: http://edocs.bea.com/wls/docs100/jdbc_drivers/sybase.html
Re-catalog all components in the Catalog of your project.
This step is needed to re-generate the metadata associated with each component. You must re-catalog all types of components, including Java classes, SQL tables, Web Services, .Net, JNDI, CORBA, COM and SAP components.

Note: On version 5.x, Java type java.util.Date (when used in method arguments or as return type) was cataloged as Fuego.Lang.Time. On version 6 onwards, the type java.util.Date is maintained as such when cataloging. This doesn't cause incompatibilities.

Important: Cataloged Java classes do not include inherited members anymore (see next step).
Catalog additional Java classes as needed.
On version 5.7, a cataloged Java class included all members inherited from parent classes. Starting with version 6.0, cataloged Java classes only include methods and attributes explicitly defined by the class, excluding the ones inherited by its parent class. If there's code in your project using inherited members of a class, you must also catalog the parent Java classes that includes such members.

For example, if your project has cataloged EJBs (Enterprise JavaBeans), you must also to include the standard javax.ejb.* classes and interfaces into your catalog. Otherwise, standard methods like getEJBHome() and getHandle() do not show as members of your Bean.

Parent topic: Migrating Project Code

Previous topic: Import 5.7 project into Studio 6.0

Next topic: Changes in Standard Components