Configuration Parameters.... Simple Question! :)

Administration
1

Hi all,

So, if I were put this in my SCS Applications’ Start-Up parameters;

-host hostname -port 2020 -app SCS -l “7260@licenseserver1:7260@licenseserver2”

Instead of this;

-host hostname -port 2020 -app “SCS” -l “7260@licenseserver1:7260@licenseserver2”

…what would you expect, as a result?

And I really do have a Kit Kat in my top drawer… :slight_smile:

Thanks!

Tony

2

I’d expect to search a service named “SCS” and if it doesn’t exists will fail or behave strangely…

1 Like
3

Thanks cav - my thoughts too - or the Application will start and LCA/SCS/SCI will not capture it correctly - or it will not start/stop correclty from SCI… or something like that…

Anyone else want to have a go…? :slight_smile:

T

4

Interesting thread, cause for me the command line has always been a pain in the neck issue.
Frankly I’m quite surprised by what you guys are saying, cause from my point of view the app parameter is related to the application name only, why should the service be involved?
Also, what the Genesys Framework Deployment guide states and what I knew:

When an application is installed on a UNIX operating system and the
application name, as configured in the Configuration Database, contains spaces
(for example, T-Server Avaya), you must surround the application name by
quotation marks (“ ”) in the command line, as follows:
-app “T-Server Avaya”

However, I think that the installation wizard on a Windows box would add quotation marks.

Fra

1 Like
5

Thanks buddy - I think half a Kit Kat is yours…

There appears to be 2 parameters - and it appears to be “either”, “or”;

One is the - service parameter
One is the - appplication parameter

AFAIK, you should add quotes for both, if there are spaces/blanks in the instance name…

?

6

oh yes, I love the Kit Kat bar, yummy! ;D

You would have both of them for a Windows box, only app for a Unix one.

Exactly what I think.

Fra

7

Hum I have seen strange behaviours on SCI and the windows services when the -service is different in some ways that the real service name, I guess because it does a net status like command and passes the service name configured as parameter and may fail if something is wrong. I also agree to use quotations when using complex names but on simple names don’t know why sometimes do strange stuff…

1 Like
8

Similar to cav’s posting, I have seen similar strange behaviors on Windows hosts where there may have been quotes around the executable (for example, “e:\gcti\tserver\succession.exe” … ) in the service but not in the config layer, or if the drive or directory didn’t match in case (for example, e:\gcti in config layer and E:\GCTI in service ).

9

agree, saw weird things too..