Forum Replies Created
-
Posts
-
I don’t know of anything.
But, if you upgrade to BizTalk 2006 it comes with some type of JD Edwards adapters. I don’t know for sure if that would work for you but many new adapters will be available for free with BizTalk 2006.
You can get all the details on the Hot To Buy page: http://www.microsoft.com/biztalk/2006/howtobuy/pricing.mspx
Hope this helps.
Nope, not really any easy way to do this in BizTalk.
You could put all your “Goto” logic inside separate Orchestrations and then use content based routing to pass the message to the correct next step.
Your approach seems fine. The key is to break up the message into single messages before you process them.
You could also look at using a Convoy to process the received messages one at a time. This, along with an Envelope on the Receive Pipeline to break up the message can be a good solution without an atomic scope.
I have several samples of Convoys on this site and well as a lot information on de batching.
If you are using BizTalk 2006, it will not work with Visual Studios 2003. You need to have the RTM of Visual Studios 2005.
Do you know what type of error you are getting? Are you using the Community BizTalk Sharepoint Adapter?
I have a lab that uses the adapter for some basic posting. You can check it out here: http://www.biztalkgurus.com/Labs/Sharepoint-Infopath-BizTalk-Exceptions.html
Hope this helps.
This is difficult. It can be scripted, I think using the Explorer OM.
You can also use this tool (it won the Biztalk Design Contest in 2004): http://www.gotdotnet.com/workspaces/workspace.aspx?id=992ca223-553c-475a-ac87-da7ae2c9016a
Also, Todd Uhl’s blog has some deployment scripts for working with parties: http://geekswithblogs.net/toddu/archive/2004/11/09/14602.aspx
Hope this helps.
Just to add a little more to this post, I am winding down a project where we organinzed the solution by functionality. For example, we created a new project for each action (createItem, updateItem, confirmupdate, etc…). Each project had its own orchestration and transform map. All projects shared common schemas and pipelines, which were implemented as separate projects. Thus, our structure was as follows:
SampleSolution
SampleSolution.CreateItem
SampleSolution.UpdateItem
SampleSoluiton.ConfirmUpdate
…
SampleSolution.Pipelines
SampleSolution.Schemas
SampleSolution.ComponentThe rational for this solution structure was that we felt it would be easier to maintain if an action needed to be updated in the future. We would only need to replace the single assembly containing that action.
During development, we quickly discovered that each time we had to tweak a schema or pipeline, we had to undeploy each and every action assembly before we could deploy the update. This quickly became a rather tedious task. The Deployment Framework can simplify this task considerably, but you will need to make modifications for each solution you create if you use the approach I am describing. If you use the suggestion made by the instructor, however, you can use the Deployment Framework, essentially wothout modification.
In hindsight, my next project, I will structure my solution into BizTalk pieces, as mentioned, because I now realize the maintenance will essentially be the same, but deployment will be much simpler and less complex. (you still only need to redeploy a single assembly.
I hope this helps.
JimM
Well, I have resolved this issue. The problem was this box was unpatched, so I applied the Windows Server 2003, BizTalk Server 2004, and SharePoint services service packs. After doing that, my web services are working…but the Service Pack for BizTalk brought up another interesting issue which I have to ponder for a while and will probably post on later 🙂 Thanks for the help!
Bob
Hi,
If I understand you correctly, you’re trying to deploy a BizTalk solution to a BizTalk server without Visual Studio .NET installed. What you’re going to have to do is deploy and bind the orchestration on your development machine, and then use the BizTalk Deployment Wizard to export the assembly to a binding file (it’s an XML file). After you have this binding file, you will have to open it and edit all the send/receive locations so they are correct for your production environment. Then, use the Deployment Wizard on your production machine to deploy your assemblies and import the binding file.Hope this helps.
Sorry, I do not know of any way to test it using NUnit.
What I did in the past using NUnit for Orchestration was expose them as web service. Then, I made a call and waited for the response file. You could try something like that. Not very programmatic though.
I’d be curious how it works out for you.
As Biztalk developers what do you find are the most difficult challenges in your day-to-day work? Mapping disparate schemas? Debugging message flow? SSO? Creating custom components for Biztalk? I would like to know…?
Hi! What you heard from your instructor about seperating different BizTalk \”pieces\” into seperate projects is good practice. What I usually do is I have 1 solution, lets call it SampleSolution. Underneath this solution, I have 1 project for each piece in the solution…so orchestrations get a project, transforms get a project, pipelines get a project and etc. I usually name my projects with the solution name followed by a period and whatever component happens to be. So for my SampleSolution, my orchestrations project would be called SampleSolutions.Orchestrations, my maps would be called SampleSolution.Transforms and so on.
This tends to help keep things organized and a bit less chaotic. It also is handy if you use custom deployment tools such as the Deployment Framework from Scott Colestock. Hope this helps!
Hi Dipesh,
Thank you for reply.
I have seen that binding file and realize that, the binding files are created by some utility. Because in binding file all the information related to project is stored. But don’t know how to create it?
You have any idea about how to create that binding file? Please guide me about how to create it.
Thank you
Jyo
I am a newbie in Biztalk. I am trying to transform a flat file into an XML file.
1.The source text file has a [b]Birthdate[/b] field, in the flat file’s schema I have set the data type property to ‘xs:date’ and customdate/time format property to ‘MMddyyyy’.2.I have created the Receive pipeline and have used FlatFile disassembler.
3. I have created a destination schema for my XML file, it also has a BirthDate field whose data type property is set to xs:date. I am using a map to transform my source flat to XML destination.
My Concern:
I have deployed the project and its working fine only when all the records have valid (not null) date values in the birthdate field. But it fails if any of the record is having a null value in the date field.I checked and received the following description in HAT:
There was a failure executing the receive pipeline: \”ImpFile.RecMembers\” Source: \”Flat file disassembler\” Receive Location: \”C:\\BizTalkPractice\\In\\*.txt\”
Reason: The Date or Time value received for Field: BirthDate is incorrect. Error: String was not recognized as a valid DateTime.Now that I have run only 3 records in my sample text file but after the project is deployed live then I will be processing 10 MB file. Is there any better option that could be followed to check the date fields against null and invalid date values. At the same time the transformation process should not eat up much time and resource…… thanks in advance ( 🙂 Amit)
