![]() Once the update process is complete successfully, the Update Status of the device will display as Up to date in green color on Device Status page. Clicking the Update icon will start the update process in a new tab called Upgrade Console. You can also view the latest available version for each device on Upgrade Assistant > Device Status page.When Access Manager release updates are available for any of the devices, the Update icon on the Device Status page is enabled for the respective devices. Whenever a new Access Manager release is available, you can view the new release details, such as latest Access Manager release version and its description, on the Upgrade Assistant page. ![]() Upgrading Access Manager through Upgrade Assistant On Administration Console Dashboard, click Upgrade Assistant > Device Status.Ĭlick the Register icon associated with the device which you require to register to Update Service. Perform the following steps to register an individual device: You can invoke the registration for an individual device in the following scenarios: Registering a Single Device to Update Service Use the same base URL that you used in Access Manager 5.0 or 5.0 Service Pack 1.Īfter successful synchronization of registration information into Administration Console, in the Access Manager 5.0 Service Pack 2 or later, you can use Upgrade Assistant to receive future Access Manager release updates and to update devices to the latest Access Manager version. Log in to Administration Console and register by using Upgrade Assistant by following the procedure mentioned in Registration Using Local Repository on RHEL. If a repository is created with a name such as xyz.repo instead of nam.repo, then delete the file from all devices. To assign expected ownership: chown novlTo assign file permission on each device: chmod 644 /etc//nam.repo If the /etc//nam.repo file ownership and file permission are not as expected, then run the following commands: Verify /etc//nam.repo has nowlThe sample output will look similar to the following: -rw-r. To restart the Upgrade Assistant agent, perform the following steps: After the certificates are re-pushed, restart the Upgrade Assistant agent by running the restart command to apply the certificate changes. Re-push the connector certificate of devices and keystore of Administration Console. You can change this to the device certificate by re-pushing the certificate. ![]() The Upgrade Assistant agent works with the default certificate. After de-registering, you can re-register. You can de-register the service for all devices or an individual device by clicking Deregister on the Upgrade Assistant page or on the Device Status page respectively. Follow steps in Upgrading Access Manager through Upgrade Assistant. If updates are pending on a device, you can update the device to the latest available Access Manager release version. When a new Access Manager Release is available, you can view the release details in Available Updates table.Ĭlick Device Status to view various statuses of each device, such as whether the device is on the latest version or any update is pending. For more information, see Registering a Single Device to Update Service. If a device is not registered for the update, you can register it on the Device Status page. Auto-registration does not work in a hybrid environment. The new devices are also auto-registered as part of the import process.Īuto-registration while adding a new device into Administration Console works only when the device and Administration Console have the same Access Manager versions installed. When you register to any of these services, all devices get registered to Update Service.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |