Config Personas3SP01 Final

8/20/2019 Config Personas3SP01 Final

http://slidepdf.com/reader/full/config-personas3sp01-final 1/13

SAP Library

SAP Screen Personas Configuration 2015_SP43 1

SAP Screen Personas Configuration

PUBLIC | CUSTOMER | INTERNAL | CONFIDENTIAL | STRICTLY CONFIDENTIALDocument Version: 2015_SP43 – 6/30/2015



SAP Library


Copyright© 2015 SAP SE or an SAP affiliate company. All rights reserved

SAP Library document classification: PUBLIC

No part of this publication may be reproduced or transmitted in any form or for any purpose without

the express permission of SAP SE or an SAP affiliate company

SAP and other SAP products and services mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other

countries. All other product and service names mentioned are the trademarks of their respective

companies.

Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional

trademark information and notices.

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark






SAP Library


Icons in Body TextIcon Meaning

Caution

Example

NoteRecommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types of

information at a glance. For more information, see Help on Help General Information Classesand Information Classes for Business Information Warehouse on the first page of any version ofSAP Library .

Typographic ConventionsType Style Description

Example text Words or characters quoted from the screen. These include field names, screentitles, pushbuttons labels, menu names, menu paths, and menu options.

Cross-references to other documentation.Example text Emphasized words or phrases in body text, graphic titles, and table titles.EXAMPLE TEXT Technical names of system objects. These include report names, program

names, transaction codes, table names, and key concepts of a programminglanguage when they are surrounded by body text, for example, SELECT andINCLUDE.

Example text Output on the screen. This includes file and directory names and their paths,messages, names of variables and parameters, source text, and names ofinstallation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in the systemexactly as they appear in the documentation.

<Example text> Variable user entry. Angle brackets indicate that you replace these words andcharacters with appropriate entries to make entries in the system.

EXAMPLE TEXT

Keys on the keyboard, for example, F2 or ENTER.



SAP Library


SAP Screen Personas Installation and Configuration ..................................................................... 5

1 Installing SAP Screen Personas 3.0 ......................................................................................... 6

2 Configuring SAP Screen Personas 3.0 ..................................................................................... 7

3 Configure Authorizations and Roles ......................................................................................... 9



SAP Library


SAP Screen Personas Installation and Configuration

This document describes all necessary activities for the installation and initial configuration of

SAP Screen Personas 3.0 SP01. In addition, it proves information about the components andguides that are required during the implementation process.

Implementation Considerations

SAP Screen Personas 3.0 requires SAP NetWeaver Basis 7.40 and kernel release 7.42 or above.Note the following implementation considerations:

Kernel Basis SP Supported Additional RequiredNotes

Required KernelExchange

738 SP1, SP2 (No) (Not supported) (Not supported)

740 SP3, SP4 (Yes) (Yes) (742 )

741 SP5, SP6,SP7

(Yes) (Yes) (742)

742 SP8 (Yes) (Yes) (None)

742 SP9 or above (Yes) (None) (None)

Make sure to install the required minimum kernel patch level according to SAP Note 2175479.

For roadmap information on kernel release and basis service packs please read SAP Note1969546.

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fsap%2Fsupport%2Fnotes%2F2175479









SAP Library


1 Installing SAP Screen Personas 3.0

Procedure

1. Deploy kernel and the necessary kernel patch.

o For more information about kernel exchange please read SAP Note 19466.

o Note that the kernel is composed of multiple components that do not always havethe same version number, i.e. some components are updated more frequently.When a kernel version is recommended by the Personas Team, then this usuallyrefers to the patch level of the disp+work package found in Service Marketplaceunder section “Database independent” , based on your OS and kernel version.

Apart from this, please make sure that you keep all components up to date.

2. If your NetWeaver Basis Support Package level is below SP9, you must implement SAPNote 2007072 – Class include is not activated following implementation of SAP Note.Without this, there is a risk of bringing your NetWeaver into an inconsistent state.

o Important: After applying this note, close your current SAP GUI session, andreconnect to your system before proceeding. This step is required because withSAP Note 2007072 you have updated the correction workbench itself and thecorrection only becomes active with the next ABAP session that is created.

3. Depending on your NetWeaver SP level, apply one of the following SAP notes:

