|
Application Administration
Application Deployment
The first step of deploying your application on the server is to create an application entry on the server.
The JNetStart server stores information about the deployed applications and their states in
the applications registry JNS_ROOT/jns/registry.properties.
If using Internet Explorer or Firefox browse to the home page of the JNetStart server, for example if your server is started on
hostname browse to http://hostname. Click on the JNS Admin Console icon to
start the console and login using a user account with application administration privileges. If using the
Accendia Browser browse to jns://hostname/jns.html and login using the form for the administration
console.
In the Administration Console click on the Create Application icon and enter the application name and the application description.
We will deploy the SwingSet2 demo application packaged with the JDK in
JAVA_HOME\demo\jfc\SwingSet2:
Click the Create button to create the application entry on the server side. The console
will automatically switch to the Edit Application screen.
In the application edit screen you'll deploy the application jars. Click on the Add Jar
button to open an Open File dialog. Browse to the location of the SwingSet2.jar, select
the jar file and click the Open button. This will upload the jar file on the server side:
The SwingSet2 sample application is now deployed on the server and its state is Stopped.
Application Lifecycle
To start the deployed application switch to the Applications Administration screen,
select the SwingSet2 application entry and press the Start button at the bottom of the
screen:
The state of the application has changed to Active meaning that remote users can launch
the application.
An application can be in one of the following states:
- Stopped
- A newly created application is in stopped state. Jar files can be added or removed while the
application is stopped. A stopped application can not be launched by remote users;
- Active
- Remote users can only launch applications that are active. Applications with identical names
can not be activated at the same time;
- Retired
- An application in retired state can be used by users that launched the application
when the application was active. A retired application is not accessible to other remote users.
To deploy a newer version of an application follow these steps:
- Create an entry for the new version of the application with the same application name
as the old entry. Create an application description to distinguish the new version from the older one, for
example "Application Name - version number";
- Deploy the application's jars;
- Retire the old version of the application if active. The application is still accessible to the users
that are currently running the application;
- Start the new version of the application;
- Stop the old application when it is not used by any remote user.
This is the Applications Administration screen after redeploying and activating a newer version of SwingSet2:
To revert to the old version of the application:
- Retire the new application;
- Start the old version of the application;
- Stop the new application when it is not used by any remote user.
| 
