This chapter describes how to configure your Oracle WebCenter Portal components to get them up and running and ready for use.
When you install Oracle WebCenter Portal, the components that you choose to install are deployed to various default managed servers.
The following table lists the managed server and the port number on which Oracle WebCenter Portal components are deployed.
Table 6-1 Oracle WebCenter Portal Components and Managed Servers
| Component | Managed Server | Port |
|---|---|---|
|
WebCenter Portal (Portal Composer) |
|
|
|
Discussions Server |
|
|
|
Portlet Producers |
|
|
|
Pagelet Producer |
|
|
|
Analytics Collector |
|
|
Oracle WebCenter Portal provides an out-of-the-box enterprise-ready customizable application called Portal Composer, also generally referred to as WebCenter Portal, with a configurable work environment that enables individuals and groups to work and collaborate more effectively.
To access WebCenter Portal:
Start the WC_Portal managed server.
Access WebCenter Portal using the following URL format: http://host:port/webcenter
Where host:port refers to the host name and port number of the system where WebCenter Portal is installed. By default, WebCenter Portal is installed on port 8888.
Log on to WebCenter Portal as an administrator.
Note:
If you specified any user other thanweblogic as the domain administrator while creating your Oracle WebCenter Portal domain, you must manually grant the administrator role to that nondefault user for WebCenter Portal. For information, see Granting the WebCenter Portal Administrator Role in Administering Oracle WebCenter Portal.For information about getting started with WebCenter Portal, see Getting WebCenter Portal Up and Running in Administering Oracle WebCenter Portal.
WebCenter Portal supports automatic service configuration for certain tools and services.
Every time you start WebCenter Portal, it automatically tries to create connections for certain various tools and services, unless connections already exist. This section describes what services are automatically configured, how to verify that the automatic configuration succeeded, and how to deactivate automatic configuration if needed.
The following table lists the tools and services for which automatic service configuration is implemented.
Table 6-2 Connections Automatically Configured for WebCenter Portal
| Component/Tool/Service | Default Connection Name |
|---|---|
|
Discussions and Announcements |
|
|
Documents |
|
|
Pagelet producer |
|
|
Preconfigured portlet producers |
|
|
Worklists and WebCenter Portal workflows |
|
For the listed WebCenter Portal connections to be automatically configured, the following general conditions must be met:
WebCenter Portal and the target component must be installed in the same domain.
The managed server of the target component must have an explicit listening address. If its listening address is empty or null or localhost, then it must have a system associated to it that has an explicit address. For information about listening address, see Configure Managed Servers in Creating WebLogic Domains Using the Configuration Wizard.
The target component must not be deployed to a cluster.
You must start the managed servers associated with the specified tool or service first. Then start the WC_Portal managed server.
If the target component has already been automatically configured on application startup, it will not be configured again regardless of the result (Fail or Success). Automatic connection configuration of a service fails if the target component does not pass the target component-specific rules. If the automatic configuration fails for a specific component, then you must manually configure the service. For information, refer to the required target component-specific section in this chapter.
Verifying Automatic Connection Configuration for Tools and Services
To verify that tools and services connections are automatically configured for WebCenter Portal when you start the managed servers:
Access the Oracle Enterprise Manager Fusion Middleware Control Console using the following URL format: http://host_name.domain_name:port_number/em
For example: http://myhost.mycompany.com:7001/em
Enter a valid administrator user name and password for the farm, and click Login.
Navigate as follows in Enterprise Manager Console:
farm_wc_domain > WebCenter > Portal > Server > WebCenter Portal
The WebCenter Portal home page displays the WebCenter Portal menu.
From the WebCenter Portal menu, select Settings, and then Service Configuration.
Select the different tools and services and verify that the tools and services that support Automatic Service Configuration are configured.
Disabling Automatic Service Configuration for WebCenter Portal
If required, you can disable the auto-configuration feature by setting the following Java property: -Dwebcenter.spaces.disableAutoConfigure=true
You can set this Java property in two ways:
You can add the property to JAVA_PROPERTIES in DOMAIN_HOME/bin/setDomainEnv.sh (on UNIX) or DOMAIN_HOME\bin\setDomainEnv.cmd (on Windows).
You can append it at the end of the script when starting up the WC_Portal managed server. For example: DOMAIN_HOME/bin/startManagedWebLogic.sh WC_Portal -Dwebcenter.spaces.disableAutoConfigure=true
Oracle WebCenter Portal's Discussions Server provides the ability to integrate discussion forums and announcements into a portal.
WC_Collaboration managed server. You can choose to install the Discussions Server while installing Oracle WebCenter Portal for the first time, or to install it later by extending an existing Oracle WebCenter Portal domain.weblogic as the domain administrator, that user is granted all the domain administrative rights. After creating the domain, you must manually grant the Administrator role to that nondefault user for the discussion server. For information, see Granting Administrator Role on the Discussions Server in Administering Oracle WebCenter Portal.Oracle WebCenter Portal's Portlet Producers provides several preconfigured portlet producers that you can access and register.
WC_Portlets managed server is created, and the following applications are deployed to the server:
wsrp-tools - Supports WSRP Tools
portalTools - Supports OmniPortlet
Note:
In 12c, Pagelet Producer replaces the functionality of Web Clipping portlets available in earlier releases of WebCenter Portal throughportalTools.To access preconfigured portlet producers, you can use the following URLs, depending on the preconfigured portlet producer you want to access:
http://host:port/portalTools for OmniPortlet
http://host:port/wsrp-tools/ for WSRP Tools
Where host:port refers to the host name and port number of the system where Portlet Producers is installed. The default port number is 8889.
To work with the preconfigured portlets available in Oracle WebCenter Portal, you must:
Oracle WebCenter Portal's Pagelet Producer provides a collection of useful tools and features that facilitate dynamic pagelet development. This topic describes how to access and begin working with Oracle WebCenter Portal's Pagelet Producer.
Note:
Oracle WebCenter Portal's Pagelet Producer replaces the functionality of Web Clipping portlets available in earlier releases of WebCenter Portal.Pagelet Producer is deployed to the WC_Portlet managed server.
To access the Pagelet Producer console, use the following URL: http://host:port/pagelets/admin
Where host:port refers to the host name and port number of the system where Pagelet Producer is installed. The default context root is pagelets, but Pagelet Producer can be deployed to any location of your choice. For example: http://myhost.com:8889/pagelets/
All post deployment connection configuration is stored in the Oracle Metadata Services (MDS) repository. Pagelet Producer stores all configuration data on a separate partition in the MDS schema of RCU. Typically, this schema is installed as part of the Oracle WebCenter Portal installation. This configuration data does not conflict with data that belongs to other services. When you deploy the Pagelet Producer domain template, Configuration Wizard prompts for connectivity information to the database in which the schema has been created. The names that the Pagelet Producer expects are:
Datasource Name: mds-PageletProducerDS
JNDI name: jdbc/mds/PageletProducerDS
MDS partition name: pageletproducer
To work with Pagelet Producer:
Oracle WebCenter Portal's Analytics Collector supports the Analytics feature that enables users to display usage and performance metrics for portals. This topic describes how to begin working with Analytics Collector.
ACTIVITIES) to be installed. By default, Analytics Collector is installed on the WC_Portal managed server on port 8888.ACTIVITIES schema cannot be shared across applications.WC_Portal managed server.