To Reconfigure and Redeploy Access Manager

1. If you chose to upgrade your web container software, as described in Upgrading Access Manager Dependencies, make sure the upgrade is complete

2. Make sure that the administrative instance of your web container is running, and is in a mode supported by the amconfig.bat file, as indicated in the table below:

   Web Container	Supported Mode	Default Port Number
   Application Server (8.x): Java ES 4 and 5	SSL (secure)   non-SSL	4849
   Web Server (7.0):  Java ES 5	SSL (secure)	8989
   Web Server (6.x): Java ES 4	non-SSL	8888

3. If the web container is running in SSL mode, make sure that the container's SSL certificates have not expired and are still valid.

4. If Access Manager is deployed in Release 5 Web Server, disable all Java ES components depending on Access Manager that are running in the same instance as Access Manager.

   These components would likely be components such as Portal Server or Sun Java Communications Suite; Communications Express, Instant Messaging, or Delegated Administrator. The procedure is as follows:

   1. Log in as administrator at https://host:8989

   2. Go to Edit Virtual Server.

   3. Select the Web Applications tab.

   4. Select all Access Manager dependent applications.

   5. Click Disable.

   6. Click Save.

   7. Click deployment pending | Deploy Config.

      The configuration change will propagate to the Web Server instance

5. Check that Directory Server and the appropriate web container are running.

6. Set the configuration parameters in the AMConfigurator.properties file.

   Some of the parameter values can be migrated from the AMConfig.properties file and others are more specific to the upgrade procedure, as shown in the following table.

   Parameter	Value
   Upgrade Parameters
   DEPLOY_LEVEL	Set to 26 for undeploy  Set to 1 for reconfigure and deploy
   DIRECTORY_MODE	Set to 5 (Existing Upgrade)
   AM_REALM	Set to disabled. Because Realm Mode is disabled, Legacy Mode is therefore enabled
   JAVA_HOME	Set to the JDK Release 5 directory
   WEB_CONTAINER	Set to the value appropriate to the web container type you are using and fill out only the corresponding section of the configuration file.
   WS61_INSTANCE (If using Web Server as the web container)	Set to https-hostname.domain where the value above matches the instance name in install-dir\webserver The value is case-sensitive.
   AS81_INSTANCE (Using Application Server 8.x as the web container)	Set to Application Server.x instanceName Default: server
   AS81_INSTANCE _DIR (Using Application Server 8.x as the web container)	Set to Application Server.x domain directory for the instance Default: AppServer8Config-base\domains\domain1
   AS81_DOCS_DIR (Using Application Server 8.x as the web container)	Set to Application Server.x docroot directory for the instance Default: AppServer8Config-base\domains\domain1\docroot
   AS81_ADMIN_IS_SECURE  (Using Application Server 8.x as the web container)	Set to false Default: true
   Migrated from AMConfig.properties
   SERVER_PROTOCOL	com.iplanet.am.server.protocol
   SERVER_PORT	com.iplanet.am.server.port
   SERVER_HOST	com.iplanet.am.server.host
   DS_HOST	com.iplanet.am.directory.host
   DS_PORT	com.iplanet.am.directory.port
   ROOT_SUFFIX	com.iplanet.am.defaultOrg
   CONSOLE_DEPLOY_URI	com.iplanet.am.console.deploymentDescriptor
   SERVER_DEPLOY_URI	com.iplanet.am.services.deploymentDescriptor
   PASSWORD_DEPLOY_URI	com.sun.identity.password.deploymentDescriptor
   AM_ENC_PWD	am.encryption.pwd

   For other parameters, provide the same values that were used in the Release 4 configuration that you are upgrading, unless you are changing web container or passwords. For example, if you have upgraded Web Server to Release 5, provide the values from the following table.

   Parameter	Value
   WS_CONFIG	The name of the Web Server configuration: configName
   WS_INSTANCE	https-configName
   WS_HOME	WebServer7-base
   WS_PROTOCOL	http or https
   WS_HOST	Fully qualified host name on which Web Server instance is listening for connections
   WS_PORT	Port on which Web Server instance is listening for connections
   WS_ADMINPORT	Port on which Web Server administration instance is listening for connections
   WS_ADMIN	Web Server administrator user ID
   WS_ADMINPASSWORD	Web Server administrator password

7. Run AccessManager-base\setup\amconfig.bat to undeploy Access Manager.

   1. Set the value of DEPLOY_LEVEL to 26 in the AccessManaget-base\setup\AMConfigurator.properties file.

   2. Change to the setup directory.

      cd AccessManager-base\setup

   3. Run amconfig.bat file.

8. Run AccessManager-base\setup\amconfig.bat to reconfigure Access Manager and deploy into web container.

   1. Set the value of DEPLOY_LEVEL to 1 in the AccessManager-base\setup\AMConfigurator.properties file.

   2. Change to the setup directory.

      cd AccessManager-base\setup

   3. Run amconfig.bat file.