Yearly Archives: 2016


What are Profiles and Folders in WCC – A comparision

Profiles and Folders are two different features of Oracle WebCenter Content. Both features are useful for grouping and classifying documents.

Your Content Management system can use both Profiles and Folders to provide an effective classification of documents. Profiles – apart from providing usability benefits to your users, also provides effective administrative and customization capabilities to your Developers and Administrators (example, for mass metadata update, migration, creating search index etc..). Folders provide an easy and familiar interface to your users to browse and locate documents.

Profiles provide the ability to hide/show selected metadata fields and group them to present user friendly Check-In/Update and Search screens. The metadata of the content being checked-in can be verified and manipulated based on rules during check-in. Profiles allows organizations to customize the screens according to the needs of a subset of users (for example the Marketing Department). Please note that a single document can be assigned to only one profile.

Recommendation: Use limited Profiles. Group the Metadata in the Check-In/Update screens to further improve the usability.

Folders are used to organize documents in a structured fashion. Folders are created in the context of a library, and like libraries, they can be shared, followed, copied, moved, and secured. By using folders to organize content, you can:

  • Find content quickly by browsing the folder structure.
  • Create a query folder to organize content associated by search criteria.
  • Share groups of content easily with co-workers.

The folders feature can be used when the organization wants to group documents under a specific folder structure and hide/show the folder and documents under it based on Security Group.

A single document can be linked with multiple folders.

Recommendation: Enable folders and formulate a folder structure based on your organizations classification needs.

Both Profiles and Folders might provide the common features of grouping and classifying documents, but they provide different approaches when it comes to maintaining the content management system. For administrative tasks – Profiles are most commonly used than Folders. The following are comparison of Profiles and Folders with respect to other WebCenter Content features:

Security:

  • Profile: Rules can assign a default Security Group or Account to a document at check-in/update time.
  • Folder: Folder level security (fSecurityGroup ) can override document security permissions.
  • Folder: Documents can be forced to inherit folder security using the Force Folder Security and Information Field Inherit Configuration setting.

Workflow:

  • Profile: Profile (xIdcProfile) can be used as a Criteria Definition to trigger a workflow.
  • Folder: Parent Folder (fParentGUID) can be used as a Criteria Definition to trigger a workflow.

Retention:

  • Profile: Can be used to as a trigger field to apply a specific Retention Policy during Check-In.
  • Folder: Can perform basic content retention scheduling by creating a retention query folder, assigning retention attributes to the folder, and then configuring the retention schedule. The schedule can be applied to all content under the query folder. The folder query can be modified dynamically to apply retention for documents matching a new criteria.

Metadata:

  • Profile: Rules can hide/show Metadata and group them in Check-In & Search screens. Values can be set based on rules.
  • Profile: Archiver can use Profiles to bulk update metadata values to a set of documents. This can be achieved by Export & Import with Value Mappings.
  • Folders: Documents can inherit Metadata values assigned to Parent Folders.
  • Folders: Propagate feature can be used to bulk update metadata values to all documents under a folder. Archiver can use fParentGUID to bulk update metadata values to a set of documents. This can be achieved by Export & Import with Value Mappings.
Pros/Con Profile Folder
Pros
  • Customization of Check-In/Update and Search screens
  • Suitable to change the core behavior of Content Server extensively during check-in/update.
  • Profile metadata (xIdcProfile) can be used to perform administrative actions on documents such as bulk update of metadata.
  • Provides a easy and familiar User Interface to view documents in a hierarchical structure
  • Folder metadata can be used to perform administrative actions
  • Folder Propagate can be used to perform bulk update of metadata
  • Documents can be moved, copied, shared (linked) to other folders
  • Can access Folders from Desktop Integration Suite (DIS)
Con
  • User Interface benefit is limited to Check-in/Update/Search interface only.
  • Limited capabilities to change the core behavior of Content Server
  • User Interface benefit is limited to viewing of documents only

 

Recommendation: Use both Profiles and Folders to provide balanced, effective usability and management capabilities in Oracle WebCenter Content

Profiles should be used if you have user groups that have defined custom metadata that are specific to their group only and will use the web interface to check-in and search for documents. Profiles are most commonly used in customizing the Content Server behavior via Custom Components that are built to extend the capabilities of Content Server.

Folders should be used to provide a user friendly hierarchical view of the documents.

A combination of Profiles and Folders based on your requirements will allow you to build an efficient Content Management system for your organization.


Creating DataSource in Weblogic Console – for applications to access Database server

Developers building applications to be deployed in WebCenter Spaces / Portal, WebCenter Sites will need access to the database server.  There are two options to achieve this.

Option A: Create a user/password in the database and pass it to the developer team.

This option has the following dis-advantages.

  1. The username/password is hardcoded in the Application. So in future if there is a change in username/password, the change has to be made in the Application.
  2. Giving direct access to the database is not a secure option, and will compromise Database Security.

