sap lvm post copy automation integration
Post on 22-Jan-2018
139 Views
Preview:
TRANSCRIPT
SAP LVM Post Copy Automation Integration
• This is the third in a series of presentations dedicated to SAPLandscape Virtualization Management (LVM)
• This document provides a quick overview of how to integrateSAP LVM Post Copy Automation (PCA) in SAP LVM
• The document is aimed at system administrators responsiblefor configuring SAP LVM and performing SAP system copies
• The document assumes the reader has a high level ofexperience with system copies and associated terminology
Introduction
Overview• SAP LVM Enterprise Edition can be used for various system
provisioning activities such as cloning, copying, refreshing andrenaming of SAP systems
• With Enterprise Edition, customers have the option to use PCAfor ABAP and Java systems
• SAP LVM Enterprise Edition allows integration of PCA for SAPsystems without activating them for provisioning activities i.e. itcan be invoked in standalone mode
• This document focuses on the integration of standalone PCAwith an example showing steps following a database refresh
Pre-‐Requisites in ABAP• Before integrating PCA with LVM you must configure PCA in the back-‐
end systemthat is the target of the systemcopy• An overview of this configuration is available in SlideShare document
entitled “SAP Post Copy Automation”• In addition to this configuration, a system user (e.g. LVMADM) with
high authorizations (e.g. SAP_ALL) is required in all clients excludingclient 000
• This system user is used during the PCA BDLS task in the back-‐endsystemvia RFC calls from client 000 to all other relevant clients
• Ensure you know the password for SAP* in client 000 of the sourcesystem as this will be needed by PCA before the user masters areimported into the new target system
Configuration in LVM• Before being able to perform any system copy or refresh
related activities, the system must be enabled for provisioningin LVM
• The system is enabled for provisioning in the “Systems” tabunder the “Configuration” section
Configuration in LVM• Edit the system for which provisioning should be enabled and
select the “Standalone PCA” radio button in the “System and ASProvisioning” section
Configuration in LVM• Now, in the “Provisioning” section, with the system selected,
you will see the new button “Standalone PCA”• Standalone PCA can now be executed for this system
Task Lists• Depending on your scenario (i.e. copy or refresh) you will need
to decide which PCA tasks to execute in the system• For a system copy, you’ll probably want to include PCA standard
task lists SAP_BASIS_COPY_INITIAL_CONFIG andSAP_BASIS_COPY_BDLS
• For a system refresh (export), you’ll probably want to includePCA standard task lists SAP_BASIS_COPY_REFRESH_EXPORT
• For a system refresh (import), you’ll probably want to includePCA standard task lists SAP_BASIS_COPY_REFRESH_IMPORTand SAP_BASIS_COPY_BDLS
Execution for System Refresh• Start the standalone PCA with type “Task List Execution”
Execution for System Refresh• Using the “Add” button and drop-‐down, add tasks
– SAP_BASIS_COPY_REFRESH_IMPORT– SAP_BASIS_COPY_BDLS
• Modify the parameters for the BDLS task
Execution for System Refresh• Add logical systems pairs to be converted during the BDLS
execution
Execution for System Refresh• When all tasks have been added and parameterized, move on
to the summary screen
Execution for System Refresh• Start the execution
Monitoring the Execution• Basic monitoring of the standalone PCA execution can be done
via the “Monitoring” section in LVM
Monitoring the Execution• Detailed monitoring on the progress of individual tasks within
the PCA task lists can be done in the ABAP back-‐end systemusing transaction “STC02” in client 000
Reference Material• The following pages on SAP Help are useful:
– Provisioning Systems– System Copy– System Refresh– Refreshing a Database Only
• Further details are available on request – mailto:info@aliterconsulting.co.uk
Thank-‐you
top related