ITCanopy

Below error was received when invoking Siebel IP15 Web Service through php client (Web Application). In Soap request Session Type was set to None.     Error Code: 10944642 Error Message: Error: Inbound SOAP Message - Session Token is missing or invalid or has expired. Siebel will only ask for Session Token when calling web service with Session Type Stateless. On investigation it was clear that we need to add below parameters to eai.cfg file to run web service with Session Type None. AllowAnonymous = TRUE Impersonate = False Search for AllowAnonUsers in cfg and paste above parameters under it. CFG can be found on path: C:\Siebel\15.0.0.0.0\ses\siebsrvr\BIN\enu Save the cfg file and restart the Siebel services and test. Soap Header:    <soapenv:Header>       <UsernameToken xmlns="http://siebel.com/webservices">username</UsernameToken>       <PasswordText xmlns="http://siebel.com/webservices">pass...

Inbound Web Services: The Inbound Web Service allows an external system to call a Siebel published Web Service. You can publish a business service or a business process as a Web Service and generate a Web Service Definition Language (WSDL) file that an external system can import. The Inbound Web Services can only be published from Siebel C using SOAP-RPC binding. Source: Oracle Docs What Is The Difference Between Web Services and APIs? An API is an interface that allows you to build on the data and functionality of another application, while a web service is a network-based resource that fulfills a specific task. Yes, there’s overlap between the two: all web services are APIs, but not all APIs are web services. Both web services and APIs are — at their core — very useful and very much used today. However, it’s the web services associated with SOAP and/or Service Oriented Architecture which are falling out of favor. Source: NordicApis Process: Prepare the workflow which will serve as Si...

Open wsdl in SoapUI and undernder "<soapenv:Envelope" add below in request section: <soapenv:Header>       <wsse:Security S:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:S="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">          <wsse:UsernameToken wsu:id="UsernameToken-ORbTEPzNsEMDfzrI9sscVA22" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">             <wsse:Username>usr</wsse:Username>            <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">pas123</wsse:Password>          </wsse:UsernameToken>       </wsse:Security> </soapenv:Header>

Siebel is returning below error, when invoking Outbound Web Service through Workflow. Error Code (SBL-BPR-00162)--IDS_EAI_WS_OD_RESPONSE_EXPECTED Error Message Error invoking service 'Business Service', method 'Method Name' at step 'Workflow Step Name'.(SBL-BPR-00162)--Operation 'Method Name' is expecting a response but no response was received.(SBL-EAI-04311) You should be getting above error while invoking Outbound Web Service through Workflow. Reason: Web Service might be unavailable at the host location. The machine on which Siebel Web Server is installed is not able to access the end point URL. Solution: Check with Vendor. Add entry of End Point URL in Windows Host file or exclude from Firewall and Antivirus.

Why Pagination in Siebel Inbound Web Service? When creating Inbound Web Services in Siebel for external system consumption data might be huge and web service either take time or timeout when invoking. So in this scenario we need to introduce the pagination. When calling the web service external system will request the page size meaning number of rows in one request. Prerequisite: IO must be compiled on SRF (EAI, SIA) and Deployed to run time data base for which you want to execute query in Siebel Workflow. Process: Add new Business Service step in Siebel Workflow, set its properties as below: Business Service Name: EAI Siebel Adapter Business Service Method: QueryPage Set the values of Input Arguments as below: Input Argument: OutputIntObjectName Type: Literal Value: IO Name Input Argument: SearchSpec Type: Expression Value: "[IC Name.Field Name] = '" + [&Process Property Name] + "'" Sample Expression: "[IC Name.Field Name] ...

Why Integration Component: We use IO in Siebel for inbound and outbound integration. But we can use IO for normal use as well. For example you have requirement to move data (rows) from one business component to an other. Looping is the long way you can make IO and do this in one go. Just query, use data map if you need to modify the data or destination business component have different fields name and insert or upsert the data in other business component or in the same if only data modification is required. Upsert method is interesting choice because on defined user keys in IO you can update the data if no key matches siebel will insert new row. Below is the process of using "Upsert" method of "EAI Siebel Adapter" business service using workflow business service step. Procedure: IO must be compiled on SRF (EAI, SIA) and Deployed to run time data base for which you want to upsert (insert/ update) data in Siebel using Workflow and we have to prepare SiebelMessage befo...

What is Data map? Data maps usually use to process data in bulk. Data map is based on Source and Destination integration objects. And then we map the integration components and after that their fields source and destination. Source field can be expression or integration component field coming from the SiebelMessage.   Below is process of invoking data map using business service step in Siebel workflow.   Procedure: Add new Business Service step in Siebel Workflow, set its properties as below: Business Service Name: EAI Data Transformation Engine Business Service Method: Execute Set the values of Input Arguments as below: Input Argument: MapName Type: Literal Value: Data Map Name Input Argument: OutputIntObjectName Type: Literal Value: IO Name Input Argument: SiebelMessage Type: Process Property Property Name:  SiebMessage Note: SiebMessage cloud be repose from Query in IO or from Web Service input and it should be based on above "IO Name" and ...

IO must be compiled on SRF (EAI, SIA) and Deployed to run time data base for which you want to execute query in Siebel Workflow. Add new Business Service step in Siebel Workflow, set its properties as below: Business Service Name:  EAI Siebel Adapter Business Service Method:  Query Set the values of Input Arguments as below: Input Argument: OutputIntObjectName Type: Literal Value: IO Name Input Argument: SearchSpec Type: Expression Value: "[IC Name.Field Name] = '" + [&Process Property Name] + "'" Set the values of Output Arguments as below: Property Name: SiebelMsg  Type: Output Argument Output Argument: SiebelMessage SiebelMsg is a process property with type hierarchical. Below are some SearchSpec expressions: "[IC Name.Field Name] = Today() AND [IC Name.Field Name] = '"+LookupValue("LOV_TYPE","Value")+"'" "[Id]= '"+[&Object Id] +"'...

Please add below security header in SoapUI request after importing Siebel IP19 Inbound Web Service in SoapUI also make the following change in: Administration - Web Services/ Inbound Web Services/ Operation Change Authentication Type to: None <soapenv:Header>       <wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/04/secext">          <wsse:UsernameToken>             <wsse:Username>******</wsse:Username>             <wsse:Password Type="wsse:PasswordText">*****</wsse:Password>          </wsse:UsernameToken>       </wsse:Security>    </soapenv:Header>

<soapenv:Header> <wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/07/secext"> <wsse:UsernameToken xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility"> <wsse:Username>Atif</wsse:Username> <wsse:Password Type="wsse:PasswordText">Atif</wsse:Password> </wsse:UsernameToken> </wsse:Security> </soapenv:Header>