A WebCenter Configuration

A.1.1 adf-config.xml and connections.xml

adf-config.xml and connections.xml both store design time configuration information, such as the discussions server, mail server, or Oracle Content Server that is used by the WebCenter application in the development environment:

• adf-config.xml - Stores application-level settings, such as the which discussions server or mail server the WebCenter application is currently using.

  See also, Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.

• connections.xml - Stores connection details for WebCenter services.

  See also, Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.

After you deploy a WebCenter application to a production environment, you can use Fusion Middleware Control or WLST commands to reconfigure some properties to meet your production requirements. For example, you can modify connection details to point to production server instances.

Any configuration changes that you make, post deployment, are stored as customizations in the WebCenter application's Oracle Metadata Services (MDS) repository. MDS uses the original deployed versions of adf-config.xml and connections.xml as base documents and stores all subsequent customizations separately into MDS using a single customization layer.

When a WebCenter application starts up, customizations stored in MDS are applied to the appropriate base documents and the WebCenter application uses the merged documents (base documents with customizations) as the final set of configuration properties.

For information on MDS customizations, see "Understanding the MDS Repository" in Oracle Fusion Middleware Administrator's Guide.

Locating Base Documents

adf-config.xml and connections.xml are both located in the /META-INF folder for your application. In a WebCenter application deployment (.ear), you will find the base documents of these files under:

DOMAIN_HOME/servers/server_name

For example, if the DOMAIN_HOME is MW_HOME/wlshome/ /domains/wc_domain/, both configuration files are located under MW_HOME/wlshome/user_projects/domains/wc_domain/servers/WLS_Spaces.

To determine the exact location, search for the configuration file under this folder. For example, enter the following at a command prompt:

> cd MW_HOME/wlshome/user_projects/domains/wc_domain/servers/WLS_Spaces

> find . -name adf-config.xml

A sample response, for this particular example, is as follows: ./tmp/_WL_user/webcenter/8gco54/adf/META-INF/adf-config.xml

You can locate connections.xml in a similar way.

Reviewing Post Deployment Customizations in MDS

Post deployment, always use Fusion Middleware Control or WLST commands to review the latest configuration or make configuration changes. In Fusion Middleware Control you will mostly use WebCenter application configuration screens but a useful Systems MBean Browser is also available for reviewing configuration settings. These tools always show you the current configuration so, typically, there is no need for you to examine or change the content of base documents or MDS customization data for files such as adf-config.xml and connections.xml.

At times it might be useful to 'see' the information in MDS. If for any reason you must extract or examine configuration file customizations that are stored in MDS, use the WLST command exportMetadata.

For example, to determine MDS customizations for connections.xml in WebCenter Spaces, where application name is always webcenter, the managed server is always WLS_Spaces, and the file name and location is always /META-INF/mdssys/cust/adfshare/adfshare/connections.xml.xml, you might specify:

exportMetadata(application='webcenter', server='WLS_Spaces', toLocation='/tmp/mydata', docs='/META-INF/mdssys/cust/adfshare/adfshare/connections.xml.xml')

And similarly, to determine MDS customizations for adf-config.xml:

exportMetadata(application='webcenter', server='WLS_Spaces', toLocation='/tmp/mydata', docs='/META-INF/mdssys/cust/adfshare/adfshare/adf-config.xml.xml')

You choose where to save file customizations by specifying toLocation. If, for example, toLocation is set to /tmp/mydata, then the requested file is saved to /tmp/mydata/META-INF/mdssys/cust/adfshare/adfshare.

If no customizations exist for the requested file, then nothing is saved to the specified location—previously extracted customizations at the same location are not overwritten.

Handling Configuration Conflicts

MDS customizations use references to elements in the base document to call out which elements must be inserted/deleted/replaced, and at what location. If an element is inadvertently removed from a future redeployment and MDS contains a reference to that element, then the WebCenter application's configuration appears corrupt. You are unlikely to face this problem but should a previously deployed application appear corrupt after making changes to adf-config.xml or connections.xml you have the following options:

• Delete MDS customizations for adf-config.xml or connections.xml, deploy the new EAR file, and reconfigure your application from scratch using Fusion Middleware Control or WLST.

  See below for detailed steps, "Deleting MDS Customizations for adf-config.xml or connections.xml".

