We are testing WebFocus version 8.1.04. I have successfully exported and
imported all data from WebFocus 7.7.05 to the the testing server.

As users are testing their code, they are running into issues with the server name being
hard-coded into some of their fexes or html launch pages. When users run a report they get a message, to login to Managed Reporting, which still points to the old server.

Is there a way to globally replace the server name from webfocus:8080 to
wf8sandbox:8080, or will they need to edit each file individually? I've tried
using Wild Edit, but no matter what I do, the server name does not change.

Is this because the repository is now stored in the database?

Does anyone know of another way to accomplish this?

Any help you can offer would be greatly appreciated.

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

Go to each of the Reporting Servers and add this to edasprof.prf file:

-SET &&SERVER = 'HTTP://AAA.YYY.xx.XXX:8080';
or
-SET &&SERVER = 'HTTPS://AAA.YYY.xx.XXX:8080';

Then, replace the hard-coding in the fex's to the &&SERVER variable...

Thanks, Tom.

Just so I am clear, users would need to edit each fex or html file manually?

Yes, there is currently no easy method to automate updating files that are located in the Repository.

The only way I can think of doing this is to:

- use Developer Studio or App Studio to drag the files to a folder on the PC desktop
- use a smart, programmer's text editor to make the changes to the files
- use Developer Studio or App Studio to drag the files from the desktop folder to the Repository folder

This would have to be done one folder at a time and carefully.

This message has been edited. Last edited by: Francis Mariani,

Francis,

thank you so much for your input. I'm sure my users won't be pleased, but there isn't much we can do about it.

thanks again!

The only way we have "globally" update anything is to do an export (with IBI_CM_Format_Raw set to True so the export is text files), then use some editor, etc to effect the change, then re-inport.

We don't use MRE, so things could be different there, but we've seen this happen when deploying projects from incorrectly configured Developer Studio environments.

Basically, the user's Dev Studio environment (mine) was set up to use port 8080 directly, while we deploy our HTML (and other static content) to a server at port 80. The deploy process noticed this discrepancy and prepended URL's in the HTML with http://servername:8080/