Welcome to my world. » Glassfish

Uploading Files Using Flash and Java

Marc — Tue, 10 Nov 2009 23:02:59 +0000

The sample code attached below is a complete example for uploading multiple files using flash cs3 and java. After much searching I could not find a complete Flash File uploading tutorial that utilized java; most if not all are for php. This flash interface provides progress for each file independently, and upon completion can notify a javascript function. The files are sent to a simple JAVA servlet where they are saved to the local file system.

For the java servlet there are two library requirements:
commons-fileupload-1.2.1.jar
commons-io-1.3.2.jar

They are included in the web/WEB-INF/lib folder. The source files are saved as a Netbeans 6.7 project with Glassfish set as the target server. It is simple to open the project and change the target server. Both the compiled flash and source file are in the web folder.

I extracted two settings to variables listed in the index.html file so that this could be used without recompiling/editing the flash file. The first variable url is the address of the java servlet to send the files to. The second variable is f and is the name of the javascript function to call when each file is uploaded. f is optional. These variables need to be set 3 times in the index.html file. See the file for further documentation.

I expect to update the source code slightly over the next couple weeks. I will replace the zip file with the latest as updates are completed.

source files

Glassfish Enterprise v2.1 with HADB Setup on Windows 2003 Cluster

Marc — Wed, 26 Aug 2009 13:54:03 +0000

I am going to go over setting up Glassfish Enterprise v2.1 in a windows clustered high availability environment. For this we will be using two Windows 2003 servers with two network interface cards (NIC) in each server that are network loadbalanced, 2 instances of IIS as the web container and 4 instances of glassfish with HADB behind IIS. You may ask why, and the reason is simply those were the technologies I had to work with; my task was to move from JBOSS to Glassfish. I will attempt to go over this setup in great detail, so as anyone with a basic understanding of these technologies should be able to get this running. For all of the images in the post, click on them for a full size version.

Environment Setup

At this point you should already have 2 identical windows 2003 servers running, for this tutorial I will refer to them as SERVER1 and SERVER2. Each server should have 2 NICs. Make sure the default gateway is the SAME on all NICs. For clarification you will be using a total of 5 IP addresses. Two for each server, and one will be the virtual IP to reference the cluster. Though yours will likely be different, for this tutorial I will use 192.168.1.2 for the virtual IP, 192.168.1.3 and 192.168.1.103 for SERVER1, and 192.168.1.4 and 192.168.1.104 for SERVER2. Make sure your web address (if you have one) resolves to your virtual IP (192.168.1.2 here).

Network Load Balancing

You will need two identical windows 2003 servers. Keep in mind that as there are two NICs in each server, it does not matter which network connection you use for the network load balancing, just make sure to only load balance one. I chose to load balance 192.168.1.3 and 192.168.1.4.

In Network Connections right click one of the LAN connections and select properties.
Verify Network Load Balancing present and checked, if not you may need to add it by clicking Install.
Select Network Load Balancing and click properties
Enter the Virtual IP address to be associated with both servers.
For Cluster operation mode select Multicast.
For host parameters set the machines IP and subnet.
For port rules use all the defaults.
Click ok, select Internet Protocol (TCP/IP) and click properties
Click advanced
Under IP addresses make sure both the server IP and the virtual IP is listed.
Repeat above for both servers.

Java Setup

I would assume since we are setting up a java server you are at least familiar with setting up java and may already have it installed. However for completeness I have outlined the exact setup I used.

Sun’s JAVA 1.6 JDK should be setup on both servers. You can download it from http://java.sun.com. You can likely just use the latest version, as of this writing that was 1.6.15. I installed the jdk to the default location: C:\program files\java\jdk1.6.0_15 and the JRE to C:\program files\java\jre6. Then create an environmental variable JAVA_HOME with the value C:\Program Files\Java\jdk1.6.0_15. Add C:\program files\java\jdk1.6.0_15\bin to the PATH environmental variable.

IIS Install

