Install the Creo Schematics client

Load CadActive in Creo Schematics with CLIENT_CLASSPATH, custom shortcuts, and the ribbon .ui file.

Install CadActive so Creo Schematics can find the Java application, show CadActive commands, and place them on the ribbon. You need all three pieces. This is not the Creo Parametric plugin: do not use config.pro, creotkdat, or Auxiliary Applications.

If you do not have the files yet, start with Download the Creo Schematics client.

Before you start

Creo Schematics is installed, and you can edit schematics.psf next to schematics.exe (often under Program Files — you may need an administrator).
You have the CadActive jar (or class folder), creo_schematics_shortcuts.dat, and creo_schematics_user_customization.ui.
A Java 17 or later JRE is installed, and PRO_JAVA_COMMAND points at it if PTC requires that on your Schematics version.
Exit Creo Schematics completely before you copy files or edit the psf. Schematics locks the ribbon .ui and shortcut store while it is running.

1. Put the application on disk

Copy the CadActive .jar (or the folder of .class files) to a stable location on the workstation. A common choice:

Example after copy:

Use the real folder and file name from your package. CAD admins can use a shared path instead; every workstation’s CLIENT_CLASSPATH must point at a location that workstation can read.

2. Set CLIENT_CLASSPATH in schematics.psf

Creo Schematics loads CadActive Java from CLIENT_CLASSPATH in the psf that launches Schematics — the same folder as schematics.exe:

Open schematics.psf in a text editor.
Find the line ENV=CLIENT_CLASSPATH= (add it if it is missing). This is an ordinary Windows Java classpath: entries are separated with ;, and each entry may be a directory or a .jar file.
Set it to the full path of the CadActive jar (or class folder). Example:

Use a fully expanded path. If you already have other entries on CLIENT_CLASSPATH, append CadActive with a semicolon rather than deleting them.

Do not try to load CadActive with add_java_class_path in creo_schematics_config.dat. That option is leftover from Creo Parametric / J-Link. Schematics ignores it, and CadActive will fail with ClassNotFoundException: cadactive.CadActive.

Save the psf. You must restart Schematics for the change to take effect.

3. Deploy Custom Java shortcuts

CadActive commands are Custom Java shortcuts. Creo Schematics reads them from the per-user custom-command store:

Copy the creo_schematics_shortcuts.dat from your CadActive package into that folder (create the folder if this user has never launched Schematics).

That file defines the CadActive actions (including Log In, Log Out, Import Design Data, and Export Design Data). The interactive equivalent is File → Options → Environment → Custom Command Settings → Define Custom Command → Custom Java. CadActive ships the file so you do not have to create each button by hand.

If this workstation already has custom commands you must keep, have a CAD admin merge the CadActive records into the existing file instead of overwriting it.

If an older RSdesigner_shortcuts.dat is still in that folder, it can shadow your new shortcuts. Prefer creo_schematics_shortcuts.dat and remove or rename the stale file if buttons do not appear.

4. Deploy the ribbon customization (.ui)

Shortcuts define the commands. The ribbon tab, groups, and button sizes live in a separate file:

Copy the creo_schematics_user_customization.ui from your CadActive package into that folder. Copy the shipped file — do not hand-edit it. The file is not a plain-text layout.

If this user already customized the Schematics ribbon, copying the CadActive .ui replaces that customization. Coordinate with your CAD admin if you need both.

5. Restart and check the ribbon

Start Creo Schematics. You should see a CadActive tab. Drawing the ribbon does not load Java by itself; the application loads when you run a CadActive command (next: Sign in to CadActive in Creo Schematics).

Optional: run CadActive when Schematics starts

Creo Schematics does not auto-load CadActive Java at launch unless a startup trail fires a Custom Java shortcut. If CadActive included a startup trail and creo_schematics_config.dat settings, your CAD admin can deploy those to the same %APPDATA%\PTC\Creo\Schematics folder.

Paths in startup_trail / startup_trail_name must be absolute Windows paths. Creo Schematics does not expand %APPDATA% in that file. Leave startup_trail_set off unless CadActive asked you to enable it.

If CadActive does not appear

Confirm Schematics was fully closed before you copied files, then restart.
Confirm CLIENT_CLASSPATH in schematics.psf points at the jar or class folder you copied, and that the path exists.
Confirm both creo_schematics_shortcuts.dat and creo_schematics_user_customization.ui are in %APPDATA%\PTC\Creo\Schematics.
Confirm Java 17+ is installed and PRO_JAVA_COMMAND is set if PTC requires it for your Schematics version.
Do not use add_java_class_path for this plugin.

If you need help installing, email support@cadactive.com.