SIEMENS

Teamcenter 12.2

Data Share Manager

PLM00572 • 12.2
Contents

Introduction to the Data Share Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Exporting a public key for the data share manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Install the Data Share Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Data Share Manager installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Install the Data Share Manager with the stand-alone installer . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Bundle keys with the Windows stand-alone installer for the Data Share Manager . . . . . . . . . . . 3-4
Uninstall the Data Share Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Control file uploads and downloads with the Data Share Manager . . . . . . . . . . . . . . . . . . 4-1

Import a Data Share Manager private key into a new database . . . . . . . . . . . . . . . . . . . . . 5-1

Import a Data Share Manager private key into an existing database . . . . . . . . . . . . . . . . . 6-1

Considerations for using the Data Share Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Configure PKI for the Data Share Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Determining what is wrong . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
SQL exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Importing a briefcase file in Teamcenter fails after migration . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Saving or synchronizing a briefcase fails after adding non-CAD attachments . . . . . . . . . . . . . . A-2
Fixing an unhandled exception error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Running 64-bit Teamcenter applications on the same host . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Null pointer exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Causes of unexplained errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Fix license errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Date format mismatch causes an error message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
NX does not display a part when it is opened from Briefcase Browser . . . . . . . . . . . . . . . . . . A-4

Migrate a supplier site from a managed to unmanaged site . . . . . . . . . . . . . . . . . . . . . . . B-1

PLM00572 12.2 Data Share Manager 3

Chapter 1: Introduction to the Data Share Manager

The Data Share Manager allows end users to asynchronously upload and download files. It is
supported on the rich client. The Data Share Manager is a separate executable with its own user
interface. It allows users to view large file uploads and downloads and to manage them by pausing,
resuming, or canceling the processes.

The Data Share Manager can run on Windows, Linux, and Mac OS clients. On Windows machines,
the Data Share Manager resides in the system tray. To open the application, right-click the Data
Share Manager icon and select Restore Data Share Manager. (To close the Data Share
Manager, select Exit Data Share Manager.)

The Data Share Manager is initiated whenever you log on or start a file upload or download. For
example, in the rich client, right-click a dataset, choose Named References, and click the Upload or
Download buttons in the Named References dialog box.

PLM00572 12.2 Data Share Manager 1-1

 Chapter
Chapter 1: 1: Introduction
Introduction
to thetoData
the Data
ShareShare Manager
Manager

1-2 Data Share Manager PLM00572 12.2

Chapter 2: Exporting a public key for the data share manager

Data Share Manager must be installed with a public key that grants access to the Teamcenter
database. If this key has not been installed, users will receive the an error message stating "The Task
File "file-name.plmd" required the key file "key-file-name.x509", which was missing".
By default, each Teamcenter database contains a private/public key pair that validates Data Share
Manager clients accessing the database. Export and install the public key as follows.
1. Export the public key using the utility:
install_datasharekeys -u=username -p=password -g=dba -f=exp_pubkey

This exports a *.pem file and a *.x509 key file.

2. Zip the resulting *.x509 key file into a keys.zip file. (The .pem file is not needed in the ZIP file.)
Ensure the *.x509 file is in a \keys directory in the keys.zip file so it can be properly read by
installers.

3. If users need access to multiple databases from their client, export a public key for each database
and add it to the keys.zip file.

4. Distribute the keys.zip file to individuals who need to install the Data Share Manager.

PLM00572 12.2 Data Share Manager 2-1

Chapter 3: Install the Data Share Manager

Data Share Manager installation overview

The Data Share Manager can be installed on Windows, Linux, and Mac OS clients. It can be used
to manage file uploads and downloads for the rich client. Data Share Manager must be installed
if you require external site file virus scanning.

Note
If a client has a previous version of the Data Share Manager installed, uninstall the earlier
version before installing the new version of the Data Share Manager.

Follow this process to install the Data Share Manager:

1. End users cannot use the Data Share Manager unless the Data Share Manager has been
installed with a public key that grants access to the Teamcenter database.
The system administrator exports the public key from the database with the
install_datasharekeys utility by running the following from a Teamcenter command prompt:
install_datasharekeys -u=username -p=password -g=dba -f=exp_pubkey

