Sadly, it appears that the BIE project is now dead and gone. The sourceforge project has been deleted, and so the mailing list is also gone. The BIE GPL site is also gone. So it appears the slate has been swept clean and Open Source has lost a truly one-of-a-kind solution. Shame upon the new owner, or un-owner, of the BIE code for this train wreck.

BIE's legal limbo appears to be finally drawing to a close. Mr. Fruetel has posted to the bie-developer list that the BIE product has been sold by Brunswick and that the new owner is interested in seeing the project go forward. I hope to be able to post more good news soon. You can see Mr. Fruetel's message in the rest of this story.

BIE users and their passwords are stored in the USERS table of the internal Hypersonic database. If you happen to end up with an account that is locked out of BIE because they forgot their password or tried the wrong time too many times you can reset their status and password by modifying the database.

You can use the "Assign" action in BIE to retreive the contents of an element or attribute of an XML document (or "message" in BIE-speak). But if you try to retrieve the value of an element in a document like -


<root attribute="value"><parameter name="id">1</parameter></root>


- via the obvious XPath of "/root/@attribute" you will get a "BIE INTERNAL ERROR". The workaround is to do something like this: "concat(/root/@attribute, '')".

An SCP action plugin as been announced for the Business Integration Engine. You can download this plugin here at the BIE website or here from this site. With an SCP action you can read a message from a remote file or write the contents of a message to a remove file via the SCP protocol. The SCP action supports password, keyboard interactive, and public-key authentication.

Within BIE is an internal Hypersonic database that contains configuration, state, and audit information. The actual messages and data used by workflows is stored in an internal eXist database. It is occasionally useful to access the internal Hypersonic database to perform maintenance or correct an error; fortunately BIE contains an embedded GUI Hypersonic client.

This is a copy of an e-mail from the BIE mailling list. It describes how to setup a route that cleans old data from BIE's internal Hypersonic database. Hypersonic has issues with very large record sets and long transactions so keeping this database small really helps BIE's stability and performance.

This page is an index of information, work, and downloads relating to BIE (the Business Integration Engine).