NGASI Universal APP Panel Administration and User Guide WebAppShowcase DBA NGASI

Transcription

1 NGASI Universal APP Panel Administration and User Guide

2 2 Universal App Panel Table of Contents Part I Introduction 5 1 Overview Requirements... 5 Part II Administrator 8 1 Login Resellers/Webhosts... 8 Create Reseller... 8 Delete Reseller Runtimes Database Part III Resellers/Webhosts 15 1 Login Create User Edit User Delete User Management Part IV Users 19 1 Login Applications Deploy New Deploy From... List 29 Virtual Hosting Delete Deployed... Application 30 File Privileges Delete Application... Archive 30 3 Configuration Restart 5 Examples Programming... Language/Framework 33 JAVA CfWheels RAILS GRAILS Play Scala/Lift Django Railo

3 Contents 3 PHP/Zend Other Scripts Troubleshooting NOT FOUND java.lang.noclassdeffounderror:... java/lang?stringbuilder 35 Part V Rest API 38 1 Administrator Web Host/Reseller Create User Update User Set Web Configuration Clients Memory... Usage 39 3 User Deploy Application Install Complete Success Upload Application Install Complete Success Set Password Index 0 3

4 I

5 Introduction 5 1 Introduction NGASI Universal App Panel enables drag-and-drop deployment of standard web applications on a local machine, VPS, and remote servers. 1.1 Overview The first true web application panel. Enabling web providers capabilities for end users to easily deploy and manage their web applications. NGASI Universal App Panel provides great flexibility by supporting several programming languages and frameworks. This include JAVA, RAILS, GRAILS, Play,Scala/Lift, Django,Railo (CFML), CfWheels, PHP/Zend and other scripting languages. NGASI Universal App Panel is architected for an application centric environment. This enables fine grain configuration, management, and control of each deployed application. 1.2 Requirements NGASI Universal App Panel requires a valid installation of NGASI AppServer Manager. A valid and up-to-date license for NGASI AppServer Manager and NGASI Universal App Panel is required. Windows Requirement Apache Web server is used instead of IIS as a proxy to accounts runtimes for RAILS, PHP/Zend and other scripts. Configuring Apache Web Server may be done Globally or on a per-user basis. NOTE: Microsoft httpcfg.exe or netsh.exe utility must already be installed on the Server. First the IP Address for Apache to listen to must be specified in the wsportal. properties. Add an entry for "win_apache_listener_address" with a valid IP address that will not be used by IIS. NOTE: If the user domain relies on the local DNS server, then the DNS Zone

6 6 Universal App Panel settings would need to be updated in the site's hosting Control Panel (such as Plesk) to reflect the IP Address associated with Apache. NOTE: The Apache Web Server used is automatically installed by NGASI AppServer Manager.

7 II

