Skip Headers
Oracle® Fusion Applications Extensibility Guide
11g Release 1 (11.1.2)
Part Number E16691-03
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
PDF · Mobi · ePub

12 Customizing and Extending SOA Components

This chapter describes how to customize (edit) service-oriented architecture (SOA) components during runtime in a deployed composite with a runtime tool such as Oracle BPM Worklist, Oracle SOA Composer, or Oracle Enterprise Manager Fusion Applications Control or customize and extend (create) SOA components during design time in JDeveloper. It also provides recommendations for merging runtime customizations from a previously deployed revision into a new revision and instructions for synchronizing customized flexfields in the SOA MDS repository.

This chapter includes the following sections:

For information about troubleshooting SOA issues, see Chapter "Troubleshooting Oracle SOA Suite" of the Oracle Fusion Applications Administrator's Guide.

Notes:

12.1 About Customizing and Extending SOA Components

SOA provides an enterprise architecture that supports building connected enterprise applications to provide solutions to business problems. SOA enables you to develop enterprise applications as modular business web services that can be integrated and reused, resulting in a flexible, adaptable IT infrastructure. SOA separates business functions into distinct units, or services.

Oracle SOA Suite provides a complete set of service infrastructure components for designing, deploying, and managing composites. A composite is an assembly of services, service components, and references designed and deployed in a single application. Wiring between the services, service components, and references enables message communication.

Oracle SOA Suite consists of SOA components that comprise the business logic and processing rules in a SOA composite. You can include components such as the following in a SOA composite:

For more information about these components, see Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

Oracle SOA Suite supports the following types of customizations and extensions of these components:

The tool to use depends on the component you are customizing or extending and whether you are performing these tasks during runtime or design time. Table 12-1 provides details.

Note:

If you are customizing approval configuration and assignment rules or nonapproval business rules for a deployed project (either for Oracle SOA Suite or Oracle BPM Suite), always use Oracle BPM Worklist or Oracle SOA Composer. If you are customizing approval configuration and assignment rules or nonapproval business rules as part of a new Oracle BPM Suite project being extended in Oracle Business Process Composer, then use Oracle Business Process Composer. For information about using Oracle Business Process Composer, see Chapter 13, "Customizing and Extending Oracle BPM Project Templates."

Table 12-1 Customization and Extension Tools for Oracle SOA Suite

To Perform These Tasks... Use This Tool... Use This Tool At... Tool User

Customize business rules:

  • Approval configuration and assignment rules

  • Nonapproval business rules

  • Oracle BPM Worklist (recommended) or Oracle SOA Composer

  • Oracle SOA Composer

Note: If you use Oracle SOA Composer to customize approval configuration and assignment rules during runtime, changes in subsequent revision patches are not applied successfully.

Runtime in a deployed composite

Runtime in a deployed composite

Technical analyst

Business analyst

Customize domain value maps

Oracle SOA Composer

Runtime in a deployed composite

Business analyst

Customize composite endpoint properties such as the following:

  • Attached Oracle Web Services Manager (OWSM) security policies

  • Service and reference binding component properties

Oracle Enterprise Manager Fusion Applications Control

Runtime in a deployed composite

System administrator

  • Customize or extend business rules

  • Customize or extend BPEL processes

  • Customize or extend human tasks

  • Customize or extend Oracle Mediators

  • Customize composite components such as binding components and wires

  • Extend or customize transformations

  • Extend WSDLs or XSDs

  • Extend business rules

  • Extend JCA adapters

JDeveloper (when logged in with the Customization Developer role)

Design time (when complete, you must deploy the composite)

System integrator

Notes:

  • You cannot customize human tasks, BPEL processes, and Oracle Mediators during runtime in a deployed composite.

  • When using Oracle SOA Composer, you can save your customizations in a sandbox environment without applying them to a running instance and later return to the sandbox to make additional customizations. These customizations are only applied to the running instance when you click Commit.

12.1.1 Before You Begin Customizing SOA Composites

