HI, New EDI Freight project came up as a part of it we are trying to implement through webMethods.We just received sample EDI from one of the customer and they are using EDI X12 210 Transaction Set 210 is used by the motor carrier industry to provide an itemized detail of freight charges to parties relevant to the shipment. I am Just wondering how to start with. Is there is a way I mean to map to the standard x12 810 in webMethods? Any Ideas will be really helpful.Could you please advise. Thanks in advance, Capri_lak.

EDI 210 (Motor Carrier) is used differently than 810 (purchased materials/Items PO invoicing).So you should create a different canonical/standard document depending on source/target you are mapping to.

HTH,
RMG

Hi RMG, Thank you very much for your response. I will definitely work in that direction. thanks, Capri_Lak.

Hi, Actually, as a part of the freight EDI project we were going through the EDI Specs and found the req fields as M-Mandatory, O-optional but there are some segments which are displayed as X,X/Z…I am just wondering what that type exactly means.If possible is there any list of information available for usage indicators handy?Any help is greatly appreciated. Thanks, Capri_lak

X - indicates Relational

Relational Conditions
Relational conditions may exist between two or more data elements within a segment based on the presence or absence of one of those data elements (presence means a data element must not be empty). Relational conditions are specified by a condition code and the identity of the subject elements.

Within a segment, the existence of a relational condition is indicated by the designator ‘X’ in the attributes column and is displayed under the heading ‘Syntax Notes’. The code is constructed using an uppercase letter (P, R, E, C, or L) followed by the two-digit number of the data element reference designator for each data element included in the relational condition.

Please check this[FONT=Arial] Data Element Requirement Designator:[/font]

[FONT=Arial][B][url]http://www-03.ibm.com/procurement/proweb.nsf/0/95f8f1d5d90b66ee85256c91005a67c2?OpenDocument[/url][/b][/font]

[B][/b]HTH,
RMG

HI RMG, Thank you very much for your response. It is really helpful. Thanks, Capri_lak

your welcome

Hi, Currently we are trying to decide on the protocol to receive the EDI 210 document from the customer.we are not using VAN. IF I am not wrong AS2 does require certificates and we also want to avoid that route as much as possible to avoid the maintenance overhead. I think we can also implement SFTP. But we wanted to keep simple as much as possible. So thinking in that aspect,Actually we do have one integration which customer sends XML via HTTPS using username/password.I am just wondering is it acceptable or possible for the customer to send the EDI via HTTPS with username/password? or DO we have to use AS2? Any Help is greatly appreciated. Thanks, Capri_lak

I am just wondering is it acceptable or possible for the customer to send the EDI via HTTPS with username/password? → If they can wrap EDIdata inside a XML wrapper then it works via https post/get.

or DO we have to use AS2\https–> I would also suggest this route and ofcourse self/partner certificates are required over security layer.

HTH,
RMg

Hi RMG, Thank you very much for your response.I will check back with the customer on that regarding wrapping EDI in XML.Also just wondering if we implement SFTP, If I am not wrong it is been provided by a external package,in such cases, if some issues comes Does wewbmethods tech support provide us enough support? if we implement SFTP. Thanks, Capri_lak.

Wrapping the EDI in XML is not necessary. Simply post the EDI doc with the appropriate content type (application/EDIstream) in the HTTP header. It will work just fine.

Rob,Do you think it will work with just by setting Content-Type (application/EDIStream) and passing data/stream via pub.client:http service for EDI docs?

For incoming (calling an IS service) pub.client:http would not be used. The caller would simply HTTP post to the appropriate URL for the gateway service. The IS content handler will put the EDI data in the pipeline as a stream.

For outgoing, pub.client:http can be used, setting the content-type header to application/EDIstream – if the recipient supports that type (I think that’s custom to IS). Or they could post it as text/plain and get the raw text and handle as desired.

It make sense now and we are on same page…ty

Hi RMG, I am just wondering if we go using the AS2 protocol which includes certificates as well, Whenever we install/renew the certificates, Is it Mandatory to restart the server? Because we do have one partner right now which we do AS2, when they renewed their certs we installed them on our end and had to restart to make everything back to normal. So if that is the Case, Moving forward there will be more than 50 customers on the board which restart is kind of performance if we have to restart every time new certs came into picture…Could you please advise. Thanks, Chandra.

