Skip Headers
Oracle® Fusion Middleware Release Notes
11g Release 1 (11.1.1) for IBM AIX on POWER Systems (64-Bit)

Part Number E14771-27
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
View PDF

56 Oracle AIA Foundation Pack

This chapter describes issues associated with Oracle AIA Foundation Pack. It includes the following topics:

The issues and workarounds listed here are those that were known at the time of the product's initial release to the public. Additional issues and workarounds may have been discovered since the initial release. View the latest known issues associated with Oracle Application Integration Architecture Foundation Pack on Oracle Technology Network (OTN) at: http://www.oracle.com/technetwork/middleware/docs/aiasoarelnotes-196861.html

56.1 General Issues and Workarounds

This section describes general issues and workarounds. It includes the following topic:

56.1.1 Enabling Coherence Cache for AIA Cache

In AIA, the configuration properties file which is stored in MDS is cached in memory. This cache is referred to by AIA XPath functions. The file is stored in MDS and its cached contents are kept in sync. To monitor the changes that are being made to MDS, Foundation Pack has implemented MDS-change listeners. MDS-change listeners update Foundation Pack's proprietary Cache implementation:

  • In a single-node deployment, only the cache of that node is updated.

  • In a cluster deployment, the cache in all the nodes is updated.

Foundation Pack provides an option to use Oracle Coherence for caching. Coherence is an in-memory distributed data grid solution for clustered applications. Using coherence, a 'distributed' cache is effectively implemented for a cluster-scenario.

Coherence is set up by default on a SOA managed server. When coherence is enabled, the configuration properties file which is stored in MDS is cached in the coherence store. Foundation Pack keeps them in sync; the Foundation Pack's MDS-change listener updates the coherence's cache when changes are made to the file in the MDS.

AIA recommends Coherence-enablement as the best practice in a cluster deployment.

To enable coherence add following lines at the bottom of <FMW_HOME>/user_projects/domains/soainfra/bin/setSOADomainEnv.sh.

EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES} -DenableCoherenceCache=true"

export EXTRA_JAVA_PROPERTIES

And then bounce the SOA-server.

56.2 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds. It includes the following topics:

56.2.1 After Upgrade, META-INF In AIA Harvester Directory was not Removed

The upgrade installation contains an old directory which should be removed: $AIA_HOME/Infrastructure/LifeCycle/AIAHarvester/META-INF. The side effect of this directory is it will trigger JNDI lookup for MDS no matter what, and it will need remote JDBC enabled. PLW Import/Export should not do any MDS lookup, however without removing the directory it will automatically trigger the MDS lookup.

56.2.2 Config Wizard PLW Seed Data Failing in Case of FP Upgrade on Cluster

After the upgrade installation, AIAHome/Infrastructure/LifeCycle/AIAHarvester contains a directory META-INF. This directory should be removed.

56.2.3 Several Optional Fields are Currently Required in Config Wizard

On the Oracle Data Integrator Access Details screen there are no mandatory fields in the application pages. Validation associated with required fields has been removed to address overlapping requirements between PIPs, where one PIP would require the validation and another would not. The validations are now limited to the type and range of the values.Earlier, AIA defaulted previously entered information in the passwords and encrypted fields, along with other fields. As a part of the security guidelines, passwords and encrypted fields are no longer defaulted.

56.2.4 Usability Issue in FP Cluster Install on SOA Server Details Page

During the Foundation Pack cluster install, on the SOA Server Details page, if any of the managed servers are down, the drop down for Managed Server does not auto-populate with the cluster name. This is because of a behind-the-scenes validation by the Foundation Pack Installer to make sure that the managed servers are running before it auto-populates the name of the SOA cluster. The purpose of doing that is to ensure that the actual install does not fail because the managed servers are down. On this particular install page, there is no description, popup, or warning to the user as to why the auto-populate is not working.

56.2.5 Response File Associated with the Installer Inconsistent

The Response file template does not have entries for the Update process. If you need to do the update through the Silent Install file, you must use the response file shown below:

[ENGINE]
 
#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0
 
[GENERIC]
 
#
ORACLE_HOME=/slot/ems1390/oracle/test
 