Before you customize SOA components, you should be familiar with the Oracle Fusion application architecture that enables customizations, as described in Chapter 1, "Customizing and Extending Oracle Fusion Applications." You should also understand the typical workflows for working with runtime customizations, as described in Chapter 2, "Understanding the Customization Development Lifecycle."

In addition, you will need to perform the following tasks before you can begin customizing your application:

12.2 Customizing SOA Composites

As described in Table 12-1, you can customize SOA components during runtime in a deployed composite with a runtime tool. This section provides an overview of these tasks and provides references to additional documentation for more specific instructions.

Note:

You cannot customize SOA components in CRM Application Composer. However, you can extend a business event in CRM Application Composer and use the Event notification action to notify a SOA composite by email of the occurrence of the event. For information about extending events in CRM Application Composer, see Section 4.2, "Editing Objects."

Task: Launch the Runtime Customization Tool

Use a web browser to launch the tools shown in Table 12-2 for customizing approval configuration and assignment rules, nonapproval business rules, domain value maps, and composite endpoint properties at runtime:

Table 12-2 Launching the Customization Tool

For Customizing... Launch... By Entering...

Business rules

    

  • Approval configuration and assignment rules

  • Oracle BPM Worklist (recommended)

  • Oracle SOA Composer

Note: If you use Oracle SOA Composer to customize approval configuration and assignment rules during runtime, changes in subsequent revision patches are not applied successfully.

 
http://host:port/integration/worklistapp


http://host:port/soa/composer

  • Nonapproval business rules

Oracle SOA Composer

 
http://host:port/soa/composer

Domain value maps

Oracle SOA Composer

 
http://host:port/soa/composer

Composite endpoint properties such as OWSM security policies and binding component properties

Oracle Enterprise Manager Fusion Applications Control

 
http://host:port/em

Task: Select the Data to Customize

After accessing the runtime customization tool to use, select the data to customize.

Task: Customize Business Rules

Two categories of rules are available:

Task: Customize Domain Value Maps

You can customize domain value map rows included in a deployed composite in Oracle SOA Composer, as shown in Figure 12-5. For more information, see Chapter "Using Oracle SOA Composer with Domain Value Maps" of the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

Figure 12-5 Domain Value Map Customizations in Oracle SOA Composer

Editing DVMs in Oracle SOA Composer

Task: Customize Composite Endpoint Properties

You can customize endpoint address properties for an external reference such as OWSM security policies and binding components included in a deployed composite in Oracle Enterprise Manager Fusion Applications Control.

Figure 12-6 provides details about customizing OWSM security policies. For more information, see Section "Managing SOA Composite Application Policies" of the Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite.

Figure 12-6 Security Policy Customizations in Oracle Enterprise Manager Fusion Applications Control

Editing policies in Enterprise Manager

Figure 12-7 provides details about customizing binding component properties for services and references. For more information, see Chapter "Configuring Service and Reference Binding Component Properties" of the Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite.

Figure 12-7 Binding Component Property Customizations in Oracle Enterprise Manager Fusion Applications Control

Changing binding component values

Task: Synchronizing Customized Flexfields in the SOA MDS Repository

SOA composites in Oracle Fusion Applications reference copies of the original XSD schema files included in the SOA Metadata Services (MDS) repository. When you customize and deploy Oracle Fusion Applications flexfields (or upgrade the base table, after which the flexfields are automatically re-applied), which result in a new XSD being generated in the Oracle Fusion Applications MDS, the updated XSD files must be synchronized in SOA MDS for use in the fact models in business rules.

