PC Command Listener

[brett.elston]

Hi,

As I can see the support for Java applets is being withdrawn from many browsers. We also use the RunPCCommand extensively and are having the same problems.

I have installed the Command listener, it is running in the background, and am trying to get commands to run. I have tried adding the pui["use pc listener"] = true; into the user .js, and also simply as the line preceding a RunPCCommand command. Unfortunately without success.

If you could help please?

Do we need to change the execution string for the RunPCCommand(a new command) or does the PC listener listen for this command now as opposed to trying to run the applet? It currently still seems to try run the applet?

Thanks

Brett

[Emily]

Hi Brett,

Sorry to hear that you're having troubles with this. You should be able to use runPCCommand() or pui.runPCCommand() with the PC Command Listener -- these APIs are identical. If you're having troubles with the PC Command Listener, you should make sure that you have the Listener configured correctly and that it is actually listening. You can right-click on the Command Listener icon to make sure that 'start listening' is selected from the options.

Once the Listener is configured correctly and is listening, you will need to set the following configuration options for your instance:

Code: Select all

pui["use pc listener"]
pui["pc listener port"]

It's important that you include both of these configuration options in a .js file in the following directory: /userdata/custom/js

You will need to set pui["use pc listener"] to true for your instance, as the default behavior is to use the Java applet. You will also need to set pui["pc listener port"] to the appropriate port that your listener is configured for. If this isn't set, the default HTTP port 80 will be used. I've included links to our documentation for these configuration options below:

http://www.profoundlogic.com/docs/displ ... tener+Port
http://www.profoundlogic.com/docs/displ ... C+Listener

After including these configuration options, you may also have to start a new browser session or clear your browser's cache in order for your browser to pick up the changes.

I hope that this helps!

--Emily

[brett.elston]

Hi Emily,

Thank you for all the information. I have tried this but still without success. We are quiet a few releases behind with our Profound and I am wondering if this might be why it is not working?

We have scheduled an upgrade to the latest version for this evening so I will try it again thereafter.

Regards

Brett

[Scott Klement]

First release to suoport the listener was 5.2.0, from December 2015.

[brett.elston]

Thank you Emily and Scott, we upgraded to 5.12 tonight and getting much better results. Thanks always for your excellent support.