You cannot map the existing Developer and Runtime EAE 3.3 security settings to Agile Business Suite. Refer to Preparing to Migrate that discusses Runtime security in an MCP environment.
The concept of setting security via privilege levels is superseded by COM+ role-based security. You must manually configure the security of your existing applications specifically for Agile Business Suite by using the tools available in your operating system.
Security requirements for Runtime can be configured via the Administration Tool. The runtime security tasks are performed post-installation and are described further in Using the Administration Tool.
User Accounts
Prior to installing Agile Business Suite, you must create two user accounts; the Application User and the Administrative User, which form the basis of your role-based security system.
Under these two initial user identities, the following operations are executed:
Application User – performs standard operations and has a lower privilege level
Administrative User – performs administrative tasks and requires a higher privilege level. These users are authorized to perform administrative tasks according to the COM+ roles to which they belong.
The above user accounts must also be granted access to the server.
Note: The AB Suite Developer and Runtime require two user accounts, Application User and Administrative User that perform various operations. You should not change the Application User and Administrative User accounts once they are set up. If an account needs to be changed, whether it is simply renaming or creating an entirely new account, you must manually replace all references to the old account.
Refer to Security in the Agile Business Suite Developer User Guide for information on how to apply security to the AB Suite model and the elements.
Debugger Security
To run debug sessions against a test database, it is necessary to grant access to the user running the debug session (the Debugger user).
Using the Administration Tool, the Debugger user should be made a member of the “Secure Users” role, as described in the Administration Tool Online Help.
SQL Server
The Debugger user should be granted access to the model database against which the debug session is run.
To do so:
A debugger user should be added as a new SQL Server Login. You can add either an individual user or the Debugger users group.
A user associated with the SQL Server Login of Debugger user should have permissions to create new model databases against which the debug session is run.
Runtime Security
The Runtime Manager takes connections from various Agile Business Suite processes, as well as the Administration Tool and based on the COM+ role-based configuration information provides access to the Runtime environment as well as all the applications.
Note: The Runtime security is valid only for Windows Runtime.
Refer to Runtime Manager for more information.