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. Procedure The system administrator exports the public key from the database with the install_datasharekeys utility by running the following from a Teamcenter command prompt: Copy 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. 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). Place the setup.exe file and the keys.zip file into a temporary directory. On a Windows system, run the iexpress command from a command prompt. The IExpress wizard runs. In the Welcome to IExpress 2.0 dialog box, select Create new Self Extraction Directive file and click Next. In the Package purpose dialog box, select Extract files and run an installation command and click Next. In the Package title dialog box, type a title for the installer (such as Datashare Manager Installation) and click Next. In the Confirmation prompt dialog box, select No prompt and click Next. In the License agreement dialog box, select Do not display a license and click Next. 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. In the Install Program to Launch dialog box, select setup.exe and click Next. In the Show window dialog box, select Default and click Next. In the Finished message dialog box, select No message and click Next. 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. In the Configure restart dialog box, select No restart and click Next. 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. In the Create package dialog box, click Next. The installation package file is created. 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. 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.