Solution Manager 7.2 SP05 (Up-to-date) installation and Configuration on SAP HANA Database (MCOS) on Distributed environment

[prathapnaidu09]

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:

1. Download all the Solution Manager 7.2 software's from Service Market Place and Install the Solution Manager 7.2 system


2. Calculate the latest (up-to-date) support stack files for update (for eg: SP05) using Maintenance Planner (MP)


3. 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.