API / Java Documentation

[RussCraig]

Hi All,

I've read through a number of posts mentioning various Java functions and ProfoundUI API calls. Is there any form of documentation on these? Where could I find some more info?

For example, in the Version History I saw the following:
•Sessions can now be assigned a unique "workstation id" (i.e. job name) using query string parameter "workstnid".
•The session controller can automatically generate "suffixed" workstation ids when the "workstnid" and "suffixid" query string parameters are used. Similar to "Avoid duplicate names with other workstations" option in Client Access.

How would I go about implementing this?

Thanks.

[Rob]

I have attached a PDF document describing how to use the new Workstation Id parameter in Profound UI.

You would use this to specify the workstation id within the link or shortcut that a user clicks on the start a Profound UI session.

I will post details of other Profound UI APIs to this forum shortly.

[RussCraig]

Thanks for that info, that will help quite a bit.

I have a question though: I added the "workstnid" and "suffixid" to my URL, and the workstnid is functioning properly, but not the suffixid. Here is how my URL is formatted:

//myserver.com/client?workstnid=CLIENTX&suffixid=1

/client is a ScriptAlias that points to /profoundui/start.html.

I can open one session just fine, and it properly assigns the job name "CLIENTX". Now when I go to open a second session using the same link, it gives the error message PUI0031: Device not available.
Cause . . . . . : Device CLIENTX is invalid or in use by another Profound UI session.
Recovery . . . : Specify a unique device id for the session or use the option to prevent duplicate ids by appending a unique suffix.


Any ideas what could be wrong? Thanks.

[RussCraig]

Currently using 2.1.2 and the suffixid is still not working for me. Again, the workstnid works fine, but I still get the duplicate device error. I have followed the directions in the PDF to the letter, but still cannot get this to work.

Are there any ideas as to why this is not working?

Thanks.


edit: I've tested this in IE8 v8.0.7600.16385, as well as Firefox v3.6.3. The error is identical in both.

[David]

We have been able to recreate this problem. It seems to work properly when using anonymous sessions, but not with system sign on sessions. We will advise when an update is available to correct the problem.

[David]

This issue is fixed pending release of version 2.1.3 in the coming days. Check your "Welcome" page from time to time -- you'll get an automatic notification of the update there when it's available.