If you're looking for Oracle WebCenter Interview Questions for Experienced or Freshers, you are at the right place. There are a lot of opportunities from many reputed companies in the world. According to research, Oracle WebCenter has a market share of about 0.1%.
So, You still have the opportunity to move ahead in your career in Oracle WebCenter Analytics. Mindmajix offers Advanced Oracle WebCenter Interview Questions 2021 that help you in cracking your interview & acquire a dream career as an Oracle WebCenter Analyst.
Oracle WebCenter Portal provides design time and runtime tools for building enterprise portals, transactional websites, and social networking sites. It provides portal-specific features such as page hierarchies, navigation models, delegated security, customization, and others.
Portals can also include features like portlets, content management system integration, personalization, social computing services, search, analytics, etc.
A pagelet is a reusable user interface component similar to a portlet, but while portlets were designed specifically for portals, pagelets can be run on any web page, including within a portal or other web application.
Oracle composer provides a runtime editing tool that enables business users to edit application pages.
Panel customizable, Show Detail Frame, Custom Actions, Layout Customizable.
MDS or Metadata Repository is the repository for metadata of certain deployed applications. When the user commits run-time changes, they are stored and deploys an MDS on the server.
|If you want to enrich your career and become a professional in Oracle WebCenter, then visit Mindmajix - a global online training platform: "Oracle WebCenter Training" This course will help you to achieve excellence in this domain.|
JCR or Java Content Repository API adapters enable users to access data stored in content management systems, such as Oracle WebCenter Content, Oracle Portal, or even your file system, available to your application.
PortalWebAssets is used to separate all the static resources in the application like HTML, image files, etc.
Yes, It can be renamed.
No, if the developer does not configure the security in WebCenter, the ADF security gets configured by default. As part of this, a default username/password is automatically created. Also, it also provides default Login and Logout pages.
If the application contains run-time customizations using MDS, it must be bundled as an EAR. For a simple WebCenter portal application with no such customizations, WAR can be created.
This file is used for defining the permissions and privileges for various groups of users on various task flows created in the application.
The identity Store is used to store information about users and groups while the Policy Store is used to store information about security policies.
The DataBindings.cpx file contains the Oracle ADF binding context for your entire application and provides the metadata from which the Oracle ADF binding objects are created at runtime. The DataControls.dcx file is created when you register data controls on the business services.
This file is not generated for Oracle ADF Business Components. It identifies the Oracle ADF model layer data control classes(factory classes) that facilitate the interaction between the client and the available business service.
trinidad. the config file is created when you create a WebCenter portal application. This is used to register the skin-family you are going to use for your entire application.
Trinidad. skins are used when we use the skin as a Jar file. This file provides a mapping between the Skin Id and the actual path where the skin exists.
Binding context is a runtime map between the data controls and page definition of pages in the application which is used to access the binding layer. It is accessible through the EL expression in your jspx pages. The binding container is a request-scoped map that is used to instantiate the page bindings.
This is accessible through the EL expressions. Also, since it is a request-scoped map, it is accessible during every page request.
|Related Article: Oracle WebCenter Tutorial|
ADF contains the following types of bindings:
Actions are designed for business logic and participate in navigation handling, whereas action listeners typically perform user interface logic and do not participate in navigation handling.
Action listener is a class that wants to be notified when a command component fires an action event.
A view-state allocates a new viewScope when it enters. This scope may be referenced within the view-state to assign variables that should live for the duration of the state. This scope is useful for manipulating objects over a series of requests from the same view.
The visible property is set to true/false based on the requirement whether we want to see the field on the page or not at run time. The field or component still exists on the page, though hidden. The render property is used to conditionally load the component based on criteria.
We define custom pagination in ADF by creating a custom table as a task flow using the af:iterator tag. This renders the collection of data just as a table renders it. Now we bind the value property of the iterator to the collection model from ADF bindings declaration and set the number of visible rows to, say 15.
Validators and Convertors are used to provide conversion and validation capabilities to the ADF input components respectively.
Converters convert the values on ADF forms to the type in which the application accepts them after the values are edited on the form and submitted. Validators are used to impose validations on the input components.
Restore View: The request comes to the FacesServet controller which extracts the view from this request.
Apply request values: The purpose of the apply request values phase is for each component to retrieve its current state. The components must first be retrieved or created from the FacesContext object, followed by their values.
Process validations: This phase makes use of the validators to validate the validation rules on the fields.
Update model values: In this phase, JSF updates the actual values of the server-side model, by updating the properties of your backing beans.
Invoke application: Here the JSF controller invokes the application action to handle Form submissions.
Render response: In this phase, JSF displays the view with all of its components in their current state.
When immediate is true on a button, the command’s action and ActionListeners, including the default ActionListener provided by the JavaServer Faces implementation, will be executed during the Apply Request Values phase of the request processing lifecycle, rather than waiting until the Invoke Application phase.
In the case of a text field, by default, values are converted and validated together in the Process Validators phase.
However, if you need access to the value of a component during Apply Request Values – for example, if you need to get the value from an actionListener on an immediate commandButton – then setting this to “immediate” makes that possible.
Inter-portlet communication is achieved when an action in one portlet triggers a response in the second portlet. It's a communication bridge between two portlets.
For eg, one portlet contains a checkbox containing a list of products. When I choose a product from the list and click on submit, the other portlet displays the details of the respective product.