The administrator zips the resulting *.x509 key file from the database into a keys.zip file (inside
a \keys subdirectory inside the ZIP file). The administrator then distributes the keys.zip file to
individuals who need to install the Data Share Manager.

2. The administrator can distribute the public keys in the following ways:
• keys.zip file
Distribute the keys.zip file to users and tell them to point to this file when they install the Data
Share Manager using the stand-alone installer.

• Individual key files

Distribute the *.x509 key files directly to end users and tell them to place the files into
their keys directory after installation using the stand-alone installer. For example, on a
Windows machine that uses the stand-alone installation, end users copy the key files to the
C:\Users\username\Siemens\dsmgr\dm\keys directory.

3. The system administrator sets the Use_DataShare_Manager preference to true on the server.
This activates the Data Share Manager for file uploading and downloading.

PLM00572 12.2 Data Share Manager 3-1

 Chapter
Chapter 3: 3: Install
Install the Data
the Data ShareShare Manager
Manager

Tip
If users do not want to use the Data Share Manager, they can set the
Use_Datashare_Manager preference to false with a User protection scope. Instead,
they use the synchronous import and export mechanism for file upload and download.

4. If the client has a previous version of the Data Share Manager installed, uninstall the earlier
version before installing the new version of the Data Share Manager.
Install the Data Share Manager using the stand-alone installer for your platform.

Install the Data Share Manager with the stand-alone installer

Use the stand-alone installer to install the Data Share Manager on individual client machines.
1. Ensure that the administrator has set the Use_DataShare_Manager preference to true on
the server.
If users do not want to use the Data Share Manager, they can set the Use_Datashare_Manager
preference to false with a User protection scope. Instead, they use the synchronous import and
export mechanism.

2. If your client has a previous version of the Data Share Manager installed, uninstall the earlier
version before installing the new version of the Data Share Manager.

3. Browse to the additional_applications\dsm_install folder in the Teamcenter installation source.

4. Run the installation file for your platform.

• Windows: setup.exe
By default, Data Share Manager is installed to be available to only the user installing Data
Share Manager. To have Data Share Manager available for all users on the workstation, run
setup.exe with the /v option and specify an installation directory. For example:
setup.exe /v "INSTALLDIR=c:\apps\dsm_all_users"

• Linux: install.bin

• Mac OS: install.bin

5. Follow the prompts in the installation wizard to install the Data Share Manager.
• On Windows, if your administrator has provided you with a public key file (keys.zip), the
wizard will use this key file automatically if it is stored in the same directory as setup.exe. If
the key file is not found in the same directory as setup.exe, the wizard will prompt you to
choose a security key file. If you know the key file location, check Enter Security Key File,
browse to the key file, and select the file. Leave Enter Security Key File unchecked if you
do not know the key file location. The key file can be installed after Data Share Manager is
installed.
On Linux and Mac OS systems, you have the option to choose either a Typical or a Custom
setup type. If your administrator has provided you with a public key file (keys.zip), the wizard

3-2 Data Share Manager PLM00572 12.2

 Install the Data Share Manager

will use this key file automatically if it is stored in the same directory as install.bin when you
select a Typical install set.

• If your administrator has provided you with individual *.x509 public key files, choose the
Complete setup type. (If choosing the Custom setup type, leave Enter Security Key File
unchecked.)
Copy the *.x509 public key files into the keys directory after installing the Data
Share Manager. For example, on a Windows machine, copy the key files to the
C:\Users\username\Siemens\dsmgr\dm\keys directory.

6. Once the installation wizard finishes, log off and log on again to complete installation.

After logon, the Data Share Manager icon is displayed in the system tray.

Handling possible installation errors

If a previous version of Data Share Manager was installed, you may encounter an error stating
the older version of Data Share Manager cannot be uninstalled. This is a known issue with
InstallAnywhere, the underlying installation program. Use the following steps as a workaround:
1. Navigate to the following directory:
(Windows): ProgramFiles\Zero G Registry
(UNIX)$HOME/

2. In that directory, locate the file .com.zerog.registry.xml. You may need to enable viewing hidden
files.

3. Create a backup copy of .com.zerog.registry.xml. The file may be required by other

InstallAnywhere-based installations, such as Teamcenter client communication system (TCCS).

