thanks for answering kedar !
I see, since we don't support hadb, I guess we don't need to have theses entries anymore. we might still need to support them as no-op for backwards compatibility although I suppose that quietly accepting those parameters as no-op can lead to more problems later...
jerome
On Mar 26, 2010, at 9:04 PM, Kedar Mhaswade wrote:
>
>
> Sent from my iPhone
>
> On Mar 26, 2010, at 3:56 PM, Jerome Dochez <Jerome.Dochez_at_Sun.COM> wrote:
>
>> I looked at our documentation at
>>
>> http://docs.sun.com/app/docs/doc/821-0179/create-cluster-1?l=en&a=view
>>
>> and I cannot figure out how the command parameters map to the Cluster.jar configuration object as defined in the config-api module at
>> /trunk/v3/admin/config-api/src/main/java/com/sun/enterprise/config/serverbeans/Cluster.java
>>
>> In particular, I am puzzled by all the ha related entries :
>> [--hosts hadb-host-list
>> ]
>> [
>> --haagentport port_number
>> ]
>> [
>> --haadminpassword password
>> ]
>> [
>> --haadminpasswordfile file_name] [--devicesize devicesize
>> ]
>> [
>> --haproperty (name=value)[:name=value
>> ]*]
>> [
>> --autohadb=false]
>>
>> Is our cluster.java configuration definition out-dated ? If yes, who can update the model to reflect what V2 final shipped with ?
> No one (should), :).
> I think there was a configuration where we undertook creation of. Hadb tables. This was if the user wanted us to create the hadb session store. These entries are not required to be persisted in domain.xml since the server uses jdbc connection to actually save session state.
>
> - Kedar
>>
>> jerome
>>
>>
>>