Explore topic-wise InterviewSolutions in .

To move your organization toward greater service orientation, you need to take a balanced approach to building versus buying. To create the infrastructure for an SOA, you’ll need the RIGHT commercial off-the-shelf software that complements (rather than REPLACES) your existing IT infrastructure. This is a “buy” statement. On the “build” side, you may also choose to access know-how and hands-on INVOLVEMENT to use these software products effectively and get the most out of them. This infrastructure and the associated tools can help you create the business services that run on your SOA. Again, there is some “building” associated with this. So the REAL answer is that you need a certain measure of both building and buying.

To move your organization toward greater service orientation, you need to take a balanced approach to building versus buying. To create the infrastructure for an SOA, you’ll need the right commercial off-the-shelf software that complements (rather than replaces) your existing IT infrastructure. This is a “buy” statement. On the “build” side, you may also choose to access know-how and hands-on involvement to use these software products effectively and get the most out of them. This infrastructure and the associated tools can help you create the business services that run on your SOA. Again, there is some “building” associated with this. So the real answer is that you need a certain measure of both building and buying.

Oracle WSM Policy Manager PROVIDES the INFRASTRUCTURE for ENFORCING global security and auditing POLICIES in the Service Infrastructure.

Oracle WSM Policy Manager provides the infrastructure for enforcing global security and auditing policies in the Service Infrastructure.

Oracle Business Rules, initiated by a BPEL process service component, ENABLE dynamic DECISIONS at runtime. In addition, the human TASK and MEDIATOR service components can make USE of rules for dynamic routing.

Oracle Business Rules, initiated by a BPEL process service component, enable dynamic decisions at runtime. In addition, the human task and mediator service components can make use of rules for dynamic routing.

Oracle Metadata Repository MDS STORES business events, rulesets for use by Oracle Business Rules, XSLT files for Oracle Service Bus and Oracle MEDIATOR, XSD XML schema files for Oracle BPEL Process Manager, WSDL files, and metadata files for Complex Event Processing.

Oracle Metadata Repository MDS stores business events, rulesets for use by Oracle Business Rules, XSLT files for Oracle Service Bus and Oracle Mediator, XSD XML schema files for Oracle BPEL Process Manager, WSDL files, and metadata files for Complex Event Processing.

BUSINESS events are messages sent as the RESULT of an occurrence or situation, such as a NEW ORDER or completion of an order. In Oracle SOA Suite, the mediator service component subscribes or publishes events. When an event is published, other applications can SUBSCRIBE to it.

Business events are messages sent as the result of an occurrence or situation, such as a new order or completion of an order. In Oracle SOA Suite, the mediator service component subscribes or publishes events. When an event is published, other applications can subscribe to it.

Oracle Adapters use JCA (Java Connector Architecture) technology to connect external systems to the Oracle SOA Suite.
Oracle SOA Suite provides the FOLLOWING technology adapters to INTEGRATE with transport protocols, data stores, and messaging middleware:

• BAM
• FTP
• Java Messaging Service (JMS)
• Advanced Queuing (AQ)
• Files
• MESSAGE Queuing (MQ) Series
• Legacy Adapters
• Application Adapters

Oracle Adapters use JCA (Java Connector Architecture) technology to connect external systems to the Oracle SOA Suite.
Oracle SOA Suite provides the following technology adapters to integrate with transport protocols, data stores, and messaging middleware:

Oracle Service Bus provides standalone service bus capabilities, enabling separation between application developers and TARGET systems or SERVICES. Oracle Service Bus receives messages through a transport protocol such as HTTP(S), JMS, File, and FTP, and sends messages through the same or a different transport protocol.

Service response messages FOLLOW the inverse path. Oracle Service Bus handles the deployment, management, mediation, messaging, security and GOVERNANCE of implementing SOA to enterprise applications.

Oracle Service Bus provides standalone service bus capabilities, enabling separation between application developers and target systems or services. Oracle Service Bus receives messages through a transport protocol such as HTTP(S), JMS, File, and FTP, and sends messages through the same or a different transport protocol.

Service response messages follow the inverse path. Oracle Service Bus handles the deployment, management, mediation, messaging, security and governance of implementing SOA to enterprise applications.

