Explore topic-wise InterviewSolutions in .

Primarily we have three types of BPEL template in SOA Suite TOOL.

1. Synchronous BPEL Template
2. ASYNCHRONOUS BPEL Template
3. OneWay BPEL Template

Primarily we have three types of BPEL template in SOA Suite tool.

Below are different parts of BPEL as mentioned below.

1. Service Interface: A WSDL describing the functionality of the BPEL process. The service interface provides the end user a way to interact with the BPEL process component using Service Interface / Service Binding.
2. Activities: units of WORK. The actual elements that MAKE up the BPEL process FLOW or sequence of instructions to be executed.
3. Partner links: also called Reference bindings. A partner link describes the roles played for the interaction between the BPEL process and the service it invokes.

Below are different parts of BPEL as mentioned below.

BPEL stands for Business Process Execution LANGUAGE, it is one of the component of SOA SUITE TOOL. BPEL is a XML based language used to DESIGN business process/flows. We perform service orchestration in BPEL.

BPEL stands for Business Process Execution Language, it is one of the component of SOA Suite tool. BPEL is a XML based language used to design business process/flows. We perform service orchestration in BPEL.

CONNECTION between service & binding component and WITHIN service & binding components KNOW as wire. I.e. This ENABLE US to graphically connect the components in a SOA composite application.

Connection between service & binding component and within service & binding components know as wire. I.e. This enable us to graphically connect the components in a SOA composite application.

Composite needs to send the MESSAGE to first target by JMS queue and to other target by WRITING the file, in this SCENARIO we have TWO exist for composite.

Composite needs to send the message to first target by JMS queue and to other target by writing the file, in this scenario we have two exist for composite.

When a composite can be INITIATED either by direct call or by consuming the same MESSAGE from JMS QUEUE, in this scenario we have two entry point for same composite.

When a composite can be initiated either by direct call or by consuming the same message from JMS queue, in this scenario we have two entry point for same composite.

Yes, we can more than one SERVICE & reference binding in one COMPOSITE, that means we can have more than one entry & EXIST point for composite.

Yes, we can more than one service & reference binding in one composite, that means we can have more than one entry & exist point for composite.

Binding components are of TWO types as mentioned below.

1. Service Binding : With the help of this binding we connect COMPOSITE to SOURCE or client system or we can say this is entry point of composite.
2. Reference Binding: This binding helps composite to connect to target or reference systems or we can say it is EXIST point of the composite.

Binding components are of two types as mentioned below.

As name SUGGEST, this COMPONENT is used to bind composite application to EXTERNAL world. i.e. we use these COMPONENTS to LINK composite with source and target system.

As name suggest, this component is used to bind composite application to external world. i.e. we use these components to link composite with source and target system.

Each SERVICE component is HOSTED in its own service engine CONTAINER. E.g. Any logic added in BPEL COMPONENTS will be handled by BPEL service engine only.

Each service component is hosted in its own service engine container. E.g. Any logic added in BPEL components will be handled by BPEL service engine only.

yes, we can have as MANY as SERVICE components in one COMPOSITE but it is not RECOMMENDED, we should not have all the components in one composite itself.

yes, we can have as many as service components in one composite but it is not recommended, we should not have all the components in one composite itself.

All prebuilt components BPEL , Mediator, BUSINESS RULES, HUMAN Task and Spring known as service components.

All prebuilt components BPEL , Mediator, Business Rules, Human Task and Spring known as service components.

SOA composite is a assembly comprises of one or more than one pre-build components. In SOA composite we WIRES different components TOGETHER to perform REQUIRED business functionality.

SOA composite is a assembly comprises of one or more than one pre-build components. In SOA composite we wires different components together to perform required business functionality.

1. Easier Development :No NEED to write lengthy code as we get all COMPONENTS prebuilt.
2. Easily COMPOSE a assembly (composite) by just linking DIFFERENT these prebuilt components.
3. Better re-usability

We cannot be sure that the data will be persistent throughout in Memstore. ASSUME that a PARTICULAR datanode is down. Then the data that resides on that data node’s memory will be LOST.

To OVERCOME this problem, when the request comes from the master it written to WAL as well. WAL is nothing but Write Ahead Logs which resides on the HDFS, a permanent storage. Now we can make sure that even when if the data node is down the data will not be lost I.e. we have the copy of all the ACTIONS that you are supposed to do in the WAL.

We cannot be sure that the data will be persistent throughout in Memstore. Assume that a particular datanode is down. Then the data that resides on that data node’s memory will be lost.

To overcome this problem, when the request comes from the master it written to WAL as well. WAL is nothing but Write Ahead Logs which resides on the HDFS, a permanent storage. Now we can make sure that even when if the data node is down the data will not be lost I.e. we have the copy of all the actions that you are supposed to do in the WAL.

The MemStore is a write BUFFER where HBase accumulates data in memory before a permanent write.

Its contents are flushed to DISK to form an HFile when the MemStore fills up.It doesn’t write to an EXISTING HFile but instead forms a new file on every FLUSH. There is ONE MemStore per column family.

The MemStore is a write buffer where HBase accumulates data in memory before a permanent write.

Its contents are flushed to disk to form an HFile when the MemStore fills up.It doesn’t write to an existing HFile but instead forms a new file on every flush. There is one MemStore per column family.

HBase comes integrated with Zoo keeper. When I start HBase, Zoo keeper instance is also started. The reason is that the Zoo keeper helps us in keeping a track of all region servers that are there for HBase. Zoo keeper keeps track of how many region servers are there, which region servers are holding from which DATA node to which data node. It keeps track of smaller data SETS where Hadoop is missing out. It decreases the overhead on top of Hadoop which keeps track of most of your META data. Hence HMaster gets the DETAILS of region servers by actually contacting Zoo keeper.

HBase comes integrated with Zoo keeper. When I start HBase, Zoo keeper instance is also started. The reason is that the Zoo keeper helps us in keeping a track of all region servers that are there for HBase. Zoo keeper keeps track of how many region servers are there, which region servers are holding from which data node to which data node. It keeps track of smaller data sets where Hadoop is missing out. It decreases the overhead on top of Hadoop which keeps track of most of your Meta data. Hence HMaster gets the details of region servers by actually contacting Zoo keeper.

If we have MULTIPLE composites with same NAME then only ONE composite will act as DEFAULT composite which will run only. But we can GO to EM console and make other composite default.

If we have multiple composites with same name then only one composite will act as default composite which will run only. But we can go to EM console and make other composite default.

Yes, we can have MULTIPLE COMPOSITES with same NAME on SOA server but this is possible when we have composites with REVISIONS.

Yes, we can have multiple composites with same name on SOA server but this is possible when we have composites with revisions.

Config plan is used during COMPOSITE DEPLOYMENT. This is a XML file where we SPECIFY the PARAMETERS that we want to replace while doing the deployment to next environment.

Config plan is used during composite deployment. This is a xml file where we specify the parameters that we want to replace while doing the deployment to next environment.

There are different METHODS to deploy SOA composite to SOA server.

1. Through EM console
2. Directly from JDeveloper
3. Scripting (Ant, WLST ETC.)

There are different methods to deploy SOA composite to SOA server.

We can perform below OPERATIONS.

1. START all composites
2. SHUT down all composites
3. Undeploy all composites
4. Retire all composites
5. Activate all composites
6. List all composites

We can perform below operations.

Below are the major benefits of partition.

1. Logically GROUP SOA composites.
2. PERFORM bulk LIFECYCLE management tasks on LARGE numbers of composites.

Below are the major benefits of partition.

Sections of the SOA Infrastructure where we deploy SOA composite applications known as partition. When we INSTALL SOA SUITE tool, default partition GET created with name “default” but we can add as many as PARTITIONS as required.

Sections of the SOA Infrastructure where we deploy SOA composite applications known as partition. When we install SOA suite tool, default partition get created with name “default” but we can add as many as partitions as required.

We require following schema.

1. MDS – This schema is used to STORE all the ARTIFACTS like WSDL, XML, XSD etc.
2. SOA_INFRA – This schema is used to store SOA Component Engine properties, DEPLOYED composites, payloads, runtime metadata etc.
3. ORABAM – This schema is used to store the metadata that is related to BAM and its components and this is optional schema.
4. ORASDPM – This schema is used to store metadata about the USER messaging systems.

We require following schema.

soa-infra is a J2EE application that is TARGETED to EITHER a MANAGED SERVER or a cluster. All the composites gets DEPLOYED under soa-infra application.

