2. Create your local repository directory to be used to serve the RPMs

mkdir -p /var/www/repos

3. Extract the Directory Structure/RPMs from the BOTH the Ambari and the IOP tarballs to the local repository directory
NOTE: Your filenames will be different depending on which tarballs you downloaded in Step 1.

Example:
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot â€ś/var/www/â€ť
#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the â€śdefaultâ€ť to be a very restrictive set of
# features.
#
Options FollowSymLinks
AllowOverride None
#
# Note that from this point forward you must specifically allow
# particular features to be enabled â€“ so if somethingâ€™s not working as
# you might expect, make sure that you have specifically enabled it
# below.
#
# This should be changed to whatever you set DocumentRoot to.
#
Directory â€ś/var/www/â€ť

Save the configuration file and exit.

7. Start Apache

service httpd start

8. In a browser, navigate to the web server URL to verify that the RPMs are available.

12. Install IBM Open Platform as directed per the Knowledge CenterNOTE: START on Step (5) …but STOP when you reach Step (14) in the following link, and continue with this guideIBM Knowledge Center : Ambari Installation

13. In the Launch Wizard, the page after naming your cluster, click on the Advanced Repository Options and modify the â€śIOP-4.1â€ł URL to the newly created Apache repository

http://[hostname]/repos/IOP/RHEL6/x86_64/4.1-Spark-1.5.1

14. Proceed with the rest of the installation as normal with Step 15 in the Knowledge Center Guide. Ambari should now pick up the IOP stack w/Spark 1.5.1 from the local repository we just created.