Integration Repository Parser is a standalone design-time tool used by the integration administrator to validate annotated custom interface definitions against the annotation standards and generate an Integration Repository loader file (iLDT). The generated iLDT files are uploaded to the Integration Repository using the FNDLOAD command so that the custom interfaces can be searched, generated, and deployed from the Integration Repository user interface.
Note: Integration Repository Parser does not support the integration interfaces registered under custom applications.
Before executing the Integration Repository Parser, you need to install Perl modules with the following steps:
Note: It is required to obtain a native C compiler for the platform and operating system version that you are running on to build the Perl modules. The following are the minimum versions of compilers certified for Oracle E-Business Suite platforms:
Linux x86-64: Intel C/C++ Compiler (icc) version 7.1.032
Oracle Solaris on SPARC (64-bit): Oracle Studio 12
HP-UX Itanium: HP ANSI C B3910B A.0.06.05
IBM AIX on Power Systems (64-bit): XL C Enterprise 8.0
Microsoft Windows platform is currently not supported in this release.
Installing Perl Modules on all UNIX platforms
Perform the following steps to install Perl modules on all UNIX platforms mentioned above:
Establish the Oracle E-Business Suite application environment.
From the Oracle E-Business Suite APPS_BASE, establish the run file system APPL_TOP environment by running the EBSapps.env script.
In both the run and patch file systems, locate the Perl configuration files that need to be modified and back up these files.
For example, on Oracle Solaris, the Config.pm is located in the following directory:
$FMW_HOME/webtier/perl/lib/5.10.0/sun4-solaris-thread-multi-64
In both the run and patch file systems, modify the Perl configuration file Config.pm to point to the Perl directory in $FMW_HOME/webtier.
For example, on Oracle Solaris, these are the statements that need to be modified with the absolute path of $FMW_HOME/webtier/perl:
Note: <FMW_HOME> is the value of $FMW_HOME.
archlibexp =>relocate_inc('<FMW_HOME>/webtier/perl/lib/5.10.0/sun4-solaris-thread-multi-64')
privlibexp =>relocate_inc('<FMW_HOME>/webtier/perl/lib/5.10.0')
sitearchexp =>relocate_inc('<FMW_HOME>/webtier/perl/lib/site_perl/5.10.0/sun4-solaris-thread-multi-64')
sitelibexp =>relocate_inc('<FMW_HOME>/webtier/perl/lib/site_perl/5.10.0')
If your system is on Oracle Solaris, modify the Config.pm and Config_heavy.pl files to point to the C compiler installed as a requirement of the Integration Repository Parser. For example:
Config.pm
cc =>'/opt/SunProd/studio12u3/solarisstudio12.3/bin/cc',
libpth =>'/opt/SunProd/studio12u3/solarisstudio12.3/lib /opt/SUNWspro/WS6U1/lib/v9 /usr/lib/sparcv9 /usr/ccs/lib/sparcv9 /usr/local/lib/usr/lib /usr/ccs/lib,
Config_heavy.pl
cc='/opt/SunProd/studio12u3/solarisstudio12.3/bin/cc'
ld='/opt/SunProd/studio12u3/solarisstudio12.3/bin/cc'
Create a directory 'perl' in $APPL_TOP_NE where the new Perl modules will be installed. For example,
mkdir $APPL_TOP_NE/perl
chmod 755 $APPL_TOP_NE/perl
In the run file system, set the following environment variables in APPL_TOP environment:
Prepend PATH with the path to the C compiler installed as a requirement of the Integration Repository Parser.
Prepend PERL5LIB with $FND_TOP/perl and $APPL_TOP_NE/perl in that order.
For example, export PERL5LIB=$FND_TOP/perl:$APPL_TOP_NE/perl:$PERL5LIB.
Add $FMW_HOME/webtier/lib to LIBPATH if it is not present.
For example, export LIBPATH=$LIBPATH:$FMW_HOME/webtier/lib.
Set $FMW_HOME/webtier as ORACLE_HOME.
For example, export ORACLE_HOME=$FMW_HOME/webtier.
Prepend LD_LIBRARY_PATH with $ORACLE_HOME/lib32 and $ORACLE_HOME/lib.
For example, export LD_LIBRARY_PATH=$ORACLE_HOME/lib32:$ORACLE_HOME/lib:$LD_LIBRARY_PATH.
Set JAVA_HOME to the JDK top directory.
Obtain the path returned by 'which java' and set JAVA_HOME to the current JDK top directory.
For example, on Oracle Solaris:
which java /prod/EBS122/fs1/FMW_Home/jdk/jre/bin/java export JAVA_HOME=/prod/EBS122/fs1/FMW_Home/jdk
Download and unzip patch 13602850 (p13602850_R12_GENERIC.zip) into a temporary area.
Patch 13602850 contains the following Perl modules:
Compress-Raw-Zlib-2.009
Compress-Zlib-2.009
Class-MethodMaker-1.12
Install these modules in the order shown above using the following commands:
Note: If Perl command is not found, invoke Perl in $FMW_HOME/webtier/perl/bin/perl.
For Oracle Solaris, AIX, and HP-UX Itanium platforms Only
After installing the Compress-Raw-Zlib-2.009 Perl module but before installing Compress-Zlib-2.009, prepend PERL5LIB with $APPL_TOP_NE/perl/lib/5.10.0/<platform thread-multi directory>.
For example, on Oracle Solaris:
export PERL5LIB=$APPL_TOP_NE/perl/lib/5.10.0/sun4-solaris-thread-multi-64:$PERL5LIB.
cd $APPL_TOP_NE/perl
Copy the module to be installed into $APPL_TOP_NE/perl.
For example: cp -r /temp/Compress-Raw-Zlib-2.009 .
cd <Perl module name>
For example: cd Compress-Raw-Zlib-2.009
perl Makefile.PL
Note: On HP-UX Itanium, the option CC=cc may be needed when installing Compress-Raw-Zlib-2.009. For example, perl Makefile.PL CC=cc.
If errors occur, verify your setup and remove the Perl module being installed from $APPL_TOP_NE/perl before copying it into $APPL_TOP_NE/perl to try again.
make
Note: If the 'cc' compiler is not found, verify the LD parameter in the Makefile contains the correct path to the C compiler executable.
If the following warning appears on Oracle Solaris, replace -xarch=v9 with -m64 throughout the Makefile, and run make again.
cc: Warning: -xarch=v9 is deprecated, use -m64 to create 64-bit programs
make install
Once the Integration Repository Parser has been installed and set up properly, you can execute the parser to generate iLDT files and then upload them to the Integration Repository if no error occurs.
Note: For an object (or class) which is present in the Integration Repository, the Integration Repository Loader program reloads the new definition of that object ONLY if the new version is greater than the current version present in the Integration Repository. If the new file version is the same or lower than the current one in the repository, then the new file will not be uploaded.
Therefore, before executing the parser, you need to increment the Header version of the target source file so that the modifications to the object defined in the source file can take effect in the Integration Repository.
The following sections explain the use of Integration Repository Parser and FNDLOAD utilities in greater detail.