/
s4s_installation_sap.xml
1174 lines (1115 loc) · 36.5 KB
/
s4s_installation_sap.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE chapter
[
<!ENTITY % entities SYSTEM "generic-entities.ent">
%entities;
]>
<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="cha-install-sap">
<title>Installing &sap; applications</title>
<para>
This section guides you through the installation of &sap; media sets you
received from &sap;.
</para>
<itemizedlist condition="noquick">
<listitem>
<para>
If you are installing an &sap; application within the installation workflow,
continue with <xref linkend="sec-install-sap-welcome"/>.
</para>
</listitem>
<listitem>
<para>
If you are installing an &sap; application within an installed system,
continue with <xref linkend="sec-install-sap-product"/>.
</para>
</listitem>
</itemizedlist>
<sect1 condition="noquick" xml:id="sec-install-sap-list">
<title>Products that can be installed using &sapwiz;</title>
<para>
Using the &sapwiz;, you can install stand-alone &hana; database instances.
Additionally, the following &sap; products (along with a database) can be
installed using the &sapwiz;:
</para>
<xi:include href="s4s_installation_product.xml" parse="xml"/>
<important>
<title>Installation of Oracle databases not possible</title>
<para>
The &sapwiz; does not allow installing products together with Oracle
databases. To install an Oracle database, install the base product &sls;
first, then install the Oracle database and later convert your
installation to &s4sa;. This is necessary because the Oracle databases
installer queries for the existence of certain files, not all of which are
included in a &s4sa; installation.
</para>
<para condition="noquick">
For more information about converting, see
<xref linkend="sec-convert-sles"/>.
</para>
</important>
</sect1>
<sect1 xml:id="sec-install-sap-welcome">
<title>First steps</title>
<para>
These first steps are only relevant during the installation workflow.
</para>
<procedure>
<step>
<para>
When the system is booted, it displays the screen
<guimenu>Welcome</guimenu>.
Proceed with <guimenu>Next</guimenu>.
</para>
</step>
<step>
<para>
The screen <guimenu>Network Settings</guimenu> will now open.
This gives you an opportunity to change the network settings.
</para>
<para>
When you are finished configuring networking, proceed with
<guimenu>Next</guimenu>.
</para>
<important>
<title>Configure networking as recommended by &sap;</title>
<para>
Make sure to configure the network connection according to the
documentation of your &sap; application.
</para>
</important>
<para>
For information about configuring networking, see
<citetitle>
&admin;, Chapter <quote>Basic Networking</quote>,
Section <quote>Configuring a Network Connection with YaST</quote>
</citetitle> (&docaddress;).
</para>
<para>
(While the next screen loads, the <guimenu>Welcome</guimenu>
screen may appear again for a few seconds.)
</para>
<remark>
It does appear for around 8s for me which makes you wonder a bit as a
user. - sknorr, 2016-01-25
</remark>
</step>
<step>
<para>
Choose one of the following options:
</para>
<variablelist>
<varlistentry>
<term>
<guimenu>Create SAP file systems and start SAP product
installation</guimenu>
</term>
<listitem>
<para>
Allows installing an &sap; application and setting up the system as a
server providing &sap; installation routines to other systems.
</para>
<para>
Continue with <xref linkend="sec-install-sap-product"/>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<guimenu>Only create SAP HANA file systems, do not install SAP products
now</guimenu>
</term>
<listitem>
<para>
Create an &hana; file system on &b1;-certified hardware.
</para>
<!--
Next steps: click Next, click OK, click OK, click Finish.
- sknorr, 2016-02-25
-->
<remark>
Create a procedure for HANA fs creation? It just does stuff and you
can't do much anyway. - sknorr, 2016-01-28
</remark>
<important>
<title>Hardware requirements</title>
<para>
Make sure your machine fulfills the hardware requirements for &hana;
detailed in <xref linkend="sec-hardware"/>.
Otherwise, this option will not create a new file system and the
installation workflow ends at this point.
</para>
</important>
</listitem>
</varlistentry>
<varlistentry>
<term>
<guimenu>Finish wizard and proceed to OS login</guimenu>
</term>
<listitem>
<para>
Do not install an &sap; application and continue to the login screen of
&sles4sap;.
</para>
<!--
Next steps: click Next, click Finish. - sknorr, 2016-02-25
-->
</listitem>
</varlistentry>
</variablelist>
<para>
Proceed with <guimenu>Next</guimenu>.
</para>
</step>
</procedure>
</sect1>
<sect1 xml:id="sec-install-sap-product">
<title>Using the &sapwiz;</title>
<para>
Use the &sapwiz; to install an &netweaver; system (including database) or an
&hana; system.
</para>
<para>
To install other &sap; applications or to create a more advanced &hana;
setup, directly use one of the installation methods provided by &sap; instead
of this wizard.
</para>
<tip>
<title>Installing an &sap; application in a fully installed system</title>
<para>
This process is documented as it appears during the installation workflow.
However, it also applies to the &yast; module <guimenu>&sapwiz;</guimenu>
which is available in the installed system.
</para>
<para>
To start the &sapin;, from the desktop, choose
<menuchoice><guimenu>Applications</guimenu><guimenu>System</guimenu>
<guimenu>YaST</guimenu></menuchoice>, continue in the &yast; control center
by choosing
<menuchoice><guimenu>Miscellaneous</guimenu>
<guimenu>SAP Installation Wizard</guimenu></menuchoice>.
</para>
</tip>
<tip>
<title>&sapwiz; configuration</title>
<remark>
Terminology: "SAP Installer"/"SAPinst" and "SAP Installation Wizard" are
pretty close. Maybe SUSE should change the wizard's name some time in the
future..? - sknorr, 2016-01-15
</remark>
<para>
The &sapwiz; configuration is specified and
documented in
<filename>/etc/sysconfig/sap-installation-wizard</filename>. You can
change it according to your needs.
</para>
</tip>
<procedure>
<step xml:id="st-copy-master">
<para>
In the screen <guimenu>SAP Installation Wizard</guimenu>, provide the
<guimenu>Location of the SAP Installation Master</guimenu>
(<xref linkend="fig-sap-wizard-source"/>). The
location can either be a local, removable, or remote installation source.
</para>
<figure xml:id="fig-sap-wizard-source">
<title>Location of &sap; installation master</title>
<mediaobject>
<imageobject role="fo">
<imagedata fileref="s4s_sap_wizard_source.png" width="73%"/>
</imageobject>
<imageobject role="html">
<imagedata fileref="s4s_sap_wizard_source.png" width="73%"/>
</imageobject>
</mediaobject>
</figure>
<para>
Select the appropriate option from the drop-down box.
In the text box, specify the path to your source according to the format
given in the following table.
</para>
<table xml:id="tab-sap-media-source">
<title>Media source path</title>
<tgroup cols="3">
<colspec colnum="1" colname="option" colwidth="15*"/>
<colspec colnum="2" colname="desc" colwidth="30*"/>
<colspec colnum="3" colname="format" colwidth="55*"/>
<thead>
<row>
<entry>
<para>
Option
</para>
</entry>
<entry>
<para>
Description
</para>
</entry>
<entry>
<para>
Format of Path
</para>
</entry>
</row>
</thead>
<tbody>
<row>
<entry namest="option" nameend="format">
<emphasis role="strong">Local Sources</emphasis>
</entry>
</row>
<row>
<entry>
<para>
<guimenu>dir://</guimenu>
</para>
</entry>
<entry>
<para>
a local directory
</para>
</entry>
<entry>
<para>
<filename><replaceable>/path/to/dir/</replaceable></filename>
</para>
</entry>
</row>
<row>
<entry namest="option" nameend="format">
<emphasis role="strong">Removable Sources</emphasis>
</entry>
</row>
<row>
<entry>
<para>
<guimenu>device://</guimenu>
</para>
</entry>
<entry>
<para>
a locally connected hard disk
</para>
</entry>
<entry>
<para>
<filename><replaceable>devicename</replaceable><replaceable>/path/to/dir/on/device</replaceable></filename>
</para>
</entry>
</row>
<row>
<entry>
<para>
<guimenu>usb://</guimenu>
</para>
</entry>
<entry>
<para>
a USB mass storage device
</para>
</entry>
<entry>
<para>
<filename><replaceable>/path/to/dir/on/USB</replaceable></filename>
</para>
</entry>
</row>
<row>
<entry>
<para>
<guimenu>cdrom://</guimenu>
</para>
</entry>
<entry>
<para>
a CD or DVD
</para>
</entry>
<entry>
<para>
<filename><replaceable>//</replaceable></filename>
</para>
<!--
This is correct: the relevant files are usually at the top
level which is //. - sknorr, 2016-01-20
-->
</entry>
</row>
<row>
<entry namest="option" nameend="format">
<emphasis role="strong">Remote Sources</emphasis>
</entry>
</row>
<row>
<entry>
<para>
<guimenu>nfs://</guimenu>
</para>
</entry>
<entry>
<para>
an NFS share
</para>
</entry>
<entry>
<para>
<filename><replaceable>server_name</replaceable><replaceable>/path/to/dir/on/device</replaceable></filename>
</para>
<!--
This is correct: YaST does not need a colon after the server_name.
- sknorr, 2016-02-12
-->
</entry>
</row>
<row>
<entry>
<para>
<guimenu>smb://</guimenu>
</para>
</entry>
<entry>
<para>
an SMB share
</para>
</entry>
<entry>
<para>
<filename>[<replaceable>user_name</replaceable>:<replaceable>password</replaceable>@]<replaceable>server_name</replaceable>/<replaceable>/path/to/dir/on/server</replaceable>[?workgroup=<replaceable>workgroup_name</replaceable>]</filename>
</para>
</entry>
</row>
</tbody>
</tgroup>
</table>
<tip condition="noquick">
<title>Remote location specification</title>
<para>
To install from an NFS source, specify the name of
the server and the complete path to the media data. For
information about setting up a remote installation server, see
<xref linkend="cha-serve-mediaset"/>.
</para>
</tip>
<para>
If you have installed an &sap; application from an installation server
before or set up your
system to be an installation server, you can also directly choose
that server as the provider of the &instmaster;.
To do so, use the drop-down box below <guimenu>Choose an installation
master</guimenu>.
</para>
</step>
<step>
<para>
Under <guimenu>Advanced Options</guimenu>, choose from the following
options:
</para>
<variablelist>
<varlistentry>
<term>
<guimenu>Collect installation profiles for SAP products but do not execute
installation</guimenu>
</term>
<listitem>
<para>
Use this option to set the installation parameters,
but not perform the actual installation. With this option, the
&sapin; (&sapina;) will stop without performing the actual &sap;
product installation. However, the steps that follow fully apply.
</para>
<para condition="noquick">
For more information, see <xref linkend="sec-install-continue"/>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<guimenu>Serve all installation media (including master) to local
network via NFS</guimenu>
</term>
<listitem>
<para>
Set up this system as an installation server for other &sles4sap;
systems.
The media copied to this installation server will be offered through
NFS and can be discovered via Service Location Protocol (SLP).
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
Proceed with <guimenu>Next</guimenu>.
</para>
<para>
The &sapwiz; will now copy the &instmaster; to your local disk.
Depending on the type of &instmaster; you selected, the installation
will continue differently:
</para>
<itemizedlist>
<listitem>
<para>
If you are installing an &hana; database, skip ahead to
<xref linkend="st-supplement" xrefstyle="select:label"/>.
</para>
</listitem>
<listitem>
<para>
If you are installing an &netweaver; application, continue with the
next step.
</para>
</listitem>
</itemizedlist>
</step>
<step xml:id="st-copy-media">
<para>
On the screen <guimenu>SAP Installation Wizard</guimenu>, provide
the location of additional &instmedia; you want to install.
This can include an &sap; kernel, a database, and
database exports.
</para>
<variablelist>
<varlistentry>
<term><guimenu>Copy a medium</guimenu></term>
<listitem>
<para>
Specify a path to additional &instmedia;. For more information about
specifying the path, see <xref linkend="tab-sap-media-source"/>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><guimenu>Skip copying of medium</guimenu></term>
<listitem>
<para>
Do not copy additional &instmedia;. Choose this option
if you do not need additional &instmedia; or to install
additional &instmedia; directly from their source, for example
CDs/DVDs or flash disks.
</para>
<para>
When choosing this option despite your &sap; product requiring additional
&instmedia;, you will later need to provide the &sapin; (&sapina;)
with the relevant paths.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
Proceed with <guimenu>Next</guimenu>.
</para>
<para>
If you chose to copy &instmedia;, the &sapwiz; will copy the relevant
files to your local hard disk.
</para>
<figure xml:id="fig-sap-wizard-sapmedia">
<title>&sapwiz;: additional &instmedia;</title>
<mediaobject>
<imageobject role="fo">
<imagedata fileref="s4s_sap_wizard_location_sapmedia.png" width="73%"/>
</imageobject>
<imageobject role="html">
<imagedata fileref="s4s_sap_wizard_location_sapmedia.png" width="73%"/>
</imageobject>
</mediaobject>
</figure>
</step>
<step>
<para>
After copying the &instmedia;, you will be asked whether you want to
prepare additional &instmedia;.
To do so, click <guimenu>Yes</guimenu>.
Then follow the instructions in
<xref linkend="st-copy-media" xrefstyle="select:label"/>.
</para>
<para>
Otherwise, click <guimenu>No</guimenu>.
</para>
</step>
<step>
<para>
In the screen <guimenu>What Would You Like to Install</guimenu>,
under <guimenu>The SAP product is</guimenu>, choose how you want to
install the product:
</para>
<variablelist>
<varlistentry>
<term><guimenu>SAP standard system</guimenu></term>
<listitem>
<para>
Install an &sap; application including its database.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><guimenu>SAP standalone engines</guimenu></term>
<listitem>
<para>
Engines that add functionality to a standard product: &sap; TREX,
&sap; Gateway, and Web Dispatcher.
</para>
<!--
"Engines" in plural: A bit of an inconsistency. Still just one at a
time. - sknorr, 2016-01-15
-->
</listitem>
</varlistentry>
<varlistentry>
<term><guimenu>Distributed system</guimenu></term>
<listitem>
<para>
An &sap; application that is separated onto multiple servers.
</para>
<!--
Inconsistent terminology: Why is this not called
"SAP Distributed System"? - sknorr, 2016-01-15
-->
</listitem>
</varlistentry>
<varlistentry>
<term><guimenu>SAP high-availability system</guimenu></term>
<listitem>
<para>
Installation of &netweaver; in a high-availability setup.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><guimenu>System rename</guimenu></term>
<listitem>
<para>
Allows changing the various system properties such as the &sap; system
ID, database ID, instance number, or host name. This can be used to
install the same product in a very similar configuration on different
systems.
</para>
<!--
Normally, this option would not make sense within the first-boot
wizard. But on preconfigured systems, it can be useful.
- sknorr, 2016-01-20
-->
</listitem>
</varlistentry>
</variablelist>
<figure xml:id="fig-sap-wizard-mode-db">
<title>&sapwiz;: installation type and database</title>
<mediaobject>
<imageobject role="fo">
<imagedata fileref="s4s_sap_wizard_mode_db.png" width="73%"/>
</imageobject>
<imageobject role="html">
<imagedata fileref="s4s_sap_wizard_mode_db.png" width="73%"/>
</imageobject>
</mediaobject>
</figure>
</step>
<step>
<para>
If you selected <guimenu>SAP Standard System</guimenu>,
<guimenu>Distributed System</guimenu>, or
<guimenu>SAP High-Availability System</guimenu>,
additionally choose a back-end database under
<guimenu>Back-end Databases</guimenu>.
</para>
<para>
Proceed with <guimenu>Next</guimenu>.
</para>
</step>
<step>
<para>
You will now see the screen <guimenu>Choose a Product</guimenu>.
The products shown depend on the &mediaset; and &instmaster; you received
from &sap;.
From the list, select the product you want to install.
</para>
<para>
Proceed with <guimenu>Next</guimenu>.
</para>
<figure xml:id="fig-sap-wizard-avail-products">
<title>&sapwiz;: choose a product</title>
<mediaobject>
<imageobject role="fo">
<imagedata fileref="s4s_sap_wizard_available_products.png" width="73%"/>
</imageobject>
<imageobject role="html">
<imagedata fileref="s4s_sap_wizard_available_products.png" width="73%"/>
</imageobject>
</mediaobject>
</figure>
</step>
<step xml:id="st-supplement">
<para>
You will be asked whether to copy &supmedia; or
&thirdmedia;.
To do so, click <guimenu>Yes</guimenu> and then follow the instructions in
<xref linkend="st-copy-media" xrefstyle="select:label"/>.
</para>
<para>
Otherwise, click <guimenu>No</guimenu>.
</para>
<note>
<title>Difference between &supmedia;/&thirdmedia; and additional software repositories</title>
<para>
Both types of delivery mechanisms allow installing software
that is neither part of the &sles4sap; media nor part of your &mediaset;
from &sap;. However, the delivery mechanism is different:
</para>
<itemizedlist>
<listitem>
<para>
&supmedia;/&thirdmedia; is installed using an &ay; file which allows
creating an installation wizard and custom installation scripts.
</para>
</listitem>
<listitem>
<para>
Additional software repositories are RPM package repositories that you will
remain subscribed to. This means you receive updates for &thirdmedia;
along with your regular system updates.
</para>
</listitem>
</itemizedlist>
</note>
<para condition="noquick">
For information on creating &supmedia;, see
<xref linkend="app-component-supplement"/>.
</para>
</step>
<step>
<para>
On the screen <guimenu>Additional software repositories for your
SAP installation</guimenu>, you can add further software repositories.
For example, for add-ons that are packaged
as RPM. To do so, click <guimenu>Add new software repositories</guimenu>.
For more information about adding repositories, see
<citetitle>&deploy;,
Chapter <quote>Installing and Removing Software</quote>,
Section <quote>Adding Software Repositories</quote></citetitle>
(&docaddress;).
</para>
<para>
Proceed with <guimenu>Next</guimenu>.
</para>
<note>
<title>Location of copied &sap; media</title>
<para>
At this point, all data required for the &sap; installation has been
copied to <filename>/data/SAP_CDs</filename> (unless you chose to skip
the process of copying).
Each Installation Medium is copied to a separate directory. You might find
the following directory structure, for example:
</para>
<screen>&prompt.user;ls /data/SAP_CDs
742-KERNEL-SAP-Kernel-742
742-UKERNEL-SAP-Unicode-Kernel-742
RDBMS-MAX-DB-LINUX_X86_64
SAP-NetWeaver-740-SR2-Installation-Export-CD-1-3
SAP-NetWeaver-740-SR2-Installation-Export-CD-2-3
SAP-NetWeaver-740-SR2-Installation-Export-CD-3-3</screen>
<para>
<filename>/data/SAP_CDs</filename> is the default directory as specified
in the <filename>/etc/sysconfig/sap-installation-wizard</filename>
configuration file.
</para>
</note>
</step>
<step xml:id="st-collect-parameter">
<para>
Depending on the product you are installing, one or more dialogs will
prompt you to supply values for several configuration parameters for the
&sap; application you are installing.
</para>
<para>
Supply the values as described in the documentation provided to you by
&sap;. Help for the configuration parameters is also
available on the left side of the dialog. For more information, see
<xref linkend="sec-data"/>.
</para>
<para>
Fill out the form (or forms), then proceed with <guimenu>OK</guimenu>.
</para>
<figure xml:id="fig-product-parameter">
<title>Product parameters</title>
<mediaobject>
<imageobject role="html">
<imagedata fileref="s4s_sap_wizard_product_param.png"/>
</imageobject>
<imageobject role="fo">
<imagedata fileref="s4s_sap_wizard_product_param.png" width="73%"/>
</imageobject>
<textobject role="description">
<phrase>Dialog to configure product parameters</phrase>
</textobject>
</mediaobject>
</figure>
<para>
When you are done, the &sapwiz; will download additional software packages.
</para>
</step>
<step>
<!-- FIXME: This step hana-only? - sknorr, 2017-09-01 -->
<para>
You will be asked whether to continue the installation or prepare another
&sap; product for installation. If you choose to prepare another &sap;
product, start from the beginning of this procedure.
</para>
</step>
<step performance="optional">
<para>
When installing &hana; on a system that is not certified for &hana; and
does not meet the minimum hardware requirements for &hana; TDI
(Tailored Datacenter Integration), you will be
asked whether to continue. If you receive this message unexpectedly,
check <xref linkend="sec-hardware"/> and the sizing guidelines from
&sap; at <link xlink:href="https://service.sap.com/sizing"/>
(you need your SAP ID to access the information).
</para>
<para>
Otherwise, continue with <guimenu>Yes</guimenu>.
</para>
</step>
<step xml:id="st-sapinst">
<para>
The following steps differ depending on the type of
&sap; application you are installing:
</para>
<itemizedlist>
<listitem>
<para>
When installing an &hana; database, &hana; will now be installed
without further question.
</para>
</listitem>
<listitem>
<para>
When installing an &netweaver; application, the actual installation will
be performed using the &sapin; (&sapina;). After a few seconds, &sapin;
will open automatically.
</para>
<para>
Follow the &sapin; as described in the documentation provided
by &sap;. Most configuration parameters are correctly filled already.
</para>
</listitem>
</itemizedlist>
<figure xml:id="fig-sapinst-param">
<title>&sapin;: defining parameters</title>
<mediaobject>
<imageobject role="fo">
<imagedata fileref="s4s_sapinst_param.png" width="73%"/>
</imageobject>
<imageobject role="html">
<imagedata fileref="s4s_sapinst_param.png" width="73%"/>
</imageobject>
</mediaobject>
</figure>
<tip>
<title>Installation log files</title>
<para>
If the installation of the &sap; application fails, refer to the
installation log files. They are located in
<filename>/var/adm/autoinstall</filename>. Failed installations are
recorded in files with names ending in <filename>.err</filename>.
</para>
<para condition="noquick">
For more information about log files, see
<xref linkend="cha-trouble"/>.
</para>
</tip>
</step>
<step>
<para>
The final screen is <guimenu>Installation Completed</guimenu>.
</para>
<para>
To create an &ay; file for this installation, activate
<guimenu>Clone This System for AutoYaST</guimenu>.
The &ay; file will be placed in <filename>/root/autoinst.xml</filename>.
</para>
<para>
Click <guimenu>Finish</guimenu>.
</para>
</step>
</procedure>
</sect1>
<sect1 condition="noquick" xml:id="sec-install-continue">
<title>Continuing an installation using an installation profile</title>
<para>
If you chose <guimenu>Collect installation profiles but do not execute
installation</guimenu> during the previous run of the &sapwiz;, this section
will show you how to continue the installation of the selected
&sap; applications.
</para>
<para>
When collecting an installation profile, the &sapwiz; copies
product images to <filename>/data/SAP_CDs</filename>.
It also prepares an installation environment for every product under the
path <filename>/data/SAP_INST</filename>:
</para>
<screen>/data/SAP_INST/0/Instmaster
/data/SAP_INST/1/Instmaster
/data/SAP_INST/2/Instmaster
[...]</screen>
<para>
These files are re-used in the following.
To continue the installation, follow these steps:
</para>
<procedure>
<step>
<para>
In <filename>/etc/sysconfig/sap-installation-wizard</filename>,
set the following:
</para>
<screen>SAP_AUTO_INSTALL="yes"</screen>
</step>
<step>
<para>
In the case of an &hana;/&b1; installation, the &sapwiz; will later use
the parameters documented in the &ay; files in
<filename>/data/SAP_INST/<replaceable>number</replaceable></filename>.
</para>
<para>
If you need to change any parameters, make sure to adapt the &ay; files at
this point.
</para>
</step>
<step>
<para>
Open the &yast; control center and start
<guimenu>SAP Installation Wizard</guimenu>.
</para>
</step>
<step>
<remark>
This question appears whether SAP_AUTO_INSTALL is yes or not. However,
if not, all questions will be asked again. There seems to be partial state
at least, in that the installer remembers what is already copied. Bug or
working as intended?
- sknorr, 2016-02-03
</remark>
<para>
You will be asked whether to continue the pending installation.
Select <guimenu>Install</guimenu>.
</para>
</step>
<step>
<para>
All further interactions happen within the &sapin;.
Follow the steps of &sapin; as described in the documentation provided to
you by &sap;.
</para>
<itemizedlist>
<listitem>
<para>
In the case of an &netweaver; installation, all parameters of the &sapin;
will be offered again for fine-tuning.
</para>
</listitem>
<listitem>
<para>
In the case of an &hana;/&b1; installation, the installer will not be
offer to make any changes to parameters.
</para>
</listitem>
</itemizedlist>
</step>
</procedure>
</sect1>
<sect1 condition="noquick" xml:id="sec-partition-command">
<title>Partitioning for an &sap; application without the &sapwiz;</title>
<para>
If you do not want to use the &sapwiz;, you can also create the partitioning
for &sap; applications directly from the command line. First, find the
correct partitioning file in the directory
<filename>/usr/share/YaST2/include/sap-installation-wizard/</filename> or
create your own partitioning file. For more information, see
<xref linkend="sec-partition-sap"/>.
</para>
<para>
When you have determined the correct partitioning XML file, run:
</para>
<screen>&prompt.root;<command>yast2 sap_create_storage_ng <replaceable>ABSOLUTE_PATH_TO_PARTITIONING_FILE</replaceable></command></screen>
</sect1>
<sect1 condition="noquick" xml:id="sec-install-sap-autoyast">
<title>Automated installation of &sap; applications with &ay;</title>
<para>
The &sapwiz; can be used from &ay; to automate the installation of &sap;
Applications.
</para>
<sect2 xml:id="sec-install-sap-autoyast-hana">
<title>&hana; installation</title>
<para>
The following &ay; snippet shows how an &hana; or &trex; installation can
be automated:
</para>
<screen language="xml"><![CDATA[
<sap-inst>
<products config:type="list">
<product>
<media config:type="list">
<medium>
<url>nfs://server/path1</url>
<type>sap</type>
</medium>
<medium>
<url>nfs://server/path3</url>
<type>supplement</type>
</medium>
</media>
<sapMasterPW>]]><replaceable>PASSWORD</replaceable><![CDATA[</sapMasterPW>
<sid>]]><replaceable>SID</replaceable><![CDATA[</sid>
<sapInstNr>]]><replaceable>INSTANCE_NUMBER</replaceable><![CDATA[</sapInstNr>
<sapMDC>no</sapMDC>
</product>
</products>
</sap-inst>
]]></screen>
<itemizedlist>
<listitem>
<para>
The <tag>sapMDC</tag> element is only applicable to &hana;.
</para>
</listitem>
<listitem>
<para>
The <tag>sapVirtHostname</tag> element must be specified for
distributed or highly available installations.