Storing Variables globally

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Storing Variables globally

Viewing 2 reply threads
  • Author
    Posts
    • January 14, 2007 at 11:07 PM #17237
      community-content
        Hi All,
        In BizTalk 2006 is there a way to store variables(.net class, xml file) globally so that it is accesible to all the orchestrations?
        To explain the scenerio, suppose i have ten orchestrations all wants to read a xml lookup file to modify the input message values. If i implement the xml reading concept in orchestration level then for each instances of orchestration it has to read the xml file and close it. Suppose if i have 100 messages it has to read 100 times. Instead i have to store xml file in one location and share it across all orchestrations.
        Let me know any approach to handle this kind of issues?
        Appreciate your help.
      • January 15, 2007 at 7:44 AM #17239
        community-content

          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.

        • January 15, 2007 at 7:49 AM #17241
          community-content

            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.

            • January 15, 2007 at 9:17 PM #17247
              community-content
                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.
                • January 16, 2007 at 12:21 AM #17249
                  community-content

                    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

                  • January 17, 2007 at 8:40 AM #17268
                    community-content

                      Isn't the Business Rules Engine a possibility?  Using SSO for lookup values can be expensive, so it should only be used for secure values, or something that can benefit from the SSO infrastructure.  If you use the BRE, you could use caching to prevent constant reads from the database or file system.

                    • January 17, 2007 at 9:18 AM #17269
                      community-content

                        Anon,

                        why not take the advice of Dijkstra? If you are going to optimize – do it last. Wait until you have a performance problem and then fix it. You will be better employed working on a real problem or adding real functionality, rather than something that might happen.

                        Just make sure part of your testing is performance testing, and you have a good tool to find out where the performance issues are.

                        John D.

                • Author
                  Posts
                Viewing 2 reply threads
                • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.