5 Next Steps After Configuring the Domain

After configuring a product domain, there are additional tasks that you may want to perform.

5.1 Performing Basic Administrative Tasks

After you configure your new domain, there are administration tasks that Oracle recommends you perform on the domain.

The following table lists common administration tasks to perform on your new domain.

Table 5-1 Basic Administration Tasks for a New Domain

Task Description More Information

Getting familiar with Fusion Middleware administration tools

Get familiar with various tools that you can use to manage your environment.

See Overview of Oracle Fusion Middleware Administration Tools in Administering Oracle Fusion Middleware.

Starting and stopping products and servers

Learn how to start and stop Oracle Fusion Middleware, including the Administration Server, Managed Servers, and components.

See Starting and Stopping Oracle Fusion Middleware in Administering Oracle Fusion Middleware.

Configuring Secure Sockets Layer (SSL)

Learn how to set up secure communications between Oracle Fusion Middleware components using SSL.

See Configuring SSL in Oracle Fusion Middleware in Administering Oracle Fusion Middleware.

Monitoring Oracle Fusion Middleware

Learn how to keep track of the status of Oracle Fusion Middleware components.

See Monitoring Oracle Fusion Middleware in Administering Oracle Fusion Middleware.

Understanding Backup and Recovery Procedures

Learn recommended backup and recovery procedures for Oracle Fusion Middleware.

See Introducing Backup and Recovery in Administering Oracle Fusion Middleware.

5.2 Performing Additional Domain Configuration Tasks

Review additional configuration tasks you will likely want to perform on a new domain.

Table 5-2 Additional Domain Configuration Tasks

Task Description More Information

Deploying Applications

Learn how to deploy your applications to Oracle Fusion Middleware.

See Deploying Applications in Administering Oracle Fusion Middleware.

Adding a Web Tier front-end to your domain

Oracle Web Tier hosts Web pages (static and dynamic), provides security and high performance along with built-in clustering, load balancing, and failover features. In particular, the Web Tier contains Oracle HTTP Server.

To install and configure Oracle HTTP Server in the WebLogic Server domain, see Installing and Configuring Oracle HTTP Server.

See also Installing Multiple Products in the Same Domain in Planning an Installation of Oracle Fusion Middleware for important information.

Tuning and configuring Coherence for your topology

The standard installation topology includes a Coherence cluster that contains storage-enabled Managed Coherence Servers. This configuration is a good starting point for using Coherence, but depending upon your specific requirements, consider tuning and reconfiguring Coherence to improve performance in a production environment.

For more about Coherence clusters, see Configuring and Managing Coherence Clusters in Administering Clusters for Oracle WebLogic Server.

For information on tuning Coherence, see Administering Oracle Coherence.

For information on storing HTTP session data in Coherence, see Using Coherence*Web with WebLogic Server in Administering HTTP Session Management with Oracle Coherence*Web.

For more about creating and deploying Coherence applications, see Developing Oracle Coherence Applications for Oracle WebLogic Server.

5.3 Preparing Your Environment for High Availability

Scaling out for high availability requires additional steps.

Table 5-3 lists tasks to perform if you want to scale out your standard installation environment for high availability.

Table 5-3 Tasks Required to Prepare Your Environment for High Availability

Task Description More Information

Scaling out to multiple host computers

To enable high availability, it is important to provide failover capabilities to another host computer. That way, if one computer goes down, your environment can continue to serve consumers of your deployed applications.

See Scaling Out a Topology (Machine Scaleout) in High Availability Guide.

Configuring high availability for Web Tier components.

If you added a Web Tier front-end, you must configure it for high availability and the WebLogic Server software.

See Configuring High Availability for Web Tier Components in High Availability Guide.

Setting up a front-end load balancer

You can use a load balancer to distribute requests across servers more evenly.

See Server Load Balancing in a High Availability Environment and Configure Load Balancer in High Availability Guide.

Configuring Node Manager

Node Manager enables you to start, shut down, and restart the Administration Server and Managed Servers from a remote location. This document assumes you have configured a per-domain Node Manager. See Node Manager documentation for more on advanced Node Manager configuration options and features.

See Administering Node Manager for Oracle WebLogic Server.

5.4 Configuring WebCenter Content User Interface on Additional Nodes

If you install WebCenter Content User Interface on one node, its configuration is complete. However, if you scale out WebCenter Content User Interface to a second node (in a high availability or enterprise deployment topology, for example), you must complete additional configuration steps.

To run WebCenter Content User Interface on additional nodes, you must:

  • Enable WebCenter Content User Interface components.

  • Set the server socket port to 4444.

To enable WebCenter Content User Interface components:
  1. Log in to WebCenter Content as a WebCenter Content administrator.
  2. From the Administration tray or menu, choose Admin Server, then Component Manager.
  3. On the Component Manager page, select all three components under WebCenter Content UI Components:
    • AutoSuggestConfig
    • DynamicConverter
    • FrameworkFolders
  4. Click Update then click OK to confirm that you want to enable the components.
  5. Restart WebCenter Content. See Starting and Stopping Managed Servers in Administering Oracle Fusion Middleware.
Continue to the topic Setting the WebCenter Content User Interface Server Socket Port.

5.5 Setting the WebCenter Content User Interface Server Socket Port

If you are scaling out WebCenter Content User Interface you must change the server socket port.

