Sybase recommends that you use the new roles defined in EAServer 6.0, and not jagadmin. The “Admin Role” role, of which jagadmin is a member is not automatically migrated. This may cause problems for migrated applications that use “Admin Role”. When you migrate a Web application from EAServer 5.x to EAServer 6.0, J2EE roles and mapped EAServer roles defined in this Web application are migrated, but EAServer 5.x users are not. For example, the migrated sample Tier1 Web application does not have correct role name mapping, if the “Admin Role” from EAServer 5.x uses the default values.
In this case, the Web application in EAServer 5.x has the J2EE role “EAF Admin” mapped to the EAServer “Admin Role”. In the file $DJC_HOME\config\webapp-eaf-user.xml, you see this mapping:
<setProperties securityDomain="default"> <addRole role="eaf.EAF Admin" toRole="Admin Role"/> </setProperties>
To work around this issue, modify $DJC_HOME\config\webapp-eaf-user.xml, to add the jagadmin user to the “Admin Role”, and run the configuration file.