#
ORACLE_HOME_NAME=test
 
#
AIA_Home=test
 
#
AIA_HOME_PATH=/slot/ems1390/oracle/test
 
#
MW_HOME_PATH=
 
#
SOA_HOME_PATH=
 
#
TEST_EMPTY=false
 
#
COMPLETE_INSTALL=true
 
#
INSTANCE_NAME=ASDFG
 
#
JAVA_HOME=/slot/ems1390/oracle/RC10_MW/jrockit_160_22_D1.1.1-3
 
#
AIA_UpgradeInstance_Combo=
 
#
UPGRADE_FLAG=N
 
#
SOA_USER_NAME=weblogic
 
#
SOA_DOMAIN_NAME=soaedg_domain
 
#
PORT_NUMBER=7001
 
#
ADMIN_PASSWORD=<SECURE VALUE>
 
#
MANAGED_SERVER_PORT=0
 
#
MANAGED_SERVER=SOA_Cluster
 
#
HOST_NAME=adc6160011.us.oracle.com
 
#
DOMAIN_ROOT=/scratch/abhishkk/oracle/admin/soaedg_domain/aserver/soaedg_domain
 
#
REMOTE_INSTALL=true
 
#
SOA_JDEV_HOME=/slot/ems1390/oracle/RC10_MW/Oracle_SOA1
 
#
CLUSTER_CHECK=true
 
#
CLUSTER_PROXY_HOST=slc60036sems.us.oracle.com
 
#
CLUSTER_PROXY_PORT=7777
 
#
AIADB_URL=sdc60025sems.us.oracle.com:1611/srglrgfp
 
#
AIADB_ADMIN_USERNAME=ASDFG_AIA
 
#
AIADB_ADMIN_PASS=<SECURE VALUE>
 
#
AIADB_SYS_USER=sys
 
#
AIADB_SYS_PASS=<SECURE VALUE>
 
#
AIADB_DTSPACE=SYSTEM
 
#
AIADB_TTSPACE=TEMP
 
#
AIADB_SYS_ROLE=SYSDBA
 
#
AIADB_SYS_CREATE=true
 
#
AIADB_PORT=1611
 
#
AIADB_CONFIRM_PASS=<SECURE VALUE>
 
#
XREF_PORT=1611
 
#
XREF_URL=sdc60025sems.us.oracle.com:1611/srglrgfp
 
#
XREF_ADMIN_USERNAME=ASDFG_XREF
 
#
XREF_ADMIN_PASS=<SECURE VALUE>
 
#
XREF_SYS_USER=sys
 
#
XREF_SYS_PASS=<SECURE VALUE>
 
#
XREF_DTSPACE=SYSTEM
 
#
XREF_TTSPACE=TEMP
 
#
XREF_SYS_ROLE=SYSDBA
 
#
XREF_SYS_CREATE=true
 
#
XREF_CONFIRM_PASS=<SECURE VALUE>
 
#
AIALC_PORT=1611
 
#
AIALC_URL=sdc60025sems.us.oracle.com:1611/srglrgfp
 
#
AIALC_ADMIN_USERNAME=ASDFG_AIALIFECYCLE
 
#
AIALC_ADMIN_PASS=<SECURE VALUE>
 
#
AIALC_SYS_USER=sys
 
#
AIALC_SYS_PASS=<SECURE VALUE>
 
#
AIALC_DTSPACE=SYSTEM
 
#
AIALC_TTSPACE=TEMP
 
#
AIALC_SYS_ROLE=SYSDBA
 
#
AIALC_SYS_CREATE=true
 
#
AIALC_CONFIRM_PASS=<SECURE VALUE>
 
#
JMSDB_PORT=1611
 
#
JMSDB_URL=sdc60025sems.us.oracle.com:1611/srglrgfp
 
#
JMSDB_ADMIN_USERNAME=ASDFG_JMSUSER
 
#
JMSDB_ADMIN_PASS=<SECURE VALUE>
 
#
JMSDB_SYS_USER=sys
 
#
JMSDB_SYS_PASS=<SECURE VALUE>
 
#
JMSDB_DTSPACE=SYSTEM
 
#
JMSDB_TTSPACE=TEMP
 
