Page tree
Skip to end of metadata
Go to start of metadata

The Packages tab is used to add device drivers and other types of product extensions. Some packages are installed as part of the base software installation and some packages must be added after the base software is installed.

When a device driver package or extension is installed on a node, the name of the driver or extension appears on the list of packages on the tab.

The Packages tab has a table format with columns that provide the name of the package, the type of package (such as a device driver), and the version number of the package. When a row is selected, additional information appears at the bottom of the tab.

Obtaining the package or extension file

It is assumed you have a Management Portal user ID and password and know how to log on. You need this to download the package or extension file from the Management Portal.
If you need a Management Portal account, see Creating your Management Portal account.
If you received the package or extension file from your sales representative, you can skip the download steps and proceed with Adding device drivers and extensions.

To download a device driver or extension package from the Management Portal, follow these steps:

  1. Log on to the Management Portal, select Developer and then select Resources.

  2. From under Index of files, click the appropriate build that matches the version of the runtime installed on your node.


    It is important that the version of the package or extension is one that is supported on the runtime version installed on your node.
    If there are any questions, contact your sales representative.

  3. Select the appropriate product platform, for example OS_Windows. If there is a 32bit or 64bit directory, select the one that matches your deviceWISE runtime product.

  4. Select Packages.

  5. Select Generally_Available, Pilot_Ready, or Prototype for the list of the various packages for that product platform.

  6. Select the appropriate file and download it to a temporary location.

Adding device drivers and extensions

From the Packages tab, you can add the device driver or extension to the node.

To add a device driver or extension package, follow these steps:

  1. From the Workbench left pane, expand the node where you want to add the package.

  2. Select the Administration icon.
    The Administration window appears.

  3. Select Packages to bring the tab to the front.
    The Packages tab displays all packages that are currently installed on the node.

  4. At the bottom of the Package tab, select Add.
    A message similar to the following appears informing you the node may be restarted.

  5. Select Yes.
    The Package File Location window appears.

  6. Change to the location of the packages file, and then select the file.
    The file name is added to the File name box.

  7. Click Select.

The package will be copied to the node and installed, and then the runtime will be automatically restarted. If there is any problem with the automatic restart of the runtime, you will have to manually restart the components.

Removing device drivers and extensions

From the Packages tab, you can remove a device driver or extension from the node.

Select the desired package and then select the Remove button.

Platform limitations when adding or removing packages

On some platforms with limited operating system resources for memory or disk (persistence storage), there may be failure when attempting to add or remove packages. These failures are the result of the limited system resources and possible runtime behavior such as memory fragmentation. When these failures occur, restarting the node at the operating system level (power off then power on) may then allow the package add or remove to succeed. In other scenarios, you may have reached a platform limit based on the application definitions, the number and size of packages added and other dynamic runtime requirements.

Manually restarting a node

To manually restart a node, use an option that applies to the operating environment as follows:

Using the Workbench:
  • From the Workbench left pane, expand the node you want to restart.
  • Select Administration, and then select the Node Administration tab.
  • From the the bottom of the tab, select Restart.
    A Restart window appears.
  • Select Restart Runtime.
Using Windows directly:
  • From the Start menu, select All Programs ->deviceWISE ->Runtime, and then select Stop deviceWISE Core.
  • From the Start menu, select All Programs ->deviceWISE ->Runtime, and then select Start deviceWISE Core.
Using AIX or Linux directly (as root):
  • From the command line, type /opt/dw/devicewise restart (and the press Enter).
Using Enterprise Gateway for Siemens EPRC and Mitsubishi MESInterface IT nodes:
  • Toggle the RESET switch on the node or power off then power on the rack where the node is located.

You will know that a device driver package was installed successfully (assuming any required licenses were added) because you will see the corresponding device types listed in the Device window for a device driver or the corresponding features for the extension. For example:

Node processing of software update packages using the Workbench Packages tab

In addition to using a SUP file in a Campaign defined and started in the IoT Portal, a node can have a SUP file applied to it by using the Workbench -> Administration -> Packages tab.
When using the Workbench -> Administration -> Packages tab, Add function, change the Files of type parameter from the default Package Files (*.pkg) to Software Update Package Files (*.sup), to be able to browse for your SUP output files.

This processing of the SUP file by the node is similar to its processing when it is initiated in a Campaign. The main difference is that the completion status is not reflected in the IoT Portal in a Campaign's status.

Adding a license for the package

Depending on the package or extension installed, you may need to add a license to activate the features.
For more information, see Licenses.

  • No labels