• Redeploy the EAR file on a new partition or a partition where older customizations are deleted. In either case, all data previously stored in MDS for the application is lost, including any customizations for adf-config.xml or connections.xml, and all user personalizations. You must reconfigure your application from scratch too, using Fusion Middleware Control or WLST.

  See also, "deleteMetadata" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

Deleting MDS Customizations for adf-config.xml or connections.xml

1. Delete customizations for connections.xml, using WLST. For example:

   deleteMetadata(application='webcenter', server='WLS_Spaces', docs='/META-INF/mdssys/cust/adfshare/adfshare/connections.xml.xml')
   

2. Delete customizations for adf-config.xml, using WLST. For example:

   deleteMetadata (application='webcenter', server='WLS_Spaces', docs='/META-INF/mdssys/cust/adfshare/adfshare/adf-config.xml.xml')
   

3. Restart the WebCenter application.

4. Reconfigure your application from scratch using Fusion Middleware Control or WLST.

A.1.2 web.xml

web.xml is a standard J2EE application deployment descriptor file and it is located in the /META-INF directory for your application. Typical run-time settings in web.xml include initialization parameters, custom tag library locations, and security settings.

Unlike connections.xml and adf-config.xml, web.xml does not store post deployment customizations in MDS.

Locating web.xml

To determine the exact location of web.xml in a particular WebCenter application deployment, search for the configuration file under:

DOMAIN_HOME/servers/server_name

For example, if the DOMAIN_HOME is MW_HOME/wlshome/user_projects/domains/wc_domain/, web.xml is located under MW_HOME/wlshome/user_projects/domains/wc_domain/servers/WLS_Spaces.

For example, enter the following at a command prompt:

> cd MW_HOME/wlshome/user_projects/domains/wc_domain/servers/WLS_Spaces

> find . -name web.xml

A sample response, for this particular example, is as follows:

./tmp/_WL_user/webcenter/8gco54/adf/META-INF/web.xml

Editing web.xml

You cannot use Fusion Middleware Control or WLST to modify web.xml in an existing WebCenter application deployment. If you must modify settings in web.xml you will have to do so manually, as described in Appendix A, "Editing Configuration Files Manually".

The are several instance where you might be required to modify web.xml, for example, if you must change:

• Content repository upload parameters: UPLOAD_MAX_MEMORY, UPLOAD_MAX_DISK_SPACE, and UPLOAD_TEMP_DIR. For details, see Section 11.9, "Changing the Maximum File Upload Size".

• Time after which HTTP sessions expire. For details, see Tuning Oracle WebCenter Performance.

• JSP page timeout value. For details, see Tuning Oracle WebCenter Performance.

A.3.1 Configuration Through Fusion Middleware Control, WLST Commands, and System MBeans Browser

Post deployment, always use Fusion Middleware Control or WLST commands to review the latest configuration or make configuration changes. In Fusion Middleware Control you will mostly use WebCenter application configuration screens but a useful Systems MBean Browser is also available for reviewing and modifying configuration settings.

For more information about these tools, read:

• Oracle Enterprise Manager Fusion Middleware Control Console

• Oracle WebLogic Scripting Tool (WLST)

• Oracle System MBean Browser

These tools always show you the current configuration so, typically, there is no need for you to examine or manually change the content of configuration files or MDS customization data for files such as adf-config.xml or connections.xml.

If you must edit these files directly, to set concurrency options for example, follow instructions in Appendix A, "Editing Configuration Files Manually" carefully.

A.3.2 Editing Configuration Files Manually

A few configuration settings, such as those stored in web.xml, are not exposed through MBeans, and therefore, you cannot use Fusion Middleware Control, WLST commands, or the System MBeans Browser for post deployment configuration.

If you must modify these settings, Oracle recommends that you re-create the WebCenter application deployment .ear file with the desired configuration, and redeploy the application. Sometimes this is not feasible or desirable—maybe you do not have access to the .ear file, or perhaps you must configure properties uniquely based on where the file is deployed—in this case, follow the manual steps below, using WLST:

1. Prevent the Weblogic Server from re-staging the WebCenter application, except at deployment time. From the WLST shell, type:

   connect()
   edit()
   startEdit()
   cd("DeploymentConfiguration/<domain_name>")
   cmo.setRestageOnlyOnRedeploy(true)
   activate()
   

