Smarteam Install

Smarteam Server Installation V4.0 12/19/00

1. Hardware requirements are shown below...

If the vault server is a strong machine, you can use it both to SmarTeam and
Vaults server.
You do not need two machines for those issues.

The recommendations are as follows:
Have a different computer for the Oracle database server and the vault
server.
The Oracle 8i should use a Pentium III of one of the latest models. (733
+). If running on Windows 2000 server, it is recommended to use a dual
processor. This fastens the response time of Oracle.
You should use at least 512M RAM. More is better, of course, but not
vital.
Disk space should be 5G or more. Raid 5 or mirrored disks will improve
performance, and will provide recovery option in case of hardware
failure.
The vault server should be located on a similar machine. Dual processor
is not much an added value.
Disks should be SCSI with RAID for backup against hardware failure.
RAID5 or mirror will do. Size: 40G, with an option to add more disks to
the array if run out of space.
Operating system could be either NT server or 2000 server.
Network should support at least 100M/Sec.

Regards,
Ronnie Efrat

The data above is based on the following....

1. How much data is going to be produced in a month / year?

month per user = ~40mb
yearly per user = ~480mb

2. Please provide a typical assembly size?

700-1500 unique parts

3. Can you estimate the data increase per month / year?

Our data needs should be pretty flat. Use 1.2 as an aggressive factor
based
on 40mb per user.

4. Is it distributed environment?

No

5. How many users are concurrent users?

50

6. What network you are using?

Microsoft Windows Network

7. Can you have two machines?

Yes we already have an Oracle server. Do we need to have Vault on a
server
other than the Smarteam server?

2. Software requirements are found in the README.htm file on the CD-ROM in the E:\Smarteam folder

3. Begin installation from CD-ROM.

Note: All menu picks are usually the defult but I have identified several key ones below.

    Note: Install may require a change of Registry Key Entry for NT OS Service Pack Data.
If Service Pack data includes a character appended to a number you may need to remove the character, Ex; "Service Pack 6a" must be changed to "Service Pack 6"
    Change Reg Key...
    \HKLM\SOFTWARE\Microsoft\Windows NT\CSDVersion.

Don't forget to login as Administrator before installation.

Dialogue:Select Components
Vault Server
License Manager
Smarteam
Smart Tools
Vault Tools
Integration Plugins (Note: Software for Integration should be loaded first ie; SolidEdge, Microstation, Office)
Help Files
Documentation
Icons Library

Dialogue:Protection Server Name
Name: SMSRV

Dialogue:SmarTeam Vault Server Users Group
Name: SmVaultAdmins
Description: Smarteam Vault Admin Group set up by Smarteam Installer

Dialogue:SmarTeam Vaults Clients User Groups
Name: SmVaultUsers
Description: Smarteam Vault Users Group set up by Smarteam Installer
Everyone: Everyone

Dialogue:Vault Server Service
Username: MDCAD\mdcad-admin
Password: ********
Confirm Password: ********

Accept Defaults for the remaining dialogs.

SmarTeam Terminal Server Setup

Windows 2000 Server Terminal Services

How to configure TS for "Remote Administration" Mode

I) Apply latest hotfix Q286132 'Invalid RDP data cause Terminal Server failure' path (or SP2 for Windows 2000).

II) Modify Terminal Server's listening Port in the following registry keys:

HKLM\System\CurrentControlSet\Control\TerminalServer\Wds\Rdpwd\Tds\Tcp

HKLM\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp

Find 'PortNumber' subkey and modify value to: '3ff' in hex (1023 as suggested by Security).

III) Configure 'Terminal Services Configuration' MMC:

