Defining the skin and assigning it to a theme manually

When you create new skin resources, you can define them so that you can assign them to a theme.

About this task

You can define the skin and assign it to a theme by using Manage properties or manually. Learn more about Defining the skin and assigning it to a theme using Manage properties.

Procedure

  1. Use the following code snippet as a template for the XMLAccess skin definition to import, where theme_context, skin_folder_name, skin_unique_name, skin_title, theme_folder, skin_folder_name, and theme_unique_name are the unique values for your theme and skin.
    Note: This template creates a title in English only, but you can add more locales.
    <?xml version="1.0" encoding="UTF-8"?>
    				<request
    					xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" build="wp80" version="8.0"
    					xsi:noNamespaceSchemaLocation="PortalConfig_8.5.0.xsd"
    					type="update" create-oids="true">
    					<portal action="locate">
    						<skin action="update" active="true" context-root="theme_context" default="false" domain="rel" 
    						  resourceroot="skin_folder_name" type="default" objectid="skin_unique_name" uniquename="skin_unique_name">
    						<localedata locale="en">
    							skin_title
    						</localedata>
    							<parameter name="com.ibm.portal.skintype" type="string" update="set"><![CDATA[template]]></parameter>
    							<parameter name="com.ibm.portal.skin.template.file.name.html" type="string" update="set"><![CDATA[skin.html]]></parameter>
    							<parameter name="com.ibm.portal.skin.template.ref" 
    							  type="string" update="set"><![CDATA[dav:fs-type1/themes/theme_folder/skins/skin_folder_name/]]></parameter>
    						</skin>
    						<theme action="update" uniquename="theme_unique_name">
    							<allowed-skin skin="skin_unique_name" update="set"/>
    						</theme>
    					</portal>
    				</request>
  2. Import the XMLAccess skin definition by using the command line or the Import XML portlet.