Oracle mediator is used for route, validate, filter and transform data from SERVICE providers to external partners.

Route: DETERMINES the service component (BPEL process, business rule, human task, and mediator) to which to send the messages.

Validate: Provides support for validating the incoming message payload by using a schematron or an XSD FILE.

Filter: If specified in the rules, applies a filter expression that SPECIFIES the contents (payload) of a message be analyzed before any service is invoked.

Transformation: If specified in the rules, transforms document data from one XML schema to another, thus enabling data interchange among applications using different schemas.

Oracle mediator is used for route, validate, filter and transform data from service providers to external partners.

Route: Determines the service component (BPEL process, business rule, human task, and mediator) to which to send the messages.

Validate: Provides support for validating the incoming message payload by using a schematron or an XSD file.

Filter: If specified in the rules, applies a filter expression that specifies the contents (payload) of a message be analyzed before any service is invoked.

Transformation: If specified in the rules, transforms document data from one XML schema to another, thus enabling data interchange among applications using different schemas.

The following components comprise an Oracle SOA SUITE installation:

• Service INFRASTRUCTURE
• Oracle Mediator
• Oracle Adapters
• Business Events and Events Delivery Network
• Oracle Metadata Repository
• Oracle Business Rules
• Oracle WSM Policy Manager
• Oracle BPEL Process Manager (Business Process Execution Language)
• HUMAN Workflow
• Oracle Business ACTIVITY Monitoring
• Oracle User Messaging Service
• Oracle B2B
• Oracle JDeveloper
• Oracle Enterprise Manager

The following components are included with Oracle SOA Suite, but available as a separate download:

• Oracle Service Bus (provides service virtualization and protocol transformations for oracle SOA appl)
• Oracle COMPLEX Event Processing

The following components comprise an Oracle SOA Suite installation:

The following components are included with Oracle SOA Suite, but available as a separate download:

XSLT processes XML documents and transforms document data from ONE XML SCHEMA to another.

XSLT processes XML documents and transforms document data from one XML schema to another.

BPEL provides enterprises with an INDUSTRY standard for business process ORCHESTRATION and EXECUTION. Using BPEL, you design a business process that integrates a series of discrete services into an end-to-end process flow. This integration REDUCES process cost and COMPLEXITY.

BPEL provides enterprises with an industry standard for business process orchestration and execution. Using BPEL, you design a business process that integrates a series of discrete services into an end-to-end process flow. This integration reduces process cost and complexity.

Service DATA Objects (SDO) provides a data programming architecture. It provides a standardized view on data, and provides efficient transportation, as well as change capture, in form of a change summary. More specifically, it COLLECTS a data GRAPH of related business objects, called DataObjects. This graph tracks the schema that describes the DataObjects. Knowledge is not required about how to access a PARTICULAR back-end data source to use SDO in a SOA composite APPLICATION. Consequently, you can use static or dynamic programming styles and obtain connected and disconnected access.

Service Data Objects (SDO) provides a data programming architecture. It provides a standardized view on data, and provides efficient transportation, as well as change capture, in form of a change summary. More specifically, it collects a data graph of related business objects, called DataObjects. This graph tracks the schema that describes the DataObjects. Knowledge is not required about how to access a particular back-end data source to use SDO in a SOA composite application. Consequently, you can use static or dynamic programming styles and obtain connected and disconnected access.

SERVICE Component Architecture (SCA) assembly model abstracts the implementation and ALLOWS assembly of components, with little implementation DETAILS. SCA enables you to represent business logic as reusable service components that can be easily integrated into any SCA-compliant application. The resulting application is known as a SOA composite application. The specification for the SCA standard is maintained by the Organization for the Advancement of Structured Information Standards (OASIS).

Service Component Architecture (SCA) assembly model abstracts the implementation and allows assembly of components, with little implementation details. SCA enables you to represent business logic as reusable service components that can be easily integrated into any SCA-compliant application. The resulting application is known as a SOA composite application. The specification for the SCA standard is maintained by the Organization for the Advancement of Structured Information Standards (OASIS).

CONCRETE: Besides the information about how to communicate to the web service, it the information on where the service exist. It has BINDINGS (Protocol the message should be sent) and Services(has endpoint for each bindings). 

