| Oracle® Application Integration Architecture Installation and Upgrade Guide for Pre-Built Integrations Release 11.4 Part Number E37608-03 |
|
|
PDF · Mobi · ePub |
| Oracle® Application Integration Architecture Installation and Upgrade Guide for Pre-Built Integrations Release 11.4 Part Number E37608-03 |
|
|
PDF · Mobi · ePub |
This chapter provides an overview of the Application Integration Architecture (AIA) upgrade process for the Pre-Built Integrations included in this release.
This chapter includes the following sections:
Note:
If you have AIA 2.4 or 2.5 installed, you cannot migrate or upgrade to AIA 11.1. You must install AIA 11.4 following the steps included in Chapter 3, "Installing Pre-Built Integrations"
To migrate customizations made to OOTB 2.4 or 2.5 artifacts, see the Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack
To migrate the 2.4 or 2.5 xref data to AIA 11.4, you must use the SOA xref utility. For more information, see the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.
If you have modified or created custom services, custom DVMs and Xrefs, you must migrate these to AIA 11.4. For more information on migrating custom services, custom DVMs and Xrefs from AIA 2.4 or 2.5 to AIA 11.4, see the Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack
The AIA upgrade process consists of three phases:
Upgrade newer AIA Release: the file-system (under $AIA_HOME) is updated with the latest content.
Redeploy previously deployed PIPs or DIs: update the server to the latest content by redeploying new PIPs or DIs from the new release.
Merge customizations and extensions: if you have customized services, you must merge the customizations.
After these three tasks are completed, you can configure and deploy new PIPs or DIs from the new release.
You must run the AIA Pre-Built Integrations Installer and point to the existing $AIA_HOME where the previous AIA version is installed. The AIA Pre-Built Integrations Installer:
Warns you when there is a previous release of AIA Pre-Built Integrations installed in $AIA_HOME.
Updates the PIP and DI content in $AIA_HOME with the latest version, after you back up AIA_HOME.
After upgrading the release and merging your customizations, the previously deployed PIPs and DIs may be redeployed. FOR OOTB PIPs or DIs that require redeployment, see Section 36.2, "Upgrading Pre-Built Integrations", Section 36.3, "Upgrading AIA 11.3 Integrations" and Section 36.4, "Upgrading AIA 3.1 PIPs and DIs". The required upgrade scripts are included by the PIPs or DIs in this release.
For custom PIPs or DIs, you must identify the artifacts that require redeployment by rerunning the deployment plan of the specific PIP or DI or by redeploying the specific artifacts using a custom deployment plan.
This section lists the tasks that you must perform to upgrade pre-built integrations.
AIA Pre-Built Integrations Installer upgrades your 11.1 version PIPs and DIs to RV 11.4.
Note:
Before upgrading Pre-Built Integrations 11.1 or AIA RV 3.1.1 PIPs or DIs, you must upgrade Foundation Pack to version 11.1.1.6.0, RUP patch 16301959 or later. For more information and instructions, see the Oracle Fusion Middleware Installation and Upgrade Guide for Oracle Application Integration Architecture Foundation Pack. If you are using an AIA Foundation Pack release that is earlier than 11.1.1.5.0, first upgrade to release 11.1.1.5.0 using the respective upgrade guides and then upgrade to version 11.1.1.6.0, RUP patch 16301959 or later..
To upgrade from Foundation Pack 11.1.1.5.0 to version 11.1.1.6.0, RUP patch 16301959 or later, you must manually run the upgrade scripts found in the Oracle Fusion Middleware Installation and Upgrade Guide for Oracle Application Integration Architecture Foundation Pack. To upgrade individual PIPs or DIs, you must manually run the upgrade scripts after you upgrade Foundation Pack.
AIA Pre-Built Integrations Installer does not republish AIA content to the service registry when you upgrade from Foundation Pack 11.1.1.5.0 to 11.1.1.6.0. To upgrade the registry with AIA 11.1.1.6.0 content, you must manually republish.
AIA Foundation Pack 11.1.1.6.0 contains bug fixes in Core Infrastructure areas (CAVS, BSR, and so on). When you upgrade from 11.1.1.5.0 to 11.1.1.6.0, RUP patch 16301959 or later, these applications get redeployed. However, the upgrade does not have any impact because your data is preserved and all fixes are backward compatible.
Note:
The upgrade of individual components is not supported in this release.
The system requirements for the upgrade (CPU/memory/disk space) are the same as those discussed under Hardware Requirements.
For more details on the software requirements for your specific PIPs or DIs, see Chapter 2, "Software Requirements".
Before running the AIA Pre-Built Integrations Installer, you must:
Navigate a command prompt to the <AIA_HOME> parent directory: For example: "cd $AIA_HOME/..." (Go to the <AIA_HOME> directory and move up one directory higher).
Change the file permissions for the <AIA_HOME> directory and all subdirectories recursively to Read/Write/Execute for User/Group/Other owners. For example: chmod -R 777 <AIA_HOME>.
Back up your existing AIA_HOME before you start the 11.4 AIA Pre-Built Integrations Installer.
Note:
These steps must be performed to upgrade every PIP or DI in Section 36.3, "Upgrading AIA 11.3 Integrations" and Section 36.4, "Upgrading AIA 3.1 PIPs and DIs".
Back up extended solution artifacts
Following the AIA extensibility model, as documented in the extensibility sections of the Oracle Application Integration Architecture - Foundation Pack: Concepts and Technologies Guide and the Oracle Application Integration Architecture - Foundation Pack: Integration Developer's Guide, you created or updated one or more of the following artifacts:
Custom EBOs:
These are AIA schema extensions performed on EBOs. Though the AIA Foundation Pack Installer automatically preserves these schema extensions, it is advisable to back up the custom directory. For example, all custom xsd files for core EBOs are accessed as http://hostname:port/AIAComponents/EnterpriseObjectLibrary/Core/Custom/EBO/
If you are using the oracle application server, you can access this folder from SOA_HOME/Apache/Apache/htdocs/AIAComponents/EnterpriseObjectLibrary/Core/Custom/EBO/
Custom XSLTs:
These are the extensions performed on the AIA Transformation style sheet. Foundation Pack does not contain any Extensible Stylesheet Language Transformations (XSLTs) for its components and utilities. Because the process content is delivered only in PIPs or DIs, you must manually back up the XSLTs if you have developed any for the custom integrations, and reapply them as a postupgrade step.
Custom EBS WSDL:
If you have customized any EBS WSDL that is delivered or shipped with AIA Foundation Pack, you must back it up and restore it manually as a postupgrade step
Before you upgrade the Product MDM pre-built integration from PIP version 11.1 to 11.2, you must apply the patch 16367095 on Product MDM PIP 11.1 if not applied.
Launching the AIA Pre-Built Integrations Installer
To launch AIA Pre-Built Integrations Installer:
Navigate to aiapip/Disk1.
Follow the launch instructions for your platform.
Table 36-1 Launch Instructions for AIA Pre-Built Integrations Installer
| Platform | To launch the AIA Pre-Built Integrations Installer |
|---|---|
|
Linux x86 Solaris SPARC (64-bit) IBM AIX Based Systems (64-bit) HP-UX 11i (64 bit) |
At the command line prompt, enter: ./runInstaller -invPtrLoc <AIA_HOME>/oraInst.loc -jreLoc <location of the jre specific to your operating system. This directory should have /bin/java> |
|
Microsoft Windows (32-bit) |
Double-click setup.exe |
Click Next.
To choose the home directory where the existing version of Pre-Built Integrations is installed:
Specify the home directory of your existing AIA implementation.
Note:
Provide the directory where Foundation Pack 11.1.1.6.0, RUP patch 16301959 or later was installed. The path should be available in the list. When you select the current home directory, AIA Pre-Built Integrations Installer disables the rest of the options in the screen and displays the information related to AIA (product name and version number) that is in the directory.
Click Next.
To run the directory selection and upgrade process:
On the Summary screen, review the summary of upgrade information.
The summary screen provides information about the existing AIA Pre-Built Integrations installation.
Click Install. This upgrades the Pre-Built Integrations version.
PIP- and DI-related files get copied to the specified location. You must manually execute the PIP or DI upgrade scripts to complete the upgrade.
Note:
The integrations that are not listed in this section do not require updates because the contents have not changed.
This section discusses the upgrade process for AIA 11.3 integrations.
To upgrade the Product MDM: Base Pack pre-built integration from PIP version 11.1 to 11.2, perform the following task discussed below:
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.
Navigate to <AIAHOME>/pips/MDMProductPIM/upgrade/11.2 and run the deployment commands for your platform.
Configure the endpoint URLs for Oracle PIM web services as described in Section 15.5.1, "Configuring Endpoint URLs for Oracle PIM Web Services" of this guide.
To upgrade the Product MDM: E-Business Suite pre-built integration from PIP version 11.1 to 11.2, perform the following task discussed below:
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.
Navigate to <AIAHOME>/pips/MDMProductEbiz/upgrade/11.2 and run the deployment commands for your platform.
To upgrade the Product MDM: Siebel CRM pre-built integration from PIP version 11.1 to 11.2, perform the following task discussed below:
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.
Navigate to <AIAHOME>/pips/MDMProductSiebel/upgrade/11.2 and run the deployment commands for your platform.
In item sync with pricelists scenario, SyncItemListPIMReqABCS service waits for a response. The response from the ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl service is sent to the requester through CommunicationsPriceListResponseEBSV2. Therefore, after you deploy the Siebel CRM services, you must update the following integration services:
ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl
SyncItemCompositionListSiebelCommsProvABCSImpl
To update the ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl service:
Edit the AIAConfigurationProperties.xml file that is located in <AIA_INSTANCE>/AIAMetaData/config.
Ensure that the following properties are listed in the AIAConfigurationProperties.xml file:
<Property name="EBSOverride.CommunicationsPriceListResponseEBS.SyncPriceListListResponse.Address">http://HOST_NAME:PORT_NAME/soa-infra/services/default/CommunicationsPriceListResponseEBSV2/CommunicationsPriceListResponseEBSV2_ep</Property>
<Property name="EBSOverride.CommunicationsPriceListResponseEBS.SyncPriceListListResponse.PortType">{http://xmlns.oracle.com/EnterpriseServices/Core/PriceList/V2}CommunicationsPriceListResponse</Property>
<Property name="EBSOverride.CommunicationsPriceListResponseEBS.SyncPriceListListResponse.ServiceName">{http://xmlns.oracle.com/EnterpriseServices/Core/PriceList/V2}CommunicationsPriceListResponse</Property>
To update the SyncItemCompositionListSiebelCommsProvABCSImpl service:
Edit the AIAConfigurationProperties.xml file that is located in <AIA_INSTANCE>/AIAMetaData/config.
Ensure that the following properties are listed in the AIAConfigurationProperties.xml file:
<Property name="EBSOverride.CommunicationsItemCompositionResponseEBSV1.SyncItemCompositionListResponse.Address">http://HOST_NAME:PORT_NAME/soa-infra/services/default/ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl/ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl</Property>
<Property name="EBSOverride.CommunicationsItemCompositionResponseEBSV1.SyncItemCompositionListResponse.PortType">{http://xmlns.oracle.com/ABCSImpl/Siebel/Industry/Comms/ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl/V1}ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl</Property>
<Property name="EBSOverride.CommunicationsItemCompositionResponseEBSV1.SyncItemCompositionListResponse.ServiceName">{http://xmlns.oracle.com/ABCSImpl/Siebel/Industry/Comms/ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl/V1}ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl</Property>
To upgrade the Product MDM: Routing Rules pre-built integration from PIP version 11.1 to 11.2, perform the following task discussed below:
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.
Navigate to <AIAHOME>/pips/MDMProduct/upgrade/11.2 and run the deployment commands for your platform.
Upgrade the Design to Release: Agile - EBS pre-built integrations by followingthe tasks discussed below:
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.
Configure the PIP by following the steps listed in Section 21.3, "Configuring and Deploying Design to Release: Agile - EBS Pre-Built Integration".
Apply the patch 15847182.
Navigate to <AIAHOME>/pips/AgileToEbiz/upgrade/11.2 and run the deployment commands for your platform.
To perform postupgrade tasks:
Navigate to the folder $AIA_HOME/aia_instances/<INSTANCE_NAME>/AIAMetaData/config.
Open AIAConfigurationProperties.xml and change the following property values listed below from your backup:
<ModuleConfiguration moduleName="Agile">
<Property name="LANG_LOCALE">English</Property>
<Property name="MULTISITE_ENABLED">TRUE</Property>
<Property> name="Item.UnitCostAttribute">Site.Numeric01</Property>
<Property>
name="Item.AvailableQuantityAttribute">Site.Numeric02</Property>
<Property> name="Item.OnHandQuantityAttribute">Site.Numeric03</Property
<Property> name="Item.ReservedQuantityAttribute">Site.Numeric04</Property>
<Property> name="Change.TransferStatusAttribute">PageTwo.Text02</Property>
<Property> name="Change.TransferStatusDetailedMessageAttribute">PageTwo.Multitext35 </Property>
<Property name="REPLICATE_BOM_ENABLED">FALSE</Property>
<Property> name="COMMON_BOM ENABLED">FALSE</Property>
</ModuleConfiguration>
Update MDS with the above AIAConfigurationProperties.xml changes and any other custom changes present in the AIAConfigurationProperties.xml backup file from preupgrade.
To update AIAConfigurationProperties.xml with custom serviceconfiguration elements:
Open the $AIA_HOME/aia_instances/$INSTANCE_NAME/config folder.
Open the AIAConfigurationProperties.xml and add the customelements under respective service configurations.
Open the deployment plan file, UpdateMetaDataDP.xml. Update the UpdateMetaDataDP.xml by inserting the include tags for AIAConfigurationProperties.xml, which you may want to add to the MDS:
Open the $AIA_HOME/aia_instances/$INSTANCE_NAME/bin folder.
Execute the following command: source aiaenv.sh
Access the file path, $AIA_ HOME/Infrastructure/Install/scripts. Execute the script, UpdateMetaData.xml by using the following command: ant -f $AIA_ HOME/Infrastructure/Install/scripts/UpdateMetaData.xml
Any custom modifications/customizations must be reapplied.
Upgrade the Design to Release: Agile - SAP pre-built integrations by following the tasks discussed below:
To upgrade the Design to Release: Agile - SAP pre-built integrations from PIP version 11.1 to 11.2, you must manually execute the upgrade scripts. Before you upgrade Design to Release: Agile - SAP PIP, you must download the SAP JCO 3.0 from the SAP market place and copy the JCO.jar file in the lib directory of adapters.
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.
Apply the patch 15835701.
Navigate to <AIAHOME>/pips/AgileToSAP/upgrade/11.2 and run the deployment commands for your platform.
Upgrade Foundation Pack first and then upgrade the Comms Agent Assisted Billing Care: Siebel CRM - BRM Pre-Built Integrations following the tasks discussed below.
To upgrade the Comms Agent Assisted Billing Care: Siebel CRM - BRM Pre-Built Integrations from PIP version 11.2 to 11.3, you must manually execute the upgrade scripts. You must upgrade Foundation Pack to 11.1.1.6.0, RUP patch 16301959 or later from your existing version before you can upgrade Comms Agent Assisted Billing Care: Siebel CRM - BRM.
To upgrade the integration on the Fusion Middleware server, run the command specific to your platform:
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.
Navigate to <AIAHOME>/pips/Communications/AABC/Upgrade and run the command for your platform.
Review the log at location <AIA_INSTANCE>/<INSTANCE_NAME>/logs/AABC-Upgrade-11_2_To_11_3-DD-MM-YYYY_HH-HH-SS.log.
You must perform the following postupgrade tasks:
Reconfigure MultiBRM setup in AIA Configuration file and update the MDS.
This step is required because the upgrade script forcemerges the AIA service configurations into <AIA_INSTANCE>/<INSTANCE_NAME>/AIAMetaData/config/AIAConfigurationProperties.xml.
Perform additional post upgrade tasks as described in Section 36.5, "Performing Postupgrade Tasks for Pre-Built Integrations" and Section 36.6, "Performing Postupgrade Tasks for AIA".
Upgrade Foundation Pack first and then upgrade the Comms Order to Cash: Siebel CRM, OSM and BRM Pre-Built Integrations following the tasks discussed below.
To upgrade the Comms Order to Cash: Siebel CRM, OSM and BRM Pre-Built Integrations from PIP version 11.2 to 11.3, you must manually execute the upgrade scripts. You must upgrade Foundation Pack to 11.1.1.6.0, RUP patch 16301959 or later from your existing version before you can upgrade Comms Order to Cash: Siebel CRM, OSM and BRM.
To upgrade the integration on the Fusion Middleware server, run the command specific to your platform:
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.
Navigate to <AIAHOME>/pips/Communications/O2C/Upgrade and run the command for your platform.
Review the log at location <AIA_INSTANCE>/<INSTANCE_NAME>/logs/O2C-Upgrade-11_2_To_11_3-DD-MM-YYYY_HH-HH-SS.log.
You must perform the following postupgrade tasks:
Reconfigure MultiBRM setup in AIA Configuration file and update the MDS.
This step is required because the upgrade script forcemerges the AIA service configurations into <AIA_INSTANCE>/<INSTANCE_NAME>/AIAMetaData/config/AIAConfigurationProperties.xml.
Perform additional post upgrade tasks as described in Section 36.5, "Performing Postupgrade Tasks for Pre-Built Integrations" and Section 36.6, "Performing Postupgrade Tasks for AIA".
Upgrade Foundation Pack first and then upgrade the Comms Order to Cash: Siebel CRM and BRM Pre-Built Integrations following the tasks discussed below.
To upgrade the Comms Order to Cash: Siebel CRM and BRM Pre-Built Integrations from PIP version 11.2 to 11.3, you must manually execute the upgrade scripts. You must upgrade Foundation Pack to 11.1.1.6.0, RUP patch 16301959 or later from your existing version before you can upgrade Comms Order to Cash: Siebel CRM and BRM.
To upgrade the integration on the Fusion Middleware server, run the command specific to your platform:
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.
Navigate to <AIAHOME>/pips/Communications/O2B/Upgrade and run the command for your platform.
Review the log at location <AIA_INSTANCE>/<INSTANCE_NAME>/logs/O2B-Upgrade-11_2_To_11_3-DD-MM-YYYY_HH-HH-SS.log.
Reconfigure MultiBRM setup in AIA Configuration file and update the MDS.
This step is required because the upgrade script forcemerges the AIA service configurations into <AIA_INSTANCE>/<INSTANCE_NAME>/AIAMetaData/config/AIAConfigurationProperties.xml.
Perform additional post upgrade tasks as described in Section 36.5, "Performing Postupgrade Tasks for Pre-Built Integrations" and Section 36.6, "Performing Postupgrade Tasks for AIA".
Upgrade Foundation Pack first and then upgrade the Comms Order to Cash: Siebel CRM and OSM Pre-Built Integrations following the tasks discussed below.
To upgrade the Comms Order to Cash: Siebel CRM and OSM Pre-Built Integrations from PIP version 11.2 to 11.3 you must manually execute the upgrade scripts. You must upgrade Foundation Pack to 11.1.1.5.0 from your existing version before you can upgrade Comms Order to Cash: Siebel CRM and OSM.
To upgrade the integration on the Fusion Middleware server, run the command specific to your platform:
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.
Navigate to <AIAHOME>/pips/Communications/O2A/Upgrade and run the command for your platform.
Review the log at location <AIA_INSTANCE>/<INSTANCE_NAME>/logs/O2A-Upgrade-11_2_To_11_3-DD-MM-YYYY_HH-HH-SS.log.
Perform additional post upgrade tasks as described in Section 36.5, "Performing Postupgrade Tasks for Pre-Built Integrations" and Section 36.6, "Performing Postupgrade Tasks for AIA".
Note:
The PIPs or DIs that are not listed in this section do not require updates because the contents have not changed.
This section discusses the upgrade process for AIA 3.1 PIPs and DIs. The PIPs and DIs included in this section are upgraded from version 3.1 to 3.1.1 and from 3.1 to 11.2.
Upgrade the Design to Release: Agile - EBS pre-built integrations by followingthe tasks discussed below:
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.
Configure the PIP by following the steps listed in Section 21.3, "Configuring and Deploying Design to Release: Agile - EBS Pre-Built Integration".
Apply the patch 15847182.
Navigate to <AIAHOME>/pips/AgileToEbiz/upgrade/11.2 and run the deployment commands for your platform.
To perform postupgrade tasks:
Navigate to the folder $AIA_HOME/aia_instances/<INSTANCE_NAME>/AIAMetaData/config.
Open AIAConfigurationProperties.xml and change the following property values listed below from your backup:
<ModuleConfiguration moduleName="Agile">
<Property name="LANG_LOCALE">English</Property>
<Property name="MULTISITE_ENABLED">TRUE</Property>
<Property> name="Item.UnitCostAttribute">Site.Numeric01</Property>
<Property>
name="Item.AvailableQuantityAttribute">Site.Numeric02</Property>
<Property> name="Item.OnHandQuantityAttribute">Site.Numeric03</Property
<Property> name="Item.ReservedQuantityAttribute">Site.Numeric04</Property>
<Property> name="Change.TransferStatusAttribute">PageTwo.Text02</Property>
<Property> name="Change.TransferStatusDetailedMessageAttribute">PageTwo.Multitext35 </Property>
<Property name="REPLICATE_BOM_ENABLED">FALSE</Property>
<Property> name="COMMON_BOM ENABLED">FALSE</Property>
</ModuleConfiguration>
Update MDS with the above AIAConfigurationProperties.xml changes and any other custom changes present in the AIAConfigurationProperties.xml backup file from preupgrade.
To update AIAConfigurationProperties.xml with custom serviceconfiguration elements:
Open the $AIA_HOME/aia_instances/$INSTANCE_NAME/config folder.
Open the AIAConfigurationProperties.xml and add the customelements under respective service configurations.
Open the deployment plan file, UpdateMetaDataDP.xml. Update the UpdateMetaDataDP.xml by inserting the include tags for AIAConfigurationProperties.xml, which you may want to add to the MDS:
Open the $AIA_HOME/aia_instances/$INSTANCE_NAME/bin folder.
Execute the following command: source aiaenv.sh
Access the file path, $AIA_ HOME/Infrastructure/Install/scripts. Execute the script, UpdateMetaData.xml by using the following command: ant -f $AIA_ HOME/Infrastructure/Install/scripts/UpdateMetaData.xml
Any custom modifications/customizations must be reapplied.
Upgrade Foundation Pack first and then upgrade the Design to Release: Agile PLM for Process - OPM PIP following the tasks discussed below.
Note:
Existing patches for the Design to Release: Agile PLM for Process - OPM 3.1.1 PIP are still applicable in the 11.4 release and are not included as part of the upgrade process. After upgrading you must reapply any patches installed for the RV 3.1.
To upgrade the Design to Release: Agile PLM for Process - OPM PIP from version 3.1 to 3.1.1, you must manually execute the upgrade scripts. You must upgrade Foundation Pack to 11.1.1.6.0, RUP patch 16301959 or later from your existing version before you can upgrade Design to Release: Agile PLM for Process - OPM PIP.
To upgrade the PIP on the Fusion Middleware server, run the command specific to your platform:
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.
Run the command for your platform
Note:
When you copy and paste the command in the command line, ensure that there is space between.xml and -. The same is true when running the undeployment command.
Table 36-13 Deployment Commands for the Design to Release: Agile PLM for Process - OPM PIP
| Platform | Deployment Command |
|---|---|
|
Linux Solaris SPARC IBM AIX Based Systems HP-UX |
ant -f <AIA_HOME>/Infrastructure/Install/AID/AIAInstallDriver.xml -DDeploymentPlan=<AIA_HOME>/pips/PLM4PEbizOPM/upgrade/11.1/PLM4PEbizOPMUpgrade31_To_111DP.xml -DPropertiesFile=<AIA_HOME>/aia_instances/<aia_instance>/config/AIAInstallProperties.xml -l <AIA_HOME>/pips/PLM4PEbizOPM/upgrade/11.1/PLM4PEbizOPMUpgrade31_To_111.log |
|
Microsoft Windows |
ant -f <AIA_HOME>\Infrastructure\Install\AID\AIAInstallDriver.xml -DDeploymentPlan=<AIA_HOME>\pips\PLM4PEbizOPM\upgrade\11.1\PLM4PEbizOPMUpgrade31_To_111DP.xml -DPropertiesFile=<AIA_HOME>\aia_instances\<aia_instance>\config\AIAInstallProperties.xml -l <AIA_HOME>\pips\PLM4PEbizOPM\upgrade\11.1\PLM4PEbizOPMUpgrade31_To_111.log |
Review the log file in the location specified in the command to verify successful deployment.
Perform additional post upgrade tasks as described in Section 36.5, "Performing Postupgrade Tasks for Pre-Built Integrations" and Section 36.6, "Performing Postupgrade Tasks for AIA".
Upgrade Foundation Pack first and then upgrade the Lead to Order: CRM OD -EBS PIP following the tasks discussed below.
Note:
Existing patches for the Lead to Order: CRM OD -EBS 3.1.1 PIP are still applicable in the 11.4 release and are not included as part of the upgrade process. After upgrading you must reapply any patches installed for the RV 3.1.
To upgrade Lead to Order: CRM OD - EBS PIP from version 3.1 to 3.1.1, you must manually execute the upgrade scripts. You must upgrade Foundation Pack to 11.1.1.6.0, RUP patch 16301959 or later from your existing version before you can upgrade Lead to Order: CRM OD - EBS PIP.
To upgrade the PIP on the Fusion Middleware server, run the command specific to your platform:
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.
Navigate to <AIA_HOME>pips/CRMODtoEbizLeadToOrder/upgrade/11.1 and run the command for your platform.
Review the log file in the location specified in the command to verify successful deployment.
Perform additional post upgrade tasks as described in Section 36.5, "Performing Postupgrade Tasks for Pre-Built Integrations" and Section 36.6, "Performing Postupgrade Tasks for AIA".
Upgrade Foundation Pack first and then upgrade the Order to Cash: Siebel CRM - EBS PIP following the tasks discussed below.
Note:
Existing patches for the Order to Cash: Siebel CRM - EBS 3.1.1 PIP are still applicable in the 11.4 release and are not included as part of the upgrade process. After upgrading you must reapply any patches installed for the RV 3.1.
To upgrade the Order to Cash: Siebel CRM - EBS PIP from version 3.1 to 3.1.1, you must manually execute the upgrade scripts. You must upgrade Foundation Pack to 11.1.1.6.0, RUP patch 16301959 or later from your existing version before you can upgrade Order to Cash: Siebel CRM - EBS PIP.
To upgrade the PIP on the Fusion Middleware server, run the command specific to your platform:
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.
Run the command for your platform:
Note:
When you copy and paste the command in the command line, ensure that there is space between.xml and -. Ensure that there is space between these two when you run undeployment command too.
Table 36-15 Deployment Commands for the Order to Cash: Siebel CRM - EBS PIP
| Platform | Deployment Command |
|---|---|
|
Linux Solaris SPARC IBM AIX Based Systems HP-UX |
ant -f <AIA_HOME>/Infrastructure/Install/AID/AIAInstallDriver.xml -DDeploymentPlan=<AIA_HOME>/pips/OrderToCash/upgrade/11.1/OrderToCashUpgrade31_To_111DP.xml -DPropertiesFile=<AIA_HOME>/aia_instances/<aia_instance>/config/AIAInstallProperties.xml -l <AIA_HOME>/pips/OrderToCash/upgrade/11.1/OrderToCashUpgrade31_To_111.log |
|
Microsoft Windows |
ant -f <AIA_HOME>\Infrastructure\Install\AID\AIAInstallDriver.xml -DDeploymentPlan=<AIA_HOME>\pips\OrderToCash\upgrade\11.1\OrderToCashUpgrade31_To_111DP.xml -DPropertiesFile=<AIA_HOME>\aia_instances\<aia_instance>\config\AIAInstallProperties.xml -l <AIA_HOME>\pips\OrderToCash\upgrade\11.1\OrderToCashUpgrade31_To_111.log |
Review the log file in the location specified in the command to verify successful deployment.
Perform additional post upgrade tasks as described in Section 36.5, "Performing Postupgrade Tasks for Pre-Built Integrations" and Section 36.6, "Performing Postupgrade Tasks for AIA".
Upgrade Foundation Pack first and then upgrade the LSP Order Mgmt: OTM - EBS - Siebel CRM PIP following the tasks discussed below.
The steps to upgrade the LSP Order Mgmt: OTM - EBS - Siebel CRM PIP from version 3.1 to version 3.1.1 are the same if upgrading from the AIA 3.1 release to the AIA 11.4 release or the AIA 11.3 release to the AIA 11.4 release.
Note:
Existing patches for the LSP Order Mgmt: OTM - EBS - Siebel CRM 3.1.1 PIP are still applicable in the 11.4 release and are not included as part of the upgrade process. After upgrading you must reapply any patches installed for the RV 3.1.
To upgrade the LSP Order Mgmt: OTM - EBS - Siebel CRM PIP from version 3.1 to version 3.1.1, you must manually execute the upgrade scripts. You must upgrade Foundation Pack to 11.1.1.6.0, RUP patch 16301959 or later from your existing version before you can upgrade the Order to Cash: Siebel CRM - EBS PIP.
Note:
If you have not installed the 11.4 AIA release, run the AIA 11.4 installer on your existing AIAHOME to get the latest version of the files.
To upgrade the LSP Order Mgmt: OTM - EBS - Siebel CRM PIP on the Fusion Middleware server, run the command specific to your platform:
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.
Navigate to $AIA_HOME/pips/FleetOrderManagement/upgrade and run the command from your platform.
Review the log file in the location specified in the command to verify successful deployment.
Perform additional postupgrade tasks as described in Section 36.5, "Performing Postupgrade Tasks for Pre-Built Integrations" and Section 36.6, "Performing Postupgrade Tasks for AIA".
You must perform the following key tasks after you successfully upgrade to pre-built integrations 11.4:
Deploy any custom processes that were developed.
If you plan to use any of the enhanced or new features in pre-built integrations 11.1, including the EBO changes, you must update these custom processes before re-deployment.
Merge extensions.
Any xsl extensions and wsdl customizations maintained in AIA HOME / SOA HOME must be merged with the preupgrade back up changes after comparison.
Restore customizations.
Any custom code developed and maintained in AIA HOME / SOA HOME must be restored.
Upgrading ABCS Service Generator input.xml
The input.xml files created in previous versions of the pre-built integrations do not directly work with 11.1.1.6.0 version of ABCS Service Generator. You must move GenerateReferenceWSDLFileIndicator element from GenerateOutputFiles section to each TargetService where you must reference the WSDL. This flag must be added to each of the targetservice sections.
Log in to the AIA Console to verify that the following components are working:
OER (optional):
Ensure that the services and objects can be searched for and viewed. If you had any integration scenarios published, check whether they are accessed as well.
CAVS:
Check that the existing Test and Simulator definitions defined can still be viewed and are functional.
Error Handling and Setup:
Verify that the existing setup data (Setup Tab Page) is unchanged and two new columns (ERROR_TYPE, ERROR_EXT_HANDLER) are added to the Error Notifications table.
Perform additional post upgrade tasks as described in Section 36.6, "Performing Postupgrade Tasks for AIA".
Evaluate the upgrade log file for any exceptions or warnings:
For pre-built integrations, the upgrade DP log is created on the name of the integration. For example, if you are upgrading the CRMOD to Ebiz Lead to Order PIP, the name of the log file is AIA_HOME/pips/CRMODtoEbizLeadToOrder/upgrade/11.1/CRMODtoEbizLeadToOrderUpgradeDP31_TO_111.log.
The following warning message describes the EOL content:
runCustomExtTracer:
[java] java.io.UTFDataFormatException: Invalid byte 1 of 1-byte UTF-8 sequence.
For objects that were identified to have been extended, the AIA Pre-Built Integrations Installer logs the list of EBOs that it found extended by you. These are reported in the following way:
[java] /slot/ems1846/oracle/FP_Upgrade_9June_1/patchset/AIAComponents/EnterpriseObjectLibrary/Core/Custom/EBO/InstalledProduct/V2/CustomInstalledProductEBO.xsd
[java] :[Element: <xsd:sequence [Namespace: http://www.w3.org/2001/XMLSchema]/>]element updated
Every major task performed by the AIA Pre-Built Integrations Installer is audited in the file. Here are some sample audit comments:
undeployAIAUI:
[echo] - Undeploying the Ear AIAApplication.ear
[java] 08/08/09 16:12:33 Notification ==>Application UnDeployer for AIAApplication STARTS.
DeployAIAUI:
[echo] - Deploying the Ear AIAApplication.ear
[oracle:deploy] Deploying application AIAApplication.
[oracle:deploy] Application deployer for AIAApplication COMPLETES.
[echo] - Deployment of AIAApplication.ear completed
From the backups that you performed, compare the following files and manually merge the configuration settings, as required:
You should consider restoring files from the backups of the <aia_instance>/AIAMetaData/config folder.
For more information about how to perform implementation-related configurations, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack.
|
 Copyright © 2001, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
