We have a custom import program that we use to import customer records into 
remedy from external sql databases has anyone else utilized the remedy api to 
build an application to do this? I will need to modify this program 
substantially in fact it may need a complete re-write and I am looking into 
what would be the best way to proceed with such a task, with the downturn in 
the economy support is not something my company is willing to shell out for so 
I am pretty much on my own with figuring out the best means to accomplish this, 
our goal is to update the records 3 different ways, we would like an 
incremental update to adjust for password changes (our support web uses the 
user table for authentication) we would also like to do a daily update and 
finally a weekly overwrite everything update..just looking for input feedback 
from the list as to what solutions you may have implemented in your 
environments to accomplish this type of task. 
  ----- Original Message ----- 
  From: Shafqat Ayaz 
  Newsgroups: public.remedy.arsystem.general
  To: arslist@ARSLIST.ORG 
  Sent: Monday, December 01, 2008 6:01 PM
  Subject: Re: Problems with Remedy Migrator.


  ** Hello Alberto
        Migrator logs into the server slightly differently than the Admin Tool 
or the User Tool. You need to set up the server you want to log into 
individually, and although in the login window you might select multiple 
servers, it will still make you login one at a time.
        Make sure that you have the server names configured and you have 
licensed the servers and you won't get that message. if you are still stuck 
drop me a line and i will send you screen shots on how to configure the server 
names

        thanks

        shafqat

        --- On Mon, 12/1/08, Grooms, Frederick W <[EMAIL PROTECTED]> wrote:

          From: Grooms, Frederick W <[EMAIL PROTECTED]>
          Subject: Re: Problems with Remedy Migrator.
          To: arslist@ARSLIST.ORG
          Date: Monday, December 1, 2008, 2:47 PM


          ** 
          I use Migrator to do a complete server to server migration with no 
problems.  We do partial (using .def files) to migrate from our dev server to 
test.  Once the test group and the users have completed their testing we do a 
full server to server migration to production (NOTE: We do not have any of the 
canned Remedy Applications).



          We also use Migrator to do a full server to server migration from 
Production down to development about twice a year (or when we can schedule it 
in).



          Main tip:  Run Migrator on a machine with a large amount of available 
memory.



          Fred



          From: Action Request System discussion list(ARSList) [mailto:[EMAIL 
PROTECTED] On Behalf Of Frank, Gordon M. (CMS/CTR)
          Sent: Friday, November 28, 2008 6:32 AM
          To: arslist@ARSLIST.ORG
          Subject: Re: Problems with Remedy Migrator.



          Do you have Migrator licensed?



          Do you have Tools, Licenses, Server Licenses declared?



          Do you have a valid AR Server license?



          Note: Migrator can be very disastrous if handled improperly. Read the 
documentation. Migrator can be your best friend if you understand it 
thoroughly. Sorry to sound condescending, but the problems that people have 
with Migrator are always a mis-understanding. Here’s a couple of rules of thumb:

            1.. Never migrate whole systems at one time. It will run forever 
and it is probably not what you want. If you are migrating a whole system, use 
a .def instead. 
            2.. Use the Scripting Mode. If you perform immediate mode, you 
might migrate something that you do not want. Scripting mode gives you a chance 
to look at it a second time. 
            3.. Use the Diff capability to make sure you have all changes. 
            4.. Migrate objects and data in small chunks. Setup several scripts 
and migrate them one at a time. 
            5.. Remember, Migrator will migrate the lowest lever change, 
including X,Ys, so be careful. It’s pretty stupid about these things, so you 
the tools it gives you (Diff and scripting) and make sure it is what you want.


          Gordon M. Frank

          Remedy Skilled Professional

          ITIL V3 Certified

          Lockheed Martin


----------------------------------------------------------------------

          From: Action Request System discussion list(ARSList) [mailto:[EMAIL 
PROTECTED] On Behalf Of Alberto Mel.
          Sent: Friday, November 28, 2008 6:30 AM
          To: arslist@ARSLIST.ORG
          Subject: Problems with Remedy Migrator.

          Hi all!,
          I'm installed the remedy Migrator 7.1 but I don't know why I'm unable 
to connect with our Remedy Server.
          When I try to connect, I have this message: "No servers for this 
account", but I can connect with the User and Administrator clients.....
          Anyone knows why?.
          Thank you very much!.
          Alberto


          __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers 
Are" html___  

  __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to