3 Installation Issues

This chapter describes installation and their workarounds associated with Oracle Application Server. It includes the following topics:

• Section 3.1, "Installation Issues"

3.1 Installation Issues

This section describes issues with installation of Oracle Application Server. It includes the following topics:

• Section 3.1.1, "Java Access Bridge"

• Section 3.1.2, "Question Marks in Configuration Assistant Output"

• Section 3.1.3, "Error Messages after Setting VIRTUAL_HOST_NAME"

• Section 3.1.4, "Error Message in application.log File"

• Section 3.1.5, "Middle Tier Installation Failure for Turkish Locale"

• Section 3.1.6, "Graphical User Interface Issue"

• Section 3.1.7, "Recommended Locales for Simplified Chinese and Traditional Chinese"

• Section 3.1.8, "Icon and URL Link Errors in Spanish and Brazilian Portuguese Language Locales"

• Section 3.1.9, "Oracle HTTP Server Welcome Page Displays Only In English"

• Section 3.1.10, "opmnctl Command Time Out with Old Data"

• Section 3.1.11, "Exception in Error Log when Installing MainCD"

3.1.1 Java Access Bridge

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 http://java.sun.com/products/accessbridge/ .

3.1.2 Question Marks in Configuration Assistant Output

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.

3.1.3 Error Messages after Setting VIRTUAL_HOST_NAME

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.

3.1.4 Error Message in application.log File

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.

3.1.5 Middle Tier Installation Failure for Turkish Locale

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.

3.1.6 Graphical User Interface Issue

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.

3.1.7 Recommended Locales for Simplified Chinese and Traditional Chinese

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

3.1.8 Icon and URL Link Errors in Spanish and Brazilian Portuguese Language Locales

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.

3.1.9 Oracle HTTP Server Welcome Page Displays Only In English

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)

3.1.10 opmnctl Command Time Out with Old Data

The opmnctl stopall command times out if the BPEL schema in your OracleAS Metadata Repository Database contains old schemas.

To workaround this issue, run the production IRCA (???) to load new schemas in the OracleAS Metadata Repository.

3.1.11 Exception in Error Log when Installing MainCD

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.