s4s_install_network.xml

<?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-serve-mediaset">
 <title>Setting Up an Installation Server for &sap; Media Sets</title>

 <para>
  Using the &sapwiz;, it is possible to copy the &sap; media sets from a
  remote server (for example, via NFS or SMB).
  However, using the option provided there means that you need to install
  the product at the same time.
  Additionally, it does not allow for copying all &sap; media used in your
  organization to a single server.
 </para>
 <para>
  However, you can easily create such a server on your own.
  For example, to put the &sap; media sets on an NFS
  Server, proceed as follows:
 </para>

 <procedure xml:id="pro-s4s-nfs-server">
  <title>Adding &sap; Product Installation Files to an NFS Server</title>
  <step>
   <para>
    On your installation server, create the directory
    <filename>/srv/www/htdocs/sap_repo</filename>.
   </para>
  </step>
  <step>
   <para>
    Open the file <filename>/etc/exports</filename> and add the following:
   </para>
<screen>/srv/www/htdocs/sap_repo *(ro,no_root_squash,sync,no_subtree_check,insecure)</screen>
   <important>
    <title>Executable Rights Must Be Visible</title>
    <para>
     Clients must be able to see which files are executable. Otherwise,
     &suse;'s &sapwiz; cannot execute the &sapin;.
    </para>
   </important>
  </step>
  <step>
   <para>
    In <filename>/srv/www/htdocs/sap_repo</filename>, create a directory for
    every &sap; medium you have. Give these directories speaking names, so you
    can identify them later on. For example, you could use names like
    <filename>kernel</filename>, <filename>java</filename>, or
    <filename>hana</filename>.
   </para>
  </step>
  <step>
   <para>
    Copy the contents of each &sap; medium to the corresponding directory
    with <command>cp -a</command>.
   </para>
   <important>
    <title>Avoid Using Windows&ast; Operating Systems for Copying</title>
    <para>
     Using Windows operating system for copying or copying from/to Windows
     file systems like NTFS can break permission settings and capitalization
     of files and directories.
    </para>
   </important>
  </step>
 </procedure>

 <para>
  You can now install from the NFS server you set up.
  In the &sapwiz;, specify the path this way:
  <filename><replaceable>server_name</replaceable>/srv/www/htdocs/sap_repo</filename>.
  For more information about specifying the path, see
  <xref linkend="tab-sap-media-source"/>.
 </para>

 <para>
  For information about setting up an NFS server from scratch, see
  <citetitle>
   &admin;,
   Part <quote>Services</quote>,
   Chapter <quote>Sharing File Systems with NFS</quote>,
   Section <quote>Installing NFS Server</quote>
  </citetitle> (&docaddress;).
 </para>

 <para>
  For information about installing &sls; from an NFS server, see
  <citetitle>&deploy;, Chapter <quote>Remote Installation</quote>,
  Section <quote>Setting Up an NFS Repository Manually</quote>
  </citetitle> (&docaddress;).
 </para>
</chapter>