Skip to main content

I have been struggling to perform a fresh install of IFSAPP10 following the documentation here: Installing Fresh System

IFS sent my team a vanilla deliverable.  When unzipped, the folder structure matches what is documented here: Folder Structure for Builds

 

Following the Preparing IFS Applications section leads me to IFS Configuration Builder which is where I am getting stuck.  I understand that preparing the IFS application involves compiling source and preparing the database scripts for the installer.  The problem I am running into is that per the Configuring IFS Configuration Builder section, this requires a Customer Configuration File and a Release Repository Catalog neither of which I have nor will I have which means I cannot configure the IFS Configuration Builder.  I also found additional pages on How to Build Manually and Page: Create Build Structure And Compile, but neither provided much insight as to how to build manually with the directory structure I screenshotted above.  The vanilla delivery provided by IFS also does not have a directory structure that matches the one documented in Workspace Folder Structure.

I also attempted to follow the instructions in the How to Compile Source Code section, but when I execute build\build.cmd on a Windows based machine, the build fails because it cannot find a source folder or additional build scripts (such as _msbuild.cmd) which I assume are generated by the IFS Configuration Builder.

IFS Support directed me to Preparing Delivery but this is specific to patches/existing installs and is not applicable to a fresh install.

I have attempted to search for existing articles or community topics about how to perform the fresh install of IFSAPP10 manually but have not had any success so I’m at a loss as to how to proceed.  Is there a step by step guide on how to do this somewhere that I missed?  Does the vanilla delivery that IFS provided not have to undergo the build preparation step and can just be executed through the installer?

Any direction would be greatly appreciated.

Following up: the deliverable that I was trying to install was an incomplete deliverable where the source was not pre-built.  I have since received an official deliverable with the source pre-built so this question is now OBE.


Reply