Forum Replies Created
-
AuthorPosts
-
November 7, 2005 at 11:10 PM in reply to: Problem with BizTalk Mapper merging two messages to one. #12201
You might also want to try putting them all in different assemblies – or at least not putting the map with the orchestration. You should be ok putting schemas and maps together.
Just something else to try.
Is the Oracle Adapter you are trying to use compatible with Oracle 10g?
I know the Microsoft Adapter for Biztalk 2006 (a.k.a. iway adapter) is but there are a lot of other Oracle Adapters out there.
You might be better off contacting the vendor.
I fixed this by adding <?xml version=\”1.0\” encoding=\”utf-8\” ?> to the
beginning of the string.Everything works now.
Unfortunately, all I have in the xsd is:
<xs:element name=\”user\” type=\”tns:user\” />
<xs:complexType name=\”user\” mixed=\”true\” />I would guess you could set this is message context properties.
When you construct the message you are going to send inside the Orchestration, see what WSE properties are available.
It would look like this: youMesage(Something) = “your value”
I would guess WSE would have there own set of properties you can set, probably starts with WSE.
Hope this helps.
November 6, 2005 at 6:30 PM in reply to: Problem with BizTalk Mapper merging two messages to one. #12200If you wanted to zip up the project, I would be happy to take a look at it.
You can find my email on the contact page or in my profile.
November 6, 2005 at 5:46 PM in reply to: using promoted property(Input Schema) in Send Pipeline #12115Thanks Man, I am able to achieved with promoting the property.
November 6, 2005 at 2:00 PM in reply to: Problem with BizTalk Mapper merging two messages to one. #12204Stephen
Thanks for taking the time to look at this and reply.
We have started with new projects in case anything was corrupted, but the same problems apply. The namespaces have not changed, and as yet we have not really started the mapping process – I wish we could get that far – most of the fields we are after are those not visible in the complex schema.
I will try to reproduce this in a simple contained project and post back the results of this.
Regards
MarkThis sure sounds like an error on your send port. Are you sure it is enlisted, started, and the filer is set up correctly?
You can always test it by adding a 2nd Receive Location to your receive port. Set this to file and then drop a test message into that location.
The routing report should be in HAT. I think it is adapter specific – so the error message will always say that even if the adapter does produce an error report. That would be the case.
Can you look at the complex type and see how it is defined? It should be in the schema someplace. I would have guessed it was a string
Maybe something else is wrong someplace.
November 6, 2005 at 3:54 AM in reply to: Problem with BizTalk Mapper merging two messages to one. #12199Did any of the namespace change since you created the map?
About the only other thing I can think of is to re-import you source schema and more or less redo the map. Make sure you redo the transform shape as well. I have seen that work in the past.
If you get it to work, please let me know.
I think that is all you need to do. Just make sure that is the host you are using on the Receive Adapter.
Other then that, I do not have any other ideas.
Thank you for your answer. I’ve been trying to do some experiments these days 😉
I’ve tried to use Loopback adapter from El Grego ([url]http://geekswithblogs.com/gwiele/archive/2004/11/10/14737.aspx[/url])
I had no luck, the send pipeline it’s configured with a Flat File Assembler and the receive one is pass through and expects a System.Xml.XmlDocument. The problem is that it’s trying to validate it and fails. I’m a bit confused now.
Probably I will try tomorrow to make a dummy orchestration and call it from the first one.
I have the host set to authenticated trusted in BTA hosts. Is that the same as trusted host? Or is there somewhere else where the host is set to trusted?
OK, I haven’t fixed it yet, but I’m close. The initial problem I had was a typo in the namespace of the property schema. This caused BizTalk to not send the SOAP header. Now that I’ve corrected the typo, I am getting better error messages.
If the WSDL file declares a SOAP header as only mixed=\”true\”, what data type should I use in the property schema? I initially tried xs:string, but I received the error attached below.
—————- WSDL excerpts —————-
<s:element name=\”user\” type=\”tns:user\” />
<s:complexType name=\”user\” mixed=\”true\” /><wsdl:message name=\”Createuser\”>
<wsdl:part name=\”user\” element=\”tns:user\” />
</wsdl:message><wsdl:input>
<soap:body use=\”literal\” />
<soap:header message=\”tns:Createuser\” part=\”user\” use=\”literal\” />
</wsdl:input>—————-Error ——————–
Details:\”Failed to initialize the SOAP header field or property \”userValue\”. Details: \”System.InvalidOperationExceptionThere is an error in XML document (1, 1).\”.
Possible reasons are:
1) MemberName property of System.Web.Services.Protocol.SoapHeaderAttribute does not map to a field or property in the type.
2) The message context property value associated with the header cannot be converted to the target header type.
3) The target field or property is read-only or cannot be modified. \”. -
AuthorPosts