This article introduces the architecture of the Oracle WebCenter Content Server. In particular, we will discuss the BrowserUrlPath component and the EncodeHtml Idoc Script function. This feature is enabled by default for discussions in the Threaded Discussions component. This article will also cover the various options available for filtering data input. The next section of this article explains the different settings for the HtmlDataInputFilterLevel configuration variable.
Powered by Idocscript com
A web content server is a central repository for all types of content, including both structured and unstructured content. With the Oracle WebCenter Content Server, content owners can easily manage and share content with contributors. The architecture is based on web content management and allows for a unified experience across a variety of business users and devices. The Oracle WebCenter Content Server manages all phases of the content lifecycle.
Idoc Script is a server-side custom scripting language that is used for presentation of HTML templates and configuration settings. This language uses a set of server-side variables, which are often called configuration variables. These variables are stored in the server’s configuration files. The Idoc Script language is the preferred programming language of Oracle WebCenter Content. This technology has the highest level of integration with other content management systems, such as Microsoft SharePoint Server and Adobe Flash.
Inbound Refinery enables the creation of thumbnails for files that are checked into the Content Server. It manages file conversions at the input side of the system. Then, you can create thumbnails by using the Outside In Image Export feature, which converts files to multiple-page TIFF files. It is important to install and configure Inbound Refinery properly to be able to use the Content Server.
Personalization functions refer to user properties defined in the personalization file. The user topic file, which is located in the directory WC_CONTENT_ORACLE_HOME/data/users/profiles/us/username, is used for personalization. Conditionals enable if and else clauses, and you can also use variable names and functions in these conditions.
In addition to the iDocScript and Java API, Content Server supports many legacy and business document types, including HTML. It also supports the full suite of SOAP web services. It is compatible with many programming languages, including Java API, JSP, ASP, and COM. This allows you to use existing taxonomies or develop your own based on your unique needs.
A content server uses multiple technologies, and customizations require experience in several of them. Depending on the customization required, technical skills vary, but many can be accomplished by someone with a basic knowledge of HTML and Idoc Script. If you’re not familiar with Java, it’s also possible to customize the product using VBScript, C++, or Visual Basic. However, most customizations can be performed using a standard text editor.
Dynamic data pages are a powerful part of the Content Server architecture. Dynamic data resources are used to display different types of data to users based on their context. Dynamic data resources can be defined in any resource file and are mapped into the database by Content Server code. Besides that, dynamic data resources can also be used in idocscript pages. They can be used in error messages, web pages, applets, and more.
The BrowserUrlPath component powered with Idoc Script is a scripting language that enables reference variables, conditional inclusion of content, and looping over query results. These variables are evaluated on the server, after the browser requests the page elements. If they match, the response will be a Boolean value, rather than a value. If they don’t, then the response will be an empty string.
EncodeHtml Idoc Script function
IdocScript can be a useful tool when working with content from multiple sources. It can filter data input for illegal or corrupted HTML constructs. For example, the Idoc Script EncodeHtml function in Threaded Discussions filteres input to include only well-known unsafe script tags. To use this feature, first define the string to encode. This string is then converted into HTML constructs, preserving the line breaks in the original text.