To perform this synchronization, a special SOA composite named UpdateSOAMDS is included with Oracle Fusion Applications. By default, the UpdateSOAMDS composite is automatically deployed. When a synchronization is required, you manually invoke an instance of this composite to synchronize the updated XSD files in SOA MDS. You can view the results of this synchronization in the audit trail in Oracle Enterprise Manager Fusion Applications Control.

  1. Invoke the UpdateSOAMDS composite.

    1. Log in to Oracle Enterprise Manager Fusion Applications Control.

    2. In the navigation pane, expand soa-infra and the domain.

    3. Select the UpdateSOAMDS composite.

    4. At the top of the Dashboard page for UpdateSOAMDS, click Test.

    5. In the Operation list, select the operation to perform, as shown in Figure 12-8.

      Figure 12-8 Operations to Perform

      Test operations

      Table 12-4 describes the operations available for selection.

      Table 12-4 Operations

      Operation Description

      updateDuring

      Select to specify how far back in time to go to get flexfield updates for synchronizing in SOA MDS.

      updateSince

      Select to specify the time from which you want to get flexfield updates for synchronizing in SOA MDS.

    6. In the Value field of the Input Arguments section, enter a value, as shown in Figure 12-9.

      Figure 12-9 Value Field

      Specify a value

      Table 12-5 provides details about the value to specify.

      Table 12-5 Operation Values

      If You Selected... Description

      updateDuring

      This operation uses the xsd:duration type as input to obtain the data. For example:

      • Enter P50D to go back fifty days to get flexfield updates that occurred.

      • Enter P1M2DT3H to go back one month, two days, and three hours to get flexfield updates that occurred.

      updateSince

      This operation uses the xsd:dateTime type as input to obtain the data.

      For example, entering 2011-02-10T00:00:00 gets flexfield updates that have occurred since February 10, 2011.

    7. Click Test Web Service.

      The list of XSD schema files synchronized in SOA MDS is returned as output in the Response tab, as shown in Figure 12-10.

      Figure 12-10 Test Output

      Test output

      All rule dictionaries in SOA MDS that use the impacted XSD schemas are altered. The data model of the rule dictionaries is modified and the fact types are re-imported. After re-importing the XSD schemas, the rule dictionary is saved in SOA MDS.

      The JAXB 2.0 classes for the fact type model of the rule dictionaries that have been altered are regenerated and compiled into the appropriate composite SCA-INF/gen-classes directories.

      Other SOA instances in the cluster are notified of the flexfield customizations.

      The composite class loader for the SOA composites where the rule dictionary was altered is invalidated and a new class loader is extended with the next request for the composite.

      The SOA instances not involved in updating the rule dictionary in SOA MDS regenerate the JAXB 2.0 classes for the composites that comprise a rule dictionary where the fact type model was altered.

  2. View the results in the audit trail.

    1. In the Recent Instances section of the Dashboard page, click the instance ID.

    2. In the Trace section of the Flow Trace page, click the UpdateSOAMDS BPEL service component.

    3. View the list of XSD schema files synchronized in SOA MDS in the audit trail, as shown in Figure 12-11.

      Figure 12-11 Audit Trail Results

      Audit trail results

Note:

In previous releases, Oracle BPM Worklist included a feature known as flex fields. Starting with Release 11g R1 (11.1.1.4), flex fields are now known as mapped attributes. Do not confuse Oracle BPM Worklist flex fields with Oracle Fusion Applications flexfields; they are completely different features.

12.3 Merging Runtime Customizations from a Previously Deployed Revision into a New Revision

After using a composite customized at runtime for a period of time, a new patch revision of the composite may become available. Repeating the process of customizing the new revision of the composite at runtime can be cumbersome and time-consuming. To avoid these challenges, use the OPatch tool. The OPatch tool is an Oracle-supplied, Java-based utility that enables you to merge customizations made during runtime in a previously deployed composite into a new patch revision of the composite. OPatch preserves your runtime customizations and prevents you from having to re-enter the customizations again for the next patch revision.

OPatch merges a new patch revision into a composite that was previously customized during both design time in JDeveloper and runtime in Oracle SOA Composer, Oracle BPM Worklist, or Oracle Enterprise Manager Fusion Applications Control. For specific procedures on patching SOA composites with OPatch, see Oracle Fusion Applications Patching Guide.

Task: Merge Runtime Customizations from a Previously Deployed Revision into a New Revision

Before using the OPatch tool to merge runtime customizations from a previously deployed revision into a new revision, review the recommendations in Table 12-6 to ensure that you merge customizations successfully.

Table 12-6 Recommendations on Merging Patch Revision Customizations and Extensions

Component Recommendation

Deletion of base components