8 8 Universal App Panel 2 Administrator 2.1 Login The Administrator "admin" is the NGASI Universal App Panel super user. It is used for managing all accounts, which includes Resellers and Users. The host name and port should be the same as NGASI AppServer Manager. So assuming the default HTTPS port 8663 and host name localhost: Login URL: The login Administrator is "admin" and the default password is the same as the "admin" password for NGASI AppServer Manager. The default "admin" password is "coolgeek". To change the "admin" password requires login in to NGASI AppServer Manager ( 2.2 Resellers/Webhosts Use this feature to manage Resellers (Webhosts). Resellers manages the end user accounts. By default the "admin" account is also a built-in Reseller account that cannot be removed. If you just want the "admin" account to function as a Reseller for all User Accounts, then skip to the Resellers/Webhosts section Create Reseller Click the "Create Reseller" to create Reseller Accounts. Select a Reseller in the Select-box. Then click the "Add" button. The Resellers listed in the Select-box are derived from the installed Control Panel. Plesk

9 Administrator 9 A Plesk Client or Reseller Account is considered as a NGASI Universal App Panel Reseller Account. cpanel A cpanel account with cpanel Reseller privileges is considered as a NGASI Universal App Panel Reseller Account. By default, cpanel users are owned by "root". System User Reseller If an available Reseller is not in the "Available" drop-down list, you may create the Reseller by entering the desired name. Since this Reseller is not affiliated with any Control Panel privileges, this Reseller will be able to create System User. This Reseller can only create System Users that does not already exists. Once the NGASI Universal App Panel Reseller Account is Added, the Reseller should appear in the "Reseller List". The Reseller Login and management is detailed in the Resellers/Webhosts section. As the Administrator, you can login directly to the Reseller Account by clicking on the corresponding icon in the "Reseller List" Delete Reseller NOTE: Deleting a Reseller will automatically Delete any User Accounts created by the Reseller. Also the embedded "admin" Reseller cannot be Deleted. Select one or more Resellers in the "Reseller List". Then Click the "Delete User" button to delete the selected Reseller Accounts. 2.3 Runtimes NGASI Universal App Panel supports a number of Runtime environments. JAVA JDKs: 1.7.x 1.6.x 1.5.x

10 10 Universal App Panel Application Servers: Tomcat GlassFish JBoss RAILS Supported Ruby versions include Supported JRuby versions include Supported RAILS versions include Application Servers Passenger Mongrel GlassFish GRAILS Supported GRAILS versions include 1.3.x 1.2.x Application Servers GRAILS Embedded Tomcat Play Supported Play versions include 1.x 2.x Application Servers Play Embedded Netty Scala/Lift

11 Administrator 11 The Simple Build Tool (SBT) is used to build and deploy Scala/Lift Applications. Application Servers Scala/Lift Embedded Jetty Django Supported Python versions include 2.6.x 2.5.x Supported Django versions include 1.2.x Railo (CFML) Supported Railo (CFML) versions include 3.1.x Railo (CFML) Supported CfWheels versions include 1.x and higher PHP/Zend PHP-5.3;Zend-1.10.x PHP-5.2;Zend-1.10.x Quercus (JAVA) Other Scripts Apache 2.4 Database If available, a Database is automatically created for the application to use. JAVA If a DataSource name is specified, the application server is configured with a JNDI DataSource entry containing the database access information. RAILS

12 12 Universal App Panel The "production" database configuration is populated in the database.yml file. db:migrate is automatically run on the application upon deployment. GRAILS The "production" database configuration is populated in the DataSource.groovy file. Play The "production" database configuration is populated in the application.conf file. Scala/Lift The database configuration is populated in the default.props file like so: src/main/resources/props/default.props db.driver= db.url= db.user= db.password= db= db.host= Django The "default" database configuration is populated in the settings.py file. And the "syncdb" command is executed. During installation of Django apps, a superuser is created. Below are the default credentials: User: admin Password: coolgeek Railo (CFML) The database configuration is populated in the railo-web.xml.cfm file. CfWheels The DataSource configuration is set. The DataSource name is set to "wheels". There are various ways to make one or more Databases available to user applications. 1)NGASI Universal App Panel will check for MySQL access configuration in one of the following files: /root/.my.cnf [client] user="root" pass="coolgeek" /etc/psa/.psa.shadow coolgeek

13 Administrator 13 If found, NGASI Universal App Panel will attempt to open a test connection to MySQL with the configuration information. If successful, MySQL is marked as being available. 2)Login to NGASI AppServer Manager as admin. Click on "Services". Click on "Databases". Configure databases accordingly.

14 III

15 Resellers/Webhosts 15 3 Resellers/Webhosts Use this feature to manage User Accounts. User Accounts are the end users that deploys and manages the applications. 3.1 Login Login Info: The host name and port should be the same as NGASI AppServer Manager. So assuming the default HTTPS port 8663 and host name localhost: Login URL: The user login information would be the same as for your Control Panel (Plesk or cpanel/whm). 3.2 Create User Click the "Create User" to create User Accounts. Select a User in the Select-box. Then click the "Add" button. The Users listed in the Select-box are derived from the installed Control Panel or an existing system account with execute privileges. Plesk A Plesk Domain user is considered as a NGASI User Account. cpanel A regular cpanel account with Domain privileges is considered as a NGASI User Account. System User A System User account belonging to a Reseller other than "admin", has a naming convention similar to: <RESELLER_NAME>1 <RESELLER_NAME>2

