How to Create and Connect to a Rocket U2 Connection in VDM

Use a Rocket U2 Connection Profile in VDM to connect to a Rocket UniVerse or UniData database for reporting. This guide explains the connection’s purpose, the setup information you need, available client software, and the steps shown in the existing screenshots.

Trouble viewing images? Right-click an image and select Open image in new tab to view it at full size.

What Is Rocket U2, and When Should I Use This Connection?

Rocket U2 refers to Rocket Software’s UniVerse and UniData MultiValue databases. Applications built on these databases store business information that you may need to query, report on, or visualize in VDM.

Use this connection when your application’s database is UniVerse or UniData and your administrator or BridgeWorks Support has directed you to use VDM’s Rocket U2 connection type. Creating a profile connects to an existing database; it does not install a database server or create the application’s data.

Rocket provides both native client interfaces and standards-based ODBC interfaces. See Rocket U2 Clients for an overview.

Rocket U2 Connection or ODBC?

For the ODBC route, the driver and ODBC Administrator must match the application’s architecture. VDM version 10 and later use 64-bit ODBC drivers. See Understanding 32-bit vs. 64-bit ODBC Driver Configurations.

Do not add an ODBC DSN as a troubleshooting step for the Rocket U2 workflow unless you are intentionally switching to the ODBC connection route.

Before You Begin

Obtain the following from your database administrator or application provider:

• The UniVerse or UniData server name or IP address.
• The database/account name or account path required by the connection.
• A username and password with access to the required data.
• The appropriate VDM Platform selection.
• The server’s client connection service, port, and any TLS or other security requirements.

Have the administrator confirm that the server permits the required client connections and that the VDM computer can reach it. Rocket documents 31438 as the default UniRPC port, but your deployment may use a different port. Use the actual configuration, not a guessed default. See Rocket’s UniRPC connection and port guidance.

Client Software and Download Links

Which installer is required? These are official Rocket resources, not a requirement to install every package. Confirm with BridgeWorks Support whether your VDM installation already includes the necessary client components and whether a separate installer is required for your version and server. Use the compatible package they identify.

Windows checklist: Confirm VDM and its required runtime are installed, any identified Rocket client dependencies are available, and network/DNS access works. Configure a Windows ODBC driver, UCI file, and DSN only for the ODBC route. You do not need to install a UniVerse or UniData server on the reporting workstation merely to connect to an existing remote server.

Create the Rocket U2 Connection Profile

Step 1: Open VDM

Launch VDM on the computer where you will use the connection.

Step 2: Open the Database Tab

Select Database on the ribbon.

Step 3: Start a New Profile

Select New to start the Connection Profile Wizard.

Step 4: Select Rocket U2

Choose Rocket U2 as the connection type.

Step 5: Disable the Schema Prefix

Clear Prefix TO/Schema Name, as shown for this workflow, then select Next.

Step 6: Enter Credentials

Enter the Username and Password supplied for database access.

Step 7: Enter the Server

Enter the server name or IP address supplied by your administrator.

The original guide includes these deployment-specific ResolveIP rules:

• Linux Docker with ResolveIP = True: Use the DNS name.
• Linux Docker with ResolveIP = False: Use the IP address.
• Windows: Either a reachable DNS name or IP address can be used.

If these settings apply to your environment, confirm them with your administrator or BridgeWorks Support. They are specific to this connection configuration and are not a general instruction to change Windows DNS settings.

Step 8: Enter the Database or Account

Enter the database/account value supplied for your U2 application. Confirm whether your environment requires an account name or path; do not substitute the server name or username.

Step 9: Select the Platform

Select the Platform appropriate to your application and database configuration. Ask your application provider or BridgeWorks Support if you are unsure which option to use.

Step 10: Test and Save

1. Select Test Connection.
2. If successful, select Next.
3. Enter a recognizable profile name and save the Connection Profile.

If the test fails, correct the connection details or resolve the client/server issue before testing again.

Open and Verify the Connection

Select Load All on the Database ribbon, then locate and open the profile in Tables and Fields. Confirm that the expected data objects are available and run a View to verify the results.

See How to Open a Database Connection in VDM for connection indicators.

Troubleshooting

• Missing client component or provider error: Ask BridgeWorks Support to identify the required Rocket component and compatible version before installing or replacing software.
• Timeout or connection refused: Have your administrator check the U2 connection service, configured port, firewall access, and server address.
• Authentication or account error: Confirm the credentials, database/account value, permissions, and Platform selection.
• DNS or ResolveIP issue: Check the deployment-specific server-name rules above.
• ODBC DSN issue: Use the separate ODBC setup guide if you are configuring the ODBC route.

Need Help?

Contact support@bridgeworksllc.com with your VDM version, UniVerse or UniData version, connection route, Platform selection, and error message. Do not include passwords.