Oracle WebCenter Test

You can enable this during the Gadgets application installation process. ✘ By changing the cs_site property in GadgetsApplication.xml ✘ By changing the cs_site property in futuretense_xcel.ini file ✘ By defining/editing cs_site property from Admin application of Admin Site ✔

Oracle Database Oracle WebLogic Server Oracle Coherence Oracle Identity Manager Oracle WebCenter Content

manually approving the asset with a SQL script using the "Approve Multiple Assets" option for the Publish destination manually approving by clicking the Approve icon on the asset toolbar when the asset is in workflow, where the final step is approval configuring the publish destination for Auto-Approve

Pagelet authentication Support for vanity URLs Detailed page fragment analytics Built-in 404 response for deleted assets

cold backup of the database schema backup of the WebCenter Sites shared file system backup of the WebCenter Sites web applications backup of the Webserver configuration files

an Records Management solution with smart WYSIWYG authoring, a preview environment, and publication workflows ✘ a Content Management System (CMS) that is complete with a delivery platfom, to manage multiple business sites ✘ a .NET development platform with a high performance caching architecture ✘ a commerce site management solution to deliver multichannel, multibrand, and multilingual websites ✔

Community widgets or Gadgets cannot be deployed on any web pages in any domain. ✘ Community widgets or Gadgets can be deployed on any web pages in any domain. ✘ Community widgets or Gadgets can be deployed on any web pages in the same domain in which the Community-Gadgets production application is running. ✘ Community widgets or Gadgets can be deployed only on web pages in the same domain in which the WebCenter Sites production application is running. ✔

Page Attribute Editor Start Menu Page Definition Workflow Process

create an external dependency for the element ✘ create a SiteEntry for the element ✘ add the tag to the element ✘ add the tag to the element ✔

Flex asset types are part of an asset type structure called a flex family and therefore, can be made up of a pool of attribute assets for that flex family. A flex family can have only one flex asset type. The parent asset values inherited by a flex asset are stored in one of the flex asset type tables instead of the parent asset type tables. Attribute data is stored in records instead of columns in the database table so that they can be changed without editing the structure of the database table. Attribute editors and flex filters can be used but not named associations.