16 16 Universal App Panel Once the User Account is Added, the User should appear in the "User List". The User Login and management is detailed in the Users section. As the Reseller, you can login directly to the User Account by clicking on the corresponding icon in the "User List". NOTE: The "admin" Reseller may enter a non-existent user, and NGASI Universal App Panel will attempt to create the system user. NOTE: At the minimum, a JAVA application requires at least 64MB RAM. At the minimum, a RAILS Application requires at least 32 MB RAM (Passenger), 80MB (GlassFish), 50MB (Mongrel on Linux), or 70MB (Mongrel on Windows). At the minimum, a GRAILS application requires at least 256MB RAM. At the minimum, a Play application requires at least 128MB RAM. At the minimum, a Django application requires at least 12MB RAM. Keep this in mind when allocating Memory and Application limits. 3.3 Edit User Select an Account in the "User List". Then Click the "Edit User" button to edit the selected User Account. After making the appropriate changes, click the "Save" button. 3.4 Delete User NOTE: Deleting a User will automatically Delete any applications deployed by the User. Select one or more Accounts in the "User List". Then Click the "Delete User" button to delete the selected User Accounts. 3.5 Management NGASI Universal App Panel comes equipped with resource management tools such as

17 Resellers/Webhosts 17 Memory Management CPU Management Maximum Application Limits Disk Limits (System User Accounts)

18 IV