ABSTRACT: It has information about how to communicate to the web service like types (Schema), Message (INPUT and output messages service ACCEPTS) ,Operations (operation that can be performed on this service) and port Type.

Concrete: Besides the information about how to communicate to the web service, it the information on where the service exist. It has Bindings (Protocol the message should be sent) and Services(has endpoint for each bindings). 

Abstract: It has information about how to communicate to the web service like types (Schema), Message (input and output messages service accepts) ,Operations (operation that can be performed on this service) and port Type.

• In 10G for ROUTING, separate router need to KEEP along with ESB for routing and filter expressions.
• Where as in 11g MEDIATOR contains routing rules and filter expressions itself. 

The Mediator is in charge of interconnecting, WITHIN an SOA composite application, components that expose DIFFERENT interfaces. In addition, the Mediator can perform duties such as filtering and making routing decisions. 

The composite editor in Jdeveloper gives you the FLEXIBILITY to define the interface now, to choose an existing interface, or to define the interface later as you wire components to the Mediator. 

TRANSFORMING data from one representation to another is, along with routing, one of the key functions of the Mediator.

The Mediator is in charge of interconnecting, within an SOA composite application, components that expose different interfaces. In addition, the Mediator can perform duties such as filtering and making routing decisions. 

The composite editor in Jdeveloper gives you the flexibility to define the interface now, to choose an existing interface, or to define the interface later as you wire components to the Mediator. 

Transforming data from one representation to another is, along with routing, one of the key functions of the Mediator.

• A URI is an identifier for some resource, but a URL gives you specific information as to obtain that resource. 
• A URI is a URL and as one commenter pointed out, it is now considered incorrect to use URL when describing applications. Generally, if the URL describes both the location and NAME of a resource, the TERM to use is URI. 
• Since this is generally the CASE most of us encounter EVERY day, URI is the correct term.

WEB SERVICES are application COMPONENTS, which are self-contained and self-describing and PROVIDE services BASED on the open protocol communication (i.e. SOAP UI, HTTP over the net). 

Web services are application components, which are self-contained and self-describing and provide services based on the open protocol communication (i.e. SOAP UI, HTTP over the net). 

Throw activity will EXPLICITLY throw the FAULT and this fault will get caught by the catch block and the CORRESPONDING actions will get EXECUTED. 

Throw activity will explicitly throw the fault and this fault will get caught by the catch block and the corresponding actions will get executed. 

• CUSTOM ERRORS 
• TIMED out errors 
• BPM errors 
• VALIDATION Errors

Scenario A: The BPEL CODE USES a fault-policy and a fault is handled using the “ora-human-intervention” ACTIVITY, then the fault is marked as Recoverable and the instance STATE is set to “Running”. 

Scenario B: The BPEL code uses a fault-policy and a fault is caught and re-thrown using the “ora-rethrow-fault” action, then the fault is marked as Recoverable and the instance state is set to “Faulted”; provided the fault is a recoverable one (like URL was not available).

Scenario A: The BPEL code uses a fault-policy and a fault is handled using the “ora-human-intervention” activity, then the fault is marked as Recoverable and the instance state is set to “Running”. 

Scenario B: The BPEL code uses a fault-policy and a fault is caught and re-thrown using the “ora-rethrow-fault” action, then the fault is marked as Recoverable and the instance state is set to “Faulted”; provided the fault is a recoverable one (like URL was not available).

YES, by SELECTING the Do not read file CONTENT check BOX in the JDEVELOPER wizard while configuring the "Read operation."

Yes, by selecting the Do not read file content check box in the Jdeveloper wizard while configuring the "Read operation."

When FILE has to be read in the mid of the BPEL process, then we will USE syncFileRead OPERATION, means some process should initiate the file read process and it is an outbound operation and process can’t BEGIN with Sync File read.

When file has to be read in the mid of the BPEL process, then we will use syncFileRead Operation, means some process should initiate the file read process and it is an outbound operation and process can’t begin with Sync File read.

When EVER the services returns the response in few seconds, it is RECOMMENDED to go for synchronous BPEL PROCESS if not the BPEL process should be Asynchronous the reason is calling APPLICATION can’t proceed further in case of synchronous process.

