Friday, August 23, 2013

WebCenter (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!

No comments:

Post a Comment