Siebel Application does not support REST web services on Siebel 8.0.x version, inbound .REST inbound web service support is GA in release 8.1.1.4.For more information on REST support please refer to this MOS posting:
EAI HTTP Transport does not read the sleep time parameter from the enterprise or object manager settings.
Instead, it defaults to 120 seconds internally (hardcoded).
The default can be changed if you explicitly pass the value as input to the business service.
There are a few different ways to do this for outbound web services and they depend on the version you are running.
Details can be seen at document :
It is possible to add a searchspec to child integration components but some restrictions apply.
As seen in document "searchspec on integration Component (Doc ID 523483.1)" , you must also search on the parent.
Lets take the example of parent Accounts and child Contacts.
The EAI JMS Transport is provided to allow connection to a JMS queue / topic. This document will outline overall required steps (referencing document as necessary) in order to achieve this.
Steps:
The DEP feature (Data Execution Prevention) must be turned OFF when used with Siebel, as Oracle has not yet included the specialized code required to fully implement this feature. This may be done by unchecking the relevant box on the individual client browsers, or by using the Group Policy tools, or by using the relevant Vista control panel.
Following new IE8 features are not supported in Siebel 8
1.Containers
2.Accessibility
3.Enhanced security (downloads, XSS, DEP - buffer overflow prevention)
4.Tab-level crash recovery.
5.The DEP feature (Data Execution Prevention)
The following configuration changes need to be made on the Siebel Application Server for each Siebel installation, so that it knows the capabilities of the IE8 browser. This configuration step is mandatory for all Siebel versions whenever IE8 is used in any environment, regardless of patch level:
After upgrading Siebel applications to a higher release, certain columns that were previously not List-of-Value (LOV) bounded became LOV bounded that could cause EIM import failure Oracle Siebel highly recommends that users evaluate the potential impact of schema upgrade before they perform any EIM loading in a new release.
In the "Advanced Usage" chapter of the Siebel "Enterprise Integration Manager and Administration Guide", it is recommended that batch sizes of 5,000 records or less be used. Running Enterprise Integration Manager Tasks with batch sizes greater than 5,000 records could result in a stalled Transaction Router or memory leak in Replication Agent server component when merging records into regional node database.