Hi, Actually I am just wondering the basic difference between 997 and MDN. I was going through documentation it does said 997 will be sent when we receive the document syntactically validated from customer as not being processed.So Does it really make sense to have 997 and MDN as well? If 997 is being only sent to inform the customer that we recived the document without any validation is it worth to have 997 in place, as if I am not wrong, MDN does the same thing. Could any body advise what and why they are exactly used both technically and functionally. Any help is greatly appreciated, Thanks, Capri_lak

Hi, I am trying to install EDI x12 4030 210 document type from admin console and getting the following error:com.wm.ff.parse.StorageException: [FFP.0015.0003] Cannot save changes to dictionary EDIFFSchema.X12.V4030:Dictionary. Dictionary is not locked. Could anyone please help. Thanks in advance, Capri_lak.

May be it could be due to IS memory issue or something might happened that moment…

If not can you try same install diff timings/server restart and see if the error still persists? or Reload the WmEDIForTN package and try it again. Do you see the doc type got installed in TN even though error occurred?

HTH,
RMG

Hi RMG, Thank you very much for your quick response. Actually the Document type is getting installed on TN even though the error is showing up as I checked it is showing the most recent timestamp. I am going to try out the options you listed and let you know. Thanks, Capri_lak.

ok let us know the outcome…

HTH,
RMG

HI RMG, Everything worked fine after the server restart.Thank you very much for the advise. Thanks, Capri_lak

Glat to hear it worked!

Hi, I am implementing pub.client.http built in service to retreive data from the customer using get method. I am able to see the service is getting executed and displaying the results.But while testing the service, the results panel is frozen and the developer is getting hung.Could anyone please advise. Thanks in advance, Capri_lak.

Is the document received very large (EDI or xml)? Also you can try increase developer heap size in the developer.bat and resart session.See how it goes.

First test with smaller files and see the difference.

HTH,
RMG

Hi RMG, Thank you very much. Yes it is an Large XML. I am going to increase the heap size and work in that direction. I did search in my developer.bat file and didn’t find any parameter related to heap size.I am Just wondering is there any other place i need to look for that parameter? Could you please advise. Thanks, Capri_lak.

The setting used to be earlier versions and now it points to jvm folder…anyways since the doc is large it as expected…you should implement the IS large file handling using WmPublic node iterator services (node) or TN large doc handling configuration to view bytes by bytes…Pls check this forum on large file techniques as there were many threads discussed in this direction.

HTH,
RMG

Hi, I am just wondering when we use Deployer tool to prmote the packages from test to production, Do we need to restart the production servers regarding the new packages to take effect? I mean is it mandatory to restart the server.Could any one please advise. Thanks in advance, Capri_lak.

No need for restart always unless you see any issues/in logs…Normally after the package deployment (patch or full build) successfully installed (per build report),then just make sure Packages–>Management -->your deployed package is loaded with out any errors (some times partial) and must be in the enabled state…

HTH,
RMg

Currently I am working EDI project which I am having an issue as follows: So we are basically getting the EDI from Customer and need to send 997(FA) to them. As a part of it I selected auto generate option in Partner specific TPA. It is processing fine, but the 997 are going under the Document type as x12 envelope instead of X12 version 997 as document type in the TN console, which we are having trouble to recognize which document while troubleshooting. I am just wondering am I missing anything which is causing the issue. Could anyone please advise when you get a chance Thanks in advance, Capri_lak

By default it will send X12 Envelope only as expected and you should be sending envelope level that acks all (ISA/GS level)…

Other wise you can set up a custom generateFA (logic) service and create a processing rule that will send X12 version 997 transaction level.But this over head can be avoided with default auto generation option.

HTH,
RMG

Our present architecture is 4 IS’s running on two physical boxes not clustered.We have created the same number of schedulers on each instance and made sure they are enabled on only one instance at a time. we are in the process of coming up with a script that should take care of suspending those schedulers before it brings down the instance on weekly basis.I am just wondering when I ran the get taskIDs service on all the 4 instances it did give me the information regarding the schedulers fine, but they are having the same taskIds on all the 4 servers, Just curious to know how the taskids are assigned? even though the schedulers are on different instances will they have the same taskiD?Could anyone please advise when you get a chance. Thanks, Capri_lak.

