3 Configuring the SOA Infrastructure

1. Access this page through one of the following options:

   From the SOA Infrastructure Menu...	From the SOA Folder in the Navigator...	From the SOA Composite Menu...
   Select SOA Administration > Common Properties.	Right-click soa-infra. Select SOA Administration > Common Properties.	Select SOA Infrastructure Common Properties.

   The SOA Infrastructure Common Properties page is displayed.

   Note:

   • Some property fields are designated with an icon showing green and red arrows. If you change these properties (for example, Server URL), you must restart the SOA Infrastructure.

   • If you exit this page without clicking Apply, the changes are not saved.

   • If you make changes and want to reset these properties to their previous values, click Revert.

   
   Description of the illustration GUID-65E9059C-F167-4B3D-B356-9CDB3ACFE842-default.gif

The properties of the SOA Infrastructure Common Properties page are described in the following sections:

• Configuring and Oracle BPM Suite Profiles

• Configuring the Audit Trail_ Payload Validation_ and Default Query Duration

• Configuring UDDI Registry Properties

• Configuring Callback Server and Server URLs

• Configuring Analytics and Sensors

• Configuring Data Sources and Web Service Binding Properties

• Configuring SOA Infrastructure Advanced Configuration Properties

1. Click Change Profile.
2. Select the desired profile, and click OK.

   Profile Type	Profile Description	Adapter Set Provided
   BPM Classic	Contains the Oracle SOA Suite and Oracle BPM Suite functionality enabled in Release 11g (BPEL, BPMN, case management, Oracle Mediator, Oracle B2B, human workflow, and business rules). When you upgrade from Release 11g to 12c, this is the default profile.	The full set of adapters is included (file, FTP, database, JMS, MQSeries, AQ, E-Business Suite, User Messaging Service, socket, LDAP, Coherence, MSMQ, and JDE).
   SOA Foundation	Contains SOA Foundation functionality (BPEL, human workflow, Oracle Mediator, and business rules).	The limited set of adapters is included (file, FTP, database, JMS, MQSeries, AQ, E-Business Suite, and User Messaging Service).
   SOA Foundation With B2B	Contains SOA Foundation and the Oracle B2B functionality (BPEL, human workflow, Oracle Mediator, business rules, and Oracle B2B).	The full set of adapters.
   SOA Foundation With Healthcare	Contains SOA Foundation and the Oracle B2B functionality (BPEL, human workflow, Oracle Mediator, business rules, and Oracle B2B).	The full set of adapters.
   BPM Enterprise	Contains standard Oracle SOA Suite and Oracle BPM Suite functionality (BPEL, BPMN, case management, human workflow, Oracle Mediator, and business rules).	The full set of adapters.
   Orchestration	Contains BPEL and human workflow functionality.	The limited set of adapters.
   BPM Basic	Contains the standard Oracle SOA Suite platform, Oracle B2B, and Oracle BPM technologies (BPEL, BPMN, case management, human workflow, business rules, and Oracle B2B).	The limited set of adapters.
   SOA Classic	Contains the Oracle SOA Suite functionality enabled in Release 11g (BPEL, BPMN, case management, Oracle Mediator, Oracle B2B, human workflow, and business rules). When you upgrade from Release 11g to 12c, this is the default profile.	The full set of adapters.
   BPEL Only	Contains the BPEL service component. This is the minimal profile that only supports BPEL.	The limited set of adapters.
   SOA Foundation Enterprise	Contains the SOA Foundation functionality (BPEL, human workflow, Oracle Mediator, and business rules).	The full set of adapters.

3. Click Apply.

   Until you click Apply, you can click Revert to revert the profile change. In addition, no changes are made if you select different profiles (for example, to view their descriptions) and click Cancel in this dialog.

4. Restart Oracle WebLogic Server immediately.

   Any server that includes a SOA Infrastructure deployment must be restarted:

   • If the SOA Infrastructure is deployed on the administration server, then it must be restarted.

   • If the SOA Infrastructure is deployed on a managed server or a cluster of managed servers, then these servers must all be restarted.