4. In .com.zerog.registry.xml, use an ASCII editor to locate and remove the entries for Data
Share Manager and its components:
<product name="Data_Share_Manager" id="8ca639e8-1f16-11b2-8d72-974fa857b767"
upgrade_id="8ca639e8-1f16-11b2-8d72-974fa857b767" version="11.2.0.3"
copyright="2014" info_url="" support_url="" location="C:\Users\<userid>\
Siemens\dsmgr"
last_modified="2015-07-30 10:53:00">
<![CDATA[]]>
<vendor name="Siemens PLM Solutions" id="54cad4f2-1f16-11b2-bbc2-974fa857b767"
home_page="" email=""/>
<feature short_name="Application" name="Application"
last_modified="2015-07-30 10:53:00">
<![CDATA[This installs the application feature.]]>
<component ref_id="54cad522-1f16-11b2-bbef-974fa857b767" version="1.0.0.0"
location="C:\Users\<userid>\Siemens\dsmgr\
_Data_Share_Manager_installation\
Change Data_Share_Manager Installation.exe"/>
<component ref_id="54cad521-1f16-11b2-bbed-974fa857b767" version="1.0.0.0"
location="C:\Users\<userid>\Siemens\dsmgr\dm\com\teamcenter\fms\dlmgr\
ui\controls\dialogs.css"/>
</feature>
<feature short_name="Help" name="Help" last_modified="2015-07-30 10:53:00">

PLM00572 12.2 Data Share Manager 3-3

 Chapter
Chapter 3: 3: Install
Install the Data
the Data ShareShare Manager
Manager

<![CDATA[This installs the help feature.]]>

<component ref_id="54cad522-1f16-11b2-bbef-974fa857b767" version="1.0.0.0"
location="C:\Users\<userid>\Siemens\dsmgr\_Data_Share_Manager_installation\
Change Data_Share_Manager Installation.exe"/>
<component ref_id="54cad521-1f16-11b2-bbed-974fa857b767" version="1.0.0.0"
location="C:\Users\<userid>\Siemens\dsmgr\dm\com\teamcenter\fms\dlmgr\
ui\controls\dialogs.css"/>
</feature>
</product>

<component id="54cad522-1f16-11b2-bbef-974fa857b767" version="1.0.0.0"

name="InstallAnywhere Uninstall Component"
location="C:\Users\<userid>\Siemens\dsmgr\_Data_Share_Manager_installation\
Change Data_Share_Manager Installation.exe" vendor="Siemens PLM Solutions"/>

<component id="54cad521-1f16-11b2-bbed-974fa857b767" version="1.0.0.0"

name="Common" location="C:\Users\<userid>\Siemens\dsmgr\dm\com\teamcenter
\fms\dlmgr\ui\controls\dialogs.css" vendor="Siemens PLM Solutions"/>

5. Save .com.zerog.registry.xml.

6. Restart the installation file for your platform.

Bundle keys with the Windows stand-alone installer for the Data
Share Manager
Rather than provide a separate key file to end users, an administrator can bundle the key file with
the Windows-based Data Share Manager stand-alone installer. Then the keys are already included
when end users run the stand-alone installer.
1. The system administrator exports the public key from the database with the
install_datasharekeys utility by running the following from a Teamcenter command prompt:
install_datasharekeys -u=username -p=password -g=dba -f=exp_pubkey

The administrator zips the resulting *.x509 key file from the database into a keys.zip file. If users
need access to multiple databases from their client, the administrator must export a public key for
each database and add it to the keys.zip file.

Tip
The *.x509 files must be included in the keys.zip file in a \keys directory so they can
be properly read by installers.

2. Copy the Data Share Manager stand-alone installer setup.exe file from the directory where it is
located in the Teamcenter installation source (additional_applications\dsm_install).

3. Place the setup.exe file and the keys.zip file into a temporary directory.

4. On a Windows system, run the iexpress command from a command prompt.

The IExpress wizard runs.

3-4 Data Share Manager PLM00572 12.2

 Install the Data Share Manager

5. In the Welcome to IExpress 2.0 dialog box, select Create new Self Extraction Directive
file and click Next.

6. In the Package purpose dialog box, select Extract files and run an installation command
and click Next.

