Security Considerations

As mentioned above, 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 Cúram username and password. By default the DB-to-JMS transfer operation uses user 'DBTOJMS', so this account must exist on the Cúram 'Users' table and must be enabled and assigned the role 'SYSTEMROLE'.

It is also possible to configure a different user name and password for DB-to-JMS. This is done by providing values for the following properties:

• curam.security.credentials.dbtojms.username - The username that Cúram uses to process JMS messages created by batch programs.
• curam.security.credentials.dbtojms.password - The password that Cúram uses to process JMS messages created by Batch programs. This password must be encrypted.

The above credentials must exist on the Cúram 'Users' table, must be enabled, and should be assigned the role 'SYSTEMROLE'.

The previous mechanism for providing custom DB-to-JMS credentials, via the curam.omega3.DBtoJMSCredentialsIntf, APIs has been deprecated.