Delete only components you added as part of the customization, and not components that are part of the base revision. This is because the deletion of base components does not survive the move to the new revision, but the deletion of the wiring does. If you delete an existing base component, it comes back again when you get the new revision, which still has the component. However, the wire deletion survives the upgrade because the composite.xml file is customizable.

Business rules

If business rules are customized at runtime, and those runtime customizations must be preserved in subsequent revisions of the base version of the composite, it is recommended that the rules dictionaries be split into two dictionaries and linked using the dictionary linking functionality.

The base rule, linked dictionary contains the data model of the dictionary and the custom rules dictionary contains all the rules customized at runtime. The OPatch process preserves the customized dictionary when it merges the customized application with subsequent versions of the application. Business rules are used in different scenarios and the following information identifies how to handle each situation.

  • Approval configuration and assignment rules

    These rules are used within human tasks to determine approvers and the routing of human tasks. Approval rules are always generated as base and custom dictionaries at design time. No further configuration is necessary at design time. Runtime customizations:

    If you must customize approval configuration and assignment rules during runtime, use only Oracle BPM Worklist to perform this task. Using Oracle BPM Worklist enables:

    -) Approval assignment and configuration rules to automatically be stored in a custom rules dictionary (Rule.rules). The custom rules dictionary is initially shipped with only sample, preseeded rules. The custom rules dictionary is separate from the base rule, linked dictionary (RuleBase.rules). The base rule, linked dictionary contains Oracle Fusion Applications fact definitions. Revision patches are applied to the base rule, linked dictionary.

    -) Changes in subsequent revision patches to be applied successfully to the base rule, linked dictionary.

    If you use Oracle SOA Composer to customize approval configuration and assignment rules during runtime, changes in subsequent revision patches are not applied successfully.

    Design time customizations:

    You cannot customize existing rules that are part of the base version of the composite at design time in JDeveloper. However, you can extend new rules that you later customize.

  • Nonapproval business rules

    These rules are used directly in processes like BPEL and BPMN outside of the context of a human task. These dictionaries are not generated as linked dictionaries in JDeveloper and must be manually split as linked dictionaries.

    Runtime customizations:

    If the dictionaries are split as linked dictionaries, ensure that only the linked dictionaries are customized from Oracle SOA Composer. Identification of the base rule and linked rule dictionary is up to you to develop.

    Design time customizations:

    You cannot customize existing rules that are part of the base version of the composite at design time in JDeveloper. However, you can extend new rules that you later customize.

Default URLs for service binding components

Use default URLs for service binding components. If the revision is used in the URL for service binding components, when the SOA composite is patched using OPatch, the revision of the composite is customized. In this case, the reference to URLs for service binding components fails to work. In this scenario, you must manually update all the URL references for service binding components.

Oracle BPEL Process Manager scope activity

If a base composite team removes the scope activity in the next revision of the composite, when a vertical composite team or customer runs the OPatch utility to apply the new revision of the composite to their customized version, all customizations they performed on that scope activity in the first revision are lost.

Renaming of a composite whose SOA archive (SAR) file is imported in JDeveloper

When importing a SAR file for customization in JDeveloper, the composite must not be renamed. In addition, if you rename a composite, OPatch cannot detect runtime customizations made in Oracle SOA Composer, Oracle BPM Worklist, and Oracle Enterprise Manager Fusion Applications Control. You must manually re-apply those customizations.

Base revision of a composite with JDeveloper customizations

Assume you customize the base revision of a composite with the Customization Developer role in JDeveloper, and then deploy the composite. When the base revision is updated and a newer revision is made available, the customer uses OPatch to apply the patch revision. OPatch may then fail because there are JDeveloper customizations in the deployed composite.

To resolve this issue, perform the following steps:

  1. Open the customized composite with the Default Role in JDeveloper.

  2. Import the patched base version 2 SAR file into this composite project extended in Section 10.3, "Customizing SOA Composites with JDeveloper."

  3. Restart JDeveloper with the Customization Developer role.

  4. Open the above customized composite. Error messages are shown in case of conflicts.

  5. Resolve the conflicts in the composite.

  6. Deploy the composite to the SAR file. The new SAR file should be replaced by the patched base version 2 SAR file.

  7. Proceed with the OPatch process.

