RE: [Soaplab-users] Remote deployment of Applab

[Marc L. <Mar...@de...>]

> I have been trying out the possibility to run an Applab=20
> server on a differnt machine from my Tomcat webserver.=20
> However, Tomcat seems to reject the incoming requests due to=20
> security settings. Which Tomcat or Soaplab settings do I=20
> change to fix this? Is there any possibility to get Tomcat to=20
> use a specific user name and password when remote accessing=20
> Tomcat? If not, this means I have to open the Tomcat server=20
> for anonymous remote administration from anywhere, does it not?
>=20
> Would appreciate any help.
Hi Anders,
Suppose you have soaplab running on machine A and you want to wrap a =
soaplab service around a command that can not be run on machine A, but =
only on machine B.=20
This is possible by running AppLab on machine B and saying to soaplab on =
machine A that the service has to be executed on B. This message goes =
via the IOR.
1) Install soaplab on machine B.
2) In Server.cfg set ooc.iiop.host =3D <machine B>
3) In ws/add-services.pl two blocks have to be commented out:

...

# --- where is Axis-in-Tomcat directory
#unless ($opt_x) {
#    my $tomcat =3D ($ENV{'CATALINA_HOME'} or $ENV{'TOMCAT_HOME'} or
#                 die ("Axis-in-Tomcat directory must be specified. Use =
-x <axis-lib>.\n"));
#    $opt_x =3D File::Spec->catdir ($tomcat, 'webapps', 'axis', =
'WEB-INF', 'lib');
#}

...


# --- copying derived classes (to Tomcat, and to 'dynalib')
#foreach my $file (glob (File::Spec->catfile ('lib', '*'))) {
#    my $in_tomcat =3D File::Spec->catfile ($opt_x, basename ($file));
#    die ("File $in_tomcat already exists.\nUse -f to force overwriting: =
add-services -f ...\n")
#       if !$opt_f and -e $in_tomcat;
#    copy ($file, $in_tomcat) or die "Can't copy $file to $in_tomcat: =
$!\n";
#    copy ($file, File::Spec->catdir ($dest_dir, 'dynalib'))
#       or die "Can't copy $file to $dest_dir/dynalib: $!\n";
#}

...


4) First of all, you should have deployed the services on machine A, the =
normal way. The distribution file is copied to machine B and added as =
such:
ws/add-services.pl -d ./ /your-distri-file.tar.gz
The most important things here are that the Applications.xml from the =
distribution file is merged to the existing one and that the IOR files =
are created. Now start Applab on machine B in the usual way.

5) Make IOR available to machine A
This can be done in two ways:
 5.1) Copy the generated ior file for your service from machine A to =
machine B (in the appropriate folder, /IOR/analyses/)
 5.2) Make the machine A ior file for your service available via the web =
(e.g. by creating soft link to /var/analysis-interfaces/IOR/analyses). =
In the server-config.wsdd file of machine A change the line:

  <parameter name=3D"applab_factory" =
value=3D"file:/blah/blah/IOR/AppLabFactory.ref"/>

To:

<parameter name=3D"applab_analysis" value=3D"http://machine =
B/link_to/my::service.ior"/>

And, finally restart tomcat.

HTH,
Marc