Did you configure Remote Servers alias (on 4ll 4IS’s)

HTH,
RMG

Hi RMG, Yes we did configure remote aliases on all 4 IS’s. Thanks, Capri_lak.

Did you selected the right Target server on all IS’s during Scheduler configuration and this could be the check point?

Hi RMG, Thank you for your response. I am actually confused regarding the configuration of target server on 4 IS’s? Like I mentioned in the past all the schedulers are defined on the 4 servers and they are enabled on only one instance at a time based on the need.I am just wondering Can we do something like you are mentioning as configuring the same target server? Could you please advise. Thanks, Capri_lak.

Can we do something like you are mentioning as configuring the same target server? → What i mean is when you created scheduler have you selected that particular IS Name in the Cluster Target Node? (I understand you have enabled schedulers only on one of the 4 IS’s)

HTH,
RMG

Hi RMG, I would like to let you know that the 4 IS’s are not in cluster and they are stand alone on two physical boxes two on each and the schedulers are enabled on only one instance at a time. Thanks, Capri_lak.

Since you configured remote servers on each IS…do you see the Target param filled in the scheduler admin page on each IS?

Hi RMG, I do not see ant target param field on the scheduler admin page on any of the IS’s. I would like to let you know that we are on IS 6.5 sp3 environment. Thanks, Chandra.

Uh…I thought you are on 7.x…Sorry!

Hi RMG, Any advise on 6.5 SP3? Thanks, Capri_lak

“same taskIds on all the 4 servers” → I am still unsure how come they are same esp in a non-clustered env…Can you try to recreate on single IS and check it?

Hi, we are getting an 4060 210 EDI from customer which is having record delimiter as …(3 dots) But when is getting submitted to TN is it getting replaced as little square box in the content of TN console.This is not causing any problem while splitting the documents. But just trying to maintain a sync between the data sent by customer and view in the TN.What I understood was when that special delimiter(…) is coming, the webMethods EDI is not able to recognize and replacing it with small square box.Also I realized the current setting for charset in our environment is as follows:ISO-8859-1. Based on my research,I realized that we should be using charset=UTF-8 to get that delimiter displayed. Is there any way I can populate it? I mean any place specifically to take care of it and get it recognized.I am also little bit concerned of not touching the existing charset:ISO-8859-1 to effect the current integrations. If there is any other way around I would like follow.Could anyone please advise when you get a chance. Thanks, Capri_lak.

By default it should be charset=UTF-8 (XMLdata or EDIdata processing) not ISO…It shoudn’t effect env and test it.

HTH
RMG

It is not replacing anything. As we’ve discussed in our email exchanges, it is a display concern only. The character used for the delimiter in ISO-8859-1 is simply a non-printable character, and is displayed as a square box.

Unlikely. It depends on what encoding the partner used to send the EDI data. Most likely it is ISO-8859-1, not UTF-8. In any case, processing the incoming data you’ll want to explicitly set the charset to use when the bytes are read–the charset must match what the partner used to encode the bytes. Even if the default charset of the JVM is UTF-8, the charset of the data will still be ISO-8859-1 (if that’s what the partner is sending) and that delimiter will still display as a square box.

The out-of-the-box default charset is UTF-8. But that can be changed. I’ve seen at least one installation that changed it to ISO-8859-1 to make bytesToString/stringToBytes service calls easier by not needing to explicitly set the encoding. This can be useful when the majority of interfaces use ISO-8859-1.

Changing the default charset of the JVM can have serious impact on existing integrations. A change to it is not something to take lightly–if assumptions were made about the default charset then changing it can break existing integrations.

I agree with you Rob.,…out-of-the-box default charset is UTF-8 and not ISO as I indicated above also…and use the service calls that you mentioned for convertion.But I have not seen installation that changed to ISO charset based default…

Hi, Currently we have a partner, we do send 856 to the partner. As a part of new requirement, we are receiving 410 from the same customer.When the document gets processed in TN, In Transaction Analysis I do see x12 group/x12 envelope processing status as Done W/Errors. which is displaying the error msg as follows: Expected a control number of 2, but received 1. This is a duplicate control number. [EDIFTN.000010.000248]. This is not causing any issues as data is getting parsed the way it is supposed to be.But from trouble shooting point of view it is displayed as Done W/Errors which is misguiding us.I am just wondering, since it is an existing partner, the control numbers are some how getting used again.Is there any way to update/configure the control numbers that way they don’t overlap and avoids this issue.Could anyone please advise. Thanks, Capri_lak

