community-content

Forum Replies Created

Viewing 15 posts - 6,076 through 6,090 (of 9,648 total)
  • Author
    Posts
  • in reply to: Construct Message #17256

    Anon,

    one quick way is to create a map. In the map, *do not map* the element you dont want if it is empty (use the conditional mapping functoid).

    I don't see what this has to do with the flat file input by the way – in the orchestration you are treating an XML message.

    John D.

    in reply to: Accessing plain dll #17254
    Hi John,
    Did you mean accessing the dll using [DllImport] command from the .NET wrapper?
    -Baskar-
    in reply to: Accessing plain dll #17252

    Anon, 

    Create a thin .NET wrapper which just calls out to the C++ component. This will give you testability and flexibility.

    John D.

    in reply to: Storing Variables globally #17249

    You can use SSODB.

    You can refer my link below where I discussed about SSODB.

    http://biztalkblogs.com/nishil/archive/2006/11/28/1534.aspx

     

    I would first modify the target namespaces on the schemas so there are no conflicts with having multiple schemas with the same root node. Then i would use a listen shape with multiple recieve shapes. The listen shape would allow for the orchestration to listen for different messages matching a schema for any of the recieve shapes in the listen shape. However, you need to change the namespaces for the schemas…

    1. Open a project that has the schema

    2. Double-click the schema to open it

    3. Select the schema node.

    4. Right-click and select properties

    5. Modify the target namespace property.

     

    in reply to: Storing Variables globally #17247
    Hi John,
    Thanks for the reply. We are considering of the issue about opening & closing of xml files each time when an orchestration fires up. Will it be a problem? Not sure about the performance hit that happens.  If i implement the lookup file to database table also then it would be again opening/closing connection each time for an orchestration. The DB people wont be happy to make hundreds of connection opening & closing.
    The xml file content would be changed often.
    in reply to: biztalk server2006 #17246

    The best thing to do is spend a little time looking for the BizTalk content on the Microsoft site.  It shows at a high level what BizTalk is and what it is used for.

    in reply to: Error notification from Receive port #17245

    You need to enable Suspended Message Routing.  And then build a process (Orchestration probably) to subscribe to the message and send an email.

     

    Check out the sample here: http://www.biztalkgurus.com/Samples/Suspended-Message-Routing-Biztalk-2006.html

     

    It should get you started.

    in reply to: Single receive folder for different file formats #17244

    You’ll need some type of schema resolver pipeline component.  There is a sample in the SDK in the Pipeline folder I think.  It based on Flat Files so it should be easy to modify.

    in reply to: Messaging Engine failed to initialize the transport adapter #17242

    I am having the same issue. Any resolutions?

    in reply to: Storing Variables globally #17241

    Anon,

    are you really worried about the performance hit of reading a small file for each instance of an orchestration which starts? I wouldn't worry, I think, because it will only be a small element against all the other things which one orchestration instance incurs.

    But you could try to make the retrieval of the info faster – for example, by COM+ singleton (System.Enterprises) or by a database table.

    John D.

    in reply to: Storing Variables globally #17239

    Anon,

    if the contents of the 'lookup file' aren't changing very often, then perhaps you could use the BizTalk config file?

    But, I agree that this is not really an answer to your question about a 'global' variable.

    John D.

    in reply to: MSMQ – Transport #17238

    Jeaha 🙂 MANY thx 🙂 that helps its exactly my prob Thx 🙂

    in reply to: Receive End options #17236

    Greg,

     Thanks for the reply and congrats to you on receiving the MVP, you truly deserved it.

    Regards,

    Sajid.

    in reply to: Receive End options #17234

    My first choice would always be Web Services (preferably WCF although you need BTS 2006 R2)

    Legacy protocols like File and FTP should only be used when you have no other choice. These protocols require other software components to deliver messages and there is no continuity between sender and receiver.

    HTTP is similar to Web Service, although is a lower level protocol – no metadata discovery, less options for security (restricted to HTTPS/SSL for  authentication and encryption)

    Queuing is an definite option for asynchronous messages when you cannot rely on the end-points being available, and you do not wish to handle error recovery/retries in your client code. WCF reliable messaging is not yet at the stage to replace MSMQ or Websphere MQ ( no underlying message persistence)

    Using WCF will enable you to use a similar interface model for Biztalk delivered services and other services using the WS-* protocols.

Viewing 15 posts - 6,076 through 6,090 (of 9,648 total)