Since the Batch Launcher does not require the application server to be running, it does not perform any application level authentication or authorization. It must only authenticate against the database. The same credentials as used by the application server (located in %SERVER_DIR%/project/properties/Bootstrap.properties ) are used by the Batch Launcher to connect to the database and run batch programs.
The Batch Launcher or batch programs can optionally trigger the application server to begin a DB-to-JMS transfer. This involves logging in and invoking a method on the server, which in turn requires a valid username and password. By default the DB-to-JMS transfer operation uses default credentials; therefore, the DBTOJMS account must exist on the Cúram Users table and must be enabled and assigned the role 'SYSTEMROLE' to allow authorization. The locale DB-to-JMS transfer is the default locale for this user as specified in field 'defaultLocale' on the Users table.
The Security Considerations section in the Cúram Batch Processing Guide guide should be consulted for further details on changing the user for the DB-to-JMS transfer.
The property batch.username can be used to specify the user name for the operations run by the Batch Launcher. This is set using the -D parameter. For example: build runbatch -Dbatch.username=admin