2 LVM 2.0 Delta Overview

30
1

Transcript of 2 LVM 2.0 Delta Overview

Page 1: 2 LVM 2.0 Delta Overview

1

Page 2: 2 LVM 2.0 Delta Overview

2

Page 4: 2 LVM 2.0 Delta Overview

Enhancements and new features are available in the following fields:

Usability and CustomizationSystem ProvisioningAdditional Platform Support and Integration

4

Page 5: 2 LVM 2.0 Delta Overview

5

Page 6: 2 LVM 2.0 Delta Overview

6

Page 7: 2 LVM 2.0 Delta Overview

The following terms have changed:

Services are now called Instances and Systems.Resources have been renamed to Hosts, andController Logs are now just called Logs

7

Page 8: 2 LVM 2.0 Delta Overview

The pods are arranged in up to five columns on the dashboard. You can movethe pods around the dashboard by drag and drop. You can collapse and expandpods. If a pod does not contain any information, it is automatically collapsed.Different dashboards can have identical names.In some pods, for example, the Validation pod, you can navigate directly torelated information, such as instances, hosts, and virtual host provider.

Some features have been enhanced to improve usability:Navigation options are available on clicking on the pod detailsPods may be moved between dashboardsLegends are available in the podsThe Pod Edit/Add roadmap was replaced by a single viewDashboard title display has been enhanced.Dynamic height adjustments are performed based on contents and legendenabling

8

Page 9: 2 LVM 2.0 Delta Overview

The visualized system landscape lets you view landscape entities and theirrelationship, in a graphical form.

These are the default landscape views :PoolsVirtualization ManagersNetworksStorage Managers

These views help you in identifying the landscape entity hierarchy, dependenciesand their statuses in a simple and easy form.Other than the default views, if you want any specific landscape view to beavailable, you can configure the specific characteristics in the Configuration view.For example, (other than the default views), if you want to view the entities basedon their groupings, you can create a characteristic called Groups in theCharacteristic Configuration view. The newly created characteristic will beavailable in the Landscape Views dropdown list.

9

Page 10: 2 LVM 2.0 Delta Overview

You configure pools to group the landscape entities logically and separate themphysically. The logical grouping helps administrators to manage the hosts andinstances more efficiently.

You can group identical or different pools in a pool container. The pool containercan contain both pools and containers.

To create a pool or container, choose Configuration Pools.

10

Page 11: 2 LVM 2.0 Delta Overview

You configure characteristics and define the attributes for the characteristicsaccording to the needs of your company, such as:

Group instances and hosts according to these characteristics.Make the mass operations easier to handle.

To create characteristics, choose Configuration Characteristics.

Once the characteristics are defined in the configuration, they are added asentries to the Group By filter of the instance, host, and virtual host views. If acharacteristic is selected in the Group By field, the view is grouped accordingly.The characteristic values are the nodes with the instances and hosts underneaththem.

You can now assign colors to your characteristics and add a column for thecharacteristic to the overview table of the host, instance, or virtual host views.The name of the characteristic is then displayed in the table header of therespective overview table.

11

Page 12: 2 LVM 2.0 Delta Overview

You can define custom tabs to view external applications or files. This enablesyou to minimize the number of browser windows that you need to navigate to forreference while performing operations.You can specify the screen on which you want a custom tab to be available, as inthe above example, on the Overview screen.

12

Page 13: 2 LVM 2.0 Delta Overview

13

You can extend the existing operations and functionality to manage your own onpremise SAP system landscape.

To execute your own scripts on managed hosts from within SAP NetWeaverLandscape Virtualization Management, you must configure a providerimplementation definition type.

All custom operations and hooks get default parameters for the instances, hosts,and virtual hosts on which they are executed.

All configured custom properties of the instance are available with the prefixPROP-<Custom Property Name>.

For custom operations you can also configure your own parameters which haveto be set by the user and are available with the prefix PARAM-<CustomParameter Name>.

For further details, see the documentation.

Page 14: 2 LVM 2.0 Delta Overview

You can personalize basic settings in the user interface according to yourpreferences.

In the main menu, open the administrator user menu and choose Personalize.

The following options are available:

Enable Persistence for UI PreferencesSelect the checkbox to retain UI preferences in the same state even if youlog off.

Display Online Help Vertically [on the right-handside]Select the checkbox to view the online help pane on the right hand side ofthe screen. To view the help content at the bottom of the screen, deselect thecheckbox.

Online Help LanguageSelect the required help content language from the drop down list.

Time FormatSelect the appropriate time format from the dropdown list.

Icon Accessibility ModeSelect the checkbox to view the top level navigation icons.

14

Page 15: 2 LVM 2.0 Delta Overview

You can track changes by defining your custom change ID.

Custom change IDs need to be created in the configuration wizard of SAPNetWeaver Administrator.

