• Blazix Java Server
  • Congratulations!

    If you are viewing this page by accessing the URL http://oemcomputer/ or http://localhost/ in a browser, your Blazix server is up and running successfully!

    Here are more links to confirm that various pieces of the server are working correctly.

    JSP

    In order to have JSP work correctly, the "javac" command must be available in your PATH (typing "javac" in a Command window should invoke the compiler.)  If it is not, you must add it and reboot the machine, then restart the server.

    If "javac" is already setup correctly, click on the link below to confirm that JSPs are working correctly.  (Note: the first time it will take a while because the JSP page will be turned into Java and compiled using javac.)

    JSP Test Page

    Authentication

    The following link demonstrates authentication.  Use the username "test" and the password "testpwd" when asked.  You can change the "application.default.authType" parameter in web.ini to "Basic" and restart the Blazix server, to see an instance of "Basic" authentication instead of "Form" authentication.
    Authentication Sample

    Internationalization

    The link below demonstrates JSP internationalization.  View the page from the link below.  Then temporarily change your browser's language preference to french (the only translation file included with the sample is for french) and reload the page.  You should see the language on the page change.
    Internationalization Sample
    HTML internationalization is similar, but instead of only one base file and multiple translation files, involves maintaining separate HTML files for each language.  The server automatically picks the right language version if available.

    WIRELESS

    The installation adds a sample index.wsp file.  If you have access to a WAP-capable wireless device (or a WAP simulator), you can also confirm that the WSP suffix is available and working correctly by pointing your wireless device or simulator to the URL http://oemcomputer/

    Notes:

    • You may have to enter the IP address rather than the name of your machine if the machine's hostname is not externally known.
    • If you are inside a firewall, the WAP device or WAP simulator will not be able to get to your machine unless your machine's port 80 is opened through the firewall.  (WAP simulators placed on the same machine, or at another machine inside the firewall will not have this problem.)
    • The first time this page is accessed it will take a little while, because the WSP page will be turned into Java and compiled using javac.

    What next?

    You can now start adding your own pages.  A simple test is to place an HTML file in C:\Blazix\webfiles folder, and view it from the browser.  If you create a file called C:\Blazix\webfiles\myfile.html, it will be accessible from your browser as http://oemcomputer/myfile.html or http://localhost/myfile.html

    If you look in the web.ini file in C:\Blazix, you will see that application.default.dir attribute has been set to C:\Blazix\webfiles directory.

    If you would like to change the directory where you will keep your web pages, change the web.ini file so that "application.default.dir" points to your directory.

    See the links on "Getting Started" in the online documentation for further suggestions on getting started with the Blazix server.