Preparing Delivery

The way to deliver patches and corrections as well as customizations is through deliveries. The easiest way to prepare a delivery for later installation is to use the tool IFS Solution Developer (ISD) since it will automate a number of steps for you. This is the recommended approach.

An IFS Applications delivery prepared with ISD is always based on a delivery defined in Life Cycle Support (LCS) as a Customization Project. Please refer to the Application Quality Standard (AQS) for more details on how to prepare a delivery using ISD.

For situations when ISD is not available, the manual way of preparing a delivery is described in the sections below.

Prerequisites and Settings

Make sure to read the patch and install notes before you start. In some cases there are additional steps necessary before and/or after the installation or upgrade. So get in the habit to always check the patch notes before you start.

The files included in the patch should be on hand.

You need to have full access to the <build_home> and <ifs_home> folders.

You need to know the passwords for some of the IFS system users:

Manually Preparing a Delivery

Preparing a delivery is essentially about three things:

  1. assemble files and place them in the correct structure
  2. create install.tem (only valid if database files are included in the delivery).
  3. make sure to compile the type of files that require compilation (middle and client tier)

If the patch contains database files it is a good idea to use the tool IFS Configuration Builder. It will convert the component folder structure into a build folder structure, and also gather and merge all database files into deployable files. If the patch does not contain database files the tool could still be used, but then it is quite easy to manually create the build folder structure.

When created, the build structure should then be copied into the <build_home> folder.

Follow these steps:

  1. Create a build structure and place it in a temporary delivery folder:

    If the patch contains database files (use IFS Configuration Builder):
    1. Put you patched files in a folder structure identical to a component folder structure, i.e. at the first level you have the components with relevant sub folders below.

    2. Fetch the deploy.ini files for the components in the delivery and include them among the other files. The deploy.ini file should be placed on the top level for each component.
    3. Start IFS Configuration Builder, create a temporary workspace and select the folder where you have your patched files as the "Component Folder". Create a new delivery location folder (e.g.c:\delivery62111) and define this to be the "Build Destination".
    4. Make sure that you unselect the compile options (for Java and C#) before you start building by clicking the Build button.
    5. Create the install.tem file. From the tool, log on the database to get the correct upgrade scenario for the included components.

    Else if the patch does not contain any database files (manually create the build structure):
    1. Create a new delivery location (e.g. c:\delivery62111). The folder structure should be identical to a <build_home> structure.
      In other words, files in the folder \fndadm\source\fndadm\ApplicationMonitoring\ are copied to the folder  c:\delivery62111\source\fndadm\ApplicationMonitoring\.
  2. Note! Remove Read Only attributes on all files in the delivery folder.
  3. Copy the contents of the delivery folder (c:\delivery62111), into the top of an existing <build_home>.
  4. Open a command window and navigate to the <build_home>\source folder.
  5. Set an environment variable to point to your delivery location (i.e. write set DELIVERY=c:\delivery62111).
  6. Run the script _ant_compile.cmd to compile java code
  7. Run the script _msbuild.cmd to compile IFS Enterprise Explorer

 

The delivery/patch is now ready to be installed/deployed.