Oracle webcenter 11g Quick Development Guide-translation (III)

1.6.2 How to access the link wizard?

Access Connection Wizard from new gallery:

1. File ---> New.

2. In the new gallery dialog box, expand connections, select the connection type you want to create, and click OK.

   Depending on the type you selected, the dialog box for creating the <connection_type> connection opens.

3. Create a link in this option. application resources is set to the default mode.

   You can choose resource palette --> ide connections to create a link.

Access Connection Wizard from application Navigator:

1. Right-click connections node under application resources, select new connection, and select connection type from the content directory.

2. Depending on the type you selected, the dialog box for creating the <connection_type> connection opens.

   Create a link in this option. application resources is set to the default mode.

Access Connection Wizard from resource palette

1. Click the new icon in resource palette, select new connection, and select connection type from the content directory.

2. Depending on the type you selected, the dialog box for creating the <connection_type> connection opens.

   Create a link in this option. Ide connections is set to the default mode.

1.6.3 where can I learn more about connection?

For information about creating and consuming connections, see:

Chapter 26th "indexing content repository connections"

Chapter 2 "consuming portlets"

Part IV "Integrating and publishing content"

Chapter 2 "deploying and testing your webcenter portal application"

1.7 plan portal Layout

You can use page templates to control the layout of your portal. A page template is a jspx file that specifies the look and feel of your portal's pages. the template defines header, footer, content, and navigation regions within the page. you can apply the template to any number of pages, resulting in a consistent look and feel.

Webcenter provides several default page templates to help you get started. For more information, see Chapter 8, "Understanding pages, page templates, and the portal page hierarchy ."

1.8 skin Processing

A skin is a CSS file that defines the overall look of a portal, including color schemes, fonts, and the display characteristics of ADF faces components. webcenter also provides a portal skin file that you can conveniently edit in jdeveloper. this file lets you override settings in the default skin. just open the file, uncomment any components you wish to modify, and save the file when you are finished making changes. for details, see chapter 14, "creating and managing skins."

1.9 preparations for bidirectional development

Round-trip development refers to features and techniques that allow you to retrieve (repeated) resources from a deployed, runtime portal back to jdeveloper for maintenance (maintenance) or enhancement (enhancement ). after modifying a resource in jdeveloper, you can use the resource manager to upload the resource back to the deployed portal. webcenter's round-trip development features provide a simple, convenient (convenient) Way to modify portal resources without redeploying the entire application.

For more information on round-trip development, see section 16.3, "enabling runtime administration of your portal" and section 16.4, "enabling round-trip development of resources ."

1.10 What should we know about the configuration file?

A number of automatically generated configuration files are placed underWEB-INFAndPage FlowsFolders of a portal project when you create a webcenter portal application.

Tip:

For a complete listing of portal configuration files, see Appendix H, "manually migrating A webcenter portal application ."

This section briefly describes these file:

• Section 1.10.1, "The webcenter portal application template default web. xml file"

• Section 1.10.2, "The webcenter portal application template default faces-config.xml file"

• Section 1.10.3, "The webcenter Application Template default trinidad-config.xml file"

• Section 1.10.4, "The webcenter Application Template default adfc-config.xml file"

1.10.1 default configuration file web. XML for webcenter portal application templates

Part of webcenter portal application configuration is determined by the content of its J2EE application deployment descriptor file:web.xml.web.xmlFile defines your application settings that are required by the application server.

Note:

Rather than being specified inweb.xml, The context root path is assigned when the application is deployed.

Typical runtime settings include initialization parameters, custom tag library location, and security settings. Depending on the technology you use, other settings may be addedweb.xmlAs appropriate.

Note:

For standard Java EE files likeweb.xml, There is usually a counterpart Oracle-specific file with additional Oracle-specific options, for example,weblogic.xml.

Theweb.xmlFile is located in/public_html/WEB-INFDirectory relative to the project in your webcenter portal application.

When you first create your webcenter application, configuration settings for JSF Servlet and mapping and for resource Servlet and mapping are automatically added to the starterweb.xmlFile.

TheFaces ServletEntry inside<servlet></servlet>Tags provides information about the JSF servlet,javax.faces.webapp.FacesServlet. This servlet manages the request processing life cycle for Web applications that use JSF to construct the user interface. The configuration setting maps the JSF servlet to a symbolic name, faces servlet.

TheresourcesEntry inside<servlet></servlet>Tags provides information about the ADF resource Servlet used to serve up Web application resources (images, style sheets, JavaScript libraries) by delegating toResourceLoader.

The<servlet-mapping></servlet-mapping>Tags map the URL pattern to a Servlet's symbolic name. You can use either a path prefix or an extension suffix pattern.