o NW 7.40 SP3:SAP Note 1918906 – SAP Screen Personas 3.0 Basis Enablement

o NW 7.40 SP4,5,6,7:SAP Note 2044643 – SAP Screen Personas 3.0 Basis

Enablement

4. Install the Personas 3.00 add – on and the SP01 support package.

When upgrading from the original Personas 3.0 installation SP00 to SP01, you canignore the SPDD warning about modified Data Dictionary objects, accept all changesincluded in SP01 and continue with the import.

5. Implement all the basis and Internet Transaction Server (ITS) related notes according toSAP Note 2175479 as applicable to your environment. Depending on your NW 7.40Basis SP level, SNOTE will tell you if the note is needed.

6. Apply all the SAP Screen Personas notes listed in SAP Note 2175479. For this, adjustthe System Change Option via transaction SE06 so that software componentPERSONAS and namespace /PERSONAS/ are set to “Modifiable”.

o SAP Note 2175479 is always kept up – to – date to include all notes relevant forSAP Screen Personas 3.0 SP01. Therefore it is recommended to subscribe tothis note in order to help keep your Personas installation current.



































SAP Library


2 Configuring SAP Screen Personas 3.0

Procedure

1. Configure the following Profile Parameters using transaction RZ11:

o Update the current value of parameter em/global_area_MB to at least 1 GB. Forfurther details, check SAP Note 1888428

o Update the current value of parameter ztta/diag_area to at least 20MB(20000000 bytes). For further details, check SAP Note 204502

The current value of the above mentioned profile parameters will be lost onsystem restart when changed via transaction RZ11. Consult your System

Administrator to update the instance profile values to make these settingspermanent.

2. Complete the Service Configuration

o Activate the following services in transaction SICF:

/default_host/sap/bc/personas

/default_host/sap/bc/personas3

/default_host/sap/bc/gui/sap/its/webgui

o Ensure and test that the webgui service is fully operational

o Verify that the service “personas” has the following GUI Configurationparameters:

Parameter Name Value

~WEBGUI 1

~XSRFCHECK 1

~THEME sap_bluecrystal

~WEBGUI_DLGAREA2 1

~WEBGUI_DLGAREA2_MBAR 1

SAP-IE edge

SAP-HTMLRENDERMODE standards

3. Assign Roles

In this step, you will assign Personas role(s) for the specified user(s). You can either usethe pre – configured shipped roles or create new ones.

o Go to transaction SU01, select a user and under the Roles tab, enter one of thefollowing pre – configured roles:











SAP Library


/PERSONAS/ADMIN_ROLE (for full rights to all Personas features)

/PERSONAS/EDITOR_ROLE (for full access to all flavor – and theme – editing features, but not the administration functions)

/PERSONAS/CONSUMER_ROLE (for read – only / rendering access toPersonas flavors)

o Alternatively, you can also create new roles. Refer to Configure Authorizationsand Roles.

4. Use the Configuration Checklist

o Go to transaction /PERSONAS/ADMIN and click on the Run Health Check Toolbutton under the Additional Administrative Tasks. Look through all the entriesand ensure that all of them have a status Green/Yellow.

o Make sure you are using the latest version of your web browser to edit flavors.Please see SAP Note 2050838 for browser considerations.

5. Test Configuration

In this step, you will launch Personas 3.0 SP01.

o In transaction SICF, select Hierarchy Type SERVICE and Service Namepersonas then hit Execute (F8).

o In the Services tree list, right click on the service personas and select TestService.

o Your default web browser will open and the WebGUI comes up. After some initialcompilation and decompression time (on first load per application server) the

browser shows a blue line on top and the (Personas) icon appears.

o Click this icon to launch Personas 3.0 SP01.







SAP Library


3 Configure Authorizations and Roles

SAP Screen Personas 3.0 will only be enabled for a user when the relevant authorizations (basedon a user role) are granted. This is essential since without the necessary authorizations, thesolution will not be available. Roles are assigned to user via the regular user administrationprocess.

Process Flow

As mentioned in the Configuring SAP Screen Personas 3.0 section, the standard product deliveryincludes three roles. You can use these roles to allow users access to the system via Personas.

