Comprehensive Siebel Connectivity

The Oracle JCA Adapter for Siebel provides connectivity to Siebel. It uses the Siebel COM and Java Data Bean API to synchronously invoke Siebel transactions - Siebel Business Objects and Business Services.

Simple and Easy to use Design Time Graphical Interface

The design-time tool of Oracle JCA Adapter for Siebel enables dynamic browsing of the various Siebel Business Objects, Business Services and Integration Objects by interfacing with the Siebel Business Layer without any coding effort. The design-time tool exposes the Adapter Services as a Web Service in few simple clicks and enables rapid implementation. Since this introspection is dynamic, all custom written or extended Siebel interfaces and objects are available for use.

Standards Support

The Oracle JCA Adapter for Siebel is based on open standards and exposes the underlying Siebel functionality as JCA and Web Services. The Oracle Fusion Middleware product components are seamlessly and rapidly integrated with the Siebel system through these standard interfaces.

Complete Management through the Oracle Application Server

The Oracle JCA Adapter for Siebel is deployed on top of Oracle Application Server and leverages it for scalability and high availability. The Oracle Application Server enables the user to monitor and manage the adapter Life-cycle.

Siebel Exceptions Handling

Oracle JCA Adapter for Siebel exceptions are either Retry-able exceptions or non-Retry-able exceptions. Remote exceptions (or remote exception) are usually retry-able exceptions. The Oracle JCA Adapter for Siebel throws these types of exceptions based on the error from an outbound invocation to the Siebel system. The JCA framework catches the remote exception and initiate a retry action. Business exceptions (or binding exceptions) are non-retry-able exceptions. The message enters a recovery queue and the calling service engine performs the recovery work.

Design-time Features

Runtime Interaction Features

You must deploy the application profile for the SOA project and the application you created in the preceding steps. To deploy the application profile using JDeveloper, perform the following steps:

Business Component XSD

XSD is generated for Business Component methods. For example, here is the request/response schema for the Account Business Component.

The following is an example of Request Schema for Business Component.

<xsd:schema xmlns:xsd=http://www.w3.org/2001/XMLSchema …>
<xsd:element name="SiebelRequest">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="insert" type="ns1:record" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="record">
<xsd:sequence>
<xsd:element name="_nb52_0x20_Week_0x20_High" type="xsd:string"
minOccurs="0" />
<xsd:element name="_nb52_0x20_Week_0x20_Low" type="xsd:string"
minOccurs="0" />
<xsd:element name="ADL_0x20_Status" type="xsd:string"
minOccurs="0" />
<xsd:element name="ATM_0x20_Flag" type="xsd:string"
minOccurs="0" />
<xsd:element name="Access_0x20_Level" type="xsd:string"
minOccurs="0" />
<xsd:element name="Account_0x20_Competitors" type="xsd:string"
minOccurs="0" />
<xsd:element name="Account_0x20_Condition" type="xsd:string"
minOccurs="0" />
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

The following is an example of Response Schema for Business Component.

<xsd:schema …>
<xsd:element name="SiebelResponse">
<xsd:complexType>
<xsd:attribute name="ROW_ID" type="xsd:string" use="required" />
</xsd:complexType>
</xsd:element>
</xsd:schema>

WSDL

WSDL is generated on the Business Component methods. The WSDL operation name is the action name. For example, the following WSDL is generated for insert method of the Account/Account.

The following is an example of Insert Method Siebel Adapter WSDL Artifact

<definitions …>
<types>
<!—import the request and response schema 
</types>
<message name="response">
<part element=”ns1:SiebelResponse" name="output_insert"/>
</message>
<message name="request">
<part element=" ns1:Siebel" name="input_insert"/>
</message>
<portType name="insertPortType">
<operation name="insert">
<input message="ns2:request" name="Input_insert"/>
<output message="ns2:response" name="Output_insert"/>
</operation>
</portType>
<plt:partnerLinkType name="insertPartnerLinkType">
<plt:role name="insertRole">
<plt:portType name="ns2:insertPortType"/>
</plt:role>
</plt:partnerLinkType>
</definitions>

JCA

JCA properties are generated for the Siebel integration endpoint. It includes the connection-factory, endpoint-interaction, interaction-spec, property for interaction-spec and so on.

The following is an example of JCA property File

<connection-factory location="eis/MySiebel"/>
<endpoint-interaction portType="Internal_0x20_Contact_0x20_Interface_PT">
<interaction-spec className="oracle.tip.adapter.siebel.SeblBCInteractionSpecImpl">
<property name="BusinessObjectName" value="Contact"/>
<property name="BusinessComponentName" value="Account"/>
<property name="Action" value="insert"/>
<property name="ExecutionTimeout" value="50000000"/>
</interaction-spec>
</endpoint-interaction>

Business Service XSD

The request schema represents the input parameters of a Business Service method. For example, the following request schema represents the CreateAccount method of the Account Business Service.

The following is an example of Request Schema Business Service XSD for CreateAccount Method.

<xsd:schema …>
<xsd:element name="AdapterParams">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Account_0x20_IO" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>

The response schema represents the output parameters of a Business Service. However, the response schema does not include the error message and success flag. The error message is wrapped in an exception.

The following is an example of Request Schema Business Service XSD for CreateAccount Method.

<xsd:schema …>
<xsd:element name="Response">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Account_0x20_Id" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>

Business Service WSDL

WSDL is generated for the Business Service method. The WSDL operation name is the method name. The following example shows the Business Service WSDL of the CreateAccount Method.

The following is an example of Business Service CreateAccount Method WSDL.

<definitions …>
<types>
<!—import the request and response schema 
</types>
<message name="request">
<part element="ns1:AdapterParams" name="input_CreateAccount"/>
</message>
<message name="response">
<part element="ns1:Response" name="output_CreateAccount"/>
</message>
<portType name="CreateAccountPortType">
<operation name="CreateAccount">
<input message="ns2:request" name="Input_CreateAccount"/>
<output message="ns2:response" name="Output_CreateAccount"/>
</operation>
</portType>
<plt:partnerLinkType name="CreateAccountPartnerLinkType">
<plt:role name="CreateAccountRole">
<plt:portType name="ns2:CreateAccountPortType"/>
</plt:role>
</plt:partnerLinkType>
</definitions>

JCA Property for Business Service

JCA properties are generated for the Siebel integration endpoint. It must include the connection-factory, endpoint-interaction, interaction-spec, property for interaction-spec, and so on. The adapter generates the JCA property file for the Business Service. An example file follows.

The following is an example of JCA File for Business Service CreateAccount Method.

<connection-factory location="eis/MySiebel"/>
<endpoint-interaction portType="Account_0x20_PT">
<interaction-spec className="oracle.tip.adapter.siebel.SeblBSInteractionSpecImpl">
<property name="BusinessServiceName" value="Account"/>
<property name="MethodName" value="CreateAccount"/>
<property name="ExecutionTimeout" value="50000000"/>
</interaction-spec>
</endpoint-interaction>