Creating a skin involves the following steps:
Perform the following procedure to copy an existing skin.
Follow these steps:
For illustrative purposes, this section assumes that you chose the look of the neteauto skin and will call it yourskin. The name yourskin is the name of your company’s skin.
iam_im.ear/user_console_war/app/imcss/neteauto
iam_im.ear/
Give it the following name:
iam_im.ear/user_console_war/app/imcss/yourskin
|
Current Name |
New Name |
|---|---|
|
neteauto.css |
yourskin.css |
|
neteauto_task.css |
yourskin_task.css |
|
neteauto.properties |
yourskin.properties |
To simplify administration, the name of the .properties file and the .css files should correspond to the name of the skin.
Note: Skin names are case-sensitive.
Update any of the images (.gif, .jpg, or .png) in the following directories with the images that match the look of your company’s skin:
For example, to put your company’s logo in the yourskin skin, replace logo.jpg from the image directory with your company’s logo.
We recommend using the same image file names because many of these images are already mapped with the appropriate paths in the yourskin.properties file.
Update the yourskin skin’s cascading style sheets with the fonts and menu, background, margin, and other colors of your choice.
The paths to the style sheets are as follows:
Perform the following procedure to modify the .properties file.
Follow these steps:
parent=/app/imcss/idm/im.properties
The parent section specifies the location to the properties file of the parent skin. In this example, the parent skin is idm.
stylesheet/skin.css=yourskin/yourskin.css stylesheet/skin_task.css=yourskin/yourskin_task.css
If you replaced the images in the skin without renaming them, go to Step d. If you renamed images, do the following:
You can add multiple image entries to the .properties file by adding an entry like the following:
image/logo.gif=yourskin/image/logo.jpg
Perform the following procedure to modify the index.jsp file.
Follow these steps:
<iam_im.ear>/user_console_war/app/imcss
<skin:skin name="yourskin" filename="/app/imcss/yourskin/yourskin.properties" />
CA Identity Manager selects the default skin for the CA Identity Manager User Console based on which skin tag is listed first in the <skin:update> section of the index.jsp file.
As noted in the following <skin:update> section from the index.jsp file, CA Identity Manager will display the user console for the yourskin skin:
<skin:update>
<skin:skin name="yourskin" filename="/app/imcss/yourskin/yourskin.properties" /> <skin:skin name="idm" filename="/app/imcss/idm/im.properties" /> <skin:skin name="neteauto" filename="/app/imcss/neteauto/neteauto.properties" /> <skin:skin name="horizontal" filename="/app/imcss/horizontal/horizontal.properties" /> <skin:skin name="horizontal2" filename="/app/imcss/horizontal2/horizontal2.properties" />
</skin:update>
When you want to use a different skin, you need to change the order of the skin tags listed.
If you are running CA Identity Manager on a JBoss application server, you must recompile the JSP files and restart the application server after you have created a skin, as follows:
Note: If you are using a different application server, you do not need to complete this step.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|