Deploying authorization rules
Application rules determine the action of the Rules Engine in your application. They are typically deployed to a Production environment by delivering a flat file (with extension .CON).
Authorization rules are different because USoft Authorizer is not only a design-time, but also a runtime application. To deliver them, you must transfer information contained in design-time records in T_AUTH_... tables from Development to Production.
The optimal way to deliver authorization rules is different for each application. Delivering authorization rules is similar to delivering design-time application data. The most practical deployment strategy is probably to deliver all design-time records that are needed in Production in the same way. Popular ways to deliver design-time application data in a USoft environment include:
•USoft batch jobs dedicated to delivering application data (by export from Development) and to upgrading application data (importing in Production), often leveraging USoft's XML Toolkit.
•Database-level scripts or SQL procedures.
•USoft Repository Manager routines.
For more information about USoft batch jobs and USoft's XML Toolkit, please go to USoft Definer Help.
For more information about USoft Repository Manager routines, please go to USoft Repository Manager Help.