Migration from 3.7B and 3.7.1 and Having to Reboot all Endpoints

We are planning to migrate Framework from 3.7B to 3.7.1 very soon. We have been told by Tivoli that this would require a reboot after the Endpoint code got updated, or else 3.7.1 features such as TAP account authentication at the BDC won't be available. The Endpoint may continue to work but will not have 3.7.1 features because of changes in the TivoliAP.dll code. Is this true?

In our environment, the TAP account is a domain account and it authenticates with the PDC every time TAP initializes causing problems such as DM starting with the wrong authority. We are hoping to minimize these problems by moving to 3.7.1 (Patch 60). But rebooting each Endpoint (there are 15,000+ of them) would take time. Has anyone upgraded without rebooting?

Contributed By: Cooper Begis
You will have to reboot, there is now way around it. You will get 'spawn_impl' errors if you do not and you will have more issues than just DM, assuming that you are running other Tivoli apps.

If you have some time, to complete your migration, you can get a copy of the new 'TIVOLIAP.DLL' and distribute it to your environment. Reboot the machines on a schedule that works for you and then work on the upgrades of the Endpoints. The latest DLL is compatible with the older versions of the Endpoint. This will allow you to continue with Endpoint functionality and not have to worry too much about timing of the Endpoint upgrade and the reboot. You have already completed the reboot to load the latest DLL. If you take this method, the Endpoint will function immediately after the upgrade and you will not have to coordinate with a reboot.

You will have a new option with TAP to authenticate to a BDC rather than a PDC, this may also help alleviate some of your errors.

You also need to be aware of the upgrades and DM. During an upgrade, the Endpoint recycles and if DM is running, you may get a failure. This is due to the upgrade timeout and the amount of time it takes for the Endpoint to move to a secondary port, 9496. DM has 9495 locked even though the Endpoint was bounced. I believe there is a patch coming out to resolve this, it may be out already.