4.3.
Managing Applications
Up one level
This section covers the administrative tasks of deploying and undeploying applications. After deploying an application to your job service, it becomes available for execution by remote clients. Note, however, that clients usually must satisfy additional business constraints, such as having an appropriate service level agreement or account, before they can execute deployed applications.
The GRIA Basic Application Services software is provided with a set of tutorial applications. These are made available during installation of the software. The web based Administration Interface provides the location of these files during the installation process, and guides you through the simple process of application deployment.
In addition to the tutorial applications, it's straightforward to develop new applications and deploy these in the same way.
This section assumes that you have all necessary files for application deployment and that any required executable applications have been installed according to the application documentation. If you are installing the tutorial applications, you have all the files you need. If you are deploying your own applications, first see Writing Application Scripts for details of the files you need to produce before application deployment.
Deploying applications
Having obtained or created the files and scripts needed for application deployment, the application can now be deployed to the job service. To do this, make sure that Tomcat is running then, using a web browser, log into the GRIA Basic Application Services administration page. This can be found at http://<servername>:8080/gria-basic-app-services. Make sure you enter the appropriate security credentials and adjust the URL for the administration page, according to your server setup.
From the administration page, select the Job Service link, as shown below.
Link to the Job Service Administration Page
This displays the Job Service Admin page. In the Applications section, enter the location of the directory containing the files and scripts needed for deployment. Then click the button.
This displays the Application properties for the application. You may optionally enter arguments for the
application wrapper script, which will be supplied in addition to any user-specified arguments. Select the preferred resource manager for this application (LocalExecution is the default). Finally, resource manager directives may be supplied, as a JSDL (XML) fragment (see example provided).
Once all application properties have been set, click the button.
This completes deploying an application to the Job Service.
Undeploying applications
Undeploying an application is straightforward. First click the button along side the entry for the application you wish to undeploy.
Click the button to undeploy the application.
