Oracle Application Integration Architecture 2.5 Installation Summary
Over the past few weeks, Prōject has been installing and testing Oracle’s Application Integration Architecture and the Project Portfolio Management Integration Pack for Primavera P6 and Oracle E-Business Suite 2.5. This article summarises the technical installation process.
Summary of Tips to avoid issues
Details of the following are contained in this article:
- If installing on 64-bit OS use a 32-bit shell if the software is 32-bit
- Disable SELinux during OS install
- Be very careful when entering connection details in OSR, AIA and PIP install otherwise install will fail
- Deploy the OSR application manually after installation
- Do not create a database user called AIA before the AIA Foundation Pack install
- Alter timeout values before PIP installation
- AIA Foundation Pack and PIP install guide has sections to record the information that will be required during installation – use it!
- Be careful which java version is in use when installing OSR
Software versions
- Database – This needs to be 10.2.0.2 or higher for certification with SOA. We used 10.2.0.4.
- Oracle Service Orientated Architecture Suite (SOA) – 10.1.3.4 + MLR#8 or later. We used 10.1.3.5.
- Oracle Application Server (OAS) 10g Release 3
- Oracle Service Registry (OSR) 10.3.0 (Optional)
- Oracle Application Integration Architecture (AIA) 2.5
- Oracle Project Portfolio Management: Primavera P6-EBS Projects PIP 2.5
Hardware
The installation was performed on a virtual machine (VMware) which was allocated 2 virtual CPU’s, 2G of memory and 50G of disk space. This virtual machine is running on top of 64-bit AMD hardware.
OS Install
It was decided to use Oracle Enterprise Linux 5.4 64-bit and then where available 64-bit versions of the other software. The install was standard, however SELinux needs to be disabled for the database software, this can be done during installation or switched off after.
Database Install
The installation of SOA will require a database of 10.2.0.2 or higher, so it was decided to stay with 10g but use the latest release which is 10.2.0.4. This gives a reasonable balance of support lifetime and stability. As we are on 64-bit hardware, we decided to fully utilize this and install the 64-bit version of the software.
All pre-requisites can be found in the installation guide and should be checked for the relevant platform.
A standard install was performed, and a normal empty database was created during the installation. We called our database AIA.
To install 10.2.0.4 it is necessary to install 10.2.0.1 and then apply 10.2.0.4 patchset. You will then need to upgrade the database created during installation to 10.2.0.4 with dbua.
SOA Install
The first step of installing SOA is to create the necessary schema’s in the database created in the previous step. This is done by running the irca.sh script which is found on the installation media under Disk1/soa_schemas/irca.
Before running the installer various pre-requisite patches are required. These enable the installer to run. Check the documentation for the latest patches needed.
As the SOA suite is 32-bit software I ran the installer in a 32-bit shell by issuing the ‘linux32 bash’ command.
To run the installer use runInstaller along with parameters that are detailed in the pre-requisite patches. E.g:
./runInstaller PREREQ_CONFIG_LOCATION=/home/oracle/Software/1031SOA/6339508/prereq -paramFile /home/oracle/Software/1031SOA/6339508/oraparam.ini
Perform an advanced installation and select J2EE Server, Web Server and SOA Suite:
Make the OC4J instance an Administration instance (on Administration Settings page):
and do not select ‘Access this OC4J Instance from a separate Oracle HTTP Server’ on the Cluster Topology screen.
Once the installer completes SOA 10.1.3.1 will have been installed.
Upgrade SOA to 10.1.3.5
In order to get SOA to the latest available version patchset 10.1.3.5 was applied. This involves running scripts to upgrade the bpel and esb schema’s, bouncing the database and then running the installer. Again a 32-bit bash shell was used for this.
Install OC4J instance
Oracle Service Registry is optional in this technology stack, but if it is being installed a separate OC4J instance is required for this (Oracle AquaLogic Service Registry can be used instead – this has to be installed into Oracle WebLogic Server rather than an iAS OC4J instance).
The media for this is the same as for the SOA install, again run in a 32-bit bash shell and use the parameters to runInstaller supplied in the pre-requisite patches.
This time just install a standalone OC4J instance (into a separate Oracle Home to SOA).
Install Oracle Service Registry
One of the pre-requisites for OSR is an install of JDK. The version of this affects how well the installer runs. I found the JDK installed with the database worked fine (JDK 1.4.2_14), so set your environment to use this.
Also required are a database – use the one installed earlier, and an application server – use the OC4J install as detailed above.
Once again perform the install in a 32-bit bash shell. To run the installer, use the supplied jar file Oracle-service-registry-10.3.jar (requires an x windows session so have DISPLAY set suitably).
The installer will ask for various connections details etc, be very careful when entering these as a slight error (eg wrong case) can cause the install to fail.
When I tried to deploy the app through the installer it kept failing, so I opted to deploy manually after installation (untick the checkbox on the application server details page). To manually install login to Enterprise Manager (OC4J instance), select the OC4J jvm and applications deploy. The OSR installation will have created the necessary ear file for you to use to deploy.
Install AIA Foundation Pack
Before installing the AIA Foundation Pack, various pre-requisites need to be met (details can be found in the installation guide):
- Configure Fusion Middleware memory Settings
- Configure java transaction API transaction timeout value
- Enabling Directory Browsing in the Apache Server
- Download and install JDK 1.5_16 or above
- Grant sysdba to system
The last of the pre-requisites is because the installer needs a database login with sysdba privilege. Do not create a new user called AIA to fulfil this requirement as the installer tries to create a new user with this name and will fail if the user already exists. Revoke this after the installation.
The installation guide provides a check list of required information needed during the installation. I would recommend using this to acquire the information before hand.
Run the installer pointing the inventory location to the oraInst.loc file in the SOA Oracle HOME:
./runInstaller –invPtrLoc <SOA_HOME>/oraInst.loc
On the first screen select the Foundation Pack to install and set the Oracle Home to a suitable value.
If the installer fails for any reason that install needs to be completely cleared out before re-attempting the installation. Please see Oracle note 876044.1 for details of the procedure to do this.
Install Project Portfolio Management: Primavera P6-EBS PIP
The final stage of this tech stack build was to install the product specific AIA PIP.
In order to avoid timeout errors during installation set the following timeout limits (reset after install):
Update the transaction-timeout=”3000″ value in the
<ORACLEHOME>j2eeoc4j_soaconfigtransaction-manager.xml
Change the syncMaxTime to 300 in the
<ORACLE_HOME>bpeldomainsdefaultconfigdomain.xml
The following pre-requistes are required in the E-Business suite install:
- EBS 11.5.10 CU2
- Patch 5644830 for Oracle Projects Rollup Patch 4 for Oracle Projects Family Pack M (11i.PJ_PF.M)
- Patch 3485155 for 11iPJ_PF.M
- Patch 8979063 for 11I.MRUP4 : Projects AIA Third Party Application Integration Cumulative Checkin
To actually install the PIP use the AIA installer as per the Foundation Pack install but select the PIP to install.
Thanks, a good document for starters. Highly appreciated
If you can provide me step by step methodology of Primavera Integration with Oracle Projects that will be great.
Its depicted in the integration document that you are using a request called Project Integration Synchronisation…………………. how do you populate the request
Thanks and Regards
Shiva Kumar
Thank you for the overview, it is very focused and helpful.