PxWeb Admin API and what it really does on the file based PxWeb

[Hansseman]

PxWeb Admin API and what it really does on the file based PxWeb

1. Does the Admin API start the indexing of the database immediately or does it wait for the worker process to start in the file based PxWeb.
   I fear it waits for the worker process to start and that is by default set in admin interface to 3600 sec.

2. When the Admin API does a “clear cache” does this mean it reloads the aggregation files every time we do an admin api “clear cache”.
   We have over 5 000 aggregation files to load when PxWeb starts up and it takes minutes to load the aggregation files. Reloading of the aggregation files every time you clear the caches does not make any sense. The resources can be used more wisely. At the publishing moment there should be running processes generating menu.xml and the database INDEX, not reloading the aggregation files.
   The Admin API should also have an option to reload the aggregation files as it is done in the PxWeb admin interface.

3. Also the reloading of every aggregation file at every PxWeb startup is not a viable way to do it. This should be solved in some better way.

Please correct me if I am wrong …

Hans