1. Make changes appropriate to your environment.

   Element	Description
   Audit Level	Select the level of information to be collected by the message tracking infrastructure. This information is collected in the instance data store (database) associated with the SOA Infrastructure. This setting has no impact on what gets written to log files. Off: No business flow instance tracking and payload tracking information is collected. Drilling down into a flow shows the components and their status. Using this setting limits database growth, and also helps reduce latency and improve throughput. Production: Flow and audit event information is collected and stored in the database. Drilling down into a flow provides the flow trace. The flow trace shows the exact sequence of component interaction, and also shows component statuses. Drilling down into a BPEL instance shows the execution of BPEL activities, and their statuses. As the flow-trace audit trail may not be required for all composites, you may want to set the audit level to Off at the SOA Infrastructure level, and set the audit level to Production for the required composites Development: This option collects payload details in addition to flow and audit events. This setting is not recommended for a production environment, as it will impact performance and result in rapid database growth. This level is useful largely for testing and debugging purposes only. For more information about reducing the audit level for SOA composite applications and the data written to the Oracle SOA Suite schema, see Reducing Audit Levels.
   Payload Validation	Select to enable validation of incoming and outgoing messages. Nonschema-compliant payload data is intercepted and displayed as a fault. By default, this checkbox is not selected.
   Default Query Duration	Specify the time period for retrieved instances and fault data, or accept the default value of 24 hours. This property controls the amount of instance and fault data fetched by default by all out-of-the-box queries. This value is also displayed as the default time range value on pages with query/search functionality (for example, the Dashboard page regions that include query functionality, the Flow Instances pages, Error Hospital pages, the Resequencer pages, and so on). You can override this value on the corresponding page, as needed. Note: It is highly recommended that you set a time period duration because it has a significant impact on the performance of multiple Oracle Enterprise Manager Fusion Middleware Control pages and queries.

2. Click Apply.
3. If you make changes and want to reset these properties to their previous values, click Revert.

1. Make changes appropriate to your environment.

   Element	Description	Example
   Inquiry URL	Enter the URL of the master registry you want to query. The URL must not refer to the slave registry itself. Otherwise, you can lose some data. The inquiry URL obtains full-standard UDDI version 3 structures. This is the same UDDI inquiry URL that you specified in the Create UDDI Registry Connection wizard.	http://master.mycompany.com:8888/registry/uddi/inquiry
   User	Enter the registry inquiry user.	admin
   Password	Enter the password for the master registry inquiry user.	Enter a password that uses good security practices.

   For information about setting the endpoint reference and service key, see Changing the Endpoint Reference and Service Key for Oracle Service Registry Integration.

2. Click Apply.
3. If you make changes and want to reset these properties to their previous values, click Revert.

1. Make changes appropriate to your environment.

   Element	Description
   Callback Server URL	Enter the callback server URL. This setting applies to all SOA composite application service or reference callbacks. This setting typically takes the format of http://host:port and is used to construct the SOAP service URL (for example, http://host:port/endpoint-context-uri for a service callee to asynchronously send back responses to the caller).
   Server URL	Enter the server URL. This URL is published as part of the SOAP address of a service in the concrete WSDL file. Note: SOAP optimization is automatically configured. Therefore, if you upgrade to Release 12c and are using the optimized shortcut approach in existing applications, optimized calls are activated only when the hostname value (as referred to in the WSDL URL in the composite.xml file) matches the Server URL value. Either set both values to the hostname (for example, myhost) or to the full domain name (for example, myhost.domain.com). If these values do not match, a regular SOAP call is performed instead of an optimized local call. For information about local optimization, see Configuring Local Optimization.

   Note:

   If you change the Callback Server URL and Server URL values (for example, when moving from a test to a production environment), you must restart Oracle WebLogic Server for the WSDLs to be regenerated.

2. Click Apply.
3. If you make changes and want to reset these properties to their previous values, click Revert.

1. Make changes appropriate to your environment.

   Element	Description
   Analytics	Use to manage the collection of analytics in SOA composite applications. When enabled, analytics enable you to perform the following tasks: Measure a business indicator at a certain point in the process or in a section of the process. Capture BPEL process metrics that are sent to Oracle BAM Server, and then used for analysis and graphic display.
   BPEL Sensors	Use to manage the collection of BPEL sensor details in SOA composite applications. When enabled, BPEL sensors collect data for any fault, activity, and variable sensors defined in the composite.
   Composite Sensors	Use to manage the collection of composite sensor details in SOA composite applications. When enabled, composite sensors perform the following tasks: Monitor incoming and outgoing messages. Specify composite sensor details in the search utility of the Flow Instances page of a SOA composite application in Oracle Enterprise Manager Fusion Middleware Control. This action enables you to locate a particular instance. Publish JMS data computed from incoming and outgoing messages.

