admin@glassfish.java.net

Re: config changes for sun-domain_1_3.dtd ...

From: Anissa Lam <Anissa.Lam_at_Sun.COM>
Date: Tue, 24 Oct 2006 23:38:07 -0700

Kedar Mhaswade wrote:
> Folks,
>
> I have updated the table for changes to configuration at:
>
> http://www.glassfishwiki.org/gfwiki/Wiki.jsp?page=GlassFishV2ApplicationServer9.1
>
>
> Please make sure that we are on the same page here. These are the only
> requests I have received for milestone 3 and the status for each of them
> is shown in the table.
>
> Anissa, please make a provision for the GUI screen changes that might be
> required to set the additional attributes defined on connection pools, if
> you've not already done so.
>
Yes, GUI and the IEC team has agreed on the GUI changes to support the
new attributes added regarding the connection pools. Please see
attached email.

However, its not clear what support is needed in GUI for the addition of
"extension-element" to "application". Please refer to the 2nd attached
email. I am not sure what Jerome meant by "some support" in 9.1
I believe we can add the tree node for "extension-element", and also a
table on the right hand side to show them. We can commit to this. Any
additional support will just be 'nice to have' for this release.

thanks
Anissa.


> Lloyd, make a call regarding the AMX changes.
>
> CLI commands won't change -- to set the additional attributes,
> administrators
> will have to use the generic "set" command.
>
> Regards,
> Kedar


attached mail follows:


Hi Jagadish,

Thanks for the list.   I want to confirm that we all agree on the following GUI support:
thanks
Anissa

Jagadish Prasath Ramu wrote:
Hi Anissa,
These are the advanced attributes/features of jdbc, connector connection
pool respectively.


1) jdbc-connection-pool:

validate-atmost-once-period-in-seconds
connection-leak-timeout-in-seconds 
connection-leak-reclaim
connection-creation-retry-attempts
connection-creation-retry-interval-in-seconds
statement-timeout-in-seconds
max-connection-usage-count
lazy-connection-enlistment
lazy-connection-association
associate-with-thread
match-connections
wrap-jdbc-objects



2) Connector-Connection-Pool :

validate-atmost-once-period-in-seconds 
connection-leak-timeout-in-seconds 
connection-leak-reclaim  
connection-creation-retry-attempts
connection-creation-retry-interval-in-seconds
lazy-connection-enlistment
lazy-connection-association
associate-with-thread
match-connections
max-connection-usage-count

Default values are at :
http://www.glassfishwiki.org/gfwiki/attach/OnePagersOrFunctionalSpecs/DTD-Changes-Connection-Pool.html

Thanks,
-Jagadish

On Mon, 2006-10-09 at 09:37 -0700, Anissa Lam wrote:
  
Hi Jagadish,

Gui will be able to support all the new attributes for the 9.1
release.
Since the list of attributes are quite long,  Here is what i suggest
for creating and editing the pool:
- creation:    Since most of the attributes has default,  GUI will
just show those attributes that we believe user usually will want to
set differently than the default.   Please give me the list of
attributes that needs to be shown to user during creation.

- Editing:  We will have extra tab to accommodate new attributes.
Please divide the attributes into 2 different sets so that 1 set will
be shown in the general tab, and another in the new tab.   Also, give
me suggestion to the name of the tab.

As for the properties list,  i cannot commit that we will divide the
properties to different list to show to user.  This will be nice to
have but we probably will not get to this for 9.1 release.

thanks
Anissa.

Jagadish Prasath Ramu wrote: 
    
Hi Anissa,
Please find attached the mail from Sreeram having the latest document.
Mostly it will be the same. 
Once we get a response from Sreeram and also feedback from "asarch", we
shall freeze it.

Please let us know sometime Tue/Wed PDT, all of us can know what will be
done in GUI, apis required for GUI from connectors back-end.

Thanks,
-Jagadish

---------------------------------------------------
Hi Jagadish,
Can you send me the latest proposed change ?   

thanks
Anissa
---------------------------------------------------



-------- Forwarded Message --------
From: Sreeram Duvur <sduv@sfbay.sun.com>
To: Jagadish.Ramu@Sun.COM
Cc: Sreeram Duvur <Sreeram.Duvur@Sun.COM>, Rebecca Parks
<June.Parks@Sun.COM>, Kshitiz Saxena <Kshitiz.Saxena@Sun.COM>, Binod
<Binod.Pg@Sun.COM>, Sivakumar Thyagarajan
<Sivakumar.Thyagarajan@Sun.COM>, Srikanth Anandal
<Srikanth.Anandal@Sun.COM>, Anissa Lam <Anissa.Lam@Sun.COM>, Kedar
Mhaswade <Kedar.Mhaswade@Sun.COM>, Jane.Young <Jane.Young@Sun.COM>,
Abhijit Kumar <Abhijit.Kumar@Sun.COM>, Sridatta Viswanath
<Sridatta.Viswanath@Sun.COM>, Sreenivas.Munnangi@Sun.COM
Subject: Re: DTD Change for review
Date: Thu, 05 Oct 2006 12:43:46 -0700

