Configure Connection

Skyward SMS 2.0 guide

Connect NIM to Skyward SMS 2.0 through the Progress OpenEdge driver, with optional VPN automation where needed.

Before you beginDirect link to Before you begin

This integration uses a database connection through Progress OpenEdge Driver 11.7 or later. Review the vendor's Skyward ODBC Launch Kit before configuring the connection.

For the connector overview and supported database operations, see Skyward SMS 2.0. This guide covers the driver and network prerequisites, including a client VPN example when direct database access is unavailable.

NIM requires the Progress driver installation, Hostname, Port, Database Name, Username, and Password.

Install the driver and arrange accessDirect link to Install the driver and arrange access

Follow the existing Skyward ODBC Launch Kit to install Progress OpenEdge Driver 11.7 or later on the NIM server.
Obtain the database hostname, port, database name, and account credentials from your Skyward or database administrator.
Arrange read access to the tables needed for downstream provisioning. Grant the corresponding write permissions only for the records and operations your process will manage.
Confirm network access from the NIM server. If a VPN is required, review the existing VPN guidance below.

Enter the connection settingsDirect link to Enter the connection settings

In NIM Studio, open Systems > Overview and add a Skyward SMS 2.0 system, or select the existing system.
Open Connection, enter the following settings, and save.

Requirement or setting	Value
Progress driver installation	Ensure the required Progress OpenEdge driver is installed and available on the NIM server.
Hostname	The Skyward database server hostname.
Port	The database connection port supplied by your administrator.
Database Name	The Skyward database NIM will access.
Username	The account authorized for the intended database operations.
Password	The password for that account.

Test database connection and table discoveryDirect link to Test database connection and table discovery

Select Test Connection. NIM attempts to open a database connection and execute the following query:

SELECT TBL 'Name', 'Table' "Type"  FROM sysprogress.SYSTABLES_FULL WHERE TBLTYPE = 'T' ORDER BY TBL

If the test fails, verify the driver installation, Hostname, Port, Database Name, credentials, network access, and any required VPN connection.
Collect the tables required by your process and validate record matching and field mappings before enabling downstream provisioning.
Test intended database changes, such as a user email update, with safe records and verify the result before enabling automated writes.

The connection test checks database connectivity and table discovery. Validate permissions for the selected tables and each intended Read, Create, Update, or Delete operation separately.

Step 1 of 3

Use a client VPN when requiredDirect link to Use a client VPN when required

Prefer a site-to-site VPN

When a VPN is required to reach the database, use a site-to-site VPN where possible. It is more reliable for an unattended NIM service than an interactive client VPN.

The following Cisco AnyConnect example opens the VPN before NIM connects to the database.

Create a connection file, such as C:\Tools4ever\Scripts\connect.txt.
connect.txt
```
connect vpn-1.iscorp.com idofgroup thisismyusername thisismypassword
y
quit
```
Do not store passwords in plain text
The example above illustrates the required VPN command structure only. Do not place a real password in connect.txt. Use an approved secure credential method for the account running the NIM service.

Create C:\Tools4ever\Scripts\OpenVPN.bat to close existing AnyConnect processes and open the VPN.

OpenVPN.bat
@echo off
cd /d C:\Tools4ever\Scripts
taskkill /S localhost /IM vpncli.exe /F /T
taskkill /S localhost /IM vpnui.exe /F /T
"C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\vpncli.exe" -s < connect.txt

Create C:\Tools4ever\Scripts\CloseVPN.bat to disconnect when the connection is no longer required.
CloseVPN.bat
```
@echo off
"C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\vpncli.exe" disconnect
```
Configure NIM to run the opening script before its database connection is used, then test the connection from the NIM server.