7. In the Package title dialog box, type a title for the installer (such as Datashare Manager
Installation) and click Next.

8. In the Confirmation prompt dialog box, select No prompt and click Next.

9. In the License agreement dialog box, select Do not display a license and click Next.

10. In the Packaged files dialog box, click Add button and select the setup.exe file and the keys.zip
file from the temporary directory location. Click Next.

11. In the Install Program to Launch dialog box, select setup.exe and click Next.

12. In the Show window dialog box, select Default and click Next.

PLM00572 12.2 Data Share Manager 3-5

 Chapter
Chapter 3: 3: Install
Install the Data
the Data ShareShare Manager
Manager

13. In the Finished message dialog box, select No message and click Next.

14. In the Package Name and Options dialog box, click the Browse button and select a temporary
directory where to place the installer. Name the installer file with a temporary name such as
myinstaller.exe. This is to differentiate it from the original setup.exe file. Click Next.

15. In the Configure restart dialog box, select No restart and click Next.

16. In the Save Self Extraction Directive dialog box, click the Browse button and select a temporary
directory where to place the installer directive file. Click Next.

17. In the Create package dialog box, click Next.

The install package file is created.

18. When you look in the temporary directory where the output files were placed, you should see two
new files, for example, myinstaller.EXE and myinstaller.SED.
If the original setup.exe file is in this directory, rename it to something different, such as
setup_original.exe. Then rename the packaged installer file (for example, myinstaller.EXE) to
setup.exe. This new setup.exe file contains the keys.zip file.

19. Distribute the new setup.exe file to end users. When they run the file to install the Data Share
Manager, the bundled keys.zip file is unzipped into the \keys directory.

3-6 Data Share Manager PLM00572 12.2

 Install the Data Share Manager

Uninstall the Data Share Manager

Note
You must first close the Data Share Manager to stop the Java process before uninstalling.
For example, on a Windows system, right-click the Data Share Manager icon and
choose Exit Data Share Manager. On a Linux system, click the close button (X) in
the upper-right corner of the Data Share Manager user interface and click Yes in the
confirmation dialog box.

The way you uninstall the Data Share Manager depends on how it was originally installed.
• Teamcenter Environment Manager (TEM)
o Windows systems
1. Use the Windows Task Manager to terminate the dsm.exe process.

2. Remove the Data Share Manager item from the Windows Start menu.

3. Delete the TC_ROOT\dm directory.

o UNIX or Linux systems

1. Use the kill -9 command to stop the dsm process.

2. Remove the DSM entries from $HOME/.mime types and $HOME/.mailcap.

3. Delete the TC_ROOT\dm directory.

• Stand-alone installer
Use this method for stand-alone installations.

1. Browse to the location where the Data Share Manager is installed. For example, on a
Windows machine, browse to C:\Users\username\Siemens\dsmgr\ directory.

2. In the _Data_Share_Manager_installation directory, run the Change Data_Share_Manager

Installation file.
The uninstall dialog box is displayed.

PLM00572 12.2 Data Share Manager 3-7

 Chapter
Chapter 3: 3: Install
Install the Data
the Data ShareShare Manager
Manager

3. Click Next.
The Data Share Manager is uninstalled.

4. Log off and log back on to complete the uninstallation.

3-8 Data Share Manager PLM00572 12.2

Chapter 4: Control file uploads and downloads with
the Data Share Manager

1. By default, the Data Share Manager is hidden until the first new transaction is launched, when
a tile view is displayed as shown.

Click the restore button in the upper left corner of the tile view to the expand the user
interface to its larger size.

You can return to the tile view by clicking the tile button in the upper right of the Data Share
Manager.
You can also open the Data Share Manager by selecting the Data Share Manager icon in the
system tray. For example, on a Windows system, right-click the Data Share Manager icon
and select Restore Data Share Manager. (To close the Data Share Manager, select Exit Data
Share Manager.)

2. Upload or download files to initiate the Data Share Manager.

PLM00572 12.2 Data Share Manager 4-1

 Chapter
Chapter 4: 4: Control
Control file uploads
file uploads and downloads
and downloads withData
with the the Data
ShareShare Manager
Manager

Example
• Right-click a checked-out dataset, choose Named References, and click the
Upload or Download buttons in the Named References dialog box.

• Create a dataset and click the Import button to upload a file.

3. View the file upload and download processes in the Data Share Manager.

4. Hover your mouse over the user interface to see the available actions.

4-2 Data Share Manager PLM00572 12.2

 Control file uploads and downloads with the Data Share Manager

5. If there is an upload or download error, it is displayed with an ! symbol. Click the arrow to see
the error message.

The following error means that this file was already downloaded and the duplicate record for this
file is already shown in the list. If you want to download the file again, you must first delete the

duplicate record for this file from the list by clicking .

6. Click a process to pause it. Click it again to resume the process.

PLM00572 12.2 Data Share Manager 4-3

 Chapter
Chapter 4: 4: Control
Control file uploads
file uploads and downloads
and downloads withData
with the the Data
ShareShare Manager
Manager

7. When you are done working with the Data Share Manager, close it.
• Windows
Right-click the Data Share Manager icon in the system tray and select Exit Data Share
Manager.

• Linux
Click the close button (X) in the upper right corner of the Data Share Manager user interface
and click Yes in the confirmation dialog box.

Note
If you are upgrading Teamcenter, you must first close the Data Share Manager to stop
the Java process before proceeding with upgrade.

4-4 Data Share Manager PLM00572 12.2

Chapter 5: Import a Data Share Manager private
key into a new database

When creating a database at installation or during upgrade, you have the option of importing a private
key into the database to be used for Data Share Manager key validation. This may be necessary if
you have previously distributed a public key to users and wish to import the corresponding private key
to the new database so that these same users can have access to the new database.
1. While creating a new database using Teamcenter Environment Manager (TEM), click the
Advanced button in the Foundation Database panel.

2. Select the Import Data Share PRIVATE Key check box and click the ... button to browse
to the location of the key.
The file should be a ZIP file that contains the private key file from another database previously
obtained by an administrator using the install_datasharekeys utility with the -exp_pvtkey
argument.

PLM00572 12.2 Data Share Manager 5-1

 Chapter
Chapter 5: 5: Import
Import a Data
a Data ShareShare Manager
Manager private
private key ainto
key into newa database
new database

3. Click OK to proceed with the installation.

5-2 Data Share Manager PLM00572 12.2

Chapter 6: Import a Data Share Manager private key
into an existing database

There is only one active private key in the system that is used by Teamcenter. To import a private
data share key to an already installed database, use the install_datasharekeys utility. This utility is
initially called by the Teamcenter installation process to install the predefined private key.
To use the same key for more than one database (for example, after installing test environments),
perform the following steps:
1. Export the private key from a database that already uses it (for example, the database that
generated it):
install_datasharekeys -u=username p=password -f=exp_pvtkey

This generates the private_keypairID.pem file.

Caution
Always keep the private key in a safe and secure place, inaccessible to unauthorized
parties, preferably away from the public key files.

2. Import (seed) the private key into each of the other already-installed databases:
install_datasharekeys -u=username -p=password -f=seed -f=private_keypairID.pem

private_keypairID.pem is the private key file exported from the master database in step 1.

Caution
Always keep the private key in a safe and secure place, inaccessible to unauthorized
parties, preferably away from the public key files.

3. Export the corresponding public key for distribution to the clients from any database that already
has the master private key installed (after step 1 or 2):
install_datasharekeys -u=username -p=password -f=exp_pubkey

This generates the public_keypairID.pem and public_keypairID.x509 public key files. The
public_keypairID.x509 public key file can be freely distributed to Data Share Manager clients.

PLM00572 12.2 Data Share Manager 6-1

Chapter 7: Considerations for using the Data Share Manager

Following are some considerations to keep in mind as you use the Data Share Manager:
• In the rich client, the Data Share Manager lets you upload multiple files of the same file type as
named references to a dataset object.

• If you are upgrading Teamcenter, you must first close the Data Share Manager to stop the Java
process before proceeding with upgrade.

PLM00572 12.2 Data Share Manager 7-1

Chapter 8: Configure PKI for the Data Share Manager

