Sap Hana Solution Manager 7.1
The steps described in this wiki page have to be performed after finishing the SAP HANA setup steps on the SAP HANA database, the SAP HANA host and the SAP Solution Manager host, to finish the SAP HANA managed systems setup and make the SAP HANA system available for System Monitoring setup.
Prerequisites
Make sure you have performed the OS and DB level preparations for the Managed System Configuration as described here: Prepare Managed System Setup for SAP HANA
Check SAP HANA System in LMDB
Before running the managed system setup, you should check if the SAP HANA system was successfully reported from the SLD into LMDB of SAP Solution Manager. If you changed the SLDSYSTEMHOME for HANA to the SAPDBHOST in ABAP, the assignment between HANA and the ABAP system should happen automatically.
Even if the ABAP system already registered a HANA earlier via the RZ70 SLD data supplier, as long as HANA and the ABAP system register with the same SystemHome value, the assignment between HANA and ABAP system happen automatically. The formerly registered RZ70 HANA system will be enriched with the additional information from the HANA SLD data supplier.
Please note that SAP HANA systems with MDC and/or System Replication will have to look differently in LMDB than a simple SAP HANA installation. Please refer to the respective wiki pages for more information.
Call transaction LMDB and select you HANA system:
Make sure the product version is supplied automatically.
Check the SAP HANA DATABASE software is marked as Installed on Instance. This should at least be the case for the HANA master node.
Make sure all HANA nodes are reported under Technical Instances. For our database it is just one node, for multi-node HANA databases you should see multiple lines under "SAP HANA Database Server".
Check that the database known to your ABAP system matches the HANA DB. To do this, open the ABAP system in LMDB and check the database under System Database:
Run Managed System Setup for HANA
The next step is to run the managed system setup for HANA. HANA has its own Technical System Type, unlike other database systems. We run the managed system setup for HANA separately to make sure that the product SAP HANA DATABASE is recognized as diagnostics relevant. As it is not explicitly installed on the ABAP system, this would be missed, if we run only the managed system setup for the ABAP system.
Before you can run the managed system setup, make sure that the Diagnostics Agents for all HANA nodes are available. HANA nodes always register with their internal HANA hostname. So if you installed the agents manually without HLM but with the external HANA hostname you might have to create agents on-the-fly for the internal HANA hostnames. Or you just install the agents with the internal HANA hostname to begin with.
More information on agents on the fly can be found here.
To start the managed system setup for HANA, call transaction SOLMAN_SETUP → Managed System Configuration. Search for your HANA System. You'll find it on the tab "Technical Systems".
In the first step you have to create a product system for HANA and also assign the diagnostics relevance.
You can either use a product system that already exists for the ABAP system (if the ABAP system was already connected to Solution Manager) or create a new one. After all you should use the same product system for ABAP and HANA.
The diagnostics relevance can be set automatically. Click the respective button in the Managed System Setup.
In the next step you check the prerequisites. In step 3 you have to assign the Diagnostics Agents to each HANA node.
In step 4 you have to maintain the system parameters. You only have to set up the DB Connection in this step. Use the same user you created in HANA for monitoring earlier.
If you have any problems creating the DB connection, check if there is a DB connection in table DBCON (transaction DBCO). If yes, test the connection using the report ADBC_TEST_CONNECTION. The output of this report will tell you what is wrong and also lead you to the trace file of the workprocess in which the error occurred. If the DB connection doesn't exist yet, please try to create it in DBCO and test it.
The most common reasons for failures here is a not correctly installed HANA client or missing HANA DB libraries. Please refer to the section about the HANA client installation.
Remark:
You might notice that the value for "Database Host" is an IP address. This is correct! What you see in this field depends on the value that is delivered as connect string to the SLD. The origin of this value is the value that is maintained in the HANA view SYS.M_HOST_INFORMATION for the key net_publicname.
Whether this is an IP or a FQDN depends on the parameter use_default_route int he global.ini file of the HANA DB.
But back to SOLMAN_SETUP. In the step "Enter Landscape Parameters" you have to maintain the landscape parameters.
In some cases you will see the installation path as "<Not Defined>" on Technical System Level. You can ignore this. We are currently working on providing this value automatically.
This missing path will lead to an error in the Configuration Check later on:
If you want to fix this (technically you could also ignore this specific error until we fill this value automatically), you can do so by marking the software SAP HANA PLATFORM EDIT. 1.0:HANA database as "Installed on System" in the LMDB.
After this change you will be able to fill in the installation path in the managed system setup and the errors will go away.
The next step is the Automatic Configuration. Execute all and make sure everything finishes successfully. Make sure you see the activity "Database Extractor Setup" as well as "Extractors Setup".
In the step "Configure Manually" you set up the OSS connection to be able to open HANA DB for SAP in case you need remote support.
In the last step you check the configuration and make sure everything is OK.
If you run a multi-node HANA DB you now also have to make sure, that the HANA is still reachable if the master node moves to another host. Unfortunately we cannot do this automatically yet.
To make sure the HANA DB can be monitored and reached by DBACOCKPIT no matter who the master node ist, you have to adjust the DB connection used by DBACOCKPIT. You add all possible HANA master noder servers to the DB connection string.
Call transaction DBCO and open the DB connection for the HANA DB in change mode. Add the server names for all possible master nodes and ports separated by semicolon in the form:
<server1>:3<SysNo>15;<server2>:3<SysNo>15;<server3>:3<SysNo>15
You can test your DB connection using the report ADBC_TEST_CONNECTION.
The concept is also described in SAP note 1983628.
Run Managed System Setup for ABAP System
Run the managed system setup for the ABAP system as usual. You will see that some activities are already done by the SAP HANA Managed System Setup. You don't need to redo those steps.
Troubleshooting
If you have problem with the managed system setup please refer to the Troubleshooting section of this wiki.
Source: https://wiki.scn.sap.com/wiki/display/TechOps/Managed+System+Setup+for+SAP+HANA+with+Solution+Manager+7.1
0 Response to "Sap Hana Solution Manager 7.1"
Post a Comment