To overcome this an alternate method generally used is,

Option B: Create a Data Source in the Weblogic Server and grant access to this data source to the applications deployed to the WebCenter Spaces/Portal servers.

This option has the following advantages.

  1. The application only references the data source name. All applications running on the server can use the same Data Source to securely access the database.
  2. Any change in permissions, passwords etc., can be done centrally at the Weblogic Server Console by modifying the Data Source configuration, and the applications can remain unaffected.
  3. This also ensures that a secure access to the Database is provided.
  4. Moving WAR files from Development Environment to UAT and then to Production Environment can be done seamlessly without changing any application code. (To achieve this, a Data Source with the “same name” should be created in all (DEV, UAT, Production) environments.

Now, Let’s see how to create a “Data Source” in the Weblogic server.

Login to WeblogicServer Console and select“DataSources” from the menu on the left (under “Domain Structure” tab “Services” menu). The screen on the right displays the list of Data Sources created. Click on the NEW button at the top (as shown in the below screen), to create a new Data Source.

GJ_WLDS-1

After clicking new button, select “GenericDatasource” from ListPopup then Specify the name for Data source,JNDI Nameand Database type. In the screenshot below, we have used the following details.

Name of Data Source: Sample

JNDI Name: jdbc/testDS              >> ADF Expects ALL JNDI names used by it to end with the string DS.

Database type: Oracle (We have chosen “Oracle” here. But you could choose the name of the respective database used in your setup).

GJ_WLDS-2

then click NEXT to continue…….

GJ_WLDS-3

This screen prompts us to enter the details for the Database connection (Oracle) chosen in the previous screen.

Database Name:  The Database name given here is OWCSDB. You can replace it with the name of  your database.

HostName: – <IP-address> or hostname

Port: -The default port for Oracle is 1521. This might be different for other databases.


Click on “NEXT” button. The next screen has an option to test the configuration details entered for the Database Connection.

GJ_WLDS-4

Click on “Test Configuration” button to test the Database connection. If the Connection details entered in the previous screen are valid, and connection to database is established successfully, a success message “Connection test Succeeded” is displayed.

If there are errors, an error message is displayed. Click on “Back” button to go to the previous screen and re-enter the Database Connection Configuration details.

Once Connection test is successful, click on NEXT button to proceed.

GJ_WLDS-5The next screen, as shown above, lists all servers running in Weblogic. In this screen, select the target servers to which the Data Source needs to be deployed.

For e.g., if the server “WC_Spaces” is selected, the Data Source is deployed to this server and all applications running on this server can access the database using the “Data Source” created. Multiple servers can be selected as target servers.

The application developers need only know the Data Source Name to be included in their application, thus providing a secure access to the database.

 

 


Bilingual Portal in WebCenter Portal & Content Internationalization

bilingual

If you are working with a customer who has a global presence and needs to present information in more than one language in their public facing portal or website, you can rely on Internationalization capabilities of Oracle WebCenter.

Oracle WebCenter Portal supports internationalization for portal assets. However, if you integrate content from WebCenter Content, you need to implement your own solution to support more than one language. This post provides a simple approach to accomplish this goal. The solution described here uses out-of-the-box features of WebCenter Portal and Content, does not require any customization and supports bi-lingual content.

This solution will accomplish two goals:

  1. Present portal page content from WebCenter Content
  2. Switch to selected language content automatically when user switches to a different language (in the Portal)

The sample code referred here uses a portal named PortalLab and a WebCenter Content connection named WCC. It switches content between English (en) and Tamil (ta)

We are using WebCenter WIKI pages to surface content in Portal pages. WIKI pages can be edited in a Rich Text editor and stored in WebCenter Content and hence its life-cycle (workflow, revision and archiving) can be controlled from WebCenter Content. We use WebCenter Expression Language (EL) to select language specific content.

Let us assume that your Portal has several pages including an “About Us” page and “Contact Us” page.

1. Create a portal page named Content Administrator and set the page permissions to allow only Administrators to view the page. Edit the page and add a Document Viewer taskflow Save and view the page and add folders matching the name of each portal pages (for example: AboutUs, ContactUs etc…)

Create WIKI pages under each folder as below:

>AboutUs
 - content_en
 - content_ta
 >ContactUs
 - content_en
 - content_ta

View the info tab for the each of the WIKI page and note down the Identifier

Example:
 WCC#dDocName: 37001
 WCC#dDocName: 37002

2. Edit the About Us portal page (Not the Folder we created, but the Portal Page) and add a Content Presenter. Edit the Content Presenter (the white wrench icon) and enter the following properties:

Data Source: #{facesContext.externalContext.requestLocale == 'en' ? 'WCC#dDocName: 37001' : 'WCC#dDocName: 37002'}

Save the portal page.

Test by visiting the page and switching the language.