When ever the services returns the response in few seconds, it is recommended to go for synchronous BPEL process if not the BPEL process should be Asynchronous the reason is calling application can’t proceed further in case of synchronous process.

DURABLE:- It is long running PROCESS and initiated through a one-way invocation and do incur one or more dehydration points in the database during execution Ex: ASYNCHRONOUS 

Transient:- It is short-lived process, request-response STYLE processes and do not incur dehydration during their process execution Ex: Synchronous.

Durable:- It is long running process and initiated through a one-way invocation and do incur one or more dehydration points in the database during execution Ex: Asynchronous 

Transient:- It is short-lived process, request-response style processes and do not incur dehydration during their process execution Ex: Synchronous.

Property needs to be defined to START the new transaction or to CONTINUE with the same transactions 

Property NAME: Transaction and if this has value as required then the BPEL process will be CONTINUED in the same transaction where as if the value is defined as requiresnew then it will start the new transaction.

Property needs to be defined to start the new transaction or to continue with the same transactions 

Property Name: Transaction and if this has value as required then the BPEL process will be continued in the same transaction where as if the value is defined as requiresnew then it will start the new transaction.

By avoiding use of VARIOUS if STATEMENTS and using CHOOSE and by using for-each GROUP in PLACE of for-each.

By avoiding use of various if statements and using choose and by using for-each group in place of for-each.

Non- BLOCKING invoke is used when PARALLEL flow needs to be executed where NEW thread will be created for each invoke a activity and which will execute SIMULTANEOUSLY.

Non- blocking invoke is used when Parallel flow needs to be executed where new thread will be created for each invoke a activity and which will execute simultaneously.

If we have to SEND the request to different service which has the same wsdl then dynamic PARTNER link will be used and using addressing SCHEMA we can set the endpoint dynamic to send the request to the DESIRED service.

If we have to send the request to different service which has the same wsdl then dynamic partner link will be used and using addressing schema we can set the endpoint dynamic to send the request to the desired service.

PICK activity can ACT as a multiple receive activity in some business SCENARIOS. If we have two inbound operations and both can TRIGGER the bpel process then we will go with pick activity as we can’t have two receive activity with CREATE Instance box checked.

Pick activity can act as a multiple receive activity in some business scenarios. If we have two inbound operations and both can trigger the bpel process then we will go with pick activity as we can’t have two receive activity with create Instance box checked.

USING JAVA embedding activity in BPEL, Java CODE can be EMBEDDED in BPEL and can be used.

Using JAVA embedding activity in BPEL, Java code can be embedded in BPEL and can be used.

Activities like Pick, Wait, RECEIVE, reply and checkpoint() are called non-Idempotent activity and during the EXECUTION of the process whenever these activities are ENCOUNTERED then it GETS dehydrated to the DEHYDRATION store.

Activities like Pick, Wait, receive, reply and checkpoint() are called non-Idempotent activity and during the execution of the process whenever these activities are encountered then it gets dehydrated to the dehydration store.

Flow activity is USED, when parallel execution of the flow is needed and to use this PROPERTY “non blocking invoke should be SET as true “at the partner LINK level and no. of execution of parallel flow is defined and static. Where as in Flown the no. of execution of parallel flow is not static and it is determined during RUN time.

Flow activity is used, when parallel execution of the flow is needed and to use this property “non blocking invoke should be set as true “at the partner link level and no. of execution of parallel flow is defined and static. Where as in Flown the no. of execution of parallel flow is not static and it is determined during run time.

Pick activity picks the MESSAGES from SERVICE (Source) which has MULTIPLE operations or the BPEL process needs to receive the messages from multiple source SYSTEM. Pick activity should have at least on Message branch.

Pick activity picks the messages from service (Source) which has multiple operations or the BPEL process needs to receive the messages from multiple source system. Pick activity should have at least on Message branch.

In the clustered environment when the processing of the message should HAPPEN via only ONE SOA managed server, then the PROPERTY singleton needs to be defined at the ADAPTER level.

In the clustered environment when the processing of the message should happen via only one SOA managed server, then the property singleton needs to be defined at the adapter level.

In the clustered environment, FILE and FTP adapters should be used as HA (High-Availability) 

