Devilish detail when you register a domain

The GlassFish/SJSAS integration allows you to register domains created by a number of different version of these projects and products. This flexibility is great, but it isn't free.

I recently spent some time helping a user that wanted to deploy J2EE applications to SJSAS 8.2 EE on a remote machine. He had registered the domain using the registration wizard, but the tests to see if the server was running were failing. That caused a deployment failure.

After digging into the issue for a few minutes, I realized what the root cause of the issue was. The user had registered the remote domain by using the install directory of GlassFish V2 build in the Platform Location field. And that just doesn't work.

To maintain the flexibility, the integration uses code from the jars of a server install to communicate with that install (or remote installs) of that server. So, that means that if you register a domain, you need to have an install of that server available locally, so that the plugin can load and use the correct code to communicate with that domain.

You can learn more about domain registration through these resources, though some of them are dated:
http://blogs.sun.com/vkraemer/entry/new_glassfish_integration_feature_shared
http://blogs.sun.com/vkraemer/entry/register_a_java_ee_5
http://blogs.sun.com/vkraemer/entry/server_registration_does_double_duty
http://j2ee.netbeans.org/docs/promoe/j2ee-server-ui-spec-promoe.html#Wizard_Add_Server

Comments:

Post a Comment:
Comments are closed for this entry.
About


Vince Kraemer writes the entries in this blog.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today
News
Blogroll

No bookmarks in folder

automarks