33 Managing Business Events

This chapter describes how to manage business events and the Event Delivery Network (EDN), including mapping the flow of different business events through different JMS destinations, testing the publishing of business events, viewing the event definition language (EDL) file of the business event, viewing service components subscribed to business events, changing the JMS type, and configuring the inbound poller thread number. Business events consist of message data sent as the result of an occurrence in a business environment. When a business event is published, other service components can subscribe to it.

This chapter includes the following topics:

For information about troubleshooting business event issues, see Business Events and Event Delivery Network Troubleshooting.

For information about creating business events in Oracle JDeveloper, see Using Business Events and the Event Delivery Network in Developing SOA Applications with Oracle SOA Suite.

33.1 Introduction to the Event Delivery Network and JMS Provider Types

You create business events in Oracle JDeveloper and include them in SOA composite applications that you deploy to Oracle Enterprise Manager Fusion Middleware Control. Service components can subscribe to business events. When a business event is published, the entity subscribed to that event receives it.

EDN is the subsystem of Oracle SOA Suite that accepts published business events and delivers them to the subscribers. EDN uses a JMS topic as a back-end store. EDN provides two JMS-based types:

  • Oracle WebLogic Server JMS

    EDN uses a default Oracle WebLogic Server JMS topic as the underlying JMS store for all event types. Figure 33-1 provides details.

    Figure 33-1 JMS Topic of Oracle WebLogic Server JMS

    Description of Figure 33-1 follows
    Description of "Figure 33-1 JMS Topic of Oracle WebLogic Server JMS"

    The following JMS adapter connection factories are supported:

    • eis/wls/EDNxaDurableTopic (supports XA, durable topic with ClientID=edn_wljms_xa_client)

    • eis/wls/EDNxaTopic (supports XA)

    • eis/wls/EDNLocalTxDurableTopic (supports local transaction, durable topic with ClientID=edn_wljms_localtx_client)

    • eis/wls/EDNLocalTxTopic (supports a local transaction)

    You can change the default JMS type. For information, see Changing the JMS Type. You can also create custom JMS topics and specify certain event types of interest to map to the custom topics.

  • Oracle Advanced Queueing (AQ) JMS

    AQ JMS topics can also be created and used. EDN provides a preprovisioned AQ JMS topic out of the box. Figure 33-2 provides details.

    Figure 33-2 JMS Topic of Oracle AQ JMS

    Description of Figure 33-2 follows
    Description of "Figure 33-2 JMS Topic of Oracle AQ JMS"

AQ JMS is exposed through a foreign server.

The following JMS adapter connection factories are supported:

  • eis/aqjms/EDNxaDurableTopic (supports XA, durable topic with ClientID=edn_aqjms_xa_client)

  • eis/aqjms/EDNxaTopic (supports XA)

  • eis/aqjms/EDNLocalTxDurableTopic (supports local transaction, durable topic with ClientID=edn_aqjms_localtx_client)

  • eis/aqjms/EDNLocalTxTopic (supports a local transaction)

The following JDBC data sources are supported:

  • jdbc/EDNDataSource (supports XA)

  • jdbc/EDNLocalTxDataSource (supports local transaction)

The following foreign servers are supported:

  • EDNAQjmsForeignServer (supports XA)

  • EDNAQjmsLocalTxForeignServer (supports local transaction)

Table 33-1 describes the benefits of both JMS provider types.

Table 33-1 Comparison Between JMS Provider Types