Inbound: It is controlled by Control Files and avoids the race between the MANAGES servers in reading the files where the reference of the files read by the managed servers will be maintained in the control directory. 

Outbound: It is controlled by DB Mutex table exist in the SOA dehydration STORE and this avoids DUPLICATED been written to the same file when all the managed servers in the clusters process the same messages.

In the clustered environment, File and FTP adapters should be used as HA (High-Availability) 

Inbound: It is controlled by Control Files and avoids the race between the manages servers in reading the files where the reference of the files read by the managed servers will be maintained in the control directory. 

Outbound: It is controlled by DB Mutex table exist in the SOA dehydration store and this avoids duplicated been written to the same file when all the managed servers in the clusters process the same messages.

We will DIRECTLY deploy the XSLT,
options: - 
Using ANT SCRIPT by file REPLACEMENT in TMP folder.
By CREATING a folder in BPEL PM Installation folder and specifying its location in our BPEL code with http call and replacing our xslt to that location.

We will directly deploy the XSLT,
options: - 
Using ANT script by file replacement in TMP folder.
By creating a folder in BPEL PM Installation folder and specifying its location in our BPEL code with http call and replacing our xslt to that location.

When accessing the SERVICES should be restricted to the group,then service should be secured VIA WSM (WEB service Manager).

When accessing the services should be restricted to the group,then service should be secured via WSM (Web service Manager).

An XA transaction involves a coordinating transaction MANAGER, with one or more databases (or other RESOURCES, like JMS) all involved in a SINGLE global transaction. Non-XA transactions have no transaction coordinator, and a single resource is doing all its transaction work itself (this is sometimes called local transactions).

An XA transaction involves a coordinating transaction manager, with one or more databases (or other resources, like JMS) all involved in a single global transaction. Non-XA transactions have no transaction coordinator, and a single resource is doing all its transaction work itself (this is sometimes called local transactions).

OSB is the light-weight service bus wherever there is not much business logic involves and there is NEED to just GET the message routed between the systems OSB is used where as when there is more business logic involves in the process, then BPEL will be used.

OSB is the light-weight service bus wherever there is not much business logic involves and there is need to just get the message routed between the systems OSB is used where as when there is more business logic involves in the process, then BPEL will be used.

Oracle SOA Suite provides SUPPORT for Decision components that support Oracle BUSINESS Rules. A Decision component is a MECHANISM for publishing rules and rule sets as a reusable service that can be invoked from multiple business processes. These rules can be changed without redeploying the CODE.

Oracle SOA Suite provides support for Decision components that support Oracle Business Rules. A Decision component is a mechanism for publishing rules and rule sets as a reusable service that can be invoked from multiple business processes. These rules can be changed without redeploying the code.

Dehydration STORE is the database where the instances GET stored when it GETS dehydrated by the process on the OCCURRENCE of non-idempotent activities and also stores the information on the LONG running processes.

Dehydration store is the database where the instances get stored when it gets dehydrated by the process on the occurrence of non-idempotent activities and also stores the information on the long running processes.

XREF: It is DYNAMIC SINCE the values to the XREF can be populated dynamically and it is stored in XREF_DATA table in SOA DEHYDRATION store. 

DVM:- Domain Value Map is STATIC mappings between a source and target system which can be used in transformations.

XREF: It is dynamic since the values to the XREF can be populated dynamically and it is stored in XREF_DATA table in SOA Dehydration store. 

DVM:- Domain Value Map is static mappings between a source and target system which can be used in transformations.

DVM-Domain Value Map is static mappings between a source and TARGET system which can be USED in transformations. The value can be changed via SOA COMPOSER.

DVM-Domain Value Map is static mappings between a source and target system which can be used in transformations. The value can be changed via SOA composer.

Generally a service bus is used for ENDPOINT virtualization and in 11g stack; Oracle Service Bus (OSB) is the primary service bus. In exposed PROXY's message flow, it can route the request to any of your environment's ACTUAL (physical) service on the basis of whatever logic.

Mediator can also be used to EXPOSE the service and in mediator routing rule, it can be routed to actual service.

