| Info |
|---|
| This article includes updates for Card SDK 6.1. |
This article describes how to
...
install Nexus Card SDK.
...
...
| See Card SDK requirements and interoperability regarding the installation requirements for Card SDK |
...
Step-by-step instruction
| Expand |
|---|
| title | Run Card SDK setup file |
|---|
|
Run the setup file: Nexus_Card_SDK_Setup_(xxx).exe. In the pop-up window User Account Control, enter an administrator username and password, and click Yes. - In Installer language, select a language and click OK.
|
| Expand |
|---|
| title | Silent installation of Card SDK |
|---|
|
You can also do a silent installation of Card SDK. Silent installation can be used for installing Card SDK on several machines at once via software distribution. Use the /S parameter when you run the setup file: Nexus_Card_SDK_Setup_(xxx).exe /S |
| Note |
|---|
Silent installation with "Wibu Dongle" is not supported. |
| Expand |
|---|
| title | Do Nexus Card SDK setup |
|---|
|
- In the Nexus Card Setup window, click Next to continue.
- Read and accept the End-User License Agreement.
- Select components to be installed.
- Choose installation path for application and data.
- Example:
Application: C:\Program Files (x86)\Nexus Card SDK
Application data: C:\ProgramData\cms
If an existing installation of Nexus Card SDK (or IDExpert SDK) is found, choose the “Do not overwrite data” option. Click Install. Click OK to proceed. - Internet/Intranet access is needed, so “Allow the access”.
- New items were installed in the start menu and on the desktop.
|
| Expand |
|---|
| title | Licensing for Nexus Card SDK |
|---|
|
After the installation of Nexus Card SDK, the system always runs in demo mode. It is only after installing the license file, including matching it with the dongle-ID or the computer-bound system ID, that the system will be licensed in accordance with the information contained in the license file. |
Result after installation
| Expand |
|---|
| title | Entries to the registry |
|---|
|
The installation adds the following entries to the registry of the local PC. |
...
32-bit OS:| Key | HKEY_LOCAL_MACHINE\SOFTWARE\Nexus\IDExpert SDK |
|---|
| Values | Name | Type | Value |
| InstallDir | REG_SZ | C:\Program Files\Nexus Card SDK |
| Name | REG_SZ | Nexus Card SDK X.X.X |
|
...
64-bit OS:| Key | HKEY_LOCAL_MACHINE\SOFTWARE\ Wow6432Node\Nexus\IDExpert SDK |
|---|
| Values | Name | Type | Value |
| InstallDir | REG_SZ | C:\Program Files (x86)\Nexus Card SDK |
| Name | REG_SZ | Nexus Card SDK X.X.X |
|
| Expand |
|---|
| title | Entry on the Windows client PC |
|---|
|
The installation creates the following entry on the Windows client PC: Start/Programs/Nexus Card SDK/ - CardDesigner - Application for layout designing and card types
- ConfigurationManager - Configurator for devices and licensing
- Overview and Quickstart - HTML file with information about Nexus Card SDK
|
| Expand |
|---|
| title | Item in Windows Control panel |
|---|
|
The installation creates an item in the Windows control panel, which can also be used to uninstall the program package. |
| Expand |
|---|
| title | Installation directories |
|---|
|
...
Two directories are created, which have the following basic meaning: - Program and documentation directory
Contains all program files (EXE, DLL, OCX), as well as PDFs and example programs - Configuration and data directory
Contains configuration files (for example of Configuration Manager), layout files (unless working in Web mode), encoding rules, etc.
The directory structure looks like this: Programs/Nexus Card SDK/ System (program files)
Doc (documentation)
Examples (integration samples) ProgramData/cms/ (configuration files) |
...
...
Card SDK
...
installation
...
FAQ
| Expand |
|---|
| title | Card SDK installation FAQ |
|---|
|
| Question | Answer |
|---|
| Does the application need access to Network Drive UNC-Path/Drive? | No | | Is the application backend located on a Network Drive UNC-Path/Drive? | No | | Does the application receive automatic updates from a network drive UNC-Path/Drive? | No | | Does the application require web services protocol, DNS name, or IP address? | Yes, https | Does the application require a software protection device, for example dongle or floppy
disk? | Yes | | Does the application require a licence key or an activation code? | Depends on installation | | Does the application require a licence server DNS name or IP address? | No | | Does the application require a description of the activation process? | No | | Does the application require a particular network printer or print server (DNS name or IP address)? | No | | Does the application require a particular local printer and driver? | No | | Does the application require a particular hardware device and driver? | No | | Does the application require another application for execution? | No | | Does the application require modify permission on the C:\ drive, apart from the default installation/program folder? | No | Is this application certified for the current operating system by its manufacturer? See Card SDK requirements and interoperability for supported OSs. | Yes | | Does the application require access to a centrally managed SQL database? | No | | Are ODBC data sources required? | No |
|
...
Related information
...
