Applies to:
Siebel System Software - Version: 7.7.2.2 [18356] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.7.2.2 [18356]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Sun Solaris 9
This document was previously published as Siebel SR 38-3003544447.
""""Checked for relevance on 01-Jun-2010""""
Symptoms
A new web service was built and tested using Siebel web client (thick client). Directions in Note 473838.1: 'How To Test Siebel Inbound Web Services Using a Siebel Client' were used in order to test the new Inbound Web Service in a thick client. Testing the web service results in the following error:
"Error while processing argument SiebelMessage for operation TIBCOTrnAdmCrseQueryById(SBL-EAI-04316)".
However, the same web service for records not including attachments works fine.
Cause
After further research, it was found that the issue was being produced with the attachment data. The web service was able to get the attachment data correctly from Siebel, but when it was creating the SOAP message it erred out.
The CR 10508563 was created to address this issue on Siebel 7.7.x, since this issue does not affect Siebel 7.8.x. The issue was solved in Siebel version 7.7.2.9 QF0903 and 7.7.2.10.
Solution
Consider to validate the following workaround for the behavior, besides of the validation for the QF available for Siebel version.
It was suggested to the customer to use the MIME messages over HTTP to exchange attachments as described in the Bookshelf > Integration Platform Technologies: Siebel Enterprise Application Integration > Siebel EAI and File Attachments > Using MIME Messages to Exchange Attachments.
On the other hand, Note 477604.1: 'Invoking a Workflow using the HTTP Inbound Transport in Siebel version 7.5' explains how to call an inbound workflow using named subsystems.
Note that the web services approach to get attachments will send the attachment data in a Base64 string and the external application will need to be able to convert the Base64 string to its original value. In a similar manner, the external application on the MIME approach will need to understand MIME messages to be able to handle the attachments.
Related
Applies to:
Siebel CRM - Version: 7.8 [19038] to 8.0.0.4 SIA [20417] - Release: V7 to V8
Information in this document applies to any platform.
***Checked for relevance on 18-Nov-2010***
Goal
Does Siebel support MTOM attachments in web services ?
Solution
SOA, WS-Attachments, XOP/MTOM are all standards that exist for handling attachments but Siebel currently does not support any of them.
In those standards the attachment is sent as binary data in a MIME message.
The only supported attachment standard is: Inline base64 encoded data in the xml payload.
and only at 7.7.2.10 Fix pack or higher due to Change Request 12-1E3CBSB seen in Getting SBL-EAI-04316 with Web Service including Attachment (Doc ID 488868.1)
See also : "Web Services attachments as Inline base64 encoded data in the xml payload (Doc ID 757377.1)"
References
NOTE:579815.1 - How to send attachments in real time from Siebel to an external system using Siebel EAI?
NOTE:757377.1 - Web Services attachments as Inline base64 encoded data in the xml payload
NOTE:488868.1 - Getting SBL-EAI-04316 with Web Service including Attachment
NOTE:1076251.1 - Master Note for Siebel Web Services
Related
Applies to:
Siebel System Software - Version: 7.8.2.4 [19224] and later [Release: V7 and later ]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Professional)
Version: 7.8.2.4 [19224]
Database: Oracle 10.2.0.2
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 9
This document was previously published as Siebel SR 38-3285135471.
***Checked for relevance on 28-DEC-2010***
Symptoms
Customer is calling an outbound web service and receiving the following error when the response message arrived :-
ObjMgrLog Error 1 0 2007-02-22 15:26:59 (app.cpp (2010)) SBL-EXL-00151: Error invoking service 'TC SFA Merge Common Service', method 'Execute' at step 'Parse & Post XML to BO'.(SBL-BPR-00162)
--
Error while processing argument http://www.siebel.com/xml/TC%20Contact%20Interface:SiebelMessage for operation execute(SBL-EAI-04316)
--
Required message header property 'IntObjectName' is missing or invalid(SBL-EAI-04019)
Cause
It was found that the error was being raised because one of the SOAP XML tags was called "SiebelMessage". Due to this fact the Siebel XML converters was trying to find the "IntObjectName" property.
This was not correct since the SOAP message should not be treated as a Siebel message but as a simple XML document.
Solution
The Change Request 12-1II4GH4 was raised to address this issue.
The workaround is to change the name of the argument to a name different from SiebelMessage.
References
BUG:10520274 - WEB SERVICE TREATING A SIEBELMESSAGE TAG AS EAI SIEBEL MESSAGE
Related
Applies to:
Siebel System Software - Version: 8.0 [20405] and later [Release: V8 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V8 (Enterprise)
Version: 8.0 [20405] FRA Pub Sect
Database: Microsoft SQL Server 2005
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server
This document was previously published as Siebel SR 38-3474521161.
***Checked for relevance on 22-NOV-2010***
Symptoms
Have a Siebel Web Service that has a file (buffer) as an input parameter.
Push a file bigger thant 10 Kilobyte and get the following error :
Erreur lors du traitement de l'argument http://www.siebel.com/xml/RBQ%20Form%20Instance%20Attachment:ListOfRBQFormInstanceNumerisation de l'op�ration IncrireDocument(SBL-EAI-04316)
in english
SBL-EAI-50187 The file 'D:\sba80\siebsrvr\temp\1-IG49_0.tmp'does not exist.
Cause
WS-Security is used to pass security credentials in the SOAP header. When a SOAP / inline XML message reaches Siebel the SOAP header is parsed and temporary attachment files are created.
After the authenticate event the EAI OM runs the ReLogin event to disconnect the anon user and connect the SOAP header user. During this event the EAI OM deletes the temporary files.
When the XML Converter is invoked to convert the XML message and attachment temp file into property set the message error SBL-EAI-50187 is experienced, crashing the EAI OM component.
The Change Request# 10531649 was created to address this issue on future releases.
Solution
Since customer was not allowed to pass security credentials in the URL it was suggested to use the Session Management instead of WS-Security.
Reference Bookshelf 8.0 > Integration Platform Technologies: Siebel Enterprise Application Integration > Web Services > About Siebel Authentication and Session Management SOAP Headers
This issue has been fixed in 8.0.0.6 Fix Pack and 8.1.1.1 Fix Pack
References
NOTE:745864.1 - EAI File Streaming is NOT supported before 8.0.0.6 Fix Pack or 8.1.1.1 Fix Pack
Related
Applies to:
Siebel CRM - Version: 8.0.0.2 [20412] to 8.0.0.5 [20420] - Release: V8 to V8
Information in this document applies to any platform.
***Checked for relevance on 22-NOV-2010***
Description
EAI File Streaming is NOT supported on Siebel before 8.0.0.6 Fix Pack or 8.1.1.1 Fix Pack
There are known issues in using the new "EAI File Streaming" that causes failure in specific cases.
One example is BUG :12-1LTG2F6 described in "Problem with file attachment size with EAI object manager (Doc ID 496506.1)"
Please do not use it prior to 8.0.0.6 Fix Pack or 8.1.1.1 Fix Pack
Likelihood of Occurrence
May happen if "LargeFileChunkingEnabled" is explicitly set to TRUE in the [Application] section of eapps.cfg and a large dataset is returned from an inbound web service call.
Possible Symptoms
EAIFileAttachments EAIFileAttachmentDebug 5 00000af848f814f2:0 2008-10-18 11:35:28 Getting file reference manager Session Global by key 'FileReferenceManager'
EAIFileAttachments EAIFileAttachmentDetail 4 00000af848f814f2:0 2008-10-18 11:35:28 New large file reference is created - '/sbsiebcrmtest/siebsrvr/temp/1-DN5R_0.tmp'
EAIFileAttachments EAIFileAttachmentDebug 5 00000af848f814f2:0 2008-10-18 11:35:28 New large file reference is registered - '/sbsiebcrmtest/siebsrvr/temp/1-DN5R_0.tmp'
ObjMgrLog Error 1 00000af848f814f2:0 2008-10-18 11:35:28 (filerefutil.cpp (249)) SBL-GEN-10103: Error opening specified file
ObjMgrLog Error 1 00000af848f814f2:0 2008-10-18 11:35:28 (filerefutil.cpp (249)) SBL-EAI-50176: Error writing to file reference
and
Erreur lors du traitement de l'argument http://www.siebel.com/xml/RBQ%20Form%20Instance%20Attachment:ListOfRBQFormInstanceNumerisation de l'op�ration IncrireDocument(SBL-EAI-04316)
SBL-EAI-50187 The file 'D:\sba80\siebsrvr\temp\1-IG49_0.tmp'does not exist
Workaround or Resolution
Please ensure "LargeFileChunkingEnabled" is explicitly set to FALSE in the [Application] section of eapps.cfg. and restart the web server.
Or please apply 8.0.0.6 Fix Pack or higher or 8.1.1.1 Fix Pack or higher.
Related
Applies to:
Siebel System Software - Version: 7.5.3 [16157] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3 [16157]
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2000 Server SP 2
Database Server OS: Microsoft Windows 2000 Server SP 2
This document was previously published as Siebel SR 38-1123400181.
***Checked for relevance on 25-FEB-2011***
Symptoms
An outbound web service is being invoked from Siebel. A custom Business Service is used to build the input for the proxy Business Service, but the call to the proxy results in :-
[1] Error while processing argument createContact:myContact for operation createContact (SBL-EAI-04316)
[2] Integration Object Message error -- object list property set has wrong type: 'MyContact' (expecting 'ListOfMyContact') (SBL-EAI-04007)
Cause
The structure of the propertyset input to the proxy web service was not as expected (in particular, a 'ListOfMyContact' container element was missing).
Solution
The resolution was to modify the custom business service to add the element 'ListOfMyContact' (in a SetType statement) to the integration object.
For further information on creating integration object instances for invoking outbound web services, see :-
Integration Platform Technologies: Siebel Enterprise Application Integration > Web Services > Examples of Invoking Web Services
Also, see :-
Document 556846.1 - How To Create Integration Object Instances Programmatically
References
NOTE:556846.1 - How To Create Integration Object Instances Programmatically
Related
No comments:
Post a Comment