Skip Headers
Oracle® Fusion Middleware Release Notes
11g Release 1 (11.1.1) for Microsoft Windows x64

Part Number E14774-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

4 Oracle Fusion Middleware Administration

This chapter describes issues associated with Oracle Fusion Middleware administration. It includes the following topics:

4.1 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topic:

4.1.1 Supported Combinations for Extending Domains

When you create an Oracle WebLogic Server domain, you create it using a particular domain template. That template supports a particular component or group of components, such as the Oracle SOA Suite. If you want to add other components, such as Oracle WebCenter, to that domain, you can extend the domain by creating additional Managed Servers in the domain, using a domain template for the component which you wish to add.

Table 4-1 shows which components you can add to an existing domain and the domain templates needed.

Table 4-1 Supported Domain Extensions

Existing Domain Template Components That Can Be Added

Oracle SOA Suite

Any Oracle SOA Suite component.

Any Oracle WebCenter component. Extend with Oracle WebCenter domain template.

Any Web Tier component. Extend with Web Tier domain template.

Oracle Identity Management

Any Identity Management component.

Any Web Tier component. Extend with Web Tier domain template.

Oracle Portal, Oracle Reports, Oracle Forms Services, Oracle Business Intelligence Discoverer

Any of these components.

Any Web Tier component. Extend with Web Tier domain template.


4.1.2 Supported Topologies for IPv6 Network Protocols

The following topologies for IPv6 are supported (dual-stack means that the host is configured with both IPv4 and IPv6):

  • Topology A:

    • Oracle Database on IPv4 protocol host

    • Oracle WebLogic Server on dual-stack host

    • Clients on IPv4 protocol host

    • Clients on IPv6 protocol host

  • Topology B:

    • Oracle Database on IPv4 protocol host

    • One or more of the following components on dual-stack hosts: Oracle WebLogic Server, Oracle SOA Suite, Oracle WebCenter, Oracle Business Activity Monitoring, Fusion Middleware Control

    • Oracle HTTP Server with mod_wl_ohs on IPv6 protocol host

  • Topology C:

    • Database, such as MySQL, that supports IPv6 on IPv6 protocol host

    • Oracle WebLogic Server on IPv6 protocol host

    • Clients on IPv6 protocol host

  • Topology D:

    • Oracle Database on IPv4 protocol host

    • One or more of the following components on dual-stack hosts: Identity Management, Oracle SOA Suite, Oracle WebCenter, Oracle Business Activity Monitoring, Fusion Middleware Control

    • Clients on IPv4 protocol host

    • Clients on IPv6 protocol host

  • Topology E:

    • Oracle Database on IPv4 protocol host

    • One or more of the following components on IPv4 protocol host: Oracle Portal, Oracle Forms Services, Oracle Reports, Oracle Business Intelligence Discoverer, and Oracle Single Sign-On Release 10.1.4.3

    • Oracle HTTP Server with mod_proxy on dual-stack host

    • Clients on IPv6 protocol host

  • Topology F:

    • Oracle Access Manager Release 10.1.4.3 and applications, such as SOA composite applications on IPv4 protocol host

    • Oracle HTTP Server with mod_proxy on dual-stack host

    • Clients on IPv6 protocol host

  • Topology G:

    • Oracle Database on IPv4 protocol host

    • One or more of the following components on IPv4 protocol host: Oracle SOA Suite, Oracle WebCenter, Oracle Business Activity Monitoring, Fusion Middleware Control on IPv4 protocol host

    • Oracle HTTP Server with mod_wl_ohs on dual-stack host

    • Clients on IPv6 protocol host

See Also:

The section "Using IPv6" in the Oracle Fusion Middleware Administrator's Guide

4.1.3 Fusion Middleware Control May Return Error in Mixed IPv6 and IPv4 Environment

If your environment contains both IPv6 and IPv4 network protocols, Fusion Middleware Control may return an error in certain circumstances.

If the browser that is accessing Fusion Middleware Control is on a host using the IPv4 protocol, and selects a control that accesses a host using the IPv6 protocol, Fusion Middleware Control will return an error. Similarly, if the browser that is accessing Fusion Middleware Control is on a host using the IPv6 protocol, and selects a control that accesses a host using the IPv4 protocol, Fusion Middleware Control will return an error.

For example, if you are using a browser that is on a host using the IPv4 protocol and you are using Fusion Middleware Control, Fusion Middleware Control returns an error when you navigate to an entity that is running on a host using the IPv6 protocol, such as in the following situations:

  • From the Oracle Internet Directory home page, you select Directory Services Manager from the Oracle Internet Directory menu. Oracle Directory Services Manager is running on a host using the IPv6 protocol.

  • From a Managed Server home page, you click the link for Oracle WebLogic Server Administration Console, which is running on IPv6.

  • You test Web Services endpoints, which are on a host using IPv6.

  • You click an application URL or Java application which is on a host using IPv6.

