Accessing multiple FMS Servers from a single machine

[SteveMC]

We've got a Terminal Server (Windows 2003 based) which is running on a network with several servers running SIMS for a number of local schools. We're having a few problems persuading the Terminal Server to connect to different FMS servers depending on the user logged in.

The FMS servers themselves are all running without a hitch (we've disabled broadcasting, and have changed the SQL Anywhere server names so they no longer clash).

I can change the FMS server accessed by the Terminal server as a whole by editing the ODBC configuraion for the SIMS32 System DSN, but if I create other System DSNs for the other servers (and update each user's sims_db.ini accordingly) everything still uses the SIMS32 one.

Does anyone know if the SIMS32 DSN is hard-coded into FMS, or can it be overridden?

Stephen

[wesleyw]

You need to install multiple fms clients each in it's own directory and linked to a specific FMS server.

Wes

[SteveMC]

You need to install multiple fms clients each in it's own directory and linked to a specific FMS server.

Ok, I've got two FMS folders now, but I can't see where to link them to different servers? - any pointers?

Cheers,

Stephen

[wesleyw]

Each one should have been installed and told which FMS server they would run from. All that is needed then is for the shortcut to be renamed to show which FMS system it connects to.


Wes

[SteveMC]

Each one should have been installed and told which FMS server they would run from. All that is needed then is for the shortcut to be renamed to show which FMS system it connects to.

Hmm. I'm obviously missing something here

I've run the FMS setup (for version 6.78) twice, and installed to two different folders (let's call them 'FMSSch1' and 'FMSSch2'). For each install, I specified the correct (remote) drive path for the SQL files (each school has a separate physical server, but the drive paths for the FMS SQL are the same on each).

There is only one ODBC System DSN created, called SIMS32, and that seems to be the problem, as it always points to the last school's FMS installed. I can create other DSNs, and even tweak sims_db.ini files, but all installations of FMS still use the SIMS32 DSN.

All I can say is roll-on FMS .NET (although I'll probably be regretting that!)

Cheers

Stephen

[Heebeejeebee]

Can you not just use the FMS Database selector tool? Maybe this doesn't work if the databases are located on different servers but it works fine for us where two versions are on the same server.

HBJB

[SteveMC]

Just a quick update - I've got FMS working now, with the following configuration:

1 x Server 2003 Terminal Server, with a single client install of FMS
2 x Server 2003 Std, with server installs of FMS

On the TS, I have configured the SIMS32 System DSN, in the 'Startup Options' to have a 'Start command' of:

c:\progra~1\sqlany50\win32\dbclient.exe @S:\fmsconf.txt

The file 'fmsconf.txt' on the S: drive contains the following:

-ta 600 
-x TCPIP{host=172.31.255.14;ServerPort=1501}

The host IP is changed for each server, and I'm running the servers on different ports too (avoiding the startup problems). The port is configured in the registry on each FMS server machine, at:

HKLM\System\CurrentControlSet\Services\SQLANYs_SIMS_SQL_DB_Server\Parameters

And the value of the 'parameters' is:

-n SIMS_Database -c 8192 -tl 1500 -x NamedPipes,TCPIP{BROADCAST=FALSE;ServerPort=1501}

With that set, it's all running without any problems.

I've just got the old Personnel via SIMS launcher to do now, but that's another thread

Stephen