| Oracle® Fusion Applications Extensibility Guide 11g Release 6 (11.1.6) Part Number E16691-08 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Applications Extensibility Guide 11g Release 6 (11.1.6) Part Number E16691-08 |
|
|
PDF · Mobi · ePub |
This chapter describes how to configure Oracle JDeveloper for implementing customizations in Oracle Fusion applications. It also describes how to customize Service-Oriented Architecture (SOA) composite applications with JDeveloper, including setting up the JDeveloper application workspace and SOA composite application project for Oracle Metadata Services (MDS) Repository customization, customizing the SOA composite application, and customizing the SOA resource bundle.
This chapter includes the following sections:
Section 10.2, "Customizing Oracle ADF Artifacts with JDeveloper"
Section 10.3, "Customizing SOA Composite Applications with JDeveloper"
You use JDeveloper when you need to customize or create business objects or security outside of CRM applications, or when you need to make more sophisticated changes, like changes to SOA composite applications, Oracle Enterprise Scheduler jobs, Oracle Business Process Management project templates, or embedded help. While you use JDeveloper to both customize existing standard objects and to create new custom objects, the procedures you use for each are different.
New custom objects created in JDeveloper are not saved into MDS Repository, and are therefore created in a standard application workspace using the Oracle Fusion Applications Developer role. However, when you customize standard objects, those customizations are saved into MDS Repository, and therefore must be implemented using the Oracle Fusion Applications Administrator Customization role. Implementing the customizations using this customization role ensures that your changes are saved to the upgrade-safe MDS Repository, and not written directly to the standard object. In the future, when you patch or upgrade Oracle Fusion Applications, your customizations held in these metadata files are not affected, so you do not have to redo them. For more information about customizations and MDS Repository, see Chapter 1, "Customizing and Extending Oracle Fusion Applications."
When customizing Oracle Application Development Framework (Oracle ADF) artifacts, you create a special customization application workspace, using the developer role. This application workspace includes a connection to a deployed Oracle Fusion Applications environment (typically a test environment), which allows you to import the artifacts you want to customize into your application workspace. This customization application workspace is automatically configured to work within Oracle Fusion Applications, so that when you test and deploy your customizations, they behave as though they were native Oracle Fusion Applications. When customizing SOA composite applications, you create a SOA Composite application workspace in the developer role.
After the application workspace is created, you switch roles to the customization role and import the Oracle ADF artifact or the SOA archive you want to customize. You then make your customizations to the imported artifact. After completion, you package and deploy the artifacts in the application workspace to the Oracle Fusion Applications environment.
Often, you must perform both customizations (customizing an existing standard object) and extensions (creating a new object). For example, say you want to create a new entity object and expose that new object in an existing application module. First, because you are creating a new custom entity object, you would create a standard application workspace and then create your entity object. After completion, you would package the application workspace as an ADF Library, and place it into the exploded enterprise archive (EAR) directory for your test environment. Next, you would create a customization application workspace, and import both the new entity object library and the library that contains the application module to which you must add the entity object. After both are imported, you log in using the customization role and make the customizations to the application module. After customizations are complete, you would deploy the customizations to the test environment.
Oracle Fusion applications are built using Oracle Application Development Framework (Oracle ADF) artifacts on Oracle Fusion Middleware, including the following:
Application modules: An application module is the transactional component that UI clients use to work with application data. It defines an updatable data model along with top-level procedures and functions (called service methods) related to a logical unit of work related to an end-user task.
Entity objects: An entity object represents a row in a database table and simplifies modifying its data by handling all data manipulation language (DML) operations for you. It can encapsulate business logic to ensure that your business rules are consistently enforced. You associate an entity object with other entity objects to reflect relationships in the underlying database schema to create a layer of business domain objects to reuse in multiple applications.
View objects: A view object represents a SQL query and simplifies working with its results. You use the SQL language to join, filter, sort, and aggregate data into whatever form is required by the end-user task being represented in the user interface. This includes the ability to link a view object with other view objects to create master-detail hierarchies of any complexity. When end users modify data in the user interface, your view objects collaborate with entity objects to consistently validate and save the changes.
Task flows: A task flow defines the flow of control throughout an application. It can also be included in a page as a region, where users can navigate through a series of page fragments, without leaving the original page.
JSPX pages and page fragments: The view layer of Oracle Fusion Applications consists of a small number of pages per application. These pages then contain task flows, which in turn contain a number of page fragments.
For more information about Oracle ADF components, see the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework (Oracle Fusion Applications Edition).
When you customize Oracle ADF artifacts, you usually work in an overview editor that allows you to make your customizations declaratively. For example, Figure 10-1 shows the editor for an entity object. Among other things, you can set validation or change how the UI displays the data.
For JSP pages, you work in a WYSIWYG environment using the Design tab in the editor window, as shown in Figure 10-2.
Oracle Fusion applications are built using SOA composite artifacts on Oracle Fusion Middleware, which include the following:
Service components: A service component implements the business logic or processing rules of a SOA composite application. Available service components include the following:
Business Process Execution Language (BPEL) processes: A BPEL process enables you to integrate a series of business activities and services into an end-to-end business process flow.
Business rules: A business rule enables you to create business decisions in your business process flow based on rules.
Human tasks: A human task enables you to create human workflows that describe the tasks for users or groups to act upon as part of an end-to-end business process flow. You use Oracle Business Process Management (BPM) Worklist to act upon the tasks during runtime.
Oracle Mediator: An Oracle Mediator enables you to define services that perform message and event routing, filtering, and transformations within the SOA composite application.
Binding components: A binding component establishes the connection between a SOA composite application and the external world. There are two types of binding components:
Services provide the outside world with an entry point to the SOA composite application. The Web Services Description Language (WSDL) file of the service advertises its capabilities to external applications. These capabilities are used for contacting the SOA composite application components. The binding connectivity of the service describes the protocols that can communicate with the service (for example, Simple Object Access Protocol (SOAP)/Hypertext Transfer Protocol (HTTP) or Java EE connector architecture (JCA) adapter).
References enable messages to be sent from the SOA composite application to external services in the outside world.
Wires: A wire connects services, service components, and references into a complete SOA composite application.
For more information about SOA composite applications, see the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.
Before you use JDeveloper to customize, be familiar with the Oracle Fusion application architecture that enables customization, as described in Chapter 1, "Customizing and Extending Oracle Fusion Applications." Also understand the typical workflows for working with customizations, as described in Chapter 2, "Understanding the Customization Development Lifecycle."
Do the following before using JDeveloper to customize:
Deploy the application you are customizing to a test environment. You must have access to the test environment and to the exploded EAR directory for that application.
Install JDeveloper and set up your development environment. Before you can implement customizations using JDeveloper, you must create a customization application workspace that imports the necessary parts of the application you want to customize. For more information, see the "Setting Up Your Development Environment" chapter in the Oracle Fusion Applications Developer's Guide.
Note:
Before you can use JDeveloper to customize your application, JDeveloper must have access to the customization layers for the application. To enable JDeveloper to see the customization classes that define the customization layers, use the -Dide.extension.extra.search.path VM option, as described in the "Adding Customization Extension Bundles to the jdev.conf File" section of the Oracle Fusion Applications Developer's Guide.
For information about locating the Java archive (JAR) files containing the product-specific customization classes, see the product-specific documentation from Oracle Enterprise Repository for Oracle Fusion Applications. You can also use the steps in the "Adding Customization Extension Bundles to the jdev.conf File" section of the Oracle Fusion Applications Developer's Guide to locate the JAR files.
To customize Oracle ADF artifacts, you first create a customization application workspace, using the Oracle Fusion Applications Developer role in JDeveloper. After the application workspace is created, you exit JDeveloper and then reenter, using the Oracle Fusion Applications Administrator Customization role and import and customize your artifacts.
You must set up a customization application workspace in JDeveloper to create the application that holds your customizations.
Note:
Before you start the FA Customization Application wizard to create a customization application workspace, make sure that the entire topology for the application you want to customize is up and running. The conn.xml file in Oracle Fusion applications contains EL expressions pointing to common server endpoints, such as the BI server, that cannot be resolved unless the entire topology for the application is running.
To create the customization application workspace:
Start JDeveloper using the Oracle Fusion Applications Developer role, as shown in Figure 10-3.
In JDeveloper, from the main menu, choose File > New to open the New Gallery. In the New Gallery, select Applications > Fusion Applications Customization Application.
In the Step 1 page of the FA Customization Application dialog, enter the following and click Next:
Application Name and Directory: These are the name and location of your customization application, and can be anything you like.
Fusion Database: Enter the connection to your Oracle Fusion database.
Application Package Prefix: This can be anything, but must not start with oracle.
Deployed Application Ear: Browse to the exploded EAR for the application you want to customize.
Policy Store Security Information: Browse to the exported jazn-data.xml file. First, you must export all predefined function security policies of the application that you are customizing into a jazn-data.xml file. For details about how to export the application policy store, see the "Securing Oracle Fusion Applications" chapter in the Oracle Fusion Applications Administrator's Guide.
For information about security customization, see Chapter 15, "Customizing Security for Oracle ADF Application Artifacts."
Complete the wizard by changing any default settings as needed.
After you complete the wizard, an application with a project is created for you. This application is configured to be the same as a deployed Oracle Fusion application. For example, it is connected to the same database, same metadata repository, and has similar web.xmland weblogic.xml settings. This configuration allows it to work correctly when deployed into your Oracle Fusion Applications environment, and also ensures that when you test your customizations locally in JDeveloper Integrated WebLogic Server, the customizations behave as they will in the full test environment.
JDeveloper also creates a connection to the exploded EAR directory named Customizable Archive, which is accessible from the Application Resources panel of the Application Navigator. Figure 10-4 shows a connection to the exploded EAR directory for an application.
Most often, the customizations you want to make are surfaced on an existing page. For example, say you want to add a field to a page. So, you first must identify the page to customize, which may actually be a page fragment within a task flow. You then must identify which business objects you'll need to customize to add the field.
The easiest way to identify which artifacts you need to customize is to follow this path:
In a runtime environment, access the page you want to customize and open it in the Source view of Page Composer. The page's structure is displayed, and from here, you can identify the page name, or if the customization is actually on a page fragment within a task flow, you can identify the task flow name. For more information about using Page Composer, see Chapter 3, "Customizing Existing Pages."
If you need to customize a page fragment (.jsff) file within a task flow, from Page Composer, click Manage Customizations to open the page in the Manage Customizations dialog. From here, you can identify the .jsff file name.
In JDeveloper, after you have created a connection to the exploded EAR directory, you can use the Filter Customizable Archive dialog to search for the .jsff file or the task flow file.
Right-click the file and choose Customize to import the file and open it in JDeveloper.
Right-click the file, and choose Go to Page Definition.
The page definition file shows you the view objects being used by the components on the page to return the data.
Open the view object in JDeveloper.
The view object can be customized, or if needed, you can identify the associated entity object and customize that. Note that you can also identify the application module from here.
You must switch to the Customization Developer role before you can begin customizing.
Restart JDeveloper and select the Oracle Fusion Applications Administrator Customization role, as shown in Figure 10-5.
In the Application Resources panel, expand Connections, and then Customizable Archive.
To locate the artifact you want to customize, right-click Base Application Archive and choose Filter.
For help in determining which artifacts you need to customize, see Section 10.2.2, "Determining Which Oracle ADF Artifacts You Need to Customize."
In the Filter Customizable Archive dialog, enter the file name of the artifact you want to customize, and click the Go icon.
When the file is located, it is displayed in the Application Resources panel.
Right-click the artifact, and choose Customize, and choose to add the associated library to the project.
The artifacts from the imported library now display in the Application Navigator, under the ADF Library Customizations node, and the artifact you selected to customize opens in the editor window, as shown in Figure 10-6.
Note:
If imported data controls are not displayed in the Data Controls panel, do the following:
From the JDeveloper main menu, choose Tools > Preferences to open the Preferences dialog.
Expand the Business Components node.
Select General.
Select Display Imported ADF Libraries in Data Control Palette.
In the Customization Context window (by default, displayed at the bottom of JDeveloper), select the layer to which you want the customizations written.
All customizations for Oracle ADF business components must be done in the global layer. View layer customizations can be made in any other layer except User. For more information about customization layers, see Section 1.2, "Understanding Customization Layers."
You are now ready to begin customizing your artifact. For more information about customizing specific artifacts, see the following chapters:
There may be occasions when you need to import other customizations into your application workspace. For example, someone else may have made customizations to an application module to which you need to make changes as well. Before you make your customization, you must import that application module into your customization application workspace.
If you need to import customizations made to a single page or page fragment, you can use the Manage Customizations dialog to download the file, as described in Section 2.4.1, "Downloading and Uploading Customization Files Using the Manage Customizations Dialog." Save the customization files to a zip or JAR file.
If you need to import multiple customizations available in the metadata repository for an application, you use the exportMetadata Oracle WebLogic Scripting Tool (WLST) command. For more information, see the "Application Metadata Management Commands" section of Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. This command saves the customization files in a JAR file that you can import into your application workspace. For procedures, see the "Viewing ADF Library Runtime Customizations from exported JARs" section of the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework (Oracle Fusion Applications Edition).
Tip:
You can also use Oracle Enterprise Manager Fusion Applications Control to import and export customization files. For more information, see the "Transferring Metadata Using Fusion Middleware Control" section of the Oracle Fusion Middleware Administrator's Guide. The referenced procedure describes using Fusion Middleware Control, but also applies to Fusion Applications Control.
If you want to use extensions (for example, if you want to add a custom entity object to an existing application module), the extensions must be deployed into the environment to which you have a connection. For more information, see Section 11.14, "Deploying Oracle ADF Customizations and Extensions."
During the process of customization, it is possible that the base application that you are customizing is updated with a patch. If this happens, you might need to resynchronize the configuration files in your local customization application workspace from the exploded EAR of the application you are customizing.
When you create a customization application workspace in your local development environment, workspace configuration files (such as, adf-config.xml, connections.xml, and web.xml) are copied to the local development environment. In some cases, the file is modified to allow you to implement and test customizations locally. When a patch is applied to the base application, these configuration files might change, and would therefore need to be synchronized to your local development environment so that you can continue to implement and test customizations.
JDeveloper allows you to check for and process updates to the workspace configuration files after a patch has occurred on the base application. When you run the check, there are three potential results for each file:
The file in the local development environment does not need to be updated.
The file in the local development environment needs to be updated, and can be updated safely because the local version has not been modified.
The file in the local development environment needs to be updated, but cannot be updated safely because the local version has been modified.
After the check, JDeveloper lets you decide how to handle the update. If you choose to proceed with the updates, backups of the local files are created. You can use the backup files to manually merge changes into the updated files if necessary.
To synchronize your customization application workspace configuration files:
Start JDeveloper in the Oracle Fusion Applications Administrator Customization role, and open your customization application workspace.
From the main menu, choose Application > Synchronize Patch Changes.
The check is run, and the Synchronize Patch Changes dialog displays the results.
If no files in the development environment need updating, the Synchronize Patch Changes dialog gives you the option to review the list of possible updates. Click Yes to view possible updates, or No to close the dialog.
If one or more files need to be updated, the Synchronize Patch Changes dialog displays the files that might be out of date. Files that have been modified locally are indicated with a green icon. Click Yes to update the files, or No to skip the updates and close the dialog.
Note:
If you choose to proceed with the updates, backups of the local files are created. You can use the backup files to manually merge changes into the updated files if necessary.
Before you begin customizing, you must identify the SOA archive (SAR) file to customize, retrieve the configuration plan from the default SOA composite application in MDS Repository, and set up the application workspace and SOA composite application project for MDS Repository customization in JDeveloper using the Oracle Fusion Middleware Developer role. After the application workspace is created, you must exit and reenter JDeveloper using the Oracle Fusion Applications Administrator Customization role.
Perform the following tasks before you begin customizing SOA composite applications with JDeveloper:
Identify the SAR file to customize, and locate it in the APPLICATIONS_BASE/fusionapps/applications/product_family/deploy directory. This directory includes the following files:
Composite SAR (sca_*.jar)
Business process management (BPM) template (bta_*.jar)
List of resource bundle classes (jar_*.jar)
Ensure that the SAR file is marked as customizable by Oracle Fusion Applications. Otherwise, customizations do not survive patching or are not properly patched and merged. For information about which SOA composite applications are customizable, see the product-specific documentation from Oracle Enterprise Repository for Oracle Fusion Applications.
If you encounter the following message when importing the SAR file for customization, it means that Oracle Fusion Applications did not mark the SOA composite application for customizations in JDeveloper and your changes cannot survive patching.
The composite from the archive was not created for customization. If you import the composite for customization, you can customize it but you will have problems to merge your customizations to any new versions of that composite. Do you want to continue? Otherwise, uncheck "Import for Customization" box, and click "Finish" option.
Get the configuration plan from the default SOA composite application in MDS Repository using the following WLST commands:
Identify the default revision of the SOA composite application with sca_getDefaultCompositeRevision. For example:
wls:/mydomain/ServerConfig> sca_getDefaultCompositeRevision("myhost",
"7001", "weblogic", "weblogic",
"FinGlCurrencyUserPreferredCurrencyComposite")
Export the full SOA composite application corresponding to the default revision with sca_exportComposite. For example:
wls:/offline/mydomain/ServerConfig> sca_
exportComposite('http://myhost:8001', 'none', '/tmp/sca_
FinGlCurrencyUserPreferredCurrencyComposite.0.jar',
'FinGlCurrencyUserPreferredCurrencyComposite',
'1.0')
Extract the configuration plan used originally with the export action with sca_extractPlan. For example:
wls:/mydomain/ServerConfig> sca_extractPlan("/tmp/sca_
FinGlCurrencyUserPreferredCurrencyComposite_
rev1.0.jar", "/tmp/FinGlCurrencyUserPreferredCurrencyComposite_
configPlan.xml")
For information about using these commands, see Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.
You must set up the JDeveloper application workspace and SOA composite application project for MDS repository customization.
To set up the JDeveloper application workspace and SOA composite application project for MDS Repository customization:
Start JDeveloper using the Oracle Fusion Applications Developer role.
From the File main menu, choose New, then Applications, then SOA Application, and then OK to create a SOA application with an XX prefix in the application name.
The XX prefix identifies a SOA artifact or object created by the customer and distinguishes it from Oracle Fusion Applications artifacts. You can delete the SOA project named Project1 that was created by default.
The Oracle Fusion Applications SOA composite application references shared SOA artifacts through the SOA-shared repository stored in MDS Repository instead of replicating the shared SOA artifact throughout the Oracle Fusion Applications code source. If the references to the SOA shared repository are not resolved, you receive the error message shown in Figure 10-7.
To resolve references to the SOA-shared repository (oramds:/apps), define an MDS Repository entry in the adf-config.xml file. The entry must point to the MDS repository of the SOA Infrastructure partition in the MDS Repository schema corresponding to the SOA cluster where you plan to deploy the customized SOA composite application. Add a <namespace> attribute with path="/apps" to <metadata-namespaces>:
<namespace metadata-store-usage="mstore-usage_2" path="/apps"/>
Add a <metadata-store-usage> attribute to <metadata-store-usages> for a database-based MDS Repository that points to the MDS repository of the SOA Infrastructure partition in the MDS repository for SOA schema.
Replace the database schema name, database server, database port, and database name with actual values. To identify the user name, password, and database connection information, see the configuration for the MDS data source for SOA in Oracle WebLogic Server Administration Console.
<metadata-store-usage id="mstore-usage_2">
<metadata-store class-name="oracle.mds.persistence.stores.db.
DBMetadataStore">
<property value="soa_mds_schema_name" name="jdbc-userid"/>
<property value="soa_mds_schema_password" name="jdbc-password"/>
<property value="jdbc:oracle:thin:@database_server:
database_port:database_name" name="jdbc-url"/>
<property value="soa-infra" name="partition-name"/>
</metadata-store>
</metadata-store-usage>
The following code shows an <adf-mds-config> example in the adf-config.xml file. The mstore-usage_2 entry resolves references to the SOA shared repository:
<adf-mds-config xmlns="http://xmlns.oracle.com/adf/mds/config">
<mds-config xmlns="http://xmlns.oracle.com/mds/config">
<persistence-config>
<metadata-namespaces>
<namespace metadata-store-usage="mstore-usage_1" path="/soa/shared"/>
<namespace metadata-store-usage="mstore-usage_2" path="/apps"/>
</metadata-namespaces>
<metadata-store-usages>
<metadata-store-usage id="mstore-usage_1">
<metadata-store
class-name="oracle.mds.persistence.stores.file.FileMetadataStore">
<property value="$\{oracle.home}/integration"
name="metadata-path"/>
<property value="seed" name="partition-name"/>
</metadata-store>
</metadata-store-usage>
<metadata-store-usage id="mstore-usage_2">
<metadata-store
class-name="oracle.mds.persistence.stores.db.DBMetadataStore">
<property value="FIN_FUSION_MDS_SOA" name="jdbc-userid"/>
<property value="FIN_FUSION_MDS_SOA" name="jdbc-password"/>
<property
value="jdbc:oracle:thin:@database_server.us.example.com:1521:database_name"
name="jdbc-url"/>
<property value="soa-infra" name="partition-name"/>
</metadata-store>
</metadata-store-usage>
</metadata-store-usages>
</persistence-config>
</mds-config>
</adf-mds-config>
From the File main menu, choose Import, then SOA Archive Into SOA Project to import the SAR file, and then click OK.
In the Project Name field, enter the name of the new SOA project with an XX prefix and select a name to identify the base SOA composite application that you are extending. For example, specify XXFinGlCurrencyUserPreferredCurrencyComposite if you are customizing FinGlCurrencyUserPreferredCurrencyComposite.
Click Next.
In the Composite Archive field, perform the following steps:
Click Browse to select the SAR file to customize that you identified in Section 10.3.1, "Before You Begin Using JDeveloper to Customize."
Accept the default setting for the SOA composite application name.
Select the Import for Customization checkbox.
Click Finish.
Accept the default SOA composite application name to ensure that patching and Oracle SOA Suite can identify whether runtime customizations, JDeveloper customizations, or both types have been applied to the SOA composite application. If the SOA composite application is renamed, patching and SOA have no knowledge of the renamed SOA composite application.
You may see an error icon on a partner link in Design view of the composite.xml file that reports the following error:
Couldn't resolve classpath:/META-INF/wsdl/ServiceException.wsdl
This error is addressed in subsequent steps.
Right-click the SOA composite application project and go to Project Properties, then Libraries and Classpath.
Click Add Library, and select the BC4J Service Client library.
Click OK to close the Add Library dialog.
Click OK to close the Project Properties dialog.
By adding this library to your SOA project, you avoid the design time error you may have received in Step 9d.
Click the Validate icon in the Design view of the composite.xml file. The error shown in Step 9d that you may have received for the partner link should now be resolved.
Make the customization classes and values available in your project.
There are two types of customization classes:
Applications Core customizing classes are available from the Applications Core shared library. See Section 1.2, "Understanding Customization Layers" for the list of Applications Core customization classes permitted in JDeveloper.
Product team customization classes are available in the appropriate EAR file. These customization classes are bundled in a JAR file in the EAR's APP-INF/lib directory. These JAR files follow a naming convention of Ext...jar. Therefore, you must get these JAR files from the deployed area, and perform the following steps:
Put the customization class JAR file under $JDEV_HOME/jdev/extensions.
Add the JAR file in the new project's library and class path setting.
Right-click the SOA composite application project and go to Project Properties, then Libraries and Classpath.
Add the Applications Core library to the SOA composite application project, as shown in Figure 10-8.
Go to Application Resources, then Descriptors, then ADF META-INF, and then adf-config.xml.
Add the appropriate customization class in the MDS Repository configuration, such as oracle.apps.fnd.applcore.customization.SiteCC.
Right-click the SOA composite application project and go to Project Properties, then Libraries and Classpath.
The following libraries have now been added:
Application Core
BC4J Service Client
You must customize the SOA composite application.
To customize the SOA composite application:
Start JDeveloper using the Oracle Fusion Applications Administrator Customization role.
Select the value for the layer in the Customization Context dialog that you want to customize. Figure 10-9 provides details.
See Chapter 12, "Customizing and Extending SOA Components" for instructions about customizing the SOA composite application during design time in JDeveloper and runtime with Oracle SOA Composer, Oracle BPM Worklist, and Oracle Enterprise Manager Fusion Applications Control.
When introducing new components, partner links, and SOA artifacts to the SOA composite application, add the XX prefix to the name to prevent problems with existing and future components that may be introduced in Oracle Fusion Applications patches.
Use the configuration plan that you extracted in Step 3 of Section 10.3.1, "Before You Begin Using JDeveloper to Customize." If any new partner links were added to your SOA composite application, add entries to the configuration plan, if needed. For information about configuration plans, see the "Customizing Your Application for the Target Environment Prior to Deployment" section of the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.
Deploy the SOA composite application using the same revision you found in Section 10.3.1, "Before You Begin Using JDeveloper to Customize."
Table 10-1 describes how to customize SOA resource bundles.
Table 10-1 Customizing SOA Resource Bundles
| To Modify or Add Translatable Strings for... | Description |
|---|---|
|
An existing human task, activity guide, or BPEL process |
This feature is not supported in the first version of Oracle Fusion Applications (for example, modifying the human task title). Runtime modifications do not support this functionality and the |
|
Human task mapped attributes |
This feature is not supported in the first version of Oracle Fusion Applications. Translations for human task mapped attribute labels are defined in the following resource bundle: oracle.bpel.services.workflow.resource.WorkflowLabels For this version, the |
|
Server name in Federated Worklist on the Oracle Fusion Applications home page |
The server names that appear in the Federated Worklist on the Oracle Fusion Applications home page are defined in the following file: oracle/apps/common/acr/resource/ResourcesAttrBundle.xliff See Section 11.12, "Customizing or Adding Resource Bundles" for instructions about overriding strings in XML localization interchange file format (XLIFF) resource bundles. |
Note:
Oracle Fusion Applications automatically seed human task-protected mapped attributes and labels, but do not seed public mapped attributes. If you require human task mapped attributes, it is recommended that you use the public mapped attributes. However, if protected mapped attributes are required, then add the XX prefix to your label names to prevent problems with Oracle Fusion Applications seeded labels.
|
 Copyright © 2011, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
