We have had a lot of issues with moving things from development to production within in Dev Studio. We are on version 7.67. What is the best way to move these files and/or whole domains? We are pretty new to WebFOCUS and Dev Studio. It seems to get confused when we are signed into both environments.

This message has been edited. Last edited by: Kerry,

We are on 7.6.8 and I sign in to both dev and prod from Dev Studio. I haven't tried copying a domain, but I can copy a fex(es) or master(s) just by doing a right click and selecting copy and going to my production server selecting the domain and right click and paste.

Hi,

We have had webfocus for some time. In our environment our test and prod webfocus servers are in 2 different data centers. We have found the best way to manage movement of code within the MRE is to use the MRE Change Management utility. (It is found on the homepage server/ibi_apps/homepage.jsp You run the extract which creates a zip file this file is then moved to the utilities/cm/load directory on the production server and the MRE change management load is then used. This preserves domain and std rpt group names so that they remain consisted between test and prod.

Thank you...i will give the change managment a try

Hi,

we have 4 different zones ( Dev, test, beta, production). We do our deployment using regular filesystem copy.
Depending on how clean your development is, you could copy the whole "domainname"-folder to the other machine or do this just the first time and then only copy changed items.
But you have to be careful with the "domainname".htm-File!

Your development environment configurations, metadata, connection names should match your production environment. You can copy the fex files, but it is not IBI recommended way of moving the reports or domains. You should alwayse use change management.

Also, I will recommend that only administrator should be able to move new fex and domains to the production system. If less hands are involved, you will have lesser problems in your production environment.

quote:

Originally posted by Computix:
Hi,

we have 4 different zones ( Dev, test, beta, production). We do our deployment using regular filesystem copy.
Depending on how clean your development is, you could copy the whole "domainname"-folder to the other machine or do this just the first time and then only copy changed items.
But you have to be careful with the "domainname".htm-File!

I have tried this and that is where we have problems. Maybe because both environments are on the same box?

I got the change managment tool to work, but it seems to be a manual process. Once I create the zip file, it places it in a directory in test. The when I sign into production to try the upload, it is not there. I have to manually go behind the scenes and move the file to the correct place sense there is not a browse option. Could this be correct?

Yes it is and that is one of our major complaints with the tool We have had a new feature request in for this for ages and we keep getting told next release. They have the ability to pick the file up in dashboard change management and it works like a charm. But we have to move the file manually in Managed Reporting change management. Frustrating. The good part is though that all the domainname.htm files get updated correctly so you don't end up with any missing code or having to edit that file on your own. Also even with the manual copy of the zip file it does work much smoother then any fully manual method.