Thursday, February 23, 2012

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.


  1. Thanks for sharing this valuable info. You were pretty lucky in getting it all the way through. I am stuck after managed servers came up but 'webcenter' app has failed saying 'java.lang.ClassNotFoundException: oracle.mds.lcm.weblogic.WLLifecycleListener'. Have anyone seen this error ?
    Library version is a puzzle, still seeing and while installing it is for Webcenter.

  2. Arun,

    Sorry for the late reply.
    I found this thread:
    Don't know if it's you :)
    Ever got it fixed?
    Did you compare the checksum of your download?
    (to make sure it's OK)