|
Home > Archive > BizTalk Server General > July 2005 > EDI schema takes long long time to validate
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
EDI schema takes long long time to validate
|
|
| mis_gdtransportation 2005-07-07, 5:52 pm |
| Anyone have any ideas why validating a schema takes several minutes
(sometimes, as many as 8)?
I add an existing schema to my project (C:\Program Files\Microsoft BizTalk
Server 2004\EDI\Adapter\EDI Schemas\X12\4010\850Schema.xsd), right-click on
it and choose Validate Schema.
devenv.exe spikes for a while, then xsd2edi.exe spikes for a while, then
esp_srv.exe spikes for a while.
Finally, after as much as 8 minutes, it comes back and says the schema is
valid...
Invoking component...
Z:\My Documents\Visual Studio
Projects\btsMaddocks\btsMaddocksOceanCon
firmation.Schemas\850Schema.xsd:
warning BEC1007: Node "<Schema>" - Target namespace is empty.
Validate Schema succeeded for file: <file:///Z:\My Documents\Visual Studio
Projects\btsMaddocks\btsMaddocksOceanCon
firmation.Schemas\850Schema.xsd>.
Component invocation succeeded.
...but it hung at the "Invoking component..." portion for about 8 minutes.
I do have BTS2004 SP1 in place, as well as .NET Framework 1.1 with SP1.
I also applied "BizTalk Server 2004 SP1 Update for .NET Framework 1.1"
(http://www.microsoft.com/downloads/...&displaylang=en).
Anyone got any ideas why this is taking soooooo long?
I'm running Windows XP Professional on a 2.4 Ghz machine with 1 Gig of RAM.
The process of validating the schema doesn't drop my machine to it's knees
(CPU % is usually below 50%-60% for the devenv/xsd2edi/esp_srv
processes)....but it just takes so long to complete.
?Question: Once I put a solution in place utilizing the "base EDI" system,
are processes going to take this long to execute in production?
Thanks,
Dan
| |
| mis_gdtransportation 2005-07-07, 5:52 pm |
| Well, I've figured out how to prevent this huge increase in memory and CPU
utilization from happening....but I'm still not warm and fuzzy with they way
this Covast stuff is working.
I opened an example VS BizTalk project that came with the base EDI system:
C:\Program Files\Microsoft BizTalk Server 2004\EDI\Adapter\Getting Started
with EDI\Visual Studio Projects\Getting Started with EDI\Getting Started
with EDI.sln
The EDI schema (X124010850Schema.xsd) can be validated right away...no huge
spike in RAM or CPU.
However, if you set the root "<Schema>" tag's "Schema Editor Extensions"
property to "Covast EDI Schema Editor Extension", then the validation takes
a long long time and more than doubles (almost triples) the RAM the
development environment requires.
(My original test/validation had this set, so I'm sure that's why it was
spiking.)
This is still a problem though. The above is just a workaround.
I don't understand why you have to remove the "Covast EDI Schema Editor
Extension" value on "Schema Editor Extensions" every time you go to validate
the schema.
Thanks,
Dan
"mis_gdtransportation" <mis_gdtransportation@nospam.nospam> wrote in message
news:urEtMkygFHA.3164@TK2MSFTNGP15.phx.gbl...
> Anyone have any ideas why validating a schema takes several minutes
> (sometimes, as many as 8)?
> I add an existing schema to my project (C:\Program Files\Microsoft BizTalk
> Server 2004\EDI\Adapter\EDI Schemas\X12\4010\850Schema.xsd), right-click
> on it and choose Validate Schema.
> devenv.exe spikes for a while, then xsd2edi.exe spikes for a while, then
> esp_srv.exe spikes for a while.
> Finally, after as much as 8 minutes, it comes back and says the schema is
> valid...
>
> Invoking component...
> Z:\My Documents\Visual Studio
> Projects\btsMaddocks\btsMaddocksOceanCon
firmation.Schemas\850Schema.xsd:
> warning BEC1007: Node "<Schema>" - Target namespace is empty.
> Validate Schema succeeded for file: <file:///Z:\My Documents\Visual Studio
> Projects\btsMaddocks\btsMaddocksOceanCon
firmation.Schemas\850Schema.xsd>.
> Component invocation succeeded.
>
> ..but it hung at the "Invoking component..." portion for about 8 minutes.
>
> I do have BTS2004 SP1 in place, as well as .NET Framework 1.1 with SP1.
> I also applied "BizTalk Server 2004 SP1 Update for .NET Framework 1.1"
> (http://www.microsoft.com/downloads/...&displaylang=en).
>
> Anyone got any ideas why this is taking soooooo long?
>
> I'm running Windows XP Professional on a 2.4 Ghz machine with 1 Gig of
> RAM.
> The process of validating the schema doesn't drop my machine to it's knees
> (CPU % is usually below 50%-60% for the devenv/xsd2edi/esp_srv
> processes)....but it just takes so long to complete.
>
> ?Question: Once I put a solution in place utilizing the "base EDI" system,
> are processes going to take this long to execute in production?
>
> Thanks,
> Dan
>
>
| |
| WenJun Zhang[msft] 2005-07-08, 7:47 am |
| Hi Dan,
I'm afraid this's expected that the operation will be a bit slow.
However, since you are using X12, you should not disable the EDI
extension. Please look at the explanation below:
" It can take several minutes (or more, depending on the platform) to
build the Schema project; this is because the Validate process needs
to build relation tables that are used to conduct EDI rules
validation on incoming and outgoing documents. To speed up deployment
of the B2B solution, you can choose to disable EDI. However, the
solution will not be able to process EDI messages. To disable EDI:
a. Open the Litware.sln file in Visual Studio.
b. Expand the EDI folder inside the Schema project.
c. Double-click the X124010850Schema.xsd file.
d. In the Properties dialog, click Browse under Schema Editor
Extensions.
e. Uncheck Covast EDI Schema Editor Extension and click OK.
f. Save the Schema project, then build and deploy. "
Let me know if you have any further question. Thanks.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
| |
|
| Hi,
What's happening is that the Schema serve a dual purpose, they carry
infomation that populates the EDI Daabase and run-time cache file called
live.eif. Unless you are changing edi definitions - you only need to do this
once. So once you have built live.eif you can remove the "covast edi
extensions" from the Schema as you have done. BizTalk only uses the xml
information. You can deploy the live.eif file to the live system.
The engine information file (live.eif) also contains the edi addresses for
the trading partners. So you will need to maintain live.eif whenever trading
partner details change (only for edi partners). This can be done using the
compeif.exe programs.
m
"mis_gdtransportation" wrote:
> Anyone have any ideas why validating a schema takes several minutes
> (sometimes, as many as 8)?
> I add an existing schema to my project (C:\Program Files\Microsoft BizTalk
> Server 2004\EDI\Adapter\EDI Schemas\X12\4010\850Schema.xsd), right-click on
> it and choose Validate Schema.
> devenv.exe spikes for a while, then xsd2edi.exe spikes for a while, then
> esp_srv.exe spikes for a while.
> Finally, after as much as 8 minutes, it comes back and says the schema is
> valid...
>
> Invoking component...
> Z:\My Documents\Visual Studio
> Projects\btsMaddocks\btsMaddocksOceanCon
firmation.Schemas\850Schema.xsd:
> warning BEC1007: Node "<Schema>" - Target namespace is empty.
> Validate Schema succeeded for file: <file:///Z:\My Documents\Visual Studio
> Projects\btsMaddocks\btsMaddocksOceanCon
firmation.Schemas\850Schema.xsd>.
> Component invocation succeeded.
>
> ...but it hung at the "Invoking component..." portion for about 8 minutes.
>
> I do have BTS2004 SP1 in place, as well as .NET Framework 1.1 with SP1.
> I also applied "BizTalk Server 2004 SP1 Update for .NET Framework 1.1"
> (http://www.microsoft.com/downloads/...&displaylang=en).
>
> Anyone got any ideas why this is taking soooooo long?
>
> I'm running Windows XP Professional on a 2.4 Ghz machine with 1 Gig of RAM.
> The process of validating the schema doesn't drop my machine to it's knees
> (CPU % is usually below 50%-60% for the devenv/xsd2edi/esp_srv
> processes)....but it just takes so long to complete.
>
> ?Question: Once I put a solution in place utilizing the "base EDI" system,
> are processes going to take this long to execute in production?
>
> Thanks,
> Dan
>
>
>
|
|
|
|
|