IIS setup is trivial. In windows use the “Add a Role” on both servers to install IIS. In IIS Manager (found in administrative tools) right click on the default website, go to properties and enter in the virtual IP address and fully qualified domain name for the description. To verify it works try accessing http://localhost. If it doesn’t come up the first thing you should check are the permissions. Check the user account used for anonymous access. Once both servers are setup you then should be able to access IIS’s “Under Construction” page from the virtual ip, in this tutorial: http://192.168.1.2/.

Glassfish setup

Make sure you download Glassfish Enterprise Server v2.1 with HADB. At the time of this writing you can find it here.

A. Complete the following setup on SERVER1 only:

Open the setup file. Click next.
The agreement will come up, complete that and click next again.
For installation Directory leave the default C:\Sun\AppServer.
Click next, if prompted select “create directory”. It should now ask you for “Component Selection”.
1. Select all of the check boxes in the Server Tier: Node Agent, High Availability Database Server, and Load Balancing Plugin.
2. Under Administration Select the first option: Domain Administration Server and Administration Tool.
3. Make sure Sample Applications is checked under Additional.
Click Next to go to “Java Configuration”. Select Reuse existing Java 2 SDK. It should automatically then say C:\Program Files\Java\jdk1.6.0_15.
Click Next to go to “Web Server Location”. Select Microsoft IIS 5.0 or above.
Click Next. It will prompt you to setup the load balance plug in, select OK.
You should now be on “Admin Configuration”. Type in a password and master password. Set HTTP port to 8080 and HTTPS to 8433.
Click Next to go to “Installation Options” Do not enable the update center client. Do not Create Windows Service, we will set this up later.
Click Next and Complete the installation.

B. IIS Redirector

Open IIS Manager.

Right click the default website and click properties.
Select the ISAPI filter tab.
Click Add
1. Filter Name: Application Server
2. Executable: C:\Inetpub\wwwroot\sun-passthrough\sun-passthrough.dll
In the default website create a new virtual directory
1. Alias: sun-paththrough
2. Directory: C:\Inetpub\wwwroot\sun-passthrough
3. Under Permissions check Execute
Make sure the following is set for the PATH environmental variable:
1. C:\Inetpub\wwwroot\sun-passthrough;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Program Files\Java\jdk1.6.0_15\bin
Right click Web Service Extensions and Select ADD
1. Name: Sun-Passthrough
2. File: C:\Inetpub\wwwroot\sun-passthrough\sun-passthrough.dll
3. Check set status to allowed
Create the file: C:\Inetpub\wwwroot\sun-passthrough\lb.log
1. Modify the permissions on the file so the group IIS_WPG has write and modify.
Reboot your server.

C. Start the Node Agent and Admin Server.

This can be achieved by going to Start -> Program Files -> Sun
- Start both the admin server and node agent. You will be prompted for the passwords you entered during setup.

D. Install glassfish on SERVER2

Repeat steps A through C above with the following exceptions:

In the “Component Selection” of the glassfish install selection No Administration Tools
Setup will ask you to specify the admin host. Use SERVER1′s IP: 192.168.1.3

Glassfish Cluster

By now the domain admin server should be running on SERVER1 and the Node agents should be running on SERVER1 and SERVER2. Now we will create the glassfish cluster, with two instances on each physical server.

login to the Admin Console found at https://localhost:4848/ on SERVER1
Select Clusters, then click New
For the name of the cluster I used application_cluster
under instances select new, call the instance app1, give it a weight of 100, and select SERVER1 as the node.
- create 3 more instances, app2, app3, and app4, all with a weight of 100. Make sure app3 and app4 user SERVER2 for their nodes.

HTTP Load Balancer

Now we need to setup the load balancer. This piece is essentially the map from IIS to glassfish. It is an xml file that will need to be updated every time you add a new application to the server, or add additional glassfish instances to the cluster. The admin console will build it for you, all is needed is to copy it over to IIS.

