Forum Replies Created
-
Posts
-
I am having the same dilemma with BizTalk. I want to publish the web service to another server but I don’t know the requirements for biztalk in this server.
I do need the same but just want to know the properties you set at root and chile root and record level…Quick reply will help me ..thank you.
Actually sorry misread ur reply.I believe you have given me the answer I was waiting for. Thank you for your guidance.
Hi xman,
Thank You for your reply. Although the file name is accessible through the constructed message, the file name alone does not help me uniquely identify the drop location. How can I ensure that I can access the folder path so I can use some regular expression and parse some identity against the filepath? If the folder path is not accesible in the orchestration, can i assign some property to the receive location that i can access through the orchestration. Once again I appreciate your guidance.
Regard Ty
Hi Ty,
This is a pretty straightforward answer to your question:
In your orchestration, you define a message associated with your receive port that activates your orchestration (let's call this message mInitOrch). Then, in an Expression shape, you can reference the property for this message that return the drop location folder name by using this statement:
vMyString = mInitOrch(BTS.InboundTransportLocation);
vMyString is a variable of type String in your orchestration.
I hope this helps.
"However, when I "ignored" this error and proceeded with submitting a message through BizTalk, the custom component "woke up" and realized that it was going to be called. The breakpoint errors went away, and debugging worked exactly as it was supposed to!"
Perfect ! That solved my problem … Thanks a lot !
Depending on what you are trying to do you can do most activities in a pipeline and build an object to or from Teradata.
See these two pages… msdn.microsoft.com/…/aa577468.aspx and salmanzg.wordpress.com/…/biztalk-shared-application
The problem is the same schema deployed in two or more applications. You'll need to create another applications that have the schemas that you will want to use, for more than application, and then reference that schema as many times as is needed.
Hi,
What you need to do is following
1. Create a Schema for the new XML file format(Ordering System).
2. Create a Map which will convert the 850 to the new XML format.
3. Use the map in the Orchestration or on the Sendport.
4. Drop the mapped XML format to the output folder where the Ordering system picks up the file.
