Production server - WF762
Test server - WF 769

Both Prodution and Test server are two diffent machine.I am trying to migrate the Sever setting from Production server drive:\ibi\srv762\wfs to Test server drive:\ibi\769\wfs. Do I have to manually copy this file from Prod to Test ?

This message has been edited. Last edited by: <Vijaya_settu>,

If some one knows any different than this, I would like to know, but having gone through a similar scenario in the last few days, we could not find a way to do this other than manually. There are migrate tools, but that assumes that the install directories are on the same machine.
The only other thing I can think of is to copy the srv76 directory to your new Test box and then use the migrate tool, pointing to the "dummy" location of your copied directory.

I haven't seen any migration tools for the server? For WebFocus client (MRE and Dashboard and such) there are tools, but for the server?

The only thing that comes close is to use the 'Save Diagnostic' from the program menu. That will give you more than you need, but the relevant config files are in the created diag subdir. You would still have to move them manually though.

The server migration utility is available from the Workspace pulldown of the web console, 4th entry down. I have used it many times and it works great!

I think you only have to copy the wfs/bin and wfs/etc directories to the new box. I know I did that several years ago but I don't remember what the steps were.

I think it converts edaserve.cfg, odin.cfg, and edasprof.prf. If you made any customizations to the edastart script, you have to re-make those.

Thank you all of you , I copied all these four files from prod to New server and modified according to New server setting. I checked the manual says only these four files to copy over.Did I miss any other stuff to copy "New Server".
1.edasprof.pf
2.edaserver.cfg
3.odin.cfg
4.profile

Thanks Ginny, for pointing me there. Never ever looked at that tool....

Vijaya,
It may be that there have been made other customizations in your server environment. I always advise people to track changes to these kind of installations in some config document, so that when you need to migrate or upgrade, you always know what has been changed. Usually these changes are made in the client environment, but it also possible to make changes to the server.
If no extra changes have been made, I think that the small list you have should be sufficient.

When we mentioned that they should be copied to the new server, it should be made clear that you should NOT just copy them over and use them in your new environment. The new configuration files may have many additional or different settings for the new version. They should be copied over in their same directory structure (so the migration tools know where to find them) and then you should allow the migration tools to gather your settings and place them in the appropriate locations in the new configuration files.

As I said before, make sure (and document as Gam said) you look at the edastart script. I know we have to put special stuff in ours for the Xserver implementation on Unix so that we can do graphs. That script is not 'migrated' using the tool.

And I totally agree with Darin.