You can configure public key infrastructure (PKI) authentication for the Data Share Manager to
authenticate all uploads and downloads from the Data Share Manager to FMS volumes. This relies
on two-way SSL between the client (the Data Share Manager) and the server (FMS) and requires the
FMS system to be fronted by a reverse proxy configured with two-way SSL.
To enable PKI authentication for the Data Share Manager, open the
Data-Share-Manager-installed-location\dm\dm.properties file and set the
com.teamcenter.fms.servercache.ssl.enabled parameter to true. Setting only this value to true
without setting the keystore and truststore properties indicates that the certificates should be read
from the browser store. This is the recommended setting. (Setting the value to false disables the
authentication.) Setting the com.teamcenter.fms.servercache.ssl.enabled parameter to false (or
letting it default to false) may cause PKI-authenticated reverse proxy connections to fail.
After PKI authentication is enabled, configure the following properties to use file-based keystore or
truststore:
• com.teamcenter.fms.servercache.ssl.keystore=keystore.jks

• com.teamcenter.fms.servercache.ssl.keystorepassword=password

• com.teamcenter.fms.servercache.ssl.keystoretype=jks|pkcs12

• com.teamcenter.fms.servercache.ssl.truststore=truststore.jks

• com.teamcenter.fms.servercache.ssl.truststorepassword=password

• com.teamcenter.fms.servercache.ssl.truststoretype=jks

To allow self-signed certificates from untrusted parties, set the value of the
com.teamcenter.fms.servercache.ssl.allowuntrusted parameter to true.

Warning
Siemens PLM Software does not recommend using self-signed (untrusted) certificates.
This configuration is provided only for test purposes and should only be used if you are
confident in the identity of the FMS (reverse proxy) URL and the integrity of your connection.

PLM00572 12.2 Data Share Manager 8-1

Appendix A: Troubleshooting

Determining what is wrong

If you are unable to correct the problem with the information provided or you cannot find a topic related
to your problem, contact the Global Technical Access Center (GTAC). You can access GTAC at:
http://www.siemens.com/gtac
If you encounter:
• A failure while saving the briefcase in Briefcase Browser, see SQL exceptions.

• A failure while synchronizing or saving the briefcase in Briefcase Browser, see Saving or
synchronizing a briefcase fails after adding non-CAD attachments.

• An unhandled exception in Briefcase Browser, see Fixing an unhandled exception error.

• A failure when opening a CAD assembly from Briefcase Browser on a 64-bit operating system,
see Running 64-bit Teamcenter applications on the same host.

• A failure when using a menu option or a button in Briefcase Browser, see Null pointer exceptions.

• A failure when opening or saving a CAD assembly in Briefcase Browser when another CAD
product is installed on the same host as NX, see Causes of unexplained errors.

• A failure when opening a briefcase or CAD assembly when same briefcase/CAD assembly is
opened in another instance of Briefcase Browser.

• An error message when you start Briefcase Browser that indicates there is a problem with the
license, see Fix license errors.

• An error message when saving a briefcase file that contains new parts, see Title not found.

• An error message when opening or synchronizing a briefcase file on a non-English operating

system, see Date format mismatch causes an error message.

• NX does not launch when you double-click a part file in Briefcase Browser, see NX does not
display a part when it is opened from Briefcase Browser.

If your site:
• Has sent data to a Teamcenter (managed) site prior to using Briefcase Browser

• Is defined at the Teamcenter as an offline (managed) site

You must perform an unmanaged site migration for the previously sent data to avoid errors and
unexpected results.

PLM00572 12.2 Data Share Manager A-1

 Appendix
Appendix A: A: Troubleshooting
Troubleshooting

SQL exceptions
If you open and modify parts that were created or used in an earlier version of Briefcase Browser
(10.1 or earlier), from an existing working directory, an SQL exception may occur during the save
action. This happens when an update to the briefcase database contains new or modify attributes or
elements.
To avoid this, delete any existing folders with old database files (attributes.db and elements.db)
before opening the parts in a newer Briefcase Browser version.

Importing a briefcase file in Teamcenter fails after migration

After migrating Briefcase Browser to Teamcenter, while trying to export data from the migrated
Teamcenter to other site an error occurs.
To avoid this, you should set the opt_all_ds_vers option set value to true.

Saving or synchronizing a briefcase fails after adding non-CAD

