Deploying Your INtime System

Once you have an application to run on INtime, you may want to automate its deployment onto production systems

INtime for Windows

The following process assumes that you have already installed and configured Windows to your specifications.

Using runtime*_installer.exe manually

To manually install INtime runtime software, use the runtime installer runtimeXX_installer.exe. You can find runtimeXX_installer.exe in the redistribution folder of the CD-ROM, or in the most recent runtimeXX-YYYYY_installer.exe installer obtained from TenAsys (XX is the current product version and YYYYY is the patch number).

Start runtimeXX_installer.exe program by double-clicking it.
Note: If the Installation program detects a previous version of INtime software, it prompts you to upgrade the installation. For details of the upgrade process, see the document intime_installer.ovw.exe in the %INTIME%\help folder.
Review the INtime License and note its terms and conditions.
Select a destination directory for the INtime software files, then click the Next button. The default is %PROGRAMFILES%\INtime.
Click the Next button to install the software.
The runtimeXX_installer.exe program creates the directory you specified, then installs the INtime software files.
Click the Finish button to complete the installation process.
Restart your system using one of these methods:
- Click OK at the last screen. The runtimeXX_installer.exe program restarts your system.
- Restart your system at a later time. You must restart your system before running INtime software.
Note: The runtimeXX_installer.exe program installs those portions of INtime software that you can include in your derivative works. Use of runtimeXX_installer.exe is governed by the INtime Software Redistribution License Agreement you must enter into in order to include INtime Software in your product.

For information about obtaining a Software Redistribution License and on the associated per unit royalty due to TenAsys Corporation for use of the INtime software in your product, contact sales@tenasys.com.

Note: If the user account that will use INtime on this computer is not an administrator, you must add the user to the system's INtime Users Group.

Custom/command-line installation of the INtime for Windows runtime package

Customization of the runtime installation can be achieved using command -line options, and then your specific configuration can be applied using other commands. These are suitable for inclusion in a batch file.

Command Line options

The INtime for Windows installer accepts some command line options for initial configuration.

/silent – passing the silent flag to the installation package will suppress any user input and show only progress dialogs during installation. No reboots will be initiated automatically. The calling process should check the return code and handle a reboot manually if ERROR_SUCCESS_REBOOT_REQUIRED is returned. .
/forcereboots – This command line option can only be used with the /silent option. It will change the behavior of the installation sequence so that a reboot is initiated immediately after the any package has been installed or upgraded.
/skipusbdriver – This option will skip the installation of the SafeNet Hardware Key driver software.

Other commands specified on the command line will be passed onto the INtime package installer. These options include the standard options available to any MSI package, as well as other options provided by TenAsys to customize the INtime installation: (please note the behavior is different for an upgrade installation, detailed below)

SKIPVETHERINSTALL=1 – Setting this property to 1 will not install the Virtual Ethernet Windows Driver
INSTALLLEVEL=1000 – When running the INtime installation package silently, it will default to only install development components (for example, visual studio support, INscope, Spider Debugger, etc.) If you wish to have local INtime kernels, you must set the INSTALLLEVEL property to 1000. During an upgrade installation this will is the default.
INSTALLDIR=”[Path]” – Setting this property to a path will change the default installation location. Please note that settings in the configuration may depend on this path being the same as the system you prototyped on.
AUTHCODEACTIVATION=1 – Setting this property to 1 will configure the INtime License Manager to prompt for a Single Use Authorization Code. The default internet activation process requires a username and password to be issued by TenAsys before you can activate against the TenAsys license server.
Please note that some standard MSI command line options will not change the behavior of the installer package.
/q options – will not be honored by the installer because they are already set inside the installation package
/restart, /promptrestart, /forcerestart – will not be honored

Use the switches mentioned earlier to control restart and user interface levels.

INtime for Windows installer return values

The INtime for Windows installer will return values based on the state of the installation. You can use these return values in your own installation script to determine the next steps.

