Multiple Relay Servers on a machine / multiple MobiLink Servers on a machine

[Former Member]

SETUP: We currently have a test environment as follows:

Client side - Servers running SQL Anywhere 11.0.1 and MobiLink client

DMZ zone (customer facing) - POLYGON (Windows Server 2003 SP2) - running MobiLink Relay Server v11.0.1 - Website address is 142.x.y.23

Application zone - SCALE (Windows Server 2003 SP2) - running o MobiLink Outbound Enabler v11.0.1 o MobiLink Server v11.0.1

Database zone - Oracle 10g database - ODBC connection to AAIT10G

QUESTION: A new project is requesting 3 additional end-to-end test environments.

We can easily: - duplicate the client side with multiple SQL Anywhere databases, - duplicate the Database side with multiple Oracle schemas.

Can we duplicate the Relay Servers and MobiLink servers on the existing servers, namely POLYGON and SCALE? - POLYGON o add 3 new 'MobiLink Relay Servers' using the same IP address 142.x.y.23 o with different url suffixes on the MobiLink client configurations - SCALE o add 3 new Outbound Enablers o add 3 new MobiLink Servers o add 3 new ODBC connections, 1 for each of 3 new Oracle schemas

Thanks

[Former Member]

Currently, you can only have one instance of RS on a single machine and it seems all you need is to use the multi-tenant feature in RS to partition the traffics into 3 ML farms. There is no need of adding more RS unless physical resource is limiting your scalibility. -Wing

[Former Member]

One could work around that by running each RS instance in a different VM, but then each would have a different IP address.

Also, unless one is using integrated Outbound Enablers (via ML's -oe switch), one has to configure each OE-ML pair to use a different port.

[Former Member]

It is true that you cannot start multiple ML servers on the same machine while all of them are listening to the same port on all of the network interfaces. However you may increase the number of network interfaces in your VM and then use the host parameter in mlsrv??.exe -x to bind to dedicated network interface individually.