Enabling OTA for R12 :
Rather than manually modifying the orion-web.xml file, do
the following to set the Autoconfig oavar variable:
1) Logon as the System Administrator Responsibility.
2) Under Oracle Applications Manager, select Autoconfig.
3) Click the icon for Edit Parameters on the Applications
tier.
4) Click on the System tab.
5) Look under oa_web_server for Load OXTA Servlet
(s_load_oxta_servlet).
6) If this is currently set to -1 (default disabled
configuration), you need to set the value to 1 (enable).
7) Look in this same section for the following and set as
needed (if you have a proxy server that http/https communications need to go
through):
OXTAOutUseProxy (s_oxta_proxy)
OXTAOutProxyHost (s_oxta_proxyhost)
OXTAOutProxyPort (s_oxta_proxyport)
Once you make changes, you will need to run Autoconfig to
apply them and then bounce the applications tier to start up the OXTA.
Additional Parameters that are Set Through AutoConfig for
XML Gateway OTA:
applSysSchema : APPLSYS (this indicates queues are in
applsys schema)
OXTAInPoolSize=1
OXTAOutThreads=1 (These 2 set the number of DB connections
in your system for inbound and outbound requests)
OXTAOutUseProxy
OXTAOutProxyHost
OXTAOutProxyPort (These control whether a proxy is used for outgoing
socket connections).
Parameters not Set Through AutoConfig:
OXTAOutBaseTimeout =10
OXTAOutLinearTimeout = 500
OXTAOutMaxAttempts= 5 (these control the time allowed for
transactions to complete).
OXTAInMaxContent=1000000 (maximum payload size in bytes).
Preserving Autoconfig parameters
To preserve parameters for XML Gateway in Autoconfig that do
not appear via the web interface, please refer to:
Note 829449.1 - Preserve System Properties Customized For
Your ECX (XML Gateway)
Inbound OTA URL
The new parameter for posting inbound XML transactions to
OTA is now the following URL:
12.1.1+ OTA Failure
The OAFM Container will not start OTA if the ASADMIN EBS user
is not enabled.
Error:
Exception creating connection pool. Exception:
oracle.oc4j.sql.DataSourceException: Exception setting the property 'dbcFile'
on the DataSource. Exception: java.lang.reflect.InvocationTargetException
Note 1087499.1 - Cannot Start OXTA After Upgrade To R12.1.x
Solution: Setup/Configuration Changes
In E-Business Suite Applications (EBS) Release 12 (R12) and
Release 12.1 (R12.1), Jserv is no longer used in the applications tier for java
components. It has been replaced by the Oracle Containers for J2EE (OC4J)
component. The configuration and setup for Oracle Transport Agent (OTA) has
changed accordingly.
In EBS Release 11i instances where OTA was utilized, OTA ran
under Jserv having its properties set in the files found in the directory:
$IAS_ORACLE_HOME/Apache/Jserv/etc
11.5.10/11.5.10.2 - xmlsvcs.properties
For R12 (versions 12.0.X or 12.1.X) , OTA is run in the oafm
container under OC4J. The system properties are read from the oc4j.properties
file of the oafm container located in the file
$INST_TOP/ora/10.1.3/j2ee/oafm/config/oc4j.properties
There is also an autoconfig property,
<load-on-startup>, as reflected in the orion-web.xml file:
$INST_TOP/ora/10.1.3/j2ee/oafm/application-deployments/oafm/webservices/orion-web.xml
In the orion-web.xml file the following section will be
found:
<!-- OXTA Servlet -->
<load-on-startup>1</load-on-startup>
To verify that OTA is started, the value of the attribute
<load-on-startup> in orion-web.xml should be set to 1 for enabled. By
default, this is set to -1, or disabled.
The AutoConfig oavar name for <load-on-startup> is
s_load_oxta_servlet.