Sun Java Enterprise System 5 Upgrade Guide for Microsoft Windows

Access Manager Dependencies

Access Manager dependencies on other Java ES components can affect the procedure for upgrading and reconfiguring Access Manager software. Changes in Access Manager interfaces or functions, for example, could require upgraded version of components upon which Access Manager depends. The need to upgrade such components depends upon the specific upgrade path.

Access Manager has dependencies on the following Java ES components:

Web Container Upgrade Scenarios

Access Manager can be deployed in a web container provided by either Web Server or Application Server. As a result, the upgrade of Access Manager to Release 5 can be complicated by the possibility of also having upgraded to Release 5 the web container in which it is deployed. In this regard, there are a number of web container upgrade scenarios possible, enumerated in the following table:

Table 9–3 Web Container Upgrade Scenarios for Access Manager Upgrade

Scenario 

Web Container in which Access Manager is Originally Deployed 

Web Container in which Access Manager is Deployed After Upgrade 

Applicable Access Manager Upgrade Paths: Upgrades From 

Scenario 1 

Web Server 6.x

Web Server 7.0 

Release 4 

Scenario 2 

Application Server 8.1 

Application Server 8.2 

Release 4 

You must be careful when upgrading Access Manager (for example when using the amconfig.bat) to provide values appropriate to the upgrade scenario in Table 9–3that applies, especially when there is a major version upgrade of the web container.