attachments
If non-CAD attachments added to a part, either automatically following the naming convention, or
through Add Dataset dialog box, are deleted from the local instance, synchronize and save will
fail for the part.

Fixing an unhandled exception error

If the Briefcase Browser error log contains an error message similar to the following:
Unhandled event loop exception

A third-party tool may be hijacking the Java process environment.

To resolve this issue, remove the third-party tool or change the JAVA_ARGS or JAVA_OPTS
environment variable values to the Briefcase Browser required settings.

Running 64-bit Teamcenter applications on the same host

You can run a 64-bit Briefcase Browser and NX applications on a 64-bit operating system only.

Null pointer exceptions

Briefcase Browser is an Eclipse-based Java application. The Java Runtime Environment (JRE) must
be compatible with the Java version used to compile Briefcase Browser. For Teamcenter 10.1.3,
Briefcase Browser requires JRE 7 (Java 1.7 or higher).
If you encounter errors in Briefcase Browser, such as a null pointer exceptions, you may be running
an incompatible JRE version. Ensure that you have JRE 7 update 7 installed and its location is
in your PATH environment variable.

A-2 Data Share Manager PLM00572 12.2

 Troubleshooting

If the JRE version and PATH variable are correct ensure that you copied or extracted the JRE
contents into the directory that contains your Briefcase Browser application (BriefcaseBrowser.exe)
during the installation procedure.

Causes of unexplained errors

Unexplained errors are normally a configuration issue. Ensure that you have the UGII_ROOT_DIR,
UGII_BASE_DIR, and PATH environment variables set properly as described in the installation
instructions and that you have the JRE installed and configured.
JRE installed and configured
If you have another CAD product, such as Pro/ENGINEER, installed on the same host as your NX
application, add the UGII_ROOT_DIR environment variable to the front of the PATH environment
variable.

Fix license errors

Briefcase Browser supports a node locked license. This license is supplied through a license file that
you normally obtain from the Global Technical Access Center (GTAC):
http://www.siemens.com/gtac
If you have not renamed this file correctly and placed it in the proper location, Briefcase Browser
cannot connect to the license server:

Ensure that you have correctly performed the following steps during the installation procedure:
1. Obtain a Briefcase Browser license file from GTAC.

2. Rename the file bc_browser_license.lic.

3. Copy the license file to the desired-directory\BB\11.2.0\bbworkspace\configurations directory.

This file must contain specific content. If you get the following error when you start Briefcase Browser,
the license file does not contain the required bc_browsr_strt_lic module.

PLM00572 12.2 Data Share Manager A-3

 Appendix
Appendix A: A: Troubleshooting
Troubleshooting

For instructions on resolving this issue, contact GTAC.

Date format mismatch causes an error message

If you get an error message when you attempt to open or synchronize a briefcase file, ensure the
Format box in the Windows Region and Language dialog box is set to the local language of your
Briefcase Browser application or to US English. Otherwise, the date formats used do not match
and cause this error.

NX does not display a part when it is opened from Briefcase Browser

On systems where Teamcenter Integration for NX is installed, the .prt extension is associated with
Teamcenter Integration for NX. When you double-click a .prt file the operating system tries to open it in
Teamcenter Integration for NX. Because Teamcenter Integration for NX does not support opening local
files, it does not display the part. This behavior is retained even if have the NX application installed. If
you double-click a .prt file it launches NX but does not open the part file. Therefore, if you select an
NX part file in Briefcase Browser and click Launch NX, NX opens but does not display the part.
This is due to the Windows file associated for the .prt extension being set to the wrong program. You
must change the file association to open the file with NX.
Change the file association to use the following command to open part files in NX:
NX-installation-directory\UGII\ugs_router.exe" -ug -use_file_dir "%1

The instructions for changing the Windows default program used to open a file type are provided
for your operating system at:
http://windows.microsoft.com
To change this association in the Windows registry:
1. Start the registry editor by typing regedit in the start menu search box.

2. Choose Edit→Find, type ugs_router.exe in the Registry Editor Find dialog box, and select
the Key option.

3. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Classes\UGpartfile\shell\open\command.

4. For NX 11 or later, type NX-install-directory\UGII\ugs_router.exe" -ug -use_file_dir "%1".

5. For versions prior to NX 11, type NX-install-directory\nxbin\ugs_router.exe" -ug -use_file_dir

"%1".

A-4 Data Share Manager PLM00572 12.2

Appendix B: Migrate a supplier site from a managed
to unmanaged site

You can change a supplier site that has previously been defined as a managed site in Teamcenter to
an unmanaged site without causing any data errors for previously transferred data. This procedure
designates the site migrating to an unmanaged site as the supplier site and the OEM site as a
managed site.
1. At the supplier site, identify all assemblies that were sent to the OEM site.

2. Ensure that any shared data is not checked out to a remote site.

3. Create new revisions for all shared items:

a. Turn off the smart baseline feature by changing the value of the ITEM_smart_baseline
preference to 0.

b. At the supplier site, create a baseline of the supplier data that has been sent to the OEM site.

All new revisions occur in the migrated unmanaged site. Shared objects have multiple revisions,
and OEM replica parts are not baselined.

4. If the supplier site is a hub site, in the Organization application, clear the Is a Hub check box
for the supplier site.

5. At the supplier site, export all supplier owned objects to a briefcase file.
a. Choose Tools→Export→To Briefcase.

b. Select the unmanaged site and click the Display/Set remote export options button .

c. In the TIEConfiguredExportDefault dialog box, select the Replica Bypass check box.

PLM00572 12.2 Data Share Manager B-1

 Appendix
Appendix B: B: Migrate
Migrate a supplier
a supplier site from
site from a managed
a managed to unmanaged
to unmanaged site site

Note
You may have to scroll down to access the check box.

6. Export all baseline assemblies for migration. This includes:

• New baseline assemblies that were previously sent.

• Supplier-owned data.

• OEM replica data that must be preserved.

7. Install Briefcase Browser at the supplier site being migrated using the same site ID as the
managed site for the unmanaged site.

8. In Briefcase Browser, extract all briefcase files in the migration working directory.

9. Confirm the briefcase files extracted meet the OEM requirements.

Notify the Teamcenter administrator at the OEM site that the briefcase file output is as expected.

B-2 Data Share Manager PLM00572 12.2

 Migrate a supplier site from a managed to unmanaged site

10. In the Organization application at the OEM site, modify the previously managed supplier site by
selecting the Unmanaged option for the site.

11. At the unmanaged supplier site, use Briefcase Browser to add parts to new assemblies. You can
copy the required .prt files to a new working directory and create briefcase files based on them.

12. Transfer briefcase files to the OEM and import them into Teamcenter using Tools→Import→From
Briefcase.

PLM00572 12.2 Data Share Manager B-3

Siemens Industry Software

Headquarters
Europe
Granite Park One
Stephenson House
5800 Granite Parkway
Sir William Siemens Square
Suite 600
Frimley, Camberley
Plano, TX 75024
Surrey, GU16 8QD
USA
+44 (0) 1276 413200
+1 972 987 3000

Asia-Pacific
Americas
Suites 4301-4302, 43/F
Granite Park One
AIA Kowloon Tower, Landmark East
5800 Granite Parkway
100 How Ming Street
Suite 600
Kwun Tong, Kowloon
Plano, TX 75024
Hong Kong
USA
+852 2230 3308
+1 314 264 8499

About Siemens PLM Software

© 2019 Siemens Product Lifecycle Management

Siemens PLM Software, a business unit of the Siemens
Software Inc. Siemens and the Siemens logo are
Industry Automation Division, is a leading global provider
registered trademarks of Siemens AG. D-Cubed,
of product lifecycle management (PLM) software and
Femap, Geolus, GO PLM, I-deas, Insight, JT, NX,
services with 7 million licensed seats and 71,000 customers
Parasolid, Solid Edge, Teamcenter, Tecnomatix and
worldwide. Headquartered in Plano, Texas, Siemens
Velocity Series are trademarks or registered trademarks
PLM Software works collaboratively with companies
of Siemens Product Lifecycle Management Software
to deliver open solutions that help them turn more
Inc. or its subsidiaries in the United States and in other
ideas into successful products. For more information
countries. All other trademarks, registered trademarks
on Siemens PLM Software products and services, visit
or service marks belong to their respective holders.
www.siemens.com/plm.