-
Notifications
You must be signed in to change notification settings - Fork 9
/
s4s_about.xml
372 lines (361 loc) · 12 KB
/
s4s_about.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
<?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-s4s-about">
<title>What Is &sles4sap;?</title>
<info>
<abstract>
<para>
&sles4sapreg; is a bundle of software and services that addresses the
specific needs of &sap; users. It is the only operating system that is
optimized for all &sap; software solutions.
</para>
</abstract>
</info>
<para>
Target use cases include:
</para>
<itemizedlist>
<listitem>
<para>
Unix to Linux migrations and replatforming
</para>
</listitem>
<listitem>
<para>
&sap; appliances
</para>
</listitem>
<listitem>
<para>
&sap; cloud deployments
</para>
</listitem>
</itemizedlist>
<para>
&sles4sap; consists of software components and service offerings which are
described in the following sections. The figure
<xref linkend="fig-s4s-offering" xrefstyle="select:title"/> shows an
overview of which software components and services
are also available with other products from &suse; (green)
and which are exclusively available with &sles4sap; (blue).
</para>
<figure xml:id="fig-s4s-offering">
<title>Offerings of &sles4sap;</title>
<mediaobject>
<imageobject role="fo">
<imagedata fileref="s4s_overview.svg" width="85%"/>
</imageobject>
<imageobject role="html">
<imagedata fileref="s4s_overview.png" width="85%"/>
</imageobject>
</mediaobject>
</figure>
<xi:include condition="quick" href="s4s_components_quick.xml" parse="xml"/>
<xi:include condition="noquick" href="s4s_components.xml" parse="xml"/>
<sect1 condition="noquick" xml:id="sec-s4s-repository">
<title>Software Repository Setup</title>
<para>
Software included with operating systems based on &sle; is delivered as
RPM packages, a form of installation package that can have dependencies on
other packages. On a server or an installation medium, these packages are
stored in software repositories (sometimes also called
<quote>channels</quote>).
</para>
<remark>
FIXME: "variant" is maybe not a good word... - sknorr, 2016-06-17
</remark>
<para>
By default, computers running &productname; are set up to receive
packages from multiple repositories. Of each of the standard repositories,
there is a <quote>Pool</quote> variant that represents the state of the
software when it was first shipped. There is also an <quote>Update</quote>
variant that includes the newest maintenance updates for the software
in the <quote>Pool</quote> variant.
</para>
<para>
If you registered your system during installation, your repository
setup should include the following:
</para>
<table xml:id="tab-s4s-repository">
<title>Standard Repositories</title>
<tgroup cols="3">
<colspec colname="type"/>
<colspec colname="base"/>
<colspec colname="update"/>
<thead>
<row>
<entry>
<para>Content</para>
</entry>
<entry>
<para>Base repository (<quote>Pool</quote>)</para>
</entry>
<entry>
<para>Update repository</para>
</entry>
</row>
</thead>
<tbody>
<row>
<entry>
<para>
Base packages of &sls;
</para>
</entry>
<entry>
<para><literal>SLE-Module-Basesystem&product-ga;-SP&product-sp;-Pool</literal></para>
</entry>
<entry>
<para><literal>SLE-Module-Basesystem&product-ga;-SP&product-sp;-Updates</literal></para>
</entry>
</row>
<row>
<entry>
<para>
Basic server functionality of &sls;
</para>
</entry>
<entry>
<para><literal>SLE-Module-Server-Applications&product-ga;-SP&product-sp;-Pool</literal></para>
</entry>
<entry>
<para><literal>SLE-Module-Server-Applications&product-ga;-SP&product-sp;-Updates</literal></para>
</entry>
</row>
<row>
<entry>
<para>
Packages specific to &sles4sap;
</para>
</entry>
<entry>
<para>
<literal>SLE-Module-SAP-Applications&product-ga;-SP&product-sp;-Pool</literal>
</para>
</entry>
<entry>
<para><literal>SLE-Module-SAP-Applications&product-ga;-SP&product-sp;-Updates</literal></para>
</entry>
</row>
<row>
<entry>
<para>
Packages specific to &sleha;
</para>
</entry>
<entry>
<para><literal>SLE-Product-HA&product-ga;-SP&product-sp;-Pool</literal></para>
</entry>
<entry>
<para><literal>SLE-Product-HA&product-ga;-SP&product-sp;-Updates</literal></para>
</entry>
</row>
</tbody>
</tgroup>
</table>
<para>
The tables in this section do not show <emphasis>Debuginfo</emphasis> and
<emphasis>Source</emphasis> repositories, which are also set up but
disabled by default. The <emphasis>Debuginfo</emphasis> repositories
contain packages that can be used for debugging regular packages. The
<emphasis>Source</emphasis> repositories contain source code for packages.
</para>
<para>
Depending on your installation method, you may also see
<literal>SLE-&product-ga;-SP&product-sp;-SAP-&product-ga;.&product-sp;-0</literal>
which is the installation medium.
It contains packages from all of the base software repositories listed
above.
</para>
<para>
Because there are own repositories for &productname;, &suse; can ship
packages and patches that are specific to &productname;.
</para>
<note>
<title>ESPOS Updates Shipped Directly in Update Repositories</title>
<para>
Unlike in &productname; 11, updates related to Extended Service Pack
Overlay Support (ESPOS) are shipped directly from the
<literal>Update</literal> repositories. This means there is no separate
ESPOS repository to set up.
</para>
</note>
<para>
In addition to the standard repositories, you can enable
&slea; Modules and &slea; Extensions either during the installation or from
the running system using &yast; or the command
<command>SUSEConnect</command>.
</para>
<para>
For information about all modules and extensions available for the &sle;
product line, see
<link xlink:href="https://documentation.suse.com/sles/15-SP1/html/SLES-all/art-modules.html"/>.
</para>
<para condition="noquick">
For more information about &ph;, see <xref linkend="sec-s4s-packagehub"/>.
For information about life cycle and support of modules and extensions, see
<xref linkend="sec-s4s-service"/>.
</para>
</sect1>
<sect1 xml:id="sec-s4s-service">
<title>Included Services</title>
<variablelist>
<varlistentry>
<term><emphasis>Extended Service Pack Overlap Support (ESPOS)</emphasis>
</term>
<listitem>
<para>
Subscriptions for &sles4sap; include Extended Service Pack Overlap Support
(ESPOS). It extends the overlap between the support periods of two
consecutive service packs by three years. During this period, you receive
support and all relevant maintenance updates under the terms of Long Term
Service Pack Support (LTSS).
</para>
<para>
Extended Service Pack Overlap Support allows you to perform service pack
migrations within three and a half years instead of only six months.
This enables you to schedule migrations more easily and perform testing
before a migration under less restrictive time constraints. At an
additional cost, SUSE also offers LTSS. With LTSS, you receive support
for a particular service pack after the ESPOS period ends. &sles4sap;
includes one and a half years of general support and three years of
ESPOS for each service pack.
</para>
<para>
The last service pack in each &slea; family does not have ESPOS. Instead
of ESPOS, it includes a longer general support period. Because of that,
LTSS is available only for the last service pack. All other service
packs already include three years of ESPOS, which equals LTSS.
</para>
<para>
For more information, refer to the following resources:
</para>
<itemizedlist>
<listitem>
<para>
Product Lifecycle Support Policies: <link xlink:href="https://www.suse.com/support/policy-products/#sap"></link>
</para>
</listitem>
<listitem>
<para>
Product Support Lifecycle Lifecycle Dates by Product: <link xlink:href="https://www.suse.com/lifecycle/"/>
</para>
</listitem>
<listitem>
<para>
Long Term Service Pack Support: <link xlink:href="https://www.suse.com/products/long-term-service-pack-support/"></link>
</para>
</listitem>
</itemizedlist>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis>&sls; Priority Support for &sap; Applications</emphasis>
</term>
<listitem>
<para>
Subscriptions for &sles4sap; include &sls;
Priority Support for &sap; Applications. It offers technical support for
&sles4sap; directly from &sap;. The joint support infrastructure is
provided by support engineers from &suse; Technical Support and &sap;. It is
based upon &sap; Resolve and offers seamless communication
with both &sap; and &suse;. This <quote>One Face to the Customer</quote>
support model reduces complexity and lowers the total cost of ownership.
</para>
<para>
For more information, see <citetitle>SAP Note 1056161: SUSE
Priority Support for SAP Applications</citetitle> (<link
xlink:href="&sapnoteaddress;1056161"/>).
</para>
</listitem>
</varlistentry>
</variablelist>
<important>
<title>Life Cycle and Support for Modules and Extensions</title>
<para>
Modules and extensions have a different life cycle than &s4sa; and &suse;
provides different support offerings for them:
</para>
<itemizedlist>
<listitem>
<para>
Modules:
</para>
<itemizedlist>
<listitem>
<formalpara>
<title>Life Cycle</title>
<para>
Varies depending on the module.
</para>
</formalpara>
</listitem>
<listitem>
<formalpara>
<title>Support</title>
<para>
Only up-to-date packages are supported. Support is included with
your subscription for &productname;. You do not need an additional
registration key.
</para>
</formalpara>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>
Extensions
</para>
<itemizedlist>
<listitem>
<formalpara>
<title>Life Cycle</title>
<para>
Releases are usually coordinated with &productname;.
</para>
</formalpara>
</listitem>
<listitem>
<formalpara>
<title>Support</title>
<para>
Support is available but not included with your subscription for
&productname;. You need an additional
registration key.
</para>
</formalpara>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>
Unsupported Extensions (&ph; and &sdk;)
</para>
<itemizedlist>
<listitem>
<formalpara>
<title>Life Cycle</title>
<para>
Releases are usually coordinated with &productname;.
</para>
</formalpara>
</listitem>
<listitem>
<formalpara>
<title>Support</title>
<para>
There is no support beyond fixes for security and packaging issues.
You do not need an additional registration key.
</para>
</formalpara>
</listitem>
</itemizedlist>
</listitem>
</itemizedlist>
</important>
</sect1>
</chapter>