Wednesday, September 11, 2013

Error Opening Dedicated Application in Chrome

Add to the last issue, I was also facing some issues in launching a dedicated client in Google Chrome, as whenever i was opening it i was getting the error as below : 
Oops! Google Chrome could not connect to localhost:8080

With some of the time spent in debugging this issue, i have found that Google itself given the steps to solve this one. Let me explain how.
When you get this error. There is one link which will appear at the bottom of the browser mentioning as : 
Why am I seeing this page ?

Once you clicked this, click on the link : 
Enable or disable suggestions on navigation errors

There will be below instruction which you will get on clicking the above link as : 

Suggestions for navigation errors are enabled by default. Follow the steps below to turn the feature off.

1. Click the Chrome menu Chrome menu on the browser toolbar.
2. Select Settings.
3. Click Show advanced settings and find the "Privacy" section.
4. Deselect the "Use a web service to help resolve navigation errors" checkbox to disable the feature. Select the checkbox to enable it again.

Also, make sure that you run the genb everytime you compile changes on srf before launching the dedicated client. If this is not done, you will end up with blank screen on the launch of dedicated client.

Keep Exploring !!!



6 comments:

  1. Hi

    I have compiled browser scripts using genb utility and confirmed that srf file created at public/enu folder. But still the open ui dedicated client opens as blank page. Can you pls help in this issue.

    Regards,
    Madhu

    ReplyDelete
  2. Hi Madhu,
    Can you please ensure in your cfg under section [InfraUIFramework], you have below parameter :
    EnableopenUI = TRUE

    If not, please add this and check whether this resolves the issue.

    ReplyDelete
  3. Yeah enable opeUI parameter is set in the cfg. By commenting that line and on launched using IE, I can see the client opens as expected.

    Regards,
    Madhu

    ReplyDelete
    Replies
    1. So with that i suppose the issue is resolved.
      Just wanted to mention that as of now OpenUI is supported to Higher Interactive applications only like eComm. OpenUI will be supporting for Standard Interactive in future release but as of now it do not support SI, so for the SI application like eSales you need to comment that parameter or set it as FALSE.

      Delete
    2. Is it not enabled for call center appln too? Because I can see one of my friend in other project have enabled it in dedicated client.

      Regards,
      Madhu

      Delete
    3. By Default its not enabled. To have OpenUI features you need to turn this parameter to TRUE.
      Since OpenUI do not support SI applications, as similar to your case, if you put this parameter to TRUE, you will see a blank page.
      To Sum it up :
      1) For HI Application : EnableopenUI = TRUE
      2) For SI Application : EnableopenUI = FALSE

      You can identify which application is HI or SI, by looking the value of below parameter under section [InfraUIFramework] :
      HighInteractivity

      Hope this helps.

      Delete