5.1 Portal Configuration Tasks

To configure basic cache settings:

1. Go to the Caching page.

2. In the Cache Configuration section of the page, specify global or local values for the following settings, as appropriate:

   Setting	What to do
   Lock Acquisition Timeout	Specify the time interval (in milliseconds) that the cache waits for a lock to be acquired on an object. You might want to increase this setting if the User Application gets a lot of lock timeout exceptions in the application log. The default is 15000 ms.
   Wake Up Interval Seconds	Specify the time interval (in seconds) that the cache eviction policy waits before waking up to do the following: Process the evicted node events Clean up the size limit and age-out nodes
   Eviction Policy Class	Specify the classname for the cache eviction policy that you want to use. The default is the LRU eviction policy that JBoss Cache provides: org.jboss.cache.eviction.LRUPolicy If appropriate, you can change this to another eviction policy that JBoss Cache supports.
   Max Nodes	Specify the maximum number of nodes allowed in the cache. For no limit, specify: 0 You can customize this setting for some cache holders. See Customizable Cache Holders.
   Time To Live Seconds	Specify the time to idle (in seconds) before the node is swept away. For no limit, specify: 0 You can customize this setting for some cache holders. See Customizable Cache Holders.
   Max Age	Specifies the number of seconds an entry should be allowed to stay in the cache holder since its creation time. For no time limit, specify: 0 This setting is only available for Customizable Cache Holders.

   These settings are required, which means that there must be a global value for each, and optionally a local value too.

   If you want to override the global value of a setting with a local value, select the Enable Local check box for that setting. Then specify the local value. (Make sure that all of your local values are valid. Otherwise, you won’t be able to save your changes.)

   NOTE:For those settings where Enable Local is deselected, any existing local values are deleted when you save.

3. Click Save.

4. When you’re ready for your saved settings to take effect, restart the User Application on the applicable application servers.

1. Set up your JGroups cluster. This involves using the User Application installation program to install the Identity Manager User Application to each application server in the cluster (see Section 2.5, Clustering).

2. Enable the use of that cluster in the User Application’s cache configuration settings

   See Configuring Cache Settings for Clusters.

1. Go to the Caching page.

2. In the Cluster Configuration section of the page, specify global or local values for the following settings, as appropriate:

   Setting	What to do
   Cluster Enabled	Select True to invalidate cache changes to the other nodes in the cluster specified by Group ID. If you don’t want to participate in a cluster, select False.
   Group ID	Specify the Group ID of the JGroups cluster in which you want to participate. There’s no need to change the default Group ID that’s provided for the User Application’s cluster, unless you want to use a different cluster. The Group ID must be unique and must not match any of the known JBoss cluster names such as DefaultPartition and Tomcat-Cluster. HINT:To see the Group ID in logging messages, make sure that the level of the caching log (com.sssw.fw.cachemgr) is set to Info or higher.
   Cluster Properties	Specify the JGroups protocol stack for the cluster specified by Group ID. This setting is for experienced administrators who might need to adjust the cluster properties. Otherwise, you should not change the default protocol stack. To see the current cluster properties, click view. For information on JGroups protocol stack, see Section 2.2.6, Encryption of Sensitive User Application Data.

   If you want to override the global value of a setting with a local value, select the Enable Local check box for that setting. Then specify the local value. For those settings where Enable Local is unselected, any existing local values are deleted when you save.

   WARNING:If you specify local settings and enter an incorrect configuration in the JGroups initialization string, the cache cluster function might not start. Unless you know how to configure JGroups correctly and understand the protocol stack, you should not use local settings.

   Make sure that all nodes in your cluster specify the same Group ID and Cluster Properties. To see these settings for a particular node, you must access the Identity Manager user interface running on that node—by browsing to the URL of the user interface on that server—and then display the Caching page there.

   To use the TCP protocol instead of the default UDP protocol, you can add a token to the global settings for the Cluster Properties. For example, IDM_HOST_ADDR. You can then edit the hosts file on each server in the cluster to specify the IP address for that server. For more information, see Configuring User Application Caching to use TCP.

3. Click Save.

4. When you’re ready for your saved settings to take effect, restart the User Application on the applicable application servers.

