15 October, 2020
Ans: File-Based & DB Based.
Ans: WSDL stands for Web Services Description Language
WSDL is a document written in XML. The document describes a Web service. It specifies the location of the service and the operations (or methods) the service exposes.
Ans: SOAP is a simple XML-based protocol to let applications exchange information over HTTP.
Ans: Transactional & Non- Transactional Adapter
Ans: An XML Schema describes the structure of an XML document.
Ans: <schema xmlns="http://www.w3.org/2001/SchemaXML targetNamespace="http://www.example.com/name" xmlns:target="http://www.example.com/name">
The targetNamespace declares a namespace for other xml and xsd documents to refer to this schema. The target prefix in this case refers to the same namespace and you would use it within this schema definition to reference other elements, attributes, types, etc. also defined in this same schema definition.
Ans: We usually keep Abstract WSDL’s only in MDS.
Ans: The idea behind file-based repositories is to allow developers to have a light repository available in their local environment that can be easily adapted for development and tests; a file-based repository relieves developers of having to configure and maintain an external database while providing necessary functionality, such as file referencing and customizations. These kinds of repositories are easily modified and maintained since they define a directory structure like any other directory structure inside an operating system. They can be navigated and altered using common shell commands or any kind of visual file explorer application. The file-based repository is usually located inside the Oracle JDeveloper home (JDEV_HOME/integration) if the default configuration is used.
Ans: This is a feature of Oracle File and FTP Adapters that uses an invoke activity within a while loop to process the target file. This feature enables you to process arbitrarily large files.
If an invalid payload is provided, then ChunkedRead scenarios do not throw an exception. When a translation exception (bad record violating the NXSD specification) is encountered, the return header is populated with the translation exception message that includes details such as line and column where the error occurred. All translation errors do not result in a fault. These errors are manifested as a value in the return header. You must check the jca.file.IsMessageRejected and jca.file.RejectionReason header values to ascertain whether an exception has occurred. Additionally, you can also check the jca.file.NoDataFound header value.
Ans: The Oracle File and FTP Adapters support polling multiple directories within a single activation. You can specify multiple directories in JDeveloper as opposed to a single directory. This is applicable to both physical and logical directories.
Ans: Database-based repositories are used in production environments where robustness is needed. These repositories are created using the Repository Creation Utility (RCU) application from Oracle. This utility helps with the creation of a new database schema with its corresponding tables and objects. Repositories can later be registered or deregistered via the Oracle Enterprise Manager Fusion Middleware Control console.
Ans: The adf-config.xml file is a configuration file that is used to store MDS Configurations.
Ans: Oracle Mediator provides a lightweight framework to mediate between various components within a composite application. Oracle Mediator converts data to facilitate communication between different interfaces exposed by different components that are wired to build an SOA composite application.
Ans: OWSM stands for Oracle Web Service Manager. Oracle Web Services Manager offers a comprehensive and easy-to-use solution for policy management and security of service infrastructure. It is a standalone platform for securing and managing access to web services.
Ans: The purpose of the echo option is to expose all the Oracle Mediator functionality as a callable service without having to route it to any other service. For example, you can call an Oracle Mediator to perform a transformation, a validation, or an assignment, and then echo the Oracle Mediator back to your application without routing it anywhere else.
For synchronous operations with a conditional filter, the echo option does not return a response to the caller when the filter condition is set to false. Instead, it returns a null response.
The echo option is available for asynchronous operations only if the Oracle Mediator interface has a callback operation. In this case, the echo is run on a separate thread.
Ans: Yes, we can create custom OWSM policies.
Ans: Schematron is an XML schema language, and it can be used to validate XML contents in an XML payload.
Ans: Read is used when Polling is required to be done while SyncRead is used when you need to read the file in between the flow i.e you want to have asynchronous communication.
Ans: By using getFaultAsString() function.
Ans: Parallel rules only.
Ans: Only One
Ans: Mediator has only one standard fault.
Inclined to build a profession as Oracle SOA Admin?
Then here is the blog post on, explore
Ans: When a file contains multiple messages, you can choose to publish messages in a specific number of batches. This is referred to as debating. During debatching, the file reader, on a restart, proceeds from where it left off in the previous run, thereby avoiding duplicate messages. File debatching is supported for files in XML and native formats.
Ans: Below is the list of Standard Faults in BPEL.
Ans: There are so many changes in oracle SOA 11g when compared to oracle SOA 10g in business and technology and some new functionality added
In Oracle SOA 11g contains Service Component Architecture whereas Oracle SOA 10g having no Service Component Architecture.
ORACLE SOA Suite 10g is based on Oracle AS 10g
In SOA 10g having ESB Console, BPEL Console, Application Server Control these are all individual and not well integrated.
In SOA 11g Provides service monitoring across all SOA Components Such as ESB, BPEL, Human Workflow
SOA Suite 11g has the Enterprise Management Console me a console is used for Manage SOA Suite Services, Manage SOA Suite Deployment, Review Logs, and Exceptions.
SOA Suite 11g Components
Read more of Difference B/W Oracle SOA 10g and Oracle SOA 11g
Ans: Yes, we can apply one policy to all composites in one domain using policy sets.
The <xsl: import> element is a top-level element that is used to import the contents of one style sheet into another.
Note: This element must appear as the first child node of <xsl:stylesheet> or <xsl:transform>.
Syntax: <xsl:import href="URI"/>
Ans: Call-template works similarly to the apply-templates element in XSLT. Both attach a template to specific XML data. This provides formatting instructions for the XML. The main difference between the two processes is the call function only works with a named template. You must establish a 'name' attribute for the template in order to call it up to format a document.
<?xml version="1.0"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> < xsl:call-template name="myTemplate"> < !-- Content: xsl --> < /xsl:call-template> < stylesheet>
Ans: By default, polling by inbound Oracle File and FTP Adapters start as soon as the endpoint is activated. However, if you want more control over polling, then you can use a file-based trigger. Once the Oracle File or FTP Adapter finds the specified trigger file in a local or remote directory, it starts polling for the files in the inbound directory.
For example, a BPEL process is writing files to a directory and a second BPEL process is polling the same directory for files. If you want the second process to start polling the directory only after the first process has written all the files, then you can use a trigger file. You can configure the first process to create a trigger file at the end. The second process starts polling the inbound directory once it finds the trigger file.
Ans: This activity waits for the occurrence of one event in a set of events and performs the activity associated with that event. The occurrence of the events is often mutually exclusive (the process either receives an acceptance or rejection message, but not both). If multiple events occur, the selection of the activity to perform depends on which event occurred first. If the events occur nearly simultaneously, there is a race and the choice of activity to be performed is dependent on both timing and implementation.
Non-XA (Local Transaction): It involves only one resource. When you use Non-XA transactions then you can’t involve multiple resources (different databases, Queues, application servers, etc), you can rollback or commit transactions for only one resource. There is no transaction manager for this transaction as we are dealing with only one resource at a time.
XA (Global Transaction): It involves more than one resource (different databases, queues, application servers) all participate in one transaction. It uses two-phase commit to ensure that all resources either all commit or rollback any particular transaction. When you have a scenario like you need to connect to two different databases, JMS Queue and application server, in this case, you will use XA transaction that means all resources participate in one transaction only.
Ans: Transactional & Non- Transactional Adapter
Ans: Inline schemas are XML schema definitions included inside XML instance documents. Like external schema documents, inline schemas can be used to validate that the instance matches the schema constraints.
TekSlate is the best online training provider in delivering world-class IT skills to individuals and corporates from all parts of the globe. We are proven experts in accumulating every need of an IT skills upgrade aspirant and have delivered excellent services. We aim to bring you all the essentials to learn and master new technologies in the market with our articles, blogs, and videos. Build your career success with us, enhancing most in-demand skills .