Max,
I've seen clients do this in the past and would recommend against it, unless absolutely necessary. It is possible to deploy custom JSPs and servlets into the existing Tomcat instance, but the risks/issues are:
- It isn't supported by Oracle and may cause issues supporting other App functionality (such as web server performance, etc).
- If you want to hook into the OTM security, it will require decompiling existing OTM code (not recommended)
- Any patch to OTM may wipe out your changes and/or require updates to your custom code.
Another way to tackle this is to have your own web server that runs your custom code (i.e. another Apache/Tomcat instance - or whatever you prefer). A couple OTM clients have done this with good success -- allowing them to have custom screens and reduce the impact upon the core OTM installation.
Also, as for the custom tables, ensure these are under a separate schema (i.e. completely different DB user) to ensure they don't conflict with OTM or cause issues with patches/upgrades.
--Chris