This parameter is required if a skin is to be used for at least one additional data source.
If several additional data sources have been specified, a skin can be specified for each of the specified data sources. The skins, separated by a space, are specified in the same order as the data sources.
If no skin is to be specified for one or more data sources, an empty path (
"") can be specified.
The skins for each additional message data source are applied in the following order:
|Data source with explicitly specified skin file|
Data source with empty skin file (
|1||Explicitly specified skin path for the data source||Skin file in the application directory|
|2||Main data source skin file||Main data source skin file|
|3||Default skin (IBITECH skin)||Default skin (IBITECH skin)|
This parameter can be omitted under the following circumstances:
- Only one additional data source was specified and the skin file with the name IBI.aws.Client.Additional.iacskin is located in the same directory as the application
Several additional data sources have been specified and all skins are located under the name IBI.aws.Client.Additional.<Data source position>.iacskin in the same directory as the application.
In the file name, <Data source position> must be replaced with the position of the data source in the AdditionalRemarks start parameter. Examples are listed below.
For more details on how to deploy skins, see Skin file distribution.
IBI.aws.Client.exe /AdditionalSkin "IBI.aws.Client.support.iacskin"
In this case there must be a skin file named “IBI.aws.Client.support.iacskin” in the application folder.
IBI.aws.Client.exeIf an additional message data source has been specified, a skin file called IBI.aws.Client.Additional.iacskin or IBI.aws.Client.Additional.1.iacskin must be located in the application directory.
If multiple additional message data sources have been specified, the corresponding skin file named IBI.aws.Client.Additional.<Position>.iacskin must be in the application directory - with three additional message data sources the skin file names would be: IBI.aws.Client.Additional.1.iacskin, IBI.aws.Client.Additional.2.iacskin and IBI.aws.Client.Additional.3.iacskin
IBI.aws.Client.exe /AdditionalRemarks "//fileserver/datasource1.ibi" "//fileserver/datasource2.ibi" "//fileserver/datasource3.ibi" "//fileserver/datasource4.ibi"
/AdditionalSkin "" "IBI.aws.Client.Department1.iacskin" "" "IBI.aws.Client.Department2.iacskin"
The following skins were given for four data sources:
- Data source 1 (//fileserver/datasource1.ibi): No skin
- Data source 2 (//fileserver/datasource2.ibi): Skin named IBI.aws.Client.Department1.iacskin
- Data source 3 (//fileserver/datasource3.ibi): No skin
- Data source 4 (//fileserver/datasource4.ibi): Skin named IBI.aws.Client.Department2.iacskin