Access Manager Data
Access Manager, like other Java ES components, makes use of various kinds of data that for any specific upgrade might need to be migrated to an upgraded version. The following table shows the type of data that could be impacted by an upgrade of Access Manager software.
Table 9–2 Access Manager Data Usage|
Type of Data |
Location |
Usage |
|---|---|---|
|
Configuration data |
AccessManager-base\config\AMConfig.properties AccessManager-base\config\serverconfig.xml Java Archive (JAR) files for authentication and customized modules AccessManager-base\lib |
Configuration of Access Manager and its integration with a back-end data store |
|
Web container configuration |
Web Server: server.policy and server.xml files in WebServer-base\https-hostname\config Application Server: server.policy and domain.xml files in ApplicationServer-base\domain\domain1\config |
Configuration of Access Manager web container instance |
|
Customization data (Web container customized JSP files) |
Admin Console: AccessManager-base\web-src\applications Authentication UI: AccessManager-base\web-src\services |
Configuration of Access Manager administration interfaces |
|
Directory schema Services configuration User data |
Directory Server |
Access Manager provides authentication and authorization services for end users, based on services configuration, user, and policy data that is stored in a directory |
|
Dynamic application data |
None |
Access Manager does not persistently store application data such as session state |
- © 2010, Oracle Corporation and/or its affiliates