#
JMSDB_SYS_ROLE=SYSDBA
 
#
JMSDB_SYS_CREATE=true
 
#
JMSDB_CONFIRM_PASS=<SECURE VALUE>
 
#
MDS_URL=jdbc:oracle:thin:@sdc60025sems.us.oracle.com:1611/srglrgfp
 
#
MDS_ADMIN_USERNAME=DEV2_MDS
 
#
MDS_ADMIN_PASS=<SECURE VALUE>
 
#
OER_URL=
 
#
OER_ADMIN_USERNAME=
 
#
OER_ADMIN_PASS=<SECURE VALUE>
 
#
OER_CHECK=false
 
#
CONFIG_WIZARD_RESPONSE_FILE_LOCATION=0
 
 
[SYSTEM]
 
 
[APPLICATIONS]
 
 
[RELATIONSHIPS]

56.2.6 Response File Template with the FP Installer does not have Support for Oracle RAC DB

The Response File template does not have entries for the Oracle RAC database. If you want to use an Oracle RAC database through a silent response file, you must use the Response file shown below:

[ENGINE]
 
#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0
 
[GENERIC]
 
#
ORACLE_HOME=/home/abhishkk/test
 
#
ORACLE_HOME_NAME=test
 
#
AIA_Home=test
 
#
AIA_HOME_PATH=/home/abhishkk/test
 
#
MW_HOME_PATH=
 
#
SOA_HOME_PATH=
 
#
TEST_EMPTY=false
 
#
COMPLETE_INSTALL=true
 
#
INSTANCE_NAME=ABCD
 
#
JAVA_HOME=/scratch/abhishkk/oracle/product/fmw/jrockit_160_20_D1.1.0-18
 
#
AIA_UpgradeInstance_Combo=
 
#
UPGRADE_FLAG=N
 
#
SOA_USER_NAME=weblogic
 
#
SOA_DOMAIN_NAME=soaedg_domain
 
#
PORT_NUMBER=7001
 
#
ADMIN_PASSWORD=<SECURE VALUE>
 
#
MANAGED_SERVER_PORT=0
 
#
MANAGED_SERVER=SOA_Cluster
 
#
HOST_NAME=adc6160011.us.oracle.com
 
#
DOMAIN_ROOT=/scratch/abhishkk/oracle/admin/soaedg_domain/aserver/soaedg_domain
 
#
REMOTE_INSTALL=true
 
#
SOA_JDEV_HOME=/scratch/abhishkk/oracle/product/fmw/Oracle_SOA1
 
#
CLUSTER_CHECK=true
 
#
CLUSTER_PROXY_HOST=slc60036sems.us.oracle.com
 
#
CLUSTER_PROXY_PORT=7777
 
#
AIADB_URL=
 
#
AIADB_ADMIN_USERNAME=ABCD_AIA
 
#
AIADB_ADMIN_PASS=<SECURE VALUE>
 
#
AIADB_SYS_USER=sys
 
#
AIADB_SYS_PASS=<SECURE VALUE>
 
#
AIADB_DTSPACE=SYSTEM
 
#
AIADB_TTSPACE=TEMP
 
#
AIADB_SYS_ROLE=SYSDBA
 
#
AIADB_SYS_CREATE=true
 
#
AIADB_PORT=
 
#
AIADB_CONFIRM_PASS=<SECURE VALUE>
 
#
XREF_PORT=
 
#
XREF_URL=
 
#
XREF_ADMIN_USERNAME=ABCD_XREF
 
#
XREF_ADMIN_PASS=<SECURE VALUE>
 
#
XREF_SYS_USER=sys
 
#
XREF_SYS_PASS=<SECURE VALUE>
 
#
XREF_DTSPACE=SYSTEM
 
#
XREF_TTSPACE=TEMP
 
#
XREF_SYS_ROLE=SYSDBA
 
#
XREF_SYS_CREATE=true
 
#
XREF_CONFIRM_PASS=<SECURE VALUE>
 
#
AIALC_PORT=
 
#
AIALC_URL=
 
#
AIALC_ADMIN_USERNAME=ABCD_AIALIFECYCLE
 
#
AIALC_ADMIN_PASS=<SECURE VALUE>
 
#
AIALC_SYS_USER=sys
 
#
AIALC_SYS_PASS=<SECURE VALUE>
 
#
AIALC_DTSPACE=SYSTEM
 
#
AIALC_TTSPACE=TEMP
 
#
AIALC_SYS_ROLE=SYSDBA
 
#
AIALC_SYS_CREATE=true
 
#
AIALC_CONFIRM_PASS=<SECURE VALUE>
 
#
JMSDB_PORT=
 
#
JMSDB_URL=
 
#
JMSDB_ADMIN_USERNAME=ABCD_JMSUSER
 
#
JMSDB_ADMIN_PASS=<SECURE VALUE>
 
#
JMSDB_SYS_USER=sys
 
#
JMSDB_SYS_PASS=<SECURE VALUE>
 
#
JMSDB_DTSPACE=SYSTEM
 
#
JMSDB_TTSPACE=TEMP
 
#
JMSDB_SYS_ROLE=SYSDBA
 
#
JMSDB_SYS_CREATE=true
 
#
JMSDB_CONFIRM_PASS=<SECURE VALUE>
 
#
AIADB_RAC_SERVICE=canarySOA
 
#
AIADB_RAC_RACINSTANCE=rac0,rac1
 
#
AIADB_RAC_INSTANCES=canary1,canary2
 
#
AIADB_RAC_HOSTS=stahw04,sthaw05
 
#
AIADB_RAC_PORTS=1521,
 
#
AIADB_RAC_
RACURL=jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=stahw04)(PORT=1
521))(ADDRESS=(PROTOCOL=TCP)(HOST=sthaw05)(PORT=))(LOAD_BALANCE=yes)(CONNECT_
DATA=(SERVER=DEDICATED)(SERVICE_NAME=canarySOA)))
 
#
AIALC_RAC_SERVICE=canarySOA
 
#
AIALC_RAC_RACINSTANCE=rac0,rac1
 
#
AIALC_RAC_INSTANCES=canary1,canary2
 
#
AIALC_RAC_HOSTS=stahw04,sthaw05
 
#
AIALC_RAC_PORTS=1521,
 
#
AIALC_RAC_
RACURL=jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=stahw04)(PORT=1
521))(ADDRESS=(PROTOCOL=TCP)(HOST=sthaw05)(PORT=))(LOAD_BALANCE=yes)(CONNECT_
DATA=(SERVER=DEDICATED)(SERVICE_NAME=canarySOA)))
 
#
JMSDB_RAC_SERVICE=canarySOA
 
#
JMSDB_RAC_RACINSTANCE=rac0,rac1
 
#
JMSDB_RAC_INSTANCES=canary1,canary2
 
#
JMSDB_RAC_HOSTS=stahw04,sthaw05
 
#
JMSDB_RAC_PORTS=1521,
 
#
JMSDB_RAC_
RACURL=jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=stahw04)(PORT=1
521))(ADDRESS=(PROTOCOL=TCP)(HOST=sthaw05)(PORT=))(LOAD_BALANCE=yes)(CONNECT_
DATA=(SERVER=DEDICATED)(SERVICE_NAME=canarySOA)))
 
#
XREF_RAC_SERVICE=canarySOA
 
#
XREF_RAC_RACINSTANCE=rac0,rac1
 
#
XREF_RAC_INSTANCES=canary1,canary2
 
#
XREF_RAC_HOSTS=stahw04,sthaw05
 
#
XREF_RAC_PORTS=1521,
 
#
XREF_RAC_
RACURL=jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=stahw04)(PORT=1
521))(ADDRESS=(PROTOCOL=TCP)(HOST=sthaw05)(PORT=))(LOAD_BALANCE=yes)(CONNECT_
DATA=(SERVER=DEDICATED)(SERVICE_NAME=canarySOA)))
 
#
SRDB_RAC_SERVICE=
 
#
SRDB_RAC_RACINSTANCE=
 
#
SRDB_RAC_INSTANCES=
 
#
SRDB_RAC_HOSTS=
 
#
SRDB_RAC_PORTS=
 
#
SRDB_RAC_RACURL=
 