Note: Ensure that the backup of the SAR files is taken properly.

12.4 Extending or Customizing Custom SOA Composites

You can customize or extend some SOA components during design time in JDeveloper when logged in with the Customization Developer role. Components that are extended in JDeveloper can be further customized in JDeveloper when again logged in with the Customization Developer role. Customization changes are maintained in separate .xml files from the base component files. Note that you cannot make customizations in Source view in JDeveloper; only customizations made in Design view are supported.

Notes:

  • New artifacts extended in the composite survive patching.

  • Ensure that you provide unique names for any new components and artifacts that you extend. For example, prefix each component and artifact name with a unique identifier.

Table 12-7 describes which existing base composite artifacts in a composite can be customized and which new artifacts can be extended when logged in to JDeveloper with the Customization Developer role.

Table 12-7 Customizable and Extendable Artifacts in Customization Developer Role

Artifacts Existing Artifact in Base Composite is Customizable with Customization Developer Role? Artifact is Extendable with Customization Developer Role?

Composite Components

Yes

Yes

BPEL process

Yes

Yes

Oracle Mediator

Yes

Yes

Human task

No

Yes

Business rule

No

Yes

XSLT Map

No

Yes

Cross references (XREFs)

No

No

Domain value maps

No

No

XSD

No

Yes

WSDL

No

Yes

Business events

No

Yes

JCA Adapters

No

Yes

Table 12-8 provides more specific details about which artifacts can be extended when logged in to JDeveloper with the Customization Developer role.

Table 12-8 Artifact Extensibility in JDeveloper with Customization Developer Role

Artifact Extendable? Description

Composite

No

Only one composite per Oracle SOA Suite project is permitted.

BPEL process

Yes

Can drag a BPEL process from the Component Palette into the SOA Composite Editor or Oracle BPEL Designer.

Oracle Mediator

Yes

Can drag an Oracle Mediator from the Component Palette into the SOA Composite Editor or Oracle BPEL Designer.

Human task

Yes

Can drag a human task from the Component Palette into the SOA Composite Editor or Oracle BPEL Designer.

Business rule

Yes

Can drag a business rule from the Component Palette into the SOA Composite Editor or Oracle BPEL Designer.

XSLT Map

Yes

Can extend a transformation in a transform activity in Oracle BPEL Designer or the Mediator Editor.

Domain Value Maps

No

The New Gallery dialog is disabled with the Customization Developer role.

Cross References (XREFs)

No

The New Gallery dialog is disabled with the Customization Developer role.

XSD

Yes

Right-click an Oracle SOA Suite project and select SOA, or as the result of extending other SOA artifacts.

WSDL

Yes

Right-click an Oracle SOA Suite project and select SOA, or as the result of extending other SOA artifacts.

Business events

Yes

Subscribe to or publish events for a BPEL process or Oracle Mediator component in the SOA Composite Editor, Oracle BPEL Designer, or Mediator Editor.

JCA adapters

Yes

Drag adapters from the Component Palette into the SOA Composite Editor or Oracle BPEL Designer.

Task: Customize a Base Composite in JDeveloper

This section provides an overview of the steps for customizing a base composite of Oracle Fusion Applications in JDeveloper. These steps assume you know how to set up the customization layer through the adf-config.xml editor and know the customization classes defined by Oracle Fusion Applications. For more information, see Chapter "Customizing SOA Composite Applications" of the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

Note:

