SAP HANA E2E
SAP HANA system is made of following components:
- SAP HANA mandatory components
- SAP HANA server
- SAP HANA client
- SAP HANA additional components
- SAP HANA studio
- Application Function Libraries (AFL and the product-specific AFLs POS, SAL, SCA, SOP, TRD, UDF)
- SAP liveCache applications (SAP LCA or LCAPPS-Plugin)
- SAP HANA smart data access (SDA)
- SAP HANA XS Advanced Runtime
- SAP HANA options
- SAP HANA dynamic tiering
- SAP HANA remote data sync
- SAP HANA smart data streaming
- SAP HANA accelerator for SAP ASE
Host
A host is the operating environment in which the SAP HANA database runs. The host provides all the resources and services (CPU, memory, network, and operating system) that the SAP HANA database requires. The storage for an installation does not have to be on the host. For multiple-host systems, a shared storage or a storage that is accessible on-demand from all hosts is required.
Instance (HDB)
An SAP HANA instance (HDB) is the smallest operational unit on a host. It is the set of SAP HANA system components that are installed on one host. A single-host system contains one instance on the one host. A multiple-host system contains several instances distributed across the multiple hosts (one per host). Every system has an instance number, which is a two-digit identifier. Each instance in a multiple-host system must have the same instance number.
System
A system is one or more instances with the same number. The term "system" is interchangeable with the term "SAP HANA database". If a system has more than one instance, they must be dispersed over several hosts as a multiple-host system. Every system has a unique SAP system ID (SID).shared storage system
Non-shared storage system
Single-Host Setup
Multi-Host Setup
Multi-Host System with Standby Host
Dedicated XS advanced runtime Host
HANA Network
Client zone: Network for SAP application servers, HTTP and SQL clients
Internal zone: Internode and System Replication Network
Storage zone: Enterprise Storage Network and Backup Network
VMware vSphere
SAP HANA is supported on VMware vSphere for scale-up, multi-VM and scale-out production environments, including SAP HANA Tailored Datacenter Integration deployments.
Hitachi LPAR
Hitachi Unified Compute Platform for the SAP HANA Platform with logical partitioning (LPAR) in a scale-up or multi-VM configuration is a pre-configured virtual appliance ready to plug into a network to provide real-time access to operational data for use in analytic models. SAP HANA on Hitachi solutions with logical partitioning are based on a number of bare metal appliance configurations with modifications that are required for running logical partitions (LPARs) in dedicated mode.
Huawei FusionSphere
SAP HANA is supported for production and non-production use in a virtualized environment using Huawei FusionSphere.
Red Hat Enterprise Linux KVM Hypervisor
SAP HANA is supported on the KVM (Kernel-based Virtual Machine) hypervisor in a non-production environment.
SUSE Linux Enterprise Hypervisor
SAP HANA can be run in virtualized environments using XEN and KVM for virtual single VM deployments for test and development scenarios. Both the XEN and KVM hypervisor are built into SUSE Linux Enterprise Server for SAP Applications.
IBM PowerVM
SAP HANA can be deployed on IBM PowerVM for IBM Power Systems. PowerVM is a combination of hardware, PowerVM Hypervisor, and software, which includes other virtualization features, such as the Virtual I/O Server.
cd <installation medium>/DATA_UNITS/HDB_LCM_LINUX_X86_64
./hdblcm
After installation:
- Perform a system backup
- Change the passwords
- Configure encryption on the SAP HANA server:
- Change the SSFS master keysSAP HANA secures content in two secure stores in the file system (SSFS): the instance SSFS and the system PKI SSFS. Unique master keys are generated during installation or update. However, if you received your system pre-installed from a hardware or hosting partner, we recommend that you change them immediately after handover to ensure that they are not known outside of your organization. You can also change the master keys any time later.
- Change and back up the encryption root keys used for SAP HANA data-at-rest encryption and application data encryption services.
- Enable data-at-rest encryption if required.
- Finalize customization
- Change the SSFS master keys
- Use SAP HANA lifecycle management tools to adapt the existing configuration
Start and Stop HANA
- using the sapcontrol :
- using HDB:
Displaying the Process List
/usr/sap/hostctrl/exe/sapcontrol -nr 00 -function GetProcessList
09.07.2015 14:09:20
GetProcessList
OK
name, description, dispstatus, textstatus, starttime, elapsedtime, pid
hdbdaemon, HDB Daemon, GREEN, Running, 2015 07 06 13:38:00, 72:31:20, 1195
hdbnameserver, HDB Nameserver, GREEN, Running, 2015 07 06 13:38:03, 72:31:17, 1213
hdbpreprocessor, HDB Preprocessor, GREEN, Running, 2015 07 06 13:38:18, 72:31:02, 1279
hdbindexserver, HDB Indexserver, GREEN, Running, 2015 07 06 13:38:26, 72:30:54, 1317
hdbxsengine, HDB XSEngine, GREEN, Running, 2015 07 06 13:38:26, 72:30:54, 1320
hdbcompileserver, HDB Compileserver, GREEN, Running, 2015 07 06 13:38:18, 72:31:02, 1282
hdbwebdispatcher, HDB Web Dispatcher, GREEN, Running, 2015 07 06 13:39:10, 72:30:10, 1540
- SAP HANA DB files:
- /var/lib/hdb - IPC data (volatile)
- /var/tmp - Installer log files, HDB_alive_*
- /tmp - .hdb_*_lock (volatile)
- sapstartsrv files:
- /etc/init.d/sapinit* - Boot script
- /tmp/.sap* - Sockets, lock files (volatile)
Comments
Post a Comment