Clovertech

Migrating NetConfig from test to live

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Migrating NetConfig from test to live

  • Creator
    Topic
  • November 9, 2005 at 3:14 pm #48134
    Kathy Zwilling
    Participant

      I would like to copy my modified and tested NetConfig file from my test environment to my live environment.  I made some extensive changes to it and I don’t want to duplicate effort and run the risk of getting something wrong.    I want to copy it to live, change all the test IPs/ports to live ones and be ready to go but I think there might be more to this?

      In the past, it seems like I have had problems getting the Netmonitor to work (might have been marshalling errors — not sure) because of doing this and after reading some archives I wonder if the problem is that I am not migrating other corresponding files from test to live.

      Do I have to copy all or some of the files in the /quovadx/qdx5.2/integrator/test01/views?

      I have these in that directory (Unix) now:

      config_dflt.view

      driver_dflt.view

      monitor_dflt.mvw

      monitor_view

      Any explanation of what these files each do would be great too!

      Thanks for your help!

      Kathy Zwilling

    • Creator
      Topic
    Viewing 2 reply threads
    • Author
      Replies
      • November 9, 2005 at 9:13 pm #57787
        Anonymous
        Participant

          Kathy,

          If you want to move the entire contents of a site into another site then you’d want to include the views directory in the copy.  Otherwise you get that annoying single stack of thread icons in the monitor.

          If you want to move only a particular thread from test to production then it’s a little more complicated.  You’ll want to reach into the view file and copy and paste the view entry for that thread.

          The view files:

          config_dflt.view – the view for the netconfig.

          driver_dflt.view – anybody remember blaster and catcher?  This is a legacy view that isn’t used by the current version of Cloverleaf.

          monitor _dflt.view – The view used by the Network Monitor.

          monitor_dflt.mvw – The monitor views were changed a few versions back and when you save the view in the monitor, this file is used instead of monitor_dflt.view.

          So, if you want to move a thread into the NetConfig you have to move the view entry from the source config_dflt.view file to the destination config_dflt.view AND you have to move the entry from the source monitor_dflt.mvw file to the destination monitor_dflt.mvw.

          One more tip:  If you have saved the monitor view then you’ll notice that the NetConfig view isn’t used in the monitor anymore.  If you want the monitor to use the NetConfig view again then just delete the monitor_dflt.mvw file and start the monitor GUI.  It’ll create a new mvw file from the config_dflt.view file.

        • November 9, 2005 at 10:07 pm #57788
          Kathy Zwilling
          Participant

            Greg,

            So my understanding from what I am seeing experimenting and with your response is that the only truly “valid” files in 5.2 is the config_dflt.view and the monitor_dflt.mvw.  The other two are essentially obsolete, correct?

            Thanks for all the information!

            Kathy

          • November 10, 2005 at 11:32 pm #57789
            Anonymous
            Participant

              Kathy,

              That’s right, both driver_dflt.view and monitor_dflt.view are obsolete.

          • Author
            Replies
          Viewing 2 reply threads
          • The forum ‘Cloverleaf’ is closed to new topics and replies.