community-content

Forum Replies Created

Viewing 15 posts - 2,356 through 2,370 (of 9,648 total)
  • Author
    Posts
  • in reply to: extra XML info not needed #23127

    what pipe line do you use on send port? I guess if you use XMLTransmit then it will ad those header info. If you use passthru on send port then it wouldnt add those header info. Correct me if i am wrong here.

    Siva

    in reply to: X12 997 Acknowledgement #23124

    Hi , I just wanted to add this note so that people who come across your instructions for 997 setup will also notice that if you have other outbound messages setup for the same EDI Partner (Like 310, 315) and you try to configure your 997 , BizTalk server 2006 chokes…when you remove the 310, 315 then the 997 comes out fine. Otherwise in the EDI Reports of the HAT you can see the 997 generated, but it will not create the file in the desired windows folder….if anyone has any input on how to overcome this it will be of great help.  Thanks, Asri

    in reply to: Detecting duplicate nodes in BizTalk #23123

    Hi

    Can you use the same logic without replacing the Items and Item with Errors and Error?  I would like to keep the same structure and add an attribute on the duplicates like delete=”true”.

     

    in reply to: X12 997 Acknowledgement #23122

    Hi, was your issue resolved? Thanks,Asri

    in reply to: X12 997 Acknowledgement #23121

    Hi  I followed the instruction in your post (which was very helpful) but in the EDI reports I see the acknowledgement, whereas I do not see it in the file folder path specified in the send port. no errors/warning or info in the event log!! any help is highly appreciated. – Thanks, Asri

    in reply to: Functoid Issue #23120

    Thank you Danial, It helped me to fix the issue. Once again, Thank you.

    in reply to: which functoid to use ? #23119

    Could you provide a sample input and out put?

    I guess you can use Table Loop functoid and table extract functoid.

    in reply to: Schedule Orchestration #23117

    Version 1 of the adapter was written for BTS2004, although it still works on BTS2009.
    The error is referring to the documentation browser, from Visual Studio 2003.  You can ignore this error.

    in reply to: Schedule Orchestration #23116

    Normal
    0

    false
    false
    false

    EN-US
    X-NONE
    X-NONE

    MicrosoftInternetExplorer4

    <!–
    /* Font Definitions */
    @font-face
    {font-family:”Cambria Math”;
    panose-1:2 4 5 3 5 4 6 3 2 4;
    mso-font-charset:1;
    mso-generic-font-family:roman;
    mso-font-format:other;
    mso-font-pitch:variable;
    mso-font-signature:0 0 0 0 0 0;}
    @font-face
    {font-family:Calibri;
    panose-1:2 15 5 2 2 2 4 3 2 4;
    mso-font-charset:0;
    mso-generic-font-family:swiss;
    mso-font-pitch:variable;
    mso-font-signature:-1610611985 1073750139 0 0 159 0;}
    /* Style Definitions */
    p.MsoNormal, li.MsoNormal, div.MsoNormal
    {mso-style-unhide:no;
    mso-style-qformat:yes;
    mso-style-parent:””;
    margin-top:0in;
    margin-right:0in;
    margin-bottom:10.0pt;
    margin-left:0in;
    line-height:115%;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:”Calibri”,”sans-serif”;
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:Calibri;
    mso-fareast-theme-font:minor-latin;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:”Times New Roman”;
    mso-bidi-theme-font:minor-bidi;}
    .MsoChpDefault
    {mso-style-type:export-only;
    mso-default-props:yes;
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:Calibri;
    mso-fareast-theme-font:minor-latin;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:”Times New Roman”;
    mso-bidi-theme-font:minor-bidi;}
    .MsoPapDefault
    {mso-style-type:export-only;
    margin-bottom:10.0pt;
    line-height:115%;}
    @page Section1
    {size:8.5in 11.0in;
    margin:1.0in 1.0in 1.0in 1.0in;
    mso-header-margin:.5in;
    mso-footer-margin:.5in;
    mso-paper-source:0;}
    div.Section1
    {page:Section1;}
    –>

    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:”Table Normal”;
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:””;
    mso-padding-alt:0in 5.4pt 0in 5.4pt;
    mso-para-margin-top:0in;
    mso-para-margin-right:0in;
    mso-para-margin-bottom:10.0pt;
    mso-para-margin-left:0in;
    line-height:115%;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:”Calibri”,”sans-serif”;
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:”Times New Roman”;
    mso-fareast-theme-font:minor-fareast;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;}

    When
    I try to install that MSI file in my desktop, I’m getting one error. I thing “dexplore.exe”
    are missing in that MSI file.

    in reply to: Schedule Orchestration #23115
    in reply to: multiple source mapping issue #23111

    Here is am example: input xml file has duplicate records, XSLT will remove duplicate and output a single instance of duplicate records only (base on UserID as a key)

    —————————————–

    here is the sample XML

    —————————————–

    <ns0:Employees xmlns:ns0=”http://BizTalk_Server_Project1.Employees”&gt;

    <Employee>

      <FirstName>FirstName_0</FirstName> 

      <LastName>LastName_0</LastName> 

      <RecordID>RecordID_0</RecordID> 

      <UserID>UserID_0</UserID> 

      <Address>Address_0</Address> 

      </Employee>

    <Employee>

      <FirstName>FirstName_1</FirstName> 

      <LastName>LastName_1</LastName> 

      <RecordID>RecordID_1</RecordID> 

      <UserID>UserID_1</UserID> 

      <Address>Address_1</Address> 

      </Employee>

    <Employee>

      <FirstName>FirstName_0</FirstName> 

      <LastName>LastName_0</LastName> 

      <RecordID>RecordID_0</RecordID> 

      <UserID>UserID_0</UserID> 

      <Address>Address_0</Address> 

      </Employee>

    <Employee>

      <FirstName>FirstName_2</FirstName> 

      <LastName>LastName_2</LastName> 

      <RecordID>RecordID_2</RecordID> 

      <UserID>UserID_2</UserID> 

      <Address>Address_2</Address> 

      </Employee>

    <Employee>

      <FirstName>FirstName_1</FirstName> 

      <LastName>LastName_1</LastName> 

      <RecordID>RecordID_1</RecordID> 

      <UserID>UserID_1</UserID> 

      <Address>Address_1</Address> 

      </Employee>

      </ns0:Employees>

    ——————————————–

    Here is the XSLT:

    ——————————————-

    <xsl:stylesheet xmlns:ns0=”http://BizTalk_Server_Project1.Employees&#8221; xmlns:xsl=”http://www.w3.org/1999/XSL/Transform&#8221; xmlns:msxsl=”urn:schemas-microsoft-com:xslt” xmlns:var=”http://schemas.microsoft.com/BizTalk/2003/var&#8221; exclude-result-prefixes=”msxsl var” version=”1.0″>

    <xsl:output omit-xml-declaration=”yes” method=”xml” version=”1.0″ />

    <xsl:key name=”duplicateKey” match=”Employee/UserID” use=”.” />

    <xsl:template match=”/”>

    <xsl:apply-templates select=”/ns0:Employees” />

    </xsl:template>

    <xsl:template match=”/ns0:Employees”>

    <xsl:variable name=”Employees”>

    <xsl:for-each select=”Employee/UserID”>

    <xsl:variable name=”group” select=”key(‘duplicateKey’,.)” />

    <xsl:if test=”generate-id($group[1]) = generate-id()”>

    <xsl:if test=”count($group) &lt; 2 or count($group) &gt; 1″>

    <xsl:element name=”Employee”>

    <xsl:element name=”UserID”>

    <xsl:value-of select=”$group[1]” />

    </xsl:element>

    <xsl:element name=”FirstName”>

    <xsl:value-of select=”/ns0:Employees/Employee[UserID=$group[1]]/FirstName” />

    </xsl:element>

    <xsl:element name=”LastName”>

    <xsl:value-of select=”/ns0:Employees/Employee[UserID=$group[1]]/LastName” />

    </xsl:element>

    <xsl:element name=”RecordID”>

    <xsl:value-of select=”/ns0:Employees/Employee[UserID=$group[1]]/RecordID” />

    </xsl:element>

    <xsl:element name=”Address”>

    <xsl:value-of select=”/ns0:Employees/Employee[UserID=$group[1]]/Address” />

    </xsl:element>

    </xsl:element>

    </xsl:if>

    </xsl:if>

    </xsl:for-each>

    </xsl:variable>

    <xsl:choose>

    <xsl:when test=”count(msxsl:node-set($Employees)/Employee/UserID) &gt; 0″>

    <xsl:element name=”Employees” namespace=”http://BizTalk_Server_Project1.Employees”&gt;

    <xsl:copy-of select=”$Employees” />

    </xsl:element>

    </xsl:when>

    <xsl:otherwise>

    <xsl:copy-of select=”.” />

    </xsl:otherwise>

    </xsl:choose>

    </xsl:template>

    </xsl:stylesheet>

     

    ——————-

    output:

    ——————–

    <?xml version=”1.0″ encoding=”utf-8″?>

    <Employees xmlns=”http://BizTalk_Server_Project1.Employees”&gt;

    <Employee xmlns=””>

    <UserID>UserID_0</UserID>

    <FirstName>FirstName_0</FirstName>

    <LastName>LastName_0</LastName>

    <RecordID>RecordID_0</RecordID>

    <Address>Address_0</Address>

    </Employee>

    <Employee xmlns=””>

    <UserID>UserID_1</UserID>

    <FirstName>FirstName_1</FirstName>

    <LastName>LastName_1</LastName>

    <RecordID>RecordID_1</RecordID>

    <Address>Address_1</Address>

    </Employee>

    <Employee xmlns=””>

    <UserID>UserID_2</UserID>

    <FirstName>FirstName_2</FirstName>

    <LastName>LastName_2</LastName>

    <RecordID>RecordID_2</RecordID>

    <Address>Address_2</Address>

    </Employee>

    </Employees>

    in reply to: Itinerary – whos resposibility ? #23110

    Code changes? Up to this point you shouldn’t have needed to write any custom code at all (unless you needed to extend the ESB toolkit itself for some reason)… As long as the new itinerary matches your environment (or you configure your environment to support it) it should just work.

    in reply to: Itinerary – whos resposibility ? #23109

    ok, now using the same example which you have explained …
    if I only alter the steps in the itinerary i.e. stage3–>stage1 –> stage 2
    Will I have to write code or make any alterations to execute this itinerary ?

     

     

    in reply to: Itinerary – whos resposibility ? #23108

    Nope, it’s not like that. There’s no routing at all unless the current stage (service) and the next one are configured to run in different contexts (as I explained before). Consider for example this itinerary:

    on ramp -> receive handler ( transform1, transform2 ) -> orchestration handler ( routing service) -> off ramp

    The way this would execute is:

    – The receive port receives the message and runs the ESB receive pipeline
    – The ESB pipeline figures out the right itinerary to apply to the message, initializes it and puts it in the context
    – The ESB dispatcher component in the pipeline grabs the message and executes the first 2 stages (two Transform Services) 
    – The pipeline finishes execution and the message goes into the message box
    – The ESB Routing orchestration picks up the message from the message box and executes the routing service configured for the third stage, and then drops the message into the message box again
    – The Send port (esb off ramp) picks up the message and sends it.

    Is this any clearer?

    in reply to: BizTalk 2009 Configuration Problem #23107

    Everyone,

    I figured out the problem: out-of-date download components.

    – Jack

     

Viewing 15 posts - 2,356 through 2,370 (of 9,648 total)