See Section 10.3.2, "Setting Up the JDeveloper Workspace and Composite Project for MDS Customization" for instructions on setting up the JWS workspace and composite project when customizing Oracle Fusion Applications composites.

  1. Install Oracle Fusion Applications with a SOA composite that you want to customize in JDeveloper.

  2. In Oracle Enterprise Manager Fusion Applications Control, go to the home page of the SOA composite to export.

  3. From the SOA Composite menu at the top of the page, select Export.

  4. Obtain the base SAR file for initially customizing from other locations, including:

    • Checking out the base composite project from the source control system where the base composite project was checked in by the base development team. This way, no SAR file deployment, export command, or import command is involved.

    • Importing the base composite SAR file that was deployed from the base composite project.

    • Importing the base composite SAR file that was exported (without runtime changes) from the Export Composite page of the Oracle Enterprise Manager Fusion Applications Control installation from which the SOA server is managed.

  5. Extend layer values for customization to the CustomizationLayerValues.xml file (can perform this task in JDeveloper or from the directory structure).

  6. Start JDeveloper in the Default Role.

  7. Extend a new composite application.

  8. From the File main menu, select Import > SOA Archive Into SOA Project to import the exported SAR into the new composite in JDeveloper.

  9. In the Import Composite Archive wizard, select the Import For Customization checkbox.

  10. From the Tools main menu, select Preferences > Roles > Customization Developer.

  11. Restart JDeveloper, and customize the layers of the composite.

  12. Right-click the project and select Deploy to extend a customized SAR of the SOA composite in Oracle Fusion Applications.

Note:

After performing the initial customizations described in these procedures, you can no longer export the composite from the runtime. This is because the composite is a merged composite, and no longer the original base composite.

For more information on exporting SAR files, see Section "Exporting a Running SOA Composite Application" of Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite.

Task: Extend or Customize Custom Business Rules

You can extend business rules in a composite during design time in JDeveloper when logged in with the Customization Developer role. After extending these business rules, you can further customize them in JDeveloper when again logged in with the Customization Developer role. You cannot customize existing business rules that are part of the base version of the composite.

For information on customizing business rules during runtime, see Section 12.2, "Customizing SOA Composites."

Task: Extend or Customize Custom BPEL Processes

You can extend or customize BPEL processes in a composite during design time in JDeveloper when logged in with the Customization Developer role. For example, you can perform the following tasks:

For more information about extending or customizing BPEL processes, see Part "Using the BPEL Process Service Component" of Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

Task: Extend or Customize Custom Human Tasks

You can extend human tasks in a composite during design time in JDeveloper when logged in with the Customization Developer role. After extending these human tasks, you can further customize them in JDeveloper when again logged in with the Customization Developer role. You cannot customize existing human tasks that are part of the base version of the composite.

For more information on extending human tasks, see Part "Using the Human Workflow Service Component" of Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

Task: Extend or Customize Custom Oracle Mediators

You can extend or customize Oracle Mediators in a composite during design time in JDeveloper when logged in with the Customization Developer role. For example, you can perform the following tasks:

For more information, see Part "Using the Oracle Mediator Service Component" of Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

Task: Customize Composite Components

You can customize composite endpoint properties in a composite during design time in JDeveloper when logged in with the Customization Developer role. For example, you can perform the following tasks:

For more information, see Chapter "Developing SOA Composite Applications with Oracle SOA Suite" of Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

Task: Extend or Customize Transformations (in a Transform Activity)

You cannot customize existing transformations that are part of the base composite in JDeveloper. However, you can extend a new transform activity in a BPEL process or in the Transformation Map dialog of an Oracle Mediator during design time in JDeveloper when logged in with the Customization Developer role. After extending the transformation, you can further customize it in JDeveloper when again logged in with the Customization Developer role. For example, you can perform the following tasks:

Task: Extend XSD or WSDL Files

You can extend an XSD schema or WSDL document in JDeveloper when logged in with the Customization Developer role.

  1. Right-click the Oracle SOA Suite project in the Application Navigator.

  2. Select SOA.

  3. Select the artifact to extend:

    • Create XML Schema

      Invokes the Create XML Schema dialog for extending a new XML schema file in the project. When complete, the new schema file automatically opens.

    • Create WSDL Document

      Invokes the Create WSDL dialog to extend a new WSDL file in the project.

Task: Extend Business Events

You can extend business events in JDeveloper when logged in with the Customization Developer role.

For more information, see Chapter "Using Business Events and the Event Delivery Network" of Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

Task: Extend JCA Adapters

You can extend JCA adapters in JDeveloper when logged in with the Customization Developer role.

