Sun GlassFish Enterprise Server v2.1.1- Information for Support

Sun GlassFish Enterprise Server v2.1.1 is latest public release from the GlassFish v2 family.

Although this is a public release, it is also a patch upgradeable release for existing v2.1/9.1 based customers to maintain the continuity for them (existing v2.1/9.1 based customers) and at the same time upgrade them to new components as needed.

Version Information

Reasoning for the version change:

  • This is a public release
  • It was branched out so that some new GF features like session replication and Sun GlassFish Communications Server 2.0 could be accommodated.

Why are we merging the 2.1 and 2.1.1 code branches:

  • Both are essentially the same product, with minor differences. These differences are bridged by maintaining full backward compatibility
    • All the fixes that went into v2.1 (till v2.1-Patch#5) and 9.1 (till 9.1UR2-Patch#5) are forward ported to v2.1.1 release
  • To reduce the confusion for customers of which version to use between 9.1/v2.1/v2.1.1, came out of same codebase
    • Customers can get the benefit of new release (v2.1.1) just by patching the existing versions v2.1/9.1, rather than going into migration process
    • To ensure best support/patch structure for GF/AS customers, by maintaining/sustaining one tail between v2.1.1/v2.1/9.1
    • This would reduce the number of branches that needs to sustained and a huge number of patch releases.
      • This is also helps us in reducing the pressure about huge number forward ports and backward ports required to sustain three(v2.1.1/v2.1/9.1) branches
Mapping of various versions
  • v2.1.1 would be a super set of earlier 9.1, v2.1 and v2.1 patches.
  • The mapping of the products would be : SGES v2.1.1 (aka) SGES v2.1 patch6 (aka) SJSAS 9.1_02 patch 12
    • $asadmin version --verbose
      Version = Sun GlassFish Enterprise Server v2.1.1 ((v2.1 Patch06)(9.1_02 Patch12)) (build b31f-fcs)
      Command version executed successfully.
Important Points :
  • SGES v2.1.1 would be patch upgradable from 9.1 and v2.1 patches.
  • The escalations and bugs fixed in v2.1 patches have been carefully reviewed and are forward ported into v2.1.1 codebase. This would ensure customers would have a seamless transition from v2.1 patches to v2.1.1.
Patch IDs Patch Name
128640-14
Sun GlassFish Enterprise Server 2.1.1 (v2.1 Patch06) (9.1_02 Patch12), Solaris: SVR4 patch
128641-14

 Sun GlassFish Enterprise Server 2.1.1 (v2.1 Patch06) (9.1_02 Patch12), _x86: SVR4 patch
128642-14

Sun GlassFish Enterprise Server 2.1.1 (v2.1 Patch06) (9.1_02 Patch12), RHEL4.0 RHEL3.0 Linux: Pkg_patch

128643-14
Sun GlassFish Enterprise Server 2.1.1 (v2.1 Patch06) (9.1_02 Patch12) with HADB, Solaris: File based patch

128644-14
Sun GlassFish Enterprise Server 2.1.1 (v2.1 Patch06) (9.1_02 Patch12) with HADB, _x86: File based patch

128645-14
Sun GlassFish Enterprise Server 2.1.1 (v2.1 Patch06) (9.1_02 Patch12) with HADB, Linux: File based patch

128646-14

Sun GlassFish Enterprise Server 2.1.1 (v2.1 Patch06) (9.1_02 Patch12) with HADB, Windows: File based patch
128647-14
Sun GlassFish Enterprise Server 2.1.1 (v2.1 Patch06) (9.1_02 Patch12), Solaris: File based patch

128648-14
Sun GlassFish Enterprise Server 2.1.1 (v2.1 Patch06) (9.1_02 Patch12), _x86: File based patch
128649-14
Sun GlassFish Enterprise Server 2.1.1 (v2.1 Patch06) (9.1_02 Patch12), Linux: File based patch

128650-14

Sun GlassFish Enterprise Server 2.1.1 (v2.1 Patch06) (9.1_02 Patch12), Windows: File based patch

137916-13

 Sun GlassFish Enterprise Server 2.1.1 (v2.1 Patch06) (9.1_02 Patch12), AIX: File based patch

NOTE:
  • Patch names with HADB refers to Enterprise Edition and it uses NSS for certificate management. With this you get developer, cluster and enterprise profile. 
  • non-HADB versions provide only Developer/Cluster profiles. It uses jdk's jks for certificate management. 
  • Developer profile uses admin console in non-secured mode, so most of the asadmin commands need to pass --secure=false
  • For native patches one has to download dependent components  like NSS, MQ, HADB, please refer the install instructions.
  • Patching or upgrading GlassFish downloaded from java.net site is not supported.
  • Do not download GlassFish from java.net and try to upgrade the existing supported version of GlassFish.
Comments:

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

Oracle's announcements related to using GlassFish software in production.

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