2. Open the configuration file in a text editor and modify configuration properties manually, as required.

   Read Locating Base Documents to find out how to determine the exact location of adf-config.xml, connections.xml, or web.xml.

3. Restart the managed server on which the WebCenter application is deployed.

   See, "Starting and Stopping WebLogic Managed Servers Using the Command Line" in the Oracle Fusion Middleware Administrator's Guide.

A.5.1 WebCenter Does Not Display in the Application Deployment Menu in Fusion Middleware Control

Problem

After logging into Fusion Middleware Control, you cannot find the WebCenter option in the Application Deployment menu.

Solution

Ensure the following:

• Deployed application is an ADF application.

  The WebCenter option does not display for applications that are not developed using ADF.

• Deployed application is up and running.

• Deployed application contains accurate information about the MDS repository and partition, and the MDS repository is accessible to the application. To verify this information, check the metadata-store-usages section in the adf-config.xml file. For information on MDS, see "Understanding the MDS Repository" in Oracle Fusion Middleware Administrator's Guide.

• Application is packaged with required artifacts to support configuration:

  • adf-jndi-config name space is configured in the application's adf-config.xml file. This is provisioned at design time. The following is an example (the text in bold) of the adf-jndi-config name space:

    <adf-config xmlns="http://xmlns.oracle.com/adf/config"
         xmlns:jndiC="http://xmlns.oracle.com/adf/jndi/config"
         xmlns:ns2="http://xmlns.oracle.com/mds/config"
         xmlns:ns3="http://xmlns.oracle.com/adf/mds/config">
      ...
      ... 
    </adf-config>
    

  • MDSBackingStore is configured in the application's adf-config.xml file. This is provisioned at design time. This section can exist anywhere in the upper adf-config element, for instance, after the end tag of adf-mds-config. For example, see the text in bold in the following snippet:

    <jndiC:adf-jndi-config>
       <jndiC:ConnectionsJndiContext initialContextFactoryClass="oracle.adf.share.jndi.InitialContextFactoryImpl"
            backingStoreURL="META-INF/connections.xml" backingStoreClass="oracle.adf.share.jndi.MDSBackingStore">
       <jndiC:contextEnv value="true" name="cache_application_scope"/>
       </jndiC:ConnectionsJndiContext>
    </jndiC:adf-jndi-config>
    

  • Appropriate listeners exist in the web.xml file to register the MBeans. This is provisioned at design time. For example, see the text in bold in the following snippet of the web.xml file:

    <listener>
       <description>ADF Config MBeans</description>
       <display-name>ADF Config MBeans</display-name>
       <listener-class>oracle.adf.mbean.share.config.ADFConfigLifeCycleCallBack</listener-class>
    </listener>
    <listener>
        <description>ADF Connection MBeans</description>
        <display-name>ADF Connection MBeans</display-name>
        <listener-class>oracle.adf.mbean.share.connection.ADFConnectionLifeCycleCallBack</listener-class>
    </listener>
    

• MBeans are registered for the WebCenter application. To verify this:

  1. In Fusion Middleware Control, from the Application Deployment menu, select System MBean Browser.

  2. Locate connection MBeans for your application under Application Defined MBeans > oracle.adf.mbean.share.connection.

  3. Similarly, locate adf-config MBeans for your application under Application Defined MBeans > oracle.adf.mbean.share.config. Figure A-1 shows how the Application Defined MBeans section looks in Fusion Middleware Control.

     If your application consumes producers, then locate the Producer Manager Mbean.

     Figure A-1 Application Defined MBeans

     
     Description of "Figure A-1 Application Defined MBeans"
     
     

• Check the application's diagnostic logs, analyze messages for the modules oracle.adf.mbean.share.connection and oracle.adf.mbean.share.config, and determine what must be done.

A.5.2 Configuration Options Unavailable

Problem

When you try to configure a WebCenter application through Fusion Middleware Control, the following message displays:

Configuration options currently unavailable. The application application_name might be down, did not start-up properly, or is incorrectly packaged.
Check the log files for further details.

Solution

For information on how to resolve this issue, see Section A.5.1, "WebCenter Does Not Display in the Application Deployment Menu in Fusion Middleware Control."

