in MDC, hdbuserstore keys need to be set based on the SQL port.
- Keys for Systemdb must be set using SQL port 3<02>13
- Keys for Tenant DB must be set using SQL port 3<02>13@<Tenant_DB>
here <02> is instance number.
Showing posts with label for. Show all posts
Showing posts with label for. Show all posts
Friday, 12 February 2021
SQL Ports for HANA 2.0 to connect system database and tenant database
Tuesday, 1 December 2020
Determine Ports for SAP HANA Cockpit and Cockpit Manager
The ports for SAP HANA cockpit and the cockpit manager can be determined in the XS console after the cockpit installation.
Prerequisites
- You are logged in as <sid>adm user.
- You know the XS organization manager user password. The password matches the master password, which is set during installation.
Context
Ports, through which the SAP HANA cockpit and the cockpit manager can be accessed, are assigned automatically by the installer. Once the cockpit installation is successfully completed, information about host and ports is displayed. If this information is no longer available, you can execute the following commands in the XS console to determine ports.
You can also assign free ports to SAP HANA cockpit during installation. For more information, see SAP Note 2389709 in Related Information.
Procedure
Friday, 27 November 2020
rdisp/tm_max_no
Parameter
rdisp/tm_max_no
Short text
Maximum number of possible logons
Parameter Description
This parameter restricts the maximum number of logons per instance. This includes SAP GUI logons, RFC and HTTP logons, and also logons for internal tasks (for example, the execution of background jobs or updates).
Application Area
Dispatcher
Default Value
200
Who is permitted to make changes?
Customer
Operating System Restrictions
None
Database System Restrictions
None
Are other parameters affected or dependent?
None
Values allowed
Whole Number >= 10000
Sunday, 22 November 2020
step by step process for SAP User audit(EULA)
1.Based on the SAP contract, each customer is obligated to perform system measurement of a systems.
2.measuring the system determines No. of SAP systems are in use and No. of user of SAP systems.
3.Before system measurement takes place SAP sent. so called measurement request to the customer. with some details how to perform such a measurement.
3.Before system measurement takes place SAP sent. so called measurement request to the customer. with some details how to perform such a measurement.
with the measurement request following attachments are available:
select the type of the system. in case any client in the system of type production. select the checkbox for production.
in client tab:
in the price list tab: need to select the price list according to your SAP software contract.
Depending on the selected price list chosen, the system shows related default use which is used to classify the unclassified users.
To specify the customer specific user type can defined here by replacing the special module type with best description and can user in defining user type in su01 --> LIC data tab.
All the information provided in the 5 tabs should be correct and accurate. to avoid cross questions from SAP.
Need to switch to valid users list.
with valid users option, users with validity will only will be listed.
select all unclassified or user which need to classify and go with the option classify selected Records:
Select the correct and required user type from the drop down and click on save.
select the user type in the drop down and SAVE.
Mass change option in USMM tcode.
here we have 2 option,
1. to classify all non classified user at once.
System measurement logs: logs provide all relevant information by last system measurement.
the measurement logs are structured in different sections:
Troubleshoot logs:
in case of any wrong assignments
After pressing the logs option --> the below pop up will be shown in the screen with the inconsistency list.
The system determines and display users that are made entries in certain database tables during 4 weeks period from the system measurement and which activity do not match the currently selected user classification. This user should be classified as either professional or limited professional.
Consolidation: which consolidates measurement results to avoid multiple counting of same user.
- measure plan: information about all installation and systems.
- special version of measurement plan: need to upload to measurement tool SLAW.
- self declaration plan: To add new product for the measurement plan.
- snote list. - provides the list of snote that need to implement before system measurement.
To perform system measurement need 2 t-codes:
- USMM : system measure for single system.
- SLAW ; consolidation all systems measurement.
start system measurement: need to perform on each system in the measurement plan.
1. enter the T-code: USMM.
select the type of the system. in case any client in the system of type production. select the checkbox for production.
in client tab:
Enable all the production clients in the production server.
Enable all the development clients in the dev server. similarly for QAS server also.
remaining clients can be uncheck for the system measurement.
in the price list tab: need to select the price list according to your SAP software contract.
in the system measurement request email. the info about the price list is available.
Depending on the selected price list chosen, the system shows related default use which is used to classify the unclassified users.
User types: the user list available in the list here. can be used for user classification.
SAP recommends to uncheck the active check box for the user types which are not required.
To specify the customer specific user type can defined here by replacing the special module type with best description and can user in defining user type in su01 --> LIC data tab.
Address tab: if need to get conformation once audit data sent to SAP. Need to maintain sender and receipt mail id here.
All the information provided in the 5 tabs should be correct and accurate. to avoid cross questions from SAP.
User classification:
Please note that you can classify and reclassify user with in the logon client users.
Please note that you can classify and reclassify user with in the logon client users.
Need to switch to valid users list.
with valid users option, users with validity will only will be listed.
select all unclassified or user which need to classify and go with the option classify selected Records:
select the user type in the drop down and SAVE.
here we have 2 option,
1. to classify all non classified user at once.
2.Change user type from one type to another.
to classify non classified user, follow the below process.
1. Select the user type for the unclassified users.
2.Click on execute.
To change already defined user type in to another perform the below navigation.
System measurement logs: logs provide all relevant information by last system measurement.
To display the measurement results. Click on the logs.
- sender and recipients information provided in the address tab.
- system data includes installation number and system type info.
- Status of background job should be finished for all the entries.
in case of any wrong assignments
After pressing the logs option --> the below pop up will be shown in the screen with the inconsistency list.
here i am selecting professional users w. Inconsistent Classification.
then followed by workbench users with inconsistent classification.
The system determines and display users that are made entries in certain database tables during 4 weeks period from the system measurement and which activity do not match the currently selected user classification. This user should be classified as either professional or limited professional.
To check what is the activity performed by the user to make him as professional or limited professional user --> Click on the Activity box as highlighted below --> change --> make the user changes --> save.
if you use license agreement tool to consolidate the result, download measurement results per system.
In the menu bar go to system measurement --> Export to LAW file.
alternative download for Email and sent result through email.
Now we can go for Prod login as we are sending through the SAP Central Instance Installation production system.
- Run T-code SLAW:
- Here we can upload the template(.xml file) given by SAP & upload all the req systems License report or here in you may just leave as it is if no new SAP system launched since last year & just make a reply mail by saying that other systems we are not using. If want to upload the .xml file then, as below Change view-> Maintain RFC Data
Then save the .xml file sent from SAPLabs to your desktop & as follows click on the open button to browse to the .xml template & click open & it will show what & all the systems are required to be measured as per SAPLabs & whatever systems License data you will not be sending to SAPLabs , you can just select the column & press the delete button as follows,
in case the system is not in use from last system measurement to now.
in case any new system added from the last system measurement. choose add button as shown below (4).
once after adding all the system data start consolidation and sent the final result to SAP.
Sunday, 25 October 2020
Measure System & Performance - Scale-up Systems
Pre-requisites:
- You have installed the latest version of the SAP HANA hardware and cloud measurement tool on the system.
- You have at least 20 GB of free storage space in the location where SAP HANA data can be placed during the test.
- When using nonvolatile memory, mounts for all hosts or an alias of the same name must be available.
- Port 50001 must be open for communication.
The measurement tool performs a series of automated tests based on the execution plan that you select, for
example (executionplan.json or full_executionplan.json).
Procedure
1. To start the measurement tool in verbose mode, enter hcmt -v.
2. Adjust the following variables that are contained in the execution plans:
3. . Enter hcmt -v -p
Saturday, 24 October 2020
SAP HANA Hardware and Cloud Measurement Tools for scale out systems
SAP HANA hardware and cloud measurement tools help customers and partners to optimize their hardware or
cloud systems before deploying SAP HANA.
The measurement results are saved into a single file, which can be uploaded to the SAP HANA hardware and cloud measurement analysis for further analysis and reporting.
prerequsites:
1. Download the SAP HANA hardware and cloud measurement tool from the SAP Support Portal at https:// launchpad.support.sap.com/#/softwarecenter INSTALLATION & UPGRADES Access downloads Search for: hana optim .
The download package is displayed: HANA HW CLOUD OPTIM TOOLS 2.0.
The following versions are available:
○ LINUX ON POWER LE 64BIT
○ LINUX ON X86_64 64BIT
2. Select the version according to your requirements.
3. Save the download archive in the same directory into which the tool should be installed.
4. Unpack the archive using SAPCAR.
5. Install the tool on the system you plan to analyze using hcmtsetup.
How it works:
The SAP HANA hardware and cloud measurement tool performs a series of automated tests, for example
network tests, file system consistency tests, system management BIOS tests, and CPU benchmark tests. The
duration and repeat rate of the tests depends on the type of execution plan that you intend to run. The
following execution plans are available:
● executionplan.json - Default execution plan that helps you to check if the KPIs for SAP HANA certificDtion are met.
● full_executionplan.json - Performs the same tests as the default execution plan, but has a higher test repeat rate and thus a longer test duration. This test is required for SAP HANA certification.
Measure System Configuration and Performance - Scale-out Systems:
Prerequisites
● You have installed the latest version of the SAP HANA hardware and cloud measurement tool on the system.
● You have at least 20 GB of free storage space in the location where SAP HANA data can be placed during the test.
● When using ROM memory, mounts for all hosts or an alias of the same name must be available.
● Ports 50000 and 50001 must be open for communication.
. For scale-out systems, you start the measurement tool on the master host and specify any worker hosts on which the tests should run as well. The tool reads the execution plan, starts the test locally, and delegates tests marked for scale-out to the worker hosts. The tool waits for the completion of the tests on the worker hosts before starting the next test in the execution plan. All test measurement data and the host manifests are collected in one result file written by the master host instance.
Procedure:
1.To start the measurement tool on the worker hosts in verbose mode, enter hcmt -v -S on each of the hosts.
2. To start the measurement tool on the master host in verbose mode, enter hcmt -v.
3. Adjust the following variables that are contained in the execution plans:
-----------------------------------------------------------------------------------------------------------------------------
Variable user entry
-----------------------------------------------------------------------------------------------------------------------------
Log volume Specify the location where logs should be written.
Data Volume Specify an existing location where SAP HANA data can be
placed.
<NvmBasePath> if persistent memory is available, specify mount paths of this persistent memory separated by commas, if no persistent memory is available, leave empty.
4. Enter hcmt -v -p
Tuesday, 20 October 2020
SUSE Linux Enterprise Server 15.x for SAP HANA
Software required:
The following software was used for the installation:
- ISO file of SUSE Linux Enterprise 15.
- Required registration key for the SUSE subscriptions in order to get SUSE maintenance updates.
- To check the minimum requirements between SUSE and SAP HANA: S-Note - 2235581.
You must have the following information about the host on which you intend to perform the installation:
● IP address of the host
● IP alias for SAP HANA (optional)
● Host name of the host
● Subnet mask
● Domain name
● IP address of the name servers
● Address of a time server (ntp / chrony)
● Gateway IP address
● Proxy IP address and credential (optional)
● Password for the root user and credential (optional)
● SAP master password (<sid>adm and sapadm password)
- Boot your machine from the SUSE Linux Enterprise media.
Choose Installation on the boot screen, then press Enter. This boots the system and loads the SUSE Linux
Enterprise Server installer
- Updating the Installer (if internet connection is available)
Language, Keyboard and Product Selection
Agree with the License Terms.
- Choose a network interface from the list and click Edit to change its settings. Use the tabs to configure DNS and routing.
- When you are done with the network settings, choose Next to proceed or return to the Registration screen. After at least one network interface has been configured you can register your system at the SUSE Customer Center (SCC).
- Enter the e-mail address associated with your SCC account and the registration code for SUSE Linux Enterprise Server. A successful registration is a prerequisite for getting product updates and being entitled to technical support.
- If SUSE Linux Enterprise Server for SAP Applications has been successfully registered at the SUSE Customer Center, you are asked whether to install the latest available online updates during the installation. If choosing Yes, the system will be installed with the most current packages without having to apply the updates after installation. Activating this option is recommended. If you have successfully registered your system in the previous step, a list of available modules and extensions based on SUSE Linux Enterprise Server is shown.
- Add the Legacy Module in order to be able to install for example libopenssl1_0_0.
Other interesting modules you may need, depending on your usage of the system, are:
○ SUSE Linux Enterprise Live Patching 15 (adds support for performing critical patching)
○ Development Tools Module 15 (contains compilers like gcc)
○ If you use SAP HANA in the public clouds, the Public Cloud Module 15
Choose Next to proceed with the installation workflow.
- After all extensions and modules are registered the next step is available. The installation of Add On Product’s can be prepared if needed. Proceed with Next.
- Choose Next for the System Role selection.
- Choose the default SLES for SAP Applications and choose Next. This option is the preferred and the recommended installation.
check the checkbox for Enable remote Desktop protocol(RDP) service and open port in firewall option, go continue with Next.
Subscribe to:
Posts (Atom)