Walk-through of post install tasks for Oracle WebCenter: on Windows Server 2008 x64 & MS SQL 2008

In my previous post I covered the fourth step of the "simple" installation topology, Configure domain for WebCenter, and will now focus on the fifth step (of eight): Post-install tasks for Oracle WebCenter.

1. Start Admin server and node managers
1. Start the domain by running C:\Oracle\Middleware\user_projects\domains\base_domain\bin\startWebLogic.cmd
1. Wait for the line that reads <Server started in RUNNING mode>
2. Do not close this window as it will shut down the Administration server 
3. You should now be able to access the console via: http://localhost:7001/console
   The username/password we created earlier was weblogic/welcome1
   
   
4. You can navigate to Environment: Servers to see the installed items
   
5. and if you navigate to Environment: Machines you'll see the machine we created
   
6. At this time you also will have access to: http://localhost:7001/em for the Fusion Middleware Control (same login credentials as WLS)
   
   
7. At this point you cannot start any of the servers via the WLS Admin Console.
   
   
2. Start the node manager for WebCenter Space by opening a new command prompt and navigating to C:\Oracle\Middleware\user_projects\domains\base_domain\bin\startManagedWebLogic.cmd. From there enter the following command:
   startManagedWebLogic.cmd WC_Spaces http://localhost:7001
3. Before the server is started, you will be prompted for the WebLogic Server username and password  (weblogic/welcome1)
4. The startup will take about a minute, and as with the domain you'll know it is up when you see a message stating "Server started in RUNNING mode"
5. If you refresh your WLS Admin Console you will see that WC_Spaces is now up and running.
6. You now can access Spaces through a browser by going to http://localhost:7001/webcenter
   
7. Other servers that need to be started are: WC_Portlet, WC_Collaboration, WC_Utilities (Activity and Analytics)
1. Yes, this means you need another command window for each... makes me wonder what % of users run environments so sophisticated that they need the granularity of a command line start vs just a simple start/stop service.  For those that would like to start the servers as a Windows service I'm told it isn't that hard to setup.  Hopefully in a few weeks I'll get around to posting how that is done (once I learn how!).
2. Verify installation
   At this point you will also be able to access a mess load of other URLs to verify the installation
1. To access the Administration Server:
   http://localhost:7001
2. To access the Administration Server console:  
   http://localhost:7001/console
   You will be prompted for the username and password credentials that you specified on the Configure Administrator Username and Password Screen of the Configuration Wizard.
3. To access Enterprise Manager:   
   http://localhost:7001/em
4. To access WebCenter Spaces:
   http://localhost:8888/webcenter
   
5. To access WebCenter Pagelet Producer:
   http://localhost:8889
   
6. To access the WebCenter Pagelet Producer console:
   http://localhost:8889/pageletadmin
7. To access WebCenter Analytics, Activity Graph and Personalization Server:    http://localhost:8891/activitygraph-engines
8. To access WebCenter Activity Graph:
   http://localhost:8891/activitygraph-engines/Login.jsp
9. To access WebCenter Personalization Server:
   http://localhost:8891/wcps/api/property/resourceIndex
   The default port number for the WebCenter Analytics, Activity Graph and Personalization Server is 8891.
10. To access WebCenter OmniPortlet and Web Clipping Portlets:
    http://localhost:8889/portalTools/
11. To access WebCenter Discussions:
    http://localhost:8890/owc_discussions