| Oracle® Fusion Applications Upgrade Guide 11g Release 6 (11.1.6) Part Number E35833-07 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Applications Upgrade Guide 11g Release 6 (11.1.6) Part Number E35833-07 |
|
|
PDF · Mobi · ePub |
This chapter describes how to install and upgrade a set of languages in Oracle Fusion Applications 11g Release 6 (11.1.6).
This chapter contains the following topics:
Oracle Provisioning and RUP Installer install and upgrade only the English language. To add a language or upgrade an existing language, use Language Pack Installer. If patches containing translatable artifacts were previously applied to this environment, you may 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, LDAP data, Diagnostics Test Framework, and BI Presentation Catalog data. You install language packs with Language Pack Installer.
Language Pack Installer enables you to add or upgrade a language in your Oracle Fusion Applications environment and delivers translated artifacts for that language. You can run Language Pack Installer in GUI mode or silent mode. In GUI mode, you proceed through the installation by providing information in the user interface when prompted. For more information, see Section 1.4, "Installer User Interface". In silent mode, progress is reported to the console.
The policy store can maintain attributes in only one language. If you want to override the base English strings in the policy store, you set the -J-DupdateJAZNPolicyStore option (-DupdateJAZNPolicyStore for Windows) to true when you install the Language Pack. The Description and Displayname are the two attributes which are translatable and are loaded in JAZN files in the language pack.
During the installation phase, Language Pack Installer copies all files from the language pack to the appropriate locations, such as Oracle Fusion Middleware home and Oracle Fusion Applications Oracle home. After the file copy is completed, Language Pack Installer starts the Policy Store Analysis, as described in Table 5-5. Then Language Pack Installer calls configuration assistants to perform the remaining tasks required to update and deploy the artifacts included in the language pack. Language Pack Installer supports parallel processing of certain configuration assistants to improve performance. Parallel configuration assistants are organized by groups and all configuration assistants in a group start running at the same time. For more information, see Section 1.4.7, "Parallel Configuration Assistants".
If any tasks fail during the installation phase, refer to Section 6.2, "Troubleshooting Failures During the Installation Phase" for more information.
All mandatory configuration assistants must complete successfully before proceeding to the next configuration assistant. For more information, see Section 6.4, "General Troubleshooting During the Configuration Phase in GUI Mode" and Section 6.5, "General Troubleshooting During the Configuration Phase in Silent Mode".
Table 5-1 provides a list of possible configuration assistants, including steps within the configuration assistants. The Retry Behavior and Troubleshooting column describes what Language Pack Installer does after a configuration assistant fails and you select the Retry button or you restart Language Pack Installer in silent mode. If available, links are provided to relevant troubleshooting sections.
Table 5-1 Configuration Assistants Run by Language Pack Installer
| Name | Mandatory | Description | Retry Behavior and Troubleshooting |
|---|---|---|---|
|
Activate Language |
Yes |
Activates the language in the database. |
Runs Activate Language again. |
|
Preverification |
Yes |
Performs the following validation checks:
|
Runs failed steps. |
|
Synchronize Multilingual Tables |
Yes |
Runs the Maintain Multilingual Tables utility to maintain the tables related to the newly activated language. For more information, see "Maintaining Multi-lingual Tables" in the Oracle Fusion Applications Patching Guide. |
Restart from failure. |
|
Apply Middleware Language Patches |
Yes |
|
Applies the failed patches. See Section 6.8, "Troubleshooting Applying Middleware Patches". |
|
Stop BI Presentation Server |
Yes |
Stops the BI Presentation server. |
Retries stopping the BI Presentation server. |
|
Load Database Components |
Yes |
Uploads the database content packaged in the language pack to the database. |
Runs failed database commands. See Section 6.13, "Troubleshooting Loading Database Components". |
|
Deploy Applications Policies (jazn-data.xml) |
Yes |
Performs the deployment of the updated applications policies, based on your selections during the Policy Store Analysis task. This task runs only if you chose to override the base English strings in the policy store by using the |
Deploys the failed stripes. See Section 6.14, "Troubleshooting Deployment of Applications Policies". |
|
Deploy BI Publisher Artifacts |
Yes |
Using Catalog Manager:
|
Starts from the beginning of the task. See Section 6.15, "Troubleshooting Deployment of BI Publisher Artifacts". |
|
Deploy Flexfields |
No |
Deploys flexfields to the domain that hosts the |
Starts from the beginning of the task. |
|
Deploy LDAP Data (LDIF) |
No |
Uploads LDIF XLIFF translations to the identity store |
Retries failed XLIFF files. |
|
Deploy SOA Resource Bundles |
Yes |
Deploys SOA Resource Bundles to the corresponding SOA servers. |
Deploys failed SOA resource bundles. |
|
Apply Downloaded Language Patches |
Yes |
Applies post-installation patches that you downloaded in the |
Applies failed patches. |
This section describes the following preparation steps for installing a language pack, all of which can be performed before your scheduled down time.
Before you begin the language pack installation, you should have access to the following documentation:
Oracle Fusion Applications Release Notes, 11g Release 6 (11.1.6) from the current release.
Oracle Fusion Applications NLS release notes from the current release.
You should also have a clear understanding of the following directories:
Primordial host: The primordial host is where the Administration Server for the Common Domain runs.
APPLICATIONS_CONFIG: The top-level directory for the Oracle Fusion Applications configuration files.
APPLICATIONS_BASE: The top-level directory for the Oracle Fusion Applications binaries.
FA_ORACLE_HOME: Directory named applications, located under the fusionapps Oracle Fusion Applications Middleware home.
For more information, see Figure 2-1, "Relationship of Home Directories".
The language pack repository contains the language pack installer, translated Oracle Fusion Middleware patches, and the Oracle Fusion Applications language pack contents that are required to install a language pack for a specific language or upgrade an installed 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.
Table 5-2 list the installers in the language pack repository.
Table 5-2 Language Pack Installers
| Media Label Name | Staging Destination |
|---|---|
|
Language Pack Installer |
(Unix) (Windows) or |
Language Pack Installer can apply mandatory post-installation patches that are required by Oracle Fusion Applications if you download the patches from My Oracle Support before you start the installation. Note that this feature relates only to patches that are documented in Oracle Fusion Applications NLS release notes and that are specifically required for the language pack you are installing.
Note:
If there are no post-installation patches in Oracle Fusion Applications NLS release notes when you run Language Pack Installer, there is no action required for this step.
Perform the following steps to download the patches:
If you are installing a language pack after an upgrade, proceed to Step 6 because you already performed some of the steps in this section, while following the steps in Section 2.1.4, "Download Mandatory Post-Release 6 Patches". Otherwise, proceed to Step 2.
Create a directory named 11.1.6.0.0_post_repo_patches in the parent directory of your APPLICATIONS_BASE directory. For example, if APPLICATIONS_BASE is /u01/APPTOP, the patch directory is /u01/11.1.6.0.0_post_repo_patches. For more information about the APPLICATIONS_BASE directory, see Section 2.1.1, "Before You Begin".
Download patch 16065661 from My Oracle Support and unzip the patch to any directory. After unzipping, the patch directory contains two files, PostRepoPatchDirs.zip and postRepoPatchDirsREADME.txt.
Unzip PostRepoPatchDirs.zip in the 11.1.6.0.0_post_repo_patches directory to create the directory structure for the patches you download.
Review the README file that was created when you unzipped PostRepoPatchDirs.zip, to learn how the subdirectories under the 11.1.6.0.0_post_repo_patches directory map to the corresponding components, such as Oracle Fusion Middleware, database client, and database server components.
Refer to Oracle Fusion Applications NLS release notes to find the patches to be downloaded from My Oracle Support.
Table 5-3 describes the types of patches that you download and the configuration assistant that applies the patches.
Download and unzip the patches into the appropriate subdirectory under the 11.1.6.0.0_post_repo_patches directory, based on the mapping information in the README.txt file described in Step 5. A failure could result if you do not download a patch to the correct directory. Note that when you download the Oracle Fusion Applications patches, you must use the Patch Plan feature in My Oracle Support. If you cannot create a patch plan because you do not have Oracle Configuration Manager (OCM) configured, you can create the patch plan by running the script in Step 8.
Run this step if you cannot create a My Oracle Support patch plan. This step assumes that you have downloaded the patches as described in Step 7, without using the Patch Plan feature.
The perl script, adCreateMosPlan.pl, reads the patch metadata from the downloaded patches to generate the patch plan file, mosdownload.xml. To run this script, use the Perl executable from APPLICATIONS_BASE/dbclient/perl/bin for Unix platforms and APPLICATIONS_BASE\dbclient\perl\5.8.3\bin\MSWin32-x64-multi-thread for Windows.
Use the following command syntax to create the patch plan file:
(Unix) setenv PERL5LIB $APPLICATIONS_BASE/dbclient/perl/lib/5.8.3:$APPLICATIONS_BASE/dbclient/perl/lib/site_perl/5.8.3/: $APPLICATIONS_BASE/dbclient/perl/lib/site_perl $APPLICATIONS_BASE/dbclient/perl/bin/perl $APPLICATIONS_BASE/fusionapps/applications/lcm/ad/bin/adCreateMosPlan.pl patches_download_location (Windows) SET PERL5LIB=%APPLICATIONS_BASE%\dbclient\perl\5.8.3;%APPLICATIONS_BASE%\dbclient\perl\site\5.8.3\; %APPLICATIONS_BASE%\dbclient\perl\site %APPLICATIONS_BASE%\dbclient\perl\5.8.3\bin\MSWin32-x64-multi-thread\perl %APPLICATIONS_BASE%\fusionapps\applications\lcm\ad\bin\adCreateMosPlan.pl patches_download_location
If you are installing a language pack on a freshly installed Oracle Fusion Applications environment, ensure that you performed all tasks described in "Postinstallation Tasks" in the Oracle Fusion Applications Installation Guide.
If you are installing a language pack on an upgraded environment, ensure that you completed all tasks described in Chapter 4, "Completing Post-Upgrade Tasks".
In either case, you must also perform the steps in the "Post-Installation" section of Release Notes for Oracle Fusion Applications 11g Release 6 (11.1.6).
Refer to Oracle Fusion Applications Release Notes, 11g Release 6 (11.1.6) for information about database tuning parameters, to avoid time out conditions during the installation.
Ensure that you have your own versions of any customized BI Publisher reports. If a language pack includes an update to a catalog object that was delivered with an Oracle Fusion application, the patch will overwrite any customizations applied to the original report. For more information, see "Before You Begin Customizing Reports" in the Oracle Fusion Applications Extensibility Guide.
You must run Health Checker directly from APPLICATIONS_BASE and from the primordial host. You can run these checks any number of times prior to your down time.
For more information about Health Checker, see Section 1.5.1, "Pre-Upgrade Tasks Performed by Health Checker Before Down Time".
Perform the following steps to run Health Checker:
Download and apply patch 16068097 before running Health Checker for language packs. Follow the steps in the README.txt file in this patch.
Set the APPLICATIONS_BASE environment variable to point to the directory that contains Oracle Fusion Applications. For example, if Oracle Fusion Applications is installed in /server01/APPTOP/fusionapps, then set the environment variable APPLICATIONS_BASE to /server01/APPTOP.
(Unix) setenv APPLICATIONS_BASE /server01/APPTOP/ (Windows) SET APPLICATIONS_BASE=\server01\APPTOP\
Run Health Checker.
(Unix) $APPLICATIONS_BASE/fusionapps/applications/lcm/hc/bin/hcplug.sh -manifest $APPLICATIONS_BASE/fusionapps/applications/lcm/hc/config/PreDowntimeChecks.xml [-DlogLevel=log_level] (Windows) %APPLICATIONS_BASE%\fusionapps\applications\lcm\hc\bin\hcplug.cmd -manifest %APPLICATIONS_BASE%\fusionapps\applications\lcm\hc\config\PreDowntimeChecks.xml [-DlogLevel=log_level]
Review the Health Checker log file or the HTML summary report to see if any errors occurred that require corrective action. The log file and the HTML summary are located in APPLICATIONS_CONFIG/fapatch/logs/release_version/healthchecker. Note that the following checks do not apply to Language Pack Installer and any errors that are reported for these checks can be ignored:
Verify Oracle Fusion Applications Version
Verify Free and Total Memory
Check Repository Integrity
After you resolve the issue that caused the error, start Health Checker again to run the failed tasks. You must rerun Health Checker until there are no failed tasks.
For more information, see Section 6.25, "Troubleshooting Health Checker Pre-Down Time Checks".
This section describes the following mandatory preparation steps for installing a language pack, all of which must be performed during your system down time. Language Pack Installer does not require any servers to be shut down. However, no users should be online, so it is still considered to be down time.
This section contains steps to follow for all platforms.
Confirm that all servers are up and running before installing the language pack.
Confirm that the OPMN control process and Node Manager are running. If they are not running, follow the steps in Table 3-3, "RUP Installer Screen Sequence for the Second Installer" under "Welcome" to start them.
Start the OPSS Security Store if it is not already running. The OPSS Security Store used here is an Oracle Internet Directory LDAP server instance. Before proceeding with the installation, the designated Oracle Internet Directory server instance must be up and running. If this server is not running prior to starting the installation, the related configuration assistants will fail.
For more information about starting, see "Starting and Stopping Oracle Internet Directory" in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management (Oracle Fusion Applications Edition).
You must run Health Checker directly from APPLICATIONS_BASE and from the primordial host.
For more information about Health Checker, see Section 1.5.2, "Pre-Upgrade Tasks Performed by Health Checker During Down Time".
Perform the following steps to run Health Checker:
Set the APPLICATIONS_BASE environment variable to point to the directory that contains Oracle Fusion Applications. For example, if Oracle Fusion Applications is installed in /server01/APPTOP/fusionapps, then set the environment variable APPLICATIONS_BASE to /server01/APPTOP.
(Unix) setenv APPLICATIONS_BASE /server01/APPTOP/ (Windows) SET APPLICATIONS_BASE=\server01\APPTOP\
Run Health Checker.
$APPLICATIONS_BASE/fusionapps/applications/lcm/hc/bin/hcplug.sh -manifest $APPLICATIONS_BASE/fusionapps/applications/lcm/hc/config/PreUpgradeDowntimeChecks.xml [-DlogLevel=log_level] (Windows) %APPLICATIONS_BASE%\fusionapps\applications\lcm\hc\bin\hcplug.cmd -manifest %APPLICATIONS_BASE%\fusionapps\applications\lcm\hc\config\PreUpgradeDowntimeChecks.xml [-DlogLevel=log_level]
Review the Health Checker log file or the HTML summary report to see if any errors occurred that require corrective action. The log file and the HTML summary are located in APPLICATIONS_CONFIG/fapatch/logs/release_version/healthchecker.
After you resolve the issue that caused the error, start Health Checker again to run the failed tasks. You must rerun Health Checker until there are no failed tasks.
For more information, see Section 6.26, "Troubleshooting Health Checker Down Time Checks".
To prevent an error during the language pack installation, you must temporarily enable anonymous binds in Oracle Internet Directory. To enable all anonymous binds on the Oracle Internet Directory instance with componentName oid1 using ldapmodify, run the following command:
ldapmodify -D cn=orcladmin -Q -p portNum -h hostname -f ldifFile
with an LDIF file such as the following example:
dn: cn=oid1,cn=osdldapd,cn=subconfigsubentry changetype: modify replace: orclAnonymousBindsFlag orclAnonymousBindsFlag: 1
You can also use Oracle Enterprise Manager Fusion Middleware Control to enable anonymous binds. For more information, see "Managing Anonymous Binds" in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory. You will disable anonymous binds after the upgrade by setting the value of the orclAnonymousBindsFlag to 0.
Back up your entire Oracle Fusion Applications environment by following the steps in "Backing Up and Recovering Oracle Fusion Applications" in the Oracle Fusion Applications Administrator's Guide. You should also back up your central inventory.
For additional back up steps that are specific to Windows, refer to Section 2.2.7.3, "Back Up Steps for Windows Platforms".
Set the REPOSITORY_LOCATION environment variable to point to the root directory where the repository is staged.
Examples follow:
(Unix) setenv REPOSITORY_LOCATION /server01/LPRepo/ (Windows) SET REPOSITORY_LOCATION=\server01\LPRepo\
Note:
Set this environment variable and the APPLICATIONS_BASE environment variable, described in Section 5.3.2, "Run Health Checker for Down Time Checks", on all hosts that share the same APPLICATIONS_BASE before executing all tools and utilities mentioned in this guide.
Download and apply any prerequisite patches listed in the Post-Installation and Post-Upgrade sections of Oracle Fusion Applications Release Notes, 11g Release 6 (11.1.6) prior to starting Language Pack Installer. Note that the only patches that need to be applied are those that have been added to the release notes since the last time you applied patches from this list.
Language Pack Installer does not require any servers to be shut down. However, no users should be online, so it is still considered to be down time. 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. You must run Language Pack Installer on the primordial host. Primordial host is defined in Section 5.2.1, "Before You Begin".
Ensure that the steps in Section 5.2, "Pre-Upgrade Steps - Before Down Time" and Section 5.3, "Pre-Upgrade Steps - During Down Time" are successfully completed before you start Language Pack Installer.
Language Pack Installer supports GUI mode and silent mode. In GUI mode, you navigate through screens that display the progress of the upgrade, including log file locations and status messages. In silent mode, Language Pack Installer reports the progress of the upgrade as console output.
Note:
If Language Pack Installer encounter errors, refer to Section 5.6, "Troubleshoot Language Pack Installer Sessions" before clicking any buttons in the Language Pack Installer user interface.
Perform the following steps to run Language Pack Installer in GUI mode from the command line, using specific options to further define the necessary actions. You must run Language Pack Installer from the primordial host.
Set the JAVA_HOME environment variable as follows:
(Unix) setenv JAVA_HOME APPLICATIONS_BASE/fusionapps/jdk6 (Windows) set JAVA_HOME=APPLICATIONS_BASE\fusionapps\jdk6
Confirm registration of the network location of FA_ORACLE_HOME.
If the Oracle Fusion Applications Oracle home directory (FA_ORACLE_HOME), which is APPLICATIONS_BASE/fusionapps/applications, is registered in the central inventory with a /net path, then provide the oraInst.loc location including /net when starting Language Pack Installer. An example follows:
(Unix only) $REPOSITORY_LOCATION/installers/fusionapps/Disk1/runInstaller -jreLoc APPLICATIONS_BASE/fusionapps/jdk6/ -invPtrLoc /net/APPLICATIONS_BASE/fusionapps/applications/oraInst.loc
If not triggered with a /net path, Language Pack Installer copies the -invPtrLoc file to FA_ORACLE_HOME. This results in a copy of the file to itself, which then becomes an empty or zero byte file. As a result, the copy phase will fail when oracle_common patches are applied. For more information, see Section 6.2.4, "Inventory Pointer File is Empty".
Run the following command to start Language Pack Installer in GUI mode.
(UNIX) $REPOSITORY_LOCATION/installers/fusionapps/Disk1/runInstaller -addLangs -jreLoc APPLICATIONS_BASE/fusionapps/jdk6 [-J-DpatchDownloadLocation=location_of_11.1.6.0.0_post_repo_patches_directory] [-invPtrLoc FA_ORACLE_HOME/oraInst.loc] [-J-Dworkers=number_of_workers][-J-DlogLevel=level] [-J-DserverStartTimeout=timeout_period_for_server_in_seconds] [-J-DupdateJAZNPolicyStore=true] [-debug] (Windows) %REPOSITORY_LOCATION%\installers\fusionapps\Disk1\setup.exe -addLangs -jreLoc APPLICATIONS_BASE\fusionapps\jdk6 [-DpatchDownloadLocation=location_of_11.1.6.0.0_post_repo_patches_directory] [-Dworkers=number_of_workers][-DlogLevel=level] [-DserverStartTimeout=timeout_period_for_server_in_seconds] [-DupdateJAZNPolicyStore=true] [-debug]
Table 5-4 shows valid options that can be used when running Language Pack Installer.
Table 5-4 Language Pack Installer Command Line Options
| Option Name | Description | Mandatory |
|---|---|---|
|
|
Runs Language Pack Installer to install one language. |
Yes |
|
|
Path where the Java Runtime Environment is installed. This option does not support relative paths, so you must specify the absolute path. |
Yes |
|
|
The location of an overriding inventory pointer file. If the Oracle Fusion Applications Oracle home directory ( |
Recommended, use to override the default location of the inventory pointer file, located in |
|
( |
The directory path where you downloaded mandatory prerequisite patches to be applied by Language Pack Installer. See Section 5.2.3, "Download Mandatory Post-Installation NLS Patches". |
Yes, if you are applying downloaded patches. Provide the full path to the |
|
( |
The number of workers to use for uploading database content. If you provide a value for the number of workers that is outside the calculated range, you are prompted to provide a value that is within the optimal range. If you do not use this option, a calculated optimal value is used. |
No, overrides the default number of workers calculated by Language Pack Installer. |
|
|
Configures the timeout value for server in seconds. |
No, overrides the default value for server timeout. |
|
( |
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 |
|
( |
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 in the policy store. |
|
|
Retrieve debug information from Language Pack Installer. |
No. |
Example 5-1 Language Pack Installation with no policy store translation
(Unix) $REPOSITORY_LOCATION/installers/fusionapps/Disk1/runInstaller -addLangs -jreLoc APPLICATIONS_BASE/fusionapps/jdk6 -invPtrLoc FA_ORACLE_HOME/oraInst.loc -J-DpatchDownloadLocation=location_of_11.1.6.0.0_post_repo_patches_directory (Windows) %REPOSITORY_LOCATION%\installers\fusionapps\Disk1\setup.exe -addLangs -jreLoc APPLICATIONS_BASE\fusionapps\jdk6 -DpatchDownloadLocation=location_of_11.1.6.0.0_post_repo_patches_directory
Example 5-2 Language Pack Installation with policy store translation
(Unix) $REPOSITORY_LOCATION/installers/fusionapps/Disk1/runInstaller -addLangs -jreLoc APPLICATIONS_BASE/fusionapps/jdk6 -invPtrLoc FA_ORACLE_HOME/oraInst.loc -J-DupdateJAZNPolicyStore=true -J-DpatchDownloadLocation=location_of_11.1.6.0.0_post_repo_patches_directory (Windows) %REPOSITORY_LOCATION%\installers\fusionapps\Disk1\setup.exe -addLangs -jreLoc APPLICATIONS_BASE\fusionapps\jdk6 -DupdateJAZNPolicyStore=true -DpatchDownloadLocation=location_of_11.1.6.0.0_post_repo_patches_directory
Example 5-3 Language Pack installation when FA_ORACLE_HOME is registered with a /net path
(Unix) $REPOSITORY_LOCATION/installers/fusionapps/Disk1/runInstaller -addLangs -jreLoc APPLICATIONS_BASE/fusionapps/jdk6 -invPtrLoc /net/APPLICATIONS_BASE/fusionapps/applications/oraInst.loc -J-DpatchDownloadLocation=location_of_11.1.6.0.0_post_repo_patches_directory
Table 5-5 illustrates the tasks that Language Pack Installer runs. For information about troubleshooting Language Pack Installer errors and log files, see Section 5.6, "Troubleshoot Language Pack Installer Sessions".
Table 5-5 Language Pack Installer Screen Sequence
| Screen | Description and Action Required |
|---|---|
|
Welcome |
Appears when you start Language Pack Installer. This screen does not appear if you restart Language Pack Installer after a failure. 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. Click Next to continue. |
|
Installation Location |
Specify the location of the existing 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 phase that is complete and indicates the location of the installation log file. The installation phase consists of copying files from the language pack to the appropriate Oracle homes. When the installation progress indicator shows 100 percent, click Next to continue. |
|
Policy Store Analysis (Note that this screen displays only when the |
Analysis is available for the following policy store stripes: hcm, crm, fscm, and obi. 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 to determine which deployment method you want Language Pack Installer to use for policy store changes to each stripe. Oracle recommends that you select Apply safe changes only. This is the safest method unless you have read and totally understood the consequences of the other three options. 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 pause the installation while you bring up the APM application and upload the changes. For more information, see the "Upgrading Oracle Fusion Applications Policies" chapter in the Oracle Fusion Middleware Oracle Authorization Policy Manager Administrator's Guide (Oracle Fusion Applications Edition). Note the location of the following files:
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 phase that is complete. It displays each configuration assistant in the message pane as it is performed. Configuration assistants that could be included in the configuration phase are described in Section 5.1.4, "Language Pack Installer Configuration Assistants". No additional user action is required in the Configuration Progress screen unless a failure occurs. For more information, see Section 6.4, "General Troubleshooting During the Configuration Phase in GUI Mode". Links to troubleshooting specific failures are available in Table 5-1. |
|
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. The Finish button is activated only if all mandatory configuration assistants completed successfully. If you want to rerun this session after you resolve failed configuration assistants, click Cancel. |
Proceed to Section 5.5, "Complete the Post-Installation Tasks".
Perform the following steps to start Language Pack Installer in silent mode from the command line, using specific options to further define the necessary actions. You must run Language Pack Installer from the primordial host.
Create a response file named silent.rsp to be used in silent mode. This file can be located in any directory that is accessible while launching Language Pack Installer. An example silent.rsp file follows:
ORACLE_HOME=/u01/APPLTOP/fusionapps/applications CRM_SELECTED_JAZN_MIGRATION_TYPE=PATCH_POLICY FSCM_SELECTED_JAZN_MIGRATION_TYPE=PATCH_POLICY HCM_SELECTED_JAZN_MIGRATION_TYPE=PATCH_POLICY OBI_SELECTED_JAZN_MIGRATION_TYPE=PATCH_POLICY
Note:
The stripe_SELECTED_JAZN_MIGRATION_TYPE property allow you to choose which deployment method Language Pack Installer will use for policy store changes to each stripe. The following choices are available:
PATCH_POLICY: Apply safe changes only. This is the recommended method. Choose this method if there are no conflicts.
MIGRATE_POLICY_OVERRIDE: Apply all changes and overwrite customizations.
MIGRATE_POLICY_NO_OVERRIDE: Append additive changes.
MIGRATE_POLICY_APM: Manually resolve conflicts and upload changes using Authorization Policy Manager (APM)
If you choose PATCH_POLICY or MIGRATE_POLICY_NO_OVERRIDE, then you must review the results of the analysis to manually upload any changes not applied by Language Pack Installer, based on the choice you selected, after the upgrade is complete. If you choose MIGRATE_POLICY_OVERRIDE, then you may need to reapply the customizations that are overwritten after the upgrade is complete.
If you choose MIGRATE_POLICY_APM, you must pause the upgrade while you bring up the APM application and upload the changes. For more information, see the "Upgrading Oracle Fusion Applications Policies" chapter in the Oracle Fusion Middleware Oracle Authorization Policy Manager Administrator's Guide (Oracle Fusion Applications Edition). Note the location of the following files:
Baseline file: FA_ORACLE_HOME/admin/JAZN/stripe/baseline
Patch file for fscm, crm, and hcm stripes: FA_ORACLE_HOME/stripe/deploy/system-jazn-data.xml
Patch file for the obi stripe: FA_ORACLE_HOME/com/acr/security/jazn/bip_jazn-data.xml
Set the JAVA_HOME environment variable as follows:
(Unix) setenv JAVA_HOME APPLICATIONS_BASE/fusionapps/jdk6 (Windows) set JAVA_HOME=APPLICATIONS_BASE\fusionapps\jdk6
Confirm the registration of the network location of FA_ORACLE_HOME.
If the Oracle Fusion Applications Oracle home directory (FA_ORACLE_HOME), which is APPLICATIONS_BASE/fusionapps/applications, is registered in the central inventory with a /net path, then provide the oraInst.loc location including /net when starting Language Pack Installer. An example follows:
$REPOSITORY_LOCATION/installers/fusionapps/Disk1/runInstaller -addLangs -jreLoc APPLICATIONS_BASE/fusionapps/jdk6/ -invPtrLoc /net/APPLICATIONS_BASE/fusionapps/applications/oraInst.loc -silent -response location_of_response_file JAZN_EXIST=true
If not triggered with a /net path, Language Pack Installer copies the -invPtrLoc file to FA_ORACLE_HOME. In the example, this results in a copy of the file to itself, which then becomes an empty or zero byte file. As a result, the copy phase will fail when oracle_common patches are applied. For more information, see Section 6.2.4, "Inventory Pointer File is Empty".
Run the following command to start Language Pack Installer in silent mode:
Note:
If Language Pack Installer encounters errors in silent mode, it terminates the session. You must resolve the issue that caused the failure and then restart Language Pack Installer, using the same command you used previously. Language Pack Installer then restarts from the first failed task. For more information, see Section 6.5, "General Troubleshooting During the Configuration Phase in Silent Mode".
(UNIX) $REPOSITORY_LOCATION/installers/fusionapps/Disk1/runInstaller -addLangs -jreLoc APPLICATIONS_BASE/fusionapps/jdk6 [-invPtrLoc FA_ORACLE_HOME/oraInst.loc] -silent -response location_of_silent.rsp_file JAZN_EXIST=true [-J-DpatchDownloadLocation=location_of_11.1.6.0.0_post_repo_patches_directory] [-J-Dworkers=number_of_workers][-J-DlogLevel=level] [-J-DserverStartTimeout=timeout_period_for_server_in_seconds] [-debug] (Windows) %REPOSITORY_LOCATION%\installers\fusionapps\Disk1\setup.exe -addLangs -jreLoc APPLICATIONS_BASE\fusionapps\jdk6 -silent -response location_of_silent.rsp_file JAZN_EXIST=true [-DpatchDownloadLocation=location_of_11.1.6.0.0_post_repo_patches_directory ] [-DserverStartTimeout=timeout_period_for_server_in_seconds] [-Dworkers=number_of_workers][-DlogLevel=level][-debug]
Table 5-6 shows valid options that can be used when running Language Pack Installer in silent mode.
Table 5-6 Language Pack Installer Command Options in Silent Mode
| Option Name | Description | Mandatory |
|---|---|---|
|
|
Runs Language Pack Installer to install one language. |
Yes |
|
|
Path where the Java Runtime Environment is installed. This option does not support relative paths, so you must specify the absolute path. |
Yes |
|
|
The location of an overriding inventory pointer file. If the Oracle Fusion Applications Oracle home directory ( |
Recommended, use to override the default location of the inventory pointer file, located in |
|
|
Run Language Pack Installer in silent mode. |
Yes. |
|
|
The location of the response file, |
Yes. |
|
( |
The directory path where you downloaded mandatory prerequisite patches to be applied by Language Pack Installer. See Section 5.2.3, "Download Mandatory Post-Installation NLS Patches". |
Yes, if you are applying downloaded patches. Provide the full path to the |
|
( |
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 in the policy store. |
|
|
Required for the Deploying Applications Policies configuration task. |
Yes, set to true, only when J-DupdateJAZNPolicyStore=true. |
|
( |
The number of workers to use for uploading database content. If you provide a value for the number of workers that is outside the calculated range, you are prompted to provide a value that is within the optimal range. If you do not use this option, a calculated optimal value is used. |
No, overrides the default number of workers calculated by Language Pack Installer. |
|
|
Configures the timeout value for server in seconds. |
No, overrides the default value for server timeout. |
|
( |
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 |
|
|
Retrieve debug information from Language Pack Installer. |
No |
Proceed to Section 5.5, "Complete the Post-Installation Tasks".
Perform the following required manual steps after Language Pack Installer completes successfully:
Confirm that all database artifact deployments were successful by reviewing the Diagnostics report and log files. For more information, see "Diagnostics Report" in the Oracle Fusion Applications Patching Guide.
Confirm there are no unresolved errors or exceptions in the log files. For information about resolving errors, see Section 5.6, "Troubleshoot Language Pack Installer Sessions".
Note:
If you are installing more than one language in an environment, you need to bounce servers only once at the end of installing all languages in that environment, to minimize time spent bouncing servers.
Bounce all servers using the fastarstop script "bounce" option. For more information, see "fastartstop Syntax" and "Starting Examples with fastartstop" in the Oracle Fusion Applications Administrator's Guide.
Verify that all deployed applications are up and running. You can check this from Fusion Applications Control, or by reviewing the server side log files. For more information, see "Starting Fusion Applications Control" in the Oracle Fusion Applications Administrator's Guide or Table 5-7, "Log Directories for Language Pack Installer Activities".
Disable the anonymous binds that you enabled in Section 5.3.3, "Enable Anonymous Binds in Oracle Internet Directory".
Update the LDIF file so that the orclAnonymousBindsFlag has a value of 0.
Run the following command:
ldapmodify -D cn=orcladmin -Q -p portNum -h hostname -f ldifFile
For more information, see "Managing Anonymous Binds" in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.
Follow this step if you have customized BI Publisher reports.
Reload custom templates for BI Publisher reports on Oracle-delivered BI Publisher reports by following the steps in "Task: Upload the Template File to the Report Definition" in the Oracle Fusion Applications Extensibility Guide.
Perform this step only if the J-DupdateJAZNPolicyStore option was set to true when you ran Language Pack Installer. For details about this step, see Section 4.10, "Review Policy Story (JAZN) Analysis Reports"
Perform any steps listed in the Post-Installation Tasks section of Oracle Fusion Applications NLS release notes.
For troubleshooting issues that are generic to both RUP Installer and Language Pack Installer, see Chapter 6, " Troubleshooting the Upgrade". See Table 5-7 for a list of log directories for Language Pack Installer activities.
Table 5-7 Log Directories for Language Pack Installer Activities
| Log directory name | Description |
|---|---|
|
|
Installation phase logs. |
|
|
Top level directory for Language Pack Installer logs. |
|
|
Top level log directory for configuration assistants. A log file exists for each configuration assistant. For more information, see Section 6.1.1, "Log Files for Configuration Assistants". |
|
|
Loading Database configuration assistant logs. |
|
|
Activate Language configuration assistant logs. |
|
|
Apply Downloaded Language Patches configuration assistant logs. |
|
|
StartStop utility logs. |
|
|
Log files from SOA Composite activities. Note that SOA server logs are located under respective domains. For example, the SOA server logs for CommonDomain are under |
|
 Copyright © 2011, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