To work around this issue, you can add the following entry to the /etc/hosts file:

xxx.xx.xx.xx  myserver-ipv6 myserver-ipv6.example.com

In the example, xxx.xx.xx.xx is the IPv4 address of the Administration Server host, myserver.example.com.

4.1.4 Deploying JSF Applications

Some JSF applications may experience a memory leak due to incorrect Abstract Window Toolkit (AWT) application context classloader initialization in the Java class library. Setting the oracle.jrf.EnableAppContextInit system property to true will attempt eager initialization of the AWT application context classloader to prevent this leak from occurring. By default this property is set to false.

4.2 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds. It includes the following topics:

4.2.1 Configuring Fusion Middleware Control for Windows Native Authentication

To use Windows Native Authentication (WNA) as the single sign-on mechanism between Fusion Middleware Control and Oracle WebLogic Server Administration Console, you must make changes to the following files:

  • web.xml

  • weblogic.xml

These files are located in the em.ear file. You must explode the em.ear file, edit the files, then rearchive the em.ear file. Take the following steps (which assume that while the front end is on Windows, the em.ear file is on UNIX):

  1. Set the JAVA_HOME environment variable. For example:

    setenv JAVA_HOME /scratch/Oracle/Middleware/jrockit_160_05_R27.6.2-20 
    
  2. Change to the directory containing the em.ear, and explode the file. For example:

    cd /scratch/Oracle/Middleware/user_projects/applications/domain_name
    JAVA_HOME/bin/jar xvf em.ear em.war 
    JAVA_HOME/bin/jar xvf em.war WEB-INF/web.xml
    JAVA_HOME/bin/jar xvf em.war WEB-INF/weblogic.xml
    
  3. Edit web.xml, commenting out the first login-config block and uncommenting the login-config block for WNA. (The file contains information about which block to comment and uncomment.) When you have done this, the portion of the file will appear as in the following example:

    <!--<login-config>
         <auth-method>CLIENT-CERT</auth-method>
       </login-config>
    -->  
     <!--
      the following block is for Windows Native Authentication, if you are using
     WNA, do the following:
        1. uncomment the following block
        2. comment out the previous <login-config> section.
        3. you also need to uncomment a block in weblogic.xml
     -->
       <login-config>
         <auth-method>CLIENT-CERT,FORM</auth-method>
         <form-login-config>
           <form-login-page>/faces/targetauth/emasLogin</form-login-page>
           <form-error-page>/login/LoginError.jsp</form-error-page>
         </form-login-config>
       </login-config>
       <security-constraint>
     .
     .
     .
       <security-role>
         <role-name>Monitor</role-name>
       </security-role>
     
    
  4. Edit weblogic.xml, uncommenting the following block. (The file contains information about which block to uncomment.) When you have done this, the portion of the file will appear as in the following example:

    <!--
     the following block is for Windows Native Authentication, if you are using
     WNA, uncomment the following block.
     -->
      <security-role-assignment>
         <role-name>Admin</role-name>
         <externally-defined/>
       </security-role-assignment>
     .
     .
     .
       <security-role-assignment>
         <role-name>Deployer</role-name>
         <externally-defined/>
       </security-role-assignment>
    
  5. Rearchive the em.ear file. For example:

    JAVA_HOME/bin/jar uvf em.war WEB-INF/web.xml
    JAVA_HOME/bin/jar uvf em.war WEB-INF/weblogic.xml
    JAVA_HOME/bin/jar uvf em.ear em.war 
    

4.2.2 Fusion Middleware Control Does Not Keep Column Preferences in Log Viewer Pages

In Fusion Middleware Control, you can reorder the columns in the pages that display log files and log file messages. However, if you navigate away from the page and then back to it, the columns are set to their original order.

4.2.3 Changing Log File Format

When you change the log file format note the following:

  • When you change the log file format from text to xml, specify the path, but omit the file name. The new file will be named log. xml.

  • When you change the log file format from xml to text, specify both the path and the file name.

4.3 Documentation Errata

This section describes documentation errata. It includes the following topic:

4.3.1 Additional Information About Disabling IPv6 for Oracle Web Cache

The Oracle Fusion Middleware Administrator's Guide describes how to disable IPv6 for Oracle Web Cache, which is enabled by default. However, it does not describe how to add the IPV6 element if it does not exist in the webcache.xml file.

If the IPV6 element does not exist in the webcache.xml file, you can add the element to the file. Add it after the MULTIPORT element, as shown in the following example:

...
         <LISTEN IPADDR="ANY" PORT="7786" PORTTYPE="ADMINISTRATION"/>
         <LISTEN IPADDR="ANY" PORT="7788" PORTTYPE="INVALIDATION"/>
         <LISTEN IPADDR="ANY" PORT="7787" PORTTYPE="STATISTICS"/>
      </MULTIPORT>
      <IPV6 ENABLED="NO"/>