Jagadish,

Waited a couple of days to look for a coherent Alternative #2 to evolve, 
but it seems elusive. Sreeni in Admin helped me to look at compatibility 
issue in Admin if we went with Alt #2. Refactoring may simplify coding 
at our end, but cause pain and confusion for end users. In interests of 
time, we will go with Alternative #1. See the attached document. It is 
whatever you have mailed me last, with one change.
Since we decided that all new pool configuration will be attributes, no 
need for driver-config or mcf-config.

The property space in [jdbc|connector]-connection-pool is meant for 
driver configuration only.
Should you need to introduce further experimental pool configuration as 
properties, I suggest
a) add new optional attributes
b) use some property name space convention like com.sun.enterprise.foo, 
temporarily
c) postpone to next release :-)

The CLI can be potentially a mile long, but I think we have chosen 
defaults well. GUI could group them visually
to make it easier for users to focus on an aspect of pool behavior.

Thanks.

Sreeram


Jagadish Prasath Ramu wrote:
  
      
Hi Sreeram,

We are fine with the DTD changes. Adding admin cli, gui, infrastructure
to the list.

We have modified the DTD document.
a) Description of the attributes
b) Default values of attributes
c) Clustered Pool is dropped from 9.1 
d) Added missing attributes from 9.0
e) Added 2 new attributes (RFEs 6473760, 6472065)

Thanks,
Jagadish/Kshitiz

On Fri, 2006-09-29 at 15:52 -0700, Sreeram Duvur wrote:
  
    
        
I will be pushing these changes out soon. I have reduced the number of 
properties and assigned some defaults, so things work without 
configuring half dozen things.

Pls. get back to me by Monday COB

Sreeram
    
      
          

  

attached mail follows:




no CLI support is needed, the idea is to use the current commands like
deploy and undeploy with these new module types. However the admin GUI
will need to add "some" support in 9.1 if we have time. In the next
release we will need to think about a better integration point where
such module implementation can provide JSF screens that could be embeddd
in the admin GUI to edit each module specific runtime attributes.

By adding elements to the mbeans xml description we should get MBeans
instanciated for these new modules, AMX is another story, I don't see
too much impact if this cannot be done for 9.1

We can talk about this next week if you have time.

Jerome

Sreeram Duvur wrote:
> It is very low priority to support this in Admin GUI. This element is
> optional and is meant for some new module types that are being
> proposed for support in future. So we can do GUI only if
> resources/time permit. AMX and CLI support would be needed, I suppose.
>
> Sreeram
>
>
> Anissa Lam wrote:
>>
>> Is this going to have impact in Admin GUI. I haven't seen any
>> request to support this in GUI. Do we need to show the available
>> <extension-module> like other modules ? Do we need to support the
>> addition of this <extension-module> ?
>>
>> thanks
>> Anissa
>>
>> Sreeram Duvur wrote:
>>> Jerome,
>>>
>>> These requests need to go to admin_at_glassfish.dev.java.net
>>>
>>> The proposal looks good and will serve the SIP Archive usecase also
>>> quite well.
>>> Are you planning to expose a SPI so that module handling is
>>> dispatched to a
>>> registered handler based on module type?
>>>
>>> Sreeram
>>>
>>> Jerome Dochez wrote:
>>>
>>>> Hi
>>>>
>>>> We need to support an extensible application type in the domain.xml
>>>> so non Java EE applications have a chance to be registered and use
>>>> our infrastructure for deployment lifecycle and infrastructure. I
>>>> would like to request these DTD changes to the domain.xml to
>>>> support such use case.
>>>>
>>>> <!ELEMENT applications
>>>> ((lifecycle-module | j2ee-application | ejb-module | web-module
>>>> | connector-module | appclient-module | mbean |
>>>> extension-module)*)>
>>>> <!-- extension-module
>>>> Extension modules are not handled directly by the application
>>>> server runtime
>>>> They usually are add-ons container that are installed on top of
>>>> the basic
>>>> installation. The type of such applicative extensions is used to
>>>> match deployed
>>>> artifacts with installed add-ons.
>>>>
>>>> attributes
>>>> module-type
>>>> String representing the module type. This module type will
>>>> be used
>>>> by the runtime to find the appropriate add-on container.
>>>> --> <!ELEMENT extension-module (description?, property*)>
>>>>
>>>> <!ATTLIST extension-module
>>>> name CDATA #REQUIRED
>>>> location CDATA #REQUIRED
>>>> module-type CDATA #REQUIRED
>>>> object-type %object-type; "user"
>>>> enabled %boolean; "true"
>>>> libraries CDATA #IMPLIED
>>>> availability-enabled %boolean; "false"
>>>> directory-deployed %boolean; "false">
>>>
>>>
>>
>