Using ASCiimanager in combination with para remote license

[kdroog4pvss]

Using the asciimanager from a remote user interface used to work in 3.11 when the project path on the remote client was set to the share on the server.

Now in 3.15 the following code has been added to the ASCiiman.pnl

Code: Select all

  if (io == 1 && hostname != host1 && hostname != host2 )   //Export only allowed on Server
  {
    ChildPanelOnCentralModal(\\"vision/MessageWarning\\",\\"\\",
    makeDynString(getCatStr(\\"general\\",\\"asciiExportServer\\")));
    return;
  }

We have a para remote license for the remote userinterface to develop for all the distributed wincc oa servers of the project. We are currently making the transition from 3.11 to 3.15.

Since the winccoa server does not have a para license, i am not sure how to solve this. Can i safely turn this code snippet into comment from the ASCiiman.pnl?

[fmulder]

You need a para license to open the Gedi. The Ascii manager is a standalone commandline tool that you could use from a command prompt. (so no para or para remote required)
The commandline options are very simple. What I sometimes do is : 1) Hack the 'Start' button and 2) add a DebugN() to show the commandline that this panel does.
Then go to a command prompt and execute this newly found commandline

I'm note sure whether you can do export or import on a client. Please try and let us all know

good luck

share the fun
Frenk Mulder

[adaneau]

Hi,

Using Frenk solution + -data serverhostname -event serverhostname with good hostname should also work from a remote client I think. ASCII manager just needs to know where are running data and event.

BR
Alex

[fmulder]

Kees used to use his ParaRemote license on his client because his server did not have a para license (and thus could not start a gedi).
But now he can just create a batch file on his server(!) and wont need any para(remote) license.

Share the fun
Frenk Mulder

[kdroog4pvss]

Hi guys,
I have set my project path of the remote client to the UNC path on the server. Running the ascii manager from the remote client seems to work just fine. We have been doing this in 3.11 quite a long time.
Running the ascii manager from a remote client takes quite some extra time compared to running it directly on the server.

It seems to me the para remote function is not taken properly into account by the ASCIIman.pnl.

I do like the suggestion of sending the command to the server. I will try to take a look at that in the future.

[leoknipp]

Doing the ASCII export from a remote client is officially not supported.
An ASCII export must be done on the server. For starting the ASCII export (e.g. via the command line) you do not need a license.
Therefore you can just connect to the server, open a command shell on the server and start the ASCII export.

Best Regards
Leopold Knipp
Senior Support Specialist

[Gertjan van Schijndel]

If a remote client is used to start the ascii export it is difficult to determine if the db directory of the project is the actually used database (or an older copy or even a completely different one).

If your project UNC paths are always paths to the server project, you could allow exports from these remote clients.
Another options is to use ssh (or for windows PsExec) to execute the export on the server.

[kdroog4pvss]

Thanks, Gertjan for your explanation. I will take a look at it, combining Frenk's tip with yours.
Since we have a UNC path to the actually used database, i will override the restriction for the remote client for now.

[leoknipp]

As written in my posting doing an ASCII export from a client is officially not supported.
If this solution is used there is no support for it and for any issues caused by this configuration.

Best Regards
Leopold Knipp
Senior Support Specialist