Page Retrieval Oracle UCM Search Services Integration Methods

2-4 Oracle Fusion Middleware Services Reference Guide for Oracle Universal Content Management

2.1.2 Page Retrieval

When a web page is requested from the Oracle UCM system, one of the following page types is returned: ■ static page: The content of a static web page is pre-formatted, and does not change from one request to the next. In a typical Oracle UCM web site, the only static page is the guest home page for example, DomainHomeucmcsweblayoutportal.htm. ■ dynamic page: A dynamic web page is assembled at the time of the Web server request, using Oracle UCM services and templates to determine the content and formatting. For example, each users portal design page is generated using an Oracle UCM service called GET_PORTAL_PAGE and a template called PNE_ PORTAL_DESIGN_PAGE.

2.1.3 Oracle UCM Search Services

A search request is a special kind of Oracle UCM service. When the Oracle UCM system receives a search request, it sends the request on to the search engine using a search engine API. This allows different search engines to be used with the Oracle UCM system.

2.1.4 Integration Methods

Service requests can be made by any external program or HTML page using a wide variety of protocols. The Oracle UCM system can be integrated with other enterprise applications using a wide variety of integration methods. One common integration method is to reference content that is managed within the Oracle UCM system by persistent URL. For more information, see Section 2.1.5, Calling Services Using Persistent URLs. The following are other possible integration methods: ■ Oracle WebLogic Server Web Services WS using integrated WebLogic JAXP and SAML support ■ Oracle UCM Web services component for the Oracle Content Server and Remote Intradoc Client RIDC component for clients ■ Java API IdcCommand integration using the IdcCommand Java Command Utility ■ Java Server Page JSP integration from a JSP running in Oracle UCM, a JSP through the Oracle UCM JavaBean, or a JSP through the Oracle UCM Enterprise JavaBean EJB deployed on your J2EE application server ■ Java 2 Enterprise Edition API J2EE integration by deploying the Oracle UCM Enterprise JavaBean on your J2EE-compliant application server ■ Simple Object Access Protocol SOAP integration using the SOAP protocol ■ Virtual Folders integration using the Folders_g component ■ Web Distributed Authoring and Versioning WebDAV integration using the WebDAV component Using Services 2-5 ■ Component Object Model COM integration using the ActiveX utility or the IntradocClient OCX component

2.1.5 Calling Services Using Persistent URLs