Installation TDPS and TADS

Post Installation Steps
  1. Make sure the IIS role is installed with the ISAPI supporting module included
  2. Unzip and install the Target installer (we usually ship a big .exe file and relatively small .msi file.
    The .exe must be installed only once, but .msi is installed on each update).
  3. Have the Customer Key and register the Target components
  4. Create a folder where the web application will be published to.
  5. In the IIS management, verify the following is configured by the installation procedure:
    • ISAPI and CGI Restrictions - WebAgent.dll is in the list
    • MIME types - .stt and .stp types are in the list
    • Handler Mappings - *.stt and *.stp both mapped to WebAgent.dll
    • Application Pools - the pool called "Target" is created. This application pool is created for testing purposes only.  It is a good practice to create an individual web pool for each web application.
  6. If necessary, create a new web site, that is, create a unique binding by choosing a unique name or port for the web site or web application, then point it to the created publish physical folder
  7. If the web application is designed to communicate to the SQL server in the trusted mode (Windows authentication), choose an user to the application pool be authenticated as.
  8. For 64 bit OS, for each new application pool, go to its "Advanced Settings" and turn on the "Enable 32-Bit Applications" option.

These steps allow the Target Suite components to run without elevated rights: 

  1. Add full writing rights to the group Users to the following registry key: (HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SimX_Target) 
  2. Open PortalDesigner, go to the Deploy dialog, click "Apply". The file PProfile.tmp should have been created in the Target installation folder. 
  3. Locate the file and add the write permission to the group Users
  4. Add writing permission to the “Users” group to the file “localhost.rpl”