Skip to end of metadata
Go to start of metadata

SAP Screen Personas - Getting started guides



Create:
Sebastian Steinhauer

Error rendering macro 'page-info'

com.atlassian.confluence.user.ConfluenceUserPreferences.getDateFormatter(Lcom/atlassian/confluence/core/FormatSettingsManager;)Lcom/atlassian/confluence/core/DateFormatter;

Last Update:
Regina Sheynblat

Error rendering macro 'page-info'

com.atlassian.confluence.user.ConfluenceUserPreferences.getDateFormatter(Lcom/atlassian/confluence/core/FormatSettingsManager;)Lcom/atlassian/confluence/core/DateFormatter;

An introduction to Additional Administrative Tasks


- by Regina Sheynblat , Sebastian Steinhauer

Purpose

This is a quick guide designed to help users understand the various additional administrative tasks an admin can perform in Screen Personas 3.0.

Personas Health Check

Personas Services Check

For Personas, the following 3 ICF services should be active with compression ON:

  1. personas
  2. personas3
  3. webgui 

When using Personas Web Dynpro ABAP additionally ICF Service ui5_ui5 should be enabled.

Personas  System Check

  1. em/global_area_MB : The Health Check tool just checks for initial configuration. You have to make sure that this value is calculated based on the points mentioned in SAP Note 1888428.
    For initial check, these are the traffic light indicators:
    a. Green : >512 MB
    b. Yellow : between 96 and 512 MB
    c. Red : <96 MB
  2. Memory available to ITS : This value indicates the CURRENT remaining memory available to the Internet Transaction Server (and Personas). It is influenced by the value of system profile parameter em/global_area_MB.
    The traffic light meaning is as follows:
    a. Green : If remaining memory is >10% of the allocated memory available to ITS
    b. Yellow : If remaining memory is between 1% and 10% of the allocated memory available to ITS
    b. Red : If remaining memory is < 1% of the allocated memory available to ITS
    Please note that this is just an indicator for administrators to know what's going on in their system. This parameter doesn't have to always show GREEN. For example, if the memory available to ITS is 500 MB and remaining memory is 15 MB (which is <10%), this health check value will be YELLOW, but if you have just a few active users, you should be OK. However if you have many concurrent users, then you need to increase em/global_area_MB based on note 1888428.

  3. zcsa/second_language: Checks whether a second system language has been set up which is supported by Personas. Currently supported are english, german, french, portuguese, spanish, chinese, russian and japanese.
  4. Personas / Level (Component): Shows the current Support package Level
  5. Personas / Package: Shows the current Service Pack file
  6. Personas / Transport System synchronization (Performance): Yellow in case the transport system data has not been synchronized yet. To synchronize press the toolbar button "Synchronize Transport System data". The synchronization copies all personas-related transport-data from system table E071 to table /PERSONAS/E071. Afterwards Personas will use its own table for transported objects only. As table E071 is a very huge system table the use of this table speeds up the Personas Admin Tools a lot.
  7. Personas / Object editing: A yellow sign indicates that object editing of transported Personas objects (flavors, ...) is allowed in the import-Systems as well (non-original systems).
  8. Personas / Inactive Objects: Indicates whether any inactive objects are existing in the /PERSONAS/-Namspace. If yes the sign is yellow. It indicates that something may be wrong (as for example a note has not been completely implemented).
  9. SAP_BASIS / Service Pack: Checks whether the minimum required/recommended SAP_BASIS service pack has been implemented in the local system. The minimum service pack is dependent on the installed SAP_BASIS version.
  10. SAP Note <n> / Implementation Status: Shows all available and recommended SAP Notes which can be implemented in your local system. To update the list please press on the toolbar button "Personas Notes Checker".
  11. ztta/diag_area : This value should be minimum 10 MB unless your kernel patch level allows dynamic allocation of the users' dialog area. The kernel patch information can be found in SAP note 2299342. More details can be found here.
  12. Kernel release : Shows whether your current kernel release is supported by Personas.
  13. Kernel Patch Level : In general, it's preferable to keep the kernel patch level to the latest if possible. The Health Check will show RED light if the current kernel patch is lower than the minimum required level based on the Personas Service Pack

Updated the Administration Guide for SP07 (4/24/2018)

Cleanup Tools

This screen will allow you to clean up your system. Be careful, as any action from this screen cannot be undone.

  1. Flavors: All the flavors which are marked as "deleted' will be removed permanently.
  2. Resources: All the flavors which are marked as "deleted' will be removed permanently.
  3. Themes: All the themes which are marked as "deleted' will be removed permanently.
  4. Icons: All the icons which are marked as "deleted' will be removed permanently
  5. Roles: All the roles and their assignments which are marked as "deleted' will be removed permanently
  6. Templates: All the templates which are marked as "deleted' will be removed permanently
  7. Flavor Cache: This should only be used when certain flavors are corrupted OR SAP support OR SAP Note asks you to do it.
  8. MIME Cache: This action will delete all the server MIME cache entries. This should only be used when you have applied a note where some client side sources are shipped. The note will have the information whether you need to do this step or not.
  9. Migration Mapping: The migration mapping table can become large if you are creating migration mapping for many transactions. This will give you an option to delete all migration mapping entries. Do not use this if you are in the middle of a Personas 2.0 to Personas 3.0 migration.

Updated the Administration Guide for SP07 (4/24/2018) 

Data Model Analysis

The data model analysis checks the Personas database layer and tries to find inconsistencies in the Personas data model. Here are some examples:

  • In case a user got deleted from the system, the data model analysis checks whether the flavor is still shared with the deleted user or whether the deleted user is the owner of the flavor. The same applies also for PFCG roles.
  • In case the user is the owner of a flavor, the flavor must be shared with the same user too. This behavior on database level changed from Personas 3.0 SP0 to SP1
  • In case a flavor exists for a deleted/missing transaction. For example this could happen if a transaction got deleted or a flavor got imported into a system which doesn't have the corresponding transaction.
  • In case the tool shows some other errors, this could point to a bug in the system. This error should be reported to SAP and analyzed by the ABAP backend team.

The tool currently offers 4 options:

  • Check Flavor Data Model: The tool checks the database consistency for flavors. No data is changed.
  • Fix Flavor Data Model: Same as "Check" but with additional adjustment of the database tables. For example, sharing with deleted users will be deleted too.
  • Check Resource Data Model: The tool checks the database consistency for resources. No data is changed.
  • Fix Resource Data Model: Same as "Check" but with additional adjustment of the database tables. Inconsistent data will be deleted.

The "Fix" buttons should be only used after a deep analysis of the check button results!

 Updated the Administration Guide for SP07 (4/24/2018)

 

 

 

 

 

 

Important News

This knowledge base is not solely SAP provided content - but community driven. Please also check on SMP and help.sap.com for SAP released information and notes on SAP Screen Personas.

Create New Article

Compare SAP Screen Personas versions

Search the KB

How to Open OSS Message

 What information is needed for creating OSS message?

  1. Make Sure you are on the latest patches and notes.
  2. Kernel Patch Level
  3. Two Types of connections to your environment: HTTP and R/3
  4. All the connections should be tested with proper credentials provided
  5. Steps to re-create the issue
  6. Attach related logs
  7. File tickets against BC_PER

 

 

 

 

  • No labels