MS RDP-Tcp (5.0) Properties under 'Connections' folder:

        General: Encryption Level set to "High"
        Logon Settings: Use client-provided logon information (default)
        check mark on 'Always prompt for password' (default)

        Sessions:
        Place check mark on 'Override user settings' (will override user's settings in user's profile).
        'End a disconnected session' set to 1 day
        'Active session limit': Never
        'Idle session limit': set to 3 hrs
        Place check mark on 'Override user settings'
        When session limit is reached or connection is broken:
        Place bullet on 'Disconnect from session'
        Environment: check 'Disable wallpaper' (default)
        Permission: Allow only 'Administrator' with Full Control. Remove all others.

        Network Adapter:
        Select the proper NIC being used.
        'Maximum connections' set to 2 (by license limitation only 2 concurrent users are allowed).

        Client Settings:
        uncheck 'Use connection settings from user settings' (will override user's settings)
        uncheck 'Connect client printer at logon'
        uncheck 'Default to main client printer'
        Disable the following by:
        Placing check mark on 'LPT port mapping'
        Placing check mark on 'COM port mapping'
        Placing check mark on 'Clipboard mapping'

        Remote Control:
        Select 'Use remote control with the following settings' (will override default user settings).
        Place check mark on 'Require user's permission'
        Place bullet on 'Interact with the session'

Server Settings folder in the Terminal Server MMC should be left at default settings:

        Terminal server mode: Remote Administration
        Delete temp folders on exit: Yes
        Use temp folders per session: Yes
        Internet Connector licensing: Disable
        Active Desktop: Enable
        Permission Compatibility: Windows 2000 Users

Note: For information on how to configure the Terminal Server 'Client' on your workstation, please follow the instructions here.

NT Home
SLAC Home

Feedback

SCS Windows Infrastructure Group
Last revised: October 24, 2001

Terminal Server Client Setup

How to configure MS Terminal Server client to connect to SLAC Win2k Server for Remote Administration

From the SLAC network drive: V:\SCS\Desktop\Admin\util\Tsclient\disk1

Note: Only two concurrent connections are allowed by the server - a licensing limitation of TS Remote Administration.

Run Setup. Accept the default installation directory (default path is C:\Program Files\Terminal Services Client). Click on Yes when asked to have the same initial settings for all users.

Once the install finishes. Go to the Start Menu --> Programs --> Terminal Services Client . Select "Client Connection Manager".

The "Client Connection Manager" program will run. Under the File Menu, select 'New Connection'. The Client Connection Manager Wizard will run.

Enter a label for the connection under 'Connection Name' (i.e., ServerName) and the server or IP address of the server you are connecting in the box below. In the next dialog box, do NOT enable automatic logon. Click Next for the Screen Options, select your desired resolution. Next for Connection Properties, enable data compression & cache bitmaps only if in slow links. Click Next twice & Finish to complete the wizard.

An icon has been created for this connection within the Client Connection Manager.

Select the icon, go to the File Menu and select Export. The 'Export As' dialog appears, type a name (i.e., ServerName) in the File name and Save it. Note: This file will be saved in the default installation folder.

Open up Windows Explorer (File Manager). Navigate into the installation location (default path is C:\Program Files\Terminal Services Client), open the file you created in step 5 with a text editor (i.e., Notepad). Find the 'Server Port=" entry and change the default No. to 1023. Save the file and exit.

Go back to the Client Connection Manager, select the server icon again, go to the File Menu to select Import. The 'Import From' dialog box appears, select the file you modified in step 6 and click on Open. A warning message will be displayed that looks like this:

Click on Yes, a second question will appear, click on Yes again.

Now double click on the icon to connect to the server.

Repeat steps 3 thru 7 to configure connections to other servers.

Questions: desktop-admin@slac.stanford.edu

Last revised: October 23, 2001

SmarTeam Service Packs/Patches

4. Install Smarteam Patches

Local patches stored at...
\\mdismp01\md\smarteam\service_packs\v4.0

    Retrieve Patches from
    http://www.smarteam.com/support
    User ID: smartcustomer
    Password: userPDM

SQL*Net (Net8) & SQL*Plus Install

Note: 8/27/01
A Silent Oracle client batch install is available at...
\\mdismp01\md\smarteam\oracle_client_rsp\batch_install.cmd

1. Simply logon as Administrator.
2. Map the X:\ drive and N:\ drive.
3. Double click on batch_install.cmd.
4. Done.

Batch install developed by Kurt Vaillancourt

***************************************************

Note: 7/12/01
A new client install is available at...

X:\Applications\Supported\Oracle\Client_tools\Client816\Setup.exe

Using windows explorer copy the following files:

x:\applications\supported\oracle\sqlnet.ora
x:\applications\supported\oracle\tnsnames.ora

to:

c:\orant\net80\admin

If you have trouble call George Crane

***************************************************

5. Install Net8 (SQL*Net), SQL*Plus & ODBC for connection to Oracle server from...

SLAC Domain \\Winsan1\Applications\Supported\Oracle\FormsReports\Release6i_CD

See Oracle Install Readme file at \\Winsan1\Applications\Supported\Oracle\readme.txt

This data is per George Crane, Oracle Expert (x2367)

It should look something like this...

(2) Installing the latest Oracle products:

              Oracle Installer       3.3.1.2.4
              Oracle Net8 Client     8.0.6.0.0-118119
              SQL*Plus               8.0.6.0.0-991122
              Oracle ODBC Driver     8.0.5.10.0

    a. Run the Oracle installer from:

        x:\applications\supported\oracle\FormsReports\Release6i_CD\setup.exe

        Company Name: SLAC
        Oracle Home:
            Name: DEFAULT_HOME
            Location: C:\orant
            Language: English

        Click OK with the above defaults

        Click OK to install Oracle Forms Developer products

        Select "Custom" and click OK

        Select the following products by clicking and holding
        down the Ctrl key.

              Oracle Installer 3.3.1.2.4
              Oracle Net8 Products 8.0.6.0.0-1181195
              SQL*Plus 8.0.6.0.0-991122

        Click "Install"
        Click ok at the General Information prompt (if you get it)
        Click OK when successful install completed

        Click "From..." in upper left corner of installer
        Navagate to:

            x:\applications\supported\oracle\odbc\ora8062\win32\install

        Click on the "nt.prd" file and click "Open"

        Click on "Oracle ODBC Drive 8.0.6.2.0" in the left window
        Click "Install"
        Click "Exit"

        Using windows explorer copy the following files:

            x:\applications\supported\oracle\sqlnet.ora
            x:\applications\supported\oracle\tnsnames.ora

        to:

            c:\orant\net80\admin

** Note, if this is the first time Oracle products have been installed on this
   computer (or you have changed the Oracle_Home location) then you may need
   to restart the computer. This will initialize some important environment
   variables.

You are now ready to use the oracle client install.

Note: A User ID: smarteam/testedge exists on the SLAC Oracle server for SmarTeam use.

SmarTeam Database Connection

5. Configure database connection using SmarTeam "BDE Administrator" found in Start/Programs/BDE Administrator

        1. See SmarTeam Administrator's Guide Appendix A "Creating a DatabaseAlias".
        2. Start Control Panel\BSD Administrator
        3. After the Database alias has been configured Save the configuration using Object\Save As Configuration
        4. Save as \\mdismp01\md\smarteam\slac_md.cfg
        5. Done

SmarTeam Vault Configuration

6. Configure the Vault Server for use at SLAC. The three default directories Checked In, Released and Obsolete can be placed on a remote NT Share.

        1. Assign Permissions for the Vault Service Users. See the SmarTeam Administrator's Guide (pg 5-10) for information on Assigning Permissions for the Vault Service Users
                This user must be the same as specified as the SmarTeam Server Installation Dialogue:Vault Server Service. Make sure you add users for all three Rights:
                1. Log on as service.
                2. Act as part of the operating system.
                3. Increase Quotas.

2. Make sure the SmarTeam Vault service is started by reviewing Control Panel\Services\SmarTeam Vault Service (Check values; Status:Started Started:Automatic)
Note: It may start but stop shortly after. If this happens it's probably because of licensing/HASP (dongle). Run LicenseDiagnostic.exe to review the licensing for any given HASP

        3. Enable Vault Logging. See the SmarTeam Administrator's Guide (pg 5-12) for information on creating a Vault log file. This will help you fix errors.
        4. Setup Default Vault Locations. Use ..\SmarTeam\Bin\VaultSetup.exe to set the location for the SmarTeam Vault directories. If no Default Vault is setup use ..\SmarTeam\Bin\VaultDefault.exe to setup a default fault location for Check In, Released, and Obsolete folders.
        5. Check that the Vault Service is running properly by running VaultTester.exe and VaultMonitor.exe located in the ..\SmarTeam\Bin folder.
                Note: If VaultTester.exe fails with an error stating... "Warning No: 01182, Failed to connect socket to "134.79.112.159" port 57353" This warning meams that the Vault Service is not started possibly because of permissions -or- because of the HASP (dongle).   Review log locate at ..\SmarTeam\Log\TdmVlSrv.log
                Note: If VaultTester.exe fails with an error stating.... "Error No: 00751, Internal operation code PUT FILE failed on the vault server. Please check the reason for this failure on vault server at "MDTDZ1.SLAC.Stanford.EDU" :( Failed to Copy file to 1st vault." This error probably means you need to add the Domain\User ID (MDCAD\mdcad-admin) or whoever owns the SmarTeam Vault Service for security permission on the Vault directories, Checked In, Released and Obsolete. See Dialogue:Vault Server Service in Server Install above and Assigning Permissions above.
                Note: If VaultTester.exe fails with an error stating.. ":( !!! Errors : Error No: 00751 Internal operation code GET VAULT MODE failed on the vault server. Please check the reason for this failure on vault server at "MDTDZ1.SLAC.Stanford.EDU". :( Failed to get security mode of 1st vault." This error may be because Vaults don't have ANY security mode by default, they must be set manually. Set the security mode of the vault by using Vault Server Setup utility to check and set the security mode as shown below.

High Security: No External Access, This means that the users can not see the files in the vault with utilities such as Windows Explorer. Files must be accessed through services provided by SmartVault
Medium Security: Read only external access. Users see the files stored in the vault using Windows Explorer, but can not modify them without using services provided by SmartVault.
Low Security: Read/Write access. A user can add new files to a vault, modify files that are in the vault and copy a file from a vault using external utilities..

6. Done.

Note: When attempting to delete Vaults from the Vault Server interface make sure no SmarTeam Projects/Documents are pointing to the vault you are trying to delete. Review this via Vault Maintenance by selecting each project one by one and reviewing the vaults that they point to.

SmarTeam Hasp (Dongle)

1. To check the validity of the hasp/dongle simply run ../SmarTeam/bin/LicenseDiagnostic.exe and select the "Detect" button.
2. We currently have 55 floating license and 1 Valult Server license.

Note: On Windows 2000 make sure the HASP Service (Protection Driver) is Version 3.14 (at least).
Also make sure the HASP Service has the "Recovery" set to...
"First Failure = Restart the Service"
"Second Failure = Restart the Service"
"Subsequent Failure = Restart the Service"

Msg regarding new license from SmarTeam....

-----Original Message-----
From: Kristen Lowd [mailto:KristenL@smarteam.com]
Sent: Wednesday, November 07, 2001 5:37 AM
To: Tankersley, Ricky
Subject: FW: Node Id 1490853612

Hi Rick,
Below is the new updated string. Please just copy and paste the string below into the license diagnostic.

Thanks and sorry for the delay,
Kristen

-----Original Message-----
From:   Susan Peretz
Sent:   Wednesday, November 07, 2001 5:12 AM
To:     Kristen Lowd
Subject:        Node Id 1490853612

Node id: 1490853612

License string code:

#4,F7C8,pblx,5D1F,exeS
F7C8,FabE,5C4A,S7e9

End user: Stanford University

PO number: SLAC-9497+0000021734

Options:

SmarTeam - 70
Vault Server - 1

Susan Peretz
Order & License Administrator

SmarTeam Corporation Ltd.
Phone: + 972-9-764-3968
Fax : + 972-9-764-4036
Email: susanp@smarteam.com

Server Customization

Oracle Tables

1. Use SmarTeam "SmartWizard" to modify the Demo SmarTeam database then create on the remote Oracle RDBMS.
Smart Wizard does it all, even deletes the old SmarTeam tables which may exist in Oracle.
Don't forget to save your new modified template for reuse. Review the ..\SmarTeam\SmartWizard.log for information on what SmartWizard does.

These are the mods possibe with SmartWizard... (see page 2-1 of the SmarTeam Admin guide)

    1. Creating and Defining Classes
    2. Defining Indexes and Class Attributes including Lookup Tables
    3. Defining General Links and Link Attributes
    4. Defining Tree Links and Link Attributes
    5. Defining Class Compostion
    6. Creating and Modifying Forms
    7. Finally create the SmarTeam Database Structure in Oracle. Note: SmartWizard should delete and existing SmarTeam tables.

Integration Tools Setup (required step)

1. Use SmarTeam Intergration Tools Setup to define Classes for Solid Edge and links from Solid Edge properties to SmarTeam tables.
    1. Select the Intergration Tools Setup utility and select database "SmartDB" use this as a template DB and recreate ALL the classes/links in another session of Intergration Tools Setup utility specifying your custom database on invocation. You must specify the "Supported component types" first and "Mapping group types" second.
    2. For "Supported component types" add class "Solid Edge Assembly" to "Solid Edge Assembly" and so forth for each module.
    3. Now create the link for the "Mapping group types" based on the default (SmartDB) data.

Note: This must be done when creating a database from a template.

Note: This Tool is also used to Map Default Solid Edge file properties to SmarTeam profile cards which then end up in the Oracle database.

SmarTeam Vault Configuration

2. Use SmarTeam "..\SmarTeam\Bin\VaultSetup.exe" to modify the location of the Vault directories. Create a new shared directory *under* the "DefaultVaultNode" when creating a new vault.

Note: The new vault location MUST BE shared with security permissions set at Full Control of the owner of the VaultServerService. The owner of the VaultServerService must also be validated through the SLAC domain therefore MDCAD-Admin is not a good choice because it's only good for the MDCAD domain and cannot be validated from the SLAC domain. To change the owner of the VaultServerService use: "SetServiceDependency -Install SLAC\vaillanc passwd". You may first need to uninstall the VaultServerService using "SetServiceDependency -UnInstall". See "Controlling the Vault Service" in the Admin Guide. To review who currently owns the VaultServerService simply run "SetServiceDependency.exe" and see the "Account Name" Text box at the bottom of the screen.

Note: Use "SmarTeam\Vault Maintainance" and use the Add button to change the location of the vaulted files. This will change the "Project ID" field from "*All*" to the current Project ID of the project.

SmarTeam User Adminstraton

3. Use the User Maintainence Utility to create new users and groups and also to assign/change passwords. Users can belong to more than 1 group.

Note: Create user ID's based on SLAC NT user ID's to take advantage of the onlogin.bs script that will use the current windows user ID to logon.
Note: Change the password for login "joe" just-in-case someone discovers it.

Administrator Options

4. Set the Administrator Options to the defaults suggested in the "Recommended Options for the SmarTeam System Administrator" .

Sequence Designer

5. Use Sequence Designer to modify the revision mask to "99.aa" which gives us 100 major revisions and 676 minor revisions per drawing. The revision mask MUST support major and minor versions.

Form Designer

6. Use Form Designer to modify ID mask for inherited attributes. Create sequences on the fly or before hand.

Solid Edge Mask info and Patterns.

Solid Edge Assembly

Assembly - SE-ASM-99999999
Part - SE-PAR-99999999
Draft - SE-DFT-99999999
Sheetmetal - SE-PSM-99999999

SmarTeam.ini Edits:
1.

***********************************
Add:
Note: This is from V4 SP3 upgrade text

[Solid Edge]
OutOfProcess=YES

***********************************

***********************************
From an email to SmarTeam users;

Hello all SmarTeam users and partners,

We have recently found out that using TRACE feature in SmarTeam 4.x dramatically slows down the system.

SmarTeam recommends switching TRACE_LEVEL to NOTRACE value. Please verify and, if necessary, update in SmarTeam 32.ini file as follows:

>> [Trace]
>> DSPL_ERROR_TRACE=NO
>> TRACE_LEVEL=NOTRACE
>> PRINT_TRACE_LEVEL=NOTRACE

Please, be sure that everybody using SmarTeam receives this information.

Thanks!

Best Regards,
Helena

Helena Klement
Inside Sales Representative
SmarTeam, Inc.
900 Cummings Center, Suite 307T
Beverly, MA 01915
Phone: (978) 524-1950 x 2030
Fax: (978) 524-1951
helenak@smarteam.com

************************************

Server Installation Repair

1. Add/Remove Programs on the server
2. Place the SmarTeam CD in CD-ROM drive
Note: Use the external CD-ROM on mdtdz1

Dialogue:Welcome, Modify, Repair or Remove the program
Choose "Repair".

Dialogue:Repair Installation Components
Choose "Database and Demo Files".

Smarteam Client Installation V4.0.4 07/18/01

1. Begin installation from CD-ROM.

Note: All menu picks are usually the defult but I have identified several key ones below.

Note: DO NOT install SmartEdge. Install SmarTeam as shown below.

    Install may require a change of Registry Key Entry for NT OS Service Pack Data.
    If Service Pack data includes a character appended to a number you may need to remove the character, Ex; "Service Pack 6a" must be changed to "Service Pack 6"
    Change Reg Key...
    \HKLM\SOFTWARE\Microsoft\Windows NT\CSDVersion.

Installing Microstation Client

When installing the Microstation Client for V8 you need to have some V7 Registry entries available for installation.

To create the registry entry…

HKLM\SOFTWARE\Bentley\Microstation\07.00\Version = 07.00.00.00 (Type REG_SZ)

Double click \\mdismp01\md\smarteam\client_mods\microstation_v7_registry_entry.reg

This (*.reg) file will add the required registry entry for installation.

Check to make sure Solid Edge Tools/Add-Ins is functioning properly. If it is not, you must reinstall Solid Edge.

Don't forget to login as Administrator before installation.

SmarTeam Service Packs/Patches

2. Install Smarteam Patches as per Server Install

Net8 (SQL*Net) & SQL*Plus Install

3. Install SQL*Net and SQL*Plus as per Server Install

Load Config using BSD Amdinistrator

4. Use BSD Amdministrator to load configuration created during Server Install/Configuration

    1. Start Control Panel\BSD Administrator
    2. Object\Open Configuration
    3. Browse to \\mdismp01\md\smarteam\slac_md.cfg or config file saved from Server Install/Configuration
    4. Start SmarTeam locally and and Add Database SLAC_MD.SMARTEAM
    5. Done.

Scripts and Local Changes

5. Copy the N:\smarteam\client_mods\smarteam32.ini to C:\Program Files\SmarTeam\Local Config and replace the existing one.

List of changes to Client_mod SmarTeam.ini file....

                    1. >>[Trace]
                        >>DSPL_ERROR_TRACE=NO
                        >>TRACE_LEVEL=NOTRACE
                        >>PRINT_TRACE_LEVEL=NOTRACE

2. >>[Directory Structure]
>>ScriptDirectory=n:\smarteam\script

3. >>[Solid Edge]
>>OutOfProcess=YES

                    4. >>[General Preferences]
                        >>#A new entry defining authorization for deleting an object can be added to the General Preferences section.
                        >>#When set to YES, only an object's owner or a user with administration privileges can delete a new object.
                        >>OwnerObjectAuthorizationForDelete=YES

                    5. >>[SolidEdge]
                        >>#The LinkAllToMainClass will link ALL documents to the select Project class and override the checkbox.
                        >>LinkAllToMainClass=YES

                    6. >>[VirtualFiles]
                        >>#Also copy the Weldment template (.pwd) to SmarTeam\Initfile\SEPWD1.PWD
                        >>Solid Edge Weldment=SEPWD1.PWD

Note: The onlogin.bs script in the N:\smarteam\script location is the functional script whereas the server side onlogin.bs must DO NOTHING. Otherwise you can't login to SmarTeam server apps.

2. Admin must put the "OnViewer.bs" script in the N:\smarteam\script folder for the SmarTeam embedded viewer (Solid Edge Smartview) to function properly in the SmarTeam environment.

Tree Properties

Set Tree properties as shown below... (Add "Filename" and set seperator to " : ")

Smarteam at SLAC

Admin Functions:

1. Full control of all aspects of SmarTeam.

Document Control Functions:

1. Release CAD ducuments after checking.

2. Obsolete CAD documents.

3. Create Projects for Documents assign part numbers.

User Functions:

1. Check-In, Check-Out documnets

2. Create New documents

3. Approve Documents

Approver Functions:

1. Approve Documents

Viewer Functions:

1. View Documents

2. Copy documents to local workstation

SmarTeam user ID should be the same as SLAC windows ID to use onlogin.bs script.

Use Of Smarteam....

1. When Checking-In Solid Edge documents, the Solid Edge document MUST be Checked-In from the same directory that it was Checked-Out to. i.e; if you move the file after Check-Out-it will create a new document object in SmarTeam for the Checked-In Solid Edge file.

2. The Solid Edge Revision property only updates on Check-In. It is NEVER driven from the Solid Edge revision number.

3. The location of the Check-Out directory is stored in the SmTeam23.ini file.

4. When checking out Solid Edge documents the directory structure for a hierarchical assembly is NOT created based on the CAD Directory attribute. Currently seeking solution from SmarTeam.

Questions for Admin Training....

1. How do I add Weldment to Integration Setup?