Home > Healthcare Integration > DB Filter versus DB Communication Point

DB Filter versus DB Communication Point

The DB Filter implements the same functionality as the DB communication point in Out -> In mode. Therefore, it allows an interface to be developed without the financial cost associated with a communication point if your license is based on the number of communication points. As far as I can tell this is the only value that this filter brings and it does so at a high cost. That cost is that messages continue to process on the route the filter is used on even when the filter cannot connect to the database it is using. This may be okay in some cases where a default value allows messages to be valid but those are rare.

Converting to and from a DB filter and communication point is easy since you can copy the configuration file contents between them. So I would recommend if financial feasible that only DB communication points be used.

  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: