绑定文件中的BizTalk SOAP端口密码 [英] BizTalk SOAP port password in binding file

查看:66
本文介绍了绑定文件中的BizTalk SOAP端口密码的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我继承了一个BizTalk 2006应用程序,该应用程序使用多个SOAP端口从第三方Web服务请求数据. Web服务由基本"身份验证(用户名/密码)保护.在对应用程序进行了一些增强之后,我将其部署到了可以访问第三方Web服务的集成测试服务器上. BizTalk应用程序无法检索数据,我很快意识到我忘记了在SOAP发送端口上设置用户名/密码.我希望BizTalk应用程序的make部署尽可能自动化,因为将它部署到实时服务器时可能不存在.我打开了绑定文件,找到了问题SOAP发送端口的第1个,并寻找BizTalk用来替换密码的 *-除非它没有!似乎SOAP端口的密码设置为NULL而不是* ,有关更多详细信息,请参见此处: http://msdn.microsoft.com/en-us/library/aa547319. aspx

I've inherited a BizTalk 2006 application that uses several SOAP ports to request data from a 3rd party web service. The web service is secured by "basic" authentication - username / password. After making a few enhancements to the application I deployed to an integration test server which has access to the 3rd party web service. The BizTalk app was unable to retrieve the data and I soon realised that I had forgotten to set the username / password on the SOAP send ports. I wanted the make deployment of the BizTalk app as automated as possible because I may not be present when it is deployed to the live server. I opened up the binding file, located the 1st of the problem SOAP send ports and looked for the * that BizTalk uses to replace the password - except that it doesn't! It seems that the password for SOAP ports is set to NULL rather than *, see here for more details: http://msdn.microsoft.com/en-us/library/aa547319.aspx

我继续更新绑定,但是当我进行测试时,在导入修改后的绑定文件后,我发现与以前一样存在同样的问题.我已经仔细检查过,可以确认绑定文件中现在存在正确的密码,但是,尽管BizTalk在导入过程中没有抱怨,但是当我运行该应用程序时,出现了以下异常:

I proceeded to update the binding but when I came to test, after importing my amended binding file, I found that I had the same problem as before. I've double checked and can confirm that the correct password is now present in the binding file but, although BizTalk doesn't complain during the import, when I run the app I get the following exception:

详细信息:"ArgumentNullException:字符串引用未设置为String的实例. 参数名称:s .

Details:"ArgumentNullException: String reference not set to an instance of a String. Parameter name: s ".

如果我随后通过BizTalk管理控制台手动修改密码,则一切正常.

If I then manually amend the password through the BizTalk admin console everything work fine.

对于SOAP端口的绑定,还有其他人有类似的问题吗?有人有解决方案吗?

Has anyone else had a similar problem with the bindings for a SOAP port - does anyone have a solution?

推荐答案

过去,我一直对这样的事情感到厌烦.密码输入为"****".还行吧.我不希望将我的所有机密信息与绑定文件一起导出.当您导出绑定并留下密码NULL时,会得到什么.密码的XML元素上的变量类型(vt)属性设置为vt ="1",与NULL相同.输入密码的内容无关紧要.它甚至可能导致您描述的错误.我建议您包括绑定XML的副本以供审核.

I've been bit by something like this in the past. The password is either put in as '****'. This is ok. I wouldn't want all of my secrets exported with the binding file. What does get you is when you export the bindings and you leave the password NULL. The Variable Type (vt) attribute on the XML element for the password is set to vt="1" which is the same as NULL. It won't matter what you put in for the password. It may even cause the error you described. I would suggest you include a copy of the binding XML for review.

这篇关于绑定文件中的BizTalk SOAP端口密码的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