configuration
Easy access to MySQL data on shared hosting service
<p>MySQL databases are often the main data-source of web applications when it comes to shared hosting services with very limited possibilites (no system service support, no scheduling, no in-memory database, ...). Often, management or visualization of such databases is not easily done, since no admin utility is installed, no remote connections to the database are allowed, and access by the sql binary (via SSH) is not user-friendly. A better way to manage databases visually in such cases is the challenge.</p>
configure an access point
<p>Last time I wanted to install / configure my wlan router at home. Because I have never done it, it was a really challenge for me. However I did it.</p>
Steps how to setup a Canoo Webtest Environment
Step 1: Download
You need to download several things to get Canoo started.
a) Download Canoo from http://webtest.canoo.com/webtest/manual/WebTestHome.html
b) Download at least JDK 5
c) Download at least Ant 1.7.0
Step 2: Configure your System-Path
You have to add each of the programs above to your system-path.
E.g. for Canoo its necessary to add the bin/ directory to your system-path, e.g. for Windows "C:\Programme\Canoo\bin";%PATH%
Finished ;)
It's that easy.
For working with Canoo you can either use the built-in test-project or you simply generate your own Project folder with your test-cases in it.
Taggings:
Configuring gmail in outlook 2007
Have you ever tried to configure your outlook client mail program for gmail mail server? If yes, then you should be familiar with this damn error prompt:
"The connection to the server has failed. Account: 'pop.gmail.com', Server: 'smtp.gmail.com', Protocol: SMTP, Port: 465, Secure(SSL): Yes, Socket Error: 10060, Error Number: 0x800CCC0E"
Correctly configuring a Jetty Java Servlet container to be used through an Apache Web server via mod_jk
When deploying a JVM-based Web app usually so-called Java Servlet containers resp. application servers are used for the produciton system/environment. Probably the most popular and common Java server in this field is Apache Tomcat (and other even more feature-rich ones like JBoss or GlassFish). Apart from that, there's also Jetty which can be seen as a somewhat lightweight alternative. Nevertheless, there are some subtle differences to be taken into consideration when configuring it as opposed to Tomcat. The usual way to setup such a production system for a Java Web app is to use the Servlet container to serve the Web app and put so to speak in front of it an Apache Web server which handles the requests, hands them over to the container instance (e.g., Jetty or Tomcat) and receives its responses then (to say it in an a bit simplified way). Usually this is done via Apache's mod_jk module which enables communication between app server and Web server through the AJP13 protocol. What should be described and explained now is how to setup such a Java Web app production system ready for deployment in detail (mainly from a configuration perspective). The main focus shall be put at differences which are to be taken into account here between Jetty and Apache Tomcat.
Pages
