|
|||||
|
|
|
|
|
||
Support DocumentationPlease read on for support on the following areas.
Maintaining your WebsiteMaintaining your Tomcat Web Application
Sending and Receiving EmailGetting Started with RSA Shell AccessAccessing MySQLFor any other support enquiries, please contact us by email or phone. | |||||||||||||||||||||||||||||||||||||||||||||
Maintaining Your WebsiteTo maintain the files in your website, open an ftp connection to ftp://sydney1.qnix.com.au, and provide your Qnix FTP account username and password when prompted. Once connected type in dir, and unless you have multiple domains delegated to Qnix, you should see something like this:
You only have write permission to the cgi-bin and web directories: cgi-bin is for all your cgi scripts. The web directory is for all your HTML and PHP. The contents of logs is generated by apache, and files are placed in keys by Qnix only if you require Apache ssl. Maintaining your Tomcat Web ApplicationAccessing and Navigating the Qnix Tomcat Directory StructureIf you have subscribed to a package with Tomcat JSP / Servlet support, your web application directory structure is rather different to the standard directory structure above. ftp access to your tomcat directory area is as above. The ftp directory structure for subscribers to packages with Tomcat JSP / Servlet support is organized as follows (for certain packages, the Tomcat directory structure is located located under a directory called java, off the root directory):
Managing your Tomcat Web ApplicationsTomcat 4 includes a manager application to support the deployment and reloading of your other web applications. Your Qnix tomcat account includes access to the HTML version of this application. Full documentation of this application is available here. To access your manager application, navigate to http://yourdomain.name/manager with your browser, and use your Qnix username and password to authenticate yourself. You can change this username and password through tomcat-users.xml. The following information may help you get kick-started: Deploy web application archive to http://yourdomain.name/appname
Deploy exploded web application to http://yourdomain.name/appname-exp
Reload or Unload already-deployed web application
JDBC Connection PoolingPoolMan is a (GPL) embeddable object pooling and caching library produced by, and freely available from Codestudio. Qnix provide a pre-installed and configured example poolman web application for each JSP / Servlet customer. This application is accessible at http://yourdomain.name/poolman. Documentation is included with this application. However, in the interest of another kick-start, the following information is provided:
Sending and Receiving EmailWhen you first subscribe to a Qnix package which includes email, you will be allocated a default email account for each domain that you delegate to us (you may choose to a single account for multiple domains). The email address for this account is username@domain.com, where username is the your Qnix username. To retrieve and send email using this or any other Qnix account, you can use any standard POP3 mail client (details below), or visit webmail.qnix.com.au.
Depending upon which package you have subscribed to, you are likely to be entitled to a number of other email accounts to be created within these domains. Each account will be protected with its own username and password. Please mail support@qnix.com.au with your requirements. Getting Started with RSA shell accessShell access is authenticated by COMPLETELY separate mechanism to your ftp, pop and smtp, since the passwords for these protocols travel across the internet unencrypted, and can be intercepted. Instead, you access the shell using SSH with 1024-bit public and private key RSA (Rivest-Shamir-Adleman) encryption. PuTTY is a freely available implementation of Telnet and SSH for Win32 platforms, which Qnix recommend for basic (free) shell access. More advanced users might want to consider a commerical alternative in which case, we can recommend VanDyke Software SecureCRT, which we use ourselves. For RSA access using putty you will need to download the following two applications:
Run puttygen.exe, and click on generate: The application will ask you to move the mouse around to supply some "randomness", and will then prompt you for a passphrase. This should NOT be the same as your Qnix password, which is inherently insecure. PuTTYgen will then generate a public and private key pair. Save the generated (private) key to a secure place, not a shared drive or location where it can be accessed by anyone else. Copy the public key which comes up in the puttygen window to an email, and send it to keys@qnix.com.au.
We will then copy the public key into your home directory under .ssh/authorized_keys, and mail you back a confirmation that it is in place. Once you have received this confirmation, start putty.exe. You should see a window that looks like this:
Enter the following information:
Now select SSH from connection on the left hand menu. You should see a window that looks like this:
Select the private key file you generated using PuTTYgen with the Browse button, and ensure that the preferred protocol SSH protocol version is 1. To test your connection, click Open. You will be prompted for a username, which should be supplied to you by Qnix (it is not your standard Qnix username), and the secure passphrase you specified when running PuTTYgen. You should now be logged in to the shell! If you do not have access, please mail support@qnix.com.au with a description of your problem - we'll do our best to help. Accessing MySQLIf you have subscribed to a package with MySQL access, you will have permission to create, maintain and drop any number of MySQL databases which adhere to the following naming convention: username_dbname where username is your usual Qnix username, and dbname is any string permitted by MySQL.
|
