4 General Management and Security Issues

This chapter describes issues associated with general management and security. It includes the following topics:

• Section 4.1, "Windows Shortcut to createASInstance Command Ignores Input"

• Section 4.2, "Clarification on Output to opmnctl status Command"

• Section 4.3, "Starting and Stopping Requires Administrator Privileges (Vista and Windows 2008)"

• Section 4.4, "Anonymous User not Supported"

• Section 4.5, "Cluster Layer is not Capable of Propagating Configuration Properties"

• Section 4.6, "Benign Error when Managed Server Starts for the First Time"

• Section 4.7, "Error Messages When Starting Managed Server"

• Section 4.8, "Error Message Displayed in Managed Server Logs"

• Section 4.9, "Workaround for Three Minute RAC Delay"

• Section 4.10, "Question Marks in Email"

• Section 4.11, "Documentation Errata"

4.1 Windows Shortcut to createASInstance Command Ignores Input

On Windows, if you create a Windows shortcut to the createASInstance command and invoke the command through the shortcut, and you have an existing configuration in the ORACLE_CONFIG_HOME directory, the createASInstance command prompts for the user input. However, your response, y or n, is ignored.

To work around this problem, you must enter the "Enter" key first, then respond y for overriding the existing configuration, or n for not overriding the existing configuration.

4.2 Clarification on Output to opmnctl status Command

When you use the createInstance command with the -apacheRoot option to create an additional Application Server instance, the status displayed by opmnctl status -l shows two different ports with the same HTTP protocol.

The port starting with 79** is the Apache listening port. The other port is a diagnostic port. Please check the Apache configuration files, such as ohs/conf/httpd.conf and ohs/conf/dms.conf, in the instance home for more details.

4.3 Starting and Stopping Requires Administrator Privileges (Vista and Windows 2008)

On Microsoft Vista and Windows 2008 systems, you must have Administrator privileges when starting and stopping Oracle Application Server.

• To start and stop from the command line using opmnctl, open a DOS window by running cmd.exe as Administrator (right click on cmd.exe and select Run as Administrator).

• To start and stop using the Oracle Application Server shortcuts on the Start menu, right click on the shortcut and select Run as Administrator.

If you do not have Administrator privileges when starting and stopping, you will get an Access Denied error.

4.4 Anonymous User not Supported

The "anonymous" user (i.e. a user who is not authenticated) is not supported as an Oracle Enterprise Manager 10g Application Server Control Console (Application Server Control Console) user. Assigning an administrator role to the anonymous user will result in an unusable Application Server Control Console.

It is possible to assign an Application Server Control Console administrator role (ascontrol_admin, ascontrol_appadmin, or ascontrol_monitor) to the anonymous user either by using the Application Server Control Console user admin pages or by editing the jazn-data.xml file. However, neither of these described role assignments are supported by Oracle.

OC4J denotes the anonymous user as the OC4J user when an application is initiated that does not have an authenticated user. The anonymous user may also be used during EJB RMI access.

4.5 Cluster Layer is not Capable of Propagating Configuration Properties

The DB-based polling cluster layer is capable of propagating domain configuration properties and logger settings. However, the cluster layer is not yet capable of propagating server-wide configuration properties (those found from the BPELAdmin console). The server-wide configuration properties are not stored in the database but are kept in a file within the BPEL installation directory.

The main server-wide configuration properties that are of significance to users are soapServerUrl, soapCallbackUrl and nonFatalConnectionMaxRetry.

4.6 Benign Error when Managed Server Starts for the First Time

When you start the managed server starts for the first time you may observe the following error message:

log4j:ERROR setFile(C:/WORK/mw351/soa22sep/bpel/system/logs/orabpel.log,  false)
call failed.  java.io.FileNotFoundException 

The missing log file orabpel.log is created automatically. During additional managed server starting you should not observe the error.

4.7 Error Messages When Starting Managed Server

When starting your managed server you may see error messages similar to the following:

