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

1.2 requirement Software Installation

A typical development environment includes the following components:

• Jdeveloper-refer to 3.1 "installing Oracle jdeveloper ."

• Webcenter extension bundle-please refer to 3.2 "installing the webcenter extension bundle ."

• Supported database-(optional) for example, Oracle Database 11g.

• Supported content repository-(optional) Example: Universal Content Management (UCM) 11g.

• Search engine-(optional) such as Oracle Secure Enterprise Search (SES ).

See Oracle fusion middleware Installation Guide for Oracle webcenter.

1.3 team development preparation

It is important to consider the team development environment as a whole. it is very practical to configure the team development environment to share common resources for team members, such as database resources, content library resources, and original code resources; A well-planned team environment ensures rapid and consistent development, compilation, and update of webcenter applications.

Tip:

In a typical example, a team member creates a new webcenter portal application and submits the source code to the code library. you can create the required database or content library links and submit these links to the code library in the same way.

For more topics about team development, such as source code control and file sharing, see Chapter 4th "working productively in teams ."

1.4 create a new webcenter portal application

Webcenter provides a new webcenyer Application Wizard. This wizard uses an out-of-the-box portal application template to ensure that the correct and appropriate components are included.

After the portal application is created, you can configure the link information of the database and content library and submit it to the resource control system in the same way.

If you want to, you can manually configure the webcenter portal application. For example, you can remove unnecessary components from the webcenter application.

For more information about creating, extending, and modifying portal applications, see Chapter 5th "creating webcenter applications ."

For more information about the link, see section 1.6 "creating Application resource connections ."

1.5 preparation for iterative development

This section describes the features of webcenter iterative development.

• 1.5.1 "What is iterative development? "

• 1.5.3 "enabling iterative development"

• 1.5.4 "turning off iterative development"

1.5.1 what is iterative development?

Iterative development allows you to change the webcenter portal application running on the integrated WebLogic Server, and immediately see the effect of the change by refreshing the browser. iterative development can work by disabling specific option features. iterative development provides developers with faster and more efficient operations when building portal applications. for example, iterative development allows you to see component changes by refreshing your browser:

• Page definitions (page definition)

• Navigation model (Navigation Mode)

• Page hierarchy (page level)

• Existing jspx files (existing jspx files)

• Page Templates (Page Template)

• Resource catalog (Resource Directory)

• Addition of task flows to pages (add person logistics for the page)

• Addition of portlets to pages (add portlets to the page)

The following types of operations are not supported by iterative development. You need to restart the application:

• Create a new file (such as jspx, page definition, and page level)

• Create an implicit new file. For example, when you add a sub-page to the page level, a new*pages.xmlThe file is created.

• Edit any configuration file, suchweb.xmlOradfc-config.xml.

1.5.2 how does iterative development work?

Iterative development can work by disabling specific MDS and running cache. Because these performance options are disabled, when your application runs in the development environment, the performance will be relatively low.

Tip:

When an application is deployed on the integrated WebLogic Serverapache.myfaces.trinidad.CHECK_FILE_MODIFICATIONThe tag is automatically settrue. This setting enables the background service to automatically detect the modification time of JSP and skin style CSS files. When they are changed, the Saved state is lost. the occurrence of this configuration depends on whether the iterative development feature settings are allowed.

When iterative development is allowed, the application configuration changes as follows:

• Set the MDS cache size0. This setting causes all metadata files to be reloaded on each requirement.

• The navigation mode cache will be invalid for each requirement.

For skin development, you can set the application to be practical and non-compressed. This setting is not the default one. You should only use it in the development environment. You can updateweb.xmlEnable this function for the content consistent with the following parameters:

<context-param>    <param-name>org.apache.myfaces.trinidadinternal.DISABLE_CONTENT_COMPRESSION</param-name>    <param-value>true</param-value></context-param>

 

Tip:

When Oracle JSF Portlet bridge portlets is used in your application, the ADF tries to share skin between users and products. therefore, if you do not compress on the user end, you cannot compress on the product end. otherwise, the product will not generate the correct code to match the User-Generated non-compressed IDs. see Chapter 54th "creating portlets with the Oracle JSF Portlet bridge."

 

1.5.3 open iterative development

This section explains how to start iterative development.

Tip:

The iterative development attribute is allowed by default when you create a webcenter portal application.

1. Select application properties from the application menu.

2. In the displayed Properties dialog box, expand the run node.

3. Select webcenter.

4. Check the Enable iterative development check box.

5. Click "OK ".

1.5.4 close iterative development

The steps are similar to the above. In Step 1 only, deselect the Enable iterative development check box.

 

 

1.6 create an application Resource Link

Connections allows the portal application to access external data and services. for example, if you want to use the content provider task flow to display content from the oralce content service knowledge base, you need to configure a connection for the knowledge base. if you try to use portlets In the Portlet product, you need to configure the connection of the product ..

Tip:

A good suggestion is to create and test the link and submit it to the Code resource control system. Then, other developers in the team can check out the link and use it, technically, the team is also allowed to stay in sync when the link changes.

This section describes different methods to access the Wizard to create a new link. See 1.6.3 "Where can I learn more about connections ?. "

1.6.1 where is the link located?

By calling the creation wizard, the link is placed in one of the following locations:

• You can right-click connections under ---> application resources under application navigator to create a link. connections is only used in the current application. This is the most common method for creating a knowledge base link. for specific services, you can drag a connection from application resources to create logistics registration for different types of people. for more information, see the separate L webcenter Service Section.

• Iconnections created in ---> ide connections under resource palette can be reused in the whole webcenter applications. to use these links in an application, you must drag connections from resource palette to the connections node in the application.