19 Users 19 4 Users The User accounts is the end user that deploys and manages the applications. 4.1 Login Login Info: The host name and port should be the same as NGASI AppServer Manager. So assuming the default HTTPS port 8663 and host name localhost: Login URL: The user login information would be the same as for your Control Panel (Plesk or cpanel/whm) or system login. NOTE: Your Administrator is able to configure your Control Panel to enable direct access from the Control Panel to NGASI Universal App Panel. ( 4.2 Applications This section covers topics about application management. JAVA All applications deployed under the user's java/webapps directory. Plesk: For a Plesk user with Domain mydomain.com, an application, myapp, will be deployed as follows: /var/www/vhosts/mydoman.com/java/webapps/myapp or C:\Inetpub\vhosts\mydoman.com\java\webapps/myapp cpanel or regular system user: For a cpanel user named user1, an application, myapp, will be deployed as follows: /home/user1/java/webapps/myapp

20 20 Universal App Panel GlassFish: For GlassFish, apps are deployed under the Glassfish "autodeploy" directory. JBoss: For JBoss, apps are deployed under the JBoss "deploy" directory. RAILS All applications are deployed under the user's rails/webapps directory. Plesk: For a Plesk user with Domain mydomain.com, an application, myapp, will be deployed as follows: /var/www/vhosts/mydoman.com/rails/webapps/myapp or C:\Inetpub\vhosts\mydoman.com\rails\webapps/myapp cpanel or regular system user: For a cpanel user named user1, an application, myapp, will be deployed as follows: /home/user1/rails/webapps/myapp GRAILS All applications are deployed under the user's grails/webapps directory. Plesk: For a Plesk user with Domain mydomain.com, an application, myapp, will be deployed as follows: /var/www/vhosts/mydoman.com/grails/webapps/myapp or C:\Inetpub\vhosts\mydoman.com\grails\webapps/myapp cpanel or regular system user: For a cpanel user named user1, an application, myapp, will be deployed as follows: /home/user1/grails/webapps/myapp Play All applications are deployed under the user's play/webapps directory. Plesk: For a Plesk user with Domain mydomain.com, an application, myapp, will be deployed as follows: /var/www/vhosts/mydoman.com/play/webapps/myapp or C:\Inetpub\vhosts\mydoman.com\play\webapps/myapp

21 Users 21 cpanel or regular system user: For a cpanel user named user1, an application, myapp, will be deployed as follows: /home/user1/play/webapps/myapp Scala/Lift All applications are deployed under the user's scalalift/webapps directory. Plesk: For a Plesk user with Domain mydomain.com, an application, myapp, will be deployed as follows: /var/www/vhosts/mydoman.com/scalalift/webapps/myapp or C:\Inetpub\vhosts\mydoman.com\scalalift\webapps/myapp cpanel or regular system user: For a cpanel user named user1, an application, myapp, will be deployed as follows: /home/user1/scalalift/webapps/myapp Django All applications are deployed under the user's django/webapps directory. Plesk: For a Plesk user with Domain mydomain.com, an application, myapp, will be deployed as follows: /var/www/vhosts/mydoman.com/django/webapps/myapp or C:\Inetpub\vhosts\mydoman.com\django\webapps/myapp cpanel or regular system user: For a cpanel user named user1, an application, myapp, will be deployed as follows: /home/user1/django/webapps/myapp PHP/Zend All applications are deployed under the user's django/webapps directory. Plesk: For a Plesk user with Domain mydomain.com, an application, myapp, will be deployed as follows: /var/www/vhosts/mydoman.com/zend/webapps/myapp or

22 22 Universal App Panel C:\Inetpub\vhosts\mydoman.com\zend\webapps/myapp cpanel or regular system user: For a cpanel user named user1, an application, myapp, will be deployed as follows: /home/user1/zend/webapps/myapp Railo (CFML) All applications deployed under the user's railo/webapps directory. Plesk: For a Plesk user with Domain mydomain.com, an application, myapp, will be deployed as follows: /var/www/vhosts/mydoman.com/railo/webapps/myapp or C:\Inetpub\vhosts\mydoman.com\railo\webapps/myapp cpanel or regular system user: For a cpanel user named user1, an application, myapp, will be deployed as follows: /home/user1/railo/webapps/myapp GlassFish: For GlassFish, apps are deployed under the Glassfish "autodeploy" directory. CfWheels All applications deployed under the user's cfwheels/webapps directory. Plesk: For a Plesk user with Domain mydomain.com, an application, myapp, will be deployed as follows: /var/www/vhosts/mydoman.com/cfwheels/webapps/myapp or C:\Inetpub\vhosts\mydoman.com\cfwheels\webapps/myapp cpanel or regular system user: For a cpanel user named user1, an application, myapp, will be deployed as follows: /home/user1/cfwheels/webapps/myapp GlassFish: For GlassFish, apps are deployed under the Glassfish "autodeploy" directory. Other Scripts:

23 Users 23 All applications are deployed under the user's web directory. Plesk: For a Plesk user with Domain mydomain.com, an application, myapp, will be deployed as follows: /var/www/vhosts/mydoman.com/httpdocs/myapp or C:\Inetpub\vhosts\mydoman.com\httpdocs\myapp cpanel: For a cpanel user named user1, an application, myapp, will be deployed as follows: /home/user1/public_html/myapp. regular system user: For a user named user1, an application, myapp, will be deployed as follows: /home/user1/webapps/myapp. NOTE: For PHP applications deployed with Quercus, refer to the JAVA section Deploy New Click the "Deploy New" deployment. button to Upload a new Application Archive for Fill out any necessary information then click "Continue" to proceed. Once successfully deployed, an Icon symbolizing the deployed application will be added to the Canvas display. JAVA The JAVA application must be in WAR format. The expanded directory tree should look like:... WEB-INF NOTE: If available, a Database is automatically created for the application to use

24 24 Universal App Panel and the DataSource (if the name is specified) is configured. Application Directory The application is deployed to: <HOME_DIRECTORY>/java/webapps So an application named myapp would be in the following directory: <HOME_DIRECTORY>/java/webapps/myapp NOTE:For GlassFish, apps are deployed under the Glassfish "autodeploy" directory. NOTE:For JBoss, apps are deployed under the JBoss "deploy" directory. RAILS The RAILS application must be in ZIP format. The expanded directory tree should look like: -app -config -db -doc -lib -log -public -script -test -tmp -vendor NOTE: If available, a Database is automatically created for the application to use and the "production" database configuration is populated in the database.yml file. db:migrate is automatically run on the application upon deployment. Application Directory The application is deployed to: <HOME_DIRECTORY>/rails/webapps So an application named myapp would be in the following directory: <HOME_DIRECTORY>/rails/webapps/myapp GRAILS

25 Users 25 The GRAILS application must be in ZIP format. The expanded directory tree should look like: -grails-app -lib -scripts NOTE: If available, a Database is automatically created for the application to use and the "production" database configuration is populated in the DataSource.groovy file. Application Directory The application is deployed to: <HOME_DIRECTORY>/grails/webapps So an application named myapp would be in the following directory: <HOME_DIRECTORY>/grails/webapps/myapp NOTE: You may deploy a GRAILS application as a JAVA WAR, however in order for the DataSource be set, you would need to specify the data source's JNDI name in the grails-app/conf/datasource.groovy file as follows: datasource { jndiname = "java:comp/env/mydatasource" } Play The Play application must be in ZIP format. The expanded directory tree should look like: -app

26 26 Universal App Panel -conf -public NOTE: If available, a Database is automatically created for the application to use and the "production" database configuration is populated in the application.conf file. Application Directory The application is deployed to: <HOME_DIRECTORY>/play/webapps So an application named myapp would be in the following directory: <HOME_DIRECTORY>/play/webapps/myapp Scala/Lift The Scala/Lift application must be in ZIP format. The expanded directory tree should look like: -src -project NOTE: If available, a Database is automatically created for the application to use and the database configuration is populated in the default.props file like so: src/main/resources/props/default.props db.driver= db.url= db.user= db.password= db= db.host= Application Directory The application is deployed to: <HOME_DIRECTORY>/scalalift/webapps So an application named myapp would be in the following directory: <HOME_DIRECTORY>/scalalift/webapps/myapp

27 Users 27 Django The Django application must be in ZIP format. The expanded directory tree should look like: -app -settings.py -... NOTE: If available, a Database is automatically created for the application to use and the "default" database configuration is populated in the settings.py file. And the "syncdb" command is executed. During installation of Django apps, a superuser is created. Below are the default credentials: User: admin Password: coolgeek Application Directory The application is deployed to: <HOME_DIRECTORY>/django/webapps So an application named myapp would be in the following directory: <HOME_DIRECTORY>/django/webapps/myapp Railo (CFML) NOTE: You can also install Railo as a regular JAVA Application (see above). The Railo (CFML) application must be in ZIP format. The expanded directory tree should look like:... whatever.cfm NOTE: If available, a Database is automatically created for the application to use

28 28 Universal App Panel and the DataSource configuration is set. NOTE: For security purposes (as well as for a loadbalanced cloud environment), the Railo admin console is unavailable by default. To enable, remove the security constraint in the WEB-INF/web.xml file. Application Directory The application is deployed to: <HOME_DIRECTORY>/railo/webapps So an application named myapp would be in the following directory: <HOME_DIRECTORY>/railo/webapps/myapp NOTE:For GlassFish, apps are deployed under the Glassfish "autodeploy" directory. CfWheels The CfWheels application must be in ZIP format. You only need the CfWheels project files. You do not need to bundle CfWheels - that is automatically done for you at deployment. The expanded directory tree should look like:... config models controllers views css images NOTE: If available, a Database is automatically created for the application to use and the DataSource configuration is set. The DataSource name is set to "wheels". Application Directory The application is deployed to: <HOME_DIRECTORY>/cfwheels/webapps So an application named myapp would be in the following directory: <HOME_DIRECTORY>/cfwheels/webapps/myapp

29 Users 29 NOTE:For GlassFish, apps are deployed under the Glassfish "autodeploy" directory. NOTE: You can also install CfWheels as a regular Railo (CFML) Application (see above). PHP/Zend The PHP/Zend application must be in ZIP format. The expanded directory tree should look like: -application -public NOTE: If available, a Database is automatically created for the application to use and the "production" database configuration is populated in the application.ini file. Application Directory The application is deployed to: <HOME_DIRECTORY>/zend/webapps So an application named myapp would be in the following directory: <HOME_DIRECTORY>/zend/webapps/myapp NOTE: For PHP applications deployed with Quercus, refer to the JAVA section Deploy From List NGASI Universal App Panel enables you to redeploy an Application that has already been uploaded, so you do not have to re-upload the same application each and every time. Click the "Deploy from list" button. Drag-and-drop desired Application from the Application Factory list to the Canvas. Click the "YES" button to proceed. NOTE: If available, a Database is automatically created and configured for the application to use.

30 30 Universal App Panel Virtual Hosting Application Virtual Hosting (not to be confused with Web Server Virtual Hosting) maps an application to the root of one or more Domain hostnames. For example an application, myapp, deployed on could be accessed instead as with Virtual Hosting enabled. Click on the icon, in the Canvas, of desired Application. Then click the "Virtual Hosting" button (you can also drag-and-drop the icon to the button as well). Select one or more Domain hostnames in the Selection Box, then Click "Add" to proceed. NOTE: To remove any Virtual Hosting that was set, you would click the "Delete" button instead Delete Deployed Application To delete a deployed application, click on the icon, in the Canvas, of desired Application. Then click the "Delete" button (you can also drag-and-drop the icon to the button as well). NOTE: If the associated database is managed by NGASI Universal App Panel, it will also be deleted File Privileges Although the deployment is controlled by the NGASI Universal App Panel, if your administrator has provided SHELL or FTP access, you can easily edit and manually manage your application via those methods. However the initial deploy must be done through NGASI Universal App Panel, which sets up the appropriate environment as part of the setup process Delete Application Archive Use this option to remove an Uploaded Application Archive from the Application Factory.

31 Users 31 Click the "Deploy from list" button. Drag-and-drop desired Application from the Application Factory list to the "Delete" button. Click "Continue" to proceed. 4.3 Configuration If more than 1 Application Server is available to your account, you may change the default Application Server or other aspects of your setup by following the steps below. Click the "Configuration" button in the Left Menu. Make appropriate changes. Then click the "Update" button to proceed. You may also specify specific Application Servers when deploying an application. This allows different applications to be run on different application servers. 4.4 Restart Sometimes you may have a need to Restart the Application. Click the "Restart" button in the Left Menu to do so. 4.5 Examples JAVA Below are descriptions and links to some sample JAVA Applications: sqltestapp.war This is a simple database driven counter application. The value of the counter is stored in a Database. The Database is accessed by a DataSource object, named "GenericDataSource". In addition, the application requires an SQL script be run to create the necessary tables. NGASI Universal App Panel is able to do so by uploading the SQL script. The required SQL script is sqltestapp.sql. RAILS Below are descriptions and links to some sample RAILS Applications: tracks.zip Tracks is a web-based application to help you implement David Allen s

32 32 Universal App Panel Getting Things Done methodology. It was built using Ruby on Rails. phonebook.zip This is a simple database driven contacts application. In addition, the application requires an SQL script be run to create the necessary tables. NGASI Universal App Panel is able to do so by uploading the SQL script. The required SQL script is phonebook.sql. GRAILS Below are descriptions and links to some sample GRAILS Applications: petclinic.zip Petclinic is the GRAILS framework demonstration application. Play Below are descriptions and links to some sample Play Applications: yabe.zip A sample Blog from the Play guide tutorial. Railo (CFML) Below are descriptions and links to some sample Railo Applications: cfmexample.zip This is a simple database driven contacts application for Railo (CFML). In addition, the application requires an SQL script be run to create the necessary tables. NGASI Universal App Panel is able to do so by uploading the SQL script. The required SQL script is cfmexample.sql. Finally, during the initial deployment stage, the DataSource name, "GenericDataSource", must be specified. CfWheels Below are descriptions and links to some sample CfWheels Applications: wheelspc.zip This is a simple database driven Pet Clinic application for CfWheels. It is based on the popular Petclinic application from the GRAILS framework demonstration application. In addition, the application requires an SQL script be run to create the necessary

33 Users 33 tables. NGASI App in-the-cloud Panel is able to do so by uploading the SQL script. The required SQL script is wheelspc.sql. PHP/Zend Below are descriptions and links to some sample PHP Applications: quickstart.zip quickstart Guest Book is a simple database driven Zend application. In addition, the application requires an SQL script be run to create the necessary tables. NGASI Universal App Panel is able to do so by uploading the SQL script. The required SQL script is quickstart.sql. guest_book.zip Guest Book is a simple database driven PHP application. 4.6 Programming Language/Framework JAVA Below are some information regarding specific programming languages and frameworks. When switching application servers, NGASI Universal App Panel attempts to migrate existing applications unto the new app server. When switching TO another app server FROM Glassfish, the existing glassfish apps are expanded to the "java/webapps" directory. This is because in Glassfish, the apps are deployed to the "autodeploy" directory instead of the "java/webapps" directory. And vice versa, when migrating TO GlassFish FROM another app server, the app is archived (WAR), and deployed to the "autodeploy" directory CfWheels RAILS URL Rewriting is enabled for CfWheels. The URL Rewriting engine sits in the Railo server (as apposed to Apache in most environments). Sometimes terminal (SSH) access is required to manage the application. This may require using the ruby executable (note: db:migrate is automatically run by NGASI Universal App Panel when the application is deployed). As mentioned NGASI Universal App Panel supports multiple Ruby versions so there is

34 34 Universal App Panel no global Ruby path. A list of the Ruby versions, installed by NGASI Universal App Panel, may be viewed by perusing the following directory: /usr/ruby For example, for Ruby 1.8.7/Rails 2.3.5, set the environment variable like so: export RAILS_ENV=production export RUBY_VERSION=1.8.7 export RAILS_VERSION=2.3.5 export RUBY_HOME=/usr/ruby/"$RUBY_VERSION"_$RAILS_VERSION export GEM_HOME=$RUBY_HOME/gems export RUBYLIB=$GEM_HOME:$RUBY_HOME:$RUBY_HOME/lib:$RUBY_HOME/ lib/ruby:$gem_home/lib export RUBYPATH=$RUBY_HOME Execute the Ruby command like so: $RUBY_HOME/bin/ruby NOTE: The above is added as a convenience script under your application bin directory. For an application named myapp, the Ruby script path would look like: <HOME_DIRECTORY>/rails/webapps/myapp/bin/ruby GRAILS Play GRAILS apps are run in the default GRAILS runtime (Tomcat) bundled with GRAILS. By default, each app is run under its own private GRAILS runtime. Play apps are run in the default Play runtime (Netty) bundled with Play. By default, each app is run under its own private Play runtime Scala/Lift Django The Simple Build Tool (SBT) is used to build and deploy Scala/Lift Applications. The system requires access to the internet as required libraries may need to be downloaded and installed. During installation of Django apps, a superuser is created. Below are the default credentials: User: admin

35 Users Railo Password: coolgeek Railo apps are run in the installed application server (e.g. Tomcat) PHP/Zend If the JAVA based Quercus is selected as the PHP application runtime, the app is converted to a JAVA application Other Scripts Intentionally left blank. 4.7 Troubleshooting NOT FOUND If you see a 404 NOT FOUND when browsing your application, and in the NGASI Universal App Panel there is an "X" in the Application Icon, try restarting the Application. The application may have been shutdown if your total applications memory or other resource usage exceeded the maximum allowed for your account java.lang.noclassdeffounderror: java/lang?stringbuilder PROBLEM: When starting Java Application Server (both Tomcat and Glassfish), the following error is shown: SEVERE: Class loader creation threw exception java.lang.noclassdeffounderror: java/lang?stringbuilder

36 36 Universal App Panel at java.lang.class.tostring(class.java:131) SOLUTION: This problem is the result of a corrupted JDK. The Administrator must manually delete the JDK. After which restarting the application server will induce a re-install of the JDK.

37 V

38 38 Universal App Panel 5 Rest API This section covers the Rest API functions. The URL to the Rest base looks like: or Each request should be accompanied with at least the following parameters: ftp_user ftp_pass If using a non-browser client, you should first login to the base, like so: Once successfully logged in, retrieve the "JSESSIONID" Cookie. This cookie must be sent back to the server for each subsequent request. Response are formatted in JSON. 5.1 Administrator This section covers the Administrator Rest API functions. The URL to the Administrator Rest base looks like: Web Host/Reseller This section covers the Web Host/Reseller Rest API functions. The URL to the Web Host/Reseller Rest base looks like: In addition to the Web Host/Reseller login and executing the web host/reseller functions, the Administrator may perform the functions on behalf of the Web Host/Reseller. In this case the "reseller" parameter with the web host/reseller account name must be included in the command request Create User URI: createuser? account=ngdemo&maxmemory=512&maxcpu=60&maxapps=11&programming. language=java&programming.language=django&account. password=scotttiger&create=true HTTP Method: GET; POST

39 Rest API 39 Returns: boolean name value. e.g.: true Update User URI: updateuser? account=ngdemo&maxmemory=512&maxcpu=60&maxapps=11&programming. language=java&programming.language=django HTTP Method: GET; POST Returns: boolean name value. e.g.: true Set Web Configuration Use the following command for specifying a custom IP address for a system user account not also managed by a control panel like Plesk. This is necessary for systems that also manages other web hosts accounts via control panels like Plesk. This avoids hosting conflicts. URI: setwebconfig?account=ngdemo&ip= HTTP Method: GET; POST Returns: boolean name value. e.g.: true Clients Memory Usage URI: memoryusage/clients HTTP Method: GET Returns: Hash of clients and memory used (MB). e.g.: {"asmdemo":82,"rmdemo-ve:2311":382,"farver-ve:125":-3}

40 40 Universal App Panel 5.3 User This section covers the Reseller Rest API functions. The URL to the Reseller Rest base looks like: In addition to the user login and executing the user functions, the Reseller that owns the user account as well as the Administrator may perform the functions on the user account. In this case the "account" parameter with the user account name must be included in the command request Deploy Application Install The following API functions are for deploying an already uploaded application. URI: app/deploy/mysaas4?app=mysaas&database=mysql&appserver=tomcat ;JDK6.0_20&overwritedb=true HTTP Method: GET; POST Returns: boolean (true if installation process for application with contextpath "mysaas4" starts) e.g.: true Complete URI: app/deploy/complete/mysaas4 HTTP Method: GET;POST Returns: boolean (true if installation process for application with contextpath "mysaas4" is completed) e.g.: true Success URI: app/deploy/success/mysaas4 HTTP Method: GET Returns: boolean (true if installation succeeded for application with contextpath "mysaas4") e.g.:

41 Rest API 41 true Upload Application Install The following API functions are for uploading an application archive. URI: app/archive/install Form Parameters: account (Optional) app archive (File) programming.language datasource (Optional) sql (File) (Optional) HTTP Method: POST (multipart encoding) Returns: boolean (true if installation process for application archive starts) e.g.: true Complete URI: app/archive/install/complete/myapp HTTP Method: GET; POST Returns: boolean (true if installation process for application archive with name "myapp" is completed) e.g.: true Success URI: app/archive/install/success/myapp HTTP Method: GET; POST Returns: boolean (true if upload and installation succeeded for application archive with name "myapp") e.g.: true Set Password URI: setpassword?new.password=coolgeek HTTP Method: GET

42 42 Universal App Panel Returns: boolean (true if password set succeeded) e.g.: true

43 43 Endnotes 2... (after index)

44 Back Cover