Disaster planning for APLS server


We are currently doing disaster recovery planning for the SBM application in our company and we wanted to know what the best strategy is with regards to the recovery of the APLS server. My understanding is that our SBM licenses are tied to the Host ID of the APLS server hosting the licenses so in the event that the APLS server goes down then should we just go to the license portal and make a request to re-host the licenses to a different server?

I'm not sure how long that process takes so I was hoping that you have any suggestions about how we can plan to switch over to a different APLS server as soon as the disaster hits without having to go to the license portal.



  • Suggested Answer

    Actually, if you lost the APLS machine, you would loose more than the licenses. You would also lose your configurations. So, if you configured email notifications from APLS or if you configured named users in APLS, all of that would be lost too.

    I would probably switch your APLS server to use a standard database instead of the built-in database. The license is tied to the "lock code" of the database (not the server). By default, APLS uses a simple built-in database that is installed and stored locally on the APLS machine. That is why it gives the impression as being tied to the APLS machine. If you change your APLS to use SQL or Oracle instead, then, if the APLS machine goes down, it will not impact your keys or configuration. You would still need to get APLS running again, but once you point to the database, you would be ready. 

    Of course, then you have risk if the SQL/Oracle server goes down, but typically the DBA will have plans for that. I would not store the APLS tables inside the same database where SBM stores its tables, but the APLS could use a database on the same SQL/Oracle server as where SBM's database is stored. 

    To configure APLS to use a standard database: DataBase Configuration - AutoPass License Server (microfocus.com)

    The new database will get a new "lock code", so you will need new keys for this switch. To get new keys for the new "lock code", you would use the "rehost" option documented here: https://portal.microfocus.com/s/article/KM000005202