Yes you can update/configure control numbers(increment order partner specific during add envelopes from table) using EDI Module services /WmEDI home page (Manage control numbers) partner specific (sender/receiver/standard/version combination).

HTH,
RMG

HI, I am trying to add the attribute @system type XSL information below the @version to the XML. I am just wondering Do I need to use any standard bulit in services or Do I need to hard code the value. Actually I did hard code and it is not getting generated. Could anyone please advise. Thanks, Capri_lak.

Did you created the XML doc structure using DTD? It will create those elements for you and can hardcode it. Alternative is use replace service and replace the starting tags that you want with.

for example:

HTH,
RMG

The only way to change the XML declaration (the <?xml…> line) or to add processing instructions (the <?xml-stylesheet…> line) is to create the lines in your service and concatenate them with the XML document string. Specify false for the addHeader parameter of the documentToXMLString service call.

You can hardcode the steps to create the desired prologue (the declaration and processing instructions) or you could use some sort of configuration file or DB record and read the strings from there.

I believe he is actually looking for adding attributes @SYSTEM not the xml tag version portion (addHeader=true) etc…

Hi RMG, Exactly I am looking to add attributes @SYSTEM not xml tag version portion. I am just wondering how and which replace services(mentioned in the early post) I do need to use achieve the desired output. Could you please advise. Thanks, Capri_lak.

How exactly you want that tag/attributes to be appeared? Do you have the hardcoded values to put?

Is it similar that you are looking for

In the Replace service: set the

searchString <?xml version="1.0"?>
replaceString <?xml version="1.0"?>

Hope you got it now…

HTH,
RMG

Hi RMG, Thank you very much. It worked…I really appreciate all your help. Thanks, Capri_lak.

SYSTEM is associated with the DOCTYPE [strike]processing instruction[/strike] declaration. Since the post mentioned XSL I assumed the desired result was to get the xml-stylesheet processing instruction placed into the prolog:

[/font]<?xml-stylesheet href="example2.xsl" type="text/xsl" ?>

As opposed to:

[/font]

In either case, if these lines are desired at the top of an XML document they need to be generated by FLOW steps and then that string concatenated with the resulting XML document string.

[Edit]: Or a replace step can also do the trick, as rmg suggests.

Agreed with you Rob…generated by FLOW steps (should be created those doctypes from DTD) is the better solution and force replace is just a quick alternative as long it works…

Hi, we created the IS document types and did all the mapping.As a part of new requirement business team is asking me to change(rename) the Header in this e.g. I used now they want to replace it with . But when I went to the original Document type and renamed it didn’t work meaning, it has been renamed to partnernameInvoice but it came as a new document in the Original document type as all the mappings have been done under Invoice document in the Main document type. If that is the case, I am just wondering DO I need to all the mapping all the way from scratch which is going to be weeks of work.We are using IS 6.5 SP3 version.Could anyone please advise. we are kind of little bit concerned as we already have some partners in production which I am wondering Do I need to do all the mapping again? Thanks, Capri_lak.

Refactoring things in Developer is very limited. Indeed, it really only supports renaming services reasonably.

Renaming fields in a document type is to be avoided. If it is an arbitrary change (I sincerely doubt it is a “requirement”) then I’d offer that you can easily convince them that redoing all the mappings is more risk/work than the change is worth.

If you already have partners in production using this document type and naming, then such a change would really need some serious justification.

You could use search and replace using a text editor to modify the flow.xml files–but this can be risky too.

Another option to consider is instead of changing the name of the root element, add an attribute to the root. becomes . Perhaps that would fulfill the desire?

[Edit] Forgot to suggest: you should create new threads for new topics instead of covering multiple topics in a single thread.

[Edit] Forgot to suggest: you should create new threads for new topics instead of covering multiple topics in a single thread. → You got my words Rob…:).I was about to say on the same…! as this thread already growing 7 pages now…

Chandra,Please create new thread for diff topics…

HTH,
RMg