Choose Configuration Scenarios Configuration Wizard.

The following options are available:

Enable Change IDTo assign a change ID to performed changes in SAP NetWeaver LandscapeVirtualization Management, select this checkbox.When selected, a dialog box appears after performing changes. The changeID entry is optional.

Mandatory Change IDTo assign a change ID to performed changes in SAP NetWeaver LandscapeVirtualization Management, select this checkbox.When selected, a dialog box appears after performing changes. The changeID entry is mandatory.

15

Page 16: 2 LVM 2.0 Delta Overview

The central instance is now taken into account in the calculation of available applicationservers.

Overall usability of Automatic Capacity Management has been enhanced.

16

Page 17: 2 LVM 2.0 Delta Overview

You can use the new Search field for a global search, and you can navigatebackward and forward using the arrow icons.

17

Page 18: 2 LVM 2.0 Delta Overview

18

Page 19: 2 LVM 2.0 Delta Overview

The near-zero downtime (nZDM) cloning scenario for SAP Netweaver Portal isnow available as an option in the Clone System function in the Provisioningscreen.

nZDM for SAP NetWeaver Portal is a procedure for the implementation ofsupport package stacks on a Portal system at minimum business downtime.The SP import is executed on a clone of the production system and a migrationto the clone is performed, including a transfer all recorded changes.

nZDM for the Portal is based on Java system cloning.

nZDM/Portal is currently available as consulting solution.It is planned to be generally available with SL Toolset Support Package 8.

19

Page 20: 2 LVM 2.0 Delta Overview

The following end-to-end scenarios for initial copy and refresh have already beensupported, including post-copy automation (PCA):

ABAP BasisECC and ERP

Additional scenarios are now available forSAP NetWeaver BWSAP CRMSAP SCM

For more details, see the above SAP Note.

Note that the predefined PCA task list are ready to run. They are called in the end-to-end process. They may also be executed as a standalone process. PCA may beconfigured to a customer’s particular requirements.

20

Page 21: 2 LVM 2.0 Delta Overview

You can execute post-copy automation (PCA) standalone to carry out severalconfiguration steps on a target system, which is not provisioned by SAPNetWeaver Landscape Management.

You can use post-copy automation for the following use cases:

Initial System Copy

System Refresh Export

System Refresh Import

21

Page 22: 2 LVM 2.0 Delta Overview

You can replace or add additional custom operations to the storage step orrename step during system provisioning.

To replace or add additional custom provider implementation definitions to thestorage or rename step, you configure custom provisioning processes.

Custom provisioning is needed for the following use cases:• Not all prerequisites for the standard provisioning processes are fulfilled.

Example: Virtualization, storage or other infrastructure dependencies.• The standard behavior is not suitable for your requirements.

Example: You want to use backup/restore.You can replace the following operations for storage cloning on the source ortarget system:• Prepare clone volumes• Clone volumes• Restore backup (only available for storage cloning on target system)• Post clone volumes• Finalize clone volumesFor system renaming, you can replace the operation SAPinst rename.

22

Page 23: 2 LVM 2.0 Delta Overview

23

You configure custom hooks so that you can invoke a provider implementation

definition implicitly for instances or virtual hosts.

This feature has been enhanced for system copy/refresh, as shown above.

The following options are available:Pre Hook: Custom hook is executed before the operation.Post Hook: Custom hook is executed after the operation.Error Hook: Custom hook is executed if operation fails.

Page 24: 2 LVM 2.0 Delta Overview

Select the storage volumes to be deleted at the end of the system refresh activity.

Select one of the following options:Do not delete storage volumesDelete with confirmationDelete without confirmation

Select the virtual hosts to be deleted at the end of the system refresh activity.Select one of the following options:

Do not delete virtual hostsDelete with confirmationDelete without confirmation

24

Page 25: 2 LVM 2.0 Delta Overview

For current details on system provisioning, see SAP Note 1709155.

25

Page 26: 2 LVM 2.0 Delta Overview

26

Page 27: 2 LVM 2.0 Delta Overview

27

Page 28: 2 LVM 2.0 Delta Overview

28

Page 29: 2 LVM 2.0 Delta Overview

You can view the work modes of systems that are managed by SAP NetWeaverLandscape Management in the SAP Solution Manager IT calendar. Work modesspecify downtimes for the managed systems and the reasons for the downtimes.Based on the system downtime schedule, you can manage the systems moreefficiently. Alerts for system downtimes may be explicitly suppressed.

To configure a managed system as an SAP Solution Manager system, chooseConfiguration Systems.Under Systems & Instances Overview, select the system you want to configure.

To view system work modes, choose Configuration Systems.Under Systems & Instances Overview, select the system.Under Systems tab, in Overview of systems and instances, click the MassOperations tab, and select the SolMan IT Calendar link.

29