Solution Manager 7.2 SP05 (Up-to-date) installation and Configuration on SAP HANA Database (MCOS) on Distributed environment
Hello All,
Would like to share my experience about the installation and configuration of Solution Manager 7.2 on SAP HANA SP12 ( MCOS)
As we all know, Solution Manager 7.2 is now based on Netweaver 7.4 and is no longer a Dual-Stack system.The split of functionalities between the ABAP and Java in 7.2 seems to be similar to 7.1, so the Java Stack mainly handles the communications with the various agents. Since the java stack keeps connections open to all the agents
Solman 7.2 supports up-to-date installations. The installation doesn’t have anything special than normal procedure the software DVDs must be downloaded manually but the maintenance planner will enable us to calculate and generate the stack file up to latest SP available in SMP directly without adding the system to SLD/LMDB
– Simply install the ABAP stack then the Java stack. The Java stack will use the ABAP stack for UME (User Management)
– Update the ABAP and Java systems to latest version using SUM
Our environment:
Operating system: RHEL 7.3
HDB Version: 1.00.122.03.1475845474
Solution Manager 7.2 SP05
ABAP SID – SMA
JAVA SID – SMJ
We are installing in distributed environment (Database is on one host, SAP application is another host)
SAP Media:
- Download all the Solution Manager 7.2 software’s from Service Market Place and Install the Solution Manager 7.2 system
- Calculate the latest (up-to-date) support stack files for update (for eg: SP05) using Maintenance Planner (MP)
- Update Solution Manager system to SP05
1.Solution Manager 7.2 installation on SAP Hana Database
I. SMA – HANA Database installation
II. SMJ – HANA Database installation
III. SMA – ASCS Installation
IV. SMA – Database Instance Installation
V. SMA – Primary Application server Instance installation
VI. SMJ – SCS Instance Installation
VII. SMJ – Database Instance Installation
VIII. SMJ – Primary Application Server Instance
IX. Solution Manager 7.2 SP05 update
I. SAP HANA Database Installation(SMA) on the existing SAP HANA Instance. Which means multiple SAP Hana instances on one SAP HANA system
1681092 – Multiple SAP HANA DBMSs (SIDs) on one SAP HANA system
Here we will have to restrict the memory for SID. otherwise single SID could end up consuming whole memory.
II. SMJ – HANA Database installation
SMJ Database could be same as SMA installation as above
III. SMA – ASCS Installation
Install the ASCS on the CI host, by starting the sapinst with SAPINST_STACK_XML option here
IV. SMA – Database Instance Installation
2348162 – Changes to the Naming of the SAP HANA Client Download File
1988071 – “SQL error 1033” occurred during importing package phase of installation with HANA
Downloaded and updated the HDB client (rev 120)
2372790 – R3load error during SWPM export: “SQL file … did not occur in ‘SQLFiles.LST
V. SMA – Primary Application server Instance installation
Note: Here CI instance should be same as SMA – HDB instance number
Here if you would like to add this system to already existing SLD, we could provide the SLD server details
ERROR: JCO RFC error
The JVM reports an exception during execution of class ( com.sap.sdt.ins.component.nw_abap_start_sum.CheckIfThereIsSomethingToDeploy ) and function executeStepClass. DETAILS: The reported error message from JVM is: com.sap.conn.jco.JCoExc
eption: (102) JCO_ERROR_COMMUNICATION: Initialization of repository destination 10 failed: connection closed without message (CM_NO_DATA_RECEIVED)
Solution: Installed UUID deamon
VI. SMJ – SCS Instance Installation
VII. SMJ – Database Instance Installation
VIII. SMJ – Primary Application Server Instance
Steps VI,VII,VIII are the same as steps III, VI,V except few screens..
2. Calculate the latest (up-to-date) support stack files for update (for eg: SP05) using MP
Open the Maintenance Planner
https://apps.support.sap.com/sap(bD1lbiZjPTAwMQ==)/support/mp/index.html
For SMJ – Java System
Remaining steps are same as for SMA from here
Add all stack files to download basket and Download and copy files into respective server.
3. Update Solution Manager system to SP05 (SMA and SMJ)
Run the SP05 Update for both ABAP-SMA and Java _SMJ systems with respective stackxxx.xml files.
Nice and helpful blog !!
Thanks for the wonderful blog...
Very Informative 🙂
Dear Pratap,
Awesome! Thorough document with very clear step-wise which is very helpful. Keep posting the good work.
nice one pratap keep posting ...
Thanks for the detailed blog. Its really helpful.
Thanks for the blog!
I am actually installing a new solman system right now. Have you considered using the new sapinst (SWPM SP20)? We had some trouble with the new browser based interface, because it needs the root password. With the old one, a sudo was enough.
Hi Richard,
No, We have used SWPM19, since it is automatically calculated by the Maintenance Optimizer.
If you have had problem with SWPM20 with browser based, you could still use sapinst with SAPINST_SLP_MODE=false option (old method)
./sapinst SAPINST_STACK_XML=<Path_To_Stack_XML_File>; SAPINST_SLP_MODE=false
Regards
Pratap
Hi Pratap,
thank you very much! This parameter is currently very helpful for us and presumably the majority of SAP admins too.
I wonder how long the old java sdt method will be supported. With IAAS cloud offers getting more and more used in the SAP environment, I don’t think there can be a “hard cut” any time soon.
BR, Richard
Hi Pratap,
Firstly, Thanks for sharing your experience. This is a nice blog.
One question, To connect your managed systems to Maintainance Planner (for generation of stack files), is it mandatory to connect managed systems to newly installed solution manager system and perform "support hub connectivity" in system preparation step of solution manager?
Hi Sourav,
Yes, it is mandatory to perform the step " “support hub connectivity” in system preparation step of solution manager. Going forward this will be only communication channel to sync system details from solution manager to SAP support portal.
https://apps.support.sap.com/sap/support/knowledge/preview/en/2359837
""Future SAP Solution Manager Support Packages will include incremental built-in functionalities based on the above. Functions will be migrated
to the new SAP Support Communication Channels, which will completely replace the current SAP OSS RFC communication model.""
OK..
Many thanks for sharing the knowledge Pratap.
Best Regards,
Sourav Brahma
Thank yo so much for the post. Very helpful.
Cheers
Seshu.
Hi Pratap,
Thank you for this blog. I have a question regarding JAVA stack installation using stack file. I have created SOLMAN SP5 (JAVA) stack file but after starting SWPM SP20 using stack file I see SAP NW 7.4 option not SOLMAN 7.2 SR1 option. Is this obvious/fine? In later screens also it prompts for NW 7.4 SR2 Java media, it doesn’t accept JAVA Component media which I downloaded with SOLMAN 7.2. Has anyone faced this issue?
BR,
Mukul
Hi Mukul,
Yes correct, For Solman Java stack installation, we have to go with SAP NW 7.4 option, it would require SAP NW 7.4 SR2 Java Comp DVD. Please refer to below note
2437303 - Software provisioning manager initial menu option -Business suite or Solution manager 7.2 JAVA vs ABAP stack up-to-date installation with stack configuration file generated from Maintenance planner
Regards
Pratap
Thank you Pratap!
Few other observations from my side. Surprisingly MP calculates SWPM (70SWPM) when planning a system SOLMAN 7.2 SR1 JAVA System. I tried running with 70SWPM also but that also gave me SAP NW 7.4 option to install. your provided OSS Note clears everything. For others...
Snippet from 1680045 - Release Note for Software Provisioning Manager 1.0 (recommended: SWPM 1.0 SP20)
----
Up-to-date Installation using STACK_CONFIGURATION_FILE does not match options in welcome screen
Symptom:
You called
sapinst SAPINST_STACK_XML=<your stack.xml>
but there are no options in the product.catalog file according to the information on the UI.
Solution
-----
2277574 - Central Note for Up-To-Date Installation using Maintenance Planner, Software Provisioning Manager and succeeding update tools
Best Regards,
Mukul SHarma
This is a great post, how long did it take you to install Soman 7.2 ?
Hi Irit,
Please fyi, it would take 16hrs for complete installation and update.
For installation
ABAP stack - 4hrs
Java stack - 2hrs
For update to latest SP level
ABAP stack update - 8hrs
Java stack update - 2hrs
Regards
Pratap
Hi Prathap,
How did you do the sizing for HANA.. can you please share the details
Hi Pratap,
have you configured your Solution Manager 7.2 FPS 06?..
I can't save Synchronization connection to LMDB in Infrastructure Preparation. Is there any workaround or information about this?..
My Solution Manager running on Linux and DB2 10.5
Thanks in advanced
Yunianto
Hi Pradeep,
Can we install Both ABAP /JAVA stack on one host ( say Host1) and use one tenant HANA DB.
I mean like sybase DB.
Thanks
Amit
Hi Amit,
Yes, it is possible it seems.
Please refer this sap note 2550179 - Does SAP Solution Manager 7.2 supports HANA Tenant Database?
Regards
Pratap