After installation of the Personas add-on, these roles do not yet have the necessary authorizationprofile. Please ensure that you create the authorization profile for each role via transaction PFCG to fully activate them before assignment.

If these roles are not sufficient, new roles can also be created using transaction PFCG. Based onthe three delivered standard roles and using the below authorization objects, you can definecustom roles to achieve the desired level of granularity to control access to various Personasfunctions.

SAP Screen Personas uses the following authorization objects:

Transaction code check at transaction start (S_TCODE)

o This is the usual object which determines what transaction codes the user isallowed to run.

Administration Authorizations (P_ADMIN)

o This object controls the Personas Administration features

Author izat ion Value Description

Admin Activity 01 Admin

Full administrative access to all features in transaction/PERSONAS/ADMIN

02 Support

Access to transaction /PERSONAS/USERS and/PERSONAS/FLAVORS. Ability to share or assign flavors to user or

roles.

03 Analytics

(Placeholder for future use)

04 Translation

Access to flavor translation without permitting other admin functions (via



SAP Library


transaction /PERSONAS/FLAVORS)

Edit Authorizations (P_EDIT)

o This object controls the features which allow accessing various activities whileediting flavors or themes

Author izat ion Value Descr ipt ion

Edit Activity 01 Position/Size

Allows setting the coordinates and size parameters of screen controls.

02 Set Default

Set default field values for text fields, checkboxes, radio buttons etc.

03 Font

Set font family, color, size and other properties of controls texts.

04 Style

Style group functions, like Fill Color, Border Style, Read Only,Suggested etc.

05 Annotate

Access to “Insert” tab. Add labels, sticky notes, images, HTML viewer. Access Toolbox (deleting objects and cloning controls).

06 Macros

Add buttons, dropdowns, checkboxes and text fields. Assign scripts tocontrol – or screen events. Access to “Tables” tab.

07 Advanced

Permits the use of Conditional Formatting in the Tables tab.

08 Admin Edit

Access to Compress Undo History and Versioning in the Release Tab.

Framework 01 Dynpro

Allows the selected activities for the specified traditional Dynpro – based transactions.

02 Web Dynpro

Allows the selected activities for the specified WDA application(s).

Application ID Transaction code(s) or WDA application name(s).



SAP Library


Runtime authorizations (P_RUNTIME)

o This object will control the activities the user can perform with a flavor or atheme.

Authorization Value Description

Runtimeactivity

01 Use_Flavor

Allows running the assigned default flavor

02 Select_Flavor

Allows selection of the desired flavor via the Flavor Bar

03 Manage_Flavor

Access to the Flavor Gallery and ability to move flavors to theflavor bar

04 Edit_Flavor

Access to flavor sharing, editing, creation and deletion

05 Scripting

Permits the use of the Script Editor

06 Theming

Allows using the Theme Editor

07 Admin_Runtime

Permits editing of flavors that are owned by other users

Framework 01 Dynpro

Allows the selected activities for the specified traditional Dynpro – based transaction.

02 Web Dynpro

Allows the selected activities for the specified WDA application(s)

Application ID Transaction code(s) or WDA application name(s)



SAP Library


The following matrix explains how these authorizations are distributed in case of the standarddelivered roles:

Values Roles

Consumer Editor Admin

Transaction Code

/PERSONAS/* X

/PERSONAS/ADMIN X

/PERSONAS/FLAVORS X

/PERSONAS/LAUNCH X X

/PERSONAS/RESOURCES X

/PERSONAS/ROLES X

/PERSONAS/TEST X

/PERSONAS/THEMES X

/PERSONAS/USERS X X

Admin Activity

01 – Admin X

Edit Activity

01 Position Size X X

02 Set Default X X

03 Font X X

04 Style X X

05 – Annotate X X

06 Macros X X

07 Advanced X X

08 Admin Edit X X

Runtime Activity

01 – Use Flavor X X X

02 – Select Flavor X X X

03 – Manage Flavor X X X



SAP Library


04 – Edit Flavor X X

05 – Scripting X X

06 – Theming X X

07 – Admin Runtime X

Framework

Dynpro X X X

Web Dynpro X X X

Application ID

TCode/Application ID * * *

Config Personas3SP01 Final

Documents

Transcript of Config Personas3SP01 Final