Forum Replies Created
-
Posts
-
I have seen this problem when I was using a binding file from BizTalk 2006 CTP build on BizTalk 2006 beta 2. Not sure if that helps you or not.
Best of luck.
Stephen W. Thomas
This would be like comparing a Swiss Army knife to the Swiss Army.
SAP produces a vast amount of highly functional business software from ERP, CRM, SCM etc.
Biztalk is a highly functional Integration Engine based on the .NET FrameworkSAP have a product called NetWeaver, a Java based Integration engine. One of the main purposes of NetWeaver is to open up the SAP systems using Web Service interfaces rather than the proprietary BAPI or IDOC interfaces.
Netweaver is not nearly as functional as Biztalk, in fact SAP recommend using Biztalk or IBM WebSphere when process orchestration is required.Do you already have any SAP software?
I haven’t used the EDI features of Biztalk, but your requirement looks like standard functionality.
In addition Covast have a more complete EDI implementation that extends the Biztalk EDI features1. Yes. Biztalk uses values in the Message context to determine routing. At various points in the process you can promote data from the actual message into the message context.
2. Biztalk has no preconfigured or packaged VAN connection mechanisms. But the variety of adapters, both protocol and application are standard. There are also third party adapters available and worst case you can write a custom adapter
3. Trading Partner management is ok. There is a Business Activity Services web site provided that allows managing partner info. There is no wizard for importing TP information, although I would imagine this could be created.
Hi,
I am preparing to purchase Biztalk for my company but I have a few questions. I notice there’s a few different versions, with one of the differences being the amount of ‘applications’
Can anyone here with Biztalk experience relate to me what an application is? Preferably in terms of Biztalk for EDI usage? It appears the standard version allows for 10 applications. I want to make sure we purchase the correct version.
Also, when purchasing 2006, you need to purchase one license for every processor, correct?
Thanks!
Thank you for the feedback! That really explains a lot.
Michael
[quote:8b1db2c75d=\”greg.forsythe\”]The transform shape does not validate either the input or output against the message schema. It just executes the XSLT.
If you wish to validate a message against its schema you need to use the XmlValidate pipeline component in receive pipeline.[/quote:8b1db2c75d]
For debugging I created two schemas: NameSource and NameDest. Both have three attributes: Fname, Mname, and Lname. I made Mname a \”required\” field on BOTH schemas.
I test both schema’s without Mname and get errors (as expected). All is well.
I built a simple transform – and testing resulted in errors again (as expected). All is still well.
I then built a orchestration that simply receives source… transforms…. sends results.
I obviously deploy and start the orchestration. When I drop off the test doc, it is processed [u:5b1ab4af0b]WITH NO ERRORS[/u:5b1ab4af0b]. I simply get MName=\”\” in the output XML.
Why is the orchestration not creating an error on this? It is like the \”Use Requirement\” property is completly ignored in the Orchestration.
Thanks,
MichaelUse [b:770571e7c1]Validate Map[/b:770571e7c1] to produce Xslt
There is a link in the output pane or you can find the file at:
C:\\Documents and Settings\\<user>\\Local Settings\\Temp\\_MapData\\<mapname>.xsl.xmlAssuming BizTalk 2004, you need to test the map in Visual Studio. In the output pane there will then be a link to the generated XSLT.
HTH
You need to be a bit wary when using direct ports.
A direct receive port will create a subscription of:
BTS.MessageType = [i:06e305e3d8]type of the receive shape message[/i:06e305e3d8]
+ any filter you set on the receive shapeIf you do not specify any additional filters on the receive shape then the orchestration will consume every message of that type published to the messagebox irrespective of origin. This may be what you want but can cause a loop if your orchestration sends a message of the same type.
Also, if you have multiple subscribers to one message, each subscriber will receive a copy of that message.
Biztalk Explorer reflects the configuration from the BiztalkMgmtDb database. If changes are made to the config via another mechanism e.g. deploy, import binding file, etc, these changes are not immediately reflected in Biztalk Explorer.
You need to [b:73770f1dd2]Refresh[/b:73770f1dd2] Biztalk Explorer (right click -> refresh) This forces Biztalk Explorer to read the config from the database again
I always check the assembly list and make sure my newly deployed asssembly is there before continuing.
I am not sure I understand your question:
Does anyone have idea how to define correct schema by filename?
Are you referring to how Biztalk matches an incoming message to its schema?
Hello. Problem is now [b:106ced1d5c]solved[/b:106ced1d5c].
Actually problen was in files that bts was reading. There were no namespace definitions in files and therefore it could not be routed into proper disassembler. Problem was solved by adding namespace definition to receiving XML file. This problem occured when having more than 1 receive ports in 1 solution.
Does anyone have idea how to define correct schema by filename?
/RM
[quote:106ced1d5c=\”RM \”]I am having a slight problem with BTS2006.
I have a simple orchestration with a receive port whic is using XMLReceive pipeline.It simply gets XML file (Encoding UTF16) also tried with ANSI, UTF-8 etc.
and tries to forward it to send location. Previously all were ok even with SQL connectors, transformations etc. and all worked file, then something happened and now no message readings are succesful.All messages goes suspended (resumeable).
[b:106ced1d5c]Error is :
Reason : None of the components at Disassemble stage can recognize the data [/b:106ced1d5c]I have tried to make custom pieline also but error is the same. Also other buitIn adapters are tried.
All help would be appreciated.[/quote:106ced1d5c]
