community-content

Forum Replies Created

Viewing 15 posts - 9,601 through 9,615 (of 9,648 total)
  • Author
    Posts
  • in reply to: Biztalk 2004 Configuration #12063

    Some things to check or at least think about:
    – make sure the user accounts you are using for setup are in the correct user groups
    – if you are doing a multi computer install you are using domain accounts like domain\\name
    – if you are re-running the installation make sure all the databases and user accounts that were automatically created have been removed
    – you have all required components installed
    – you have not installed any beta software (like Biztalk 2006, VS 2005, .net 2.0) on the computer prior to installing Biztalk

    It almost sounds like something might not have gotten installed correctly? If nothing else works, you might want to uninstall and reinstall Biztalk 2004.

    Hope this helps.

    in reply to: Biztalk EDI mapping #11998

    Base Edi does not have this information.
    You should use full Covast EDI Accel.
    http://support.microsoft.com/default.aspx?scid=kb;en-us;840113
    Here is a quote from Microsoft on Base EDI limitation (Covast wants you to buy the full version:))
    Miscellaneous EDI schema limitations
    No floating segment support. This limitation is the same as in Microsoft BizTalk Server 2002.
    Very limited binary segment support. This limitation is the same as in BizTalk Server 2002.
    [b:f69c076ace]EDI Envelope data is not conveyed on the inbound. Therefore, the data is not available for use in the BizTalk Mapper or in orchestrations. This limitation is the same as in BizTalk Server 2002.[/b:f69c076ace]
    EDI Envelope layouts cannot be customized or modified. This limitation is the same as in BizTalk Server 2002.
    The list of supported X12 Functional Group Identifiers is fixed according to the 4050 version. This means you cannot use transaction sets that were introduced after the 4050 version, because the system does not know which functional group identifier belongs to it (because that is not part of the schema).
    The EDI Annotation <b:RecordInfo count_ignore=\”yes\”> is ignored by the Base EDI Adapter. The Base EDI Adapter uses hard-coded technology to count the segments in EDI transactions.
    The BizTalk Server 2004 Base EDI Adapter uses stricter EDI character set validations than BizTalk Server 2002. For example, when an EDIFACT UNOA interchange is received, it will validate the characters in the interchange according to the defined character set that belongs to the UNOA syntax (which is a subset of ISO-646).
    For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

    in reply to: Biztalk EDI mapping #11997

    I used covast edi for biztalk a lot.

    The incoming 850 is translated to xml by covast edi accelerator.
    I have seen the header for the ISA and it has the partner id (sender).

    You are using base EDI biztalk right?
    Maybe the base edi don’t have it. In the Covast EDI schema, there is a thing called CovastEnvelope

    Look for it even if you are using the base EDI.

    If not, then go to Covast website and send an email and ask. They wrote the Base EDI too.

    in reply to: Installation BTS2006 Beta 2 on Virtual PC 2004 #14220

    That should not be a problem with Biztalk 2006 Beta 1. I have not actually tried it but I have not heard of anything having problems with it.

    I run mine on a Windows 2003 VPC through.

    in reply to: Database Lookup Functoid -input columns #12055

    I don’t think you will see any improvements in that area in 2006. We may have to wait until 2008 on that one. Best of luck with the custom functoid.

    in reply to: Database Lookup Functoid -input columns #12053

    Stephen,

    I have thought about that since posting. You can create a Custom Functoid using .NET classes, by inheriting from the Microsoft.BizTalk.BaseFunctoids class. There’s a sample in the SDK that comes with BizTalk 2003 -but it’s not a database sample.

    Ideally it would be great if you could inherit from the standard database functoid, then add another input for a second datase column, but I can’t see any example code that shows how to construct such an input. So I’m a bit stuck.

    I hope they have extended this area in the new 2006 version !

    -John

    in reply to: Database Lookup Functoid -input columns #12054

    Hello.

    I don’t know of a way around it.

    Could you call a custom .net component inside the map to return your data?

    in reply to: Mapping a single record into two #12057

    I’m having a bit of trouble with a map I’m working on and wondering if anyone can shed some light on this.

    I’ve got a source document where I need to take the data under a given node and map it to two or more nodes in the destination.

    For example:

    The source doc is:

    <Header>
    <Customer>ABC</Customer>
    <Date>1/1/2005</Date>
    <Details>
    <Detail>
    <Value1>A</Value>
    <Value2>B</Value>
    <Number>100</Number>
    </Detail>
    </Details>
    </Header>

    I need to end up with:

    <Header>
    <Customer>ABC</Customer>
    <Date>1/1/2005</Date>
    <Details>
    <Detail>
    <Value1>A</Value>
    <Number>100</Number>
    </Detail>
    <Detail>
    <Value>B</Value>
    <Number>100</Number>
    </Detail>
    </Details>
    </Header>

    I just can’t seem to figure out how to get Biztalk to create 2 detail records from one.

    Any help would be greatly appreciated.

    in reply to: Creating workflows dinamically at runtime #12051

    Hello.

    That can not really be done inside an Orchestration.

    But, you would use Content Based Routing and Orchestrations with the Rules Engine to achieve something close to dynamic workflows. Each message would have properties set on it what would route it to the correct “next step” in the process. Then, at the end it will run through the rules engine again to see where to go next.

    I saw a demo using this by a Microsoft guy. It was awesome.

    Hope this helps.

    in reply to: Urgent : SQLAdapteR Error #12047

    Fab,
    I would check a couple of things.

    1 – Make sure that the adapter is installed correctly. Have you tried a very simple example with the adapter just to verify it works?

    2 – make sure you have the pre-req’s installed. SQLXML 3.0 would be the key one.

    3 – What does your stored proc look like? Have you verified you are not maybe returning an unsupported type, etc? Does the stored proc work outside of the adpater?

    Todd

    in reply to: Debatching multiple SWIFT messages separated by CRLF #12045

    I don’t have any experience with SWIFT so helpfully someone else can help you out more then I can.

    One thing I might suggest is to create a higher level envelope schema to try to break it apart. Don’t know if that would work though.

    Hope this helps.

    in reply to: how to install biztalk server 2004 (urgent) #12043

    I think you might have some hard times. I have read about some problems with both installed: http://weblogs.asp.net/cschittko/archive/2004/11/21/267595.aspx

    On my home computer, I had Biztalk 2004 and VS 2003 installed. Then, I installed VS 2005. I don’t know what would happen if I uninstalled and reinstalled Biztalk 2004.

    I saw a posting on Scott Woodgate’s blog about needing to set Biztalk 2004’s config setting to use .net 1.1 vs 2.0. But, I don’t think that’s your problem since you can not get it installed.

    I don’t know

    Sorry I couldn’t be of more help.

    in reply to: partners with different transport type and address #12039

    Hello.

    I think you can do with a new different ways.

    One way is just to set up a Send Port for each Partner with the correct transport type. The, use direct binding out of the Orchestation and route the messages to the correct trading partner based on SourceFileName. Just make sure you set up the subscriptions right otherwise you will get into an endless loop.

    Another way to do it is to use Role Links. This way, you set up one Role for each partner. Then, you define a property to route your message to the Role (in your case SourceFileName). Then, you add the Send Port for the partner into the Role. This way you have a lot less risk in routing errors but you have a little more work to do.

    Hope this helps.

    in reply to: Comment on Replay Design Thoughts #12041

    This is a great comment.

    Anything that causes additional messages to be send inside Biztalk will decrease performance – even using Biztalk internal tracking will decrease performance.

    in reply to: Getting ACK and NACK #12037

    Did you look at this sample: http://www.biztalkgurus.com/Samples/Delivery-Notification-NAck-Orchestration.html

    You should be able to be it with just using Delivery Notification. That will give you the Biztalk NACK on Adapter Error.

    You can not easily catch ACKs.

    This will give you the Biztalk NACK / ACK. Is that what you are looking for or is it something HIPPA specific?

Viewing 15 posts - 9,601 through 9,615 (of 9,648 total)