We’ve discussed before installing and configuring of Jackrabbit Content Repository into your environment and gets it integrated with Apache Pluto Portal. Actually Jackrabbit isn’t only Content Repository that you may use, a lot of Repositories are provided from different vendors/parties that can be help you exposing your contents.
One of the most leading company in this field is Oracle as it provides Oracle WebCenter Content Server that can be integrated seamlessly with Oracle WebCenter Portal.
We’ve stated earlier different ways that could help you acquiring Jackrabbit repository instance; JNDI, RMI & ServletContext are mainly used to retrieve the contents inside Jackrabbit repository.
Just like Jackrabbit, different types of integration ways that can be used to integrate Oracle Webcenter Content with Portal. This tutorial will discuss the Socket way as it mostly used to achieve that,.
Oracle WebCenter Content is an integrated suite of products designed for managing content, it contains a lot of products underneath and they are enclosed as following:
- Oracle WebCenter Content (WebCenter Content): Which includes WebCenter content server, provides a unified application for several types of content management.
- Oracle WebCenter Content (Inbound Refinery): Is a conversion server that manages file conversions for electronic assets such as documents, digital images, and motion video.
- Oracle WebCenter Content (Imaging): Is an integrated framework of client software modules with an customizable user interface for managing documents from image capture to archiving.
- Oracle WebCenter Content (AXF for BPM): AXF for BPM creates configurable business components, with the application development and configuration capabilities provided by technologies such Oracle Business Process Management (Oracle BPM), Oracle Metadata services Repository (MDS), Oracle Business Rules. These components can be administered to be configured and used in any integrated solutions for Oracle WebCenter business applications.
Some of these components mentioned above may require additional steps to be integrated and used seamlessly, but actually we’re trying to provide you the most minimum steps to get Oracle Webcenter Content integrated with Oracle Webcenter Portal.
As Oracle WebCenter Content requires a Middleware home and an application server onto your system, we’ve assumed that you already get installed Oracle WebCenter Portal into your environment. If you didn’t install it yet do that now by following Installing Oracle Webcenter 18.104.22.168.0 & Developing Portlet Using JDeveloper Tutorial.
If you didn’t install Oracle Webcenter Portal 22.214.171.124, you will get finally an installed instance of Oracle Webcenter Content which can be maintained by using Oracle Webcenter Content administration application.
Install Oracle Webcenter Content (WCC)
Installing of Oracle Webcenter Content Server 126.96.36.199 isn’t so differ from what you already did with Oracle Webcenter Portal with some additional steps:
- Download Oracle Webcenter Content 188.8.131.52 from OTN or form Oracle Delivery Site if you have an official account. Make sure you’re downloading both of two disks. You should have both files like you see in the figure below:
- Open your command line console.
- Navigate into your Webcenter Content (WCC) disk 1. I assumed you specify the following location for your installation.
D:OracleWebCenterOracleContentServerofm_wcc_generic_184.108.40.206.0_disk1_1of2Disk1installwin64and type setup.exe.
- Within showed screen type the location of your JDK. I assumed you have one beneath of
- Waiting till the WCC installer welcome screen being displayed.
- Make option Skip Software Updates unchecked and click next.
- Waiting installer checking its requirement and click next.
- Specify installation location. Mainly, you should specify a Middleware directory that supports installing if Oracle Webcenter Content (WCC) 220.127.116.11. This version of WCC is already compatible with Weblogic Server Middleware 10.3.6 that’s already installed in the Preliminary steps above.
- Name your WCC Oracle Home Directory that would lead you for a created directory inside your Middleware. I assumed your Middleware home beneath
D:OracleWebCenterOracleWCWL6Middlewareand your Oracle Home Directory
- Click next and make sure your selected Weblogic server is checked. Also, double check your Application Server Location and click next.
- Take advantage of your Installation Summary screen to do last check for your installation details; Directory Details, Disk Space and Applications. This screen may be saved for later use.
- Waiting installer till it requested you specifying the second disk. Specify the location just like this
- Once you get a completed message from WCC installer, this is an indicator that you’re installed WCC successfully.
- Click next and then finish.
- By finishing the installation you may notice that you have the following components installed into your WCC Home; Oracle Webcenter Content Server, Oracle Webcenter Content Imaging, Oracle Information Rights Management, Oracle Webcenter Capture and Oracle Webcenter Manager.
Extend Oracle Webcenter Portal Schema
If you recall, part of installing of Oracle Webcenter Portal was preparing the required schema. This step is mainly considered as a mandatory if you want to leverage your Oracle Webcenter Portal facility.
The same one would be happened here for Oracle Webcenter Content, but the exceptional case here that you want to extend your DEV schemas that you’ve created them while installing Oracle Webcenter Portal. Following below required steps:
- Navigate into your Repository Creation Utility (RCU) that you’ve unzipped into your environment. We’ve assumed your RCU location is
- Waiting till you see RCU welcome screen.
- Click next and choose Create.
- Fill in database connection details. Basically, you should use a database user that has sysadmin privilege like sys user.
- Click next and waiting till RCU finished checking prerequisite. In case you faced database version warning, just ignore it.
- From Select Components screen, select an existing Prefix DEV and make sure you’re selecting also Webcenter Content box.
Extend Oracle Webcenter Portal Domain
If you recall, you won’t be able of using Oracle Webcenter Portal if you didn’t create a domain that’s leveraged it. The same issue should be done here, where your domain must be extended by Oracle Webcenter Content before any further using for it.
To extend your domain, you should follow these below steps:
- Execute config.cmd that can be found either beneath
If you recall Oracle_WC is your Oracle Webcenter Portal Home directory and from there you were created a new domain for your Portal.
- Check Extend an existing Weblogic domain from the Fusion Middleware Configuration Wizard and click next.
- Click next and make sure you’re getting all schemas tested correctly.
- From select Optional Configuration, you have to configure your Content Managed Server.
Verify Oracle Webcenter Content Installation
At this point you have a proper installation of Oracle Webcenter Content. Now you can ensure this by getting content server up and running and accessing the administration application of it.
To make sure this you may follow below steps:
- Start your node manager. This actually will help you getting all managed servers controlled by using either of Administration console or enterprise manager.
D:OracleWebCenterOracleWCWL6Middlewarewlserver_10.3serverbin>startNodeManager.cmdto get node manager started.
- Start your Administration server by executing
- Open enterprise manager by accessing
- Enter your username and password weblogic/weblogic123.
- Expand Weblogic domain and click on UCM_server1.
Configure Oracle Content Server
Mainly, you have configured your content server as you may use it normally for adding, removing and updating the digital documents by using Oracle Webcenter content administration facilities.
To prepare Oracle Webcenter content for Oracle Webcenter Portal or Portal Framework Applications, you must enable either the Folders_g or the FrameworkFolders component, and the WebcenterConfigure component.
Basically, Oracle offers two folders solutions: Folders_g (Contribution Folders) and FrameworkFolders components as hierarchical folder interface for Oracle Webcenter content for organizing and locating some or all of the content in the repository.
All releases of Oracle Webcenter that before 18.104.22.168.3 have considered Folders_g (
Contribution Folders) as the implementation for that interface while all releases after 22.214.171.124.3 including itself have used the latest implementation FrameworkFolders.
If you were used earlier version of Oracle Webcenter Portal or patched it from previous version, you must continue using of Folders_g, but in case you’re using new installations of Oracle Webcenter Portal, it’s recommended that you enable the FrameworkFolders component. Using of FrameworkFolders implementation will facilitate you new features and better performance.
In case you’re going to enable FrameworkFolders implementation into other releases you should be aware of the following:
- You should have a new installation of Oracle Webcenter Portal 126.96.36.199.0, usually your Oracle Webcenter Portal shouldn’t be patched from earlier releases (i.e. it should be a fresh instance).
- You must have an Oracle Webcenter Content 188.8.131.52.0, with the FrameworkFolders component enabled.
- Content Server should never have been configured to run with the Folders_g component. You must not enable FrameworkFolde if you were enabled Folders_g previously.
Unfortunately, if you were trying to use FrameworkFolders with Oracle Webcenter Portal 184.108.40.206.0 you may face a lot of issues that will prevent you from getting it integrated with that Oracle Content installed. You may face error says The service COLLECTION_GET_ADMIN_MARKED_CONFIG was called with user sysadmin at time 1/29/15 12:10 AM, and returned statuscode -32.
As such the Folders_g implementation will be used instead, but let’s see now the major difference between those two solutions. Mainly, both of them are providing hierarchical folder interface for the Content Server but they’re actually having different way in which the contents are organized with (i.e. directory structure).
When your Oracle Webcenter Portal uses Content Server repository with Folders_g enabled, all of your Portals are stored under the Webcenter Portal root folder (Which determined while setup, you may assume it WebCenter0202). Each user has a personal folder in the Home Portal is stored under the Path /PersonalSpaces, and this folder is named after the user.
In contrast, when Webcenter Portal is configured to use FrameworkFolders, all Portal folders and personal folders are treated as enterprise libraries and are stored under the path /Enterprise Libraries. Figure below may help you visualized what the folders can be in both cases:
- HR Portal, contains HR policies and documents.
- Partner Portal: contains documents related to partners.
- Users: Karen, Monty and Sam.
Figure below will see you how Content Server will formulate the integration from its point of view: As this will show you the created folders: JournalDevWebcenter and PersonalSpaces that content server has promised you to create them once the integration got done.
Now, it’s time to configure your Oracle Webcenter Content to use FrameworkFolders component by follow below steps:
- Make sure you’re aligned with the conditions mentioned above to get your Oracle Webcenter Portal configured properly.
And make sure it’s restarted successfully
Now, If you want to enable Folders_g you need to follow the same procedure by following below:
- Log on to Oracle Webcenter Content as administrator. Actually, you will do this by using weblogic/weblogic123 as it is administrator user.
- Expand WebCenter / Portal / Spaces / Webcenter Portal Tab.
- Click on the Service configuration showed above.
- Navigate into Content Repository connections.
- Click add to add new Oracle Webcenter content repository connection.
- Fill in required information for Socket integration like below:
Expose Digital Contents Through Oracle Webcenter Portal Content Presenter Component
Oracle Webcenter Portal’s support for JCR 1.0 open document standard enables integration with multiple back-end content stores. Different repositories got supported by Oracle Webcenter Portal like Oracle Webcenter Content Server, Microsoft SharePoint, Oracle Portal 10g and file system.
This integration can be done through using one of three choices below:
- Content Repository data controls.
- Document Tools.
- Content Presenter.
Oracle Webcenter Portal has a built-in Content Presenter component that enable you of seeing/managing the documents in its document folder that you were created while content repository integration above.
- Open your Oracle Webcenter Portal by accessing https://10.10.90.3:8888/webcenter.
- Navigate into Documents Tab that’s listed beside Activities.
- Create folder under weblogic folder and name it JournalDev. This can be done easily through File – New Folder.
- Check your content server and see the new created JournalDev folder.
- Add content from content server instance inside JournalDev folder created. From New Item – New Content and finally check in.
- See added file from Oracle Webcenter Content Presenter.
- Add new content from Portal Content Presenter. Use Upload action and fill in the information required and drop the file used and click Upload.
- Once you uploaded the file, you should see the file added listed in the Content Presenter.
These samples shown above will definitely let you understand the concept of integration that have been done. At least you should have one content repository connection active and as so to make the built-in Content Presenter component functional willingly.
Oracle Webcenter Portal & Oracle Webcenter Content 220.127.116.11.0 can be integrated smoothly through a well-defined steps. If you want to walk through Oracle documentation, you may face a lot of detailed steps that may got you confused.
This tutorial is just a trial to make this so easy for you, so contribute us by commenting below and follow us in the next coming tutorials that would cover the Oracle Webcenter Portal features and facilities.