how many SOA composite instances are generated when createCustomer business event is fired?

Over a period of time, you have deployed three versions (1.0, 1.1, and 1.2) of a SOA application X
to a three-node SOA cluster. All versions of X subscribes to a business event named
createCustomer and instantiate a new BPEL process Y on receiving the event.
At runtime, how many SOA composite instances are generated when createCustomer business
event is fired?

Over a period of time, you have deployed three versions (1.0, 1.1, and 1.2) of a SOA application X
to a three-node SOA cluster. All versions of X subscribes to a business event named
createCustomer and instantiate a new BPEL process Y on receiving the event.
At runtime, how many SOA composite instances are generated when createCustomer business
event is fired?

A.
1

B.
3

C.
9

D.
0

Explanation:

Note:
* When the Oracle SOA Service Infrastructure performs an update or redeployment of a
composite, it can overwrite an existing version (x) or create a new version (x+1). All composites
are uniquely identified based on the composite name and revision. By default, clients accessing a

composite use the version that is identified in the MDS repository as the default version (also
visible from Oracle Enterprise Manager Fusion Middleware Control).



Leave a Reply 6

Your email address will not be published. Required fields are marked *


Teps

Teps

Response -> B. 3

Source: http://docs.oracle.com/cd/E23943_01/dev.1111/e10224/obe_intro.htm

41.3.3 What You May Need to Know About Subscribing to a Business Event

Subscribers in nondefault revisions of SOA composite applications can still get business events. For example, note the following behavior:

Create a composite application with an initial Oracle Mediator service component named M1 that publishes an event and a second Oracle Mediator service component named M2 that subscribes to the event. The output is written to a directory.

Deploy the composite application as revision 1.

Modify the composite application by adding a third Oracle Mediator service component named M3 that subscribes to the same event and writes the output to a different directory.

Deploy the composite application as revision 2 (the default).

Invoke revision 2 of the composite application.

Oracle Mediator M2 writes the output to two files with the same content in the directory. As expected, Oracle Mediator M3 picks up the event and writes the output successfully to another directory. However, Oracle Mediator M2 (from revision 1) is also picking up and processing the published event from revision 2 of the composite application. Therefore, it creates one more output file in the same directory.

igor

igor

B. Subscribers in nondefault revisions of SOA composite applications can still get business events

Valdir

Valdir

I Agree it B.

Master7777

Master7777

B because Subscribers in nondefault revisions of SOA composite applications can still get business events.