Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML How to get logging from a Notification that calls a web service.
When you create a notification you can have it call a web service as its action and map return fields from the web service to your sbm item. These can be tricky to troubleshoot because there isn't a lot of logging that takes place. The log for these events should show in the ns.log file.
CMS-XML How to get more logging when the SBM GSOAP web service is called
You can use the attached registry keys to enable some very basic logging about the soap request and response that gets sent and received from notifications or other web services. This can be particularly helpful when a soap request or response is too large and gets chopped of in the Common log . This logging will show the entire request and response envelope.
CMS-XML Get the following error in the common log using the RESTCaller web service connecting to an HTTPS url.
Get the following error in the common log using the RESTCaller web service connecting to an HTTPS url.
CMS-XML Get the following error in ns.log when scheduled report takes over a minute to run. Exception occured during invoking AE web service 'RunReportXML': Read timed out
Get the following error in ns. log when scheduled report takes over a minute to run. Exception occured during invoking AE web service 'RunReportXML': Read timed out
CMS-XML RLC: How to increase Release Control logging
Newer Versions: C:\Program Files\Serena\SBM\Common\tomcat\server\default\webapps\rlc\ WEB -INF\classes Older Versions: C:\Program Files\Serena\SBM\Common\jboss405\server\default\deploy\rlc.war\WEB-INF\classes Find the section for the logging you want to increase:
CMS-XML Increase logging for Serena SBM Single Sign-On
SBM 10.x and earlier: [SBM Install Directory]\Common\jboss405\server\default\deploy\idp.war\ WEB -INF\conf\ log 4j.properties SBM 11.x and later:
CMS-XML Get "Fatal WebException occured with status: NameResolutionFailure." error in application event log every minute or so.
User Message: Fatal WebException occured with status: NameResolutionFailure. Dev Message: Fatal web exceeption Exception Message: Fatal WebException occured with status: NameResolutionFailure.
CMS-XML RLC: How to force the ZMF Connector logs to rollover when they get too big
NOTE: Similar changes can be made for the other ZMF Connector logs. Edit the properties file, by default located at: C:\Program Files\Micro Focus\common\tomcat\8.5\webapps\almzmf\ WEB -INF\classes\ log 4j.properties Comment out these lines, be adding a pound sign (#) to the beginning:
CMS-XML SBM: How to Troubleshoot a SBM to ZMF integration (Turning on ZMF trace logging)
Step 3: ZMF Connector communicates with ZMF. The ZMF connection information is configured in C:\Program Files\Micro Focus\common\tomcat\8.0\webapps\almzmf\ WEB -INF\conf\zmf_resource.properties If the connector cannot reach ZMF, those errors will also be in serenatomcat-stderr.log or serenatomcat-stdout.log (by default located at C:\Program Files\Micro Focus\common\tomcat\8.0\logs)
CMS-XML How to enable logging to show the entire ALF Event that gets sent to the ALF Event Manager.
On the Orchestration Engine server find the following file and edit it in notepad. <SBM Install Directory>\Common\jboss405\server\default\deploy\eventmanager.war\ WEB -INF\alf_ log 4j.properties Locate the following two lines
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs