registration Wizard Design for NB 6.5 Page 1
Glassfish v3 Installation Location:
_____________________________________[browse]
[Download v3 Now] [] i have read the license
-- status message area --
[back][next][finish][cancel]
the user is expected to enter the name of a directory in the install location field. if the location contains the v3 bits, the next button is enabled. the finish button may be enabled, if there is a registerable domain in the domains directory. if the location DOES NOT contain v3 bits, the user can check the box and press the download now button to install the v3 bits from java.net... Once the bits are downloaded successfully, the next and finish button are enabled. Page 2
Domain: ____________v
-- instructions --
[back][next][finish][cancel]
This page allows the user to select the domain to be registered... The domain field is an editable combobox. The box is populated by the registerable domains embedded in the installation directory. If there are no registerable domains the field is blank and the finish button is disabled. the user can select any of the domains listed and click finish. The domain will be registered in the IDE. if the user enters a new name and clicks finish, a new domain is created in the domains directory. The ports are calculated to be across a random 'swath' of values, to prevent port overlap. If the user enters a directory path and clicks finish, an existing domain will be registered or a new domain will be created in that location. New Features for 7.0
- allow users to register remote domains
there are situations where the IDE user wants to test an app on a different machine. Users can deploy an app onto a remote server using asadmin deploy, but it would be useful to deploy the apps directly from the IDE. To be able to do this, the user needs to be able to register the server.
- allow the user to associate a username and password with a registration.
in the Prelude/6.5 time frame, the default domain in v3 was an anonymous domain. If the user registered a domain that was not anonymous, the user was asked to authenticate when they accessed the server. as v3 moves from a development server to a production server role, this can be a bit more clumsy. the user name and password would be used to pre-authenticate requests.
- allow users to set the ports associated with a personal domain.
Currently users are not allowed to specify the ports used to create a personal domain. This 'works' much of the time, but there are situations where the ability to select the ports is critical.
Page 1 Installation info
Glassfish v3 Installation Location:
_____________________________________[browse]
[Download v3 Now] [] i have read the license
-- status message area --
[back][next][finish][cancel]
This page behaves like it does in 6.5. Clicking finish means: register the first registerable domain in $INSTALL/glassfish/domains with no authentication information.
Clicking next allows the user to select the domain to register/create. Page 2 domain type and location
() Local Domain:______________________v
() Remote Domain Host: _______________
Port: ______
-- instructions --
[back][next][finish][cancel]
The default value of the radio button is 'Local Domain' This page behaves in a manner similar to the page 2 of the registration wizard of 6.5, for the domain field. If the user selects the remote domain radio button, the user needs to enter host and port info. clicking finish when the Local Domain choice is selected will:
a) register the selected existing domain with no authentication information.
b) create a personal domain, with anonymous authentication on a set of randomly selected ports. Page 3 Authentication information
username: ______
password: ______
[] save authentication info in registration properties
[back][finish][cancel]
If the user is creating a domain, the default value of the save authentication checkbox is unselected. The user must enter a user name. if the username is not anonymous, the user must also enter a password. If the user is registering a normal domain, the 'save authentication...' checkbox is selected. The checkbox is also disabled, so follks cannot change the state. clicking finish means that the domain will be registered with the authentication data provided. clicking finish when the user is creating a domain means that the domain will use authentication and be based on a set of randomly selected ports. The authentication information might be saved into the registration 'database', depending on whether the state of the 'save auth...' checkbox Page 4 Port selection/display page
admin port:____
http port:____
https port: ___
.
.
.
[back][finish][cancel]
this page is read-only if the user is registering an existing domain. It just displays the port values that are embedded into the domain.xml. undetermined ports are left blank. This page is pre-populated with semi-random values if the user is creating a personal domain. the user can edit any of the port values that are displayed.... blank values are not allowed, if the fields are editable. One open issue.... what do we do with ports that don't make sense. For example, say the user creates a domain with the 'web' profile of the server. Do we send the create-domain property values for the ports that are not used in the web profile? What does create-domain do in those situations?
----(color:purple;)Old URL (read-only): GfinNB70v3RegWizardUI%%
|