Return Code	Meaning(s)
ERROR_SUCCESS 0L	No errors were detected during execution. You should reboot Windows after you have completed any other configuration steps.
ERROR_SUCCESS_REBOOT_REQUIRED 3010L	The installation is successful so far, but a reboot is required before continuing.
ERROR_BAD_COMMAND 22L	Command line options passed to the installer were not properly formed.
ERROR_CANCELLED 1223L	An installation was cancelled by the user, OR a UAC timeout has occurred.
ERROR_ALREADY_EXISTS 183L	This version of INtime is already installed, OR a newer version of INtime is already installed
Other values	Are error conditions returned from one of the steps of installation. You should further investigate the stage of installation this error was detected and contact TenAsys Support for details.

Configure INtime for Windows

Once you have installed INtime, you can run some additional configuration steps to suit your needs.

Import Configuration

You should export the working configuration on your prototype system to an icf file. Open the INtime Configuration Panel. Select one or more icons (use the Ctrl key to select more than one icon), then press the button. You are prompted for a file name to which the settings are written.

Transfer the exported settings file to your target system. On your target system, start INtime Configuration and press the Import button. Navigate to the settings file and press Open.

You can also import settings using a command line option which you can use in scripts. To import a configuration file, type:

inconfig.exe /i:intimeconfiguration.icf

For a list of all of the command line options, see the Help content for INtime Configuration (press the Help button on the utility).

Note that an .ICF file is specific to one machine configuration and does not adapt itself well to other machines. For example if you create a configuation on a system with a 4-core CPU and import it on a system with an 8-core CPU you will not necessarily get the results you expect. This also applies if you have external memory configurations imported into systems with a different amount of memory fitted.

If you need to address a range of different systems with your configuration, consider using dynamic configuration (see next section).

Dynamic configuration

You can create a configuration utility using the LNC (Local Node Configuration) library to handle dynamic configuration of your systems.

Advanced customization

The Windows Virtual Ethernet Driver Address and MAC address will both be installed with their default values. Consult the Windows netsh documentation to script the IP address(s) needed for the Windows side of the Virtual Ethernet configuration.

Device Configuration

You can export and import your device configuration using the method described above for "Import Configuration". Just select the Device Manager icon when exporting your configuration. You can also use the devconfig.exe utility in command-line mode to pass individual devices to INtime or back to Windows. For example:

devconfig64 /tointimenoirq "Intel(R) Ethernet Connection I218-LM"

See the help content for the utility for full details of the command line options.

License Installation

Once installed and configured the final step in activating the INtime for Windows installation.

License Manager command line options

You can activate the INtime for Windows installation on the command line via the licman.exe application.

Please familiarize your with the requirement for internet activation in the applicable document.

Username based activation

You can activate this installation against your pool of licenses by submitting your username and password on the command line:

Licman.exe –u:username –p:password

Optionally, and recommended, you can supply a comment to add to this activation on the license server. Please limit this to the max 64 chars:

Licman.exe –u:username –p:password –m:”Activating order 3153 – line 5”

The License manager application will default to request an INTIME-RT from your pool, however you can set the license type on the command line too. Available values are ‘s’ for single and ‘m’ for multi-core:

Licman.exe –u:username –p:password –m:”Activating order 3153 – line 5” –t:m

INtime Distributed RTOS

For Distributed RTOS installations the most convenient way is to clone the HDD. As the license file is stored on the HDD, it needs to be deleted before running the new system. An invalid license will prevent the system from start, but a missing license allows to boot and apply a new license within 10 minutes after boot. The license file is located in \boot\ and called store-0.

Note: As tethering also uses the license file, it is not enough to setup the master with tethering and clone this HDD. The /boot/store-0 file has to be excluded from HDD image in any case.

Alternatively the system can be set up with the boot stick and the folder /config can be copied manually via ftp later on. All settings for kernel startup and node configuration are stored in this folder.