|
Home
|
 Access Control System A key feature of the JDesignerPro system is the integrated Access Control mechanism and how it binds with the application structure. What we mean by "application structure" is the menu hierarchy and screen modules, combined with user menu authorization. Together these form the application structure. When you run JDesignerPro it requires a login, although the login can by turned off. This login can be done either automatically or with a User ID and Password. When you hit the web page that calls JDesignerPro the system first sends the login screen with the User ID and Password fields. You can have your users login as Guest or with a specific User ID. The deployment of screens within JDesignerPro is tightly integrated with user access. An unlimited number of people could each see a separate set of screens, simply based on their access level. For example, Jane, from Accounting, logs in and sees only the outstanding order screens but she has no update capability, Jim from Sales logs in and he gets to see only his own outstanding orders for his territory, while Jennifer, the Sales Manager, logs in and she sees all the territories with all the sales people’s orders. This is very easy to accomplish using JDesignerPro. All of these people can access this application or multiple applications from the one install of JDesignerPro on your server. When you deploy a set of application screens you define user-access authorization codes for each menu and each tab within the menu. Then you match those authorization codes with people’s access levels. When someone logs in the JDesignerPro system shows them only the menus and tabs that match their access level. Matching user authorization codes and levels to those of the menus is how you create user groups. When a new module is created, the developer must give a login User ID and Password to the database. This is done at the start of the builder on the Select Database screen. The User ID and Password used on the Select Database will be the one used to login to the database when your final applet is run unless the 'use JDP usename/password' option is chosen. The application end-users do not login to the database directly. They login to JDesignerPro which in turn logs in as your account to the database. Your users’ authorizations are controlled by the User Maintenance settings that you define under JDesignerPro’s System Maintenance area. JDesignerPro handles connection scalability through the JaggServer. BulletProof created JDesignerPro to capture the inherent power of the Intranet and Java. To that end, removed is the necessity to install anything but a browser on your users’ and developers’ desktops. At the same time BulletProof added the ability to build many applications over that single server install and have those applications be served up to users "on-the-fly." You only need to install the JDesignerPro system once on a server. From this one install can be served any number of applications to any authorized users, anywhere. |
|
|