About Using JDeveloper for Customization

2.1 About Using JDeveloper for Customization

JDeveloper is used when it is needed to customize or create business objects or new pages. The procedures for each of these are different.

New custom objects created in JDeveloper are not saved into the MDS Repository, and so are done in a standard application workspace using the Default role. However, when you customize standard objects, those customizations are saved into the MDS Repository, and so must be done using the Customization Developer role. Doing customizations using the customization developer role ensures that the changes are saved to upgrade-safe MDS Repository, and not written directly to the standard object. In future, when patch or upgrade Application, the customizations held in these metadata files will not be touched, and so, it need not be re-done.

When customizing ADF artifacts, a special customization application workspace can be created; using the Default role, for this application a default customization application workspace (/OracleFSLLEnterpriseApp/OracleFSLLEnterpriseApp.jws) is provided. This workspace includes all the artifacts that can be customized. This customization workspace can be configured, so that when customizations are tested and deployed, they appear to be part of native Oracle Financial Services Lending and Leasing Application.

Using the default workspace, it is possible to switch roles to customization developer and customize the ADF artifacts required. After completion, the artifacts are packaged and deployed in the workspace to the Oracle Financial Services Lending and Leasing environment.

Often, there is a need to perform both customizations (customizing an existing standard object) and extensions (creating a new object). For example, suppose it is needed to create a new business object and expose that new object in an existing application module. First, because a new custom business object is being created, first a standard application workspace is created and then entity object is created. After completion, the workspace is packaged as an ADF Library, and placed into a directory. Next, using the default workspace provided, the new entity object library and the library that contains the application module to which we need to add the entity object is added. After both are imported, User should log in using the customization developer role and make the customizations to the application module. After customizations are complete, User would deploy the customizations to the test environment.

Note:

Before running JDeveloper in customization mode for the application, see Section 4.3 Enable JDeveloper for Customization for pre-configuration requirement.

Parent topic: Using JDeveloper for Customizations