Package com.sun.identity.config.wizard

Class Step5

  • All Implemented Interfaces:
    Serializable
    public class Step5
extends ProtectedPage
    Wizard Step # 5: Site Name, URL and Session HA Failover indicator. Session Failover indicator new @since 10.1 This Step should be skipped when installing a secondary instance, as this information will be replicated by the underlying store.
    See Also:
    Serialized Form

    • Constructor Detail

      • Step5

        public Step5()

    • Method Detail

      • onInit

        public void onInit()
        Description copied from class: org.openidentityplatform.openam.click.Page
        The on Initialization event handler. This event handler is invoked after the Page.onInit() method has been called.

        Subclasses should place any initialization code which has dependencies on the context or other properties in this method. Generally light weight initialization code should be placed in the Pages constructor.

        Time consuming operations such as fetching the results of a database query should not be placed in this method. These operations should be performed in the Page.onRender(), Page.onGet() or Page.onPost() methods so that other event handlers may take alternative execution paths without performing these expensive operations.

        Please Note however the qualifier for the previous statement is that all form and field controls must be fully initialized before they are processed, which is after the onInit() method has completed. After this point their onProcess() methods will be invoked by the ClickServlet.

        Select controls in particular must have their option list values populated before the form is processed otherwise field validations cannot be performed.

        For initializing page controls the best practice is to place all the control creation code in the pages constructor, and only place any initialization code in the onInit() method which has an external dependency to the context or some other object. By following this practice it is easy to see what code is "design time" initialization code and what is "runtime initialization code".

        When subclassing pages which also use the onInit() method is is critical you call the super.onInit() method first, for example: 

         public void onInit() {
     super.onInit();

     // Initialization code
     ..
 }
        Overrides:
        onInit in class AjaxPage

      • clear

        public boolean clear()
        Clear all Site / VIP / Load Balancer Settings
        Returns:
        boolean indicator to view.

      • validateSite

        public boolean validateSite()
        Validate the Site Name host= site config name port = primary loadURL Just a little confusing!

      • validateURL

        public boolean validateURL()
        Validate the Site URL host= site config name port = primary loadURL Just a little confusing!