I would like Batch Export and Import Tools to support IWA (without having to use a profile).
Development has created a new custom-made SAS application to install in Production environment.
They have created a PowerShell script InstallApp.ps1 that executes all required deployment steps, like create backup, execute SAS scripts, import SAS packages, validate successful installation
InstallApp.ps1 uses SAS Batch Export Tool to make backup to SAS Package file of SAS content.
InstallApp.ps1 uses SAS Batch Import Tool to import new SAS content from SAS Package file.
Because Development does know who will deploy the SAS packages into production, they do not know what SAS profiles that person has defined on his system so
they cannot use the -profile option of ExportPackage.exe and ImportPackage.exe.
They also don't know the password of the person that will deploy the package and having InstallApp.ps1 prompt for a password is found insecure and error-prone.
Because ExportPackage.exe and ImportPackage.exe supports IWA, Development can use the -iwa option in InstallApp.ps1 as follows:
ImportPackage.exe -host metaserver -port 8561 -iwa -package "c:\rfc\newapp.spk" -target "/"
which allows ImportPackage.exe to log on to metadata server with the person's Windows account, which works for everyone that could install the new SAS application
(and has sufficient permissions).
You should provide some details about what IWA may mean. There are entirely too many TLAs (Three Letter Acronyms) in the computer world.
definitely a useful feature to have. Automated build / deployment is a must have in a modern development context. Without this, promotions are just slow and error prone and overall simply results in less stuff being built in SAS.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.