| Oracle® Application Server Release Notes and New Features 10g Release 3 (10.1.3.5.1) Part Number E15342-03 |
|
|
View PDF |
| Oracle® Application Server Release Notes and New Features 10g Release 3 (10.1.3.5.1) Part Number E15342-03 |
|
|
View PDF |
This chapter describes issues associated with Installation. It includes the following topics:
Section 3.3, "DHCP Warning Message with Static IP Addresses (Vista and Windows 2008)"
Section 3.4, "Installer Hangs When It Tries to Restart OPMN (Vista and Windows 2008)"
Section 3.5, "Custom Users and Roles are not Ported from 10.1.3.0.0"
Section 3.8, "Error While Creating Service on Microsoft Windows Platform"
Section 3.11, "Support For 32bit JDK (Sun/Jrockit) on 64bit OS"
Section 3.15, "Unable to Start the Managed Server from WebLogic Console (UNIX)"
Once you install Oracle SOA Suite with Oracle WebLogic Server you cannot uninstall it.
This release of Oracle Application Server is not certified to run on machines that are configured with IPv6. You have to install and run this release of Oracle Application Server on machines that are configured with IPv4.
When installing on a Microsoft Vista or Windows 2008 system with a valid, DNS-registered static IP address, you may see the following error:
A DHCP configuration was detected on this host. The installer also detected that the local hostname and the network hostname differ. Please resolve the networking issues by referring the "Installing on DHCP Computers" section in the installation guide.
This problem occurs if you have multiple network adapters with the same name and one of them is enabled for DHCP.
To work around this issue:
Set a dummy static IP address on the network adapter that is enabled for DHCP.
Restart the installation.
Restore the original network adapter configuration information.
On Microsoft Vista and Windows 2008 systems, when you perform the basic installation type, the installer may hang when it tries to restart OPMN (right before it runs the configuration assistants).
To work around this issue, check the following:
Ensure that you are not running IPv6. By default, Vista and Windows 2008 run IPv6, which is not supported by this release of Oracle Application Server. To disable IPv6:
Remove or comment out the following line in the C:\Windows\System32\drivers\etc\hosts file:
::1 localhost
Deselect IPv6 for all your connections and adapters, using the Network Connection Properties page. The page is available from Control Panel.
Open the Registry Editor.
Create the following registry entry as type DWORD, and set its value to 0xFF:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents
Exit the Registry Editor.
Restart the computer.
Start up the installer from a command shell that was started with "run as Administrator". To do this, right click cmd.exe in Windows Explorer, and select "Run as Administrator".
Bug 7351894
When upgrading from Oracle Application Server version 10.1.3.0.0 to version 10.1.3.5.0, defined users and roles are not automatically migrated from the jazn-data.xml configuration file to the system-jazn-data.xml configuration file. The result is that the defined users and roles no longer exist after upgrading.
To work around this issue:
From the backup of the 10.1.3.0.0 installation, copy the jazn-data.xml file from J2EE_HOME/application-deployments/ascontrol/to some location.
Migrate the users and roles of the jazn-data.xml configuration file to the new system-jazn-data.xml configuration file using the JAZNMigration Tool:
java -cp $ORACLE_HOME/j2ee/home/jazn.jar oracle.security.jazn.tools.JAZNMigrationTool -st xml -dt xml -sf J2EE_HOME/application-deployments/ascontrol/jazn-data.xml -df J2EE_HOME/config/system-jazn-data.xml -sr jazn.com -m all
The Configuration Wizard for the Oracle SOA Suite-Oracle WebLogic Server 10.1.3.5.1 installation does not support the German, French, Italian, Spanish, and Portuguese(Brazil) languages.
When you install Oracle SOA Suite-Oracle WebLogic Server 10.1.3.5.1 on Linux x86_64 operating systems, you will receive an error message during the linking phase.
To workaround the issue:
Login as root user
Move the existing /usr/bin/gcc to /usr/bin/gcc.orig by using the following command:
> $mv /usr/bin/gcc /usr/bin/gcc.orig
Create a new file called gcc41 with the following content:
$vi /usr/bin/gcc41 #!/bin/sh exec /usr/bin/gcc.orig -m32 -static-libgcc -B/usr/lib/gcc/i586-suse-linux/2.95.3/ $*
Note:
The file
i586-suse-linux/2.95.3 is different for the different versions of the Linux operating system Verify the exact file name for the Linux operating system in use. Search for the 32bit directory in the /usr/lib/gcc directory and obtain the exact file name.Change the file permission for the gcc41 file using the following command:
> $chmod 755 /usr/bin/gcc41
Create a symbolic link to gcc using the following command:
> $ln -s -f /usr/bin/gcc41 /usr/bin/gcc
On Microsoft Windows platforms when you install more than one SOA Home, during installation of the second SOA Home, the installer attempts to create an additional service. However, a problem arises because services are already in place due to the previous installation. You will receive an "Error while Creating a Service." message.
To workaround this issue:
You can delete the existing service through Windows Services.
You can continue with the second and other installations; the service will not be created.
After installation, if you see observe the following error message in the OraInventory/logs/*.err file:
"The system cannot find the path specified"
This message can be ignored.
Complete the following steps to use MDS:
Use Multi Data Source (MDS) if the backend is RAC. The MDS should point to instance specific Data sources in turn. The Data source name and the JNDI name used by the app should be set for the MDS in this case. The individual data source names and jndi name can be anything (a suggestion is to use the base name suffixed with monotonically increasing number)
Use Regular data sources if the backend is non-RAC. The Data source name and the JNDI name used by the app should be set for the Data source in this case.
For MDS:
* test-frequency-seconds should be *5*
* data-source-list should point to a list of comma separated child
* algorithm-type* *should be *Load-Balancing
* data sources ("JDBC Data Source-0,JDBC Data Source-1")
You can select 32bit JDK (Sun/Jrockit) on a 64bit Operating System to create the WLS Domain for Oracle SOA Suite during configuration
However, durinng the Oracle SOA Suite installation you need to perform the work around mentioned in the Section 3.7, "Problem During Linking Phase" and invoke the installer in the same manner as discussed in the Oracle SOA Suite Installation Guide for Oracle WebLogic Server.
For the complete list of JDK support, please refer the certification matrix at:
http://www.oracle.com/technology/software/products/ias/files/oracle_soa_certification_101310.html
During the installation of Oracle SOA Suite on rh5.0/oel5.0 computers, you may receive an error regarding the check for display colors:
Could not execute auto check for display colors using command/usr/X11R6/bin/xdpyinfo. Check if the DISPLAY variable is set. Checking if CPU speed is above 300 MHz. Actual 3391 MHz Passed. Some optional pre-requisite checks have failed (see above). Continue? (y/n)
This prerequisite check can be ignored.
If you successfully install one SOA Home 1 and then install a second SOA Home 2, then all shortcuts created for the first SOA installation are overwritten by the second SOA installation. All of the shortcuts are created with the same names.
To workaround this problem, before starting the second installation, rename the created shortcuts created by the installer that are pointing to the SOA Home 1.
You can rename the newly created shortcuts to new name by just adding 10.1.3.5.1.
In the install logs following lines are seen and they can be ignored:
*** Select a Product to Install Page*** Unable to read /scratch/aime1/work/mw886/soa2538/inventory/ContentsXML/comps.xml. Some inventory information may be lost. Setting the 'TopLevelComp ( ToplevelComp )' property to 'oracle.as.j2ee.top, 10.1.3.1.2, >0.0.0.0.0, [ 46 ][OH:2]'. Received the value from the default settings. Unable to read /ade/aime1_dadvfa0975/oracle/work/SOA_10136_ INSTAL/oraInventory/ContentsXML/comps.xml. Some inventory information may be lost.
During the configuration phase, classic installation uses node manager to start the managed servers. So, if installation and configuration is done in one step, the configuration tools fail while starting the managed servers from WebLogic console and show the following error:
Server failed during startup so will not be restarted
It also fails to configure the domain and the node manager start script.
To work around these issues, perform the following steps:
Change the parameter value for $BEAHOME/wlserver_10.3/common/nodemanager/nodemanager.properties file from:
NativeVersionEnabled=true
to
NativeVersionEnabled=false
Set StartScriptEnabled=true
|
 Copyright © 2009, 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|