• <Warning> <EJB> <BEA-010001> <While deploying EJB 'TaskNotificationSender',
  class oracle.bpel.services.workflow.task.notification.MDBTaskNotificationConsumer
  was loaded from the system classpath. As a result, this class cannot be reloaded while
  the server is running. To prevent this behavior in the future, make sure the class is not
  located in the server classpath.>
  When processing WebService module 'esb_console.war'.  Failed to load servlet Class:
  oracle.tip.jbi.servlet.JBIContainerServlet Ignoring: unable to load
  class:java.lang.ClassNotFoundException: oracle.tip.jbi.servlet.
  JBIContainerServlet at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)
  When processing WebService module 'esb_console.war'.  Failed to load servletClass: oracle.tip.jbi.servlet.JBIContainerServlet Ignoring: unable to load class:java.lang.ClassNotFoundException:
  oracle.tip.jbi.servlet.JBIContainerServlet at:weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)
  <Sep 9, 2009 8:53:42 AM UTC> <Warning> <Connector> <BEA-190155> <Compliance
  checking/validation of the resource adapter
  /scratch/aime1/work/mw5764/user_projects/domains/single_managed/servers/soa10g
  _server1/tmp/_WL_user/esbservices/1ginqd/esb-jca-dt.rar resulted in the
  following warnings:
  The ra.xml <resourceadapter-class> class
  'oracle.tip.esb.server.bootstrap.DesignTimeWLResourceAdapter' should
  implement java.io.Serializable but does not.>
  

• When processing WebService module 'worklistxpress.war'.  Failed to load
  servlet Class: WorklistServlets.TaskSearch
  Ignoring: unable to load class:java.lang.ClassNotFoundException:
  WorklistServlets.TaskSearch at:
  weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)
  When processing WebService module 'worklistxpress.war'.  Failed to load
  servlet Class: WorklistServlets.TaskSearch
  Ignoring: unable to load class:java.lang.ClassNotFoundException:
  WorklistServlets.TaskSearch at:
  weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)
  When processing WebService module 'worklistapp.war'.  Failed to load servlet
  Class: worklistapp.servlets.TaskAttachment
  Ignoring: unable to load class:java.lang.ClassNotFoundException: 
  

These error messages can be ignored.

4.8 Error Message Displayed in Managed Server Logs

WS data binding error messages are displayed in the managed server logs during startup.

These error messages are due to a additionaljava-wsdl type mappings to Oracle WebLogic Server in the JAXRPC mapping file for the HWF Webservices applications in the soabpel.ear file.

These error messages are benign and cause no functional impact. The JAXRPC mapping file is not changed for SOA Oracle WebLogic Server. These same mapping files are used for SOA OC4J and SOA Oracle WebLogic Server.

4.9 Workaround for Three Minute RAC Delay

Using the default values for XA datasources in a multi-datasource real application cluster (RAC) setup, there can be up to a 5 min delay observed in processing requests if one of the RAC nodes is brought down.

When running with a RAC database, for each XA Data Source on your system, change the XA Retry Duration variable from the default of 300 seconds to 120 seconds.

4.10 Question Marks in Email

When your Oracle SOA Suite-Oracle WebLogic Server 10.1.3.5.1 installation is running on a native environment, multibyte characters in the email notification subject line are displayed as question marks.

To workaround this issue, change your locale to UTF8 (such as en_US.utf8) and restart the SOA server.

4.11 Documentation Errata

This section describes documentation errata in general management and security documentation. It includes the following topic:

• Section 4.11.1, "Configuring Service Failover"

• Section 4.11.2, "Incorrect Operating System Configuration"

4.11.1 Configuring Service Failover

In the Oracle Application Server Enterprise Deployment Guide 10g for Release 3 (10.1.3.3.0), in Section 3.20, "Configuring Service Failover for the OC4J_ESBDT Instances", Step 4 is incorrect.

For Step 4 run the following opmnctl commands:

• > opmnctl stopall
  

• > opmnctl start
  

• > opmnctl startproc ias-component="<group_name>" process-type=OC4J_ESBDT"
  

By running these opmnctl commands in order service-failover is configured correctly.

Additionally, use the following opmnctl commands to stop and start an OC4J container using service-failover:

• > opmnctl startproc ias-component="<group_name>" process-type=OC4J_ESBDT
  

• > opmnctl stopproc ias-component="<group_name>" process-type=OC4J_ESBDT
  

If you use either of the following opmnctl commands:

• > opmnctl startproc process-type=OC4J_ESBDT
  

• > opmnctl stopproc process-type=OC4J_ESBDT
  

listed in the documentation, service-failover will not work as expected.

4.11.2 Incorrect Operating System Configuration

In Section 7.6, "Generic Apache ", of the Oracle Process Manager and Notification Server Administrator's Guide the listed applicable operating systems is incorrect. The listed configuration for the Oracle HTTP Server process module to manage generic Apache processes is valid for Linux operating systems only.