[Paraview] Paraview in Client/Server Model

[Yeraze.11960501 at bloglines.com]

Ok then... I'm using PAraview 2.4.2, freshly downloaded from the website this
morning, on Linux.  I built a PVX file like the following:

<?xml version="1.0"
?>
<pvx>
  <Option Name="reverse-connection" />
  <Option Name="connect-data-to-render"
/>

  <Process Type="client">
    <Machine Name="rhand-svc" />
  </Process>

  <Process Type="data-server">
    <Machine Name="prism" />
  </Process>

  <Process Type="render-server">
    <Machine Name="meteor" />
  </Process>

</pvx>

And then run "~/paraview/bin/pvrenderserver machine.pvx" and Get
the following errors:

[rhand at meteor pvtest]$ ~/paraview/bin/pvrenderserver
machine.pvx
Connect to localhost:22221
ERROR: In /home/amy/ParaViewReleaseRoot/paraview-2.4.2/VTK/Parallel/vtkSocketCommunicator.cxx,
line 521
vtkSocketCommunicator (0x8062aa0): Can not connect to localhost
on port 22221


ERROR: In /home/amy/ParaViewReleaseRoot/paraview-2.4.2/Servers/Common/vtkPVClientServerModule.cxx,
line 574
vtkPVClientServerModule (0x805f668): Server error: Could not connect
to the client. localhost 22221

ERROR: In /home/amy/ParaViewReleaseRoot/paraview-2.4.2/Servers/Common/vtkPVClientServerModule.cxx,
line 583
vtkPVClientServerModule (0x805f668): No GUIHelper set, can not exit
application




--- Amy Squillacote <amy.squillacote at kitware.com wrote:

No, that's what documentation is currently available.  Copy the 
> example
XML file shown, replacing rs_m1 and rs_m2 with the names of 
> the machines
in your render server.  You will need one Machine XML 
> element per machine
in your render server.  As for specifying a 
> reverse connection, you can
just specify --reverse-connection (or 
> -rc) on the command-line as in previous
versions of 
> ParaView.  Alternatively, you can include it at the top of
the .pvx 
> file (just after the <pvx> flag) using <Option Name="reverse-connection"
/>.
> 
> - Amy
> 
> At 09:56 AM 1/10/2006, Yeraze.11960501 at bloglines.com
wrote:
> >Surely there must exist more documentation that this.  As I alluded
to in
> >the previous email, I've already seen that.  Not only does this
not give any
> >information on what's required in those fields, but it doesn't
give 
> >any information
> >on how to setup Reverse Connections.
> >
>
>
> >
> >--- Amy Squillacote <amy.squillacote at kitware.com
> >wrote:
>
>
> >At 09:27 AM 1/10/2006, Yeraze.11960501 at bloglines.com wrote:
> >
>
> > >I
> >want to load paraview in a distributed client/server fashion where
the Data
> >
> > > >Server is hosted on an SGI Irix System, the Render Server
is run on a
> >high-end
> >
> > > >Linux Machine, and the Client is a Windows
Desktop.  I've found
> >references
> >
> > > >to this PVX XML file that
I need to create for such a thing,
> >but documentation
> >
> > > >for
this seems to be rather, how do you say, "Nonexistant".
> >
> > > >
> >

> > > >So, what would
> >
> > > >a typical PVX file look like for a setup
like
> >this?  I'm using Paraview 2.4.1,
> >
> > > >and I'll need to use
Reverse Connections
> >between the Windows Box & the 2 *nix
> >
> > > >systems,
although the 2 *nix systems
> >can talk freely.
> >
> > >
> >
> > > This
is described in ParaView's FAQ:
> >
> > > 
> > http://www.paraview.org/Wiki/ParaView:FAQ#How_do_I_specify_the_list_of_machines_in_the_render_server_in_ParaView_2.2_and_later.3F.

> >
> > >
> >
> > > - Amy
> >
> > >
> >
> > >
> >
> > > >Randall
Hand
> >
> > > >Visualization
> >
> > > >Scientist
> >
> > > >ERDC
> >MSRC, Vicksburg MS
> >
> > > >_______________________________________________

> >
> > >
> > >ParaView mailing list
> >
> > > >ParaView at paraview.org

> >
> > > >http://www.paraview.org/mailman/listinfo/paraview
> >
> > >

> >
> > >
> 
>