Some
features of Oracle SOA behave differently in the cloud than in an on premises environment.
Some
features of Oracle SOA behave differently in the cloud than in an on premises environment.
File adapter read actions — each managed server only reads from its local directory.
JMS store and JTA transaction logs must use the Oracle database instead of file stores.
Oracle B2B large
file processing Files are written to the local file system of the managed server
that
processes the message. The Oracle B2B Console cannot read the file unless it is running on the same
managed server (you see random behavior).
Connectivity between Oracle SOA Cloud
Service adapters and onpremises applications might be blocked by your corporate firewall. Connections can be established by using
an
SSH tunnel from the application server
to which
the adapter connects.
The SOA debugger and automatic SOA composite application tester (unit tester) in Oracle JDeveloper are not
supported when
connecting to the SOA Cloud
Service server.
Reports are not
supported in Oracle RealTime Integration Business Insight, installed as part of the Integration Analytics Cluster service type.
The iWay application adapters listed under Application Adapters (iWay) on Oracle Cloud Adapters
Documentation (http://www.oracle.com/technetwork/middleware/adapters/documentation/index.html) are not supported by Oracle SOA Cloud Service.
The Oracle Traffic Director high availability features 12.2.1.2 (http://www.oracle.com/pls/topic/lookup? ctx=fmw122120&id=GUID7535D97D6EBD49698A6DC736B44C5555) /12.1.3 (http://www.oracle.com/pls/topic/lookup? ctx=fmw121300&id=GUID7535D97D6EBD49698A6DC736B44C5555) are not supported with Oracle SOA Cloud Service.
Dehydration does work in the cloud
as
it does in the onpremises environment as described in Fusion Middleware Administering Oracle SOA Suite
and
Oracle Business Process Management Suite 12.2.1.2
(http://www.oracle.com/pls/topic/lookup?ctx=fmw122120&id=GUIDDBCFFB8F3B6740009F48404D16D503DD) /12.1.3
No comments:
Post a Comment