A.5.3 Configuration Performed in One Application Reflects in Another

Problem

You configured a WebCenter application, but those configurations also show in another application.

Solution

This happens when multiple applications share the MDS partition in the same schema. To resolve this problem, deploy these applications again and ensure that each application uses its own MDS schema and partition combination. For information about creating a MDS repository or configuring an existing WebCenter application to use a different MDS repository or partition, see section "Managing the Oracle Metadata Repository" in Oracle Fusion Middleware Administrator's Guide.

A.5.4 WebCenter Spaces Logs Indicate Too Many Open Files

Problem

WebCenter Spaces is inaccessible or displaying error messages and the diagnostic log files indicates that there is an issue with 'too many open files'.

Solution

Do the following:

• Check the number of file handles configured on each of the back-end servers, primarily the database, and increase appropriately.

• If the problem persists after increasing the file handles, check the value of fs.file-max in the /etc/sysctl.conf file and increase the value appropriately.

A.6.1 None of the WLST Commands Work

Problem

You are unable to run any WLST commands.

Solution

Ensure the following:

• No files other than Python are stored in the WLST source directory: WC_ORACLE_HOME/common/bin/wlst. This directory must contains files with the .py extension only.

  The default set of files in this location contain legal Python files from Oracle. It is possible that a user copied some non-python script to this directory, for example, a backup file or a test python file with syntax errors.

• webcenter-wlst.jar is located at WC_ORACLE_HOME/common/bin/wlst/lib.

A.6.2 WLST Commands Do Not Work for a Particular Service

Problem

You are unable to run WLST commands for a particular service, and therefore, you cannot configure that service.

Solution

First, run generic non-WebCenter commands, for example, listApplications() and displayMetricTableNames()to verify whether these commands work. If generic commands do not work, then apply the solution described in Section A.6.1, "None of the WLST Commands Work."

If generic commands work, then run test commands to check WebCenter-specific commands for syntax errors. Run the appropriate WSLT check command (see Table A-2).

See also, Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

A.6.3 A Connection with the Name Connection_Name Already Exists

Problem

You are unable to create a connection with the name connection_name. The following message displays:

A connection with name Connection_Name already exists.

Solution

Connection names are unique across WebCenter applications. This error occurs when you try to create a connection with a name that is in use. Ensure that you use a unique name for your connection.

A.6.4 WLST Shell is Not Connected to the Oracle WebLogic Managed Server Instance

Problem

The WLST shell is not connected to the managed server on which you want to run WLST commands.

Solution

Run the following command to connect the WLST shell to the managed server:

connect(username, password , serverhost:serverport)

See also, Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

A.6.5 Application with the Same Name Already Exists in a Domain

Problem

You are unable to register a producer application. The following message displays:

Another application named "YourApplicationName" exists. Specify the Server on which your application is deployed. Use: server="YourServerName".

Solution

There are multiple applications with the same name in the domain in which you are trying to register your application. This usually happens in a cluster environment, where the same application is deployed to multiple managed servers. If this is the case, specify the name of the server in which you are trying to register this application. For example, run the registerWSRPProducer WLST command with the server argument:

registerWSRPProducer(appName='myApp', name='MyWSRPSamples',url='http://host:port/application_name/portlets/wsrp2?WSDL', server=server_name) 

For command syntax and examples, see "registerWSRPProducer" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

See also, Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

A.6.6 Application with the Same Name Already Exists on a Managed Server

Problem

You are unable to register a producer application. The following message displays:

Another application named "application_name" exists on the server managedServerName.

Solution

There are multiple applications with the same name on the managed server in which you are trying to register your application. This usually happens when applications are assigned different versions. If this is the case, specify the version of the application you want to register. For example, run the registerWSRPProducer WLST command with the arguments server and applicationVersion:

registerWSRPProducer(appName='myApp', name='MyWSRPSamples',url='http://host:port/application_name/portlets/wsrp2?WSDL', 
server=server_name applicationVersion=version of the application) 

For command syntax and examples, see "registerWSRPProducer" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

See also, Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

A.6.7 Already in Domain Runtime Tree Message Displays

Problem

While running a WLST command, the following message displays:

Already in Domain Runtime Tree

Solution

None required. This is for information only.