Oracle WebLogic Server JMS AQ JMS
  • A file-based (file store) and file cached database backed (JDBC store) implementation.

  • When you have an application that runs in the same process space as the JMS server, it is always faster than AQ JMS. This is because AQ JMS always requires database round trips.

  • Does not provide SQL visibility of messages, so there is no language conversion cost.

  • In most low to medium scale and some high end (concurrency, throughput) JMS use cases, Oracle WebLogic Server JMS outperforms AQ JMS. This is because you usually compare different qualities of services when looking beyond what is expected from standard JMS (for example, crash recoverability, SQL visibility, full ordering, and disaster recovery).

  • Usually wins on a price and performance basis for most cases if you evaluate total cost.

  • Oracle database access is inherently multithreaded through the use of multiple database connections (whereas Oracle WebLogic Server JMS storage is single threaded). If you have enough database connections to spare, AQ JMS does well at high concurrencies when compared to Oracle WebLogic Server JMS arriving at the same destination both in clustered (RAC in the AQ JMS' case) and nonclustered cases.

  • AQ JMS can short-circuit 2-PCs when Oracle database operations are involved in the XA transaction. Therefore, in cases in which the messaging cost is much lower when compared to the 2-PC cost required for using XA, AQ JMS does well.

  • AQ JMS does better than Oracle WebLogic Server JMS when large message sizes are involved, when there are large message backlogs, or when there are complex selectors. This is because the database offers indexing, LOB streaming, embedded rules engines, and lock management that are much better than what Oracle WebLogic Server JMS offers.

  • AQ JMS does well in an Exadata-Exalogic pairing because it makes better use of Exadata capabilities. Oracle WebLogic Server JMS becomes bottle necked because of the lower end storage nodes in Exalogic.

Durable subscriptions are supported. This means that events are retained even if the subscriber is not up and running. Durable subscriptions continue to accumulate events. Table 33-2 describes how nondurable and durable subscriptions are handled in the various life cycle states of the SOA composite application.

Table 33-2 Business Events and Composite Life Cycle States

The Composite Is... Effect on Nondurable Subscribers Effect on Durable Subscribers

Deployed

The subscriber is created and starts receiving events.

The subscriber is created, a durable subscription is registered, and the subscriber starts receiving events.

Undeployed

The subscriber is removed and stops receiving events.

The subscriber is removed, a durable subscription is unregistered, and the subscriber stops receiving events.

Redeployed

The durable subscription and subscriber are recreated.

The durable subscription and its subscriber are recreated.

Shut down

The subscriber stops receiving events.

The subscriber stops receiving events, but events continue to be queued (are not dropped) through durable subscriptions.

Started up

The subscriber starts receiving events.

The subscriber receives events, including those queued up prior to startup.

Retired

The subscriber stops receiving events.

The subscriber stops receiving events and events are not queued (are dropped).

Activated

The subscriber starts receiving events.

The subscriber start receiving events.

33.2 Mapping Business Events to JMS Topic Destinations

You can map the flow of different business events through different JMS destinations in Oracle Enterprise Manager Fusion Middleware Control. This mapping can reduce business event bottlenecks caused by mapping all business events through a single destination. After installation, all business events are mapped by default to a single, local Oracle WebLogic Server JMS topic. You can manually create additional JMS topics and map business events to the topics appropriate to your performance needs.

Note the following best practices when mapping business events to JMS topics other than the default.

  • Perform the mapping before messages flow into JMS topic destinations. This prevents existing events from flowing into old JMS topic destinations for which there are no subscribers.

  • Restart the subscribing SOA composite applications or the SOA server after completing the mapping. This enables subscribers to be associated with the new JMS topic destination.

  • Ensure that the JMS topic is configured in the Oracle WebLogic Server Administration Console. See Creating an Oracle WebLogic Server JMS Topic.

  • Ensure that all JMS adapter connection factories are configured in the Oracle WebLogic Server Administration Console. See Optionally Creating JMS Adapter Connection Factories for JMS.

33.2.1 Creating an Oracle WebLogic Server JMS Topic

To create an Oracle WebLogic Server JMS topic:

  1. Log in to Oracle WebLogic Server Administration Console.
  2. In the Domain Structure, go to Services > Messaging > JMS Modules.
  3. In the Name column, click SOAJMSModule.
  4. Click New.
  5. Create a new topic.
  6. Target it to SOAJMSServer.

33.2.2 Optionally Creating JMS Adapter Connection Factories for Oracle WebLogic Server JMS

It is typically unnecessary to create JMS Adapter connection factories because you can reuse the ones included with EDN installation. If you need to create connection factories (for example, for a separate management purpose), follow these steps.

To create JMS adapter connection factories for Oracle WebLogic Server JMS:

  1. Log in to Oracle WebLogic Server Administration Console.
  2. From the Domain Structure, select soainfra > Environment > Deployments > JMS Adapter > Configuration > Outbound Connection Pools.
  3. Click New.
  4. Provide the JNDI name (for example, eis/wls/MyEdnWLjmsTopic).
  5. Save the new deployment plan.
  6. Return to JMS Adapter > Configuration > Outbound Connection Pools, and click the newly created connection factory.
  7. Provide values appropriate to your connection factory:
    Property Name Property Value

    AcknowledgeMode

    Leave as AUTO_ACKNOWLEDGE.

    ConnectionFactoryLocation

    For XA, use weblogic.jms.XAConnectionFactory.For a local transaction, use weblogic.jms.ConnectionFactory.

    FactoryProperties

    For a durable topic, specify ClientID=your_client_ID.For a nondurable topic, leave this field blank.

    IsTopic

    Always true.

    IsTransacted

    For XA, use false.

    For a local transaction, use true. However, if the Oracle WebLogic Server JMS server is running in a local JVM (same JVM as the EDN/JMS adapter), set IsTransacted to false.

    Password

    Leave blank.

    Username

    Leave blank.

    Transaction Support (in the Transaction tab)

    Leave as XA Transaction.

33.2.3 Creating an AQ JMS Topic

Open the Database Navigator (in Oracle JDeveloper) or SQL Developer as the soainfra user, and run the following script to create an AQ JMS topic:

define edn_user=soainfra_schema_user_here
define topic=your_custom_aqjms_topic_name_here (for example, EDN_AQJMS_TOPIC_2)
define topic_table=your_custom_aqjms_topic_table_here (EDN_AQJMS_TOPIC_
TABLE_2)
 
begin
  DBMS_AQADM.stop_queue(queue_name => '&edn_user..&topic');
  DBMS_AQADM.drop_queue(queue_name => '&edn_user..&topic');
  DBMS_AQADM.drop_queue_table(queue_table => '&edn_user..&topic_table');
end;
/
begin
  dbms_aqadm.create_queue_table(queue_table => '&edn_user..&topic_table', 
                                queue_payload_type => 'SYS.AQ$_JMS_MESSAGE', 
                                multiple_consumers => true);
  dbms_aqadm.create_queue(queue_name => '&edn_user..&topic', 
                          queue_table => '&edn_user..&topic_table', 
                          max_retries => 256);
  dbms_aqadm.start_queue(queue_name	=>	'&edn_user..&topic');
end;
/
commit;

The queue and queue table are created.

33.2.4 Exposing an AQ JMS Topic

If you created an AQ JMS topic in Creating an AQ JMS Topic , you must expose the topic to Oracle WebLogic Server applications, including Oracle SOA Suite applications. Use Oracle WebLogic Server Administration Console to either create a new foreign server or update the existing foreign server EDNAQjmsForeignServer to add AQ JMS topic mapping:

To expose an AQ JMS topic:

  1. Optionally create a new foreign service:

    1. Log in to Oracle WebLogic Server Administration Console.

    2. In the Domain Structure, go to Services > Messaging > JMS Modules > SOAJMSModule.

    3. Click New, and select Foreign Server.

    4. Name the foreign server, target it to the SOA server, and click Finish.

    5. Open the new foreign server, and go to Configuration > General.

    6. Set the following properties.

      Property Value

      JNDI Initial Context Factory

      oracle.jms.AQjmsInitialContextFactory

      JNDI Properties

      For an EDN XA JDBC data source (for example, datasource=jdbc/EDNDataSource).

      For an EDN non-XA JDBC data source (for example, datasource=jdbc/EDNLocalTxDataSource).

  2. If you also create your custom JMS adapter connection factories for AQ JMS, then you must create a connection factory mapping:

    1. Go to the Configuration > Connection Factories tab of this foreign server, and click New.

    2. Provide the local JNDI name (which matches the value configured in the adapter's ConnectionFactoryLocation) and remote JNDI name, which is XATopicConnectionFactory for XA support.

    3. If you must create another foreign server that uses a non-XA JDBC data source, set the remote JNDI name to TopicConnectionFactory for non-XA support.

  3. Add mapping to the AQ JMS topic

    1. Click New to create a new destination mapping in one of the newly created foreign servers or the existing foreign server EDNAQjmsForeignServer.

    2. Map a local JNDI name to a remote JNDI name convention of Topics/custom_aqjms_topic_name.

33.2.5 Optionally Creating JMS Adapter Connection Factories for AQ JMS

It is typically unnecessary to create JMS adapter connection factories because you can reuse the ones included with EDN installation. If you must create connection factories (for example, for a separate management purpose), follow these steps.

To create JMS adapter connection factories for AQ JMS:

  1. Log in to Oracle WebLogic Server Administration Console.
  2. From the Domain Structure, select soainfra > Environment > Deployments > JMS Adapter > Configuration > Outbound Connection Pools.
  3. Click New.
  4. Provide the JNDI name (for example, eis/wls/MyEdnAQjmsTopic).
  5. Save this new deployment plan.
  6. Return to JMS Adapter > Configuration > Outbound Connection Pools, and click the newly created connection factory.
  7. Provide values appropriate to your connection factory:
    Property Name Property Value

    AcknowledgeMode

    Leave as AUTO_ACKNOWLEDGE.

    ConnectionFactoryLocation

    For XA, the value must match the local JNDI name of the connection factory that is mapped to XATopicConnectionFactory in the foreign server of EDNAQjmsForeignServer or your custom foreign server supporting XA.

    For a local transaction, the value must match the local JNDI name of the connection factory that is mapped to TopicConnectionFactory in the foreign server of EDNAQjmsLocalTxForeignServer or your custom foreign server supporting a local transaction.

    FactoryProperties

    For a durable topic, specify ClientID=your_client_ID.For a nondurable topic, leave this field blank.

    IsTopic

    Always true.

    IsTransacted

    For XA, use false.

    For a local transaction, use true.

    Password

    Leave blank.

    Username

    Leave blank.

    Transaction Support (in the Transaction tab)

    Leave as XA Transaction.

33.2.6 Enabling a Remote Client to Interact with an AQ JMS-Based Topic

If an event type is mapped to the default EDN AQ JMS topic or a custom AQ JMS topic, EDN enables Oracle SOA Suite publishers and subscribers to interact with this event type through the AQ JMS topic. However, EDN does not enable remote publishers or subscribers to interact by default.

To enable remote publishers, subscribers, or both, the EDN foreign servers (either the one installed by EDN or the custom foreign servers) must have their JNDI properties and credential updated, as shown in Table 33-3.

Table 33-3 JNDI Properties and Credentials

Property Name Property Value

JNDI Properties

Add: db_url=jdbc:oracle:thin:@host:port:service.

java.naming.security.principal=soainfra_schema_user.

JNDI Properties Credential

Enter the password for oainfra_schema_user.

Figure 33-3 provides details.

Figure 33-3 Enable a Remote Client to Interact with an AQ- MS-Based Topic

Description of Figure 33-3 follows
Description of "Figure 33-3 Enable a Remote Client to Interact with an AQ- MS-Based Topic"

33.2.7 Mapping Business Events to JMS Topic Destinations on the Business Events Page

You can map business events to JMS topic destinations on the Business Events page in Oracle Enterprise Manager Fusion Middleware Control.

To map business events to JMS topic destinations on the Business Events page:

  1. Access this page through one of the following options:
    From the SOA Infrastructure Menu... From the SOA Folder in the Navigator...

    Select Business Events.

    Right-click soa-infra and select Business Events.

    The Business Events page displays the following details:

    • A utility for searching for a specific business event by specifying a full or partial name and clicking the Search icon. Click Help > Help For This Page under the weblogic menu for details.

    • Business events, including the namespace, event name, JMS type and mapping, number of subscriptions to each event, and number of failed event deliveries. Business events are contained within their namespace.

  2. In the JMS Mapping column, view the supported JMS topic mapping for the event:
    • Default: Indicates that the business event is using the default JMS topic destination mapping. The default configuration consists of a single, local JMS topic destination that uses Oracle WebLogic Server JMS as the underlying provider.

    • Modified: Indicates that the business event is not using the default JMS topic destination mapping.

  3. Click the JMS topic mapping type in the column. For example, if Default is selected, the following details are displayed. The connection factory settings that are initially displayed are automatically set during installation.
  4. Enter values appropriate to your environment:
    Element Description

    Oracle Enterprise Messaging System (OEMS)

    Select the underlying JMS provider:

    • Oracle WebLogic Server JMS (default provider)

    • Oracle Advanced Queueing JMS

    JNDI Connection Factory

    Specify connection factory details for the JMS adapter. EDN uses the JMS adapter to interact with JMS.

    For Oracle WebLogic Server JMS:

    • eis/wls/EDNxaDurableTopic (supports XA, durable topic with ClientID=edn_wljms_xa_client)

    • eis/wls/EDNxaTopic (supports XA)

    • eis/wls/EDNLocalTxDurableTopic (supports local transaction, durable topic with ClientID=edn_wljms_localtx_client)

    • eis/wls/EDNLocalTxTopic (supports local transaction)

    For Oracle AQ JMS:

    • eis/aqjms/EDNxaDurableTopic (supports XA, durable topic with ClientID=edn_aqjms_xa_client)

    • eis/aqjms/EDNxaTopic (supports XA)

    • eis/aqjms/EDNLocalTxDurableTopic (supports local transaction, durable topic with ClientID=edn_aqjms_localtx_client)

    • eis/aqjms/EDNLocalTxTopic (supports local transaction)

    JMS Topic Name

    Specify the JNDI name of the JMS topic.

    Use Default JMS Topic

    Select to reset all configuration fields to values to use the default JMS topic destinations provided during installation. The default configuration consists of a single, local JMS topic destination that uses Oracle WebLogic Server JMS as the underlying provider.

    However, if the default JMS type is changed to AQ JMS instead of Oracle WebLogic Server JMS, then the default configuration consists of a single, local JMS topic that uses Oracle AQ as the underlying provider.

  5. Click Apply to close the dialog and display your selection in the JMS Mapping column.
  6. Shut down and start up either of the following:
    • The impacted SOA composite applications on the Deployed Composites page of the SOA Infrastructure

    • The Oracle SOA Suite managed server

For more information, see the following documentation:

33.3 Testing the Publishing of Business Events and Viewing the EDL File

You can test the publishing of business events and view the EDL file contents. The business event is defined using EDL. EDL is a schema used to build business event definitions.

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

    From the SOA Infrastructure Menu... From the SOA Folder in the Navigator...

    Select Business Events.

    Right-click soa-infra and select Business Events.

    The Business Events page displays the following details:

    • A utility for searching for a specific business event by specifying a full or partial name and clicking the Search icon. Click Help > Help for This Page under the weblogic menu for details.

    • Business events, including the namespace, the event name, the JMS type, the mapping between the business event and the JMS topic destination, the number of subscriptions to each event, and the number of failed event deliveries. Business events are contained within their namespace.

  2. In the Namespaces and Events column, select a specific event to test.

    1. Click Test to test the selected event. This action enables you to publish a test event that subscribers can act upon.

      The Test Event dialog appears.

    2. Specify the XML payload to use in the test.

    3. Click Publish.

      If publishing is successful, the following message is displayed.

      The Event published successfully
      
  3. In the Namespaces and Events column, select a specific event for which to display the EDL file.

    1. Click Show Event Definition to display the EDL file for the selected event.

    2. Click OK to close the message.

33.4 Viewing Business Event Subscribers

When business events are published, service components can subscribe to them. You can view the service components that have subscribed to business events. Service component subscriptions are created in Oracle JDeveloper during design time and cannot be modified in Oracle Enterprise Manager Fusion Middleware Control.

All business events are applicable to the entire Oracle SOA Suite domain instead of the individual partitions of the publishers and subscribers. Business events are also displayed as separate entries in the flow trace of the business flow instance.

Note:

  • If your SOA composite application includes a business event subscription, and you deploy different revisions of the composite, all event subscriptions from all revisions of the composite are active and receive messages. To receive the event with the latest revision of the composite only, it is recommended that you retire all previous revisions of the composite.

  • A BPEL component in a retired SOA composite application cannot receive a business event, even if the event is associated with a noninitiating receive activity of the BPEL process.

To view business event subscribers:

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

    From the SOA Infrastructure Menu... From the SOA Folder in the Navigator...
    1. Select Business Events.

    1. Right-click soa-infra.

    2. Select Business Events.

  2. Click Subscriptions.

    The Subscriptions page displays the following details:

    • A utility for searching for a specific subscription by specifying criteria and clicking Search. You can search based on the namespace or event name. Click Help > Help for This Page under the weblogic menu for details.

    • The component subscriptions, including the event name, the namespace, the service component subscribing to the event, the SOA composite application, any optionally defined XPath filters, the consistency level (Guaranteed or OneAndOnlyOne), and the number of business events that failed to be delivered.

  3. In the Subscription Component column, click a service component to access its home page.

  4. In the Composite column, click a SOA composite application to access its home page.

For more information about creating business events in Oracle JDeveloper, see Chapter "Using Business Events and the Event Delivery Network" of Developing SOA Applications with Oracle SOA Suite.

Note:

Enforcement of policies for event subscriptions is not supported in this release. You can attach or detach a policy to or from a service component that subscribes to a business event (such as Oracle Mediator) without being warned. This action does not result in any errors; policy enforcement simply does not occur.

33.5 Resolving Duplicate Messages for Subscribers in Clustered Environments

SOA composite subscribers can receive duplicate events in a multiple-node cluster. This occurs when EDN uses the default JMS type and topic (that is, Oracle WebLogic Server JMS). This occurs because the template used by Oracle SOA Suite installation defaults to a Uniform Distributed WebLogic JMS topic with a replicated (instead of partitioned) forwarding policy and does not support configuration of the forwarding policy.

To automatically configure an EDN JMS topic to be a partition-distributed topic in a clustered environment, change the EDN JMS topic from replicated to partitioned.

To change to the partitioned policy:

  1. Log in to Oracle WebLogic Server Administration Console.
  2. In the Domain Structure, select soainfra > Services > Messaging > JMS Modules > SOAJMSModule.
  3. Click the distributed EDN topic (dist_EDNTopic_auto).
  4. Go to Configuration > General tab.
  5. In the dropdown list, change Forwarding Policy from Replicated to Partitioned.

When set to Partitioned, the physical member receiving the message is the only member of the uniform distributed topic that is aware of the message. When a message is published to the logical name of a partitioned uniform-distributed topic, it only arrives at one specific, physical topic member. Once a message arrives at a physical topic member, the following occurs:

  • The message is not forwarded to the rest of the members of the uniform distributed destination.

  • Subscribers at other physical topic members do not receive a copy of the message.

33.6 Changing the JMS Type

You can change the default JMS provider type from Oracle WebLogic Server JMS to AQ JMS. or vice versa.

  1. From the SOA Infrastructure menu, select Administration > System MBean Browser.
  2. Click the Search icon, enter EDNConfig, and click Find.
  3. Click JmsType.
  4. Specify a value.
    • WLJMS (Oracle WebLogic Server JMS)

    • AQJMS (Oracle Advanced Queuing JMS)

  5. Click Apply.
  6. Restart the SOA server.

    Note that you can only change the default JMS type mapped from an event type that does not have mapping to a custom JMS topic. Custom mapping (where an event type is mapped to a user-defined JMS topic) is not altered by this change.

33.7 Configuring the Inbound Poller Thread Number

For each subscriber, EDN spawns poller threads (defaults to one worker thread) for the underlying JMS consumer. You can change the number of inbound poller threads is either of two ways:

33.7.1 Updating the Global Inbound Poller Thread Number in the System MBean Browser

You can update the inbound poller thread number at the SOA Infrastructure level with the (global) attribute ThreadsPerSubscriber.

To update the inbound poller thread number in the System MBean Browser:

  1. From the SOA Infrastructure menu, select Administration > System MBean Browser.
  2. Click the Search icon, enter EDNConfig, and click Find.
  3. Click the ThreadsPerSubscriber attribute. Change the value from the default of 1 to an appropriate integer, and click Apply.

    A confirmation message indicating that the ThreadsPerSubscriber attribute has been updated successfully is displayed. No restart of the SOA server or redeployment of SOA composite applications is necessary.

33.7.2 Updating the Local Inbound Poller Thread Number Value at the Service Component Level

You can update the local inbound poller thread number at the service component level with a System MBean property corresponding to the composite containing the event subscribing component (Oracle Mediator or BPEL process).

  1. From the SOA Infrastructure menu, select Administration > System MBean Browser.
  2. Select Application Defined MBeans > oracle.soa.config > Server: Server_name > SCAComposite > composite_name > SCAComposite.SCAComponent > component_name.
  3. Expand the Events attribute.
  4. Update the numberOfPollerThreads value. The default value is -1, which means that the global SOA Infrastructure level EDNConfig MBean's ThreadsPerSubscriber value takes effect for initializing EDN inbound poller threads for the subscriber. The updated numberOfPollerThreads value that you specify takes precedence over the global value.
  5. Click Apply.
  6. When the Confirmation message appears, click Return.
  7. Switch to the Operations tab, and click save.
  8. On the operation: save page, click Invoke.

    A Confirmation message is displayed.

  9. Restart the SOA composite application of interest, or restart the SOA server for the numberOfPollerThreads to take effect.