For more information, see Oracle Fusion Middleware User's Guide for Technology Adapters.

12.5 Deploying SOA Composite Customizations and Extensions

You must redeploy a customized or extended composite after making changes in JDeveloper. The development and deployment phase is as follows:

For more information, see Chapter "Customizing SOA Composite Applications" of the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

12.6 Extending a New Oracle SOA Suite Service

You can extend new SOA composite services to integrate with Oracle Fusion Applications. This section provides an overview of tasks for extending and consuming new services and provides references to documentation that more specifically describes these tasks.

Task: Setting Up a Development Environment

You must set up and configure a development environment in JDeveloper to create new Oracle SOA Suite services. For more information, see Part "Getting Started Building Your Oracle Fusion Applications" of Oracle Fusion Applications Developer's Guide.

Task: Using JDeveloper to Create Applications, Projects, and Services

Whenever you create new projects, you must first create an application using templates provided by JDeveloper. For more information, see Chapter "Setting Up Your JDeveloper Workspace and Projects" of Oracle Fusion Applications Developer's Guide.

You can select an Oracle SOA Suite project template when creating a JDeveloper application. For more information about creating Oracle SOA Suite projects, see Chapter "Developing SOA Composite Applications with Oracle SOA Suite" of Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

You can extend an Oracle Application Development Framework (ADF) Business Component service to be consumed by the SOA composite. The Oracle ADF Business Component service is used for connecting Oracle ADF applications using service data object (SDO) data formats with the SOA composite. For more information, see Chapter "Getting Started with Binding Components" of Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

Task: Understanding Common Service Use Cases and Design Patterns

There are fundamental patterns for Oracle Fusion Applications developers to follow when building applications involving Oracle ADF and Oracle SOA Suite. These patterns fall into three main categories:

For more information about these and other design categories, see Part "Common Service Use Cases and Design Patterns" of Oracle Fusion Applications Developer's Guide.

Task: Using Oracle SOA Suite with the Oracle Metadata Services Repository

The Oracle Metadata Services (MDS) Repository contains metadata for certain types of deployed applications, such as SOA composites. You can store Oracle Fusion Applications artifacts and custom artifacts in the MDS repository. You connect to the repository to consume these artifacts.

For more information about MDS, see Chapter "Managing the Metadata Repository" of Oracle Fusion Middleware Administrator's Guide.

For more information about creating a connection from Oracle SOA Suite to MDS, using the Oracle SOA Suite MDS repository to store custom artifacts, and connecting to and consuming artifacts from the Oracle SOA Suite MDS repository, see Section "Creating a SOA-MDS Connection" of Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

Task: Discovering Oracle Fusion Application Services

Oracle Fusion Applications includes web services that are available for public consumption. These web services are defined in Oracle Enterprise Repository and available for discovery. When extending Oracle Fusion Applications and building SOA composites to invoke services built by Oracle Fusion Applications, you can use Oracle Enterprise Repository to perform the following tasks:

For more information about Oracle Enterprise Repository, see Oracle Fusion Middleware User Guide for Oracle Enterprise Repository.

Task: Securing Oracle Fusion Applications and Services

You must secure Oracle Fusion Applications and services to be consumed by SOA composites.

For more information about Oracle Fusion Applications security, see Oracle Fusion Applications Security Guide.

For more information about ADF Application Artifacts security, see Chapter 15, "Customizing Security for ADF Application Artifacts."

For more information about web services security, see Chapter "Securing Web Services Use Cases" of Oracle Fusion Applications Developer's Guide.

Task: Deploying SOA Composites and Services

You must deploy SOA composites and the services to be consumed.

For more information about deploying SOA composites, see Chapter "Deploying SOA Composite Applications" of Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

For more information about deploying external references such as web services, see Chapter "Deploying Web Services Applications" of Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

Task: Understanding Fusion Applications Deployment Topology

An enterprise deployment is an Oracle guidelines blueprint based on proven Oracle high-availability and security technologies and recommendations for Oracle Fusion Applications. For more information about deployment in an enterprise environment, see Oracle Fusion Applications Enterprise Deployment Guide.

Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Feedback page
Contact Us