| Oracle® Application Server Release Notes 10g Release 3 (10.1.3.1.0) for Microsoft Windows (64-Bit) on Intel Itanium Part Number B32229-06 |
|
|
View PDF |
| Oracle® Application Server Release Notes 10g Release 3 (10.1.3.1.0) for Microsoft Windows (64-Bit) on Intel Itanium Part Number B32229-06 |
|
|
View PDF |
This chapter describes installation and their workarounds associated with Oracle Application Server. It includes the following topics:
This section describes issues with installation of Oracle Application Server. It includes the following topics:
Section 2.1.1, "Using the Unified Oracle SOA Suite Installer for the mySOACompany Topology"
Section 2.1.2, "DHCP Warning Message on Vista Systems with Static IP Addresses"
Section 2.1.4, "Response Files Created through the Record Mode Are Not Supported"
Section 2.1.6, "Question Marks in Configuration Assistant Output"
Section 2.1.7, "Error Messages after Setting VIRTUAL_HOST_NAME"
Section 2.1.9, "Middle Tier Installation Failure for Turkish Locale"
Section 2.1.11, "Recommended Locales for Simplified Chinese and Traditional Chinese"
Section 2.1.12, "Icon and URL Link Errors in Spanish and Brazilian Portuguese Language Locales"
Section 2.1.13, "Oracle HTTP Server Welcome Page Displays Only In English"
Section 2.1.15, "Exception in Error Log when Installing MainCD"
Oracle Application Server Enterprise Deployment Guide 10g Release 3 (10.1.3.1.0) describes how to install the mySOACompany topology in a distributed environment, i.e., the various SOA components are installed in separate containers. Oracle recommends this environment for availability and performance isolation reasons. If these issues are not important to you, you may install all of the SOA components in a single container. To do this, launch Oracle Application Server SOA Suite 10.1.3.1.0 installer and select the J2EE Server, Web Server, and SOA Suite installation type.
When installing on a Microsoft Windows Vista 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.
Workaround
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.
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.
If you want to run the installer with a response file (to perform a silent or non-interactive installation), you cannot use response files created through the -record command-line option in the installer, as described in the "Creating Response Files by Using the Record Mode in the Installer" section in the Oracle Application Server Installation Guide. Instead, you must use response files that were created from the provided response file templates; you replace the placeholder values in the template files with your own values.
Sun Microsystems Java Access Bridge enables assistive technologies, such as the JAWS screen reader, to read Java applications running on the Microsoft Windows platform. Assistive technologies can read Java-based interfaces, such as Oracle Universal Installer and Oracle Enterprise Manager 10g Application Server Control.
If you require the use of assistive technologies, you can obtain Java Access Bridge 2.0 at
If you install Oracle Application Server in a language other than English, you may see strings of question mark characters ("?") in output from the configuration assistants. The "?" characters are benign and can be safely ignored.
After successfully completing the Basic Installation with the VIRTUAL_HOST_NAME environment variable set, you may find the following error messages in ORACLE_HOME\opmn\logs\default_group~home~default_group~1:
Warning: Unable to set up connection factory for a resource adapter in esb-dt: Error creating a ResourceAdapter implementation class. Error creating a JavaBean of class 'oracle.tip.esb.server.bootstrap.DesignTimeResourceAdapter: java.lang.RuntimeException: failed to get ESB_HOME: java.lang.NullPointerException Warning: Unable to set up connection factory for a resource adapter in esb-rt: Error creating a ResourceAdapter implementation class. Error creating a JavaBean of class 'oracle.tip.esb.server.bootstrap.RuntimeResourceAdapter: java.lang.RuntimeException: failed to get ESB_HOME: java.lang.NullPointerException log4j:WARN No appenders could be found for logger (org.quartz.simpl.SimpleThreadPool). log4j:WARN Please initialize the log4j system properly.
These error messages are benign and can be safely ignored.
After successful installation of Oracle Application Server, you may find the following error message in the application.log file:
javax.servlet.ServletException: ORABPEL START-UP ERROR!!!!!!!! OraBPEL run-time expected system environment property "orabpel.home".
This error message is benign and can be safely ignored.
Installation of an Oracle Application Server middle-tier fails for Turkish locale.
Oracle recommends that you avoid running the Oracle Universal Installer to install Oracle Application Server using the Turkish locale because some of the installation screens will not be displayed properly and will not be usable.
Oracle Application Server components such as OWSM and BPEL are not functional for the Turkish locale.
After you perform a Basic Installation, or an Advanced Installation of Oracle Application Server with default languages selected, the tabs and buttons in some graphical user interfaces may be displayed as square boxes under the following circumstances:
You have installed Oracle Application Server on the Japanese version of Microsoft Windows and your browser language is Simple Chinese, Traditional Chinese, or Korean.
You have installed Oracle Application Server on the Simple Chinese version of Microsoft Windows and your browser language is Japanese, Traditional Chinese, or Korean.
You have installed Oracle Application Server on the Traditional Chinese version of Microsoft Windows and your browser language is Japanese, Simple Chinese, or Korean.
You have installed Oracle Application Server on the Korean version of Microsoft Windows, and your browser language is Japanese, Simple Chinese, or Traditional Chinese.
You have installed Oracle Application Server on the European version of Microsoft Windows, and your browser language is Simple Chinese, Traditional Chinese, or Korean.
To avoid issues with installation of Oracle Application Server in locales using simplified Chinese and Traditional Chinese, Oracle recommends using:
zh_CN.gbk instead of zh_CN.gb18030 for Simplified Chinese
zh_TW.big instead of zh_TW.eucTW for Traditional Chinese
In advanced Oracle Application Server installations in Spanish and Brazilian Portuguese Language locales, the Rules Control icon is not displayed.
Additionally the URL link to Oracle Application Server is not placed correctly.
There is no Rules control link in Brazilian Portuguese locale installations.
Oracle HTTP Server Welcome page displays in English only following installation of Oracle Application Server.
In order to view the translated Oracle HTTP Server Welcome page, you need to enter you installation information in the following format where <lang> is the language you would like to use to view the Welcome page:
http://<host>.<port>/index.html.<lang>
For example,
http://<host>.<port>/index.html.ja (Japanese)
http://<host>.<port>/index.html.ko (Korean)
http://<host>.<port>/index.html.zh_TW (Traditional Chinese)
http://<host>.<port>/index.html.zh_CN (Simplified Chinese)
http://<host>.<port>/index.html.de (German)
http://<host>.<port>/index.html.fr (French)
http://<host>.<port>/index.html.it (Italian)
http://<host>.<port>/index.html.es (Spanish)
http://<host>.<port>/index.html.pt_BR (Brazilian Portuguese)
The opmnctl stopall command times out if the BPEL schema in your OracleAS Metadata Repository Database contains old schemas.
To fix this issue, run the production irca.sh to load new schemas in the Oracle database.
After successful installation of Oracle Application Server SOA MainCD, you may find the following Exception message in the oraInstallyyyy-mm-dd_hh-mm-ssAM/PM.err file:
java.lang.NumberFormatException: For input string: ""80""at java.lang.NumberFormatException.forInputString(Unknown Source) ...... Returning 0 instead
This exception message is benign and can be safely ignored.
When you install Oracle Application Server, the ONS localport is set to 6101 by default. If you then install Oracle Database on the same host, the database ONS port may also be set to 6101. This results in a port conflict. The workaround is to manually change one of the ONS ports to a different port number after installation. Refer to Oracle Application Server Administrator's Guide for instructions for changing the ONS port number.
Using the Japanese_Japan locale for user opmn startup causes opmn to become unstable because of a logging function problem. instead of using Japanese_Japan, use another language locale, such as American_America.
This section describes issues with Oracle Application Server documentation. It includes the following topics:
Section 2.2.2, "ASG Standalone Kit Runinstaller Location Correction"
Section 2.2.5, "Additional Requirement for /etc/hosts File not Documented"
In the following sections of describes the instances information pertaining to the advanced installation type is also application to the basic installation type:
Section 2.6, "Requirement for Database" mentions the requirements for supported database versions as follows:
"If you are performing an advanced installation of J2EE Server, Web Server and SOA Suite, the database for SOA suite must be one of the following versions".
Section 2.7, "Installing Database Schemas"describes the installation of database schemas as follows:
"If you are performing an advanced installation of the J2EE Server, Web Server and SOA Suite install type"
The following directory location is referenced in section 6.5.4, Installing the OracleAS 10g (10.1.3.1.0) Standalone Install of OracleAS Guard into Oracle Homes of Oracle Application Server Installation Guide:
Disk2\asg\install\runInstaller
The correct directory location is:
Disk2\asg\Disk1\install\runInstaller
In Chapter 2, Section 5.3.2, "Select Installation Type Screen" of the Oracle Application Server Installation Guide, the following incorrect installation requirements were listed in the screenshot of the Select Installation Type page:
J2EE Server, Web Server, and SOA Suite (686 MB)
J2EE Server and Web Server (477 MB)
J2EE Server (459 MB)
Web Server (350 MB)
The correct installation requirements are:
J2EE Server, Web Server, and SOA Suite (1.1 GB)
J2EE Server and Web Server (500 MB)
J2EE Server (475 MB)
Web Server (325 MB)
After installation is complete, the readme.txt is displayed and it contains a typo in the URL in the following section:
Online documentation for Oracle Application Server is available at: http://download.oracle.com/docs/cd/B31017-01/index.htm
The correct URL should be:
http://download.oracle.com/docs/cd/B31017_01/index.htm
The dash (-) in the URL should be an underscore (_) character.
In Chapter 2, "Requirements," of the Oracle Application Server Installation Guide, some additional information regarding the /etc/hosts file is missing.
The following entry must be present in the /etc/hosts file in order for the installation to start oc4j:home:
127.0.0.1 localhost
|
 Copyright © 2007, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
