[lgilmont]

HI all,

We've got a partner that send files to us via AS2. This is working okay. Now it seems that the file is always named "AS2". Our flows depend on the origin file name for us being able to know what we have to do with it.

I've checked doc and this is not clear either this is an option that needs to be setup on our side or on the remote partner?

We're using XSR with Gateway 6.11.4 sp5

Thanks for your help.

[Mario128]

Hello,
AS2 is the protocol file name, the original file name sent is known by Gateway only when the file has been completely unpackaged.
If you use the variable &(file_name) into your application you will get AS2 for the packaged file, indeed the file has not been unpackaged yet.
If you use the variable &(file_name) into your local AS2 Trading Partner ( advanced ) you will also get AS2 for the same reason.

To get the original file name there are two ways:

- The first one is to create a decision rule for Incoming AS2 transfer with ended status
This decision rule calls a script which rename the unpackeged file using the environment variable: x_file_name
( refer to the sample xpr.sh|bat into run_time/etc to get all the variable available from a script )
When the batch is called the file has been completely unpackaged and the transfer has been updated into the mailbox then x_file_name is now the
original file name

- The second way is to use an additional CGI parameter into the AS2 POST Request sent by your partner
Ask your partner to set with the original file name the CGI parameter: "filename"
Then Gateway will use this one instead of the default AS2 name and you will be able to use &(file_name ) into your Local Trading partner
If your partner is also using Gateway he has to add to peltrans command the parameter : -ftpc "filename=OriginalName"

Hope that will help you

Raphaël

[lgilmont]

Dear,

Thanks for the information.

I've tried option one and I still stick to "AS2" name!?

Now I've looked at the file created in tmp directory and in the header I do not retrieve any reference on the file name then I suppose if not present, it could be difficult to get it.

I've send a request to the remote party to see if they could provide this info. But definitively their tool isn't Gateway! But it is Drummong certified. Looking at their website, they talk about file name preservation, and their tool is listed there like the one from Axway. Then I suppose it could be somehow possible to include this.

Still thanks for your help.

Regards.

[Mario128]

Hi,
If you still have AS2 as file name into your mailbox :
- Try to apply the last service pack i remember that in the past there was an issue with AS2 file name not updated
or
- Your partner realy send AS2 as file name ..

Raphael

[lgilmont]

Dear,

Thanks again for the info;

I've updated Gateway to 6.11.4-SP5 Patch 18 and retried with my Partner, no cigar still "AS2".

I've seen that SP6 has been released but not sure on to istall it because I doubt it will help. On my partner side, they currently check their config.

Cross fingers and hope they wil lbe able to transmit this!

Thx.

[oue]

I suggest, you better have a master process id for all the inbound being received. Then you have to use CR_CopyMsg in Dynamic Processing in the process steps. And then you'll route it to different process IDs that corresponds to your need. Of course you need to make sure you have a unique values for the reference that will satisfy your criteria.

[lgilmont]

Thanks for your suggestion but

Currently we have a leased line on which we receive EDI files, sometimes we receive as well reports which are zipped. With the filename, it is easy to perform the routing.

Now we would like to replace this by Gateway. With what I see I would have to decide the filename by myself, the problem is how I could differenciate the file types and do a proper routing. Only solution I see is to have different mailbox by type of incoming file. I see it quite difficult to maintain at the end.

Thanks.

[kpolicoff]

I don't believe that the name of the file is actually part of the Drummond Group's EDIINT AS2 specification. The sending application does not have to provide a file name. That might be the case here. It's being called "AS2" because that's the directory in which the file is most likely being delivered (well, VFD or RFD anyway), and if there's no file name provided by the sender, we have to call it something. I might check with your partner to find out what application they're using to send, and see if they actually have their software setup to provide those details. Being that the file is encrypted as well as some of the AS2 headers, it's going to be difficult if not impossible to see that tag in the header. A file with encryption turned off might provide physical proof of whether or not they're actually sending the filename. If you're really curious and want to play around with the application to get a better understanding of what's happening, you could send an encrypted file and an unencrypted file to a partner, and then take a look at those AS2 headers to see how the filename is sent. Sure, it's going the opposite direction, but at least you can see the headers and know what you're looking for when something comes in (as well as what info you can't see when encryption is enabled). Sounds like a fun test, huh? Well, I think it does

Kevin Policoff
Axway Global Support