community-content

Forum Replies Created

Viewing 15 posts - 7,396 through 7,410 (of 9,652 total)
  • Author
    Posts
  • in reply to: My own EDI schema #15263

    Read the Microsoft article!!! 🙂

    It’s not an SQL table, it’s a simple MS Access database table.
    It’s location by default is:
    C:\\Program Files\\Microsoft BizTalk Server 2006\\EDI\\Adapter\\CodeLists\\EDICodeLists.mdb

    I forgot to mention that on the schema file you have to configure it and say that the codelist database is located at the path I referred.
    To do this click on the <Schema> node and on the properties under Biztalk you have a field named \”codelist database\”.

    in reply to: My own EDI schema #15265

    [quote:4809a0cffb=\”myPFerreira\”]I have a D96A (EDIFACT), but as you figure I’m not allowed to make it \”public\”.

    But the Microsoft article is very clear.

    1 – New project with an Ochestration with a receive (set to receive a file) and a send shape (set to send XML)
    2 – configure the two parties (one with the sender and other receiver id codes)
    3 – Create the schema (use an existing standard and modify it, see the stylusstudio page to see the structure you want, or if it’s !your own structure build it according to the rules on the article apge)
    4 – Build the a table with you codes and values on the codelist database
    5 – configure ports,and you are good to go.

    I think I’m not missing nothing.[/quote:4809a0cffb]

    A question on point number 4… what’s the a table? and where to find it? Is is in the BizTalkEDIDb database…

    thx

    in reply to: Flat File Assembler FFAsm issue? #15323

    With the Address record you get
    A,dd,

    With the GridData record you get
    G,dd,2006-07-10T10:20:37+0100,

    But because the GridData record has another record as a child it adds that data of 1,1 – the comma here comes from GridData not GridValue, as having an Infix delimiter on a single field record will not do anything.

    By adding GridLine you still get GridData of:
    G,dd,2006-07-10T10:20:37+0100,

    plus GridValue now with a prefix delimiter
    ,1,1

    for net result of
    G,dd,2006-07-10T10:20:37+0100,,1,1

    If you just set the delimiter to be prefix on GridValue but keeping it as a child of GridData you will get
    G,dd,2006-07-10T10:20:37+0100,,1,,1

    There will be 2 commas between the RowNums, one from GridData and one from GridValue

    in reply to: Flat File Assembler FFAsm issue? #15321

    Hello Greg, thanks for the reply. However, For the Address record, the last field UserName is optional but still it generates a empty node. Any idea why?
    Regards,
    Biju
    The TestSchema XSD is pasted below:
    <?xml version=\”1.0\” encoding=\”utf-16\”?>
    <xs:schema xmlns:b=\”http://schemas.microsoft.com/BizTalk/2003\”
    xmlns=\”http://Test.TestSchema\” elementFormDefault=\”qualified\”
    targetNamespace=\”http://Test.TestSchema\”
    xmlns:xs=\”http://www.w3.org/2001/XMLSchema\”>
    <xs:annotation>
    <xs:appinfo>
    <b:schemaInfo default_pad_char=\” \” pad_char_type=\”char\”
    count_positions_by_byte=\”false\” parser_optimization=\”speed\”
    lookahead_depth=\”3\” suppress_empty_nodes=\”false\”
    generate_empty_nodes=\”true\” allow_early_termination=\”false\”
    early_terminate_optional_fields=\”false\”
    allow_message_breakup_of_infix_root=\”false\”
    compile_parse_tables=\”false\” standard=\”Flat File\” root_reference=\”TT\”/>
    <schemaEditorExtension:schemaInfo namespaceAlias=\”b\”
    extensionClass=\”Microsoft.BizTalk.FlatFileExtension.FlatFileExtension\”
    standardName=\”Flat File\”
    xmlns:schemaEditorExtension=\”http://schemas.microsoft.com/BizTalk/2003/SchemaEditorExtensions\”
    />
    </xs:appinfo>
    </xs:annotation>
    <xs:element name=\”TT\”>
    <xs:annotation>
    <xs:appinfo>
    <b:recordInfo structure=\”delimited\”
    preserve_delimiter_for_empty_data=\”true\”
    suppress_trailing_delimiters=\”false\” sequence_number=\”1\”
    rootTypeName=\”TT\” child_delimiter_type=\”hex\” child_delimiter=\”0x0D
    0x0A\” />
    </xs:appinfo>
    </xs:annotation>
    <xs:complexType>
    <xs:sequence>
    <xs:annotation>
    <xs:appinfo>
    <b:groupInfo sequence_number=\”0\” />
    </xs:appinfo>
    </xs:annotation>
    <xs:element minOccurs=\”1\” maxOccurs=\”1\” name=\”Header\”>
    <xs:annotation>
    <xs:appinfo>
    <b:recordInfo sequence_number=\”1\” structure=\”delimited\”
    preserve_delimiter_for_empty_data=\”true\”
    suppress_trailing_delimiters=\”false\” child_delimiter_type=\”char\”
    child_delimiter=\”,\” child_order=\”infix\” />
    </xs:appinfo>
    </xs:annotation>
    <xs:complexType>
    <xs:sequence>
    <xs:annotation>
    <xs:appinfo>
    <b:groupInfo sequence_number=\”0\” />
    </xs:appinfo>
    </xs:annotation>
    <xs:element default=\”H\” name=\”RecordType\”
    type=\”xs:string\”>
    <xs:annotation>
    <xs:appinfo>
    <b:fieldInfo sequence_number=\”1\”
    justification=\”left\” wrap_char_type=\”hex\” wrap_char=\”0x22\” />
    </xs:appinfo>
    </xs:annotation>
    </xs:element>
    <xs:element name=\”CreatedDate\” type=\”xs:string\”>
    <xs:annotation>
    <xs:appinfo>
    <b:fieldInfo sequence_number=\”2\”
    justification=\”left\” wrap_char_type=\”hex\” wrap_char=\”0x22\” />
    </xs:appinfo>
    </xs:annotation>
    </xs:element>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:sequence minOccurs=\”0\” maxOccurs=\”unbounded\”>
    <xs:annotation>
    <xs:appinfo>
    <b:groupInfo sequence_number=\”2\” />
    </xs:appinfo>
    </xs:annotation>
    <xs:element minOccurs=\”0\” maxOccurs=\”unbounded\”
    name=\”Address\”>
    <xs:annotation>
    <xs:appinfo>
    <b:recordInfo sequence_number=\”1\” structure=\”delimited\”
    preserve_delimiter_for_empty_data=\”true\”
    suppress_trailing_delimiters=\”false\” child_delimiter_type=\”char\”
    child_order=\”infix\” child_delimiter=\”,\” tag_name=\”A\” />
    </xs:appinfo>
    </xs:annotation>
    <xs:complexType>
    <xs:sequence>
    <xs:annotation>
    <xs:appinfo>
    <b:groupInfo sequence_number=\”0\” />
    </xs:appinfo>
    </xs:annotation>
    <xs:element default=\”A\” name=\”RecordType\”
    type=\”xs:string\”>
    <xs:annotation>
    <xs:appinfo>
    <b:fieldInfo justification=\”left\”
    sequence_number=\”1\” wrap_char_type=\”hex\” wrap_char=\”0x22\” />
    </xs:appinfo>
    </xs:annotation>
    </xs:element>
    <xs:element name=\”UserSerialNumber\” type=\”xs:string\”>
    <xs:annotation>
    <xs:appinfo>
    <b:fieldInfo sequence_number=\”2\”
    justification=\”left\” wrap_char_type=\”hex\” wrap_char=\”0x22\” />
    </xs:appinfo>
    </xs:annotation>
    </xs:element>
    <xs:element default=\” \” name=\”UserName\”
    type=\”xs:string\”>
    <xs:annotation>
    <xs:appinfo>
    <b:fieldInfo sequence_number=\”3\”
    justification=\”left\” wrap_char_type=\”hex\” wrap_char=\”0x22\” />
    </xs:appinfo>
    </xs:annotation>
    </xs:element>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element minOccurs=\”0\” maxOccurs=\”unbounded\”
    name=\”GridData\”>
    <xs:annotation>
    <xs:appinfo>
    <b:recordInfo sequence_number=\”2\” structure=\”delimited\”
    preserve_delimiter_for_empty_data=\”true\”
    suppress_trailing_delimiters=\”false\” child_order=\”infix\”
    child_delimiter_type=\”char\” child_delimiter=\”,\” tag_name=\”G\” />
    </xs:appinfo>
    </xs:annotation>
    <xs:complexType>
    <xs:sequence>
    <xs:annotation>
    <xs:appinfo>
    <b:groupInfo sequence_number=\”0\” />
    </xs:appinfo>
    </xs:annotation>
    <xs:element default=\”G\” name=\”RecordType\”
    type=\”xs:string\”>
    <xs:annotation>
    <xs:appinfo>
    <b:fieldInfo sequence_number=\”1\”
    justification=\”left\” wrap_char_type=\”hex\” wrap_char=\”0x22\” />
    </xs:appinfo>
    </xs:annotation>
    </xs:element>
    <xs:element name=\”SerialNumber\” type=\”xs:string\”>
    <xs:annotation>
    <xs:appinfo>
    <b:fieldInfo sequence_number=\”2\”
    justification=\”left\” wrap_char_type=\”hex\” wrap_char=\”0x22\” />
    </xs:appinfo>
    </xs:annotation>
    </xs:element>
    <xs:element default=\” \” name=\”eDate\” type=\”xs:string\”>
    <xs:annotation>
    <xs:appinfo>
    <b:fieldInfo sequence_number=\”3\”
    justification=\”left\” wrap_char_type=\”hex\” wrap_char=\”0x22\” />
    </xs:appinfo>
    </xs:annotation>
    </xs:element>
    <xs:element name=\”genDate\” type=\”xs:string\”>
    <xs:annotation>
    <xs:appinfo>
    <b:fieldInfo sequence_number=\”4\”
    justification=\”left\” wrap_char_type=\”hex\” wrap_char=\”0x22\” />
    </xs:appinfo>
    </xs:annotation>
    </xs:element>
    <xs:element minOccurs=\”0\” maxOccurs=\”unbounded\”
    name=\”GridValue\”>
    <xs:annotation>
    <xs:appinfo>
    <b:recordInfo sequence_number=\”5\”
    structure=\”delimited\” preserve_delimiter_for_empty_data=\”true\”
    suppress_trailing_delimiters=\”false\” child_order=\”infix\”
    child_delimiter_type=\”char\” child_delimiter=\”,\” />
    </xs:appinfo>
    </xs:annotation>
    <xs:complexType>
    <xs:sequence>
    <xs:annotation>
    <xs:appinfo>
    <b:groupInfo sequence_number=\”0\” />
    </xs:appinfo>
    </xs:annotation>
    <xs:element name=\”RowNum\” type=\”xs:string\”>
    <xs:annotation>
    <xs:appinfo>
    <b:fieldInfo sequence_number=\”1\”
    justification=\”left\” wrap_char_type=\”hex\” wrap_char=\”0x22\” />
    </xs:appinfo>
    </xs:annotation>
    </xs:element>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:sequence>
    <xs:element minOccurs=\”1\” maxOccurs=\”1\” name=\”Trailer\”>
    <xs:annotation>
    <xs:appinfo>
    <b:recordInfo sequence_number=\”3\” structure=\”delimited\”
    preserve_delimiter_for_empty_data=\”true\”
    suppress_trailing_delimiters=\”false\” child_delimiter_type=\”char\”
    child_delimiter=\”,\” child_order=\”infix\” />
    </xs:appinfo>
    </xs:annotation>
    <xs:complexType>
    <xs:sequence>
    <xs:annotation>
    <xs:appinfo>
    <b:groupInfo sequence_number=\”0\” />
    </xs:appinfo>
    </xs:annotation>
    <xs:element default=\”T\” name=\”RecordType\”
    type=\”xs:string\”>
    <xs:annotation>
    <xs:appinfo>
    <b:fieldInfo sequence_number=\”1\”
    justification=\”left\” wrap_char_type=\”hex\” wrap_char=\”0x22\” />
    </xs:appinfo>
    </xs:annotation>
    </xs:element>
    <xs:element name=\”TotalNumberOfRecords\” type=\”xs:string\”>
    <xs:annotation>
    <xs:appinfo>
    <b:fieldInfo sequence_number=\”2\”
    justification=\”left\” wrap_char_type=\”hex\” wrap_char=\”0x22\” />
    </xs:appinfo>
    </xs:annotation>
    </xs:element>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:schema>

    in reply to: how to get contents of an invalid xmldocument #15242

    Ok, how about this.

    You get your return message from the pipeline and pass it to a helper .net component. Inside the component, you access the message as an XLang Message of type Stream and load it into something stringbuilder maybe.

    In any case, you should have a Stream that you can convert into a String.

    The overall return result from the method would be a String (your message). Or you could just return the exact data you are looking for.

    I’ll try to build a sample of this and see if I can get it to work but I’ll not have any time in the next few days.

    Oh, if you need a starting point for the .net helper you can look at and modify the helper .net class I have in this sample: http://www.biztalkgurus.com/Samples/Debatch-Smaller-Batch-Orchestration.html

    If you give it a try, let me know the results.

    in reply to: how to get contents of an invalid xmldocument #15244

    Farukh, Stephen..

    I faced this same issue at one point trying to build my notification application.

    Basically, whether or not the XML message is valid, you can always access the context properties etc. Basically, you can do whatever you want EXCEPT accessing the payload to read/write etc. The simple fact is that the pipeline didnt return a file as a well formed XML document.

    using System.string or XMLdocument as the message type would accomplish the exact same result, but as you probably know, you cant transorm, promote etc.

    I solved this by wrapping my \”payload access\” areas in a scope with an exception handler. If the message is not a wellformed doc, then it would be passed to a C# helper class that would read the contents of the message as a stream and conduct a few string methods etc to try to figure out the reason that this file is invalid. you could accomplish the same by calling the ffdasm with one node that is delimited on the eof and then run your logic in that same orchestration or in another one even another orchestration dedicated to this.

    All in all, in my use of messages in biztalk, i couldnt find any way to access data in a partially correct message and biztalk will throw an error every time.

    if anyone figures out some other way, pass it on. I would love an easier way to solve some of these problems

    in reply to: XML to EDI #15269

    now i may not be understanding your question exactly but i will try to cover all the bases here:

    when you configure a party in biztalk for EDI purposes you need to specify the Sender ID, the Qualifer and the Sender control. In the EDI world, thats the ISA05,ISA06 and GS02 for the sender and ISA07, ISA08 and GS03 for the receiver respectivly.

    SO….. hopefully, this next part answers your question….
    any XML to EDI (or vice versa) translator, be it the HIPAA accelerator or Covast, will take this party information and map it to the envelope. They will also use the party information to validate that this person sending the file is in fact a trading partner using proper IDs.

    And thats the significance of parties in biztalk and EDI. hope that helps get you on the right track.

    in reply to: Bizrules guru! #14152

    It seems that I lost the indentation formatting in the original post (now I know why there is a ‘preview’ option)
    Anyway I cannot get the correct indentation to work 😳 so I have made parent nodes in Bold I hope this helps…

    [b:3fcd4c1932]<file>[/b:3fcd4c1932]
    <SupplierName>
    <SupplierAddress>
    [b:3fcd4c1932]<Invoice>[/b:3fcd4c1932]
    <BuyerNameAndAddress>
    <SupplierAccountNumber>
    <TotalValue>
    [b:3fcd4c1932]<Line>[/b:3fcd4c1932]
    <LineItem>
    <LineItemValue>
    <GSTValue>

    Cheers
    JMan

    in reply to: Flat File Assembler FFAsm issue? #15322

    There is only part of your schema, so this is a bit of a guess.
    I assumed your Schema looks like this:
    [code:1:6b430db73b]TT
    Header
    Address
    GridData Delimiter \",\" Infix
    RecordType
    SerialNumber
    genDate
    eDate
    GridValue
    RowNum
    Trailer[/code:1:6b430db73b]
    Because the eDate field is the last field of the GridData record, there is no trailing delimiter. Therefore if eDate has no value there will be no empty node.

    One way of fixing this is to change the schema structure to:

    [code:1:6b430db73b]TT
    Header
    Address
    GridLine – no delimiter
    GridData Delimiter \",\" Infix
    RecordType
    SerialNumber
    genDate
    eDate
    GridValue Delimiter \",\" Prefix
    RowNum
    Trailer[/code:1:6b430db73b]

    in reply to: Help Orchestration Designer errors out #14150

    Any help will be greatly appreciated. I was designing a fairly complex Orchestration and when I removed a ParallelBranch I got an exception message. The designer stopped responding and I exited VS2003 and re-opened the BizTalk 2004 project. Now when I try to open that Orchestration I get a constant set of Microsoft Development Environment error message boxes. The first set says [quote:2ef0215c00]The following exception has occurred: Win32Exception: The operation completed successfully[/quote:2ef0215c00] then I get an error message box that says [quote:2ef0215c00]The following exception has occurred: Win32Exception: Not enough storage is available to process this command[/quote:2ef0215c00] I am developing on WinXP 2GB mem BizTalk 2004 with SP1.

    Nothing shows up in the Event Log. Here is the Exception text
    ************** Exception Text **************
    System.ComponentModel.Win32Exception: Not enough storage is available to process this command
    at System.Windows.Forms.DibGraphicsBufferManager.CreateCompatibleDIB(IntPtr hdc, IntPtr hpal, Int32 ulWidth, Int32 ulHeight, IntPtr& ppvBits)
    at System.Windows.Forms.DibGraphicsBufferManager.CreateBuffer(IntPtr src, Int32 offsetX, Int32 offsetY, Int32 width, Int32 height)
    at System.Windows.Forms.DibGraphicsBufferManager.AllocBuffer(Graphics targetGraphics, IntPtr targetDC, Rectangle targetBounds)
    at System.Windows.Forms.DibGraphicsBufferManager.AllocBufferInTempManager(Graphics targetGraphics, IntPtr targetDC, Rectangle targetBounds)
    at System.Windows.Forms.DibGraphicsBufferManager.AllocBuffer(IntPtr target, Rectangle targetBounds)
    at System.Windows.Forms.Control.WmPaint(Message& m)
    at System.Windows.Forms.Control.WndProc(Message& m)
    at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
    at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

    ************** Loaded Assemblies **************
    mscorlib
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2032
    CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
    —————————————-
    Microsoft.BizTalk.OrchestrationDesigner
    Assembly Version: 3.0.1.0
    Win32 Version: 3.0.4902.0
    CodeBase: file:///C:/Program%20Files/Microsoft%20BizTalk%20Server%202004/Developer%20Tools/Microsoft.BizTalk.OrchestrationDesigner.dll
    —————————————-
    Microsoft.BizTalk.VisualStudio.Shell.Interop
    Assembly Version: 7.0.3300.1
    Win32 Version: 7.00.2220
    CodeBase: file:///C:/Program%20Files/Microsoft%20BizTalk%20Server%202004/Developer%20Tools/Microsoft.BizTalk.VisualStudio.Shell.Interop.DLL
    —————————————-
    Microsoft.BizTalk.OLE.Interop
    Assembly Version: 7.0.3300.1
    Win32 Version: 7.00.2220
    CodeBase: file:///C:/Program%20Files/Microsoft%20BizTalk%20Server%202004/Developer%20Tools/Microsoft.BizTalk.OLE.Interop.DLL
    —————————————-
    System
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2032
    CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
    —————————————-
    System.Windows.Forms
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2032
    CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
    —————————————-
    System.Drawing
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2032
    CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
    —————————————-
    Microsoft.BizTalk.ObjectModel
    Assembly Version: 3.0.1.0
    Win32 Version: 3.0.4902.0
    CodeBase: file:///c:/windows/assembly/gac/microsoft.biztalk.objectmodel/3.0.1.0__31bf3856ad364e35/microsoft.biztalk.objectmodel.dll
    —————————————-
    Microsoft.BizTalk.IMS
    Assembly Version: 3.0.1.0
    Win32 Version: 3.0.4902.0
    CodeBase: file:///c:/windows/assembly/gac/microsoft.biztalk.ims/3.0.1.0__31bf3856ad364e35/microsoft.biztalk.ims.dll
    —————————————-
    Microsoft.BizTalk.TypeSystem
    Assembly Version: 3.0.1.0
    Win32 Version: 3.0.4902.0
    CodeBase: file:///c:/windows/assembly/gac/microsoft.biztalk.typesystem/3.0.1.0__31bf3856ad364e35/microsoft.biztalk.typesystem.dll
    —————————————-
    Microsoft.VisualStudio
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.573
    CodeBase: file:///c:/Program%20Files/Microsoft%20Visual%20Studio%20.NET%202003/Common7/IDE/Microsoft.VisualStudio.DLL
    —————————————-
    System.Runtime.Remoting
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2032
    CodeBase: file:///c:/windows/assembly/gac/system.runtime.remoting/1.0.5000.0__b77a5c561934e089/system.runtime.remoting.dll
    —————————————-
    Microsoft.BizTalk.VisualStudio.TextManager.Interop
    Assembly Version: 7.0.3300.1
    Win32 Version: 7.00.2220
    CodeBase: file:///C:/Program%20Files/Microsoft%20BizTalk%20Server%202004/Developer%20Tools/Microsoft.BizTalk.VisualStudio.TextManager.Interop.DLL
    —————————————-
    Microsoft.BizTalk.Studio.Extensibility
    Assembly Version: 3.0.1.0
    Win32 Version: 3.0.6070.0
    CodeBase: file:///c:/windows/assembly/gac/microsoft.biztalk.studio.extensibility/3.0.1.0__31bf3856ad364e35/microsoft.biztalk.studio.extensibility.dll
    —————————————-
    Microsoft.XLANGs.BaseTypes
    Assembly Version: 3.0.1.0
    Win32 Version: 3.0.4902.0
    CodeBase: file:///c:/windows/assembly/gac/microsoft.xlangs.basetypes/3.0.1.0__31bf3856ad364e35/microsoft.xlangs.basetypes.dll
    —————————————-
    EnvDTE
    Assembly Version: 7.0.3300.0
    Win32 Version: 7.00.9466
    CodeBase: file:///c:/windows/assembly/gac/envdte/7.0.3300.0__b03f5f7f11d50a3a/envdte.dll
    —————————————-
    System.Xml
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2032
    CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
    —————————————-
    CustomMarshalers
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.573
    CodeBase: file:///c:/windows/assembly/gac/custommarshalers/1.0.5000.0__b03f5f7f11d50a3a/custommarshalers.dll
    —————————————-
    Microsoft.BizTalk.CommonUI
    Assembly Version: 3.0.1.0
    Win32 Version: 3.0.4902.0
    CodeBase: file:///c:/windows/assembly/gac/microsoft.biztalk.commonui/3.0.1.0__31bf3856ad364e35/microsoft.biztalk.commonui.dll
    —————————————-
    Accessibility
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.573
    CodeBase: file:///c:/windows/assembly/gac/accessibility/1.0.5000.0__b03f5f7f11d50a3a/accessibility.dll
    —————————————-
    Microsoft.VisualStudio.Designer.Interfaces
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.573
    CodeBase: file:///c:/windows/assembly/gac/microsoft.visualstudio.designer.interfaces/1.0.5000.0__b03f5f7f11d50a3a/microsoft.visualstudio.designer.interfaces.dll
    —————————————-
    System.Design
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2032
    CodeBase: file:///c:/windows/assembly/gac/system.design/1.0.5000.0__b03f5f7f11d50a3a/system.design.dll
    —————————————-
    XLANGsCompiler
    Assembly Version: 0.0.0.0
    Win32 Version: 3.0.6070.0
    CodeBase: file:///C:/Program%20Files/Microsoft%20BizTalk%20Server%202004/XLANGsCompiler.dll
    —————————————-

    Thanks in advance

    in reply to: user account NT AUTHORITY\\NETWORK SERVICE #15286

    As it turns out the each web service can override the AppPool of the website to which it is assigned. The learning curve here seems to be broader than first imagined. Now if I could get the webservice to look for the same public key that I am publishing, things would probably work.
    Thanks for your comment, it helped.

    in reply to: Help! XmlDocument & Multiple maps in a single send port #14148

    I have a generic orchestration handling different document types. The messages that I’m using inside the orchestration are of type XmlDocument, and this cannot be changed as the purpose of this orchestration is to be generic for many (similar) documents. However, when I send the message to the Send Port, the mappings specified in the port are NOT executed at all, even if the XmlDocument’s content is a perfectly valid document of a certain document type.

    After some research, it seems that the BTS.MessageType property is not getting promoted, so the Send Port may not know which map to apply to it.

    Does anyone know if what I’m attempting to do can even be done? Can I send a XmlDocument to a Send Port and expect the correct mapping to be applied?

    Thanks

    in reply to: storing xml file in database using sql adapter #15332

    If you store the Xml as ntext datatype in SQL Server, you can use the standard SQL Adapter.

    If you specifically want to use an image datatype then you could try the SQL Server BLOB adapter:
    [url]http://www.gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=189360ED-B216-45D2-B11A-B42828A3697D[/url]

    in reply to: a correlation may be initialized only once #14143

    What I finally started doing in a lot of my new orchestrations is sending a dummy message before the loop in order to \”initialize\” the correlation.
    In our case, we correlate on a SOAP-Header, so we created a dummy message schema and dummy message and send it to a flat file directory.

    In my opinion, Biztalk needs an \”init correlation\” shape.

    Tomas Restrep has a \”NULL Adapter\” that you can use instead of writing to a flat file directory – the message gets \”eaten\” but the correlation is still initialized.

    http://www.winterdom.com/weblog/PermaLink,guid,475.aspx

    in reply to: Mapping results of a web service #15319

    First post/new user, so hope this isn’t too elementary…

    I have a web service that takes a parameter and is returning a dataset from a SQL database. The service is running correctly, now I would like to call it from my BizTalk orchestration. I would like to map the results that are received from the web service into a particular XML schema which I have created a schema file for. Is it possible to create a map between a web service’s return schema and another? When I go to create a map file, I can not select the web service return schema. Any suggestions on manipulating this returned dataset?

    Thanks,
    Jason

Viewing 15 posts - 7,396 through 7,410 (of 9,652 total)