When the desired services are installed and configured, you can add task flows to your application pages that access those services. The services that you choose to implement can also impact the topology you choose. For example, you might choose to have WebCenter Portal's discussion server and content repositories reside on different systems, which must both be accessible to your application.
Will there be both authenticated and unauthenticated public users? Several of the WebCenter Portal services offer limited functionality for unauthenticated users. For example, unauthenticated users can view but not contribute to discussions, and the REST services most of them are only available to authenticated users.
Due to this loss of functionality, it sometimes works better to create special public pages designed just for unauthenticated users. Use the portal page hierarchy editor to set delegated administration security policies on individual pages or on multiple pages. For more information, see Section 8. The following list suggests questions you should ask about the administrators of your application:.
It is critical that the Framework application administrator and the developers communicate when the application is under construction. At design time, developers must make many choices that determine what the administrator can do to the application at runtime. For example, if the developers choose not to implement skins, then the administrator has no control over the look and feel of the application.
Hence, the administrator and the developers should ensure that they consult over these decisions at design time. Do administrators need to customize pages and portlets for users or user groups? You may want to enable your Framework application administrator to customize pages and portlets to provide default views of the Framework application for users.
Framework application look and feel. By implementing skins for your Framework application, you enable administrators to choose the look of the pages in the application. Customizable Pages. The administrator can customize the layout of the page. Portlets can optionally include a customization mode Edit Defaults mode that enables the administrator to customize the portlet. The administrator's customization is treated as the default view of the portlet for all other users.
For more information about portlets, see Chapter 57, "Introduction to Portlets. The following list suggests questions you should ask about the developers who will contribute to your application:.
Do developers and administrators want to use the Oracle WebCenter Portal: Framework features in their application? Generally, developers should consider using the Framework application template to create framework applications. The template ensures that a new application is provisioned properly with the correct framework technology scopes and features. These portal-specific features include page hierarchies, delegated administration, navigation models, and page templates.
In addition, runtime administration tools allow authorized users to modify and change these portal features. For more information Chapter 8, "Understanding Framework Applications. Should developers build task flows or portlets as reusable components?
Hence, they have the option of creating reusable components either as task flows, which can potentially be made into JSR portlets through the bridge, or directly as JSR portlets.
If the primary purpose of the component is inclusion in one or more portals, then developers may prefer to build it directly as a JSR portlet, without going through the bridge. If the primary purpose of the component is local execution in a JSF application, then the developer may prefer to create it as a task flow first and then, optionally, use the bridge to run it as a JSR portlet.
Building task flows means that the components can be used in other ADF applications without having to repackage them as portlets first.
Do developers need to integrate content from content repositories for example, Content Server, file system, or Oracle Portal? If you have content located in content repositories to expose in the Framework application, then you must use JCR adapters and data controls to make that content available.
If you plan to have content in your Framework application that is not for everyone, then you must set up a security model with login and user roles that enable you to control access. Components, portlets, and pages can display or not display, depending upon a user's identity. If the content is open to everyone for example, a Human Resources Framework application with content for all employees , then you might not need to implement access control.
The Oracle WebCenter Portal: Framework page hierarchy feature allows you to set security policies on individual or multiple pages in the page hierarchy.
Furthermore, with Composer, you can allow users to edit the content within the application. Again, you must consider whether you want to restrict that capability to certain users and, if so, you must factor that into your security model. Does your WebCenter Portal: Framework application need to provide access to external applications? In many cases, you might have external applications to surface in your Framework application. For example, you might have email, Human Resources, or financial applications that you would like users to be able to view from within the application.
To provide seamless interaction for the user, you must employ an external application credential store of some kind. If you have legacy external application portlets that were built for Oracle Portal, then you can reuse those portlets in a Framework application.
This feature allows users to view these portlets from their Framework application rather than having to open each application separately or go back to Oracle Portal. When building such portlets, though, you must remember that they typically must authenticate themselves to the external application before retrieving and displaying any data.
As previously mentioned, such authentication requires a credential vault, where the Framework application can store the credentials necessary for logging into the external application. For more information about external application portlets, see Section Will the WebCenter Portal: Framework application be developed by a team of developers?
If your Framework application is being developed by a team, then you must think about some additional design considerations. For example, when doing team development, you must be much more aware of which files various JDeveloper actions touch, and may want to take advantage of JDeveloper's ability to integrate code management systems.
For more information about team development, see Chapter 4, "Working Productively in Teams. Accessibility involves making your application usable by persons with disabilities such as low vision or blindness, deafness, or other physical limitations. In the simplest of terms, this means creating applications that can be used without a mouse keyboard only , used with a screen reader for blind or low-vision users, and used without reliance on sound, color, or animation and timing.
This section describes accessibility features that are specific to WebCenter Portal. For information about accessibility features in JDeveloper, see the help topics available by selecting the JDeveloper Accessibility node under JDeveloper Basics in the online help table of contents.
WebCenter Portal provides several Composer components that you can add to your application pages to make them editable at runtime. These components provide attributes that are used to generate accessible HTML. To ensure that the pages you create are accessible, you must set these attributes, listed in Table This attribute transforms into an HTML alt attribute.
This attribute sets the mnemonic character used to gain quick access to the component. When you enable users to customize a page at runtime, you must ensure that any customizations are also accessible to all users.
For all components that users can create at runtime, all accessibility-related attributes are shown in the Property Inspector where users can set them appropriately.
For a list of accessibility-related attributes for WebCenter Portal-specific components, see Table IFrames are not very well accommodated by today's screen readers and so are not permitted by some accessibility standards.
You can set this attribute to false to avoid ever using IFrames. For detailed information, see Section This chapter includes the following sections: Section 2. Some of the tasks they can perform include: Editing page settings and parameters Adding content to the page Editing component properties and parameters Wiring components to page parameters Arranging content on the page Changing the layout for components on the page Removing components from the page The Composer tag library provides the components that you can add to make a page editable at runtime and define the behavior of content on the page for example, move, sequence, or hide components.
Resource Catalogs can contain the following components: Layout components. Table describes each of the available services. Chapter 45, "Integrating the Activity Graph Service" Analytics Enables you to display usage and performance metrics for your Framework application.
Chapter 46, "Integrating the Analytics Service" Announcements Provides the ability to post announcements about important activities and events to all authenticated users. Chapter 32, "Integrating the Announcements Service" Blog Provides easy integration of a blog application within the context of your application. Chapter 31, "Integrating Wikis and Blogs" Discussions Provides the ability to create threaded discussions, posing and responding to questions and searching for answers.
Chapter 33, "Integrating the Discussions Service" Documents Provides content management and storage capabilities, including content upload, file and folder creation and management, file check out, versioning, and so on. Chapter 29, "Integrating the Documents Service" Events Provides the ability to create and maintain a schedule of events relevant to a wider group of users.
Chapter 34, "Integrating the Instant Messaging and Presence Service" Links Provides the ability to view, access, and associate related information; for example you can link to a solution document from a discussion thread.
Chapter 42, "Integrating the Links Service" Lists Provides the ability to create, publish, and manage lists. Chapter 35, "Integrating the Mail Service" Notes Provides the ability to "jot down" and retain quick bits of personally relevant information. Chapter 48, "Integrating Notifications" People Connections Provides social networking capabilities, such as creating a personal profile, displaying current status, and viewing other users' recent activities.
Chapter 37, "Introducing the People Connections Service" Polls Enables you to survey your audience such as their opinions and their experience level , check whether they can recall important information, and gather feedback. Chapter 36, "Integrating the Polls Service" Personalization Enables you to deliver content within your application to targeted application users based on selected criteria.
Chapter 66, "Personalizing WebCenter Portal Applications" Recent Activities Provides a summary view of recent changes to documents, discussions, and announcements.
Chapter 49, "Integrating the Recent Activities Service" RSS Provides the ability to access the content of many different web sites from a single location—a news reader. Chapter 44, "Integrating the Search Service" Tags Provides the ability to assign one or more personally relevant keywords to a given page or document.
Chapter 43, "Integrating the Tags Service" Wiki Provides the ability for geographically diverse teams to originate and collaborate on web documents. Chapter 31, "Integrating Wikis and Blogs" Worklists Provides a personal, at-a-glance view of business processes that require attention including a request for document review, and other types of business process that come directly from enterprise applications. Chapter 50, "Integrating the Worklist Service". This section includes the following subsections: Section 2.
Leverages collective intelligence to benefit search and social applications. Chapter 45, "Integrating the Activity Graph Service". Enables you to display usage and performance metrics for your Framework application. Chapter 46, "Integrating the Analytics Service". Chapter 32, "Integrating the Announcements Service". Provides easy integration of a blog application within the context of your application. Chapter 31, "Integrating Wikis and Blogs". Chapter 33, "Integrating the Discussions Service".
Chapter 29, "Integrating the Documents Service". Chapter 42, "Integrating the Links Service". Improve this answer. Emmanuel Collin Emmanuel Collin 2, 2 2 gold badges 8 8 silver badges 15 15 bronze badges.
I also created domain via Ansible. Please advice. You say "I also created domain via Ansible. My next step is configuration of the WebCenter Portal Domain" What difference do you make between these 2 domains? It's not giving me what I asked. I need to know how to run Webcenter configuration file via Ansible.
What do you mean by Wencenter configuration file? Show 5 more comments. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. All these are called Portal Assets. WebCenter Portal WCP gives various out-of-box assets that can be used to build a rich user interface portal. These assets are customizable and editable within each portal for specific requirements.
However, sometimes you are required to develop complex components, which are difficult to achieve using only the Runtime tools. WebCenter Portal provides multiple Out-of-box task flows for multiple functionalities. For example, content manager Document explorer task flow in 11g task flow, search task flow, discussion task flow, etc. Either the user interface needs changes or some functionalities are not required, or there is a need to add additional information.
In such circumstances, task flow customization can be done to meet the requirements. WebCenter Portal offers different development strategies for transactional features, portlets and Task Flows being the most common.
Different applications or technologies fulfill different features. Choice of technology can also come into play depending on expertise and ease of development. Portal technology is used to aggregate information from multiple sources.
These aggregations can be done using service-orientated architecture, portlet-based, or direct from information source.
0コメント