Forum Replies Created
-
Posts
-
I worked with eConnect a while back and I don’t remember using the add generated items.
I would try reinstalling and make sure you have VS called when you do.
Also, make sure you are using the right version on VS (i.e. not 2005).Best of luck.
I don’t know that much about the SQL adapter. But, I think you would need to break this up into 3 separate messages to make 3 calls to the SQL.
Hope this helps.
You will have to deploy all the projects but that is the “correct” way to do it.
If I’m just building a sample or demo I’ll usually just put everything into one project.
In 2006, when you redeploy life is SO much easier since you do not have remove the referenced assemblies first.
Best of luck.
Try closing Visual Studios and stop all your BizTalk Hosts and see if you can remove the dll in the folder. Then try to rebuild.
Otherwise, make sure no other uses have the solution open in Visual Studios maybe through another logon.
Best of luck.
I don’t really know of any papers on best practices.
It really all depended on how large you document is, what type (Xml or Flat File), transaction requirements, etc.
If you wanted to post so more details I could tell you how I’d go about it.
One silly thing to note is that is you are going to use BAM, you need to have Excel installed on the production server before you install BizTalk.
I think it can then be removed
You can use an XSLT Template in a map like this:
Connect <cromatografia> to a Scripting Functoid (Advanced) and connect output to <Tag>Within the functoid select [b:f8571d04b4]Inline XSLT Call Template[/b:f8571d04b4] and add the following xsl code
[code:1:f8571d04b4]<xsl:template name=\"TagTemplate\">
<xsl:param name=\"param1\" />
<xsl:for-each select=\"$param1/@*\">
<xsl:element name=\"Tag\">
<xsl:element name=\"Description\">
<xsl:value-of select=\"local-name()\" />
</xsl:element>
<xsl:element name=\"Value\">
<xsl:value-of select=\".\" />
</xsl:element>
</xsl:element>
</xsl:for-each>
</xsl:template>[/code:1:f8571d04b4]I had a small problem with this on BTS2006 as my BTS2004 dev environment is undergoing maintenance currently.
If this does not work can you post the XSL output from the map.My company uses K2 for our human workflow interfaces. We have had to write our own workflow engine to get the functionality we were promised to work. Short story, I would avoid an investment in K2 until their product is more mature (if I remember correctly, multiple routing paths and some other \”normal\” workflow requirements don’t work as promised). A friend of mine that does BizTalk consulting has told me that the human workflow in BTS 2006 is wonderful, but I have yet to try it out. I am in the beta program and one of the TAP programs, so I haven’t had much time to play around with the workflow stuff yet. I’m looking forward to the next iteration though.
According to Sarbanes Oxley, a production server really cannot have development tools installed. In order to install BizTalk Server 2004 in a production environment, you only need to install the .Net framework.
That sounds like a permission problem.
Make sure you are a member of the local Admin group and SSO Admin (or SSO affiliate administrator).
Best of luck.
There should be. Are you sure you have the adapter installed and setup in the Biztalk admin tool? It doesn’t install with BizTalk Beta 2; it’s a separate installation. Then, it doesn’t get added to the installed adapters automatically. Check to make sure you see it under the installed Adapters.
Also, they have a good step by step guide in the C:\\Program Files\\Microsoft BizTalk Adapters for Enterprise Applications folder.
It looks like you are sending the web service data in a format it is not expecting.
I would probably wrap your web service call inside a .net component call and see if that works. That is how I have called Java web services in the past.
Typically, Java web service want arrays of objects as input. BizTalk doesn’t really like that. Although, the WSE adapter could be used for that.
Hope this helps.