By default, jdeveloper uses the path prefix (prefix)/faces/*. That is, when a URL, for example,http://localhost:8080/SRDemo/faces/index.jsp, Is issued (published), the URL activates the JSF servlet, which strips offfacesPrefix and loads the file/SRDemo/index.jsp.

Note:

If you prefer to use the extensionjsfFor Web pages insteadjspOrjspx, Then you must setjavax.faces.DEFAULT_SUFFIXContext parameterjsf, For example:

<context-param>  <param-name>javax.faces.DEFAULT_SUFFIX</param-name>  <param-value>.jsf</param-value></context-param>

Then add a Servlet Mapping inweb.xmlThat invokes the JSP servlet for files with the extensionjsf.

To editweb.xmlIn Oracle jdeveloper, right-clickweb.xmlIn the Application navigator and choose open from the context menu. This opensweb.xmlIn the web application deployment descriptor Editor, In overview mode. If you are familiar with configuration element names, then you can also use the XML editor to modifyweb.xml.

For information about the configuration elements you can use inweb.xmlFile, see "Oracle adf xml files" in the Oracle fusion middleware fusion developer's guide for Oracle application development framework.

1.10.2 the webcenter portal application template default profile faces-config.xml

Usefaces-config.xmlFile to register a webcenter portal application's resources, such as custom validators (verification) and managed beans, and to define all page-to-page navigation rules. the default name of this file isfaces-config.xml, Though this Naming Convention (Convention) is not required.

Depending on how resources are packaged, an application can have one or multiplefaces-config.xmlFiles. For example, you can create individual JSF configuration files:

• Different areas of your application

• Each library containing custom components or renderers (provider)

For more information about creating multiplefaces-config.xmlFiles, see Oracle fusion middleware fusion developer's guide for Oracle application development framework.

Example 1-1 analyze strates the defaultfaces-config.xmlFile provided through the webcenter portal application template. This file is located in/public_html/WEB-INFDirectory relative to the project in your webcenter portal application.

Example 1-1 default faces-config.xml file provided through the webcenter portal application template

<?xml version="1.0" encoding="US-ASCII"?><faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee">  <application>    <default-render-kit-id>oracle.adf.rich</default-render-kit-id>    <view-handler>oracle.webcenter.portalframework.sitestructure.handler.CustomViewHandler    </view-handler>  </application>  <managed-bean>    <managed-bean-name>preferenceBean</managed-bean-name>    <managed-bean-class>oracle.webcenter.portalframework.sitestructure.PreferencesBean    </managed-bean-class>    <managed-bean-scope>application</managed-bean-scope>  </managed-bean></faces-config>

To editfaces-config.xmlFile, double-click it in the application navigator. by default, the file is opened in the editor window in dimo-mode, as indicated by the active dimo-tab at the bottom of the editor window. when creating or modifying JSF navigation rules, dimo-mode enables you to ally create and manage Page Flows. for more information, see Oracle fusion middleware fusion developer's guide for Oracle application development framework.

To create or modify configuration elements other than navigation rules, use the editor's overview mode. Enter this mode by clicking the overview tab at the bottom of the editor window.

JSF allows multiple<application>Elements in a singlefaces-config.xmlFile. When you use the JSF configuration editor, you can edit only the first instance. For any other<application>Elements, you must edit the file directly using the XML editor. To use the XML editor, openfaces-config.xmlFile and go to the source tab in the editor window.

For reference information about the configuration elements you can use infaces-config.xmlFile, see "ADF faces configuration" in the Oracle fusion middleware fusion developer's guide for Oracle application development framework.

1.10.3 webcenter Application Template default profile trinidad-config.xml

The defaulttrinidad-config.xmlFile, available when you create an application, contains information about the application skin family. additionally, it can contain information about the level of page accessibility support, page animation (animation), time zone, enhanced debugging output, and the URL for Oracle help for the Web (Ohw ). likefaces-config.xml,trinidad-config.xmlFile has a simple XML structure that enables you to define element properties using JSF Expression Language (EL) or static values.

Example 1-2 using strates (legend description) the defaulttrinidad-config.xmlFile provided through the webcenter portal application template. This file is located in/public_html/WEB-INFDirectory relative to the project in your webcenter portal application.

Example 1-2 default trinidad-config.xml file provided through the webcenter Application Template

<?xml version="1.0" encoding="US-ASCII"?><trinidad-config xmlns="http://myfaces.apache.org/trinidad/config">   <skin-family>fusion</skin-family> </trinidad-config>

In addition to the skin family, you can define the following application values intrinidad-config.xmlFile:

• Page Animation

• Level of page accessibility support

• Time Zone

• Enhanced debugging output

• Oracle help for the Web (Ohw) URL

For reference information abouttrinidad-config.xmlFile, see "ADF faces configuration" in the Oracle fusion middleware Web user interface developer's guide for Oracle application development framework.

1.10.4 webcenter Application Template default profile adfc-config.xml

Theadfc-config.xmlFile is the configuration file for an ADF unbounded (uncontrolled, unlimited) task flow. this file contains metadata about the activities and control flows contained in the unbounded task flow. the default name for this file isadfc-config.xml, Though this naming convention is not required.

If ADF page flow is specified as a selected technology on the technology scope page of the Project Properties dialog, a newadfc-config.xmlSource file is automatically created within the project.adfc-config.xmlFile is the main source file for an unbounded task flow.

Theadfc-config.xmlFile is located in/public_html/WEB-INFDirectory relative to the project in your webcenter portal application.

Note:

If you do not plan to use task flows in your application, you can deleteadfc-config.xmlFile.

For more information about task flows andadfc-config.xmlFile, see "Oracle adf xml files" in the Oracle fusion middleware fusion developer's guide for Oracle application development framework.

1.11 installing database schemas (solution, outline, and illustration)

Certain Oracle webcenter components require Schemas that must be installed in a supported database. For details, see section 3.4, "installing database schemas ."