A very common use-case for WebCenter applications is to use them for Content Contribution projects. WebCenter Portal and WebCenter Content are designed to work seamlessly with each other. Once set up correctly a content contribution user can make all content changes from within the Portal application, without going into content administration application.
The following article shows the steps required to start a new WebCenter project for content contribution.
Create a new Content repository connection in JDeveloper and add the following values.
|RIDC Socket Type||socket|
|Server Host Name||<Content Host name>|
|Cache Invalidation Interval||2|
In our example the content server is running on a local VM hence host name is localhost.
Create a new Portal Framework Application
Index Page: Change the default page in index.html to be your home page. This will show a pretty URL when home page is rendered.
Login Success Page: For showing a pretty URL after login change the login_success page in faces-config.xml to your home page. This will always redirect to home page post login, so do not change it if users can login from any page in your application.
Page Hierarchy: Once the necessary design time pages are created, add them to the page hierarchy and set the appropriate Title and security options. Failure to do so will prevent the page to be shown on the UI.
Contrary to the name, the page hierarchy shown on UI is controlled by the Navigation Model.
Navigation Model: Best practices states that all pages should be added as Page Links within Navigation Model. The Navigation Hierarchy created here dictates how page URL is created.
Page Template: Most users choose to create their own custom template. Our recommendation is to keep taskflows to the minimum for optimal page performance. To allow users to edit page at runtime, add panelEditor tag either within the template or within page.
<pe:pageCustomizable id="hm_pgc1"> <cust:panelCustomizable id="hm_pnc1" layout="scroll"> <af:facetRef facetName="content"/> </cust:panelCustomizable> <f:facet name="editor"> <pe:pageEditorPanel id="pep1"/> </f:facet> </pe:pageCustomizable>
Content Presenter: A content can be added directly via JDeveloper or at runtime via composer. Custom content presenter templates should be created as per requirements.
When adding the content presenter via JDeveloper surround it with showDetailFrame so that it can be edited at runtime by composer.
High Availability Support: Most production grade applications run on multiple servers in cluster. Hence “High Availability for ADF Scopes” should be checked so JDeveloper can prompt developer high availability violations are detected.
Cookie Path: Cookies are enabled by default in weblogic.xml and should remain that way. Additionally Cookie Trigger Path should be set to a unique value. A good rule of thumb is to set it same as the context root.
Context Root: Needless to say a context root should always be set to appropriate name. Its done via Java EE Application in Portal project properties. Optionally, the deployment profile name and application name can also be changed for clarity.
Refer to performance blogs for other application configuration settings.
Integrated Server deployment: For design/development time testing, the application can be deployed by running index.html page.
In Part 2 we will explain how runtime environment should be set up for development time testing.
All site content is the property of Oracle Corp. Redistribution not allowed without written permission