Image component (IC) mapping stanza
In order for a VAST Platform image that is bound to image components to start properly, it must be able to find all the ICs on which it depends. The [Ic path] stanza of the .ini file is used to provide the location(s) of ICs. When the location of ICs is not specified correctly, VAST Platform will not start up.
Within the [Ic path] stanza, you can specify an entry that identifies the default IC directory. You can also specify entries that designate exact mappings of logical IC names to directory locations. The entries cause the virtual machine to search in the specified directories for ICs. The search order is as follows for a logical IC name:
1. If the .ini file specifies an explicit mapping of the name to a path and file name, use that path and file name and no other.
2. If the .ini file does not specify an explicit mapping of the name to a path and file name, look in the startup directory for an IC file named the same as the logical IC name.
3. If the IC file is not found in the startup directory, look in the directory specified by the IC_ROOT= parameter for an IC file named the same as the logical IC name.
All product ICs are shipped in the same directory. This directory is the default location in which to search for ICs. The abt.ini file shipped with the product provides an entry that identifies this default location as follows:
[Ic path]
IC_ROOT=$TARGETDIR\icsrn\
where $TARGETDIR is replaced with the client directory name specified during product installation.
The trailing separator is required on the IC_ROOT= declaration as strings for the IC_ROOT and the logical IC name are simply concatenated.
The IC_ROOT= value must have path delimiters appropriate to the execution platform.
You can place your ICs in the same directory as the product ICs, or you can keep your application ICs in separate directories (perhaps one directory per application). For example, if you want to keep your application ICs in separate directories from the product ICs, you can use the .ini file to identify the location of those application ICs by adding additional entries to the [Ic path] stanza that map logical IC names to physical path and file names as follows:
[Ic Path]
IC_ROOT=$TARGETDIR\icsrn
prereq.ic=c:\myapp\rel1\prereq1.ic
another.ic=c:\myapp\rel1\prereq2.ic
where $TARGETDIR is replaced with the client directory name specified during product installation.
If $TARGETDIR is C:\Program Files\Instantiations\VASTPlatform\13.0.0, then based on this .ini file, the IC load operation will look in the startup directory and then the C:\Program Files\Instantiations\VASTPlatform\13.0.0\icsrn directory for all IC logical names except prereq.ic and another.ic.
The logical IC names specified in the .ini file section entries must be in lowercase. The path and file name information should be appropriate for the execution platform. In addition, the IC file name is not required to be the same as the logical IC name.
If you ship your software in ICs, you must do one of the following:
•Put each IC into the startup directory of the VAST Platform image that depends on them, or
•Put each IC into the directory specified by the IC_ROOT= line in the [Ic path] stanza of the .ini file, or
•Add a <logical IC name>=<filepath> entry for each IC to the [Ic path] stanza of the .ini file.
For more information on ICs, see Packaging with image components (ICs).
Last modified date: 02/11/2021