Now we run a launcher session.
This first session connects to the hosting service we just started. We create three hosting contracts (one each for DNS, HTTP and Webtrix) so our applications can run:
% launcher
Initialising Nodality...
launcher> connect hosting {warrant:hos01-real-admin.xml}
launcher>
launcher> contractid1=`hosting.createContract dns-contract`
launcher> contractid2=`hosting.createContract http-contract`
launcher> contractid3=`hosting.createContract webtrix-contract`
launcher> echo $contractid1 $contractid2 $contractid3
1 2 3
launcher>
launcher> dns-hosting-warrant=`hosting.getWarrant $contractid1`
launcher> echo $dns-hosting-warrant
<<warrant>>
launcher>
launcher> dump $dns-hosting-warrant hosting-warrant1.xml
launcher> dump `hosting.getWarrant $contractid2` hosting-warrant2.xml
launcher> dump `hosting.getWarrant $contractid3` hosting-warrant3.xml
launcher>
This uses our warrant hos01-real-admin.xml from the node boot-up process. We create a contract for each service and a warrant for each contract, then we dump each one into a file. Then we could mail, for example, hosting-warrant1.xml to the DNS administrator so they can launch their service on our node.
Next we connect to our SAS and create a SAS contract for our service administrators:
launcher> connect sas {warrant:sas01-warrant.xml}
launcher> sas.createContract {x500dn:uid=nik} {boolean:false}
<<warrant>>
launcher> dump $0 sas-warrant.xml
launcher> quit
%
This uses sas01-warrant.xml from the node boot-up process, and the SAS consumer warrant we create is put into a file. All our services will use this consumer warrant, but this is just a shortcut because we know they're owned by the same person.
Nik Silver 2002-03-09