Show TOC Entering content frame

Procedure documentation Configuring Customized Logon Screens for Tenants Locate the document in its SAP Library structure

Use

If your multitenant portal hosts external customers, you may want the portal logon screen to display a customized branding logo for each tenant.

The portal ships with a set of predefined logon screens. One, for example, is the portal logon screen in which users are required to provide their user ID and passwords for authentication before they can access the portal. This topic describes how to use customized branding elements with the standard logon component and to assign them to tenants.

Note

If you want to create your own logon component that functions differently to the standard logon component shipped with the portal, see Customizing the Logon Screens in the Portal Administration Guide.

This procedure is optional. If you do not create a customized logon screen or assign one to a tenant, the default SAP NetWeaver logon images and stylesheet will be used instead. Once the branding elements are available, you can edit the tenant at any time and assign them as needed.

 

Prerequisites

·        You are a global system administrator with permission to deploy PAR files and to modify portal tenant properties.

·        You have installed SAP NetWeaver Developer Studio.

This graphic is explained in the accompanying text

The procedure described below can be performed without SAPNetWeaver Developer Studio. For example, use any text editor to create and edit the portalapp.xml file and a compression application to wrap the contents in a PAR file.

 

Procedure

To configure a customized logon screen for a tenant, you create a portal archive (PAR) that contains the customized branding elements (logo image files and a stylesheet) for the tenant, deploy it to the portal, and then assign the relevant branding elements to the portal tenant.

Creating and Deploying the PAR File Containing the Logon Branding Elements

...

       1.      Obtain the branding element files and specifications from the tenant customer.

As shown in the following figure, the standard logon screen in the portal displays two images placed on top of one another; together cover a screen area of 301 x 300 pixels (width by height). These are only guidelines; for optimal viewing your customized images should together cover the same screen area.

This graphic is explained in the accompanying text

Standard logon screen for portal

       2.      Using SAP NetWeaver Developer Studio, create a portal application project containing the branding elements for the tenant. For more information, see Structure linkSAP NetWeaver Developer Studio Plug-In.

Note the following

¡        For easy identification of the portal application and its images following the deployment in the portal, assign the tenant name to the portal application project.

¡        The portal application must contain only graphics and CSS files. Do not include script files.

¡        Use browser-compliant images only, such as JPG or GIF.

¡        The standard SAP NetWeaver logon images are located in the following folder:

... /irj/root/portalapps/com.sap.portal.runtime.logon/layout

You may use the images as a template for designing your own customized images. Do not remove or modify the original images.

¡        The standard SAP NetWeaver logon stylesheets are located in the following folder:

.../irj/root/portalapps/com.sap.portal.runtime.logon/css/ur/

You may use the stylesheet as a template for designing your own customized stylesheet. Do not remove or modify the original stylesheet.

¡        Copy your branding images and stylesheet to the file structure of the portal application:

This graphic is explained in the accompanying text <tenant_name>

      This graphic is explained in the accompanying text css

               This graphic is explained in the accompanying text logon.css

      This graphic is explained in the accompanying text images

                  This graphic is explained in the accompanying text branding-image1.jpg

                  This graphic is explained in the accompanying text branding-image2.jpg

      This graphic is explained in the accompanying text PORTAL-INF

                  This graphic is explained in the accompanying text portalapp.xml

¡        In the portalapps.xml file, we recommend you specify a security zone so that the PAR is not automatically assigned to an unspecified security zone.

Here is an example of a portalapps.xmlfile:

<application>

   <application-config>

      <property name="Vendor" value="sap.com"/>

      <property name="SecurityArea" value="NetWeaver.Portal"/>

   </application-config>

   <components/>

   <services/>

</application>

¡        The portalapps.xml file does not contain any portal components or services; therefore, there is no need to assign a safety level to the security zone.

       3.      Create a PAR file.

       4.      Deploy the PAR file to the portal.

To manually deploy the PAR file (without SAP NetWeaver Developer Studio), do the following:

...

                            a.      In the portal, navigate to System Administration ® Support ® Support Desk.

                            b.      In the content area, choose Portal Runtime.

                            c.      Under Portal Anywhere Admin Tools, choose Administration Console.

                            d.      In the Archive Uploader box, browse to the PAR file you created for the tenant.

                            e.      Click Upload.

       5.      In the portal, assign the deployed branding elements to the tenant (see following steps).

Assigning the Logon Branding Elements to a Portal Tenant

...

       1.      In the portal, open the Tenant Management tool (see Managing Portal Tenants).

       2.      Edit the tenant.

       3.      In the following tenant properties, specify the Portal Content Directory (PCD) paths to the deployed branding images and stylesheet:

                            a.      Logo: Refers to branding image #1 in the previous figure. According to the PAR structure shown previously, the path would be:
/irj/portalapps/<tenant_name>/images/branding-image1.jpg        

                            b.      Brand Name: Refers to branding image #2 in the previous figure. According to the PAR structure shown previously, the path would be:
/irj/portalapps/<tenant_name>/images/branding-image2.jpg     

                            c.      Stylesheet Path: Refers to the stylesheet to be used by the logon screen component. According to the PAR structure shown previously, the path would be:
/irj/portalapps/<tenant_name>/css/logon.css     

Note that the above properties also accept absolute URLs, such as: http://<anotherserver>:<port>/images/TenantABrandingImage.jpg

       4.      Save the tenant.

 

Result

The branding elements for the tenant's logon screen are available for use in the portal.

Recommendation

To customize the look and feel of the tenant's portal desktop, including the branding images displayed in the portal header area, create a custom theme using the Theme Editor in the portal. For more information, see Configuring Customized Portal Desktops for Tenants.

 

 

 

Leaving content frame