WCF Siebel Adapter – Query fails because of misconfigured fields

  Siebel adapter uses the COM interface to invoke calls on Siebel. For business component query, Siebel supports two ways of retrieving the field values for records. One can either use GetFieldValue to retrieve one field at a time or the other option is to use GetMultipleFieldValues to retrieve values for a bunch of fields…

0

Connection failure when using the WCF Siebel Adapter

I have seen quite a few instances where people run into issues while using the WCF Siebel adapter because of   a.       Siebel Web Client is not installed correctly on the machine b.      Or the URI passed to the adapter, that eventually gets transformed to the connection string passed to Siebel, is incorrect   In…

2

Performing MVG operations using the Siebel Adapter

The RTM version of Siebel Adapter no longer supports the MVG operations – Associate, Dissociate and Query_*. The reason for dropping support for these operations is a memory leak in Siebel library that the adapter uses to communicate with Siebel. We are actively following up with Siebel to get this issue (SR# – 38-3489322221) resolved….

0

Upload data from an Excel spreadsheet to Siebel using the Siebel Adapter

If you have data stored in a Excel file and need to upload that to Siebel, this blog illustrates how go about doing that using the Siebel adapter. I will be using the “Account” business component and will show how to create insertion records.    Let’s take a sample Excel spreadsheet that has a bunch…

2

Using WCF Adapters with SQL Server Integration Services(SSIS)

There are two ways the adapters belonging to Adapter Pack can be used by SQL Service Integration Services: 1. Using ADO layer built on top of base adapters. This option is available with SAP and Siebel adapters. 2. Writing custom SSIS task which directly invokes adapter to communicate with LOB system. Option 1 covers all…


Siebel adapter connection URI

Siebel adapter exposes siebel connection string as URI. Siebel URI syntax is given below: siebel://SiebelGateway[:portno]/?SiebelEnterpriseServer=SiebelEnterpriseServerName&SiebelObjectManager=ObjectManagerToConnect&Language=SiebelLanguageCode&SiebelRepository=CurrentActiveRepository&SiebelServer=servername various components of URI are: SiebelGateway: This variable point to siebel gateway hostname or ip address in case only one siebel server is configured for the gateway. If a gateway manages more than one siebel server, then individual server address must…


WCF Siebel adapter Vs Biztalk Siebel adapter

What are the differences between old Siebel adapter shipped with Biztalk releases and WCF based Siebel adapter? Here is the list: Since new Siebel adapter is developed using WCF LOB Adapter SDK (ASDK), ASDK features like Browse, Search and Resolve are available to end users via metadata search browse tool. While old adapter supports only…


Upcoming Siebel Adapter CTP release

The upcoming release for Adapter pack will have support for Siebel integration objects. This feature will allow users to invoke Siebel Business Service “EAI Siebel Adapter” to operate against any Siebel integration object. EAI Siebel Adapter business service exposes following operations for manipulation of siebel integration objects: 1.Query 2. Insert 3. Update 4. Upsert 5….


Working with Siebel multi valued link (MVL) using siebel adapter

Siebel adapter supports working with multi valued link in Siebel. Following operations are exposed for MVLs: 1. Associate 2. Dissociate 3. Query_xxx A sample is attached for associating Contact record with Account business component. Sample starts with: 1. creating record in parent business component which is Account 2. Querying the inserted record in Account. 3. Inserting record…


Connection management in Siebel adapter

iebel adapter uses Siebel COM control to connect to Siebel backend. Since Siebel COM control objects work only in STA mode, Siebel adapter creates dedicated thread for each connection being opened to server. Sometimes this thread hangs around if Siebel adapter is configured to use ASDK’s connection pool and client didn’t explicitly call ChannelFactory.Close(). By default…