When using the connection manager, we don't see DB2 as a data source type option. Is there a reason why it is not showing? If the connection manager is not the way to set up a DB2 connection, what is the recommended approach? Thanks!

I am 99% sure you have no manually provide the connection string via DB2DataSourceItem, at least that is how I do it.



Here is some code that I know works.



connStr = "Database=YOURDB2NAME;User ID=USERNAME;Password=PASSWORD;Server=xxx.xxx.xxx.xxx:446"

DataLayer.DataSources.Add(New Db2DataSourceItem("", connStr, System.Data.Common.DbProviderFactories.GetFactory("IBM.Data.DB2")))

Keith Chisarik

DB2 is not a standard or included product in the framework.  As such, the framework does not rely on its existence.  The Connection String Wizard does not have the DB2 support as it has been our experience that most developers have another mechanism that they want to use for retrieving the connection information and end up providing the connection information manually as Keith had pointed out.

That worries me. The StrataFrame framework supporting DB2 at the same level and in the same manner as other supported databases is essential for us, if it doesn't it is pretty much useless to us. I am pretty sure I remember my manager saying we had specificly requested support for DB2 to be added to the framework before we bought the licenses. I'll have to check with him on that.

I am pretty sure it is supported.



At least I hope so, I have about a year worth of work to do for my two biggest clients using DB2 (for better or worse).



Trent and SF know this and would not have let anyone move forward in a non-supported environment.



I am sure he will clarify.




Keith Chisarik

Marco,

You have taken my comments way out of context!  At present we only have two customers using the DB2 provider, you and Keith.  As I mentioned in my previous post, it is not included in the standard StrataFrame release like some of the other data providers (i.e. SQL Server, Oracle, etc.). 

You mentioned that you were concerned of our supporting the DB2 provider.  It is our commitement and desire to FULLY support the DB2 provider.  Anytime that you or Keith have ever run into an issue we have addressed and corrected it immediately.  This is the same approach that we stive for anytime that any type of bug or issue is reported. 

All I was trying to relay in my previous post is that since the DB2 provider is not included in the standard release for all customers, the Connection String Manager does not currently have a dialog allowing the DB2 connections to be specified through the wizard.  The framework supports every other facet of the DB2 provider.  We have customers using other databases that the Connection Wizard does not support as well...for example SQL Anywhere.

Additionally the reason the DB2 provider is not in the standard framework release is because we want it to go through a full application cycle before we release it to the world at large.

Sorry for any confusion that my post may have caused.  We appreciate your business!

Thanks. I already hoped that DB2 would be supported, but you did have me worried there for a second

The minor pain is that we currently have to put two different approaches out to our development teams (and many of our programmers can work on a number of projects that include a number of different database, it's fun ) for managing connections. That is what basically raised this question: a new developer that had seen the use of the connection manager for a MS SQL database and wanted to follow the same approach for a DB2 database, which seemed reasonable. We'll wrap some custom classes around it to make it a little easier to manage and we'll be looking forward to the release that incorporates DB2 into the connection manager