Forum Replies Created
-
AuthorPosts
-
As long as the web service is functionally the same, you just need to modify the Url in the send port.
You can do this using the admin console or by importing a binding file.This is a common scenario, where a test web service is used in dev/test while the production web service is only used in the production environment.
You can have multiple binding files, one per environment. You can deploy all binding files using a Target environment name. You can then export all binding files into an MSI for deployment. As part of the MSI import you will be prompted for the target environment name and the appropriate binding file will be deployed.
Hi Daniel.
Thanks a lot, this helps my further.
It is nice to see that are thrid party products available on the market.
Thanks
Wolfgang
This will depend on where you are when you need to access the properties. If you’re inside a WCF service that received a message from BizTalk, I don’t believe that context data is carried over. However, with an orchestration inside BizTalk, you can access the value of promoted properties in an expression shape using the Message(PropertyName) syntax. You can also use a message assignment to set the value of the properties.
If you are interested in moving data from context into the message, you may want to look at “Property Demotion”.
Here’s an article from Stephen Thomas on how to do it:
Although the article was written for BTS 2004/2006, it still applies to BTS 2009
July 16, 2010 at 1:11 PM in reply to: Tracking Profile Editor is not enumerated the database names #25270Hi,
Go through the following MSDN blog to see if it provides the solution to your problem:
http://blogs.msdn.com/b/vtyagi/archive/2006/02/23/tracking-profile-editor-error-messages.aspx
Cheers,
Daniel.
I posted this problem on the MSDN forums as well. Someone there suggested the following:
You can set the DOCTYPE from the grid properties of a map. I suggest you create a map to construct above message and set the below property in Grid properties.
Doctype System = http://xml.cXML.org/schemas/cXML/1.2.021/cXML.dtd
This was a great suggestion, however I unfortunately had the following issues with the approach:
1) There isn’t a source message to transform in this process
2) I hate the Biztalk mapper because it has unpredictable behavior such as including optional attributes, etc.In any case it was the best idea I had and in some simple tests with the BizTalk mapper the idea of using the DocType System property worked well. The resulting XML in testing the map does not include the [] brackets in the DOCTYPE declaration. Due to this I decided to take the idea and run with it. Since I knew just using the BizTalk mapper verbatim was going to result in some wacky output XML, I created a custom XSLT transform. My process also requires a call to an external assembly, so I created custom extension XML, so I could call the assembly in my XSLT. The resulting XSLT was as follows:
<?xml version=”1.0″ encoding=”UTF-8″?>
<xsl:stylesheet xmlns:xsl=”http://www.w3.org/1999/XSL/Transform” xmlns:msxsl=”urn:schemas-microsoft-com:xslt” xmlns:var=”http://schemas.microsoft.com/BizTalk/2003/var” exclude-result-prefixes=”msxsl var ScriptNS0 userCSharp” version=”1.0″ xmlns:ScriptNS0=”http://schemas.microsoft.com/BizTalk/2003/ScriptNS0″ xmlns:userCSharp=”http://schemas.microsoft.com/BizTalk/2003/userCSharp”>
<xsl:output omit-xml-declaration=”no” method=”xml” version=”1.0″ doctype-system=”http://xml.cXML.org/schemas/cXML/1.2.021/cXML.dtd” />
<xsl:template match=”/”>
<xsl:variable name=”var:PayLoadID” xmlns:ariba=”http://AribaHelper” select=”ariba:PayloadID("dev.service.fabio-perini.com")” />
<xsl:variable name=”var:DateTime” select=”userCSharp:DateCurrentDateTime()” />
<cXML>
<xsl:attribute name=”payloadID”>
<xsl:value-of select=”$var:PayLoadID” />
</xsl:attribute>
<xsl:attribute name=”timestamp”>
<xsl:value-of select=”$var:DateTime” />
</xsl:attribute>
<xsl:attribute name=”xml:lang”>
<xsl:value-of select=”‘en-us'”/>
</xsl:attribute>
<Response>
<Status>
<xsl:attribute name=”code”>
<xsl:value-of select=”‘200′”/>
</xsl:attribute>
<xsl:attribute name=”text”>
<xsl:value-of select=”‘OK'”/>
</xsl:attribute>
</Status>
</Response>
</cXML>
</xsl:template>
<msxsl:script language=”C#” implements-prefix=”userCSharp”>
<![CDATA[
public string DateCurrentDateTime()
{
DateTime dt = DateTime.Now;
string curdate = dt.ToString(“yyyy-MM-dd”, System.Globalization.CultureInfo.InvariantCulture);
string curtime = dt.ToString(“T”, System.Globalization.CultureInfo.InvariantCulture);
string retval = curdate + “T” + curtime;
return retval;
}]]></msxsl:script>
</xsl:stylesheet>When I tested the map, I got the perfect response! Here is what my test outputted:
<?xml version=”1.0″ encoding=”utf-8″?>
<!DOCTYPE cXML SYSTEM “http://xml.cXML.org/schemas/cXML/1.2.021/cXML.dtd”>
<cXML payloadID=”[email protected]” timestamp=”2010-07-16T10:34:15″ xml:lang=”en-us”>
<Response>
<Status code=”200″ text=”OK”/>
</Response>
</cXML>At this point the idea in my mind was a genius and while the approach was a bit unconventional it got the job done and I was happy. Then I tested it in a running application. Keep in mind my BizTalk application uses a HTTP two-way receive port. If a valid document is posted in, the above code is what should be in the GET response. Guess what I got back out in the GET response? This:
<?xml version=”1.0″ encoding=”utf-8″?>
<!DOCTYPE cXML SYSTEM “http://xml.cXML.org/schemas/cXML/1.2.021/cXML.dtd”%5B%5D>
<cXML payloadID=”[email protected]” timestamp=”2010-07-16T10:37:37″ xml:lang=”en-us”>
<Response>
<Status code=”200″ text=”OK”/>
</Response>
</cXML>The double brackets came back! It would appear that somewhere in the BTSHTTPReceive.dll assembly this problem is occurring! So I was targeting the wrong point in the process where the problem was introduced. I have NO idea how to control the behavior of the BTSHTTPReceive.dll assembly at all.
I posted this problem on the MSDN forums as well. Someone there suggested the following:
You can set the DOCTYPE from the grid properties of a map. I suggest you create a map to construct above message and set the below property in Grid properties.
Doctype System = http://xml.cXML.org/schemas/cXML/1.2.021/cXML.dtd
This was a great suggestion, however I unfortunately had the following issues with the approach:
1) There isn’t a source message to transform in this process
2) I hate the Biztalk mapper because it has unpredictable behavior such as including optional attributes, etc.In any case it was the best idea I had and in some simple tests with the BizTalk mapper the idea of using the DocType System property worked well. The resulting XML in testing the map does not include the [] brackets in the DOCTYPE declaration. Due to this I decided to take the idea and run with it. Since I knew just using the BizTalk mapper verbatim was going to result in some wacky output XML, I created a custom XSLT transform. My process also requires a call to an external assembly, so I created custom extension XML, so I could call the assembly in my XSLT. The resulting XSLT was as follows:
<?xml version=”1.0″ encoding=”UTF-8″?>
<xsl:stylesheet xmlns:xsl=”http://www.w3.org/1999/XSL/Transform” xmlns:msxsl=”urn:schemas-microsoft-com:xslt” xmlns:var=”http://schemas.microsoft.com/BizTalk/2003/var” exclude-result-prefixes=”msxsl var ScriptNS0 userCSharp” version=”1.0″ xmlns:ScriptNS0=”http://schemas.microsoft.com/BizTalk/2003/ScriptNS0″ xmlns:userCSharp=”http://schemas.microsoft.com/BizTalk/2003/userCSharp”>
<xsl:output omit-xml-declaration=”no” method=”xml” version=”1.0″ doctype-system=”http://xml.cXML.org/schemas/cXML/1.2.021/cXML.dtd” />
<xsl:template match=”/”>
<xsl:variable name=”var:PayLoadID” xmlns:ariba=”http://AribaHelper” select=”ariba:PayloadID("dev.service.fabio-perini.com")” />
<xsl:variable name=”var:DateTime” select=”userCSharp:DateCurrentDateTime()” />
<cXML>
<xsl:attribute name=”payloadID”>
<xsl:value-of select=”$var:PayLoadID” />
</xsl:attribute>
<xsl:attribute name=”timestamp”>
<xsl:value-of select=”$var:DateTime” />
</xsl:attribute>
<xsl:attribute name=”xml:lang”>
<xsl:value-of select=”‘en-us'”/>
</xsl:attribute>
<Response>
<Status>
<xsl:attribute name=”code”>
<xsl:value-of select=”‘200′”/>
</xsl:attribute>
<xsl:attribute name=”text”>
<xsl:value-of select=”‘OK'”/>
</xsl:attribute>
</Status>
</Response>
</cXML>
</xsl:template>
<msxsl:script language=”C#” implements-prefix=”userCSharp”>
<![CDATA[
public string DateCurrentDateTime()
{
DateTime dt = DateTime.Now;
string curdate = dt.ToString(“yyyy-MM-dd”, System.Globalization.CultureInfo.InvariantCulture);
string curtime = dt.ToString(“T”, System.Globalization.CultureInfo.InvariantCulture);
string retval = curdate + “T” + curtime;
return retval;
}]]></msxsl:script>
</xsl:stylesheet>When I tested the map, I got the perfect response! Here is what my test ouputted:
<?xml version=”1.0″ encoding=”utf-8″?>
<!DOCTYPE cXML SYSTEM “http://xml.cXML.org/schemas/cXML/1.2.021/cXML.dtd”>
<cXML payloadID=”[email protected]” timestamp=”2010-07-16T10:34:15″ xml:lang=”en-us”>
<Response>
<Status code=”200″ text=”OK”/>
</Response>
</cXML>At this point the idea in my mind was a genius and while the approach was a bit unconventional it got the job done and I was happy. Then I tested it in a running application. Keep in mind my BizTalk application uses a HTTP two-way receive port. If a valid document is posted in, the above code is what should be in the GET response. Guess what I got back out in the GET response? This:
<?xml version=”1.0″ encoding=”utf-8″?>
<!DOCTYPE cXML SYSTEM “http://xml.cXML.org/schemas/cXML/1.2.021/cXML.dtd”%5B%5D>
<cXML payloadID=”[email protected]” timestamp=”2010-07-16T10:37:37″ xml:lang=”en-us”>
<Response>
<Status code=”200″ text=”OK”/>
</Response>
</cXML>The double brackets came back! It would appear that somewhere in the BTSHTTPReceive.dll assembly this problem is occurring! So I was targeting the wrong point in the process where the problem was introduced. I have NO idea how to control the behavior of the BTSHTTPReceive.dll assembly at all.
By the way…this problem is with BizTalk 2009 Server.
Hi Wolfgang,
To the best of my knowledge, here are some answers to your questions:
1. You would have to create your own custom pipeline component to archive your XML file without using a Send port, or you can use a third-party component (to save you time and energy) as advertised in the following website:
2. The message does not get removed automatically from the MessageBox database after the Orchestration finishes running, but BizTalk has SQL agent jobs that would periodically clean up message box and tracking databases in production. If you need to clean up the message box database in development environment, read the following blog for more information (btw, this is not recommended for production environments):
http://blogs.msdn.com/b/biztalk_core_engine/archive/2005/03/09/390996.aspx
Hope this helps,
Daniel.
Let me guess – you’re running a 64-bit version of Windows, right?
The LOB Adapters are 32-bit only, so their registry settings are in the 32-bit area of the registry (under the Wow6432Node).
So the node you want is: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\BizTalkAdapters
The node you want to set permissions on is: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\BizTalkAdapters\Config
Cheers,
Dourn
July 16, 2010 at 3:00 AM in reply to: How to send a file from one system to another in Biztalk 2009 #25265Hi.
Have a look in that post: http://www.biztalkgurus.com/forums/t/14992.aspx
Perhaps it will go further on.
July 16, 2010 at 2:43 AM in reply to: Code promotion from dev to test. I am facing this problem, please help #25263Hi.
Are the same tools and version installed on the dev and test servers?
How did you deployed your BTS App to the test environment?
Did you use the im- and export functions out of BTS?
Did you deployed the app in Visual Studio directly in the test environment or just copied the assembly in the GAC?
Can you validate the schemas in the test environment with Visual Studio?
Best regards
Wolfgang
Thank you very much for
your replies, I have served enoughIf you want to migrate to Windows 2003, then upgrade your BizTalk installation to either version 2004, 2006 or 2006 R2.
Thank you, and if I want
to migrate to Windows 2003, Biztalk 2000 will have any problems or be
the same case as Windows 2008?July 15, 2010 at 1:53 PM in reply to: How to send and recieve file/data from the one location to another using http adapter #25256[quote user="Anonymous"]
Hi
I want to use http adapter to send and recieve the file/data from the one location to another in Biztalk 2009.
Please tell me which steps I have to follow.
[/quote]
What are the 2 locations? File folders, FTP, HTTP, SharePoint, WCF, MQ, SQL, Oracle, etc?
July 15, 2010 at 12:03 PM in reply to: Importing msi without bindings – deletes password in send port #25255In what way are these related? I would like to flag this somehow as spam unless there is a reason for linking this here. Otherwise, if this is useful in its own right, why not create it’s own thread?
-
AuthorPosts