Which two approaches are valid when using dynamic partner links in a BPEL process?
A.
A WSDL file, which contains multiple services that use the same portType, is available at
design time, but the decision to determine which service is used can only be made at runtime.
B.
When the BPEL process is designed, the endpoint URL of the WSDL file is known but the
services and port types are not known.
C.
When the BPEL process is designed, the services and port types of the WSDL file are known
but the endpoint URI is not known.
D.
A WSDL file, which contains multiple services that use different portTypes, is available at
design time, but the decision to determine which server us used can only be made at runtime.
Explanation:
A (not D): How To Create a Dynamic Partner Link at Design Time for Use at
Runtime
To create a dynamic partner link at design time for use at runtime:
etc
C (not B): The BPEL specification mandates that only the partner endpoint reference (EPR) can
be changed dynamically. In BPEL terms, only the partnerRole of a partner link element can have a
new value assigned. The myRole value doesn’t change after the BPEL has been deployed.
Note:
* Dynamic Partner Links and Dynamic Addressing
During the design-time of an application, you may need to configure certain services whose
endpoints (addresses) are not known beforehand, or it may be necessary to change an endpoint
reference while the application is running. The Dynamic Partner link feature allows you to
dynamically assign an endpoint reference to the partner link. This means that you can use one
partner link for subsequent calls to different web-services (provided that the services use the same
interface).
* For successful deployment of the process, a partner link should be completely defined. When
you deploy the project, the WSDL file for the partner link should contain and define both the
abstract and the concrete information for the partner link, including address and port, though later
the concrete information can be changed independently from the WSDL file.
A. The Dynamic Partner link feature allows you to dynamically assign an endpoint reference to the partner link. This means that you can use one partner link for subsequent calls to different web-services (provided that the services use the same interface).
C. endpoint is unknown
C.
When you are designing an application, you may need to configure certain services whose endpoints (addresses) are not known beforehand, or it may be necessary to change an endpoint reference while the application is running. The Dynamic Partner link feature allows you to dynamically assign an endpoint reference to the partner link.
(http://docs.oracle.com/cd/E19182-01/821-0017/cnfg_bpel-se-dynamic-ptnrlink_c/index.html)
A.
http://www.oracle.com/technetwork/articles/carey-090553.html
A,C
AC