Siebel EAI

Firewall Considerations when Siebel is behind a firewall

You have AIA deployed on one server, BRM is on the same network. Siebel on the other hand is installed on a server which is behind a firewall.

Which ports on the firewall need to be opened from SOA Suite and Siebel networks in order for the integration to work?

There are 2 considerations when having a firewall between Siebel and the SOA Suite used by AIA:

1- All the AIA ABCs providers which connect from SOA Suite to Siebel invoke a Web Service in Siebel.

reference an EAI Value Map in an integration field map source expression

The requirement is to convert a field value from it’s external representation into it’s internal representation and visa versa by referencing a EAI Value Map in a Data Map.

According to the information included in eAI Volume IV: Business Processes and Rules, Data Mapping Using Scripts, EAI Value Maps, the functions EAIGetValueMap, EAILookupSiebel and EAILookupExternal work on the EAI data map tables.

Increase Error Code Process property text lenght for Siebel Workflow

Here are the steps to Increase Error Code Process property text lenght for Siebel Workflow :

1.    Login to Siebel tools using SADMIN/SADMIN.
2.    Navigate to object definition "Business Component".
3.    Search for the Name "Repository WF Step" which is based on Table "S_WFR_STP".
4.    Now go to Field definition and search for the field "Error Code" which is based on Column "ERROR_CD".

Techniques to display the CTI Call Data in Siebel Application

While integrating Siebel and CTI with products like Avaya or CISCO typically clients will have following types of requirement:

- Create a customer control on the CTI toolbar and populate it with Call Data
- Present Call Data to the agent for the duration of a call
- Inform the agent at the beginning of the ANI or Language of the caller

 

Troubleshooting – Common Workflow Errors

The following lists some commonly encountered errors for Workflow Process Manager.

1. Problem: You activated your workflow but it is not executing

Solution: Verify if <Reload Runtime Events> performed. In order to tell if a process has been triggered, Turn workflow logging (EngInv, DfnLoad, StpExec, PrcExec) on. See the Business Process Administration Guide in Siebel Bookshelf for procedures on how to do this.

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 se

 

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:
- Siebel REST Service - Quick Start Guide [ID 988872.1]

How can we increase the default HTTP Sleep Time on outbound web service calls ?

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 :

Recent content