UDL Problem

Question

I have recently installed a new devleopment environment with BizTalk 2009 and the adapter for host systems.  I created my datasource UDLs in the data access tool which successfully tested the connection and queried the source.  When trying to configure a send port using DB2 and the generated UDL, I receive the error "value is of wrong type" when clicking finish.  If I create a new connection string within the send port create, it tests out successfully until I click ok to finish and I receive "The connection string is not defined or contains invalid properties"

User ID=utsme02;Initial Catalog=SFBCDBTT;Network Transport Library=TCP;Host CCSID=37;PC Code Page=1252;Network Address=10.193.**.**;Network Port=5060;Package Collection=NULLID;Process Binary as Character=False;Connect Timeout=15;Units of Work=RUW;DBMS Platform=DB2/MVS;Defer Prepare=False;Rowset Cache Size=0;Max Pool Size=100;Database Name=DBTT;Authentication=Server;Persist Security Info=False;Connection Pooling=True;Derive Parameters=True;




Any ideas?  Thanks in advance.

Answer 1

Is the value NULLID an acceptable value or is this incorrect?

Thanks,

---

If this answers your question, please use the "Answer" button to say so | Ben Cline

Answer 2

Yes, nullid is just the package collection name in db2, which is valid.

Answer 3

Hi Stacey,

I would suggest that you have a look through the following white papers to
see if you can use the format of the sample connections strings in the
papers to resolve the problem:

Setting Up the BizTalk Adapter for DB2 Using Receive Ports
http://www.microsoft.com/downloads/details.aspx?FamilyID=A08D1FA7-6B3D-4B9C-BCE2-38F40D36DAA9&displaylang=en

Setting Up the BizTalk Adapter for DB2 Using Send Ports
http://www.microsoft.com/downloads/details.aspx?familyid=0A98A3E5-5D95-4F94-99AA-CE185862B3EE&displaylang=en

See similar post: http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.hiserver.general&tid=70676bce-2f88-4e08-8469-dae8871d68ef&cat=&lang=&cr=&sloc=&p=1

---

Sandro Pereira - http://sandroasp.spaces.live.com/blog/ http://www.devscope.net/WhatWeDo/Integration/tabid/107/Default.aspx

Answer 4

Resolved this issue by removing database name from connection string.