Oracle SOA OSB Interview Questions

Weblogic and Generic :

1. JMS configuration and DB Adapter configuration in Weblogic server.
2. Scenario based question from JMS Adapter
3. Scenario based question from throttling.
4. Question from wsdl,xsd,types of wsdl.
5. OWSM policy
6. Question about unit testing using SOAPUI
7. Migration related concept.
8. Component of WSDL.
9. Given the opportunity can you prepare a wsdl file?
10. Data Source configuration
11. Configure RAC in Weblogic and implement clustering.
12. What is target namespace in schema?
13. Question related to encryption
14. In the cluster environment while updating the adapter it faults out. What could be the possible reason for it.
15. Timeouts
16. Difference between stateful and stateless webservice
17. Topic and SAF

Oracle SOA Suite Related

1. How to access http webservices in BPEL
2. Config plan
3. If you have a BPEL Service that is referencing to the third party web service, at the time of deployment the service may be down , causing deployment to fail. How to overcome it?
4. What is worklist?
5. How to get email notification and how UMS adapter work?
6. Setting composite title in bpel and sensors.
7. Fault management framework in bpel.
8. Dynamic Routing in Mediator
9. Mediator Resequencing.
10. Parallel Routing in mediator.
11. What is File Debatching ? 
12. What is File ChunkedRead ? 
13. Read from multiple directories in File Adapter.
14. Rejection Message Handler ?
15. Use of Config Plans ?
16. Standard Faults in BPEL
17. OWSM policies
18. Rollback and Transaction.
19. Compensation
20. How can we make a partner link dynamic?
21. What is getPreference property? How do we set it and what advantage it provides? 
22. How to increase performance increase in bpel (Db Adapter/file adapter)? 
23. What are dspMaxThread and recieverThread properties? Why are they important? 
24. In memory optimization and Persistence complete.
25. How does a Async request run in the backend? 
26. XREF.
27. Human Task.
28. Business Rules Related.
29. Rejection message Handler.

Oracle Service Bus Related:

1. What is the purpose of OSB.
2. What are the JCA Adapter you have used in OSB?
3. Why we use QOS and when it use.
4. How parallel processing done in OSB.
5. Error handling in OSB
6. When to use local,soa-direct protocol.
7. How to use service result caching in OSB
8. Alter,Reporting, Log, Java Callout action
9. SLA, Workforce, dispatch policy in osb
10. Difference between publish and service callout in osb
11. Transformations in OSB.
12. Difference between OSB and SOA.
13. What is MFL in OSB
14. Routing options in OSB
15. Difference between Pipeline Pair and routing in OSB
16. Xquery 
17. Significance of FLOWR / Curly braces in Xquery

Blogs:

OIC:
http://niallcblogs.blogspot.com
https://blogs.oracle.com/integration/cicd-implementation-for-oic

OSB :
https://svgonugu.com/2014/09/26/service-bus-12c-a-hands-on-tutorial/
https://svgonugu.com/2015/02/06/soa-12cedn-with-service-bus/
https://svgonugu.com/2015/03/05/service-bus-12c-two-way-ssl/
https://svgonugu.com/2015/09/20/owsm-12cusing-saml-token-policy/
https://svgonugu.com/2015/03/06/service-bus-12c-outbound-ssl/
https://nitinaggarwal.wordpress.com/2013/11/08/securing-an-osb-service-with-owsm/
https://svgonugu.com/2015/09/01/soa-12c-maven-articles/
https://svgonugu.com/2015/06/24/soa-12c-ess-articles/
https://blog.rubiconred.com/accepting-attachments-into-osb-forwarding-via-jms/

SOA Related:
http://myexperienceswithsoa.blogspot.com/2014/05/large-payload-handling-in-soa.html
https://technology.amis.nl/2015/11/27/processing-large-xml-files-in-the-soa-suite/
https://technology.amis.nl/2011/10/24/soa-suite-file-adapter-pre-and-post-processing-using-valves-and-pipelines/
https://technology.amis.nl/2014/05/07/processing-large-files-through-soa-suite-using-synchronous-file-read/
https://docs.oracle.com/cd/E28280_01/admin.1111/e15867/app_jmx_monitoring.htm#OSBAG748
https://docs.oracle.com/middleware/1221/soasuite/develop/GUID-05E65114-9664-4D60-B7DA-BED0BB87681F.htm#SOASE2325
https://docs.oracle.com/middleware/1221/soasuite/develop/GUID-A6C92CD4-A78D-4D12-B667-96CD1FB9828B.htm#SOASE85099
https://docs.oracle.com/middleware/1221/soasuite/develop/GUID-EDFF423A-3FEC-4C61-A86C-79BDF9AEDBC6.htm#SOASE337
http://prasanna-soa.blogspot.com/2017/02/business-rules-with-decision-tables-in.html
http://bhupisoa.blogspot.com/2015/01/soa-11g-bpel-transaction-handling-part-1.html
http://bhupisoa.blogspot.com/2015/01/soa-11g-bpel-transaction-handling-part-2.html
https://shrikworld.blogspot.com/2011/03/errorhandling-in-soa-11g.html
https://rathinasaba.wordpress.com/tag/fault-policy-in-oracle-bpel/
https://beatechnologies.wordpress.com/tag/fault-handling-and-management-in-oracle-soa-suite-11g/
http://soa-bpel-esb.blogspot.com/2014/07/fault-policy-editor-in-soa-12c.html
https://soaarchitecture.wordpress.com/2014/10/06/dvm-mds-table-views/

Dehydration in Oracle SOA

Idempotence in BPEL :- 

Idempotent Activity	Non Idempotent Activity
Does not dehydrate	Dehydrates
Related to Transient Process	Related to Durable process
Assign, Invoke	Wait, Receive, Pick(onMessage, onAlarm), checkpoint(), Dehydrate
Can be retried	Not Retried

So when you specify the idempotent property as "false" in the partner link of a BPEL process ,

• It becomes non idempotent and cause the BPEL process for dehydration and so a commit occurs . 
• It ends the current transaction of a BPEL process and start a new one.

If BPEL recovers from dehydration store idempotent activities are retried again.

Properties	Transient Process	Durable Process
When Dehydrated	only once the execution is completed.	Non idempotent activities. After End of Process. Mid process breakpoints.
Exception / Crash occurs	No Trace in System.	this process instance appears in Oracle BPEL Control up to the last dehydration point (breakpoints activity) once the server restarts. If the server crashes before the process instance reaches the first mid process breakpoints activity, the instance is not visible in Oracle BPEL Control after the server restarts.
Example	Synchronous process. Any Process followed by setting in composite.xml  bpel.config.inMemoryOptimization = true bpel.config.completionPersistPolicy = off/deferred/faulted	Asynchronous process.

Reference : https://www.linkedin.com/today/author/sandeep-pachauri-b03a211b?trk=author-info__article-link

Weblogic Error : Delaying formation of a new cluster; unicast networking appears to be inoperable on interface

While booting up my OSB Managed Server using :-

• Open CMD
• cd C:\Oracle\Middleware\Oracle_Home\user_projects\domains\soa12c_domain\bin 
• startManagedWebLogic.cmd osb_server1 http://Deb_Kriti:7001

I was receiving lots of warning -

<27/03/2019 8:59:13 AM IST> <Warning> <com.oracle.coherence> <BEA-000000> <2019-03-27 08:59:13.218/305.579 Oracle Coherence GE 12.2.1.0.0 <W
arning> (thread=Cluster, member=n/a): Delaying formation of a new cluster; unicast networking appears to be inoperable on interface 192.168.
0.13 as this process isn't receiving even its own transmissions; consider forcing IPv4 via -Djava.net.preferIPv4Stack=true>

And then the server was FORCE SHUTTING DOWN.

I turned off Firewall but it did not work.

I followed this blog article Here and tried the solution 2 :-

Solution 2:

To change the type of coherence the cluster is using, you have to add a property inside the CoherenceSystemResource config file (which is located in the $DOMAIN_HOME/config/coherence folder). The correct *-coherence.xml is the one with the same name as the coherence systemResource as seen in Solution 1 (by default: defaultCoherenceCluster-coherence.xml).

Just add the following highlighted line in the coherence-cluster-params element-tag:

  <coherence-cluster-params>

    <cluster-listen-port>7574</cluster-listen-port>

    <clustering-mode>multicast</clustering-mode>

  </coherence-cluster-params>




This also should lead to the server starting again.

Then I executed 

• startManagedWebLogic.cmd osb_server1 http://Deb_Kriti:7001

It Worked!!! The Server came to RUNNING Mode

However , when I tried starting my second Managed Server it did not work.

Then I attempted Solution 1 

Solution 1:

To remove the coherence cluster awareness of the default server, you just have to remove the coherence-cluster-system-resource tag from the domains config.xml file (which resides in your $DOMAIN_HOME/config folder).

<server>  
  <name>DefaultServer</name>
     …
  <coherence-cluster-system-resource>defaultCoherenceCluster</coherence-cluster-system-resource>
</server>
Just remove the highlighted entry and the server should start (without any awareness of coherence). 

and restarted all 3 servers ( Admin and Managed Servers) .

All came to RUNNING mode.