Introducing the all-new TIBCO Community site!

For current users, please click "Sign In" to reset your password and access the enhanced features. If you're a first-time visitor, we extend a warm welcome—click "Sign Up" to become a part of the TIBCO Community!

If you're seeking alternative community sites, explore ibi, Jaspersoft, and Spotfire.

Jump to content

This is reg.parsing incoming file in TIBCO BW. How can we parse any incoming file without knowing the delimiter in Businessworks. In Data format palette there is a field Column Separator should be mentioned when we use Parse data palette

Recommended Posts

Thanks for the reply. I have an incoming file with user data which contains user details like userid, username, userstatus etc. User fields are separated with either , or & or | etc in file. We do not know the separator that client is sending in the file. In this case how can we parse data in TIBCO BW 5.x/6.x. In the Data Format palette, without knowing the delimiter how can we achieve?. Thanks again

Link to comment
Share on other sites

Hi Sucharitha, not 100% I follow, but in your situation what I'll do is the following:

  • Still use ParseData as it is the best way to process "big files" of delimited records (unless you have also the option to Plug-in for Files)
  • In the Data Format Resource use n as the col separator, so you will have after the ParseData an array of "lines".
  • Use in the Mapper activity the "tokenize" function with the proper symbol you need for each record after "discovering which one is use in that record"

To simplify the explanation I'm attaching a dummy app that is able to transform the following file:





In to the following XML:

<tns1:elementList xmlns:tns1=""























Hopefully this is similar to what you're looking to achieve! Let me know if I understood it wrong.


Link to comment
Share on other sites

Thank you. Client requirement is we get couple of files in the attached format, but the separator/Delimiter may vary. There could be unknown separator added into the file by customer. Expectation is generic logic should be implemented from our end to process/parse all the files without knowing the separator character. Thanks

Link to comment
Share on other sites

I'm reading the file you attach and I think solution provided is valid, you just need to include "all possible delimiters" to the choose logic. There is no way to detect magically the delimiter in any technology as it needs to be extracted based on some logic. Some thing could be to detect it in the header line if the field names are the same. If not, the only way is to have some logic to extract it. In my sample this is just a "contains" but it can be as complex as you need. Hope that helps!

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...