|
Home > Archive > BizTalk Server General > March 2005 > not so fast
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]
|
|
| trinity 2005-03-23, 6:01 pm |
| I spoke too soon, even though the above lets you pick the right URI
from the correct Party list, it doesn't mean the EDI send port will
work.
Right now I am getting this error when my orchestration tries to save
something to the EDI send port:
Transfer of message(s) to EDI Subsystem failed.
Index was outside the bounds of the array.
Any ideas are welcome.
I have the same orchestration saving to a XML file as well (it splits
off, two Send objects, one goes to the EDI send port, the other goes
to a File send port), and the File based send port works fine. The
EDI based one gives the error above.
Ack... I am too tired of this to be angry.
There is pain, and then there is Biztalk pain. Ugh..
| |
|
| Hi,
to your original point, I am pretty sure that BizTalk and the EDI Adpaper
will work with the Database on different nodes, all the multi-processor
configurations would fail if it didn't.
I think your approach is conflicting with an area where BizTalk is weak or
not designed to work, that is managing a production system from a development
system. The preferred approach seems to be to develop on your development
system and deploy to your production system.
So installl and configure the production system as standalone, i.e. install
and configured but add no business information. i.e. make sure the production
edi server can see it's production database.
Use the deployment tools to move the tested confguraton over there. e.g. use
the Deployment wizard, BTSInstaller project and possibly some VBSCript to
deploy the configuration (no small task). You may need to run the base edi
tools to ensure it has cached the configuration and tables (look at
compeif.exe in ..\EDI\Subsystem).
There's quite a lot to do and it's not easy to summarize in a few minutes.
m
"trinity" wrote:
> I spoke too soon, even though the above lets you pick the right URI
> from the correct Party list, it doesn't mean the EDI send port will
> work.
>
> Right now I am getting this error when my orchestration tries to save
> something to the EDI send port:
>
> Transfer of message(s) to EDI Subsystem failed.
>
> Index was outside the bounds of the array.
>
> Any ideas are welcome.
>
> I have the same orchestration saving to a XML file as well (it splits
> off, two Send objects, one goes to the EDI send port, the other goes
> to a File send port), and the File based send port works fine. The
> EDI based one gives the error above.
>
> Ack... I am too tired of this to be angry.
>
> There is pain, and then there is Biztalk pain. Ugh..
>
>
|
|
|
|
|