### Configure Portrait Shared Server (PSS) - Initial Setup using PowerShell Source: https://customer.precisely.com/s/article/How-to-install-Portrait-Interaction-Optimizer-and-or-Portrait-Dialogue-version-6-1-using-the-PowerShell-scripts_language=en_US Performs the initial configuration of Portrait Shared Server (PSS), including database creation and website setup. Requires database connection details, server names, and web application pool account information. Runs using Portrait PowerShell. ```powershell .\PSS\ConfigurePortraitHQ.ps1 -CreateDatabases $true -SetupDatabaseConnection $true -IntegratedSecurity $true -DBServerName 'supportsql12' -DWDatabaseName 'VMSuite61_DW' -PSRDatabaseName 'VMSuite61_PSR' -DBAccessUsername 'pbi\portraittest' -CreateWebsites $true -PSSWebAppPoolAccountDomain 'pbi' -PSSWebAppPoolAccountName 'portraittest' -PSSWebAppPoolAccountPassword 'XXXXXXXX' ``` -------------------------------- ### Install Portrait Foundation using PowerShell Source: https://customer.precisely.com/s/article/How-to-install-Portrait-Interaction-Optimizer-and-or-Portrait-Dialogue-version-6-1-using-the-Pow_f4adb2_n-Optimizer-and-or-Portrait-Dialogue-version-6-1-using-the-PowerShell-scripts%3Flanguage%3Den_US Installs the Portrait Foundation component. Requires specifying installation locations, database details, and implementation script paths. Ensure the correct database server and name are provided. ```powershell . FDN\InstallPortraitFoundation.ps1 -FDNInstallLocation 'E:\Foundation Media\Software\Installsets\Core_Software' -FDNInstallDirectory 'C:\Program Files (x86)\PST\Portrait Foundation\' -DBSetupLocation 'E:\Foundation Media\Software\Installsets\Database' -DBServername supportsql12 -DBName VMSuite61_Fdn -DBType N -ImplementationScriptLocation 'E:\Installation\Foundation Database Scripts' -ImplementationDescription 'IO v5.6' ``` -------------------------------- ### Run deploy-client script Source: https://customer.precisely.com/s/article/Using-override-properties-to-modify-product-configuration-360036632714 This snippet provides an example of the command-line syntax for the deploy-client script, used to apply changes made to Assure Client properties. The script is typically located in the client installation's bin directory. ```bash ./deploy-client.sh -c JVM1 IA ``` -------------------------------- ### Get Automate Studio Product GUID (WMIC - for 24.0+) Source: https://customer.precisely.com/s/article/Automate-Studio-Troubleshooting-steps-to-Uninstall-and-reinstall-Automate-Winshuttle-Studio-when_language=en_US This command retrieves the product GUID for Automate Studio using WMIC, applicable for versions 24.0 and onwards. This GUID is necessary for the uninstallation process. ```bash wmic product where name='Automate studio' get IdentifyingNumber ``` -------------------------------- ### Manually Launch Studio Installer with Specific Language Source: https://customer.precisely.com/s/article/Studio-Installers-will-be-launched-in-localized-languages-only-for-globally-used-localized-formats-4836223552667_language=en_US This section provides command-line instructions for manually launching Studio installers with a specific language code. It covers both MSI and EXE installation types. Users need to replace placeholders with their actual installer name and the desired language code. ```bash msiexec /I __ ProductLanguage=__ msiexec /I __ ProductLanguage=__ ``` ```bash __ /L __ ``` -------------------------------- ### Get Winshuttle Studio Product GUID (WMIC - for 20.x) Source: https://customer.precisely.com/s/article/Automate-Studio-Troubleshooting-steps-to-Uninstall-and-reinstall-Automate-Winshuttle-Studio-when_language=en_US This command retrieves the unique product identifier (GUID) for Winshuttle Studio using WMIC, required for manual uninstallation. This method is applicable for versions 20.x. ```bash wmic product where name='Winshuttle studio' get IdentifyingNumber ``` -------------------------------- ### Get Winshuttle Studio Product GUID (PowerShell - for 20.x) Source: https://customer.precisely.com/s/article/Automate-Studio-Troubleshooting-steps-to-Uninstall-and-reinstall-Automate-Winshuttle-Studio-when_language=en_US This PowerShell command fetches the product GUID for Winshuttle Studio when WMIC is not available. It uses Get-CimInstance to query WMI for product information and is intended for versions 20.x. ```powershell powershell -NoProfile -Command "Get-CimInstance Win32_Product -Filter 'Name=\'Winshuttle studio\'' | Select-Object -ExpandProperty IdentifyingNumber" ``` -------------------------------- ### Get Automate Studio Product GUID (PowerShell - for 24.0+) Source: https://customer.precisely.com/s/article/Automate-Studio-Troubleshooting-steps-to-Uninstall-and-reinstall-Automate-Winshuttle-Studio-when_language=en_US This PowerShell command is used to obtain the product GUID for Automate Studio when WMIC is unavailable, specifically for versions 24.0 and later. It leverages Get-CimInstance for product information retrieval. ```powershell powershell -NoProfile -Command "Get-CimInstance Win32_Product -Filter 'Name=\'Automate studio\'' | Select-Object -ExpandProperty IdentifyingNumber" ``` -------------------------------- ### SAP Start Commands Source: https://customer.precisely.com/s/article/Application-replication-SAPF69FD45E_language=en_US Details the commands required to start an SAP instance. This includes calling an initialization program, starting the SAP kernel, and then initiating the SAP system start. ```shell > - CALL PGM(R3 xxx PGM/R3INLPGM) > - APYR3KRN SID( xxx ) > - STARTSAP SID( xxx ) INSTANCE(30) ``` -------------------------------- ### Start/Stop Infogix JVM via Command Line (Windows/Linux) Source: https://customer.precisely.com/s/article/How-to-start-and-stop-the-Assure-Insight-Perceive-and-ER-JVM-360020319914_nocache=https%3A%2F%2F_5d627d_e%2FHow-to-start-and-stop-the-Assure-Insight-Perceive-and-ER-JVM-360020319914%3Flanguage%3Den_US This snippet demonstrates how to start or stop the Infogix JVM using command-line scripts. Navigate to the WildFly bin directory and execute the appropriate start or stop script for your configuration. For example, 'startIA.bat' or 'stopIA.bat' for the Assure configuration named 'IA'. ```Shell cd /Infogix/Wildfly/bin ./start.sh ./stop.sh ``` ```Batch cd \Infogix\Wildfly\bin start.bat stop.bat ``` -------------------------------- ### Get Winshuttle Studio Product GUID (WMIC/PowerShell) Source: https://customer.precisely.com/s/article/Automate-Studio-Troubleshooting-steps-to-Uninstall-and-reinstall-Automate-Winshuttle-Studio-when This command retrieves the unique Product GUID for Winshuttle Studio, necessary for uninstallation. It first checks for WMIC availability and falls back to PowerShell if WMIC is not present. This command is applicable for versions 20.x. ```batch @echo off REM Check if WMIC is available where wmic >nul 2>nul if %errorlevel% == 0 ( REM WMIC is present, use it to get the GUID echo WMIC is available. Getting Product GUID for Winshuttle Studio... wmic product where name='Winshuttle studio' get IdentifyingNumber ) else ( REM WMIC is not present, use PowerShell echo WMIC not found. Using PowerShell to get Product GUID for Winshuttle Studio... powershell -NoProfile -Command "Get-CimInstance Win32_Product -Filter 'Name=''Winshuttle studio''' | Select-Object -ExpandProperty IdentifyingNumber" ) echo. ``` -------------------------------- ### Get Automate Studio Product GUID (WMIC/PowerShell) Source: https://customer.precisely.com/s/article/Automate-Studio-Troubleshooting-steps-to-Uninstall-and-reinstall-Automate-Winshuttle-Studio-when This command retrieves the unique Product GUID for Automate Studio, necessary for uninstallation. It first checks for WMIC availability and falls back to PowerShell if WMIC is not present. This command is applicable for versions 24.0 and onwards. ```batch @echo off REM Check if WMIC is available where wmic >nul 2>nul if %errorlevel% == 0 ( REM WMIC is present, use it to get the GUID echo WMIC is available. Getting Product GUID for Automate Studio... wmic product where name='Automate studio' get IdentifyingNumber ) else ( REM WMIC is not present, use PowerShell echo WMIC not found. Using PowerShell to get Product GUID for Automate Studio... powershell -NoProfile -Command "Get-CimInstance Win32_Product -Filter 'Name=''Automate studio''' | Select-Object -ExpandProperty IdentifyingNumber" ) echo. ``` -------------------------------- ### Example Environment Variable Setup Source: https://customer.precisely.com/s/article/Resolving-error-Can-t-find-entry-for-aixterm-in-PBMSPRTS-etc-a-termcap-error-when-running-instal_907a0c_-running-installdb-to-install-a-database-using-MailStream-Plus-or-CODE-1-Plus%3Flanguage%3Den_US These examples show how the PBMSP or PBC1P environment variables, which define the runtime system path, might be set. The error occurs when the installdb command cannot locate the a_termcap file using the path defined by these variables. ```shell PBMSP="/pb/msn/rts"; export PBMSP or PBC1P="/pb/c1p/rts"; export PBC1P ``` -------------------------------- ### Get Winshuttle Studio Product GUID using WMIC or PowerShell Source: https://customer.precisely.com/s/article/Automate-Studio-Troubleshooting-steps-to-Uninstall-and-reinstall-Automate-Winshuttle-Studio-when_2d7aab_ubleshooting-steps-to-Uninstall-and-reinstall-Automate-Winshuttle-Studio-when%3Flanguage%3Den_US This code snippet provides methods to retrieve the unique Product GUID for Winshuttle Studio, essential for uninstallation. It includes fallback logic using PowerShell if WMIC is not available. This is applicable for versions 20.x. ```batch :: Check for WMIC availability where wmic :: If WMIC is present, get the Product GUID wmic product where name='Winshuttle studio' get IdentifyingNumber :: If WMIC is not present, use PowerShell powershell -NoProfile -Command "Get-CimInstance Win32_Product -Filter 'Name=''Winshuttle studio''' | Select-Object -ExpandProperty IdentifyingNumber" ``` -------------------------------- ### Site.prop Configuration Example Source: https://customer.precisely.com/s/article/Data360-Analyze-prop-files-explained This snippet illustrates a typical site.prop file, located in the installation directory, which defines core application settings. It includes properties for installation paths, architecture, data directories, and license locations. It also includes include statements for other property files like ls.prop and cust.prop. ```properties ls.home="" lS.arch="" lS.brain.node.java.javaExtDirs=("") lS.appDataDir="" lS.dataDir=""include "${ls.home}/conf/ls.prop" lS.brain.server.licensePath="${ls.appDataDir}/conf" lS.brain.machineName="" lS.brain.server.host="*UNDEFINED*" lS.brain.ioMethod="file" lS.brain.tempDir="" lS.brain.logDir="" lS.desktop.install=false lS.lae.security.secureStorePath="" lS.brain.server.logDir="${ls.brain.logDir}" include "${ls.appDataDir}/conf/cust.prop" lS.brain.drone.executor.binary.extensionHandler.py="${ls.home}/platform/${ls.arch}/python/python.exe" ```