3.2.7 Changing the Context-Root for UI or Web Services

To change the default context-root of an OHI Components application web application or the OHI Components application web services deploy the application with a customized deployment plan.

Perform the following steps for a new deployment of the application:

Step 1: Edit the value of the variable UI_CONTEXT_ROOT in <OHI_ROOT>/application/plan/Plan.xml to suit your requirements.

Step 2: The following example shows how the context-root for a web service can be changed using the deployment plan (the example does so for the context-root of the Provisioning web service):

...

<variable>
    <name>PROVISIONING_CONTEXT_ROOT</name>
    <!-- Here ohi-ws-new-provisioning is the new context root which will overwrite the default context root -->
    <value>ohi-ws-new-provisioning</value>
</variable>

...

<module-override>
    <!-- Copy the name of the EAR (including .ear file extension) from <OHI_ROOT>/application/app/ dir -->
    <module-name>NAME_OF_THE_EAR</module-name>
    <module-type>ear</module-type>
    <module-descriptor external="false">
        <root-element>application</root-element>
        <uri>META-INF/application.xml</uri>
        <variable-assignment>
            <name>PROVISIONING_CONTEXT_ROOT</name>
            <!-- Here ohi-ws-provisioning refers to the default context root. 
                 See the appendix of the Installation Guide for the default context roots of web services -->
            <xpath>/application/module/web/[context-root="ohi-ws-provisioning"]/context-root</xpath>
            <operation>replace</operation>
        </variable-assignment>
    </module-descriptor>
</module-override>

 The module names for the web services are listed in an appendix.

Step 3: The EAR and Plan.xml (deployment plan) are packaged under a directory named "application" in the release bundle (See the directory structure below). It is recommended to copy the "application" directory to a location (this directory will be referred as <INSTALL-ROOT> hereafter) and optionally rename the directory (for example, rename to OHIComponents).

Step 4: To install the application using Administration Console, select the directory <INSTALL-ROOT> instead of selecting the EAR file. By default, the Administration Console will use a deployment plan named Plan.xml, if one is available in the /plan subdirectory.

3.2.7.1 Changing User Session Timeout

An OHI Components application does not ship with a default session timeout. Instead, it leverages WebLogic Server's default session timeout - which is3600 seconds(1 Hour). It is possible to change this default session timeout value through WebLogic Server's Admin Console. Follow the steps below to change the default session timeout.

Follow the section Changing the Context-Root for UI or Web Services to deploy OHI Components applications in order to change the session timeout through WebLogic Server Admin Console.

Step 1: Login to WebLogic Server Admin Console

Step 2: Click Deployments link and expand OHI Components application tree.

Step 3: Click on the name of the UI application (by default it is vbp unless the context-root is changed as mentioned in the section "Changing the Context-Root for UI or Web Services"  in Modules section

Step 4: Make sure that the name of the module is ohi-vbp-ui.war

Step 5: Click on Configuration tab and change the default Session Timeout (in seconds) from 3600 seconds (1 Hour) to suit your needs and click on Save button.

You may get into trouble if the load balancer session timeout is shorter than the WebLogic session timeout. So, it is important to set load balancer session timeout in alignment with WebLogic session timeout

Step 6: Click on Deployments link and select OHI Vbp application. Click on Update button

Step 7: Select the first option in Update Application Assistant and click on Finish button.

Step 8: After activating changes, restart WebLogic Server.