Forum Replies Created
-
AuthorPosts
-
March 22, 2009 at 9:30 PM in reply to: Performance issue – receiving IDOC’s from SAP to BizTalk #21947
The issue has been resolved.
If anyone is interested, find more details on MSDN forum:
http://social.msdn.microsoft.com/Forums/en-US/biztalkr2adapters/thread/6d772f86-19a9-42d4-b78c-df4bf675b416ok I resolved this.. Apparently the empty element doesn’t matter and the flat file assembler will honor the default value. Hey now that we’re on teh subject, is there a way to test pipelines/assemblers without having to deploy to a test application? I find it time consuming to remap my pipelines to my schema and then have to update the build numbers.. perhaps I’m doing something wrong? thanks again.
hey there,
Thanks for replying.
ya, I set the default values to ” ” in the xsd and then set the value property in the General section of the mapper file to be ” “. When I try to test the map the output elements are closed tags, like “<Remittance_Msg />”. Should I attempt to deploy this and see if that makes a difference? Is there something that I’m missing?
thanks again.
Eric
Have you tried setting the default value of your destination schema fields at the mapper file??
March 19, 2009 at 7:27 PM in reply to: How if I need to run a SQL statement to compose a message? #21937Er, I can’t user the “Database lookup” functoid, cuz my SQL statement is a bit complicated…
Please check that the account you are using has remote access enabled.
March 19, 2009 at 6:02 AM in reply to: Performance issue – receiving IDOC’s from SAP to BizTalk #21932This is a known issue. Nothing can be done about it, as this is the way SAP behaves, it never sends out IDOCS to a given RFC destination in parallel, however, if there are multiple destinatons for the same ProgramID, then IDOC are sent in round-robin fahion. One work around will be to have large number of receive locations for the given receive port.
Ok, I think I figured it out. It’s the custom fact retriever that both sets the database connection and retrieves the data, inserting the Microsoft.RuleEngine.DataConnection object into the rule engine.
Here is some of the code from the MyFactRetriever. I finally read more books, and figured out that the fact retriever is specified as a property on the Policy/version. I was having trouble before, because I couldn’t really see where the FactRetriever was used or called.
SqlConnection con1 = new SqlConnection(“Initial Catalog=Northwind;Data Source=(local);Integrated Security=SSPI;”);
DataConnection dc1 = new DataConnection(“Northwind”, “CustInfo”, con1);
engine.Assert(dc1);// I added the next two lines of code so that my new table would be “asserted”
// (My new table name = BusinessRuleParms)DataConnection dc2 = new DataConnection(“Northwind”, “BusinessRuleParms”, con1);
engine.Assert(dc2);Neal
March 17, 2009 at 7:11 AM in reply to: Newbie – Copying the raw receive file to another location before orchestration #21928Could you clarify what you are trying to do on the send of this file? Are you needing to send the file to both a location on your “domain” which I assume is your local network as well as FTP it somewhere remotely? Also, you are speaking of needing the file to be written to the “domain” before being sent via FTP, does the order matter, or do you just need to write the file to two seperate locations?
Looking at the code for Microsoft.XLANGs.Core.Part.GenericLoadFrom(Object source) it will throw a “Specified method not supported error” only if the source argument is a System.Xml.XmlNodeList with more than 1 XmlNode. This is called from Message_1 = xpath(SQLMessage, Variable_3);
I suspect the xpath function is returning more than one node. What is the HeaderInstance variable and how is it assigned?
Also, since I haven’t used database with rules, I’m confused about a few related items:
1) The sample (SDK\Business Rules\Loans Processing using Business Rules) has a c# project called “MyFactRetriever”. The setup deploys it, but I cannot see where it is actually used.
This page documents this module of the SDK, mentions that fact retriever, but again, doesn’t say how or where it is used.
http://msdn.microsoft.com/en-us/library/aa559727.aspx
2) I exported the policy file to BRL/xml file using the Deploy wizard so I can look at it.
I found this line:
<datarow ref=”db_33″ server=”BIZTALK-D3W3PVB\Northwind” dataset=”Northwind” table=”BusinessRuleParms” instances=”16″ selectivity=”1″ isdataconnection=”true” instance=”0″ />
So if I hard-codes my computer name as the database server, how does one switch to a different server when you migrate to QA or PROD machine?
Thanks,
Neal
First, you might move the Count to a different expression shape to isolate if it’s the statement bombing, or if it is the next xpath.
It might just be telling you that your Xpath was not found. You might need add namespaces, and use the long nasty form of the XPath, something like this:
/*[local-name()=’TEMS_SQL and namespace-uri()=’http://YourNamespace]/*%5Blocal-name()=’Record’ and namespace-uri()=’http://YourNamespace’%5D/*%5Blocal-name()=’SubRecord’ and namespace-uri()=’http://YourNamespace’%5D/*%5Blocal-name()=’SubReocrd’ and namespace-uri()=’http://YourNamespace’%5D
You can copy/paste the namespace from the properties in the schema. Did you build the schema, or was it auto-generated by SQL adapter or something like that?
See this blog: http://nealwalters.blogspot.com/2005_01_01_archive.html
Neal
Hi Thanks for the reply I am receiving a flatfile msg and after doing some mappings I am transforming that flatfile data into XML message and this XML msg has header,Line and Dist and I need to debatch those records into individual messages, like if there are 2 header records in a .txt file i should have 2 xml msgs for the header and for Line if there are 20 Line then i need to get 20 line messages and like wise to the Dist also so I am implementing the debatch mechanism from the Stephens. Thomas article but I am getting this error.
my schema is
TEMS_SQL>
<BUSINESS_UNIT>SN018</BUSINESS_UNIT><VCHR_BLD_KEY_C1>SN018</VCHR_BLD_KEY_C1><VCHR_BLD_KEY_N1>03162009</VCHR_BLD_KEY_N1><VCHR_BLD_KEY_N2>14:41:28</VCHR_BLD_KEY_N2><VOUCHER_ID>NEXT</VOUCHER_ID><VOUCHER_STYLE>REG</VOUCHER_STYLE><INVOICE_ID>404R285738738_08282008</INVOICE_ID><INVOICE_DT>20080828</INVOICE_DT><VENDOR_SETID>SHARE</VENDOR_SETID><VENDOR_ID>00539</VENDOR_ID><VNDR_LOC>HO1</VNDR_LOC><ADDRESS_SEQ_NUM>REG</ADDRESS_SEQ_NUM><ORIGIN>TEM</ORIGIN><OPRID>APBATCH</OPRID><ACCOUNTING_DT>03162009</ACCOUNTING_DT><GROSS_AMT>33566.39</GROSS_AMT><PYMNT_TERMS_CD>IMMED</PYMNT_TERMS_CD></Header><BUSINESS_UNIT>SN018</BUSINESS_UNIT><VCHR_BLD_KEY_C1>SN018</VCHR_BLD_KEY_C1><VCHR_BLD_KEY_N1>03162009</VCHR_BLD_KEY_N1><VCHR_BLD_KEY_N2>14:41:28</VCHR_BLD_KEY_N2><VOUCHER_ID>NEXT</VOUCHER_ID><VOUCHER_LINE_NUM>1</VOUCHER_LINE_NUM><DESCR /><MERCHANDISE_AMT>49.82</MERCHANDISE_AMT><WTHD_SW>N</WTHD_SW></LINE><BUSINESS_UNIT>SN018</BUSINESS_UNIT><VCHR_BLD_KEY_C1>SN018</VCHR_BLD_KEY_C1><VCHR_BLD_KEY_N1>03162009</VCHR_BLD_KEY_N1><VCHR_BLD_KEY_N2>14:41:28</VCHR_BLD_KEY_N2><VOUCHER_ID>NEXT</VOUCHER_ID><VOUCHER_LINE_NUM>2</VOUCHER_LINE_NUM><DESCR /><MERCHANDISE_AMT>192.19</MERCHANDISE_AMT><WTHD_SW>N</WTHD_SW></LINE><BUSINESS_UNIT>SN018</BUSINESS_UNIT><VCHR_BLD_KEY_C1>SN018</VCHR_BLD_KEY_C1><VCHR_BLD_KEY_N1>03162009</VCHR_BLD_KEY_N1><VCHR_BLD_KEY_N2>14:41:28</VCHR_BLD_KEY_N2><VOUCHER_ID>NEXT</VOUCHER_ID><VOUCHER_LINE_NUM>3</VOUCHER_LINE_NUM><DESCR /><MERCHANDISE_AMT>602.69</MERCHANDISE_AMT><WTHD_SW>N</WTHD_SW></LINE><BUSINESS_UNIT>SN018</BUSINESS_UNIT><VCHR_BLD_KEY_C1>SN018</VCHR_BLD_KEY_C1><VCHR_BLD_KEY_N1>03162009</VCHR_BLD_KEY_N1><VCHR_BLD_KEY_N2>14:41:28</VCHR_BLD_KEY_N2><VOUCHER_ID>NEXT</VOUCHER_ID><VOUCHER_LINE_NUM>4</VOUCHER_LINE_NUM><DESCR /><MERCHANDISE_AMT>237.68</MERCHANDISE_AMT><WTHD_SW>N</WTHD_SW></LINE><Dist><BUSINESS_UNIT>SN018</BUSINESS_UNIT><VCHR_BLD_KEY_C1>SN018</VCHR_BLD_KEY_C1><VCHR_BLD_KEY_N1>03162009</VCHR_BLD_KEY_N1><VCHR_BLD_KEY_N2>14:41:28</VCHR_BLD_KEY_N2><VOUCHER_ID>NEXT</VOUCHER_ID><VOUCHER_LINE_NUM>1</VOUCHER_LINE_NUM><DISTRIB_LINE_NUM>1</DISTRIB_LINE_NUM><BUSINESS_UNIT_GL>SN018</BUSINESS_UNIT_GL><QTY_VCHR>OPTIONAL</QTY_VCHR><MERCHANDISE_AMT>49.82</MERCHANDISE_AMT><PO_DIST_LINE_NUM>OPTIONAL</PO_DIST_LINE_NUM><ACCOUNT>911000</ACCOUNT><DEPTID>9000</DEPTID><CHARTFIELD1>TEM01100</CHARTFIELD1></Dist><BUSINESS_UNIT>SN018</BUSINESS_UNIT><VCHR_BLD_KEY_C1>SN018</VCHR_BLD_KEY_C1><VCHR_BLD_KEY_N1>03162009</VCHR_BLD_KEY_N1><VCHR_BLD_KEY_N2>14:41:28</VCHR_BLD_KEY_N2><VOUCHER_ID>NEXT</VOUCHER_ID><VOUCHER_LINE_NUM>2</VOUCHER_LINE_NUM><DISTRIB_LINE_NUM>2</DISTRIB_LINE_NUM><BUSINESS_UNIT_GL>SN008</BUSINESS_UNIT_GL><QTY_VCHR>OPTIONAL</QTY_VCHR><MERCHANDISE_AMT>192.19</MERCHANDISE_AMT><PO_DIST_LINE_NUM>OPTIONAL</PO_DIST_LINE_NUM><ACCOUNT>911000</ACCOUNT><DEPTID>9000</DEPTID><CHARTFIELD1>TEM01100</CHARTFIELD1></Dist><BUSINESS_UNIT>SN018</BUSINESS_UNIT><VCHR_BLD_KEY_C1>SN018</VCHR_BLD_KEY_C1><VCHR_BLD_KEY_N1>03162009</VCHR_BLD_KEY_N1><VCHR_BLD_KEY_N2>14:41:28</VCHR_BLD_KEY_N2><VOUCHER_ID>NEXT</VOUCHER_ID><VOUCHER_LINE_NUM>3</VOUCHER_LINE_NUM><DISTRIB_LINE_NUM>3</DISTRIB_LINE_NUM><BUSINESS_UNIT_GL>SN053</BUSINESS_UNIT_GL><QTY_VCHR>OPTIONAL</QTY_VCHR><MERCHANDISE_AMT>602.69</MERCHANDISE_AMT><PO_DIST_LINE_NUM>OPTIONAL</PO_DIST_LINE_NUM><ACCOUNT>911000</ACCOUNT><DEPTID>9000</DEPTID><CHARTFIELD1>TEM01100</CHARTFIELD1></Dist><BUSINESS_UNIT>SN018</BUSINESS_UNIT><VCHR_BLD_KEY_C1>SN018</VCHR_BLD_KEY_C1><VCHR_BLD_KEY_N1>03162009</VCHR_BLD_KEY_N1><VCHR_BLD_KEY_N2>14:41:28</VCHR_BLD_KEY_N2><VOUCHER_ID>NEXT</VOUCHER_ID><VOUCHER_LINE_NUM>4</VOUCHER_LINE_NUM><DISTRIB_LINE_NUM>4</DISTRIB_LINE_NUM><BUSINESS_UNIT_GL>SN008</BUSINESS_UNIT_GL><QTY_VCHR>OPTIONAL</QTY_VCHR><MERCHANDISE_AMT>237.68</MERCHANDISE_AMT><PO_DIST_LINE_NUM>OPTIONAL</PO_DIST_LINE_NUM><ACCOUNT>911000</ACCOUNT><DEPTID>9000</DEPTID><CHARTFIELD1>TEM01100</CHARTFIELD1></Dist><BUSINESS_UNIT>SN018</BUSINESS_UNIT><VCHR_BLD_KEY_C1>SN018</VCHR_BLD_KEY_C1><VCHR_BLD_KEY_N1>03162009</VCHR_BLD_KEY_N1><VCHR_BLD_KEY_N2>14:41:28</VCHR_BLD_KEY_N2><VOUCHER_ID>NEXT</VOUCHER_ID><VOUCHER_LINE_NUM>5</VOUCHER_LINE_NUM><DISTRIB_LINE_NUM>5</DISTRIB_LINE_NUM><BUSINESS_UNIT_GL>SN020</BUSINESS_UNIT_GL><QTY_VCHR>OPTIONAL</QTY_VCHR><MERCHANDISE_AMT>1157.64</MERCHANDISE_AMT><PO_DIST_LINE_NUM>OPTIONAL</PO_DIST_LINE_NUM><ACCOUNT>911000</ACCOUNT><DEPTID>9000</DEPTID><CHARTFIELD1>TEM01100</CHARTFIELD1></Dist>so now I have to debatch Header,line and Dist into single messageswhat I am doing in the orchestration is For HeaderExpression shape:HeaderCount = System.Convert.ToInt32(xpath(SQLMessage, “count(//Header)”));
in the message assignment shape:
Variable_3 = System.String.Format(“//Header[{0}]”,HeaderInstance);
Message_1 = xpath(SQLMessage, Variable_3);
and I am looping for the multiple header because there a possibility of getting multiple headers in a message.
I am getting an error in the construct message shape which says:
Uncaught exception (see the ‘inner exception’ below) has suspended an instance of service ‘TEMSInt.TemsOrchestration(10e74d9f-953f-b28d-425d-5fdbee10e5c7)’.
The service instance will remain suspended until administratively resumed or terminated.
If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.
InstanceId: aca1d817-96c0-4154-be0b-10e065b2ebf4
Shape name: Header
ShapeId: 83aa2bc8-71b9-412f-8e4a-178c40697408
Exception thrown from: segment 1, progress 32
Inner exception: Specified method is not supported.
Exception type: NotSupportedException
Source: Microsoft.XLANGs.Engine
Target Site: Microsoft.XLANGs.Core.Value GenericLoadFrom(System.Object)
The following is a stack trace that identifies the location where the exception occuredat Microsoft.XLANGs.Core.Part.GenericLoadFrom(Object source)
at Microsoft.XLANGs.Core.XSDPart.ProtectedLoadFrom(Object source)
at Microsoft.XLANGs.Core.Part.LoadFrom(Object source)
can you please help me to solve this error.
Thanks
March 15, 2009 at 5:06 PM in reply to: Using a map to turn a Flatfile schema into hierachical one #21920Looks like there is a problwm with your Xpath statement in your orchestration. Can you show us the Xpath statement and the schema
There are many ways of debatching, the most efficient is in the receive pipeline – this requires an envelope.
However there are some cases where you cannot debatch in the pipeline and you need to debatch inside the orchestration. The most common way of doing this is a looping xpath – this does not require an envelope.Can you provide an overview of your solution and why you are debatching in the orchestration instead of the pipeline?
-
AuthorPosts