Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML Audit Log Purge History does not Clear
Audit Log Purge History does not Clear
CMS-XML High CPU on database for Application Repository at midnight and also when selecting to purge the "Audit History log"
At midnight the SBM system runs SQL statements in the database against the TS_AUDITENTRY table to check how many records are in the " Audit History log ". If there are a large number of records in the Audit History log, this calculation can run for a long time and can affects the performance of the SBM database for the Application Repository. If the Repository database is stored on the same server as the AE database, the user front-end may also be affected.
CMS-XML Purging the audit log history impossible to cancel permanently on SQL Server and can cause deadlocks with Oracle - java.exe CPU 100% even after restarting
... Application Repository Log ERROR ... org.hibernate.util.JDBCExceptionReporter -- ORA-00060: deadlock detected while waiting for resource [QuartzScheduler_Worker-1]
CMS-XML SBM 11.4.2 Hotfix 3: Ability to turn on/off the automatic Audit Monitoring purge (workaround for DEF320998)
ENH335067: As a workaround to DEF320998 (High CPU on database at midnight and when selecting to purge the " Audit History log ") which cannot be addressed in a patch, this enhancement will give the ability to turn on/off the automatic Audit Monitoring purge . After this hotfix is installed, the mashupmgr.cfg will have option called "AR_MONITORING_ENABLE" which will be set to "false" to disable the automtic purge.
CMS-XML Disable Audit Monitoring in Application Repository
By default, the audit monitoring feature logs Application Repository events such as when items were added to or purged from the repository, as well as deployment and promotion activities. This log is displayed as part of the Purge Audit History tab. Audit monitoring can cause high CPU usage when SQL statements are run against the repository or during audit history purges .
CMS-XML Fails to get the snapshot list if last promote activity was deleted and purged
2. In the activity view, delete the promote activity. 3. In the Audit Log view, purge all history items 4. Refresh the snapshot view
CMS-XML Vul ID: V-69375 / STIG ID: APSC-DV-000680 - The application must provide audit record generation capability for HTTP headers
Given a need to audit all web traffic for some set of HTTP headers, setup SBM to proxy all connections with IIS. The proxy all connections with IIS will force all web connections to Tomcat to go through IIS. Thus, IIS will provide the logging for this STIG.
CMS-XML How to output logs of login access attempts
If you are interested in adding a separate access log then please like the following Idea on the Micro Focus Community: Add security audit logging to gather login info - Micro Focus Community - 2739134 Here are samples of NoSQL commands that will find authentication requests. All login attempts
CMS-XML Application Repository receives Method Not Allowed (405) error when proxied through IIS
Application Repository action performed Clear audit log Edit or remove servers from environment
CMS-XML Deploys fail or timeout: System endpoint assets keep growing in size and slow down the server
1. Create a mashup with orchestrations.. 2. Deploy the mashup a few times to an environment. 3. Open the environment and check the " Audit Log " tab, you will see that the system endpoints keep being modified after each deployment..
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs