2. Composite Deployment in Oracle SOA Suite 11g
CON8568
Antonella Giovannetti
Senior Technical Support Engineer
Oracle Support, SOA Proactive Services
09, 2014
Copyright © 2014, Oracle and/or its affiliates. All rights reserved. |

3. .

4. Program Agenda 1
From Design to Runtime From One to Many Environments Managing Deployed Composites Troubleshooting Additional Resources Q&A 2 3 4
In this presentation we will cover:
The process to deploy a SOA application to a SOA environment.
How to deploy the same application to different environments with minimal manual changes to your composites.
Operations you can perform on the deployed composites (Redeploy and Undeploy) .
Troubleshooting tips and additional resources. 5 6

5. From Design to Runtime SOA Composite Target Environment Prepare
Package
SOA Composite(s)
Deploy
SOA Composite(s)
To be able to move your SOA composite design to q running environment you need to perform three basic steps. 
1. Prepare your target environment
2. Package your application into a deployable archive
3. Deploy the archive
SOA Composite
Target Environment

6. From Design to Runtime
Preparing
Requirements
SOA Domain with Admin and Managed WebLogic Servers
Single Server or Clustered Environment
WLS servers must be able to connect to the SOA Database Schema.
DB Schema must have at least one Partition. Oracle SOA Suite automatically includes a partition called default.
A target environment is one in which you have a SOA domain with one or  more administration and managed Weblogic servers.
It can be a single or cluster environment
The weblogic servers should be able to connect to the SOA database repository. This repository must have at least one DB partition defined.  By default SOA comes with a partition called DEFAULT.
From the perspective of an administrator a db partition will allow you to manage the objects in the partition as a whole.

7. From Design to Runtime Resources Database Adapter and AQ Adapter
Preparing
Resources
Database Adapter and AQ Adapter
JDBC Data Sources and JDBC Connection Pools
JMS Adapter
Queues to Enqueue / Dequeue Messages
Human Workflow
Configure alternative identity service provider (Oracle Internet Directory, Microsoft Active Directory, or Oracle iPlanet). WebLogic embedded LDAP (default) is not supported in a SOA cluster
OWSM
Configure OWSM policies for Authentication / Authorization
B2B
Deploy B2B Trading Partner Agreements from design-time to the run-time repository
To prepare your environment you need to know which resources are needed by the SOA composite (s). Here are some of them:
1. Db or AQ adapters: you need to create/configure your jdbc datasources as well as connection pools
2. JMS adapters: you need to define the queues for incoming and outgoing messages.
3. If you are using human workflow, you may need to configure an identity provider different from the one embedded in Weblogic. Specially if you are in a cluster environment, as this is not supported.
4. Configure OWSM polices for authentication and authorization 
If you are using B2B  then you need to deploy the trading agreements from the design time to the target environment

8. From Design to Runtime Type of archive files: Artifacts Included:
Packaging
Deployable Archives
Type of archive files:
SOA Archive (SAR): single composite. Special JAR file with the prefix sca_.
sca_<composite name>_rev<version ID>.jar
ZIP file: multiple composites. Contains multiple SARs and/or Metadata Archives (MARs)
Artifacts Included:
Binding and Service Components
References to Oracle B2B agreements, OWSM policies, and human workflow task flows.
WSDL and XSD files
There are two types of archive files depending if you are packaging one or more applications.
A SA
Usually has the format: sca_<composite name>_rev<version ID>.jar
For example: sca_HelloWorld_rev1.0.jar.
ZIP file (multiple composites). Contains multiple SARs and/or Metadata Archives (MARs)
Artifacts Included:
Binding and Service Components
References to Oracle B2B agreements, OWSM policies, and human workflow task flows.
WSDL and XSD files
R file is a special JAR file that requires the prefix sca_

9. From Design to Runtime Oracle JDeveloper WLST Commands ANT Scripts
Packaging
Packaging Tools
Oracle JDeveloper
WLST Commands
ANT Scripts
Maven Plug-In
NEW
12c

10. From Design to Runtime Oracle JDeveloper Packaging Tools
Right-click the SOA project -> Deploy -> Deploy to Application Server
Creates the SAR file and Deploys to the Application Server
Right-click the SOA project -> Deploy -> Deploy to SAR
Creates the SAR file but does NOT deploy
Useful when:
WebLogic Server may not be running, but you want to create the archive file.
Need to create the archive file to deploy from the FMW Control Console.
There are two ways to package an application(s) in Jdeveloper. You can deploy a composite and Jdeveloper will automatically create a SAR file for you or you can actually “deploy” to a SAR file and create the archive file without deploying it

11. From Design to Runtime WLST and ANT Tool Script/ Command Syntax
Packaging
WLST and ANT
Tool
Script/
Command
Syntax
Example
Result
ANT
ant-sca-package
ant -f ant-sca-package.xml
-DcompositeDir
-DcompositeName
-Drevision
[-Dsca.application.home ]
[-Doracle.home]
-DcompositeDir=/tmp/HelloSOAApplication/
-DcompositeName=HelloSOAComposite
-Drevision=1.0
sca_HelloSOAComposite_rev1.0.jar
WLST
sca-package
sca_package(
compositeDir,
compositeName,
revision,
[appHome],
[oracleHome])
sca_package (
"/tmp/HelloSOAApplication/",
"HelloSOAComposite",
“1.0”)
WLST and ANT offer commands and scripts to package your SOA application. Here are the syntax and example for both. There are very similar and both of them will created the same SAR file which needs to have the format of sca_<composite_name>_rev<revision number>.jar

12. From Design to Runtime Maven Plug-In Packaging Tools
NEW
12c
Maven Plug-In
Uses archetypes to compile, package, deploy, test, and undeploy a SOA composite application.
More information:
Developing SOA Applications with Oracle SOA Suite
48 Using the Oracle SOA Suite Development Maven Plug-In

13. From Design to Runtime
Deployment
Deployment Tools
Jdeveloper (single/multiple SOA applications and Shared Data)
WLST Commands
ANT Scripts
FMW Control
Maven Plug-In
So far we have prepared our Target environment and created our deployable archive file. Now we need to actually deploy the archive file. Here is a list of the tools available for this:
JDeveloper
WLST Commands
ANT Scripts
FMW Control
Maven Plug-In

14. From Design to Runtime Need to create a Project Deployment Profile
JDeveloper – Single application
Need to create a Project Deployment Profile
By default JDeveloper creates a profile with the name of your SOA project
Deploy the Profile to the Application Server

15. From Design to Runtime
Deployment
JDeveloper – Multiple Applications
A SOA Bundle Profile includes two or more SAR files (ZIP)
Archive file is then deployed to an application server.
You cannot deploy applications that are dependent upon one another in the same SOA bundle profile. For example, if application A calls application B, then you must first deploy application B separately.

16. From Design to Runtime Create the SOA Bundle
Deployment
JDeveloper – Multiple applications
Create the SOA Bundle
From the Application menu, select Application Properties -> Deployment
Select the composites
Deploy the bundle. Application > Deploy > SOA_Bundle_Name

17. From Design to Runtime
Deployment
JDeveloper – Applications Sharing Data
Create a JAR with the shared data (WSDLs, XSDs, etc.) called a MAR.
Create a bundle with the composite and the MAR file and then deploy.
When applications in the same bundle share data you need to create a jar file with the shared artifacts and attached that to the SAR file. Here are two screenshots one showing how you create the jar file in JDEV and the other how you create the bundle by selecting the composite and the jar file with the shared artifacts.

18. From Design to Runtime WLST Commands Command Use Example
Deployment
WLST Commands
Command
Use
Example
sca_deployComposite
Deploy a SOA composite application.
Does not do the packing
sca_deployComposite(" "/tmp/sca_HelloWorld_rev1.0.jar")
sca_undeployComposite
Undeploys a currently deployed SOA composite application
sca_undeployComposite(" "HelloWorld", "1.0")
sca_listDeployedComposites
Lists all SOA composite applications deployed to the SOA platform
sca_listDeployedComposites('myhost', '7001', 'weblogic', 'welcome1')
Here are the WLST commands for deploy, undeploy and list deployed composites. There is much more information about these commands and others in the
Oracle Fusion Middleware WebLogic Scripting Tool Command Reference
9 Oracle SOA Suite Custom WLST Commands
Complete List:
Oracle Fusion Middleware WebLogic Scripting Tool Command Reference
9 Oracle SOA Suite Custom WLST Commands

19. From Design to Runtime ANT Scripts Scripts Use Example
Deployment
ANT Scripts
Scripts
Use
Example
ant-sca-deploy.xml
Deploy a SOA composite application.
Does not do the packing
ant -f ant-sca-deploy.xml
-DserverURL=
-DsarLocation=C:\demo\POProcessing\deploy\sca_POProcessing_rev6.jar
-Doverwrite=true
-Duser=weblogic -DforceDefault=true
-Dconfigplan=C:\demo\POProcessing\cfgplan.xml
ant-sca-deploy.xml undeploy
Undeploys a currently deployed SOA composite application
ant -f ant-sca-deploy.xml undeploy -DserverURL=
-DcompositeName=POProcessing -Drevision=6
-Duser=weblogic -Dpartition=default
ant-sca-mgmt.xml listDeployedComposites
Lists all SOA composite applications deployed to the SOA platform
ant -f ant-sca-mgmt.xml listDeployedComposites -Dhost=myhost -Dport=8001 -Duser=weblogic
Here are the ANT scripts for deploy, undeploy and list deployed composites. There is much more information about these commands and others in the
Oracle® Fusion Middleware Developer's Guide for Oracle SOA Suite 11g Release 1 ( )
How to Manage SOA Composite Applications with ant Scripts
Complete List:
Oracle® Fusion Middleware Developer's Guide for Oracle SOA Suite 11g Release 1 ( )
How to Manage SOA Composite Applications with ant Scripts

20. From Design to Runtime
Deployment
FMW Control Console
Requires the application(s) to be already packaged in a SAR or ZIP file.
Use to Deploy:
A new revision (for example, 2.0) alongside an older revision (for example, 1.0). The last deployed revision becomes the default revision unless otherwise specified.
A SOA bundle (ZIP file) containing revisions of different composites (dependencies are not allowed)
To deploy through the FMW Control Console you must have packaged your application(s). The console doesn’t have this functionality. You can use it to deploy:
A new revision (for example, 2.0) alongside an older revision (for example, 1.0). The last deployed revision becomes the default revision unless otherwise specified.
A SOA bundle (ZIP file) containing revisions of different composites (dependencies are not allowed)

21. From Design to Runtime
Deployment
FMW Control Console
Deployment is available from different places in the console:
SOA Infrastructure Menu > SOA Deployment > Deploy
SOA Folder in the Navigator > Right-click soa-infra > SOA Deployment > Deploy
SOA Infrastructure Home Page > Deployed Composites tab > Deploy
SOA Composite Menu > SOA Deployment > Deploy Another Composite
The console have 4 different places from where you can deploy the applications:
SOA Infrastructure Menu > SOA Deployment > Deploy
SOA Folder in the Navigator > Right-click soa-infra > SOA Deployment > Deploy
SOA Infrastructure Home Page > Deployed Composites tab > Deploy
SOA Composite Menu > SOA Deployment > Deploy Another Composite

22. From Design to Runtime
Deployment
FMW Control Console
Select archive to deploy, single (.jar) or bundle (.zip)
First step in the deployment process is to indicate the name and place of the archive file as well as the configuration plan (if any)

23. From Design to Runtime Select a Target (WLS server or Cluster)
Deployment
FMW Control Console
Select a Target (WLS server or Cluster)
Select a partition (MUST have one)
Select if this is going to be the default revision
Click Deploy (operation cannot be canceled even if you close the browser)
Verify that the composites are up an running (Green Arrow)
You then specify the Target, partition, if this will be the default revision and then deploy. Once the deploy is in progress it can’t be stopped. Check that the composites have the green arrow in the console

24. Program Agenda 1
From Design to Runtime From One to Many Environments Managing Deployed Composites Troubleshooting Additional Resources Q&A 2 3 4 5 6

25. From One to Many Environments
Configuration Plans
Replaces values at the composite level.
Values are replaced during deployment and stored in the SOA schema.
Global Token Variables
Replaces specific URIs in all the composites
Values are replaced at runtime when loading the composites
SOA or higher
SOA offers two features to help you move your applications to more than one target environment minimizing manual changes to your composite(s)
Configuration Plans
Replaces values at the composite level
Values are replaced during deployment in the target environment
Global Token Variables
Replaces specific URIs in all the composites
Values are replaced at runtime when loading the composites

26. From One to Many Environments
Configuration Plans
XML file with environment-specific values, like connection strings, hostnames, ports, etc.
Replaces values in the composite.xml, WSDL, and XSD files during deployment. Does not work on XSLT artifacts.
Attached to the SOA archive file when deploying.
Tools
Jdeveloper : Create Configuration Plan and Validate Configuration Plan.
WLST: sca_generatePlan, sca_attachPlan, sca_validatePlan, sca_extractPlan.
As you move projects from one environment to another (for example, from testing to production), you typically must modify several environment-specific values, such as JDBC connection strings, hostnames of various servers, and so on. Configuration plans enable you to modify these values using a single text (XML) file. The configuration plan is created in either Oracle JDeveloper or with WLST commands. During process deployment, the configuration plan searches the SOA project for values that must be replaced to adapt the project to the next target environment.
The configuration plan does not alter XSLT artifacts in the SOA composite application. To modify any XSL, use the XSLT Mapper. Using a configuration plan is not useful. For example, you cannot change references in XSL using the configuration plan file. Instead, they must be changed manually in the XSLT Mapper in Oracle JDeveloper when moving to and from test, development, and production environments. This ensures that the XSLT Mapper opens without any issues in design time. However, leaving the references unchanged does not impact runtime behavior.

27. From One to Many Environments
Configuration Plans
Properties that can be replaced:
Any composite, service component, reference, and binding properties in the composite.xml file.
Attribute values for bindings (for example, the location for binding.ws)
schemaLocation attribute of an import in a WSDL file.
location attribute of an include in a WSDL file.
schemaLocation attribute of an include, import, and redefine in an XSD file.
Any properties in JCA adapter files.
Policy references for Service and Reference binding components.

28. From One to Many Environments
Configuration Plans
Replaces all references to endpoints and locations in all WSDL, XSD and JCA files   
            <reference name="*">             <binding type="ws">                 <attribute name="location">                     <searchReplace>                         <search>                         <replace> </replace>                     </searchReplace>                 </attribute>             </binding>         </reference>     </composite>
</SOAConfigPlan>
<SOAConfigPlan ….>     <composite name="*">          <reference name="*">             <binding type="ws">                 <property name="endpointURI">                     <searchReplace>                         <search> </search>                         <replace> </replace>                     </searchReplace>                 </property>             </binding>         </reference>       
Here is an example of a very generic configuration plan. Replaces all references to endpoints and locations in all WSDL, XSD and JCA files . Look how the composite name and reference name have the value of “*”

29. From One to Many Environments
Configuration Plans
Advantage
Each composite can have a configuration plan for each environment (Development, Test, QA, Production, etc)
Disadvantage
Changes in an environment will require changing the configuration files of each of the composites deployed to that environment.
Metadata deployed on the runtime server will include environment-specific values.
Advantage
Each composite can have a configuration plan for each your environments (Development, Test, QA, Production, etc)
Disadvantage
Changes in an environment will require changing the configuration files of each of the composites deployed to that environment.
Metadata deployed on the runtime server will include environment-specific values.

30. From One to Many Environments
Global Token Variables
List of key-value pairs. Custom or Predefined (ServerURL and applicationURL)
Replaces specific URIs in all the composites.
Replaces any token in the composite.xml file except those in the import element.
Only for host, port, and protocol at the ws.binding location and any property under the reference tag.
Tokens are defined in the FMW Control console and stored in the
$MIDDLEWARE_HOME/user_projects/domains/<domain_name>/config/fmwconfig/mdm-url-resolver.xml
Replaces specific URIs in all the composites.
List of key-value pairs. Custom or Predefined (ServerURL and applicationURL)
Tokens are defined in the FMW Control console and stored in the
$MIDDLEWARE_HOME/user_projects/domains/<domain_name>/config/fmwconfig/ mdm-url-resolver.xml
Any token in the composite.xml file except those in the import element.
Only for host, port, and protocol at the ws.binding location and any property under the reference tag.

31. From One to Many Environments
Global Token Variables
mdm-url-resolver.xml
Composite.xml
<properties> <entry key="myprotocol">http</entry> <entry key="myhost">mymachine.us.example.com </entry> <entry key="myport">8001</entry> </properties>
<composite...>
<reference name="Service" ui:wsdlLocation="..."> . . .
<binding.ws port="..."
location="${myprotocol}://${myhost}:${myport}/
soa-infra/services/default/mycomposite/
bpelprocess1_client_ep?WSDL" soapVersion="1.1">
</binding.ws>
</reference> . . .
</composite>
When the WSDL definition file is retrieved during runtime, the tokens are replaced by the values in the
mdm-url-resolver.xml configuration file to create the following URI:
bpelprocess1_client_ep?WSDL
bpelprocess1_client_ep?WSDL

32. From One to Many Environments
Global Token Variables
Advantages:
No need to change multiple configuration plans.
Metadata deployed on the runtime server will not include environment-specific values.
In a clustered environment, global token variable changes are made on the administration server and propagated to all managed servers.
If multiple SOA composite applications invoke different services hosted on a specific server, you can use a single global token variable to reference this server across the composites. For example, instead of updating the host name of the server in ten different configuration plans, you set the name globally with global token variables. The value is retrieved and replaces the value of the global token variable for the host name in the binding.ws element of the composite.xml file of the deployed SOA composite application.

33. Program Agenda 1
From Design to Runtime From One to Many Environments Managing Deployed Composites Troubleshooting Additional Resources Q&A 2 3 4 5 6

34. Managing Deployed Composites
Redeploy
Undeploy
There are many operations that can be used to managed deployed instances. Today we will focus on only Redeploy and Undeploy. For more information refer to
Oracle® Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite 11g Release 1 ( )
7.5 Managing the State of Deployed SOA Composite Applications
More Information:
Oracle® Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite 11g Release 1 ( )
7.5 Managing the State of Deployed SOA Composite Applications

35. Managing Deployed Composites
Redeploy
Use to overwrite any existing composites with the same revision ID.
Rules:
If the deployed revision has running instances, the state of those instances will change to Stale /Aborted. You can still access audit and flow trace details.
Instances are automatically migrated. If the migration is successful, your SOA composite application is redeployed. If BPEL, Mediator, Human Workflow or Decision Services have problems then redeployment of the entire composite will fail.
Cannot redeploy multiple SOA composite applications.
Redeploy can be used to overwrite any existing composites with the same revision ID. There are many rules
If the deployed revision has running instances, the state of those instances will change to Stale /Aborted. You can still access audit and flow trace details.
Instances are automatically migrated. If the migration is successful, your SOA composite application is redeployed. If BPEL, Mediator, Human Workflow or Decision Services have problems then redeployment of the entire composite will fail.
Cannot redeploy multiple SOA composite applications.
Instances are automatically migrated. If the migration is successful, your SOA composite application is redeployed. However, if some of the following component instances cannot be migrated, redeployment of the entire composite fails.
BPEL instances: This capability is not supported if the composite includes a BPEL process service component that has changed from the previous revision.
Oracle Mediator: Checks the new component definition for compatibility. If it is incompatible with the existing component definition, the redeployment of the composite revision fails. However, if at the time of redeployment all Oracle Mediator processes within the running instances of this composite have completed, the definition change has no impact and redeployment is successful. If you want to redeploy the same version of a SOA composite application, you cannot change the composite name. You can deploy with the same revision number if you selected the Overwrite any existing composites with the same revision ID checkbox on the Deploy Configuration page.
Decision service: If the component definition has changed and is incompatible with the existing component definition, this may cause the redeployment of the composite revision to fail. However, if at the time of redeployment all decision service processes within the running instances of this composite have completed, the definition change has no impact and redeployment is successful. Because decision service instances take a short time to complete, their migration does not pose a high risk of redeployment failure.
Human workflow: Changes in human workflow do not impact any existing user task that has been created. Newly created human tasks after redeployment can use a new routing slip.

36. Managing Deployed Composites
Redeploy
In Production do not overwrite existing versions of an application.
Instead deploy a new version and set as default.

37. Managing Deployed Composites
Undeploy
Removes a revision of the composite.
Rules:
Cannot configure and monitor the revision after the composite is undeployed.
The state of running instances is changed to Stale/Aborted . No new messages are processed.
Cannot view previously completed instances.
Undeploying default revision -> next active revision becomes new default.
Undeploying default revision with no active revision -> retired revision becomes new default.
Need to reactivate to process new messages.
Can undeploy multiple SOA composites located in the same partition.
Removes a revision of the composite.
Rules:
Cannot configure and monitor the revision after the composite is undeployed.
The state of running instances is changed to Stale/Aborted . No new messages are processed.
Cannot view previously completed instances.
Undeploying default revision -> next active revision becomes new default.
Undeploying default revision with no active revision -> retired revision becomes new default.
Need to reactivate to process new messages.
Can undeploy multiple SOA composites located in the same partition.

38. Managing Deployed Composites
Redeploy & Undeploy State Transition Rules
Determines when instances (BPEL, Mediator, HWF, etc), faults, and rejected messages states are changed to Stale during redeployment or undeployment.
Many different scenarios. Details in the SOA Admin Guide.

39. Program Agenda 1
From Design to Runtime From One to Many Environments Managing Deployed Composites Troubleshooting Additional Resources Q&A 2 3 4 5 6

40. Troubleshooting Set following loggers to TRACE 32 in FMW Console:
Debug and Log Files
Set following loggers to TRACE 32 in FMW Console:
Oracle.soa.bpel.deployment
Oracle.soa.bpel.compiler
oracle.integration.platform.blocks.deploy
Check for error messages in:
DOMAIN_HOME/servers/<server-name>/logs/<server-name>.log
DOMAIN_HOME/servers/<server-name>/logs/<server-name>-diagnostic.log
The first thing to do is to set the loggers related to deployment to TRACE 32 in the FMW Console. Then you can reproduce and look at the server and diagnostic log files.

41. Troubleshooting
Error Codes
SOA Unable to find a WSDL that has a definition for service xxx
SOA Unable to register service xxx .. Error in getting XML input stream
The composite xxx is not available
java.lang.RuntimeException: java.lang.Exception: BPEL 1.1 compilation failed
javax.net.ssl.SSLKeyException: FATAL Alert:BAD_
Here is a list of some errors you can look for related to deployment issues. The most common issues are related to shared data, especially WSDLs. Authentication/Security issues, compilation and of course coherence misconfiguration.

42. Troubleshooting
Solutions – My Oracle Support (
You need to search in My Oracle Support for the errors that you are seeing. There are many many article that we have wrote with solutions or HOW TOs . These is the same Knowledge base that our support engineers use to solve Service Requests.
Here is a screenshot with articles related it deployment.

43. Troubleshooting Solutions – My Oracle Support
Here is a screenshot with articles related it undeployment

44. Troubleshooting Problem Cause Solution
Configuration plan is not taking effect during deployment
Cause
Selected the wrong configuration plan
Solution
Open SAR file and ensure it contains the soaconfigplan.xml file. This file is generated during deployment based on the configuration plan you selected.
Deploy again and ensure you select the configuration plan in the Deploy Configuration page of the Deployment Wizard.
Here is a problem that you may face with possible cause and solution.

45. Troubleshooting Problem Cause Solutions
Deployment cannot continue! No SOA Configured target servers found
Cause
You started the Managed server without starting an Admin server
Admin server is in WARNING state
In JDeveloper, you deployed to the Admin Server and not the Managed Server.
Solutions
Start the Admin Server
Use WLST to deploy to a Managed Server without starting an Admin Server.
Here is a problem that you may face with possible cause and solution.

46. Troubleshooting Problem Cause Solution
oracle.fabric.common.FabricException: Timed out waiting for operation to complete… CompositeDeploymentCoordinatorMessages.throwTimedOutWaiting
Cause
Coherence configuration is not correct. You maybe missing one or more of these parameters : tangosol.coherence.wka, tangosol.coherence.localhost, tangosol.coherence.localport)
Solution
OracleFusion Middleware Enterprise Deployment Guide for Oracle SOA Suite 11g Release 1 ( )
9.4 Configuring Oracle Coherence for Deploying Composites
Although deploying composites uses multicast communication by default, Oracle recommends using unicast communication in SOA enterprise deployments. Use unicast if you disable multicast communication for security reasons.
Unicast communication does not enable nodes to discover other cluster members in this way. Consequently, you must specify the nodes that belong to the cluster. You do not need to specify all of the nodes of a cluster, however. You need only specify enough nodes so that a new node added to the cluster can discover one of the existing nodes. As a result, when a new node has joined the cluster, it is able to discover all of the other nodes in the cluster. Additionally, in configurations such as SOA enterprise deployments where multiple IPs are available in the same system, you must configure Oracle Coherence to use a specific host name to create the Oracle Coherence cluster.
Note:
An incorrect configuration of the Oracle Coherence framework used for deployment may prevent the SOA system from starting. The deployment framework must be properly customized for the network environment on which the SOA system runs. Oracle recommends the configuration described in this section.

47. Program Agenda 1
From Design to Runtime From One to Many Environments Managing Deployed Composites Troubleshooting Additional Resources Q&A 2 3 4 5 6

48. Additional Resources
Oracle® Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite 11g Release 1 ( )
Oracle® Fusion Middleware Developer's Guide for Oracle SOA Suite 11g Release 1 ( )
Deploying a SOA Composite Application Video (OLL YouTube Channel)
Follow us on or SOA Proactive Blog

49. Q&A