1. Back up the deployed User Application WAR file (IDMProv.WAR) to the directory in which you install, for example the /opt/netiq/idm subdirectory.

2. In a test environment, extract the contents of the User Application WAR file.

   The files that comprise the User Application’s themes are located in the resource\themes subdirectory. Each theme resides in its own directory with an appropriate name.

3. In the test environment, create a directory for the custom theme.

   The directory name can be any valid directory name, but it should reflect the name of the theme, and it should not contain spaces.

4. Copy the contents of the BlueGloss theme from the extracted WAR file to the new subdirectory. You will be working with the following files:

   File Name	Description
   theme.xml	The theme descriptor file. It includes entries for display name and description. They are used in the Themes page of the Administration tab. The remaining entries correspond to the brandable selectors. The width and height attributes on these entries are used in the branding page to reference the exact dimensions needed when a user uploads a customized version of these images. These entries must match their respective images, width and height as found in the themes.css.
   theme.css	Contains the CSS selectors used to style the look and feel of the user interface.
   print.css	Contains the CSS selectors used to style a print friendly version of the user interface.
   dojo.css	Contains a pointer to additional CSS files used by RBPM.
   An images subdirectory	Contains the images used by the theme.

   Rules for working with these files:

   • Do not change the names of the theme.xml, theme.css, print.css and dojo.css files.

   • The CSS Selector names must remain the same, but you can change the properties of the selectors to establish the look and feel.

   • The images subdirectory can have any name, but you must reference it correctly in the CSS and XML files.

5. Make your changes to the images, CSS style sheets and other theme elements as needed. The following changes are recommended:

   • In the theme.xml file:

     • display-name: Change this to a value that represents your theme. It displays as the Theme-name in the Themes page of the User Application’s Administration tab.

     • description: Change this to a value that describes your theme. It displays as the Description in the Themes page of the User Application’s Administration tab.

     • Consider whether to localize the display-name and Description fields.

     • Remove the following:

       <resource-bundle>com.novell.afw.portal.artifacts.theme.BlueGloss</resource-bundle>
       <resource-group>admin-resgrp</resource-group>

     • In the dojo.css file, change the @import line to the following value:

       @import url("../../../../IDMProv/javascript/dijit/themes/idmua/idmua.css");

       where IDMProv is the name of your WAR context.

     • If you wish to change the appearance of some Dojo elements, such as the menu buttons within the profile section on the Work Dashboard, you should take the following steps, instead of performing the steps above:

       1. Copy the following from your extracted WAR in this location: /javascript/dijit/themes:

          dijit.css
          dijit_rtl.css
          idmua (folder)

          Paste these items into your new theme folder.

       2. Change the @import line in the dojo.css file, as follows:

          @import url("idmua/idmua.css");

   • In the graphics directory:

     • thumbnails.gif: Replace the copy with your own image. This image displays along with the Theme-name and Description of the theme (described above) that is shown in the Themes page of the Administration tab. It typically illustrates what the User Application landing page looks like when the associated theme is applied

     • Renaming graphics files: If you change the names of graphics files (rather than just substituting a different image of the same name), make sure to change the reference to the image in both the theme.xml and the theme.css file. If the image is not used in the branding interface (for example, if it is not listed as one of the subset of brandable images in the theme.xml file), then you will only need to change the reference to the image in the theme.css file. Suppose you want to rename images/header_left.gif to images/my_company_name.gif. Edit the theme.css file to reflect the new image name.

6. After you make all of the desired changes to the theme files, add your customized theme directory to a new WAR file that contains one or more custom themes. Deploy the new WAR to your test application server. Testing tip: Open the Themes page (available under the Administration tab). Your theme should display along with the prepackaged themes. Use the Theme Preview action to see how the customized changes to your new theme will render. This is a useful way to preview many of your intended changes to your theme. Running through commonly used features of the application is also a recommended testing step.

7. After your changes are fully tested, you can deploy the WAR containing the custom theme to your production application server.

1. Stop Tomcat.

2. Open the context.xml file located in the %tomcat-install%/conf directory.

3. Modify <Context> to <Context crossContext="true">.

4. Add the custom theme WAR to the %tomcat-install%/webapps directory.

5. Run the configupdate utility to map the context name of the custom theme WAR.

6. Start Tomcat.