#
MDS_URL=jdbc:oracle:thin:@sdc60025sems.us.oracle.com:1611/srglrgfp
 
#
MDS_ADMIN_USERNAME=DEV2_MDS
 
#
MDS_ADMIN_PASS=<SECURE VALUE>
 
#
OER_URL=
 
#
OER_ADMIN_USERNAME=
 
#
OER_ADMIN_PASS=<SECURE VALUE>
 
#
OER_CHECK=false
 
#
CONFIG_WIZARD_RESPONSE_FILE_LOCATION=0
 
 
[SYSTEM]
 
 
[APPLICATIONS]
 
 
[RELATIONSHIPS]

56.2.7 Java.Lang.UNSATISFIEDLINKERROR: NO GETVOLUMEINFO in JAVA.LIBRARY.PATH

This error does not harm the install in any way and the install completes successfully.

56.2.8 Non-ASCII Characters in Project Description may Cause Invalid WSDL File if System Encoding is non-UTF8

In native encoding, if you enter MB words for the system code field in "Step3" of Wizard, creation is successful, but when you open AIAServiceConfigurationProperties.xml in JDev, the words for "SystemID" become garbled:<Property name="Default.SystemID">????</Property> This will cause deployment failure. The workaround is to change the garbled words back to the MB words. The system ID should be written in xml using UTF8.

56.2.9 Cannot Create Project with Service Constructor with MB Application Name

Currently, neither Service Constructor nor Composite Generator is enabled to handle MB characters. All the files in the generated composite should be written in UTF-8 encoding, otherwise all multibyte chars will appear as "?" in JDev.

56.2.10 About AIA Page Cannot be Displayed from the PLW BOM Page

You cannot access the About AIA page (using the link on the page) from the Project LifeCycle Workbench Bill of Material page in the UI. When the About AIA link on the Bill of Material page is clicked, nothing happens and no About AIA page is displayed. You can access the About AIA page from any of the other available Project LifeCycle Workbench UI pages.

56.2.11 CRMOD Ebiz PIP Deploy Failing in Windows