To change the server socket port:
  1. Open WCC_DOMAIN/ucm/cs/config/config.cfg
  2. Set IntradocServerPort to 4444.
    IntradocServerPort=4444

5.6 Configuring WebCenter Content User Interface Settings

You set WebCenter Content User Interface connection and configuration settings with WLST or Fusion Middleware Control.

5.6.1 Setting Connection Attributes with WLST

You can use displayRIDCConnection and updateRIDCConnection WLST commands to read and update connection properties.

For example, to update the RIDC connection to the WebCenter Content User Interface Managed Server:
  1. Run WLST from ORACLE_HOME/oracle_common/common/bin/wlst.sh.
  2. Enter wls:/offline> connect() and enter your username and password at the prompt.
  3. Enter the Managed Server URL, for example, t3://localhost:16225
  4. Update the RIDC connection to the WebCenter Content User Interface Managed Server. For example:
    wls:/mydomain/serverConfig>updateRIDCConnection('Oracle WebCenter Content - Web UI','WccAdfServerConnection',connUrl='idc://contentserver_host:intradoc_port',credUsername='ucm_admin_user')
  5. Restart the Managed Server.

5.6.2 Setting Connection Attributes with Fusion Middleware Control

Instead of using WLST, you can set connection attributes for WebCenter Content User Interface Managed Server with the Fusion Middleware Control System MBean Browser.

To set connection attributes through Fusion Middleware Control:
  1. Log in to Fusion Middleware Control for the WebCenter Content User Interface Managed Server.
  2. In the navigation tree on the left, expand WebLogic Domain, then the WebCenter Content User Interface domain folder, then the cluster name, and then click Managed Server name.
  3. From the WebLogic Domain drop-down menu at the top of the Managed Server page, choose System MBean Browser.
  4. In the System MBean Browser navigation tree, navigate to the WccAdfServerConnection MBean. To do this, expand Application Defined MBeans —> oracle.adf.share.connections —> Server: WCCADF_server1 —> Application: Oracle WebCenter Content – Web UI. Expand the Mbean ADFConnections then the folder WccConnection.
    • Instead of opening up the folder, you can enter the connection name WccAdfServerConnection in the MBean filtered search.
  5. Click the MBean WccAdfServerConnection.
  6. In the Attributes tab, select PropConnectionURL. Enter a URL to set up the RIDC connection. Click Apply (top right)
    If you leave the PropConnectionSocketTimeout attribute blank, the default (60 seconds) becomes the RIDC Connection Socket Timeout value. This value can create problems if you download large files that are being converted to TIFF or PDF documents with annotations burned in. You can set the attribute to a larger value if you have large files.
  7. Go back to the ADFConnections page (Application Defined MBeansoracle.adf.share.connectionsServer: WCCADF_server1Application: Oracle WebCenter Content – Web UIADFConnections).
  8. On the Operations tab, click save. Then click Invoke.
  9. Restart the WebCenter Content User Interface Managed Server.

5.6.3 Setting Configuration Attributes with WLST

You can use WLST commands displayWccAdfConfig and updateWccAdfConfig to read and update WebCenter Content User Interface configuration parameters.

For example, to use updateWccAdfConfig to update the application’s URL:
  1. Run WLST from ORACLE_HOME/oracle_common/common/bin/wlst.sh.
  2. Enter wls:/offline> connect() and enter your username and password at the prompt.
  3. Enter the Managed Server URL, for example, t3://localhost:16225
  4. Update the WebCenter Content User Interface Managed Server. For example:
    wls:/mydomain/serverConfig>updateWccAdfConfig('Oracle WebCenter Content - Web UI',applicationUrl='idc://contentserver_host:intradoc_port')
  5. Restart the WebCenter Content User Interface Managed Server.

5.6.4 Setting Configuration Attributes with Fusion Middleware Control

Instead of using WLST, you can set configuration (WccAdfConfiguration) attributes for WebCenter Content User Interface Managed Server with the Fusion Middleware Control System MBean Browser.

For example, to set the WebCenter Content User Interface application URL:
  1. Log in to Fusion Middleware Control for the WebCenter Content User Interface Managed Server.
  2. In the navigation tree on the left, expand WebLogic Domain, then the WebCenter Content User Interface domain folder, then the cluster name, and then click Managed Server name.
  3. From the WebLogic Domain drop-down menu at the top of the Managed Server page, choose System MBean Browser.
  4. In the System MBean Browser navigation tree, navigate to the WccAdfConfiguration MBean. To do this, expand Application Defined MBeans —> oracle.adf.share.config —> Server: WCCADF_server1 —> Application: Oracle WebCenter Content – Web UI. Expand the folder ADFConfig, the Mbean ADFConfig , then the folder ADFConfig.
    • Instead of opening up a series of folders to reach the MBean, you can enter the connection name WccAdfConfiguration in the MBean filtered search.
  5. Click the MBean WccAdfConfiguration.
  6. In the Attributes tab, select ApplicationUrl. In the Value field, enter the base application URL. For example: https://wcc.example.com:16225. Click Apply (top right)
  7. Go back to the ADFConfig MBean page (Application Defined MBeans —> oracle.adf.share.config —> Server: WCCADF_server1 —> Application: Oracle WebCenter Content – Web UI —> ADFConfig).
  8. On the Operations tab, click save then Invoke.
  9. Restart the WebCenter Content User Interface Managed Server.