Hi I am currently involved in upgrading wf and have to write up the process so I might as well post this online so as to be of use to others and also get some feedback for myself.

This is the implementation of the plan outlined in

https://forums.informationbuilders.com/eve/forums/a/tpc/...1057331/m/1061082732

1. Prechecking
(a) Check the credentials of the existing windows service. This runs under another id to system because it needs to set the environment variable EDAEXTSEC to DBMS because we have Oracle based authenication for the server console.
(b) We plan to increase the server ports by 1000 ie 8121 becomes 9121 while parallel running so we check on wikipedia just in case something else uses these ports. Gerry, Webfocus is not there!

http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_n...#Ports_1024_to_49151

2. Install process

The .zip directory contains the server software - click on Setup

Used defaults except:

Product install directory all prefixed with c:\wf76

Server administrator id is read only webfocus and I entered a password of webfocus.

HTTP listener 9121 and TCP 9120

Entered option to start the server to check the basic installation was ok. It ran in safe mode and then I took the server down by stopping the windows service. NB this was running with EDAEXTSEC=OPSYS the system setting of this environment variable.

Checked directories and confirmed that the registry has info under software and service webfocus entry for 76 which will have to be changed later when the directory structure loses its 76 prefix.

3. Copy configuration files from original set up c:\ibi\srv71 to c:\wf71\ibi\srv76 etc etc

A. edaserve.cfg - entries in file changed c:\ibi goes to c:\wf76\ibi
B. odin.cfg - replace 81xx ports with 91xx ports.
C. admin.cfg and any user profiles - should not need to change.
D. copy application directories ibisamp is duplicated so keep newer version baseapp has our stuff in it so keep old version.
E. copy edasprof.prf - should not need to change.
F. copy hdayxxxx.err file - should not need to change

4. Modify properties of the Webfocus 76 server service.
Alter the service to run under webfocus.admin which has environment variable EDAEXTSEC=DBMS
Change service type to automatic.

5. Test

Everything worked fine except:

A. The service could not be stopped from the services menu.

This had to be done by finding the pid of the edapsrv.exe process from edaprint.log and stopping the process tree as follows.

edapsrv.exe (service) or tscom300.exe (command line) is root process
edapth.exe - workspace manager
edaplog.exe - process log
tscom3.exe - agents
edapgwy.exe - http, tcp and dfm listeners
hlisnk.exe - fds or sink machine
jscom3c.exe - jscom3 graphics

there was a stop failed message in edaprint that said pnb/webfocus.admin the userid the service was running under was not of admin privilege. An entry had to be included in admin.cfg to say that pnb/webfocus.admin and webfocus.admin were administrators. This is new in 7.6 and a bit strange since security is
being done through edaextsec=dbms.

B. the admin user ifsappreport could not enter the webconsole as the administrator.

This was a more involved activity and involved raising a hottrack which ibi say will be fixed in 7.6.3. Details appear here
https://forums.informationbuilders.com/eve/forums/a/tpc/...1057331/m/9931074732

Next activity will be to set up the server that uses EDAEXTSEC=OPSYS.

Set up the server that uses EDAEXTSEC=OPSYS. This is electra-ext server.

Followed the earlier steps with the following exceptions

When installing the earlier 76 install was detected and it offered whether to configure as an additional instance or from scratch. Decided to configure from

scratch since all this involves is setting EDAHOME to a shared directory which can be done later if neccessary.

An important point I had neglected on earlier description is that EDASPROF.PRF needs the settings of these variables need to include the new ports.

SET FOCEXURL=http://electra-ext:87/ibi_apps/WFServlet
SET BASEURL=http://electra-ext:87/approot/


There were no problems with the admin console when configure with Opsys security