Switch to a different version of the application server / JVM
- Stop the service
- Delete the
my_appservdirectory structure - Use Service initialization to create the directory structure for the new versions.
- Start the service
Note: If you have made some modifications under my_appserv, e.g.:
- start/stop/watchdog script modifications
- application server files
- environment files
- etc.
remember to keep the modified files somewhere BEFORE deleting the my_appserv directory tree.
Note: Your applications and files are kept outside of my_appserv directory tree in My App Server default configuration. Thus removing my_appserv directory will not remove your data. Consider your changes if you have made modifications to the default configs.
Note: It is also possible that some applications are integrated with the application server and are storing data under its directory structure. Consider this BEFORE removing my_appserv directory tree.
Remember it is a backend server
This service accepts connections on a private interface only. Thus it can not be directly contacted by external hosts.
Typically a frontend web server ( Apache HTTPd ) is configured to pass the required requests to the backend.
The frontend might handle some of the requests that it receives on its own. E.g. requests for:
- static resources - HTML/CSS/JS/Image files
- CGI scripts
- SSI ( Server Side Includes )
- PHP files ( handled by
mod_php)
and pass other requests to different backends. E.g certain parts of the URL space might be mapped to:
- JSP/Servlet engine - Tomcat which is configure to run via MyAppServer
- PHP-FPM backend providing specific PHP version support
See the section Servlet/filter mappings for an example on how to define the needed proxying rules .
It's a service suitable for production deployments
My App Server offers a production environment for hosting your services.
Development and testing should be done locally, not on this service.
See Restart Limits for some restrictions which apply.