The previous limits for ACLs and users familiar from previous versions of Saperion still apply to all 32-bit applications. This includes the COM and UBI APIs, as well as the Saperion Rich Client. This section describes what you should know if you plan to use 32-bit applications and the Web Client, or the new Services mixed with the Classic Connector.
Compatibility views and triggers
Saperion version 8.0 and higher contain compatibility views so that the Rich Client and COM and UBI applications continue functioning as before. The views emulate the XSUSR, XSGRP, XSACC, XSACL and XSMND tables of the old User Management system. In addition, triggers are defined that guarantee a complete compatibility between the 32-bit applications and the new APIs Classic Connector/ECM Services.
Besides the compatibility views, the 32-bit applications use the new reference tables for users, groups and ACLs. For more information, see the “Automatic Migration” and the “Data Model” topics.
If you currently access these tables directly, make sure that you can also access the views directly. If you write directly to the tables without using the Saperion API, you must replace those functions with Saperion API calls.
Objects outside of the 32-bit limitation
You can now create objects (user, group or ACL) in the User Management that go beyond the previous limitations of 200 rights per ACL and 150 groups per user or group. Such objects cannot always be used in 32-bit applications, when these applications are used in operations that make use of both 32-bit and 64-bit applications.
When an object cannot be used, the Java Core Server displays a warning when it starts, saying that the object cannot be used by 32-bit applications. For ACLs, this means that objects are not accessible. For users, it means that they cannot log in using 32-bit applications.
32-bit LDAP sync
In an LDAP sync, the system no longer deletes unavailable objects, but simply marks them as deleted, so that they do not affect the data integrity in a later sync.