Table 4. New Product Features in Integration Platform Technologies: Siebel Enterprise Application Integration, Version 8.1
|
|
About the Structure of Integration Objects |
Modified topic. It is a best practice to create a separate project for your integration objects. |
Custom Integration Component Fields |
New topic. Custom attributes can be passed as part of the integration object schema by using custom integration component fields. |
About Integration Component Keys |
Modified topic. Removed the Foreign Key and Target Key integration component key types, which are not used in Siebel version 8.1. |
Creating Integration Objects Using the EAI Siebel Wizard Business Service |
New functionality added:
- Deploying integration objects to the Siebel database (optional)
- Choosing a naming convention for XSD container elements
- Choosing a naming convention for XML tags
|
Creating Integration Object Instances Programmatically |
New topic. Integration object instances can be created using scripting. |
Testing Integration Objects |
Modified topic. The Import Account (File) and Export Account (File) sample workflows no longer exist in Siebel Tools. Replaced them with a new example. |
Deploying Integration Objects to the Run-Time Database |
New topic. Integration objects can be deployed from Siebel Tools into the Siebel run-time database and modified in the run-time environment. |
Generating Integration Object Schemas |
Modified topic. The Generate XML Schema wizard can generate simple types for all string elements in the integration object schema. |
Property Sets |
Modified topic. It is recommended that business services treat their input property sets as constants. |
Deploying Business Services as Web Services |
New topic. Business services can be deployed from Siebel Tools as Web services. The Web services can then be consumed by other applications. |
Importing Business Services into Siebel Business Applications |
New topic. Business services can be imported into the Siebel run-time database as XML files and modified in the run-time environment. |
Supported Web Services Standards |
Modified topic. Added Web Services Security (WS-Security) and Extensible Stylesheet Language Transformation (XSLT) to the list. |
Invoking Siebel Web Services Using an External System |
Modified topic. In version 8.1, you can deploy business services and workflow processes as Web services and generate WSDL files directly from Siebel Tools. |
Publishing Inbound Web Services |
Modified topic. With the EAI MQSeries, EAI MSMQ, and EAI JMS transports, the request and response must be in the same queue. |
Generating a WSDL File |
Modified topic. Added Oracle JDeveloper to the list of applications that you can use to import the Web Services Description Language (WSDL) file into the external application. |
About the Relationship of Port Types and Operations |
New topic. When deleting an operation it is necessary to delete the associated port type. |
About Defining the Web Service Inbound Dispatcher |
Modified topic. The Web Service Inbound Dispatcher business service converts incoming XML data to an XML hierarchy before mapping it to business service method arguments. |
Creating an Outbound Web Service Based on a WSDL File |
New functionality added:
- Deploying integration objects to the Siebel run-time database
- Deploying proxy business services to the Siebel run-time database
- Creating and reusing SOAP fault integration objects
Deployment and fault schema processing are optional. |
Integration Objects as Input Arguments to Outbound Web Services |
Modified topic. Added a Siebel eScript example to demonstrate passing an integration object to a proxy business service. |
Web Services Support for Transport Parameters |
New topic. The outbound Web service dispatcher supports input arguments for transport parameters defined in proxy business services. |
Configuring the Siebel Application to Use the WS-Security Specification |
Modified topic. Removed the procedure for creating the SecureWebService profile (named subsystem), because this profile already exists in version 8.0 and higher. Corrected the Uniform Resource Identifier (URI) for eai_anon_enu. |
About Siebel Authentication and Session Management SOAP Headers |
Modified topic. Added ServerDetermine to the table of valid session types. Added a note not to use Siebel Session Management and Authentication SOAP headers with WS-Security SOAP headers. |
About Web Services and Web Single Sign-On Authentication |
Modified topic. When using Web single sign-on (SSO), the trust token, instead of the password, is sent in the URL or the SOAP header. |
About SOAP Fault Schema Support |
New topic. In version 8.1, SOAP faults in WSDL files can be modeled as integration objects. |
About EAI File Streaming |
New topic. In version 8.1, streaming of EAI requests and responses is supported. |
About the Cardinality of the Root Integration Components |
Removed topic. |
About the EAI Siebel Adapter Business Service |
Modified topic. When called locally, the EAI Siebel Adapter business service creates an additional database connection. To prevent transaction errors from occurring when this second connection times out, use the TrxDbConnReconnectIntervalSeconds parameter. |
Update Method |
Modified topic. If more than one record is returned during an update operation, the EAI Siebel Adapter will throw an error. |
EAI Siebel Adapter Business Service Method Arguments |
Modified topic. Added the ExecutionMode business service method argument for the Query and QueryPage methods. Setting ExecutionMode to ForwardOnly can be useful for integrations with large record sets. |
Search Specification |
Modified topic. Added the following to the list of supported operators for the searchspec attribute of the QueryPage method of the EAI UI Data Adapter business service:
- Parentheses, including nested parentheses
- EXISTS, NOT EXISTS
- IS NULL, IS NOT NULL
|
Execute Method |
Modified topic. Added a caution that if an operation is not specified for the Execute method, an implicit Synchronize operation will be performed, deleting all unmatched child integration component instances. |
EAI UI Data Adapter Business Service Method Arguments |
Modified topic. Added the ExecutionMode business service method argument for the QueryPage method. Setting ExecutionMode to ForwardOnly can be useful for integrations with large record sets. |
Exposing Siebel Data to External Applications |
New topic. The Data Access Service wizard can be used to make Siebel data available to external applications as Web services. |
Using VBCs for Your Business Requirements |
Modified topic. You can drill down from a virtual business component (VBC) to a standard business component, another VBC, or the same VBC. |
Creating an Attachment Integration Object |
Modified topic. When creating an attachment integration object, keep only certain integration component fields active. Make sure that the attachment integration component is last in sequence. |
Using Inline XML to Exchange Attachments |
New topic. You can exchange an entire business object, including any attachments, as a single XML file. Attachments are included within the body of the inline XML attachment. |
About Data Type Mappings for Importing Table Definitions |
Modified topic. The Character Large Object (CLOB) data type is supported in version 8.0 and higher. |
Usage and Restrictions for External Business Components |
Modified topic. External business components with non-English data require the Siebel S_APP_VER and S_SYS_PREF tables in the external database. |
Predefined EAI Business Services |
Modified topic. Added EAI XSLT Service to Table 53. |