Installation of SAP Solution Manager in Windows platform compatible with Amazon / Azure Cloud / Hyper-V / Standalone server

Transcription

1 sapbasisf o rbe ginne r.co m rbeginner.co m/2013/09/installatio n-o f-sap-so lutio n-manager-in.html Installation of SAP Solution Manager in Windows platform compatible with Amazon / Azure Cloud / Hyper-V / Standalone server T he SAP Solution Manager 7.1 installation steps below suitable on all Windows server environment including Amazon Web Services (AWS), Microsof t Azure, Microsof t Hyper-V or standalone server installation. T hese configurations including: A) Prerequisite B) Oracle Database Installation C) SAP Solution Manager 7.1 Installation with SWPM D) SAP GUI Installation and login the SAP Solution Manager f or the f irst time E) Others A) Prerequisite: 1) Windows server 2008 be ready 2) Minimum SAP Solution Manager 7.1 installation f iles Download Object T itle _6 NW 7.0 Presentation Compilation 2 Present. ½ ORACLE Client _1 6 ORACLE RDBMS Windows x _1-12 SAP SOLMAN 7.1 SR1 Inst. Export (2) _1 5 SAP SOLMAN 7.1 SR1 Java Comp _9 SL CONT ROLLER _6 720 UC Kernel f or SWPM SP03 - Windows Server on x64 64bit 70SWPM10SP02_ sar Sof tware Provisioning Manager 1.0 SP2 f or NW 7.0x 3) Recommended server specif ications: Type OS RAM Hard disk Descriptions Windows Server 2012 Data Center 12GB 400GB (c:\ 100GB d:\300gb) 4) Ref erence f or OS environment setup on AWS Cloud and Microsof t Hyper-V - AWS Cloud: Section: AWS AMI Setup and Conf igurations (SAP IDES Installation) - Microsof t Hyper-V: Section: A) Creating new VM in Hyper-V (setup Red Hat Enterprise Linux Server in

2 Microsof t Hyper-V Server 2012) 5) Assumption: - The Windows OS will be conf igure as workgroup instead of joining a domain / active directory. - All the installation are mostly with def ault settings and f urther conf igurations or f ine tune will be perf orm af ter the installation. - Windows OS been patched to latest update and some prerequisite steps as in SAP IDES Installation - T he installation time estimation was based on a installation on Microsof t Hyper-V 2012 environment with the above mentioned hardware. In f act, the actual installation time might vary. B) Oracle Database Installation 1) Run the Oracle setup batch f ile "sapserver,cmd" to begin the database installation 2) Enter the installation drive and SID 3) Installation splash screen

3 4) Click "Next" 5) Click "Next" ignore the warning

4 6) Select "Skip the sof tware updates"

5 7) Select " Install database sof tware only"

6 8) Select "single instance database installation"

7 9) Click "Next"

8 10) Select "Enterprise Edition"

9 11) Choose the installation drive

10 12) Wait f or the verif ication process

11 13) The verif ication process

12 14) Click "Install" to begin the installation

13 15) Click "Details" button to shown the installation progress

14 16) The additional installation progress screen

15 17) Wait until the installation complete and the click "Close" button

16 18) Conf irm the database been installed B) SAP Solution Manager 7.1 Installation with SWPM T he installation process estimate will take about ~5 hours to complete with the above mentioned hardware specif ications 1) Double click the "sapinst" extracted f rom SWPM - Section E) Others below shown how to extract the installation f ile with sapcar program

17 2) Select "SAP Solution Manager 7.1 Support Release 1"

18 3) Select "typical"

19 4) The installation splash screen 5) Select the SWPM kernel

20 6) Enter the SAPSID and installation drive

21 7) Conf igure the FQDN or it can be conf igure af ter the installation

22 8) Enter the master password

23 9) Enter the Oracle database ID created during the database installation

24 10) Select the installation export package

25 11) Select the other installation export package

26 12) Click "Next" with all the def ault settings

27 13) Select the Java component package

28 14) Ensure the installation drive are correct

29 15) Click "Next" to accept the def ault listener conf iguration or change the port according to existing f irewall policy

30 16) Select the kernel package

31 17) Select the Oracle client package

32 18) Select "Conf igure a local SLD" in this example

33 19) Enter the computer name in "Object Server Name"

34 20) Click the "Next" button

35 21) Click "Yes" button

36 22) Click "No SLD destination" in this example

37 23) Verif y the selected options and click "Next" to accept all the settings

38 24) The installation begin

39 25) Example of the installation process

40 26) Example of the installation process

41 27) Example of the installation process

42 28) Around ~5 hours f or the installation to complete

43 29) SAP management console and listener status command showing the SAP services are up and running

44 D) SAP GUI Installation and login the SAP Solution Manager for the first time 1) Perf orm the SAP GUI installation f rom the media kit: _6 2) The settings f or the SAP logon

45 3) Login with user: "sap*" 4) The inf ormation screen

46 5) T he relevant SAP system inf ormation 6) Login to the portal (http: port: 500, https: port: 501)

47 7) Main Menu of the portal 8) Use the def ault login: "j2ee_admin" and master password entered during installation

48 9) Sample of inf ormation screen 10) Again using the "j2ee_admin" f or access

49 11) Sample of inf ormation screen 12) That's all on the basic steps to perf orm a new SAP Solution Manager installation.

50 13) Please ref er to the common troubleshooting on SOLMAN_WORKCENTER post f or f urther conf igurations or common errors troubleshooting E) Others How to extract the SWPM installation file with SAPCAR 1) Download the "Sof tware Provisioning Manager 1.0 SP2 f or NW 7.0x" f rom SAP marketplace 2) Extract the sar f ile with SAPCAR -xvf 3) T he "sapinst" program use f or the SAP Solution Manager installation

51 How to clear SWPM cache or resolve the SAP Solution Manager 7.1 selection node was not available for installation Af ter running the "sapinst", the "SAP Solution Manager 7.1 Support Release 1" option was not available and it seem appearing with dif f erent option ex: SAP Solution Manager 7.1 f or HANA. This happen due to the other SWPM was executed bef ore and the f iles were cache and causing the other SWPM relevant selection node not updated. 1) Locate to "c:\users\administrator\appdata\local\temp\2", delete all the f iles and f olders contains in it 2) Re-run the correct SWPM "sapinst" and the correct node would appear

52