The NEON adapter for Siebel provides the capability to automate data transfers to and from Siebel 6 (2000) and Siebel 7 Enterprise Applications by leveraging current New Era of Networks (NEON) and Seibel Integration Objects.

The Adapter for Siebel Integration Service is commonly used for real-time interaction with Siebel. Siebel provides an object interface that exposes Siebel Object data and functionality to the Adapter for Siebel. The Siebel object interface is composed of Siebel business service methods that expose data and functionality to external programs, providing access to Siebel interface object, events, and associated data. The Adapter for Siebel uses the Siebel COM data server to access the exposed object interfaces. Note: The Deliver Adapter uses the COM data server and not the Siebel Object Manager.

The NEON Adapter for Siebel Integration Service does not need to be installed on the Siebel server, but must be installed on a machine on which the Siebel Client is installed, as the Siebel Client provides the COM interfaces
used by the Integration Service to interact with Siebel.

The NEON Adapter for Siebel is configured and controlled through the MMC (Microsoft Management Console), a user friendly interface, or through the command line. The adapter employs one design-time mode: Schema, and three
runtime modes: Deliver, Process and Acquire. The Process mode is not covered in this document. These modes are used to accomplish the following tasks

• Extract metadata from Siebel (Schema mode)
• Deliver data to Siebel (Deliver mode)
• Capture data from Siebel (Acquire mode)

Siebel provides object interface to access Siebel Objects like Business Component, Business Object, Business services, Fields etc to be accessed from .Net, you can integrate Siebel and .Net using below steps.

Add the reference for the Siebel Data Object:

Add the “Siebel Business Object Interfaces Type Library” as reference which is available under COM tab in the add reference dialog box

Create one instance for SiebelBusObjectInterfaces:

public SiebelBusObjectInterfaces.SiebelDataControlClass SiebApp;

Login to Siebel Environment:

Mention the corresponding values for SiebelHost, EnterpriseServer and ObjectManager

string SiebLogin=”xxx”;
string SiebPassword=”xxx”;
string ConnectString = "host=\"siebel://" +
SiebelHost.ToString() + "/" +
EnterpriseServer.ToString() + "/" +
ObjectManager.ToString() + "/\"";
Boolean Ret = SiebApp.Login(ConnectString, SiebLogin.ToString(),SiebPassword.ToString());

If the value is true then the login is successful

Handling Siebel Objects from .Net :

Accessign Siebel object in .net is almost similar to Siebel script

Eg

following example shows how to access Busines object, Business service etc.:

