Siebel Application Integration for Oracle Fusion Middleware Guide > Working with Web Services Using SAI for Oracle Fusion Middleware >

Compliance Standards for SAI for Oracle Fusion Middleware Web Services


This topic provides various standards with which Siebel Application Integration for Oracle Fusion Middleware (SAI for Oracle Fusion Middleware) is compliant.

Table 4 provides a comparison of Oracle Fusion Middleware technology artifacts with the Siebel Business Applications equivalents.

Table 4. Artifacts Comparison Between Oracle Fusion Middleware and Siebel Business Applications
Artifact
Oracle Fusion Middlware Technology
Siebel Business Applications Equivalent

SOAP version

1.1 and 1.2

1.1

JCA version

1.5

1.0

WS-Security version

1.1

1.0 (partial)

Soap binding

JAX-WS 2.1

DOC_LITERAL
RPC_LITERAL
RPC_ENCODED

Attachments

MTOM - XOP

Base64Binary

Programming model

WebService for Java EE 1.2

Proprietary

Asynchronous communication

WS-Addressing 1.0

N/A

Advertisement
(registration and discovery)

UDDI 2.0

Java API for XML Registries (JAX-R) 1.0

N/A

Enterprise Java Beans version

3.0

N/A

JAX-RS for RESTful (Representational State Transfer) services

Supported

N/A

Data binding

Java Architecture for XML Binding (JAXB) 2.1

String data types

Table 5 provides a comparison of SAI for Oracle Fusion Middleware features with Siebel EAI equivalents.

Table 5. Feature Comparison of SAI for Oracle Fusion Middleware with Siebel EAI Equivalents
Features
Siebel EAI
SAI for Oracle Fusion Middleware
Customer Benefits

Integration development

Siebel Tools, C++

JDeveloper, Java

  • Integration based on standards and decoupled from Siebel-specific technologies
  • Reduced integration cost

Service design and extensibility

Repository, SRF dependent

Dynamic

  • Zero downtime for the Siebel enterprise
  • Ease of development and deployment

Service versioning

No in-built versioning

Fusion Middleware-based versioning

  • Compatible across releases
  • Low upgrade cost and risk

Service interoperability

Limited, no standard compliance

WS Basic Profile 1.1

  • Distributed coexistence
  • Platform, language, and application independent

Server-managed session pooling

None
(client manages sessions)

Managed JCA connection pool based on impersonation

  • No reliability or performance concerns due to suboptimal client session handling
  • Not vulnerable to Denial of Service (DOS) attacks because sessions are managed by Oracle WebLogic Server rather than the client

Monitoring and management

  • Minimal monitoring supported using Server manager
  • No versioning capability
  • Oracle WebLogic Administration Console provides detailed user interface-based monitoring for all connections, requests, and parameters
  • Ability to switch between versions
  • Preconfigured diagnostics and management
  • Oracle Enterprise Manager compliant
Siebel Application Integration for Oracle Fusion Middleware Guide Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices.