mike4soa building/testing/scaling Open ESB

(install step 1; radio buttons)

 I was asked today about the difference between upload and copy when using the GlassFish v2 web admin console to install a JBI component into Open ESB.

Case 1. The JBI archive is on the “client” system. Use the default “File to Upload:” radio button.

opens the web-browser’s file upload dialog to select the file to be uploaded from the client file system to the remote GlassFish Domain Admin Server (DAS).  uploads the selected file.

Case 2. The JBI archive is on the “server” system. Use the “File to Copy:” radio button.

woodstock file chooser

opens a  Woodstock file chooser in a pop-up window, showing only files on the system running the GlassFish DAS.  copies the selected file.

Case 3. The web browser and the DAS are running on the same system. Either upload or copy would work, since the JBI archive is accessible by both the web browser and the DAS.

Category: glassfish, jbi, open-esb, web admin console

Hi, I’m Mike Wright, a senior software engineer, blogging about my Sun Microsystems work.

My background is Enterprise Application Integration systems (software plumbing).  The About page has more about my past.

I’m part of the Service Oriented Architecture and Business Integration (SOA/BI) team.  I’m developing a WS-Notification JBI Service Engine for the Open JBI Components project.

I’m also enhancing the jregress test-running framework for distributed/scalable Open ESB testing.

This blog will discuss: news, architecture, implementation, issues, enhancements, testing, administration, tools, practices, and deployment related mainly to Open ESB running on GlassFish.

Category: general