Sunday, October 12, 2014

WebCenter Portal Strategy & Vision: Part 1

I was one of the happy few to visit the Oracle Open World 2014 edition.
On Sunday we attended the WebCenter Portal and WebCenter Content Customer Advisory Board (CAB) at which we were introduced to some exiting new features that we were not allowed to publish anything on.
Fortunately we got to see some announcements officially and without a Non Disclosure Agreement which basically means we can blog / tweet about it.
This will be the first post in a number of posts regarding the general direction Oracle has set out for the WebCenter products.

Before we start, we have to tell you that, as thiese posts are based on the ideas that Oracle has on the subjects they may decide to not implement some of these ideas. Ah well, probably everyone has seen the safe harbor statements from Oracle basically telling you not to make and (puchase) decision based on this information.

So here goes!

We see a slight shift in the way our WebCenter Portal users do business and what they expect of the portal. As more and more people use mobile devices (it's a challenge at OOW to find someone without one) our users want the same experience of the portal on their mobile as if they were at the office using a desktop computer. With that same experience they also want the same functionality. So all actions like creating content or editing pages need to be available on a mobile device as well.

Social aspects get more important every day. We all want to share our experiences we have during our day to day interactions. Enabling social on our sites is one part. Another part is responding to the social media. Being social increases business.

The third important trend is Cloud. Cloud enables you to quickly adopt change.
Not only by adopting new features in a timely manner (I know Oracle customers that are on version 11.1.1.6.5 of WebCenter Portal) but also implementing business needs as soon as they emerge.

To act on these shifts, Oracle makes key investments in four key areas:
  1. Innovations in core functionality in all pillars (Portal, Content, Sites and Business Process Modeling (BPM)
  2. Innovations in cross-product integrations
  3. Innovations in Line of Business Solutions and Solution composition
  4. Innovation in Cloud services
This first part will cover area one: innovations in the pillar called WebCenter Portal

As you can see in the image below, the innovations in Portal are divided in four parts

  • Next Generation Portal
  • Mobility Support
  • Business Ease Of Use
  • Deploy Anywhere



Next Generation Portal
In the 11.1.1.8 release Oracle has improved the composer functionality enormously. They intend to go even further, enabling the business use to perform page editing actions with more ease. Less need for EL expressions and the possibility to create visualizations of data that is exposed by the IT department in the form of REST Data Objects.
The way to add content onto a page has been simplified as well with the arrival of the Lightweight Content Contribution. This enables you to quickly add content without the need of WebCenter Content, classifications etc. The content is stored in a database table and can be edited with a WYSIWYG editor.

With the arrival of the Reusable User Interface (RUI) of WebCenter Content (WCC), the integration of the two becomes tighter. Parts (task flows) of the WCC user interface can be incorporated in the portal making content editing easier as the functionality is the same as in WCC but can be combined with other content through the portal.
Another focus is on the tighter integration of BPM, Business Intelligence (BI) and other Oracle products like Apps.

It's been a challenge to perform life cycle management on Portal assets. In WebCenter Portal 12c Oracle simplifies life cycle management with a user interface to export / import Portal assets including their dependencies. Even the entire portal can be exported / imported with a push on a button (after checking some check boxes :)
An extended sandbox functionality is put in place enabling workflows for the approval of a simple piece of content,  page or a set of pages. As long as the changes are not approved, the change is only visible in the sandbox.


Saturday, August 24, 2013

WebCenter Portal 11.1.1.8 new features - Composer

I'm quite impressed by the entirely new design of the composer, the edit mode of a page.
Instead of a popup containing the resource catalog, it is now an integral part of the design mode.


The basics are the same. You can create your own resource catalogs and can browse and search in the same way as in earlier releases.
But since it is now an integral part of the design view, you can easily drag and drop resources on any region of the page. As you remember, earlier you would select Add Content in a region and select resources for that specific region. Added specific resources to different region was always 'a lot of work'
You now also have a preview mode in which you can see your changes without saving them.

I don't see a lot of use for the Select mode. In this mode you can 'select' a component and edit it's properties. You can do that from the design view as well...

The structure view looks a lot like the old source view. What I miss however, is the option to edit a task flow that is on the page


A nice feature is the preview mode available only to moderators. When you are in edit mode, you get a preview icon with which you can get  a preview of the page when viewed with a specific mobile device (assuming the device groups are enabled, see previous post)



I noticed that the moderator has a lot of additional features available to maintain pages (add, remove) even though my participator account has manage all pages privileges.
What we see when we edit a page as moderator is that you can add pages with a hierarchy. It looks like you do not just add a page, but add it to the default navigation model at the same time, enabling you to create a hierarchy. On the Assets tab under Structure | Navigations you are still able to create multiple navigation models.


Another significant improvement is that you can navigate to the documents page from the edit mode. This enables you to add content while editing a page, again without saving your changes or navigating to the documents page inside a new incognito window.

All in all the interface has improved significantly and is a lot more intuitive.
I think it's a bit weird you do not see the list of pages if you have all the privileges to edit / delete pages, but I'll dive into that when I'm back from holiday. I must be doing something wrong... (the alternative is a bug?!?!?)

BTW: If you are hooked on the Add Content buttons... You can hide the catalog which will remove the docked resource catalog and will give you back your Add Content buttons. I think I'll forget the buttons within the next few weeks though :)

WebCenter Portal 11.1.1.8 new features - Administration

When we start WebCenter Portal 11.1.1.8 we see that the look and feel is brand new.
The styling is the new Skyros skin which is also available in the new JDeveloper.
It is a new and refreshing look and feel.


The first thing we do is of course checking out the new Administration options.
What we notice is the new menu orientation. In previous releases the menu was horizontally orientated with tabs and sub-tabs. Now it is a combination of a horizontal menu and a vertical sub-menu on the left which works fine. Sometimes the menu and sub menu and options of the sub menu get a bit confusing. It might have been better to split some settings to different menu options.


At some locations it's a bit confusing to see what change is set immediate and what change has to be committed explicitly wit the save button.


I can imagine the frustration with the less experienced business users who administers one or more portal.
I am sure I changed this setting but....

Some concepts have been renamed. Resources are now called Assets. And resources which were created on the Spaces application level (and not on a Space level) are called Shared Assets. Same things, different names.
Managing the Shared Assets is the same as in previous versions. New in this are is the Pagelets asset. In the previous versions you would have to know the URL of the WebCenter Ensemble Admin interface. Now, when you select Create Pagelet, you are redirected to the admin interface. It is nice the interface is easy accessible, but it would have been even better if you can create the pagelet from within the Portal interface.
The actions column often contains the most important action, Edit, but for other actions you still need to select the asset and select the action from the menu


New in the Administration section are the Device Settings. You can now differentiate between different device groups such as:

  • Desktop Browsers
  • iOS Phones or Tablets
  • Android Phones or Tablets
Within the groups you can create devices which are selected based on the User Agent they set. Per device you can specify attributes like CSS, streaming preference, height, width etc.
For most of the pages (lets say all new, user created pages) you can create a page variant to support a specific device group. Changes to the Desktop variant are copied to the device specific page variants (and vice verse)

One nice other feature is the ability to change attributes of the Portal application. The one attribute defined per default is the wcSessionTimeoutPeriod making it 100% easier to change the Session Timeout Period for the application.

In addition, there are a lot of small changes in the possibilities you have. Check them out by spending an hour clicking around in the Administration pages.

Friday, August 23, 2013

WebCenter 11.1.1.8 (PS7) installation continued

We're home from vacation (one week to go until work) so I continued the installation.
After the errors during the WebCenter Content installation I decide to first install WebCenter Portal.
No problems, no errors, a textbook install.
I also installed the Web Tier to put WebCache and the Oracle HTTP Server (OHS) in fromt of the WebCenter installation.
Again, no pain what so ever.
Leaves us at the WebCenter Content installation.
I decided to retry the installation after a five minute search on My Oracle Support (MOS) without any result.
When I got the first error it appears to be logged during the outside-in technology installation.

The log file shows the installer is trying to do a CHMOD which, of course is not available on Windows.
After clicking Continue the error pops up a second later.
And again. And again... And again.....

The logfile also shown that the installer is trying to change the permissions on a number of Linux HP-UX and Solaris folders and files. Since we install on Windows I do not see this as an issue.
After the last error the installer starts installing the Content Server component. During this install we do not see any errors. Let's assume the installation was successful...

After the software installation we can create and configure the domain.

As usual, we run the \common\bin\config.cmd to start the configuration wizard.
Since we do a fresh install, we select create a domain and click Next
Next we need to select the components to enable in the domain. My interest goes mainly to the WebCenter Portal functionality so I select the following components:

  • Basic WebLogic Server Domain - Required
  • Oracle WebCenter Spaces - Main application, so a Must have
  • Oracle WebCenter Pagelet Producer - Always nice for demo's so a Should have
  • Oracle Universal Content Management - Content Server - Must have for storing documents
  • Oracle Enterprise Manager - Should have to make the management easier.
  • Oracle WebCenter Discussion Server - Should for our environment / demos
  • Oracle WebCenter Activity Graph Engines - Should for our environment / demos
  • Oracle WebCenter Personalization - Should for our environment / demos
  • Oracle WebCenter Analytics collector - Should for our environment / demos
  • Oracle WebCenter WSM Policy Manager - Must to secure communications between components
  • Oracle JRF - Must to run ADF based applications
I always separate by domain from my executables so I name the domain 11118_domain and create the domain in E:\Oracle\Software\user_projects\domains\11118_domain and the applications in E:\Oracle\Software\user_projects\applicationss\11118_domain

The username and password are default. Create your own ;)
Since this is not a production environment, I select development mode. The JRE locations is set correct by default.

One thing what would be extremely helpful is the ability to set a schema owner prefix at the JDBC Component section. We need to enter the database information for all the JDBC connections that are going to be created. A drawback is that you need to change ALL the usernames because someone thought to set the default prefix to DEV.
Ah well. Let's start typing...
Select all the JDBC Component schemas and set the DBMS/Service, host name, port and schema password (assuming they are all the same for the schemas like in my situation) and select the component schema's to change the schema owner one by one.
On the next page the connections will be tested.

As I always try to utilize my resources as efficient as possible I change the server configuration so I select the modify the Administration Server settings, the Managed Server, Clusters and Machines settings.
The administration server will listen on port 7111 due to multiple installations on my machine.
I create four new managed servers which I will later add to the appropriate clusters.
By adding the new managed servers and adding both them and the original servers to the clusters, the applications and all other objects will be targetted to the cluster.
After the domain is created, the original managed servers can just be deleted, giving us only the new managed servers running all the applications targetted to the cluster.

We now should be done so we start the admin server.
In the Enterprise Manager (accessible at http://localhost:7111/em in my case) we can see all the details in regards to settings and connections from Spaces.

The Console (located at htpp://localhost:7111/console) will show you the domain configuration.


Now we can remove the default managed servers and start the rest.
After starting all the servers we need to configure the connections between the different components.
This process is exactly the same as with the previous release.
You can view my earlier posts to see hot to configure these connections.

Small thing that is different:
Don't forget to enable the folders_g component in WebCenter Content.
The way to do it is a bit different. Although WebCenter Portal does not support the use of the framework folders component, it is this component that is displayed at the WebCenter Content UI Components section of the component manager.


In other sections, the folders_g component cannot be found either.
You need to enable it through the advanced component manager section.
The first negative of this release, the fact that the new framework folders component is still not supported!!!

After enabling all the required components and creating the installation works.
Happy WebCentering!

Friday, August 16, 2013

WebCenter 11.1.1.8 (PS7) released

When WebCenter PS5 was released, I was in the middle of my holiday.
Two days ago, PS7 got released ant today... I'm going on holiday.
I really need to have some conversations with Oracle to align these two events in the future...

I started the installation today and for now I assume the procedure is not much different from the previous releases. The previous release I installed on the 'old' WebLogic (10.3.5) but I'll pick the 'new' release (10.3.6) for this install.

The database is reused from the previous version. Since some time you can create a prefix for your installation so we can just create a new prefix (WC8 in my case).

First thing I noticed is that the RCU supports installation of the OSN schema's.
Will OSN be released as a local installable application soon?


The next thing I noticed that I had hardly any time starting the post during the installation process.
The creation of the schema's and tables took less than five minutes. Record breaking!!

In the Weblogic 12c installation the weblogic folder is renamed from wlserver_10.3 to wlserver.
To make my life potentially easier in the future I'll adapt to this naming convention during the WebLogic installation. Again, the installation is straight forward. I did unchecked the example database (a packaged Derby database) to save some disk space (of about 5 MB :)


After the WebLogic install I first started with the WebCenter Content installation.
You still need to start the installer with the -jreLoc parameter. This sucks on Windows. I just want to click the setup.exe file...
Once it is started, the installer requires about six fields (folder locations) and the installation process starts.
No pain at all! Until 81%.
There we got an error...



In the log file we see that the installer tries a chmod statement ... on Windows ...
Not going to happen....
I really got the generic install.
Unfortunately, the flight is leaving soon so I don't have time to fix this.
End of the installation so far :(




Monday, January 21, 2013

Nice tool to replace many others

It's been a while, but last Friday I got inspired to write another post.
This time not directly related to ADF / WebCenter but to a tool I recently came across.

For some time I'm more and more involved in installation, configuration, performance testing etc.
Therefore, I spend more time on the server to do a number of tasks.
Normally I use the following tools:

  • Putty
    SSH / Telnet client to connect to a server and perform numerous command line tools
  • VNC Viewer
    Combined with VNC Server running on the server machine to run X11 applications. Often used for running Oracle installers
  • WinSCP
    Secure copy tool to copy files to and from the server
Recently I was pointed to MobaXterm 
This tool can replace all of the above.

Why do I use the tool?
First of all, the tool replaces all the tools I used before.
When you create a new session, you get to choose the type and as you can see they support a lot.


Let's say we open a SSH session to one of our servers.
As soon as the connection is made and you logged in, you can start a X11 application like the installer, provided you enabled X11-Forwarding (which is enabled by default)


As with Putty, you can change the background / foreground color of the session to differentiate the environment you are working in (Development, Production etc)


Another nice one is that you can FTP to and from the server immediately as well.
In the sidebar there is a SFTP tab in which you can browse folders and up / download.


Another great feature is the Multi-execution mode
When you enter a command, it is sent to all terminals.
This is ideal when you are managing multiple nodes. Type once. Execute many :)


There are some limitations in the free version. The professional edition will cost you E 49,00
The most annoying limitation of the free version is the fact that the number of saved session is limited to 10
However (can I mention this??) If you edit the MobaXterm.ini file, you can add additional session manually.
This is not recommended of course and for only E 49,00 who's not willing to buy the professional version :)

Friday, May 25, 2012

The birth of a WebCenter based Intranet - 2

My apologies for the time between the previous post and this one.
One would think the Bunny Inc. Intranet would be fully implemented by now :)
Lucky for us, it's an imaginary implementation (is it ?!?)

Any way. In the previous article in the series we could read what Bunny Inc. has on their wishlist.
So let's continue...

We first did a product review to select the product to best fit the needs Bunny Inc. has.
In our opinion, Oracle WebCenter Suite Plus fits best.
Oracle WebCenter is the user engagement platform for social business, delivering connectivity between people and information.
With this selection made, we presented the selected software in a demo session with Bunny Inc stakeholders such as the CEO, CFO, CIO, department management and a delegation of employees. The stakes they hold differ between them, but they will all be end users of the end product, the new Intranet.

As Bunny Inc. does not want to have a major project to start with, we picked the requirements that are quick wins. Things that come out of the box or require some configuration only. These were the main focus points during the demo and impressed all the stakeholders.
With the previous meeting in mind, where we introduced the Think Big, Start Small phrase, some managers actually thought even bigger and came up with the possibility to include communication to and from partners, suppliers and customers as well.
The employee delegates welcomed this idea and shared the ideas they have around improving communication with these parties.

Bunny Inc. wanted to do an inventory session after they had some time to workout these new ideas. In this session, we noticed that the main goals were to:

  • Share information (content)
  • Allow partners, suppliers and customers to provide feedback on this information
  • Being able to share experience and knowledge with and between partners, suppliers, customers and Bunny Inc. employees
  • Provide 'personal' information such as:
    • Order status
    • Payment status
    • Etc

After analysis of these functional area's we concluded that they had a 90+% match with the previous defined requirements and where they did not match, the requirements were in the same spirit.

This gave us a good idea on how to start implementing the new Intranet.

How we did this can be read in the third episode.



Thursday, February 23, 2012

WebCenter PS5 Installation - Quick guide - WebCenter Spaces setup

We started all the Managed Servers and all applications are running.
To use all the different components in WebCenter Portal Spaces, wee need to add the services to the configuration. I hoped that the configuration was done automatically, since a large number of components / services are installed in the same domain.

No problem, we know what to do...

Navigate to the Enterprise Manager at http://localhost:7001/em and login as administrator.
After the login, open the WebCenter folders to check it out.


One thing that worries me a bit is the fact that the version number of WebCenter Portal Spaces states 11.1.1.4.0, while I just installed 11.1.1.6 (PS5)... We'll see...

Let's continue.
First, we need to set the Intradoc Serverport in WebCenter Content.
Click on Oracle WebCenter Content - Content Server

We see some statistics and a menu in the top left corner of the right panel.
In the menu, select Configuration




For Intradoc ServerPort select 4444 which was the default in previous releases.
Then click Apply


In the Admin Server, we need to enable some components.
Navigate to http://localhost:16200/cs
Login as weblogic user.

from the menu (apologies for the Dutch menu, did not install English yet) select manage(?) and the admin server


In the list of components, DO NOT check FrameworkFolders This is the new folders component shipped with 11g. WebCenter Portal however still uses the old folders_g component.
Do check the WebCenterConfigure component.
Click Submit (or Apply, or what ever the button at the bottom says :)


After this setting, the managed server has to be restarted.
In the menu select Control, Shut Down...
And yes, we are sure...


After the shutdown, in the menu select Control, Start





Click webcenter

We see some statistics and a menu in the top left corner of the right panel.
In the menu, select Settings, Service Configuration


Let's configure WebCenter Content first.
From the list of services, click Content Repository and then the Add button


In the Add Content Repository Connection page enter the required information.
Let's name the connection OCS, short for Oracle Content Server (the Repository Type)
The connection is active
sysadmin is always a good Content Administrator :)
We're configuring the connection for WebCenter Portal Spaces, so we use the root folder /spaces and name the application Spaces.
The RIDC Socket Type is Socket. The port has the number we just entered in the WebCenter Content configuration.
The Server Host can be localhost (unless you configured something else)
The Authentication Method remains Identity Propagation, which is default.
The Web Service Context Root is /cs, the last part of the URL we entered in the previous blog post.
Again, enter sysadmin as Administrator User Name.
Click Test if everything is entered.
The test should be successful. If not, please check all the parameters.


If the test succeeded, click OK.
The server should be restarted, but first let's configure the rest as well.
In the list of services, select Discussions and Announcements and click the Add button.


Enter the connection details for the discussions and announcements.
The Connection Name will be Discussions (or anything else :)
Again, check Active Connection
The URL will be http://localhost:8890/owc_discussions unless you consolidated the WebCenter components  to a single Managed Server.
The Administrator User Name is weblogic (or the admin user you created during the domain configuration)
Leave the rest of the settings default and click Test
If the test is successful, the configuration can be stored by clicking OK


Finally, lets configure Analytics as well. Always an interesting feature for management.
Click the Analytics & Activity Graph service and click the Add button


Let's set the Connection Name to Analytics
Again, check Active Connection.
We want to enable WebCenter Portal Spaces events, so check Enable WebCenter Portal Event Collection
We do not have a cluster, so set the Messaging Mode to unicast
The Collector Host Name is localhost, since the collector is running locally.
The Collector Port is 8891, the port of the managed server the collector runs in.


Test this connection as well. If the test is successful, click OK

Now we have configured all the connections, restart the application.
From the menu, select Control, Shutdown...
After the application has stopped, select Control, Start Up

Right. That's it.
Ready for testing...
The WebCenter Portal Spaces application should be accessible at http://localhost:8888/webcenter

WebCenter PS5 Installation - Quick guide - Domain creation

Almost there... Now we're going to create the domain.
From the WebCenter Portal Oracle Home, we start the configuration wizard.
In Explorer, navigate to the \common\bin folder and start config.bat

As I said, we are going to create a domain, so we select Create e new WebLogic Domain and click Next on the welcome page.


We want to configure the domain for the use of WebCenter Portal and Webcenter Content.
For Content, we only want to use the content server.
Please check the screen shots for the product I selected fr the domain.



I keep the name of the domain 'in sync' with the name of the Middleware Home directory and the Repository schemas prefix, dev6
Note: I moved the domain location and application location one level up.
It's always wise to keep the domain folders separate from the binaries folder.
I wonder if Oracle will implement this best practice in future releases.
Click Next


Next, enter the admin username and password.
I always use the default password from the integrated WebLogic Server from JDeveloper. It's easier to remember if all are the same... Click Next


I had only one JDK available. Select the JDK or browse to another JDK if available / required.
Click Next.



We now need to enter the database connection details.
The wizard defaults the prefix to DEV and since I selected something else, I need to change all the usernames. If you did select DEV and kept all the passwords the same, you can set the details for all schemas at once.
Select the schemas you want to set properties for, and enter the details in the top part of the screen.
In short, if all passwords are equal, select all schemas and enter the password, service name, hostname and port for all of them at once.
After setting the all, click Next.


Are you sure you entered all details correctly???
The wizard will check them.
If all tests are passed, click Next. Otherwise correct any errors and try again.


I often want to see what is being set up and maybe change something, so I select the Admin Server, Managed Servers and deployments to investigate / change.
Then click Next.


I already have an admin server listening on the default port of 7001. However, I do not want to run both instances at the same time, so I keep the settings for the admin server at default.


Normally for a local installation, with a minimum of resources, I group the WebCenter components and the UCM components into two separate Managed Servers.
For now, just keep the defaults and click Next.


No clustering today, so click Next.


We install everything locally, so we create a machine within the domain with the same name as the physical machine and let the nodemanager listen on localhost port 5556


We link all the managed servers to this machine. In a production environment you'ld create more machines and divide the managed servers between these physical (or virtual) machines.
Select all Managed Servers, click the arrow pointing to the right and click Next


If you decide to minimize the number of managed servers, this is a good place to target the applications and libraries to these servers.
To make the process easy: Create the domain with the default servers and the new consolidated servers.
On this page, target all the libraries and applications targetted to the original server to the consoliated one as well. After the domain is created and the admin server is started, delete the original servers (or don't start them)
For now leave the defaults and click Next.


Same goes for the services. For now click Next.


At the summary page, you can check everything and then click Create.


Wait for the progress bar to reach 100% and click Done.
I prefer to start the admin server directly since we need to do one additional step.


When the admin server is started, navigate to the console at http://localhost:7001/console and login.
On the page select Servers, then go to the tab Control and check the box for UCM_server1. Click the start button


When the server is started, navigate to http://localhost:16200/cs to access the WebCenter Content content server. Login with the weblogic account (with the password supplied earlier)

At the first time the content server is being accessed, some additional configuration must be performed.
See my screen  shot for some pointer.
Click the I icon to see what each setting is for.
Click Send to submit the values.




Now go back to the admin server and start all required managed servers (WC_Spaces and WC_Utilities)
UCM_server1 has to be restarted.
You ready to develop you WebCenter Portal application.
We need to do some setup for the use of WebCenter Portal Spaces.