In the admin console select “HTTP Load Balancers”.
Click New. Enter applicationlb for the name, localhost for IP and 80 for port.
- The port and IP here are actually irrelevant as glassfish does not support auto updating the loadbalancer with IIS.
Add application_cluster as the selected target
Click ok. Click on applicationlb you just created and select the Export tab, then click Export Now.
If you get the following error: The XML page cannot be displayed, right click and select view source.
You need to create the file loadbalancer.xml at C:\Inetput\wwwroot\sun-passthrough\ and save the contents to this file. The file must be saved on BOTH servers. Afterward restart IIS on both machines and restart the glassfish cluster. You can see an example of my loadbalancer.xml below:

HADB Setup

Next we’ll setup the high availability. This is where the second network adapters come into play. First we install the service.

Open up a command prompt window
C:\Sun\AppServer\hadb\4.4.3-6\bin\
Run the command: ma -i ma.cfg to install the service.
open windows services and verify the HADBManagementAgent service is running.
Repeat on second server.

Next we need to setup the HADB domain.

On each server type the command hadbm listdomain, if a domain exists, delete it by using the command: hadbm deletedomain.
On SERVER1 execute the following command:
- asadmin configure-ha-cluster –user admin –hosts 192.168.1.103,192.168.1.104 –devicesize 256 application_cluster
- It is important here that we use the IP addresses from the NIC’s that are not network load balanced.

Windows Services

Now that everything should be running well, we will register glassfish as a windows service so it starts up automatically. I will user SERVER1 below, make sure you repeat this for SERVER2.

Stop the node agent if it is running, do this from Start->Program Files->Sun Stop Node Agent.
Create a file named password.txt in C:\Sun\Appserver
Add the text below to the file, replacing adminadmin with your password.

AS_ADMIN_MASTERPASSWORD=adminadmin
AS_ADMIN_PASSWORD=adminadmin

Open a command prompt window and navigate to system32.
type the command below:

sc create SERVER1 binPath= “C:\Sun\AppServer\lib\appservAgentService.exe \”C:\Sun\AppServer\bin\asadmin.bat start-node-agent –user admin –passwordfile C:\Sun\AppServer\password.txt SERVER1\” \”C:\Sun\AppServer\bin\asadmin.bat stop-node-agent SERVER1\”" start= auto DisplayName= “SunJavaSystemAppServer SERVER1″

Test Application Deployment

To test the server configuration Sun includes the Sample application clusterjsp. It is a simple application that tells you what server instance processed your request, and allows you to create session variables. you can then experiment will shutting down server instances and seeing if the session data persists. To deploy the app we do the following:

In the glassfish admin console, select Enterprise Applications then click Deploy.
For location browse to the following file: C:\Sun\AppServer\samples\quickstart\clusterjsp\clusterjsp.ear
Check the box for availability.
Add only application_cluster for Targets.
Click OK.
Expand Clusters and select application_cluster
Click on the applications tab, check clusterjsp, and select Load Balancer Enable from the –more actions– drop down.
Repeat the steps for setting up the Load Balancing. Your new loadbalancer.xml should look something like the following:

Navigate to http://192.168.1.2/clusterjsp to test the server. Make sure you use the virtual IP to reference the application.

SSL (optional)

SSL is very straight forward to setup; it only involves IIS. Microsoft has an excellent tutorial on how to achieve this:

http://support.microsoft.com/kb/313299

Summary

If you have any problems or questions leave a comment below and I will try to answer.

JAVA Security Provider Error

Marc — Thu, 13 Aug 2009 22:56:39 +0000

Just a quick note about a simple but annoying error I encountered when porting an app to glassfish; The code in question was as follows:

 
     ... 
    Charset charset = Charset.forName("UTF-8");
    CharsetEncoder encoder = charset.newEncoder();
    ByteBuffer bbuf = encoder.encode(CharBuffer.wrap(str));
    SecretKeySpec key = new SecretKeySpec( KEY_BASE, "DES" );

    private static Cipher ecipher = Cipher.getInstance( "DES");
    ecipher.init( Cipher.ENCRYPT_MODE, key ); 
    byte[] enc = ecipher.doFinal( bbuf.array() );
     ...

