Among others, we offer the following services:
OAC3 Display links for content repositories
In the initial screen, you can first use the global settings to specify whether changes should be allowed in general. Furthermore, you can define specifically for the software components and namespaces of the Repository objects whether they can be changed at all, or whether changeability should be restricted.
Finally, the presentation layer contains software components for the graphical presentation of the application. It thus forms the interface to the users (GUI).
ADMIN TOOLS
Job scheduling: your system needs to run various automated background jobs that consume resources. Your administrator must carefully schedule these tasks when user demand is low so they don't impact performance.
Before the project starts, it must be clear which systems are to be connected to the IdM and which services the system is to provide. This requires close collaboration between the department and IT, as later adaptations or additional systems will extend the implementation and exceed the budget. Analysing existing data To successfully implement an Identity Management System, high quality data is essential. Users' root data must be verified, updated, or maintained. Automation with incomplete or even incorrect data is otherwise not conceivable. Rethinking the Permission Concept With the introduction of an Identity Management System and a workflow for permission granting, the existing roles should be scrutinised once again. You should ask yourself whether the user knows what role he chooses from the current catalogue and whether it is sufficient for his task. Set Role-Owner Not only the user needs to know which role to choose. There must also be a person in charge of the role who adapts or adapts the role as required or acts as a point of contact when required.
"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.
It thus forms the interface to the users (GUI).
Migration to the Cloud Platforms.