Generally a service bus is used for endpoint virtualization and in 11g stack; Oracle Service Bus (OSB) is the primary service bus. In exposed proxy's message flow, it can route the request to any of your environment's actual (physical) service on the basis of whatever logic.

Mediator can also be used to expose the service and in mediator routing rule, it can be routed to actual service.

Service-Oriented Architecture (SOA) GOVERNANCE is a concept used for activities related to exercising control over services in an SOA.

Some key activities that are often mentioned as being PART of SOA governance are: 

Managing the PORTFOLIO of services: This includes planning development of new services and updating current services.

Managing the service lifecycle: This is meant to ensure that updates of services do not disturb current services to the consumers.

Using policies to restrict behavior: Consistency of services can be ensured by having the rules applied to all the created services.

Monitoring performance of services: The CONSEQUENCES of service downtime or underperformance can be severe because of service composition. Therefore ACTION can be taken instantly when a problem occurs by monitoring service performance and availability.

Service-Oriented Architecture (SOA) governance is a concept used for activities related to exercising control over services in an SOA.

Some key activities that are often mentioned as being part of SOA governance are: 

Managing the portfolio of services: This includes planning development of new services and updating current services.

Managing the service lifecycle: This is meant to ensure that updates of services do not disturb current services to the consumers.

Using policies to restrict behavior: Consistency of services can be ensured by having the rules applied to all the created services.

Monitoring performance of services: The consequences of service downtime or underperformance can be severe because of service composition. Therefore action can be taken instantly when a problem occurs by monitoring service performance and availability.

Yes it is possible. 

To automatically maintain long-running asynchronous processes and their current state INFORMATION in a database while they wait for asynchronous callbacks, you use a database as a dehydration store. Storing the process in a database PRESERVES the process and prevents any loss of state or reliability if a system SHUTS down or a network problem occurs. This feature increases both BPEL process reliability and scalability. You can also use it to support clustering and FAILOVER.

Yes it is possible. 

To automatically maintain long-running asynchronous processes and their current state information in a database while they wait for asynchronous callbacks, you use a database as a dehydration store. Storing the process in a database preserves the process and prevents any loss of state or reliability if a system shuts down or a network problem occurs. This feature increases both BPEL process reliability and scalability. You can also use it to support clustering and failover.

For the transaction TIMEOUT needs to be INCREASED, all the below SETTINGS timeout value needs to be changed to the expected Timeout value. 

1. JTA 
2. ENGINE Bean 
3. Delivery Bean 

For the transaction timeout needs to be increased, all the below settings timeout value needs to be changed to the expected Timeout value. 

The sequences of EVENTS involved in the delivery of invoke messages is as follows: 

• The client posts the message to the delivery service. 
• The delivery service saves the invocation message to the dlv_message table. The initial state of the message is 0 (undelivered). 
• The delivery service schedules a dispatcher message to process the invocation message asynchronously. 
• The dispatcher message is delivered to the dispatcher through the afterCompletion() call. Therefore, the message is not delivered if the JTA transaction fails. 
• The dispatcher sends the JMS message to the queue. PLACES a very SHORT JMS message in the in-memory queue (jms/collaxa/BPELWorkerQueue) in OC4J JMS. The small JMS message triggers the Worker Bean in the downstream step. 
• This message is then picked up by a Worker Bean MDB, which requests the dispatcher for work to execute. If the number of Worker Bean MDBs currently processing activities for the domain is sufficient, the dispatcher module may decide not to request another MDB. 
• MDB fetches the invocation message from the dispatcher. 
• MDB passes the invocation message to Oracle BPEL Server, which updates the invocation message state to 1 (delivered), creates the instance, and executes the activities in the flow until a breakpoint activity is reached.

The sequences of events involved in the delivery of invoke messages is as follows: 

Receiver THREADS property specifies the maximum NUMBER of MDBs that process Async ACROSS all domains. Whereas the dspMaxThread are the maximum number of MDBs that process Async and threads that operate across a domain. So, we need to ENSURE that the dspMaxThread value is not greater than Receiver Threads.

Receiver Threads property specifies the maximum number of MDBs that process Async across all domains. Whereas the dspMaxThread are the maximum number of MDBs that process Async and threads that operate across a domain. So, we need to ensure that the dspMaxThread value is not greater than Receiver Threads.