Rogue BPM Cache?

This is what I have in my notes, hope it helps Jose. Let us know what you find!

Q: Where are the BPMs compiled to and stored?

A: As of 10.1.400, the default storage location is the SQL BLOB within the Epicor database itself. This means there are no files that need to be transferred around when copy/restoring databases as the BPMs are already compiled and active within the database itself.

Q: What other custom solution options is stored in the database?

A: All items that were traditionally compiled to the file system are now stored within the SQL BLOB in the Epicor database. This includes: Method Directives, Data Directives, Updatable Business Activity Queries (UBAQ), Generic Imports, Electronic Data Interface (EDI), Posting Engine (PE) Rules and Product Configurator (PC).

Q: Do I need to recompile these after a Live to Test restore?

A: No, the BPMs, Compiled Dashboards and other Custom Solutions will move along with the database and are already compiled.

Q: How can I see the uncompiled code?

A: The intermediate files are stored on the file system. By default they are located under the inetpub\wwwroot{AppPoolName}\Server\BPM folder. These are strictly for viewing only and any changes to these files will not impact the Epicor system. This can be used to help you troubleshoot any of the wizard generated code from the modules listed above.

Q: Where is the SQL BLOB data actually stored?

A: It is stored in a binary (not human readable) format in the Ice.Customization and Ice.CustomizationStore tables.

1 Like