Start a Conversation

Unsolved

This post is more than 5 years old

1190

December 21st, 2009 07:00

Enable client tools in webconsole?

Does anyone know how to enable client tools in the webconsole? So far I've tried adding the following parameter to webconsole.properties file.

com.smarts.clientToolsInApplet=true

Then I restarted the webserver. I'm still not seeing client tools in the webconsole though.

December 21st, 2009 19:00

Did you specify com.smarts.webconsole.sitemod property? If you haven't then webconsole will look for the client tools in BROWSER_HOME/actions/client directory, and won't find any scripts .

 

 

5 Posts

December 22nd, 2009 08:00

I've tried putting my script file in c:\program files\internet explorer\actions\client  but it's still not finding it. I've also used the com.smarts.webconsole.sitemod parameter but that didn't work either. I must missing something somewhere. After changing the webconsole.properties file I'm restarting the SMARTS Servlet Engine service. Is there anything else I need to restart to make this work?

December 23rd, 2009 02:00

ok , I did a hands-on myself. And got stuck in similar situation.

Probably its the way i installed global console, I realized that it did'nt pick up the server setting.

For eg:

in webconsole.properties

i saw smarts.remote.broker= :426

It did'nt pick up localhost (or servername) , just helps in auto populating the attach manager dialogue box with broker name.

in globalConsoleApp.jnlp

I found something similar on the first line

< jnlp spec="1.0+" codebase=http://:8080 href="webconsole/globalConsoleApp.jnlp" >

until i changed the codebase to http://localhost:8080 whatever properties i entered through webconsole.properties did'nt reflect.

And i was not able to see client tool option as this file later loads up webconsole.properties.

See if you have same problem and let me know.

Regards,

Raghvendra

5 Posts

December 23rd, 2009 07:00

Thanks for looking into this for me. I checked my webconsole.properties and globalConsoleApp.jnlp and both have what they should -

After re-reading through the documentation I learned that the default dir for the client tools in Windows is \desktop\actions\client

I created actions\client folder on my desktop and stuck my .cmd file in there and now it works.

No Events found!

Top