2. Click Apply.
3. If you make changes and want to reset these properties to their previous values, click Revert.

1. Expand the Advanced section.

   The Data Sources section displays the following properties.

   
   Description of the illustration GUID-CA910A15-214A-4497-AA3F-90319869025D-default.png
2. Make changes appropriate to your environment.

   Element	Description	Example
   Server Data Source JNDI	Displays the JNDI location for the server data source. Click Configure to go to the data source configuration page of the Oracle WebLogic Server Administration Console. Global transaction support should be disabled for this data source.	jdbc/SOALocalTxDataSource
   Server Transaction Data Source JNDI	Displays the JNDI location for the server transactional data source. Click Configure to go to the data source configuration page of the Oracle WebLogic Server Administration Console. You must configure the data source for global transactions.	jdbc/SOADataSource
   Nonfatal Connection Retry Count	Enter the maximum number of times a nonfatal connection error can be retried before failing. These type of errors occur for any connection error with the dehydration store (for example, Oracle Real Application Clusters failover, database shutdown, and so on).	10

   The Web Service Binding Properties section displays the following options.

3. Make changes appropriate to your environment.

   Element	Description	Example
   Oracle SSL Ciphers	Enter the list of supported Oracle ciphers. A cipher suite is a set of algorithms that provide security for data transmissions. Before data can flow through an SSL connection, both sides of the connection must negotiate common algorithms to use.	SSL_RSA_WITH_RC4_128_MD5
   Oracle Wallet Password	Enter the wallet password for the keystore.	Enter a password that uses good security practices.
   Use Chunking	Select to enable chunking of data for SOAP over HTTP deliveries.	- -
   Chunk Size	Specify a chunk size. The value must be less than or equal to 999. The size is used for SOAP over HTTP deliveries and is specified in bytes.	500

4. Click Apply.
5. If you make changes and want to reset these properties to their previous values, click Revert.

SOA composite application states are not updated to indicate that they are down after SOA Infrastructure shutdown. If you attempt to access the composite, you receive an error message stating that composite details cannot be retrieved:

soa-infra runtime connection error  An error happened while connecting to
soa-infra runtime at  t3://address:8001/soa-infra.

This message may lead you to believe that another issue exists in the system. However, this is not the case.

These composite states display as up or, in some cases, pending because this metric indicates whether the composite is enabled, and is independent of whether the SOA Infrastructure is started. In addition, the composite is still active and can receive requests on other managed servers in a cluster.

If a SOA composite application with adapter endpoints is in a retired state, the endpoints are not activated if you perform the following actions:

• Restart the SOA Infrastructure

• Activate the SOA composite application

This is because files, records, and so on are not picked up by the endpoint adapters. As a workaround, redeploy the SOA composite application after restarting the SOA Infrastructure.

Caused By: java.security.UnrecoverableKeyException: Password verification 
failed 
        at 
sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:769) 
        at 
sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:38) 
        at java.security.KeyStore.load(KeyStore.java:1185) 
        at oracle.j2ee.ws.saaj.util.SSLUtil.loadKeyStore(SSLUtil.java:73) 
        at 
oracle.j2ee.ws.saaj.util.SSLUtil.getKeyManagerFactory(SSLUtil.java:88) 
        at oracle.j2ee.ws.saaj.util.SSLUtil.getKeyManagers(SSLUtil.java:97) 
        at 
oracle.j2ee.ws.saaj.util.SSLUtil.createSSLSocketFactory(SSLUtil.java:50) 
        at 
oracle.integration.platform.common.SSLSocketFactoryManagerImpl.getSSLSocketFac 
tory(SSLSocketFactoryManagerImpl.java:58) 
        at oracle.fabric.common.wsdl.WSDLManager.init(WSDLManager.java:356) 
        at oracle.fabric.common.wsdl.WSDLManager.<init>(WSDLManager.java:101) 
        at 
oracle.fabric.common.metadata.MetadataManagerImpl.getWSDLManager(MetadataManag 
erImpl.java:283) 
        at 
