Version: 126.96.36.199  Auto
Database: Oracle 188.8.131.52
Application Server OS: Sun Solaris 8
Database Server OS: Sun Solaris 8
This document was previously published as Siebel SR 38-1771908401.
We are trying to configure EAI Dispatch for inbound (both mime and non-mime data). For this we configured two named sub-systems. One for MIME and other for non-MIME messages. Non-MIME messages are working fine but we are facing problem with the MIME messages.
For inbound mime data we set up a named subsystem as follows:
CharSetConversion = None
ConverterService = EAI MIME Doc Converter
DispatchRuleSet = GMNA LM Inbound Requests
IgnoreCharSetConvErrors = False
RollbackOnDispatchError = True
SiebelTransactions = True
While sending a mime XML to the Siebel Server via HTTP we are observing a loss of data. For the Mime XML that we used, there was a data loss of about 100 odd bytes. Due to this the message received by Siebel is in distorted and it does not work. The error we get is "(SBL-EAI-04152) Child property set of service method arguments should have type 'MIMEHierarchy"
We are attaching herewith the Object Manager log file and a zip file containing "InboundMIME.xml" (binary attachment) and "InboundMIME2.xml" (html attachment).
Thanks & regards,
SolutionMessage 1[1 / 2]
For the benefits of other readers,
Customer was trying to configure EAI Dispatch Service business service for inbound (both MIME and non-MIME data). For this they configured two named sub-systems: one for MIME and the other for non-MIME messages. Non-MIME messages were working fine but the following error was caused with the MIME messages while processing the messages:
"(SBL-EAI-04152) Child property set of service method arguments should have type 'MIMEHierarchy"
The reported error message could be caused when no property set is passed to the EAI MIME Hierarchy Converter business service or the type of property is not MIMEHierarchy even if a property set is passed to the business service.
Thus, EAI object manager log file generated while processing the MIME message was reviewed to see if MIMEHierarchy property set was passed properly and found the following log:
StpExec Task 4 2005-02-04 01:09:28 Invoking method 'MimePropSetToSiebelMessage' on business service 'EAI MimePropSet Converter'.
StpExec TaskArg 4 2005-02-04 01:09:28 Input: @0*1*0*0*0*0*
ObjMgrBusServiceLog InvokeMethod 4 2005-02-04 01:09:28 Begin: Business Service 'EAI MimePropSet Converter' invoke method: 'MimePropSetToSiebelMessage' 4f6c678
Message 2[2 / 2]
It showed that no input data was passed to EAI MIME Hierarchy Converter in the workflow process, which meant no MIMEHierarchy property set was passed to the business service. It was caused by the EAI dispatch rule set used in the integration scenario. Especially, the transform definition was wrong in the dispatch rule so that no property set was passed to the workflow process and business service.
In order to pass the MIMEHierarchy property to the workflow process and business service, the target â€˜RootHierarchyâ€™ should be set to â€˜/*â€™ in transform definition in the dispatch rule. With this change, MIMEHierarchy property set could be passed to the workflow process and business service and the reported error could be resolved.
Siebel Technical Support