The code above just converts a string (stored as str here) to UTF-8 then encrypts it using DES. Equivalently you could use str.getBytes() for the UTF conversion. The code above worked fine on JBOSS, and worked fine stand alone. It even worked on my glassfish test server, however when deployed on glassfish enterprise I started getting the following stacktrace:

    java.security.ProviderException: update() failed
        at  sun.security.pkcs11.P11Cipher.implUpdate(P11Cipher.java:557)
        at  sun.security.pkcs11.P11Cipher.engineUpdate(P11Cipher.java:457)
        at  sun.security.pkcs11.P11Cipher.engineDoFinal(P11Cipher.java:485)
        at  sun.security.pkcs11.P11Cipher.engineDoFinal(P11Cipher.java:471)
        at  javax.crypto.Cipher.doFinal(DashoA13*..)
    ...
    Caused  by: sun.security.pkcs11.wrapper.PKCS11Exception: CKR_DEVICE_ERROR
        at  sun.security.pkcs11.wrapper.PKCS11.C_EncryptUpdate(Native Method)
        at  sun.security.pkcs11.P11Cipher.implUpdate(P11Cipher.java:510)

After much trial and error I found the issue at hand was caused by the security provider being used. Adding the following code segment I output the provider being used and ran it both stand alone and inside glassfish:

            System.out.println("--------" + ecipher.getProvider().getName());
            System.out.println(ecipher.getProvider().getInfo());
            System.out.println(ecipher.getProvider().getVersion())            System.out.println("--------" + ecipher.getProvider().getName());

    System.out.println(ecipher.getProvider().getName());
    System.out.println(ecipher.getProvider().getInfo());
    System.out.println(ecipher.getProvider().getVersion());

When running stand alone I got the following output:

SunJCE
SunJCE Provider (implements RSA, DES, Triple DES, AES, Blowfish, 
                 ARCFOUR, RC2, PBE, Diffie-Hellman, HMAC)
1.6

Running in glassfish I got:

SunPKCS11-__SUN_SJSAS_internal
SunPKCS11-__SUN_SJSAS_internal using library C:\Sun\AppServer\lib\softokn3.dll

I tried prioritizing SunJCE in java.security however the above results did not change. Finally I just specified SunJCE in my Cipher.getInstance so:

Cipher.getInstance("DES", "SunJCE");

After that all worked well. A very trivial issue to resolve, however annoying nonetheless.

Virtual Directories in Glassfish

Marc — Sat, 18 Jul 2009 11:55:09 +0000

There are many reasons you may want some of your content outside of the application server root. Perhaps you wish to share the content between applications or even webservers, or maybe you temporarily write data from a database to be served. Regardless, serving static content in glassfish is extremely easy. There are two ways to accomplish this; at the server level and at the application level.

Server level

First we will look at the server level, this will make your information available server wide, outside of any application context. Lets say you have images you wish to serve in the directory C:\media. In the glassfish admin console expand configuration > http service > virtual servers. Select ‘server’ then scroll to the bottom and select ‘add property’.

For name use: alternatedocroot_1, for value use: from=/media/* dir=C:/

Keep in mind that glassfish expects the directory in the URL pattern to exist, so the from= is not just the URL pattern, but it is also the path relative to the dir=.

Luckily these changes do not require any restarts so you can experiment easily to make sure you have the settings you want. If you used the default glassfish install and your server runs at http://localhost:8080 then http://localhost:8080/media/ should now resolve to the absolute path C:\media.

The image above shows adding an alternate docroot from in the admin console, click it for the full sized image.

Application Level

Let’s say you have an application WebApplication1. By editing sun-web.xml you can add an alternate docroot that is relative to the application. For this example I will use the same as above, serving /media/* from C:/.

Add the following line to sun-web.xml inside the tag:

If using the default glassfish setup, http://localhost:8080/WebApplication1/media/ should now resolve to the absolute directory C:\media

The image above shows an example of sun-web.xml. Click for full size.

In both of the above scenarios you can have as many alternate docroots as you want, as long as the follow the naming convention (alternatedocroot_1, alternatedocroot_2, etc…). Also your url pattern can be as specific as you like, for instance if you only wanted to catch requests for jpeg’s in the media directory then you would use: from=/media/*.jpg