如何保留交换，或不使用两个应用程序的同一方。 [英] How to Preserve Interchange, or not.. using the same party for two applications.

问题描述

所以我确实知道我的问题的快速答案，即修改EDI接收管道并推广"ReuseEnvelope"。属性为True。但它让我感到困惑，它必须以这种方式完成。对于相对
的简单问题，似乎也是复杂或侵入性的解决方案。

So I do know the quick answer to my problem, that is, Modify EDI Receive Pipeline and promote the "ReuseEnvelope" property to True. But it just baffles me that it has to be done this way. Seems too complicated or invasive solution for a relatively simple problem.

现在的问题是：

我有两个BTS 2010应用程序：

I have two BTS 2010 Apps:

1。通过接收端口获取单个EDI（文件），然后在一天中的某个时间创建批处理，并将其放入另一个批处理文件夹中。

1. Takes single EDI's (files) in, via a recieve port and then creates a batch at certain time of day and drops it in another folder with batches.

2。第二个应用程序获取批处理文件，打开它，循环遍历事务集，从批处理中的每个事务收集声明编号和标识信息列表，并创建一个xml文件，该文件发送到Web服务为
以"已处理"字样提交进入自定义内部应用程序。

2. This second app picks up the batched file, open it up, loops through the transaction sets, gathers a list of claim numbers and identification information from each Transaction in the batch and creates a xml file which is sent to a webservice to be filed as "processed" into a custom internal application.

问题在于：应用程序1和2都解析为同一方，但＃1需要"拆分交换......"。协议中的设置或它不会批处理文件。但是app＃2需要这个设置为"Preserve Interchange ...."或者它不会识别app＃2中的
多个TS Envelope架构，所以我可以遍历它们。

Here is the problem: Application 1 and 2 both resolve to the same party but #1 needs the "Split Interchange...." setting in the agreement or it wont batch the files. but then app #2 needs this setting as "Preserve Interchange...." or it wont recognize the multiple TS Envelope schema i have in app#2 so i can loop through them.

我正在考虑的分裂或保留设置是在协议属性>交换设置>本地主机设置>接收器设置>入站批处理 选项下拉。

The Split or Preserve setting I'm reffering to is in the Agreement Properties>Interchange Settings>Local Host Settings>Receivers Settings>Inbound batch processing option drop down.

有没有办法设置接收端口或方自身，以便它可以使用interchnage根据它是什么应用程序拆分或保留？

Is there a way to set the Receive ports or the party itself so it can use the interchnage split or preserve according to what app it is?

 

关于那个说明：我真的认为这个选项不应该是协议，但接收端口的一部分，因为您希望文件处理的方式与EDI标头和发送接收方业务无关。这样您就可以通过一方处理
两种方式。接收端口在管道设置中有一个名为"Preserve Interchange"的选项。是真还是假，但只有在消息无法解析为聚会时才有效。在我的情况下它确实解决了派对，因为标题是
与App＃1相同。

On that note: I really think this option should not be part of the agreement but part of the receive port because how you want the file to process is not really related to the EDI Header or send receive parties businesses. This way you will be able to process both ways with one party. The Receive port does have an option in pipeline settings called "Preserve Interchange" true or false, but that only works if the message fails to resolve to a party. In my case it does reolve to the party since the header is the same as App #1.

同样在app＃2中，我不关心标题我只是需要身体里的信息。我知道我可以使用"ReuseEnvelope"上下文但又要求app＃2的自定义管道。

Also in app #2, i do not care about the headers i just need the information in the body. And i know i can use "ReuseEnvelope" context but then again that requires a custom pipeline for app#2.

是否有创造性的方法可以在不创建自定义内容的情况下执行此操作？

Is there a creative way to do this without creating custom stuff ??

预先感谢任何解决方案或想法。

Thanks for any solutions or ideas in advance.

推荐答案

一个简单的解决方法是创建一个副本原始文件，然后以完全不同的方式处理这两个文件。

One simple workaround is to create a copy of original file, then process both files in completly separate ways.

为此，您可以使用额外的一对端口：  receive - >在第一个接收端口之前发送。

To do so you can use an additional pair of ports: receive -> send before the first receive port.

 

这篇关于如何保留交换，或不使用两个应用程序的同一方。的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！