Preparing the application

Before we begin we need to create a launch descriptor, which we will name skeleton-launcher.xml. We do it like this. As usual alter the Jtrix binaries directory to how it on your system. We're using /usr/lib/jtrix:

% jtrixmaker -type beatrix -outfile skeleton-launcher.xml \
     -x500dn o=jtrix,cn=skeleton2 -jardirs /usr/lib/jtrix \
     -jars skeleton2.jar beatrix.jar libjtrix.jar jaxp.jar parser.jar facets1.jar \
     -access ap \
     -codebase ap skeleton2.jar beatrix.jar libjtrix.jar facets1.jar \
     -plugins org.jtrix.project.skeleton2.plugins.LifeCyclePlugin
% 

First we say what type of descriptor we're generating (a Beatrix launch descriptor) and what it should be called. Then there is an X.500 distinguished name (DN) which you might like to change according to your own circumstances, e.g. O=MyCompany,UID=BobJones,CN=skeleton. The other arguments are specific to this application. See Appendix  for more on the jtrixmaker command.

Now we have a launch descriptor called skeleton-launcher.xml.

Before we can launch it we need a hosting warrant (giving us permission to run an application) and a SAS warrant (which allows us to upload and download netlet descriptors, and hence make things generally more convenient. We will assume these are in files hosting-warrant.xml and sas-warrant.xml. See the sections above on how to do this.