Announcement

Collapse
No announcement yet.

Agent Migration to OTM

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Agent Migration to OTM

    Hello all :

    Is there a way to migrate Agent changes or updates to Production environment ? At present, we are recreating them in Production. We use OTM5.5 CU2 RU5.

    Thanks in advance.
    Jay

  • #2
    Re: Agent Migration to OTM

    I believe they can be exported and imported via CSV (though I don't remember which version of OTM) - though I've always found the most accurate way is to re-create them - which is what nearly everyone is doing anyways.

    It's still a pain in the rear, though...

    --Chris
    Chris Plough
    twitter.com/chrisplough
    MavenWire

    Comment


    • #3
      Re: Agent Migration to OTM

      Agents can be migrated from environment to environment (export/import) using the DB.XML utility as well which seems to work pretty well on version 5.5 CU3 RU5.

      Regards,
      Chris
      Last edited by itnole; October 2, 2008, 23:59.

      Comment


      • #4
        Re: Agent Migration to OTM

        I am in the process of building a utility that copies Agents, and all related Queries and Conditions. Doing this in 5.0. The utility creates a ZIP file containing all the required CSV files.

        I have the process fairly down pat now. We can move agents from environment to environment in about 5 minutes now, regardless of their complexity, or the number of agents.

        Curious about the DB.XML though. Does this just copy the Agent, agent action details, and the agent event details, or does it also copy Saved Queries?
        James Foran
        Toll Global Information Services
        http://www.tollgroup.com

        Comment


        • #5
          Re: Agent Migration to OTM

          Through the DB.XML utility you can extract the following database objects (plus many more) which contain the parent and child tables: Agent, Agent_Action, Agent_Event, Saved_Query, Saved_Condition

          XML works much better than CSV since CSVs cannot handle line breaks, commas, quotes, etc.

          Comment


          • #6
            Re: Agent Migration to OTM

            Hi Itnole,

            I want to use db.xml for this agent migration from one instance to another.
            I am able to export the db.xml from OTM through Data Export-->db.xml Export successfully. After that we are saving that exported XML as xxx.db.xml. When I am trying to import the same XML file to the database of another instance through Integration Manager its throwing the below error


            XML Parsing Error: syntax error
            Location: http://xxx.yyy.com:6001/GC3/glog.int...omain=&run=Run
            Line Number 1, Column 1:Traceback (most recent call last):

            Please suggest what I have to do for getting out of this issue.?

            Thanks.
            Sirish

            Comment


            • #7
              Re: Agent Migration to OTM

              Yes i would agree with db.xml is very efficient way of moving Agents. One good thing about it is you can export all your(pain full) "Saved Queries " easily.. Exporting saved queries via CSV is pain and it's need reformatting lines and spaces etc..
              Thanks,
              Vinoth Gopalakrishnan

              Comment


              • #8
                Re: Agent Migration to OTM

                Let's not over exaggerate the agent/saved query csv export pain, also considering that working with csv gives you much more flexibility than dbxml.

                The csv pain is only caused by line breaks, which you can swiftly remove as described in this article:

                Remove Line Breaks in Direct SQL and Saved Queries - OTM Wiki

                Comment


                • #9
                  Re: Agent Migration to OTM

                  Sirish,

                  To avoid the syntax error you are receiving when attempting to update the db.xml file try removing the first line in the db xml file (XML declaration).

                  <?xml version="1.0" encoding="utf-8" ?>

                  Comment


                  • #10
                    Re: Agent Migration to OTM

                    Thanks Itnole,

                    The XML that I have extracted from db.xml export, it does not contains the line <?xml version="1.0" encoding="utf-8" ?>.

                    It has the structure like:

                    <sql2xml>
                    <TRANSACTION_SET>
                    <AGENT
                    AGENT_GID = "DOMAIN.SHIPMENT_CANCELLED_PERFORM_ACTION"
                    AGENT_XID = "SHIPMENT_CANCELLED_PERFORM_ACTION"
                    DATA_QUERY_TYPE_GID = "SHIPMENT"
                    .........
                    .........
                    </AGENT>
                    </TRANSACTION_SET>
                    </sql2xml>

                    Thanks,
                    Sirish




                    Comment

                    Working...
                    X