| Oracle® Fusion Applications Patching Guide 11g Release 1 (11.1.2) Part Number E16602-09 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Applications Patching Guide 11g Release 1 (11.1.2) Part Number E16602-09 |
|
|
PDF · Mobi · ePub |
This chapter describes how to install and maintain a set of languages in Oracle Fusion Applications.
This chapter contains the following topics:
The provisioning process installs the English language. To add a language at any time after the installation is complete, use the Oracle Fusion Applications Language Pack Installer to install and activate the new language. Installing a language pack is a one-time activity that is required for each language that you add. If patches containing translatable artifacts were previously applied to this environment, you must apply the translated versions of each of those patches after you install the new language.
This section provides an introduction to the following concepts related to language packs:
A language pack for a given language and release contains artifacts at the specific release level that are translated to the specific language. Translated artifacts include Oracle Fusion Applications seed data that is uploaded into Oracle Fusion Applications database, SOA resource bundles, JEE resource bundles, and Applications Policies. You install language packs with Language Pack Installer.
Language Pack Installer enables you to add a language to your Oracle Fusion Applications environment and delivers translated artifacts for that language. You run Language Pack Installer in interactive mode and proceed through the installation by providing information in the user interface when prompted.
Language Pack Installer performs the following tasks:
Stages database artifacts in the patchsettop/dbpatchset directory in the Oracle Fusion Applications Oracle home and calls Oracle Fusion Applications Patch Manager to upload these artifacts to the database
Copies language artifacts to the appropriate directory in FA_ORACLE_HOME
Enables the new language in the FND_LANGUAGES table
Runs the AD Administration process to maintain multi-lingual tables, which prepares the tables for the data to be copied from the source language to the new language
Updates the language content using the database artifacts for the new language that are included in the language pack
Applies the updated translated middleware database content
Deploys Service-Oriented Architecture (SOA) resource bundles
Uploads LDIF translation XLF files to Oracle Internet Directory (OID)
Uses Oracle Fusion Applications Patch Manager to copy and deploy the artifacts described in Table 6-1.
Enables the language
Language Pack Installer supports the installation and automated deployment of most middleware and database artifacts used by Oracle Fusion Applications and related to languages. Depending on the type of artifact included in the Language Pack, the artifact deployment may require manual actions. For more information about manual deployment of these artifacts, see Chapter 4, "Patching Oracle Fusion Applications Artifacts".
Table 6-1 provides a quick reference that depicts how Language Pack Installer supports the Oracle Fusion Applications artifacts that could be included in a Language Pack.
An explanation of the information presented in this table follows:
Automated Actions Performed by Language Pack Installer
Language Pack Installer always copies the artifacts from the Language Pack to the appropriate location on your system. This column describes additional actions that are performed automatically for each artifact.
Actions to Be Performed Manually
This column describes the actions you must perform when the Language Pack includes the specified artifact.
Table 6-1 Artifacts Supported by Language Pack Installer
| Artifact Type | Automated Actions Performed By Language Pack Installer | Actions To Be Performed Manually |
|---|---|---|
|
Translated ADF resource bundles |
Deploy resource bundles |
None |
|
Applications Policies ( |
Deploy changes to the policy store |
Back up the policy store before installation and choose the deployment method during configuration |
|
Oracle Business Intelligence Publisher (Reports and Captions) |
Deploy to the Business Intelligence repository using Catalog Manager, and start the BI Presentation server after patching |
None |
|
Common Resource (Activity Strings) |
None |
None |
|
Flexfields |
Deploy flexfield |
None |
|
LDAP Data (LDIF) |
None |
|
|
Translated content for seed data (XLF) |
Upload translated seed data |
None |
|
SOA Resource Bundle |
Deploy resource bundle and restart dependent composites |
Reset SOA-INFRA MBean property if resource bundle contains human task-mapped attribute labels and standard view names, see Section 4.20, "Patching SOA Resource Bundles". |
During the installation phase, Language Pack Installer copies all of the files from the Language Pack to the Oracle Fusion Applications Oracle home. After the file copy is completed, Language Pack Installer calls Configuration Assistant to perform the remaining tasks required to install and deploy the artifacts included in the Language Pack.
A complete list of possible configuration tasks, including steps within the tasks, follows.
Offline Preverification (Mandatory task)
Performs validation checks while all servers are shutdown. The following validation steps are performed during this task:
Policy Store
Database Content Upload
Activate Language (Mandatory task)
Activates the language in the database and runs the Maintain Multilingual Tables utility to maintain the tables related to the newly activated language. For more information, see Section 10.3.4, "Maintaining Multi-lingual Tables".
Apply Middleware Language Patches
Load Database Components (Mandatory task)
Deploy Applications Policies (jazn-data.xml) (Mandatory task)
Oracle Fusion Applications allows one policy store per language. The jazn-data.xml files in the Language Pack are processed only if you choose to change the policy store language to be the same as that of the Language Pack being installed. Otherwise, this step does not run.
Deploy BI Publisher Artifacts (Mandatory task)
The following steps occur during this task:
Copy captions
Deploy Webcat
Start All Servers
Starts servers that must be running for the deployment of the remaining artifacts in the Language Pack.
Online Preverification (Mandatory task)
Performs validation checks that require all servers to be running. The following validation steps are performed during this task:
Flexfields
LDAP Data (LDIF)
SOA Resource Bundles
Deploy Flexfields
Deploy LDAP Data (LDIF)
Deploy SOA Resource Bundles (Mandatory task)
Restart All SOA Servers
This section describes the following preparation steps for installing a language pack.
The language pack repository contains the language pack installer, translated Oracle Fusion Middleware patches, and the Oracle Fusion Applications language pack that are required to install a language pack for a specific language in an existing Oracle Fusion Applications environment. You download the repository from the Oracle Fusion Applications Product Media Package to a location of your choice. This directory is referred to as REPOSITORY_LOCATION.
Oracle groups its software releases by product area. A Product Media Pack refers to those groupings. Each media pack may also include a zipped file containing electronic documentation files or "Quick Install" files, which facilitate the initial installation of the software.
Once you have completed the software licensing agreements, you can obtain the Oracle Fusion Applications software using one of these two methods:
Oracle Software Delivery Cloud Portal: Provides you with a readme document that helps you to determine which media you need to fulfill the license you have purchased. You download only the media you need. This is the default delivery method.
Oracle Store: Provides a complete set of the software in DVD format. You use only the DVDs covered by your software licensing agreement.
Using either method, you can obtain the Oracle Fusion Applications language pack repository.
Go to http://edelivery.oracle.com/ and follow these instructions:
Complete the Export Validation process by entering basic identification information using the online form.
On the Media Pack Search page, specify the product pack and platform to identify the media pack you want to download. If you do not know the name of the product pack, you can search for it using the license list.
Choose the appropriate media pack from the search results and download the language pack repository (in zipped format). You can download the repository to a location of your choice.
Extract the contents of all zipped files to the same target directory. The directory must be on a networked drive or shared disk so that it will be accessible to all the hosts in your new environment. The installers are normally located in the installers subdirectory under REPOSITORY_LOCATION.
Note:
You should avoid creating the repository in a deeply nested directory on Windows. The Windows PATH variable has a limited size, and long directory names may cause it to overflow. For example, c:\work\my_repository is a better choice than c:\Work\WorkInProgress\FusionApps\FusionAppsv1\Nov2011\tempfiles\my_repository.
Skip this step if you are installing a language pack on a fresh environment where no other patches have been previously applied.
If you previously applied individual patches to your environment before adding a language, then you must apply each corresponding translation patch for the new language. Follow these steps to find the patches to bring the translated content to the same level as the base language:
Run the Patches Applied report to get a list of applied patches. For more information, see Section 3.5.3, "Patches Applied Report".
Search My Oracle Support to find and download the patches that have a translated equivalent patch for each new language. Not all patches contain translated content.
Complete the following prerequisite steps before you install the Language Pack.
Review the Language Pack Release Notes.
Confirm that the open file limit is set properly.
RUP Installer uses multiple workers for uploading database content. The number of workers used dictates the open file limit setting for the machine where you run the RUP Installer. To understand how the number of the workers are calculated and the open file limit setting that is required for the workers, see Section 3.1.2, "Patching Database Artifacts".
Confirm that the SQL*Net Timeout Configuration is set properly.
RUP Installer is tested with a SQL*Net timeout value of 500 to avoid connection timeout issues during uploading of database content. The exact setting in your environment depends on your network configuration and machine resources. To determine the parameters that need to be set, see Section 11.5.8, "Resolving the Error, "Unable to start universal connection pool"".
Confirm registration of the network location of FA_ORACLE_HOME.
If Oracle Fusion Applications Oracle home directory (FA_ORACLE_HOME), which is located under the APPLICATIONS_BASE/fusionapps directory, is registered in inventory with a /net path then provide the oraInst.loc location including /net while starting the RUP Installer.
Language packs must be applied during downtime. Oracle recommends that language packs be installed from a machine that is co-located in the same subnetwork as the database server to maximize performance.
This section contains the steps you perform to install a language pack with Language Pack Installer. It contains the following topics:
To prevent locks on patched objects and other data issues during patching of database artifacts, review and perform the following checklist before installing the language pack:
Stop all servers and processes, except the OPSS Security Store, and the database, before starting the installation. If you want to use the fastartstop utility to do this, see "Starting and Stopping the Oracle Fusion Applications Middle Tier Using the fastartstop Utility" in the Oracle Fusion Applications System Administrator's Guide. Confirm that the BI presentation servers are shut down before starting Language Pack Installer.
The manual shutdown of the Oracle Enterprise Scheduler Service (ESS) server includes the following steps:
Stop the ESS request processor and dispatcher to prevent new requests from being processed. See "Starting and Stopping a Request Processor or Dispatcher" in the Oracle Fusion Applications Administrator's Guide for more information.
Cancel any in-progress requests. See "Cancelling Oracle Enterprise Scheduler Job Requests" in the Oracle Fusion Applications Administrator's Guide for more information.
Shutdown the ESS WebLogic Server Managed server. See the "Starting and Stopping" table, specifically the "Managed Server for an application" row, in the Oracle Fusion Applications Administrator's Guide for more information.
Start the OPSS Security Store if it is not already running. For more information, see "Starting and Stopping Oracle Internet Directory" in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management (Oracle Fusion Applications Edition). If this server is not running prior to starting the installation, the related configuration tasks will fail. For more information, see Section 5.4.5, "LdapServerCheck Failure".
Back up applications and system policies for each stripe supported by Oracle Fusion Applications. If you do not back up the policies by stripe, you cannot restore the policies from your backup. Oracle Fusion Applications supports the following stripes:
fscm_system-jazn-data.xml: FSCM stripe
crm_system-jazn-data.xml: CRM stripe
hcm_system-jazn-data.xml: HCM stripe
bip_jazn-data.xml: OBI stripe
For more information, see "Migrating with the Script migrateSecurityStore" in the Oracle Fusion Middleware Application Security Guide.
Confirm that the database is running and in an idle state.
Confirm that there are no active jobs or processes running against the database
Stop all background jobs, including jobs in the database and active processes
Ensure that all Oracle Fusion Applications Patch Manager processes are complete. From your operating system, check for processes that are running fapmgr, javaworker, adpatch, adadmin, and adworker. If a session was interrupted, you may need to forcefail and abandon the session as follows:
Use the fapmgr forcefail command to update the patching tables.
(UNIX) ...lcm/ad/bin/fapmgr.sh forcefail [-logfile log file name] [-loglevel level] (Windows) ...lcm\ad\bin\fapmgr.cmd forcefail [-logfile log file name] [-loglevel level]
Use the fapmgr abort command to abandon the session:
(UNIX) ...lcm/ad/bin/fapmgr.sh abort [-logfile log file name] [-loglevel level] (Windows) ...lcm\ad\bin\fapmgr.cmd abort [-logfile log file name] [-loglevel level]
Ensure that all Oracle Fusion Applications AutoPatch processes are complete. If one is running, you must abandon the session as follows:
From FA_ORACLE_HOME:
(Unix) adpatch.sh abandon=y interactive=n defaultsfile=FA_ORACLE_HOME/admin/TWO_TASK/defaults_file_name.txt
(Windows) adpatch.cmd abandon=y interactive=n defaultsfile=FA_ORACLE_HOME\admin\TWO_TASK\defaults_file_name.txt
From ATGPF_ORACLE_HOME:
(Unix) adpatch.sh abandon=y interactive=n defaultsfile=ATGPF_ORACLE_HOME/admin/TWO_TASK/defaults_file_name.txt
(Windows) adpatch.cmd abandon=y interactive=n defaultsfile=ATGPF_ORACLE_HOME\admin\TWO_TASK\defaults_file_name.txt
Ensure that all AD Administration sessions are complete. If one is running, you must abandon the session as follows:
From FA_ORACLE_HOME:
(Unix) adadmin.sh abandon=y interactive=n defaultsfile=FA_ORACLE_HOME/admin/TWO_TASK/defaults_file_name.txt
(Windows) adadmin.cmd abandon=y interactive=n defaultsfile=FA_ORACLE_HOME\admin\TWO_TASK\defaults_file_name.txt
From ATGPF_ORACLE_HOME
(Unix) adadmin.sh abandon=y interactive=n defaultsfile=ATGPF_ORACLE_HOME/admin/TWO_TASK/defaults_file_name.txt
(Windows) adadmin.cmd abandon=y interactive=n defaultsfile=ATGPF_ORACLE_HOME\admin\TWO_TASK\defaults_file_name.txt
Back up the FA_ORACLE_HOME directory to restore and restart in case of a non-recoverable failure during the language pack installation.
Ensure that the steps in Section 6.2, "Preparing to Install a Language Pack" and Section 6.3.1, "Before You Begin" are successfully completed before installing the language pack.
You start Language Pack Installer from the command line, using specific options to further define the necessary actions. Table 6-3 shows valid options that can be used when running Language Pack Installer.
(UNIX) REPOSITORY_LOCATION/installers/fusionapps/Disk1/runInstaller -addLangs -jreLoc JAVA_HOME_LOCATION [-invPtrLoc FA_ORACLE_HOME/oraInst.loc] (Windows) REPOSITORY_LOCATION\installers/fusionapps\Disk1\setup.exe -addLangs -jreLoc JAVA_HOME_LOCATION [-invPtrLoc FA_ORACLE_HOME\oraInst.loc]
Table 6-3 Language Pack Installer Command Line Options
| Option Name | Description | Mandatory |
|---|---|---|
|
|
Runs Language Pack Installer |
Yes |
|
|
Path where the Java Runtime Environment is installed. This option does not support relative paths, so you need to specify the absolute path. |
Yes |
|
|
The location of an overriding inventory pointer file. If Oracle Fusion Applications Oracle home directory ( |
No, use only to override the default location of the inventory pointer file, located in |
|
|
Updates the policy store with translated attributes so field descriptions, display names, and other attributes display their translated values |
No, use only when you do not want to use base English |
|
|
Used for getting the debug information from Oracle Universal Installer. |
No |
|
|
Records messages in the log file at the level you specify. Enter a value to override the default log level of |
No, default value is |
Example:
(Unix) REPOSITORY_LOCATION/installers/fusionapps/Disk1/runInstaller -addLangs -jreLoc /server01/appmgr/APPTOP/fusionapps/jdk6 -invPtrLoc FA_ORACLE_HOME/oraInst.loc J-DupdateJAZNPolicyStore=true (Windows) REPOSITORY_LOCATION\installers\fusionapps\Disk1\runInstaller -addLangs -jreLoc \server01\appmgr\APPTOP\fusionapps\jdk6 -invPtrLoc FA_ORACLE_HOME\oraInst.loc J-DupdateJAZNPolicyStore=true
Example when FA_ORACLE_HOME is registered with a /net path:
REPOSITORY_LOCATION/installers/fusionapps/Disk1/runInstaller -addLangs -jreLoc
/server01/appmgr/APPTOP/fusionapps/jdk6 -invPtrLoc /net/APPLICATIONS_BASE/fusionapps/applications/oraInst.loc
Table 6-4 illustrates the tasks that Language Pack installer runs. For information about log files generated during language pack installation, see Section 6.4.1, "Language Pack Installer Log File Directories".
Table 6-4 Language Pack Installation Screen Sequence
| Screen | Description and Action Required |
|---|---|
|
Welcome |
Appears each time you start Language Pack Installer. The standard Welcome screen is read-only. It contains a navigation pane on the left-hand side that summarizes the tasks the installer will take. Each item in the pane represents an installer screen, which contains prompts for the necessary information. No action is required. Click Next to continue. |
|
Installation Location |
Specify the location of the Oracle Fusion Applications home ( Click Next to continue. |
|
Installation Summary |
Summarizes the selections you made during this installation session. It includes the Oracle home, required and available disk space, and the language to be installed. Review the information displayed to ensure that the installation details are what you intend. To make changes before installing, click Back to return to previous screens in the interview. Click Install to start installing this language. |
|
Installation Progress |
Displays a progress indicator that shows the percentage of the installation that is complete and indicates the location of the installation log file. The installation step consists of copying files from the Language Pack to the Oracle home. The configuration process starts when the installation progress indicator shows 100 percent. No user action is required. |
|
Policy Store Analysis Note that this screen displays only when the |
Select the stripes to be analyzed and then click Run Analysis to identify any conflicts or deletions. Only the stripes that are included in the language pack are enabled for analysis and the analysis could run for several minutes. After the analysis runs, review the results of the analysis and decide which deployment method you want Language Pack Installer to use for policy store changes to each stripe. If you decide to resolve the conflicts or deletions before the actual JAZN upload from Language Pack Installer, you should run the Policy Store Analysis step again to get the most accurate analysis report. The choices for deployment method are:
If you choose Apply safe changes only or Append additive changes, then you must review the results of the analysis to manually upload any changes not applied by Language Pack Installer with the choice you selected, after the installation is complete. If you choose Apply all changes and overwrite customizations, then you may need to reapply the customizations that are overwritten after the installation is complete. If you choose one of these options, click Next after you make your selection. If you choose Manually resolve conflicts and upload changes using Authorization Policy Manager (APM), you must bring up the APM application and pause the installation while you go to APM. When you complete this task in APM, shut down the APM application, return to Language Pack Installer, and click Next. |
|
Configuration Progress |
Displays a progress indicator that shows the percentage of the configuration that is complete. It displays each task in the message pane as it is performed. Tasks that could be included in the configuration phase are described in Section 6.1.4, "Language Pack Installer Configuration Tasks". No user action is required unless a failure occurs. For more information, see Section 6.4, "Troubleshooting Language Pack Installer Sessions". |
|
Installation Complete |
Summarizes the installation just completed. If you want to save this configuration to a response file, click Save. For more information, see "How Response Files Work" in the Oracle Database Installation Guide 11g Release 2 (11.2) for Linux. To complete a successful installation, click Finish. If you want to rerun this session after you resolve failed configuration tasks, click Cancel. |
Perform the following required manual steps after Language Pack Installer completes successfully:
Confirm there are no unresolved errors or exceptions in the log files. For information about resolving errors, see Section 6.4, "Troubleshooting Language Pack Installer Sessions".
Confirm that all relevant Managed Servers have a RUNNING status.
Verify that all deployed applications are up and running. You can check this from Oracle Enterprise Manager Fusion Applications Control, or by reviewing the server side log files.
Review the JAZN Analyze report for potential conflicts and deletions that are not patched automatically by the RUP installer.
Use Oracle Fusion Applications Patch Manager to apply the translated standard patches that you downloaded in Step 3, Section 6.2.2, "Downloading Translated Oracle Fusion Applications Patches" For more information, see Section 3.4, "Applying Patches".
This section provides information to assist you in troubleshooting Language Pack Installer sessions. It contains the following topics:
Table 6-5 contains a list of directories for Language Pack Installer activities.
Table 6-5 Log Directories for RUP Installer Activities
| Log directory name | Generated from... |
|---|---|
|
|
Installation phase |
|
|
Configuration phase when database actions run |
|
|
Configuration phase when language is activated |
|
|
StartStop utility |
If Language Pack Installer fails during the installation phase, review the log files to determine the cause of the failure. For more information, see Section 6.4.1, "Language Pack Installer Log File Directories". For more information about how to restart Language Pack Installer, refer to the steps in Section 5.4.2, "Error During the Installation Phase".
If a failure occurs during the configuration phase, you have the option to abort the task or retry the configuration task after resolving the cause of the failure. For more information, see Section 5.4.3, "Error During the Configuration Phase".
When Language Pack Installer notifies you that all database workers failed during the configuration task called Loading Database Tasks, you must start AD Controller to manage the failed workers. For more information, see Section 11.5, "Troubleshooting Patching Sessions for Database Content". After you resolve the issue that caused the workers to fail and you restart the failed worker, you can close the dialog box and Language Pack Installer continues processing.
After running Language Pack Installer, the contents of oraInst.loc were removed.
Language Pack Installer always tries to copy the inventory pointer file specified by the -invPtrLoc option to the Oracle home on which the language pack is to be installed. If you specify an incorrect path for the -invPtrLoc file, the inventory pointer file could result in being an empty file. There are three possible solutions to this issue:
For best results, if you are using the -invPtrLoc option, use it with this value: FA_ORACLE_HOME/oraInst.loc. This avoids a situation where you may inadvertently exclude part of the directory path to the file, as in the case of using a mapped drive. For example, if Oracle home is registered in inventory with a /net path, such as /net/home/oraInst.loc, and you provide /home/oraInst.loc to the invPtrLoc option, the installer interprets the two paths as different. The end result is an empty inventory pointer file.
If FA_ORACLE_HOME is registered in central inventory with a /net path, then you must include /net when specifying the location of the inventory pointer file with the -invPtrLoc option, for example, -invPtrLoc /net/directory_path/oraInst.loc.
Restore from a backup copy of your oraInst.loc file in case the original file is damaged.
You can recover from this error by creating a new oraInst.loc. See the "Creating the oraInst.loc File" section in the relevant Oracle Database installation guide, for example, Oracle Database Installation Guide, 11g Release 2 (11.2) for Linux.
Then click Retry.
Language packs contain BI Publisher artifacts, so the BI Presentation servers should not be running. The following error occurs if the BI Presentation servers are running during the deployment of BI Publisher artifacts:
java.lang.RuntimeException: Webcat patch file creation failed!
To resolve this issue, shut down the BI Presentation servers to release locks on the Oracle BI Presentation Catalog.
Oracle Fusion Applications content is translated to different languages and fixes are made available as individual patches. If your environment uses multiple languages, whenever you apply a patch with translatable content, you must also apply the associated translated patch for each of your installed languages. If a patch does not contain any translated content, such as a PL/SQL package, only the English patch is available.
If an Oracle Fusion Applications environment contains languages other than English, the recommended method for applying patches is to apply the English patch first and then apply the translation patch for each installed language.For example, after you apply a language pack for another language, such as Korean, whenever you apply a patch that involves translatable content, you must apply the base English patch and also the Korean patch for that fix.
For detailed information about how to apply a patch, see Section 3.4, "Applying Patches".
|
 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|