After you have installed WebCenter Content, you can configure the domain, which you can also extend for high availability.
Refer to the following sections to create the database schemas, configure a WebLogic domain, and test the configuration:
Before you can configure an Oracle WebCenter Content domain, you must install required schemas on a certified database for use with this release of Oracle Fusion Middleware.
Follow the instructions in this section to install the schemas:
You must verify that you installed and configured a certified database, and that the database is up and running.
For more information, see Understanding Database Requirements for an Oracle Fusion Middleware Installation in Planning an Installation of Oracle Fusion Middleware.
Starting RCU requires that your JDK environment variable is set correctly.
To start the Repository Creation Utility (RCU):
Use the RCU screens to create the database schemas.
The Welcome screen is the first screen that appears when you start RCU.
Click Next.
Use the Create Repository screen to select a method to create and load component schemas into the database.
If you have the necessary permission and privileges to perform DBA activities on your database, select System Load and Product Load. This procedure assumes that you have SYSDBA privileges.
If you do not have the necessary permission or privileges to perform DBA activities in the database, you must select Prepare Scripts for System Load on this screen. This option generates a SQL script that you can give to your database administrator. See Understanding System Load and Product Load in Creating Schemas with the Repository Creation Utility.
If the DBA has already run the SQL script for System Load, select Perform Product Load.
On the Database Connection Details screen, provide the database connection details for RCU to connect to your database.
Click Next to proceed, then click OK on the dialog window to confirm that connection to the database was successful.
You must enter a custom prefix to group schemas together, then select schemas you need.
Select Create new prefix, specify a custom prefix, then select the WebCenter Content schema. This action automatically selects the following schemas as dependencies:
Oracle WebCenter Content Server — Complete
Oracle WebCenter Enterprise Capture
Oracle WebCenter Content Server — Search Only
The following schemas are selected by default:
Metadata Services
Oracle Platform Security Services
Audit Services
Audit Services Append
Audit Services Viewer
Tip:
You must make a note of the custom prefix you choose to enter here; you will need this later on during the domain creation process.
Note:
If you install WebCenter Content only and select the Oracle WebCenter Content Server — Complete schema (but no other schemas) , you must select the Metadata Services schema. You must select the Metadata Services because WebCenter Content User Interface requires it.The schema Common Infrastructure Services is also created automatically. It enables you to retrieve information from RCU during domain configuration. This schema is grayed out; you cannot select or deselect it. For more information, see Understanding the Service Table Schema in Creating Schemas with the Repository Creation Utility.
The custom prefix logically groups these schemas together for use in this domain only; you must create a unique set of schemas for each domain because schema sharing across domains is not supported.
Tip:
For more information about custom prefixes, see Understanding Custom Prefixes in Creating Schemas with the Repository Creation Utility.
For more information about how to organize your schemas in a multi-domain environment, see Planning Your Schema Creation in Creating Schemas with the Repository Creation Utility.
Click Next to proceed, then click OK on the dialog window confirming that prerequisite checking for schema creation was successful.
On the Schema Passwords screen, specify how you want to set the schema passwords on your database, then enter and confirm your passwords.
Tip:
You must make a note of the passwords you set on this screen; you will need them later on during the domain creation process.
Navigate through the remaining RCU screens to complete schema creation.
On the Map Tablespaces screen, the Encrypt Tablespace check box appears only if you enabled TDE (Transparent Data Encryption) in the database (Oracle or Oracle EBR) when you start RCU. Select the Encrypt Tablespace check box if you want to encrypt all new tablespaces that RCU will create.
When you reach the Completion Summary screen, click Close to dismiss RCU.
Use the Configuration Wizard to create and configure a domain.
For information on other methods to create domains, see Additional Tools for Creating, Extending, and Managing WebLogic Domains in Creating WebLogic Domains Using the Configuration Wizard.
Start the Configuration Wizard to begin configuring a domain.
Navigate to the ORACLE_HOME
/oracle_common/common/bin
directory and start the Fusion Middleware Configuration Wizard.
On UNIX operating systems:
./config.sh
On Windows operating systems:
config.cmd
Use the Configuration Wizard to create and configure the domain for the topology.
Note:
You can use this procedure to extend an existing domain. If your needs do not match the instructions in the procedure, be sure to make your selections accordingly, or see the supporting documentation for more details.
The following sections step through the Configuration Wizard:
You must select a Domain home directory location, optimally outside the Oracle home directory.
To specify the Domain type and Domain home directory:
For more about other options on this screen, see Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.
On the Templates screen, make sure Create Domain Using Product Templates is selected, then select the following templates:
Oracle Universal Content Management - Content Server - 12.2.1 [wccontent]
Selecting this template automatically selects the following as dependencies:
Oracle Enterprise Manager - 12.2.1.0 [em]
Oracle JRF - 12.2.1.0 [oracle_common]
WebLogic Coherence Cluster Extension - 12.2.1 [wlserver]
Oracle Universal Content Management - Inbound Refinery - 12.2.1.0 [wccontent]
Oracle WebCenter Enterprise Capture - 12.2.1.0 [wccapture]
Oracle WebCenter Content - Web UI - 12.2.1 [wccontent]
Tip:
For more information about options on this screen, see "Templates" in Creating WebLogic Domains Using the Configuration Wizard.
On the Application Location screen, select the location to store applications associated with your domain, also known as the Application home directory.
Oracle recommends that you locate your Application home in accordance with the directory structure in What are the Key Oracle Fusion Middleware Directories? in Understanding Oracle Fusion Middleware, where the Application home is located outside the Oracle home directory. This directory structure helps avoid issues when you need to upgrade or re-install your software.
Tip:
For more about the Application home directory, see Choosing an Application Home in Planning an Installation of Oracle Fusion Middleware.
For more about options on this screen, see Application Location in Creating WebLogic Domains Using the Configuration Wizard.
Use the Administrator Account screen to specify the user name and password for the default WebLogic Administrator account for the domain.
Oracle recommends that you make a note of the user name and password that you enter on this screen; you need these credentials later to boot and connect to the domain's Administration Server.
Use the Domain Mode and JDK screen to specify the domain mode and Java Development Kit (JDK).
On the Domain Mode and JDK screen:
Select Production in the Domain Mode field.
Select the Oracle HotSpot JDK in the JDK field.
Tip:
For more about the options on this screen, see Domain Mode and JDK in Creating WebLogic Domains Using the Configuration Wizard.
Use this screen to specify JDBC Data Sources.
Use this screen to test the data source connections you configured in the previous screens.
Note:
To test database connections, the database you are connecting to must be running. If you don’t want to test the connections at this time, do not select any data sources and click Next to continue.A green check mark in the Status column indicates a successful test. If you encounter any issues, see the error message in the Connection Result Log section of the screen, fix the problem, then try to test the connection again.
Use the Database Configuration type screen to specify details about the database and database schema.
On the Database Configuration type screen, select RCU Data. This option instructs the Configuration Wizard to connect to the database and Service Table (STB) schema to automatically retrieve schema information for schemas needed to configure the domain.
Note:
If you select Manual Configuration on this screen, you must manually fill in parameters for your schema on the JDBC Component Schema screen.
After selecting RCU Data, fill in the following fields:
Field | Description |
---|---|
DBMS/Service |
Enter the database DBMS name, or service name if you selected a service type driver. Example: |
Host Name |
Enter the name of the server hosting the database. Example: |
Port |
Enter the port number on which the database listens. Example: |
Schema Owner Schema Password |
Enter the username and password for connecting to the database's Service Table schema. This is the schema username and password entered for the Service Table component on the "Schema Passwords" screen in RCU (see Specifying Schema Passwords). The default username is |
Click Get RCU Configuration when you finish specifying the database connection information. The following output in the Connection Result Log indicates that the operation succeeded:
Connecting to the database server...OK Retrieving schema data from database server...OK Binding local schema components with retrieved data...OK Successfully Done.
Tip:
For more information about the schema installed when RCU is run, see Understanding the Service Table Schema in Creating Schemas with the Repository Creation Utility.
For more information about other options on this screen, see Database Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.
Use the JDBC Component Schema screen to verify or specify details about the database schemas.
Verify that the values populated on the JDBC Component Schema screen are correct for all schemas.
Tip:
For high availability environments, see the following sections in High Availability Guide for additional information on configuring data sources for Oracle RAC databases:
For more information about the other options on this screen, see JDBC Component Schema in Creating WebLogic Domains Using the Configuration Wizard.
Use the JDBC Component Schema Test screen to test the data source connections.
A green check mark in the Status column indicates a successful test. If you encounter any issues, see the error message in the Connection Result Log section of the screen, fix the problem, then try to test the connection again.
By default, the schema password for each schema component is the password you specified while creating your schemas. If you want different passwords for different schema components, manually edit them in the previous screen (JDBC Component Schema) by entering the password you want in the Schema Password column, against each row. After specifying the passwords, select the check box corresponding to the schemas that you changed the password in and test the connection again.
Tip:
See JDBC Component Schema Test in Creating WebLogic Domains Using the Configuration Wizard for more information about other options on this screen.
Use this screen to set credentials for each key in the domain.
Use the Advanced Configuration screen to complete the domain configuration.
On the Advanced Configuration screen, select:
Administration Server
Required to properly configure the listen address of the Administration Server.
Node Manager
Required to configure Node Manager.
Topology
Required to configure the WebCenter Content Managed Server.
Use the Administration Server screen to select the IP address of the host.
Select the drop-down list next to Listen Address and select the IP address of the host where the Administration Server will reside, or use the system name or DNS name that maps to a single IP address. Do not use All Local Addresses
.
Do not specify any server groups for the Administration Server.
Note:
Use Mozilla Firefox to access Internet Protocol Version 6 (IPv6) URLs. You must enter the Global IPv6 address to create a domain and access URLs. (You should not use the local IPv6 address.)Use the Node Manager screen to select the type of Node Manager you want to configure, along with the Node Manager credentials.
Select Per Domain Default Location as the Node Manager type, then specify Node Manager credentials.
Tip:
For more about options on this screen, see Node Manager in Creating WebLogic Domains Using the Configuration Wizard.
For more about Node Manager types, see Node Manager Overview in Administering Node Manager for Oracle WebLogic Server.
You create and configure new Managed Servers on the Managed Servers Screen.
Examples and procedures in the rest of this document refer to these server names; if you choose different names be sure to replace them as needed.
Tip:
More information about the options on this screen can be found in "Managed Servers" in Creating WebLogic Domains Using the Configuration Wizard.
Use the Clusters screen to create a new cluster.
On the Clusters screen:
wcc_cluster_1
in the Cluster Name field.Repeat the preceding steps to create three more clusters: cpt_cluster_1
, ibr_cluster_1
, and wccui_cluster_1
.
By default, server instances in a cluster communicate with one another using unicast. If you want to change your cluster communications to use multicast, see Considerations for Choosing Unicast or Multicast in Administering Clusters for Oracle WebLogic Server.
You can also create clusters using Fusion Middleware Control. In this case, you can configure cluster communication (unicast or multicast) when you create the new cluster. For more information, see "Create and configure clusters" in Oracle WebLogic Server Administration Console Online Help.
Tip:
For more information about options on this screen, see Clusters in Creating WebLogic Domains Using the Configuration Wizard.
Use the Assign Servers to Clusters screen to assign Managed Servers to the new cluster.
On the Assign Servers to Clusters screen:
Figure 4-1 Managed Servers Assigned to Clusters
Tip:
For more about options on this screen, see Assign Servers to Clusters in Creating WebLogic Domains Using the Configuration Wizard.
Use the Coherence Clusters screen to configure the Coherence cluster.
Leave the default port number as the Coherence cluster listen port. After configuration, the Coherence cluster is automatically added to the domain.
Note:
Setting the unicast listen port to 0
creates an offset for the Managed Server port numbers. The offset is 5000
, meaning the maximum allowed value that you can assign to a Managed Server port number is 60535
, instead of 65535
.
See Table 5-2 for more information and next steps for configuring Coherence.
Note:
For Coherence licensing information, see Oracle Coherence in Licensing Information.
Use the Machines screen to create new machines in the domain. A machine is required so that Node Manager can start and stop servers.
Tip:
If you plan to create a high availability environment and know the list of machines your target topology requires, you can follow the instructions in this section to create all the machines at this time. For more information, see Optional Scale Out Procedure in High Availability Guide.
Note:
If you are extending an existing domain, you can assign servers to any existing machine. It is not necessary to create a new machine unless your situation requires it.
Tip:
For more about the options on the screen, see Machines in Creating WebLogic Domains Using the Configuration Wizard.
Use the Assign Servers to Machines screen to assign the Administration Server and Managed Servers to the new machine you just created.
On the Assign Servers to Machines screen:
Figure 4-2 Assign Managed Servers to Machines
Tip:
For more about options on this screen, see Assign Servers to Machines in Creating WebLogic Domains Using the Configuration Wizard.
The Configuration Summary screen has detailed configuration information for the domain you are about to create.
Review each item on the screen and verify that the information is correct. To make any changes, go back to a screen by clicking the Back button or selecting the screen in the navigation pane. Domain creation does not start until you click Create.
Tip:
For more about options on this screen, see Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.
The Configuration Success screen shows information about the domain you just configured.
Make a note of the following items because you need them later:
Domain Location
Administration Server URL
You need the domain location to access scripts that start Node Manager and Administration Server, and you need the URL to access the Administration Server.
Click Finish to dismiss the Configuration Wizard.
After configuration is complete, you can use tools to manage your domain.
Note:
For more information on additional tools you can use to manage your domain, see Overview of Oracle Fusion Middleware Administration Tools in Administering Oracle Fusion Middleware.
Follow the instructions in the following sections:
To start the per-domain Node Manager, go to the DOMAIN_HOME
/bin
directory.
On UNIX operating systems, start the Node Manager using nohup
and nm.out
as an example output file:
nohup ./startNodeManager.sh > $LOG_DIR/nm.out&
where LOG_DIR
is the location of directory in which you want to store the log files.
On Windows operating systems, enter:
startNodeManager.cmd
Note:
On Windows operating systems, Oracle recommends that you configure Node Manager to run as a startup service. This allows Node Manager to start up automatically each time the system is restarted.
For more information, see Running Node Manager as a Startup Service in Administering Node Manager for Oracle WebLogic Server.
For more information about additional Node Manager configuration options, see Administering Node Manager for Oracle WebLogic Server.
To start the Administration Server, go to the DOMAIN_HOME
/bin
directory.
On UNIX operating systems, enter:
./startWebLogic.sh
On Windows operating systems, enter:
startWebLogic.cmd
If you selected Production Mode on the Domain Mode and JDK screen when you created the domain, you see a prompt for the Administrator user login credentials as provided on the Administrator Account screen.
Tip:
For more information about starting the Administration Server, see Starting and Stopping Administration Servers in Administering Oracle Fusion Middleware.
In production mode, a boot identity file can be created to bypass the need to provide a user name and password when starting the Administration Server. For more information, see Creating a Boot Identity File for an Administration Server in Administering Server Startup and Shutdown for Oracle WebLogic Server.
You can verify that the Administration Server is up and running by accessing the Administration Server Console. The URL is provided on the Configuration Success screen in Writing Down Your Domain Home and Administration Server URL (http://administration_server_host:administration_server_port/console
). The default Administration Server port number is 7001
.
Note:
Make sure that the database hosting your product schemas is up and running and accessible by the Administration Server.
For more information about how to use the Administration Console, see Getting Started Using Oracle WebLogic Server Administration Console in Administering Oracle Fusion Middleware.
After you start the Managed Servers, use this topic to refer to Oracle WebCenter Content Managed Server locations.
Server | URL |
---|---|
WebCenter Content |
Example: |
WebCenter Content User Interface |
Example: |
Inbound Refinery |
Example: |
Capture |
Example: |
After completing all configuration steps, you can perform steps to verify that your domain is properly configured.
To verify that the domain is configured properly, see Performing Additional Domain Configuration Tasks.
After you start the Inbound Refinery Managed Servers, configure the settings on the post-installation configuration screen. In most cases, you can accept the default settings.
Use descriptions of Inbound Refinery configuration page fields as you complete configuration steps in Configuring Inbound Refinery Settings (Single Node).
The following table describes Inbound Refinery configuration page fields.
Field | Description |
---|---|
Inbound Refinery Instance Folder | Absolute path to the Oracle instance directory of Inbound Refinery. Default is DomainHome/ucm/ The default Oracle instance directory forInbound Refinery is ORACLE_HOME/user_projects/domains/DomainHome/ucm/ibr The top-level folder in the folder hierarchy for the Content Server instance is ibr .
The path to the Oracle instance directory is the value of the IntradocDir variable for the Inbound Refinery instance. Oracle recommends that you make this directory path unique to this Managed Server, or node. For installations that you will probably upgrade, Oracle strongly recommends that you change the location of the Oracle instance directory to a directory outside any Oracle WebLogic Server domain directories or installation directories. |
Native File Repository Location | Directory that stores conversion jobs during their processing. After a job converts and Content Server picks it up, it is removed from this directory. You do not need to change this path. |
Weblayout Folder | URL for the Inbound Refinery web interface. You do not need to change this path. |
Register Start Menu Actions | Whether or not to register Start Menu actions. |
Server Socket Port | Number of the port to call top-level services.
To set up a provider from Inbound Refinery back to Content Server, you can leave the default Server Socket Port value5555 or change it to an unused port number.
Changing this field value also changes the Note: You must set Server Socket Port correctly to useInbound Refinery.Note: The default port number for Node Manager and Inbound Refinery is5555 . If both run on the same server, you must configure a different port number for Node Manager or Inbound Refinery. |
Incoming Socket Connection Address Security Filter |
Restricts Inbound Refinery access to a computer or computers with a specified IP address or addresses. To enable access from Content Server, enter a value for this field. For example: 127.0.0.1|0:0:0:0:0:0:0:1|your.server.IP.address
This value should be the Content Server instance IP address of the or instances that will send jobs to Inbound Refinery, not the IP address of Inbound Refinery. (In a test or demo environment, these IP addresses could be the same.) This field accepts wildcards such as 10.*.*.*. You can change this value by setting SocketHostAddressSecurityFilter in DomainHome/ucm/ibr/config/config.cfg and restarting Inbound Refinery. Note: To use Inbound Refinery, you must set the Incoming Socket Connection Address Security Filter value correctly. |
Web Server HTTP/HTTPS Address | The name of the web server. (HttpServerAddress property). |
WebAddress Is HTTPS | Whether or not the URL for the web server starts with HTTPS, for a server that has SSL enabled. |
Inbound Refinery URL Prefix | Relative URL for theInbound Refinery instance. |
Server Instance Name | Inbound Refinery instance name. |
Server Instance Label | Instance name shown for Inbound Refinery. |
Service Instance Description | Inbound Refinery Instance description |
You must complete the WebCenter Content configuration on the post-installation configuration page in Content Server.
http://managedServerHost:managedServerPort/cs
Note:
The domain administrator must be the first user to log into the WebCenter Content Managed Server so that they can complete configuration. For more information, see Administering Oracle WebCenter ContentTo complete WebCenter Content configuration:
You enter or verify values in the WebCenter Content configuration page fields to completeWebCenter Content configuration.
You can use descriptions of these fields while completing steps in Configuring WebCenter Content Settings
Field | Description |
---|---|
Content Server Instance Folder | Absolute path to the Oracle instance directory of WebCenter Content. Default is DomainHome/ucm/ The default Oracle instance directory forInbound Refinery is ORACLE_HOME/user_projects/domains/DomainHome/ucm/cs The top-level folder in the folder hierarchy for the Content Server instance is cs .
The path to the Oracle instance directory is the value of the IntradocDir variable for the WebCenter Content instance. Oracle recommends that you make this directory path unique to this Managed Server, or node. For installations that you will probably upgrade, Oracle strongly recommends that you change the location of the Oracle instance directory to a directory outside any Oracle WebLogic Server domain directories or installation directories. |
Native File Repository Location | Path to the vault directory for storing native content checked into WebCenter Content. |
Weblayout Folder | Path to the weblayout directory for storing web-viewable renditions of native and alternate files. |
Register Start Menu Actions | Whether or not to register Start Menu actions. |
Is New Content Server Instance | Whether or not theWebCenter Content instance is new. |
Server Socket Port | Number of the port to call top-level services. Default: 5555
To set up a provider from Inbound Refinery back to Content Server, you can leave the default Changing this field value also changes the |
Incoming Socket Connection Address Security Filter |
Restricts WebCenter Content access to a computer or computers with a specified IP address or addresses. The default value of this field is the local host’s IP address, such as You can specify multiple IP addresses, separated by pipes ( | ). Make sure that there are no spaces on either side of the pipe character. For example: 127.0.0.1|0:0:0:0:0:0:0:1|your.server.IP.address
This field accepts wildcards * for zero or many characters, and ? for any one character. (For example, 10.10.3.*) Typically, use the IP Address Filter field only (most commoon) or Hostname Filter field, not both. |
Web Server HTTP/HTTPS Address | Name of the web server. (HttpServerAddres s property). |
WebAddress Is HTTPS | Whether or not the URL for the web server starts with HTTPS, for a server that has SSL enabled. |
Inbound Refinery URL Prefix | Relative URL for theInbound Refinery instance. |
Server Instance Name | Inbound Refinery instance name. |
Server Instance Label | Instance name shown for Inbound Refinery. |
Service Instance Description | Inbound Refinery Instance description |
Is Auto Number Enabled | Whether or not automatic numbering of WebCenter Contentinstances is enabled. |
Auto Number Prefix | Unique prefix for an WebCenter Content instance number, to avoid conflicts among multiple WebCenter Content instances (Auto Number Prefix system property). |
FullText Search Option | Search engine for full-text search:
None: The Oracle Content Server instance uses DATABASE.METADATA as the search engine. Internal: If using Oracle Database, the WebCenter Content instance uses OracleTextSearch with the system database. If using Microsoft SQL Server, it will use DATABASE.FULLTEXT. External: The Oracle Content Server instance uses OracleTextSearch with an external provider to an Oracle Database (not the system database). If you select this option, you must enter the Data Source name in the External DataSource field. |
External DataSource | Name of the Data Source, which you must create in Oracle WebLogic Server and target to the Managed Server, using an OCSSEARCH schema created with Repository Creation Utility (RCU). |