soa-infra is a J2EE application that is targeted to either a managed server or a cluster. All the composites gets deployed under soa-infra application.

EM STANDS for Enterprise Manager. It is WEBPAGE we deploy, TEST, monitor, DIAGNOSE and resolve problem for composites. It is hosted on the Admin Server.

EM stands for Enterprise Manager. It is webpage we deploy, test, monitor, diagnose and resolve problem for composites. It is hosted on the Admin Server.

Cluster is a GROUP of server instances that WORK together as a single runtime UNIT from a client perspective. Clustering provides scalability and HIGH AVAILABILITY for applications.

Cluster is a group of server instances that work together as a single runtime unit from a client perspective. Clustering provides scalability and high availability for applications.

All other WLS instances in a domain are called Managed SERVERS. Managed servers HOST APPLICATION COMPONENTS and resources.

All other WLS instances in a domain are called Managed Servers. Managed servers host application components and resources.

A domain has one WLS instance CONFIGURED as an ADMIN server. The admin server provides a CENTRAL point for MANAGING a domain.

A domain has one WLS instance configured as an admin server. The admin server provides a central point for managing a domain.

A DOMAIN is the basic administration unit for WEBLOGIC Server instances. i.e. Domains include a special WebLogic Server INSTANCE called the Administration Server, which is the central point from which you CONFIGURE and manage all resources in the domain.

A domain is the basic administration unit for WebLogic Server instances. i.e. Domains include a special WebLogic Server instance called the Administration Server, which is the central point from which you configure and manage all resources in the domain.

We use JDEVELOPER IDE for ORACLE SOA suite TOOL.

We use JDeveloper IDE for Oracle SOA suite tool.

Mostly WebLogic SERVER is USED as application server for ORACLE SOA SUITE tool.

Mostly WebLogic server is used as application server for Oracle SOA Suite tool.

FOLLOWING components needs to be installed before we install Oracle SOA Suite.

1. JDK
2. Database
3. All Required Schema (Created using RCU)
4. WEBLOGIC SERVER

Following components needs to be installed before we install Oracle SOA Suite.

We have TOTAL 5 components in Oracle SOA Suite TOOL as mentioned below.

1. BPEL : Business Process Execution Language
2. Mediator
3. Business RULES
4. Human Task
5. Spring

We have total 5 components in Oracle SOA Suite tool as mentioned below.

YES SOA Suite TOOL is a state FULL tool, that means in this tool we store every state in database i.e. we store all the incoming messages, TRANSFORMED messages, OUTGOING messages to database along with timestamp.

Yes SOA Suite tool is a state full tool, that means in this tool we store every state in database i.e. we store all the incoming messages, transformed messages, outgoing messages to database along with timestamp.

SOA Suite tool is a middleware tool from ORACLE which is based upon SOA concept comes under Oracle Fusion Middleware stack. We use this tool for integration PURPOSE .i.e. This tool is USED to integrate TWO system/applications etc.

SOA Suite tool is a middleware tool from Oracle which is based upon SOA concept comes under Oracle Fusion Middleware stack. We use this tool for integration purpose .i.e. This tool is used to integrate two system/applications etc.

Below are the major BENEFITS that we get from SOA.

1. Loose Coupling : This means that the service requester has no knowledge of the TECHNICAL details of the provider’s implementation, such as the PROGRAMMING language, deployment platform, and so forth. The service requester typically invokes operations by way of messages — a request message and the response — rather than through the USE of APIS or file formats.
2. Cost Cutting
3. Better reuse: Build new client functionality on top of existing Business Services.
4. Well defined interfaces: Make changes without affecting clients
5. Easier to maintain : Changes/Versions are not all-or-nothing
6. Better flexibility

Below are the major benefits that we get from SOA.

SOA stands for Service Oriented Architecture. SOA is not any tool, rather is a concept and there are many tools in the market BASED upon this concept. In this SOA Concept, we use SOA layer as MIDDLE or INTERMEDIATE layer between services so that these service can communicate with each other.

SOA stands for Service Oriented Architecture. SOA is not any tool, rather is a concept and there are many tools in the market based upon this concept. In this SOA Concept, we use SOA layer as middle or intermediate layer between services so that these service can communicate with each other.