Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
334 views

Executing runbook taking long time from OMI to OO

Customer have observed that the runbook execution from OMI to OO is taking about 15 secs on an average. For example when OMI needs to execute a runbook for an event it calls the OO webservice which takes this long to completely establish the connection. OMI will wait for this connection to be completed before initiating a new request for a new event. 

Below is an excerpt from the OMI log.
2017-08-24 05:34:52,060 [pool-29-thread-1] (InfraSettingsReader.java:53) DEBUG - getVariable customer[1] variable[oo.url] value [https://storchdat01.accenture.com:8443]
2017-08-24 05:34:52,060 [pool-29-thread-1] (InfraSettingsReader.java:53) DEBUG - getVariable customer[1] variable[settings.pm.settings.run.book.exe.run.suspend.flow.url] value [/PAS/app?service=RCLinkService/FlowLinkDispatch&sp=SRESUME]
2017-08-24 05:34:52,060 [pool-29-thread-1] (AdapterMethodInterceptor.java:51) DEBUG - Adapter Flow: SettingsManagerAdapter.getRunBookSuspendFlowURL(1) finished successfully and returned: https://storchdat01.accenture.com:8443/PAS/app?service=RCLinkService/FlowLinkDispatch&sp=SRESUME. Total time: 0.0 seconds
2017-08-24 05:34:52,060 [pool-29-thread-1] (ServiceInvoker.java:61) DEBUG - External Service Flow: RunBookInternalService.runRunBook(com.hp.bsm.platform.oo.integration.model.dto.operation.orchestration.RunBookFlowDTO@947d793a, true) finished successfully and returned: com.hp.bsm.platform.oo.integration.model.dto.operation.orchestration.RunBookRunIDResult@1941ee12. Total time: 13.393 seconds
2017-08-24 05:34:52,060 [pool-29-thread-1] (ServiceInvoker.java:66) INFO - External Service Flow: Execution of RunBookInternalService.runRunBook took 13.393 seconds
2017-08-24 05:34:52,060 [pool-29-thread-1] (BusinessServiceInvoker.java:83) DEBUG - Business Service Flow: IRunBookBusinessService.runRunBook(com.hp.bsm.platform.oo.integration.model.dto.operation.orchestration.RunBookFlowDTO@947d793a, true) finished successfully and returned: com.hp.bsm.platform.oo.integration.model.dto.operation.orchestration.RunBookRunIDResult@1941ee12. Total time: 13.409 seconds
2017-08-24 05:34:52,060 [pool-29-thread-1] (BusinessServiceInvoker.java:88) INFO - Business Service Flow: Execution of IRunBookBusinessService.runRunBook took 13.409 seconds

Runbook took 13.409 seconds, which customer do not accept.

From OMi team they said Omi just initial a request and then get result and give the total time. So the root cause should be at OO side.

But from the Log, how can I know what OO steps exatly take the time?  is it possible be caused by Omi?

Anyone give a clue?

0 Likes
2 Replies
Respected Contributor.. __Daniel__________ Respected Contributor..
Respected Contributor..

Re: Executing runbook taking long time from OMI to OO

Hello,

      This is a known problem, as OMi uses the old API from OO 9.x. There is a hotfix available to increase the speed of execution.

       Please open a ticket with support so we can analazy the issue and validate if the fix applies on this situation.

Thanks

Daniel

0 Likes
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Re: Executing runbook taking long time from OMI to OO

Hello Daniel,

    Thanks you great for your help, do you know where is the hotfix or the information of the hotfix, I will look for this hostfix.

     and may I have you mail?

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.