Forum Replies Created
-
Posts
-
1.You need to use Equal Functiod
—1st Parameter ….Input xml node( from Source Schema)
—2nd Paramter as custom paramter and just type P without any Quotes.
2.Pass on the output of this Equal functiod to Value Mapping Functiod.
—1st parameter Ouput of Equal to Functiod.
—2nd Parameter Custom parameter …….just type Prepaid without Quotes.
Output of Value mapping to the Destination node.
Same way for C…
Hi Stephen,
Thanks for your reply, no i am not using flat file disassembler, i am using XML disassembler.
Many thanks
Umesh
Not sure…. Something like this can be vary hard to track down. I’d start by looking at any .net components your Orchestrations might be callings.
And sometimes for things like this Microsoft Support can be a big help.
You might want to take a look at my BizTalk 2004 Sample: Limit Running Orchestrations. I do something like this for the number of running instances. Of course, your solution would be much simpler.. so just look at the Rule Engine code.
It all really depends on your client and your exact project. But in the past, we have always had separate QA and UAT Environments. We the goal is to have one mirror projects but I have never actually seen that happen.
It is had to do user testing at times but usually this is done running the end application or use some type of simulated test files.
As far as BAM, I’ve not done too much with it so I’m not sure they best approach.
Hope this helps.
Hi rseroter,
Thank you for the information. I think HIS is definitely the answer for integrationg BizTalk and IBM mainframe. But how to convince my client that we need another server like HIS for our Proof Of Concept about BizTalk ? I think my client's not ready to add extra money for a new solution because its main argument is that all business rules are implemented in the mainframe ? So what's the use of BizTalk ? converting XML into cobol format ?
Anyway, we'll going to try BizTalk & HIS.
Thank you.
Xtasy
A "quick" suggestion is to create a custom DateTime functoid. I had a similar scenario when moving data into Oracle, which has "wonderful" requirements for date and time formats. The best part is that once Date/Time is in the xsd:dateTime format, it goes in without fail. Now the only trouble is stringing together all the functoids in a map to make it work, hence the first solution was to use a scripting functoid. Of course, since I need this repeatedly, a .NET component and conversion functoid were completed that day.
If you like the idea, the SDK gives enough examples to get started. The only real work is in creating the few lines it takes to convert the formats. My solution was to allow a string to accept any valid .NET dateTime format and use the built-in methods to produce the xsd format. It wasn't pretty and can use some cleanup, but here's the basics…
public string ConvertStringToXsdDateTime(string sDateTime)
{
DateTime dReturn = new DateTime();
dReturn = DateTime.Parse(sDateTime);
return dReturn.ToString("s")
+ TimeZone.CurrentTimeZone.GetUtcOffset(DateTime.Now).ToString().TrimEnd('0').TrimEnd(':');
}It works for me in EST/EDT zone, but I haven't attempted real testing. Hopefully someone will attempt this and find a more "perfect" solution and post it here.
BizTron
Rob,
My guess it has something to do with this:
A Receive error message "Syntax error converting datetime from character string" occurs while sending updategrams to the SQL send adapter.
This problem can occur if The SQL table contains a datetime column and the updategram is trying to update that column with an incorrect value.
To resolve this issue, do not use the BizTalk Mapper functoids to create the datetime values to map to the updategram. The functoids create a datetime value in the format "1999-05-31T13:20:00.000-05:00". SQL datetime columns require datetime values to be of the format "1999-05-31T13:20:00.000". Instead of using the default date and time functoid, create the datetime value manually by calling the Parse or ParseExact method of the DateTime class.
You may have to play with the System.Xml.XmlConvert class to handle cases where the day and month are getting confused.
Doug
HI ,
I solved the issue. It was a configuration issue. I reconfigured Biztalk including the Isolated host and found that it is not making any error.
Sam
You can use MQSeries to push data to, and get data from, the mainframe. What you're doing with COBOL could best be accomplished with BizTalk and Host Integration Server (HIS) together. HIS 2006 (included with the BizTalk 2006 license) allows you to convert COBOL and RPG source to XML schemas (using the Transaction Integrator plug-in for Visual Studio that comes with HIS).
Check out http://www.microsoft.com/hiserver/default.mspx for more on HIS. They key is, HIS 2006 ships with BizTalk adapters for MQSeries, DB2, host data files, and host apps. So, you can use BizTalk to route and validate data, and use HIS to interact with the mainframe.
At this point, there's nothing "BizTalky" about the web service. Test it as you would any ASP.NET web service. Create a simple client application, establish a "web reference" that points to the generated service, and then build up the input message and post it.
