How to integrated Soa Gateway Oracle EBS R12
1.1 Upgraded with Oracle Application
Server 10g Release 3 (10.1.3) Patch Set 5 (10.1.3.5.0)
Perform the following steps for enabling Oracle E-Business Suite Integrated
SOA Gateway Release 12.1.3 upgraded from Oracle E-Business Suite Release 12.1.X
with Oracle Application Server 10g Release 3 (10.1.3) Patch Set 5
(10.1.3.5.0):
- Follow the instructions on My
Oracle Support Knowledge Document 454811.1 to upgrade your system to
Oracle Application Server 10g Release 3 (10.1.3) Patch Set 5
(10.1.3.5.0).
- Ensure that Oracle E-Business
Suite Release 12.1.3 is applied.
Note: For instructions on how to apply the Release 12.1.3, see "Oracle E-Business
Suite Applications Technology Readme for Release 12.1.3", My Oracle Support Knowledge
- Source the file
$INST_TOP/ora/10.1.3/.env and then apply the following patches to the
Oracle Application Server 10.1.3.5 Oracle Home:
- Patch 13800972: Merge Request on Top of
10.1.3.1.0 for Bugs 8857799 9223438 12352047 (Patch 13800972 is also compatible with
Oracle Application Server 10.1.3.5.0.)
- Patch 9371120: Web Service Framework Takes
More Time for Giving the Response
- Patch 7366746: WLP: Enabling "Use SAML
Authority: Verify Signature" Doesn't Require SAML Token
- Patch 15914125: Merge Request on Top of
10.1.3.5.1 for Bugs 9187189 9668283 13248533
Note: These enabling steps apply to any
of the following business scenarios:
- If your system is on Oracle
E-Business Suite Release 12.1.3 with Oracle Application Server 10g
Release 3 (10.1.3) Patch Set 5 (10.1.3.5.0) upgraded from 10.1.3.4.0.
- If your system is on Oracle
E-Business Suite Release 12.1.3 with Oracle Application Server 10g
Release 3 (10.1.3) Patch Set 5 (10.1.3.5.0).
|
- After the upgrade, you will
need to perform necessary configuration tasks to enable Oracle E-Business
Suite Integrated SOA Gateway.
1.2 Configuring Oracle E-Business Suite Integrated SOA Gateway Release
12.1.3
1. Apply the following
Oracle E-Business Suite patches:
o Patch 13516999:R12.OWF.B: Performance
Degradation of Web Service Calls Hosted in R12 SOA Gateway
- Patch ve konfigürasyonlar.
Set applications environment and stop all application tier processes.
- From the applications instance
$APPL_TOP, set the environment by running the
APPS<CONTEXT_NAME>.env script
- Stop all application tier
processes for the instance by running the script $ADMIN_SCRIPTS_HOME/adstpall
- Run TXK development script to
install Oracle Application Server Adapter for Oracle Applications as shown
below:
$FND_TOP/bin/txkrun.pl -script=CfgOC4JApp -applicationname=pcapps
-oracleinternal=Yes -oc4jpass=welcome -runautoconfig=No
Note: If the 'oc4jadmin' password for the OAFM oc4j instance is not known, then reset the password in the file $INST_TOP/ora/10.1.3/j2ee/oafm/config/system-jazn-data.xml before running the script. Take the backup of system-jazn-data.xml before resetting the password. Replace the modified system-jazn-data.xml with backup of system-jazn-data.xml after running the script.
For example, if you want to reset the password to '!welcome', below should be the entry:
<user>
<name>oc4jadmin</name>
< display-name>OC4J Administrator</display-name>
< guid>23C8E4F0BDDE11DCBFB8AF3B7E0DDB2D</guid>
< description>OC4J Administrator</description>
< credentials>!welcome</credentials>
</user>
- Enable the new container
forms-c4ws. (By default, the new OC4J container forms-c4ws will be
disabled.)Run TXK deployment script to
install forms-c4ws.ear and configure container Forms-c4ws J2EE group
correctly, as shown below:
$FND_TOP/bin/txkrun.pl -script=DeployForms-c4ws
To enable the new container forms-c4ws, modify the following values of
context variables in the $CONTEXT_FILE:
·
Set 's_forms-c4wsstatus' to "enabled".
·
Set 's_forms-c4ws_nprocs' to "1".
Note: The 's_forms-c4ws_display'
context variable is used by the forms-c4ws OC4J instance. It must be set
properly in order to use the Java APIs for Forms interfaces. This display
must always be accessible during runtime. It should be set to an active and
authorized X Windows display, and should point to a machine that is always
available to the application instance.
If you are
planning to use the Supply Chain Management (SCM) Web services (Java APIs for
Forms interfaces) published in Oracle Integration Repository that encapsulate
Oracle Forms logic, see "Oracle E-Business Suite Java APIs for Forms
Troubleshooting Guide, Release 12", My Oracle Support Knowledge Document
966982.1 for latest troubleshooting
information related to SCM Web services.
|
- Run AutoConfig script present
in $ADMIN_SCRIPTS_HOME on the application tier. For example,
$ADMIN_SCRIPTS_HOME/adautocfg.sh
Ensure to start up the middle tier when AutoConfig script completes. For
information on how to run AutoConfig, see "Using AutoConfig to Manage
System Configurations in Oracle E-Business Suite Release 12", My
Oracle Support Knowledge Document 387859.1 for details.
- Start all application tier
processes for the instance by running the script
$ADMIN_SCRIPTS_HOME/adstrtal
- Enable ASADMIN user using the
following steps:
- Log on to Oracle E-Business
Suite using sysadmin/sysadmin.
- Select the User Management
responsibility in the Navigator.
- Click the Users link from the
navigation menu to open the User Maintenance window.
- Locate 'ASADMIN' user by
entering information in the search area to retrieve the 'ASADMIN' user.
- Click the Update icon
next to the ASADMIN user to open the Update User window.
- Remove the Active To date
field and click Apply.
- Click the Reset Password
icon next to the ASADMIN user to open the Reset Password window.
- Enter new password twice and
click Submit.
- After activating the ASADMIN
user, verify if the ASADMIN user has the 'Apps Schema Connect Role'
(UMX|APPS_SCHEMA_CONNECT) role in wf_user_roles.
If the 'Apps Schema Connect Role' role is not present in the wf_user_roles
for the ASADMIN user, then run the 'Workflow Directory Services User/Role
Validation' concurrent program to grant the role.
- Reset the 'ASADMIN' password in
the file system.
After 'ASADMIN' user is enabled from Oracle E-Business Suite, update the
file
$INST_TOP/ora/10.1.3/j2ee/oafm/config/system-jazn-data.xml as shown below
to reset the password:
<user>
< name>ASADMIN</name>
< display-name>Default Apps SOA User</display-name>
< description>Used by SOAProvider for DB
connection</description>
< credentials>!<NEW PASSWORD></credentials>
< /user>
Note: The password should be preceded
by a '!' (Exclamation) so that when OAFM is started,
it gets encrypted. For example, if your password is 'welcome', then you
should write it in the above file as "!welcome".
|
Bounce the middle tier.
Step 6: Install the Perl Modules
as per Note: 1079218.1
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/x86-64: Intel C/C++ Compiler (icc)
version 7.1.032
Oracle Solaris on SPARC (64-bit): Oracle
Studio 11 (5.8)
Microsoft Windows Server (32-bit): Microsoft
Visual Studio 2005 (VC 8.0)
HP-UX Itanium: HP ANSI C B3910B
A.0.06.05
HP-UX PA-RISC (64-bit): HP92453-01 B.11.11.10
HP C Compiler
IBM AIX on Power Systems (64-bit): XL C
Enterprise 8.0
Prerequisites
for Installing Perl Modules on Windows
Perform the following steps before installing Perl modules on
Windows:
1. Apply Windows
specific Patch 9153106:R12.OWF.B.
2. It is necessary to
create a manifest file for perl.exe in the 10.1.3Home\perl\5.8.3\bin\MSWin32-x86-multi-thread
directory if your installation is on Windows.
To create a manifest file for perl.exe:
a. Log
on to the Oracle E-Business Suite middle-tier server.
b. Change directories to c:\WINDOWS\WinSxS.
c. Verify if there is a file that starts with x86_Microsoft.VC80.CRT.
For
example, x86_Microsoft.VC8.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd.
d.
Record this filename.
e. Change directories to where the perl.exe resides in the 10.1.3 Home. For
example,
cd
e:\PROD\apps\tech_st\10.1.3\perl\5.8.3\bin\MSWin32-x86-multi-thread
f.
Open a file with text editor (such as Notepad) to create a manifest file.
g. Enter the following statements, for example, with the 'version' and
'publicKeyToken' taken from the x86_Microsoft.VC80.CRT file name:
manifestVersion='1.0'>
version='8.0.50727.42' processorArchitecture='x86'
publicKeyToken='1fc8b3b9a1e18e3b'/>
h.
Save the file with the name perl.exe.manifest.
To install Perl
modules:
1. Set the Oracle
E-Business Suite application environment
From the Oracle E-Business Suite application instance APPL_TOP, set the
environment by running the APPSAPPS.env(.cmd) script.
2. Set 10.1.3
ORACLE_HOME
Navigate to the /ora/10.1.3 and source the .env/.cmd file to set your 10.1.3
ORACLE_HOME.
3. Add directory $FND_TOP/perl
to environment variable PERL5LIB:
a.
Find physical path of $FND_TOP/perl.
b. Add this physical path in PERL5LIB variable.
Example:
export
PERL5LIB=/slot/ems3404/appmgr/apps/apps_st/appl/fnd/12.0.0/perl:/slot/ems3404/appmgr/apps/tech_st/10.1.3/perl/lib/5.8.3:/slot/ems3404/appmgr/apps/tech_st/10.1.3/perl/lib/site_perl/5.8.3:/slot/ems3404/appmgr/apps/apps_st/appl/au/12.0.0/perl:/slot/ems3404/appmgr/apps/tech_st/10.1.3/Apache/Apache/mod_perl/lib/site_perl/5.8.3/i686-linux-thread-multi.
4. Use the following
steps for installation on different platforms:
On Unix:
a. Find
the value of $IAS_ORACLE_HOME/perl in your environment,
/oracleapp/EBSR12/apps/tech_st/10.1.3/perl
For
example /slot/ems1340/appmgr/apps/tech_st/10.1.3/perl.
b.
Locate the $IAS_ORACLE_HOME/perl/lib/5.8.3/i686-linux-thread-multi/Config.pm.
c. Take backup of this file.
d. Replace all occurrences of
/ade/smayer_perl58_main_linux/perl58/bin/Linux/Opt with value of
$IAS_ORACLE_HOME/perl.
For
example, /slot/ems1340/appmgr/apps/tech_st/10.1.3/perl.
On Windows:
a.
Search for all Config.pm files underneath %IAS_ORACLE_HOME%\perl, and record
their location, such as:
%IAS_ORACLE_HOME%\perl\5.8.3\bin\Config.pm
%IAS_ORACLE_HOME%\perl\5.8.3\lib\MSWin32-x86-multi-thread\Config.pm
b. For
each Cofing.pm file, modify all parameters that point to perl with the correct
location of %IAS_ORACLE_HOME%\perl.
For
example, In the %IAS_ORACLE_HOME%\perl\5.8.3\bin\Config.pm file, modify
archlibexp from '%ORACLE_HOME%\perl\5.8.3\lib\MSWin32-x86-multi-thread to
e:\PROD\apps\tech_st\10.1.3\perl\5.8.3\lib\MSWin32-x86-multi-thread.
c. For
each Cofing.pm file, modify all parameters that point to Visual C++ with the
correct location of Visual C++. The location of Visual C++ is identified
through the msdevdir parameter in the context file at %INST_TOP%\apps\admin\.xml.
For
example, in the
%IAS_ORACLE_HOME%\perl\5.8.3\lib\MSWin32-x86-multi-thread\Config.pm file,
modify libpth to the correct location of Visual C++:libpth=d:\VC8\VC\lib
(d:\VC8\VC is an example).
5. Search and download
the following Perl modules that are required to be installed manually from
CPAN:
For
example, use the following steps to install Compress-Raw-Zlib-2.009.tar.gz:
#gzip -d
Compress-Raw-Zlib-2.009.tar.gz
tar -xvf Compress-Raw-Zlib-2.009.tar
cd Compress-Raw-Zlib-2.009
On Unix:
perl
Makefile.PL
make
make install
Note: Ignore
any warning in make command.
On Windows:
perl
Makefile.PL
nmake
nmake install
