Creating a Portal Managed Server for WebCenter Producer Applications If your Creating Multiple Custom Managed Servers A template can only be applied once

3-8 Oracle Fusion Middleware Installation Guide for Oracle WebCenter When you extend the WebCenter domain with the custom portal template, it creates the Custom Portal managed server named WC_CustomPortal and targets all the necessary resources to it. It also adds the following JDBC data sources: ■ mds-CustomPortalDS for accessing the MDS schema ■ WebCenter-CustomPortalDS for accessing the WebCenter schema ■ Activities-CustomPortalDS for accessing the Activities schema If your WebCenter services use the security and policy manager, you must run the Configuration Wizard a second time to extend your domain with the Oracle WSM Policy Manager template if it is not already installed. This template is available on the Select Domain Source screen. You do not have to do this if your WebCenter services do not use the security and policy manager.

3.1.8.2.2 Creating a Portal Managed Server for WebCenter Producer Applications If your

application developers need to build WebCenter Producer applications, you must create a Custom Services Producer managed server for deployment of these applications. To create the managed server, extend the domain with the Custom Portal template, oracle.wc_custom_services_producer_template_11.1.1.jar. On the Select Domain Source screen, select Base this domain on an existing template, and click Browse to locate the template at the following paths: ■ On UNIX operating systems: WebCenter_ORACLE_HOME commontemplatesapplicationsoracle.wc_custom_services_ producer_template_11.1.1.jar ■ On Windows operating systems: WebCenter_ORACLE_HOME \common\templates\applications\oracle.wc_custom_services_ producer_template_11.1.1.jar When you extend the WebCenter domain with the custom producer services template, it creates the Custom Services Producer managed server named WC_ CustomServicesProducer and targets all the necessary resources to it. It also adds the following JDBC data sources: ■ mds-CustomServicesProducerDS for accessing the MDS schema ■ WebCenter-CustomServicesProducerDS for accessing the WebCenter schema ■ Activities-CustomServicesProducerDS for accessing the Activities schema ■ Portlet-CustomServicesProducerDS for accessing the Portlet schema

3.1.8.2.3 Creating Multiple Custom Managed Servers A template can only be applied once

to a domain. If you want to create multiple custom Managed Servers, you must clone the existing custom Managed Server with the cloneWebCenterManagedServer WLST command. For more information, see cloneWebCenterManagedServer in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. Configuring Oracle WebCenter 3-9

3.2 Post-Configuration Tasks

This section contains general information that will help you verify your installation and configuration. Some components may require custom or manual configuration, and this information is also included in this section: ■ Section 3.2.1, Starting the Servers ■ Section 3.2.2, Starting Node Manager ■ Section 3.2.3, Starting Managed Servers from the Administration Console ■ Section 3.2.4, Verifying the Installation

3.2.1 Starting the Servers

To get your deployments up and running, you must start the Administration Server and various Managed Servers: 1. Run the DOMAIN_HOME binstartWebLogic.sh on UNIX operating systems or DOMAIN_HOME \bin\startWebLogic.cmd on Windows operating systems script. 2. Run the DOMAIN_HOME binstartManagedWebLogic.sh on UNIX operating systems or DOMAIN_HOME \bin\startManagedWebLogic.cmd on Windows operating systems script. This command also requires that you specify a server name. The servers that need to be started are: ■ WC_Spaces - Hosts Oracle WebCenter Spaces ■ WC_Portlet - Hosts Oracle WebCenter Portlets and Oracle Pagelet Producer ■ WC_Collaboration - Hosts Oracle WebCenter Discussions ■ WC_Utilities - Hosts utility applications, such as Activity Graph and Analytics. For example, to start the Oracle WebCenter Spaces server on a UNIX operating system: DOMAIN_HOME binstartManagedWebLogic.sh WC_Spaces http: administration_server_ host : administration_server_port On Windows operating systems: DOMAIN_HOME \bin\startManagedWebLogic.cmd WC_Spaces http: administration_ server_host : administration_server_port Before the server is started, you will be prompted for the WebLogic Server username and password. These were provided on the Configure Administrator Username and Password Screen in the Configuration Wizard. If you do not know the names of the managed servers that need to be started, you can view the contents of the following file on UNIX operating systems: DOMAIN_HOME startManagedWebLogic_readme.txt On Windows operating systems: DOMAIN_HOME \startManagedWebLogic_readme.txt Or, you can access the Administration Server console at the following URL: http: administration_server_host : administration_server_port console