oracle.fabric.composite.model.CompositeModel.getWSDLManager(CompositeM 

1. Perform one of the following actions:

   • Delete the SOA map in cwallet.sso.

   • Remove $DOMAIN_HOME/config/fmwconfig/default-keystore.jks. Oracle Web Services Manager (OWSM) uses this file.

2. Restart the SOA Infrastructure.

1. Log in to Oracle WebLogic Server Administration Console.

2. In the Domain Structure, select Services > Data Sources.

3. At the top of the page, click Connection Pool.

4. In the Name column, select SOADataSource.

5. In the Maximum Capacity field, update the value (for example, to 300 to accommodate loads with 200 threads). The default value is 50.

6. Click Save.

1. Access this page through one of the following options:

   From the SOA Infrastructure Menu...	From the SOA Folder in the Navigator...	From the SOA Composite Menu...
   Select SOA Administration > Common Properties.	Right-click soa-infra. Select SOA Administration > Common Properties.	Select SOA Infrastructure Common Properties.

2. Click More SOA Infra Advanced Configuration Properties.

3. Expand SOAMaxThreadsConfig.

4. Make changes appropriate to your environment.

   
   Description of the illustration GUID-94C386E9-64AC-40A0-B6B4-C0235830C98C-default.png

   For example, make the following changes to accommodate these thread values:

   • incomingRequestsPercentage: 20 (to accommodate 10 threads)

   • internalBufferPercentage: 50 (to accommodate 25 threads)

   • internalProcessingPercentage: 30 (to accommodate 15 threads)

5. Click Apply.

6. If you make changes and want to reset these properties to their previous values, click Revert.

Oracle SOA Suite performs the following condition checks to determine if local optimization is possible.

• It must be a composite-to-composite invocation. This is the most fundamental criteria that makes direct Java calls possible when both the client and target services are implemented based on the same SOA Infrastructure (that is, the same SOA server).

• The composite implementing the reference (target) service must be active. This condition requires the target composite to be up and running, which in turn ensures that the reference service is available.

  Note:

  The state of the target composite must be on and active. A stopped or retired state is not eligible for local optimization.

• The client and target composites must be co-located on the same server. This is an obvious requirement for direct Java invocations. It is also a critical step in which Oracle SOA Suite compares the server (on which the client composite is deployed) host configuration with the host and port values specified in the reference (target) service endpoint URI. If the host and port values match, it can be concluded that the client and target composites are located on the same server. However, the comparison is not necessarily straightforward given that working with both standalone and clustered server setups and potential load balancer configurations is necessary. Therefore, here are the step-by-step condition checks that determine the correct server configuration on all platforms:

  • Checks the Server URL configuration property value on the SOA Infrastructure Common Properties page, as described in Configuring SOA Infrastructure Properties.

  • If not specified, checks the FrontendHost and FrontendHTTPPort (or FrontendHTTPSPort, if SSL is enabled) configuration property values from the cluster MBeans.

  • If not specified, checks the FrontendHost and FrontendHTTPPort (or FrontendHTTPSPort, if SSL is enabled) configuration property values from the Oracle WebLogic Server MBeans.

  • If not specified, uses the DNS-resolved Inet address of localhost.

  • Checks if the port value specified in the reference service endpoint URL matches the configured server port value. If no port value is specified in the endpoint URL, Oracle SOA Suite assumes 80 for HTTP and 443 for HTTPS URLs.

  • If the port values match, the server URL (that is, http(s)://host:port, where host and port are obtained from the checks mentioned above) is then compared to the server URL in the reference endpoint address. The URLs are resolved to canonical values and the comparison also takes into account the cases in which the endpoint URL host is localhost or 127.0.0.1.

  • Oracle SOA Suite concludes that the composites are co-located if the server URL comparison returns a value of true.

• The security policy configurations, if applied on either or both the client and server composites, must allow for local optimization. For information about policy configurations and local optimization, see Policy Attachments and Local Optimization in Composite-to-Composite Invocations.

You can confirm if a call went over local optimization in the Trace section of the Flow Trace page. The (Local Invocation) text for the reference and service of the invoking and invoked composites is displayed, as shown in Figure 3-1.

Figure 3-1 Local Optimization Details in the Trace Section of the Flow Trace Page

Description of "Figure 3-1 Local Optimization Details in the Trace Section of the Flow Trace Page"

For more information about the Flow Trace page, see Monitoring the Flow Trace of a Business Flow Instance.

Two configuration properties are provided for either overriding or forcing local optimization.

• oracle.webservices.local.optimization

  By default, Oracle SOA Suite prefers local optimization. However, you can override this behavior with the oracle.webservices.local.optimization binding property in the composite.xml file. When this property is set to false, local optimization is not performed and cross-composite calls are performed through SOAP and HTTP. Use this property where appropriate. For information about setting this property, see Policy Attachments and Local Optimization in Composite-to-Composite Invocations.

• oracle.soa.local.optimization.force

  You can override the oracle.webservices.local.optimization property and force optimization to be performed by setting the oracle.soa.local.optimization.force property to true. Use this property in the following scenarios:

  • The server configuration is sufficiently complicated (for example, there are fire wall or proxy settings in an intranet), which may cause the co-location checks described in Condition Checks for Using Local Optimization to not deliver the correct result.

  • You clearly understand the semantics of local optimization, the system setup qualifies for local optimization, and local optimization is absolutely preferred.

  There can be other scenarios for forcing optimization that are not described in this section.

The oracle.soa.local.optimization.force property has a default value of false. When this property is set to true, Oracle SOA Suite skips the condition checks described in Condition Checks for Using Local Optimization, except for policy configuration checking, which is necessary to ensure and enforce the integrity of service invocations.

Another important note about this property is that Oracle SOA Suite always honors the setting of this property (if policy checks allow the optimization). However, if local invocation fails due to nonapplication faults or exceptions (that is, runtime errors mostly related to the direct Java invocation), the value of this setting is ignored for subsequent invocations on the configured endpoint and for all the valid endpoint addresses configured on the endpoint.

To enable the oracle.soa.local.optimization.force property:

Add oracle.soa.local.optimization.force as a binding component level property in the reference section of the composite being invoked. For example, if composite comp_comp2 invokes comp_comp1, then define this property in the reference section of the composite.xml file of comp_comp2.

<reference name="Service1"
ui:wsdlLocation="http://localhost:8001/soa-infra/services/default/comp_
comp1!1.0/BPELProcess1.wsdl">
<interface.wsdl interface="http://xmlns.oracle.com/comp_comp/comp_
comp1/BPELProcess1#wsdl.interface(BPELProcess1)"  
                              callbackInterface="http://xmlns.oracle.com/comp_
comp/comp_comp1/BPELProcess1#wsdl.interface(BPELProcess1Callback)"/>
<binding.ws port="http://xmlns.oracle.com/comp_comp/comp_
comp1/BPELProcess1#wsdl.endpoint(bpelprocess1_client_ep/BPELProcess1_pt)"
location="http://localhost:8001/soa-infra/services/default/comp_
comp1!1.0/bpelprocess1_client_ep?WSDL">
<property name="oracle.webservices.local.optimization">false</property>
<property name="oracle.soa.local.optimization.force">true</property>
</binding.ws>

To force local optimization on the reference service callback:

Add the oracle.soa.local.optimization.force property to the <callback> element in the <service> definition of the corresponding reference service.

For example, if composite1 invokes composite2, add oracle.soa.local.optimization.force property in the <service> definition of compsite2 as follows. This forces the asynchronous callback from composite2 to composite1 to be optimized locally:

<service ui:wsdlLocation="composite2.wsdl">
. . .
<callback>
<binding.ws
port="http://xmlns.oracle.com/example#wsdl.endpoint(FooService/FooPort)">
<property
name="oracle.soa.local.optimization.force">true</property>
</binding.ws>
</callback>
</service>

For information about optimization and WS-AtomicTransaction (WS-AT) transactions, see Section "WS-AT Transactions are Not Supported When Optimization is Enabled" of Developing SOA Applications with Oracle SOA Suite.

Oracle SOA Suite provides NOTIFICATION:1(INFO) level logging for every critical decision made for local optimization versus SOAP processing. For more details or debugging information, set the oracle.integration.platform.blocks.local and oracle.integration.platform.blocks.soap loggers at the TRACE:1(FINE) level in Oracle Enterprise Manager Fusion Middleware Control.

This local optimization calls use case describes the following:

• How local optimization calls work in an environment in which composite A calls a co-located composite B on the same server, and composite B is unreachable (Table 3-1).

• What happens when you create a load balancer address with a port value that is not the port on which the Oracle WebLogic Servers are listening (Table 3-2).

The token names and the replacement values that you specified in the Token Configurations page are added to the system's mdm-url-resolver.xml file in the following directory:

$MIDDLEWARE_HOME/user_projects/domains/domain_name/config/fmwconfig/
mdm-url-resolver.xml

For example, assume four global token variable names and values are defined through the Token Configurations page.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">
<properties>
   <comment>
      URL Resolver file used by the Metadata manager to resolve $<variable> in
      URLs
    </comment>
    <entry key="myprotocol">http</entry>
    <entry key="myhost">mymachine.us.example.com</entry>
    <entry key="myport">8001</entry>
</properties> 

When the composite.xml for the deployed SOA composite application is loaded during runtime and the resources indicated by URIs within the file are retrieved, any values of global token variables within the URIs are replaced with the values specified in the Token Configurations page.

For example, the following composite.xml file specifies a URI using these tokens in the binding.ws element:

<?xml version="1.0" encoding="UTF-8"?> 
<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:

http://mymachine.us.example.com:8001/soa-infra/services/default/myComposite/
 bpelprocess1_client_ep?WSDL

1. In the Server URL field of the SOA Infrastructure Common Properties page, enter a value (for example, my.host.com:8080). A restart of the server is required when changing this property. Figure 3-2 provides details.

   Figure 3-2 Server URL Field of the SOA Infrastructure Common Properties Page

   
   Description of "Figure 3-2 Server URL Field of the SOA Infrastructure Common Properties Page"
2. Enter the serverURL token in the composite.xml file.

   http://${serverURL}/somePath/someReource.xml
   

   This results in the following URI after the token is replaced during deployment:

   http://my.host.com:8080/somePath/someResource.xml
   

Use the Resiliency Configuration page to enable or disable resiliency, and to specify global resiliency settings.

1. Under the SOA Infrastructure menu, select SOA Administration > Resiliency Configuration.
   The Resiliency Configuration page appears.Figure 3-3 shows the Resiliency Configuration page.

   Figure 3-3 Resiliency Configuration Page

   
2. Select the Enabled check box to enable resiliency.
   When you enable resiliency, downstream endpoints are monitored for errors, and when these errors exceed the specified threshold, upstream endpoints are automatically suspended.
   The other resiliency configuration parameters, like Failure Rate and Retry Interval, are now enabled.
3. Specify a Failure Rate: Enter the number of errors and the duration in minutes.
   For example, if you specify 10 errors in 5 minutes, then a downstream endpoint failing 10 times in a span of 5 minutes triggers the resiliency feature.
4. Specify a Retry Interval in minutes.
   • If you select Disable Auto Retry, then automatic retries are disabled. You would need to resume the upstream endpoint manually.
   Any suspended upstream endpoint is temporarily re-enabled after every Retry Interval to check if the downstream endpoint is back up. So, if you specify a Retry Interval of 10 minutes, then a suspended upstream endpoint is re-enabled every 10 minutes to check if the downstream endpoint is back up. If the downstream endpoint is still down, then the upstream endpoint is suspended again.

5. Note:

   This step is optional.
   Click Add Notification to configure SMS, e-mail, and IM (instant messaging) notifications for the administrator.
   You can notify the administrator when an upstream endpoint is suspended, or when an endpoint comes back up.
   1. Under Send Notification To, enter the subscriber ID for the administrator.
      The subscriber ID can be an email address, phone number, or IM identifier, depending on the chosen communication channel.
   2. Under Via, select the communication channel.
      You can click Add Notification, identified by the plus sign (+), to add another notification channel.

      You can also click Delete Notification, identified by the red X, to remove an existing notification channel.

6. Note:

   This step is optional.
   Click More Resiliency Configuration Properties to configure additional resiliency properties. See Global Resiliency Properties and Endpoint Resiliency Propertiesfor details on the properties that can be configured.
7. Click Apply on the Resiliency Configuration page to save your changes.
   • If you click Revert, then all changes made to this page are reverted.

You can tweak the resiliency settings for a downstream endpoint, and these settings will override the global Resiliency settings for that endpoint.

1. From the SOA Composite page for the composite containing the endpoint, click the endpoint name under Services and References.
   For example, if you are tweaking resiliency settings for a file adapter, click the name of the file adapter under Services and References.
   The dashboard for the endpoint appears.
2. Click Properties to switch to the Properties tab.
   A list of properties appears for the component.
3. If you cannot see the Resiliency properties, click the Add button identified by the plus (+) sign.
   See Global Resiliency Properties and Endpoint Resiliency Properties for the list of available Resiliency properties.
4. Modify the values for the properties that you wish to change.

You can modify the ResiliencyConfig MBean attribute in the System MBean Browser to globally set advanced configuration properties for Resiliency. You can also modify the properties for a Reference endpoint to override the global Resiliency settings for the endpoint.