" /> Debugging in Composer - Genesys CTI User Forum

Author Topic: Debugging in Composer  (Read 2120 times)

Offline G3n35Y5

  • Newbie
  • *
  • Posts: 46
  • Karma: 0
Debugging in Composer
« on: November 04, 2014, 07:03:13 PM »
Advertisement
Hi Guys,

Will debugging of ORS workflows happen in following scenario?

Host A: Composer is installed as a plugin on Eclipse. There is Composer bundled Tomcat on this host which is used only for validating the workflows.
Host B (Production host): Tomcat is running as a standalone. Workflows created on Host A are deployed on Tomcat of Host B.

URL of script created in Genesys Administrator for the workflow points to Tomcat of Host B (as the workflow has been deployed here)

Workflow needs to be deployed on Composer bundled Tomcat before using the debugging feature in Composer. While in debugging mode, Composer sends the URL of the deployed workflow (URL of bundled Tomcat on Host A) to ORS and ORS waits for a call to hit this URL (URL of bundled Tomcat on Host A). In reality, the call will never hit URL of host A as the URL mentioned in script object of workflow  is that of Host B. I think debugging will not happen. Any thoughts on this?

Thanks!

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Debugging in Composer
« Reply #1 on: November 04, 2014, 07:23:44 PM »
Composer sends directly to MCP, or should be. That way it interprets VXML directly without Genesys URS working.
What are you trying to achieve? If your LAB environment was ok then move to PRD and test a real call there. If a bug, fix on LAB and put again on PRD, right?

Offline G3n35Y5

  • Newbie
  • *
  • Posts: 46
  • Karma: 0
Re: Debugging in Composer
« Reply #2 on: November 05, 2014, 04:25:10 PM »
Hi Cavagnaro,

What you are saying is correct, but my problem is why I'm not able to use the debugging feature? I want to use this feature to debug my workflow.