On Linux box, the JVM heap size is set to 2GB(USER_MEM_ARGS="-Xms2048m -Xmx2048m) by default, however on Windows it is set to 1GB. The deployment works on Linux without any issue or modification. On Windows, do the following to get a successful deployment:

  1. Change the page file size to 1.5 times of the physical memory.

    For example, on a 5 GB box, change the page file size to 7.5 GB and on a 7GB box, change the page file size to 10.5 GB.

  2. Change the boot.ini file in both machine to add the /3GB switch.

    For more information, see http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx

  3. Modify the setDomainEnv.cmd to add USER_MEM_ARGS=-Xms1536m -Xmx1536m -Xgcprio:throughput.

56.2.12 Access-Keyboard Only Issues-AIA Setup Page

You can not navigate to a date on the popup and choose the date using the keyboard. It will submit the entire form when you press Enter, instead of selecting the date.In the case of any calendar control, you can not select the date from calendar control using the keyboard.

56.2.13 MDS Details not Picked Up by Installer for Cluster over Oracle RAC Database

Manually enter the Oracle RAC DB URL and enter MDS user and password associated with the SOA Installation.

56.2.14 Demo Functionality not Working after Demo Upgrade

The workaround for this is:

  1. Open Weblogic Admin Console.

  2. Browse to Home -> Summary of Deployments -> AIA_DbAdapter_Config -> Configuration -> Outbound Connection Pools.

  3. Expand the existing Groups and Connections.

  4. Click eis/DB/fodDS.

  5. Browse to Connection Pool tab.

  6. Increase values for the following parameters:

    Initial Capacity - 10

    Max Capacity - 100

    Capacity Increment - 10

  7. Save the Configuration.

  8. In the next step, the console displays "Save Deployment Plan" information.

    Click OK. This step creates a deployment plan and updates the Adapter with the new deployment plan.

56.2.15 Business Task Expansion Causes Problem in Project Creation and Updating

If you expand any business task in the Business Task page while you are creating, editing, or copying a project in Project Lifecycle Workbench and then go to another page such as Assumption, Document Links, or Description, the Save and Return button on that other page will not work. The workaround is to collapse all the expanded business tasks before clicking other links such as Assumption, Document Links, or Description, or click the Save and Return button on the Business Task page, then click Edit for this project to return so you can make other changes.

56.2.16 No Lookup Values Display in Project Lifecycle Workbench Drop-down List Boxes

No lookup values will display in Project Lifecycle Workbench drop-down list boxes when the SOA server is started using language settings other than US. This is because an AIA Installer-based installation of Foundation Pack will, by default, configure Project Lifecycle Workbench lookup values with the following language settings: LANGUAGE = US and SOURCE_LANG = US.If your SOA server implementation uses a value other than US, you must run an SQL statement to populate the AIA_LOOKUPS_TL table with the internationalized text for lookup values. For more information, see "How to Add Lookup Values" in Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack.

56.2.17 Prerequisite Failure of AIA FP OUI on SUSE 11 64 Bit Machine

Prerequisite check fails but does no harm during the install.

56.2.18 Config Wizard Giving Error in Upgrade and Script Based Install

Copy the Key file from AIA_INSTANCE/.configuration/ and place it in Infrastructure/Install/AID/.config and rename it as aid.boot.key.

For a script based install, create an empty file aid.boot.key in the same location and it should work.

56.2.19 Demo Upgrade Failure

The EOLMergeUtility used to have three arguments. AIA introduced a fourth argument for having separate logs, however the demo upgrade deployment plan was not updated with the fourth argument.

The workaround for this is to add <arg value="${AIA_INSTANCE}/logs"/> as the last argument to EOLMergeUtility call in the upgrade demo deployment plan.

56.2.20 Config Wizard has no Support for Oracle RAC Database and DB Based on Service Name

Modify the jdbc-url field in the participating application of the AIAInstallProperties.xml once you have run the Configuration Wizard and then run the deployment plan.

56.2.21 AIA Datastore not Created on Cluster

This is not a consistent error however it can happen that DATA stores are not created in Domain home and aia.jar is not extracted on all the nodes.

56.2.22 Validation Required for Cluster Selected in SOA Details Page And Config Wizard

In the case of multiple clusters such as SOA BAM and POLICY servers clusters on a single environment, the cluster name selected on the SOA Details page is not validated and the SOA Cluster is not taken as default.

56.2.23 Demo Sample CAVS Test for Credit Card Authorization Failing

A simple CAVS Test for demo is not functioning because the security policy header is missing from the test Definition input payload.

The Security Header is missing in the test definition. Adding this security header solves the issue: <soap:Header><wsse:Security soap:mustUnderstand="1"

xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-
wss-wssecurity-secext-1.0.xsd"><wsse:UsernameToken><wsse:Username>weblogic</wsse:U
sername><wsse:PasswordType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-ws
s-username-token-profile-1.0#PasswordText">yr_
password</wsse:Password></wsse:UsernameToken></wsse:Security></soap:Header>)

56.2.24 AIA-LOG-XXXXXX-Handler are Created in Admin Domain

These log files should be created in the Managed Server domain but have been created in the Admin Domain. You will see this error when the admin domain and the managed domain are different.

56.2.25 FYI Role is not Receiving Business Fault Error Notifications

The cache will not get updated when you do something from AIA Page. The workaround for this is to restart the SOA server whenever you change anything from AIA Page.

56.2.26 Aggregate Count on the AIA Setup Page is not Working

The cache will not get updated when you do something from AIA Page. The workaround for this is to restart the SOA server whenever you change anything from AIA Page.

56.2.27 projectIndustry is empty in the exported BOM

When generating and exporting a bill of material (BOM), Project Lifecycle Workbench assumes that all lookup value rows, including projectIndustry, have their language set to US. This known issue arises when the lookup value row in the lookup table has its language set to a value other than US.

Lookup value languages are set to a value other than US when the SOA server is started using language settings other than US. If your SOA server implementation uses a value other than US, you must run an SQL statement to populate the AIA_LOOKUPS_TL table with the internationalized text for lookup values.

For more information, see "How to Add Lookup Values" in Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack.

56.3 Documentation Errata

This section describes documentation errata. It includes the following topic:

56.3.1 Delete Existing AIAInstallProperties.xml Prior to Running Upgrade Script

When performing an upgrade of Foundation Pack 11g Release 1 (11.1.1.2.0) to 11g Release 1 (11.1.1.4.0) as described in "Upgrading Foundation Pack" in Oracle Fusion Middleware Installation and Upgrade Guide for Oracle Application Integration Architecture Foundation Pack, you must perform an additional task not covered in the documentation.In the "Running the Upgrade Script" procedure, after step 1 and before step 2, perform the following task: Browse to $AIA_INSTANCE/AIAMetaData/config. Delete the AIAInstallProperties.xml file.If you do not perform this step, the Foundation Pack Home Version value displayed on the Product Information tab in the About AIA area will not be updated to display the current version value of 11.1.1.4.0.

56.3.2 Inconsistency in FP Install Guide as Compared to Actual FP Install

Note the following updates to Oracle Fusion Middleware Installation and Upgrade Guide for Oracle Application Integration Architecture Foundation Pack.

  • In Section 3.1.1 "Launch the Oracle AIA Foundation Pack Installer", Step 1: Navigate to aiafp/Disk1.

  • In Section 3.1.3 "Specify Installation Location", remove Step 4: Select the Foundation Pack check box. This check box is no longer on the page.

56.3.3 Usability Issue on SOA Server Details Page - Cluster Check Box and Parameters

After selecting the cluster check box, the AIA Installer tries to find the name of the cluster based on the admin server and other details provided earlier. After it finds the cluster name, it populates the field named Managed Server with the cluster name and populates the field Managed Port with 0. However, this is confusing for any user of the install. Unlike a managed server, a cluster does not have a 'port' and that field does not make sense. This is a known bug where the Managed Server field will be populated with the cluster name.

56.3.4 Extension Config Properties need to be Aligned with Service Constructor Generated Properties

Note the following updates to Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack ,"Developing Extensible ABCS."

These configuration properties are defined for every ABCS that has been extension enabled. The Developer's Guide gives you guidelines on how you would create and leverage these configuration properties to optimize the extensibility. The number of parameters for any particular ABCS could be either more or less than four, and the names also do not have to be the same. But you have to ensure that the properties defined for that ABCS do match the property names being referred to in the ABCS.

The following information updates the tables in the Developer's Guide to ensure that the extension related configuration properties created by Service Constructor are in alignment with those mentioned in the guide.

Table 56-1 Service Operations for Requester ABCS (Request / Response) Extensibility Points

Extensibility Point Service Operation Name

Just prior to the execution of transformation of application business message (ABM) to Enterprise Business Message (EBM)

ABCSExtension.PreXformABMtoEBM

Just prior to the invocation of the enterprise business service (EBS)

ABCSExtension.PreInvokeEBS

Just prior to the execution of transformation of EBM to ABM and after invoking the EBS

ABCSExtension.PostInvokeEBS

Just prior to the invocation of callback service or response return and transforming EBM to ABM

ABCSExtension.PostXformEBMtoABM


Table 56-2 Service Operations for Requester ABCS (Fire and Forget) Extensibility Points

Extensibility Point Service Operation Name

Just prior to the execution of transformation of ABM to EBM

ABCSExtension.PreXformEBMtoABM

Just prior to the invocation of the EBS

ABCSExtension.PreInvokeEBS


Table 56-3 Service Operations for Provider ABCS (Request / Response) Extensibility Points

Extensibility Point Service Operation Name

Customer extension just prior to the execution of the EBM to ABM transformation

ABCSExtension.PreXformEBMtoABM

Customer extension just prior to the invocation of application service

ABCSExtension.PreInvokeABS

Customer extension just prior to the execution of the ABM to EBM transformation and after invoking Application Service

ABCSExtension.PostInvokeABS

Customer extension just prior to the invocation of EBS and after transforming Application Message to EBM

ABCSExtension.PostXformABMtoEBM


Table 56-4 Service Operations for Provider ABCS (Fire and Forget) Extensibility Points

Extensibility Point Service Operation Name

Customer extension just prior to the execution of the EBM to ABM transformation

ABCSExtension.PreXformEBMtoABM

Customer extension just prior to the invocation of application service

ABCSExtension.PreInvokeABS