SiebelBusObjectInterfaces.SiebelBusObject SiebBO;
SiebelBusObjectInterfaces.SiebelBusComp siebActionBC;
SiebelBusObjectInterfaces.SiebelService SiebSvc;
SiebelBusObjectInterfaces.SiebelPropertySet SiebInput;
SiebelBusObjectInterfaces.SiebelPropertySet SiebOutput;
SiebelBusObjectInterfaces.SiebelPropertySet SiebChild;
//ROWID IS THE ONLY INPUT FOR THE BELOW PROCESS-- strRowId
try
{
//Getting Siebel BO
SiebBO = SiebApp.GetBusObject("Action");
if (Convert.ToInt32(SiebApp.GetLastErrCode().ToString()) != 0)
{
//Process :error handling
}
//Getting the AIC Action BC
siebActionBC = SiebBO.GetBusComp("Action");
if (Convert.ToInt32(SiebApp.GetLastErrCode().ToString()) != 0)
{                   
//Process :error handling

}
//Getting the 'Server Request' Business Service
SiebSvc = SiebApp.GetService("Server Requests");
if (Convert.ToInt32(SiebApp.GetLastErrCode().ToString()) != 0)
{
//Process :error handling

}
//PropertySet for Workflow
SiebInput = SiebApp.NewPropertySet();
SiebOutput = SiebApp.NewPropertySet();
SiebChild = SiebApp.NewPropertySet();

//Executing Query----Search Spec
siebActionBC.ClearToQuery();
siebActionBC.ActivateField("Activity SR Id");                                                                   

            siebActionBC.SetViewMode(3);
siebActionBC.SetSearchExpr("[Id]='" + strRowId + "'");
siebActionBC.ExecuteQuery(1);
blnRecords = siebActionBC.FirstRecord();
if (blnRecords)
{
lngNumRecords = lngNumRecords + 1;

//WorkFlow Process Name
Process_Name = "Activity Asynchronous Process";

      //Getting the required field values in variables

strWorkItemID = siebActionBC.GetFieldValue("Activity SR Id");
//SiebChild Property set

SiebChild.SetProperty("RowId", strRowId);
SiebChild.SetProperty("ProcessName", Process_Name);
SiebChild.SetProperty("SearchSpec", "[Id]='" + strRowId + "'");
SiebChild.SetProperty("WorkParentId", strWorkItemID);

//Fetching SiebChild to SiebInput
SiebInput.SetProperty("Component", "WfProcBatchMgr");
SiebInput.SetProperty("Mode", "DirectDb");
SiebInput.AddChild(SiebChild);
if (Convert.ToInt32(SiebApp.GetLastErrCode().ToString()) != 0)
{
//Process :error handling
}
//Invoking WorkFlow
SiebSvc.InvokeMethod("SubmitRequest", SiebInput, SiebOutput);
if (Convert.ToInt32(SiebApp.GetLastErrCode().ToString()) != 0)
{
//Process :error handling
}
else
{
Console.WriteLine("\r\nSuccessful save for SR " + strRowId + "\r\n");
}
}
}

In Siebel Workflow, there is no function for a carriage return line feed. So, if we want to populate a text field and format the contents so that they appear on separate lines, there is no simple way to do it.
One solution would be to write some eScript in a Business Service to return the CRLF escape sequences to the calling routine. The workflow can then call your business service to populate a process property with the CRLF characters and it can then use that process property as and when required.
Another solution exists which does not involve escript is to use siebel vanilla Business Service. There exists a “vanilla” Business Service which returns CRLF as a return argument.
 
Business Service details:
Business Service Name: SSSE Address Parser (eScript)
Business Service Method: GetCRLF  
 
Note : Newline characters can be added in oracle database level using the following ASCI functions CHR(10) – Line Feed and CHR(13) – Carriage Return

The whole sub tree rooted at this node is not processed. It is the same as that whole sub tree not existing in the integration object instance. Operations specified in child nodes do not affect processing in any way since the EAI Siebel Adapter does not act on the child.

<?xml version="1.0" encoding="UTF-8"?>

Based on this example, the account is skipped. However, the EAI Siebel Adapter will attempt to insert the two contacts. 

There are a lot of instances while working on Siebel integration we use “PRM ANI Utility Service” BS with “GetProperty” method.
The issue with this is when you don’t get a proper hierarchy as expected from the previous step; your Get Property method throws an error message.
 
Usage:
When we have a hierarchy structure and want to extract a property value from that without script.
 
Required Properties:
Input Arguments:
Hierarchy Path - the hierarchical path to reach the desired property (for e.g.: SiebelMessage.Service Request)
Property Name - the Name of the property (for e.g.: SR Number)
SiebelMessage - Hierarchical structure from where we are going to extract the property value
 
Output Arguments:
Property Value - The Value of the property.
 
Issue:
When we are not getting the hierarchy in the desired format, which means the hierarchy path is not retrieved correctly as specified in the Hierarchy Path input argument.
It throws an error stating  “Error Running Method 'Execute'.(SBL-PRM-00104)”
 
Resolution:
In the “PRM ANI Utility Service” BS we can give an optional input argument that will suppress this BS from throwing error and return null when it cannot find the required property.
 
So in the WF Step -> Input Arguments, create a new input argument though it will not be available in the picklist. 
ReturnBlankIfNull      Literal              Y
 
Or if used from script Set the value of this Input Argument property (ReturnBlankIfNull) to “Y”.