signonUser

The optional signonUser argument specifies the sign‑on user code when executing existing methods or reading, compiling, and executing transient methods. (See also the signonPassword argument.)

When you specify the signonUser argument, you must also specify the schema and app arguments in the jadclient command line (and optionally the executeSchema argument), as they specify the schema and application to which the jadclient executable does a jomSignOn call.

Although the signonUser and signonPassword arguments are optional, your application logic (the appropriate authentication rules in the Global class getAndValidateUser or isUserValid method) may require these arguments for signing on to the application specified in the app argument. See also "Getting Non-GUI Client Sign-On Details".

Consider that the global validation methods will be called in non‑GUI applications, in which an exception is raised when creating and attempting to show forms unless the application is in exception state. In the getAndValidateUser method, check if the type of application is non‑GUI. If so, specify your required user code and password; for example, you could set the user code to the application name and the password to the current schema name.

Your isUserValid method can then check that the combination of non‑GUI application type, user code, and password are valid, to protect against running non‑GUI applications that are defined in the schema and are not intended to be run in production.