Downloads:
13,434
Downloads of v 2016.1.2-beta2:
412
Last Update:
30 Nov 2015
Package Maintainer(s):
Software Author(s):
- Pragmatic Works Software
Tags:
admin bixpress dbaxpress docxpress documentation excel hive inspect lineage monitoring oracle pragmaticworks salesforce sharepoint sql ssas ssis ssrs surfWorkbench Server
This is a prerelease version of Workbench Server.
- 1
- 2
- 3
2016.1.2-beta2 | Updated: 30 Nov 2015
Downloads:
13,434
Downloads of v 2016.1.2-beta2:
412
Maintainer(s):
Software Author(s):
- Pragmatic Works Software
Workbench Server 2016.1.2-beta2
This is a prerelease version of Workbench Server.
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Pragmatic Works Software. The inclusion of Pragmatic Works Software trademark(s), if any, upon this webpage is solely to identify Pragmatic Works Software goods or services and not for commercial purposes.
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
Validation Testing Unknown
Verification Testing Pending
Scan Testing Successful:
No detections found in any package files
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Workbench Server, run the following command from the command line or from PowerShell:
To upgrade Workbench Server, run the following command from the command line or from PowerShell:
To uninstall Workbench Server, run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download pragmaticworksworkbenchserver --internalize --version=2016.1.2-beta2 --pre --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade pragmaticworksworkbenchserver -y --source="'INTERNAL REPO URL'" --version="'2016.1.2-beta2'" --prerelease [other options]
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade pragmaticworksworkbenchserver -y --source="'INTERNAL REPO URL'" --version="'2016.1.2-beta2'" --prerelease
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install pragmaticworksworkbenchserver
win_chocolatey:
name: pragmaticworksworkbenchserver
version: '2016.1.2-beta2'
source: INTERNAL REPO URL
state: present
allow_prerelease: yes
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'pragmaticworksworkbenchserver' do
action :install
source 'INTERNAL REPO URL'
version '2016.1.2-beta2'
options '--prerelease'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller pragmaticworksworkbenchserver
{
Name = "pragmaticworksworkbenchserver"
Version = "2016.1.2-beta2"
Source = "INTERNAL REPO URL"
chocoParams = "--prerelease"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'pragmaticworksworkbenchserver':
ensure => '2016.1.2-beta2',
install_options => ['--prerelease'],
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
This package is exempt from moderation. While it is likely safe for you, there is more risk involved.
Workbench Server
----------
BI xPress Server, DOC xPress Server, and LegiTest Server are all included in this package, our three powerhouse team focused products. All of the included products come with a 14-day full featured trial or enter your product key for total access (separate download is not needed).
### BI xPress Server ###
BI xPress Server allows your team to apply the Auditing Framework using unified settings and to monitor your SSIS packages in your web browser and on your mobile device. See more about BI xPress Server at https://www.pragmaticworks.com/Products/Bi-xPress.
### DOC xPress Server ###
DOC xPress Server brings the metadata capabilities to a web browser, making it much easier to share documentation, lineage, and data dictionary information with your team. Generate documentation (PDF, CHM, and web pages) for SQL Server, SSAS, SSIS, SSRS, Excel, Oracle, Hive and much more with DOC xPress Server. See more about DOC xPress Server at https://www.pragmaticworks.com/Products/Doc-xPress.
### LegiTest Server ###
LegiTest Server shows your team the health of your data-centric testing over time. View the test run results in a web browser and take action if a test doesn't pass. Your team can also re-run the test(s) from within a web browser to verify results. A test suite can also be run on a schedule so you know your data-centric applications are tested constantly. See more about LegiTest Server at https://www.pragmaticworks.com/Products/LegiTest.
# IMPORTANT: Before releasing this package, copy/paste the next 2 lines into PowerShell to remove all comments from this file:
# $f='c:\path\to\thisFile.ps1'
# gc $f | ? {$_ -notmatch "^\s*#"} | % {$_ -replace '(^.*?)\s*?[^``]#.*','$1'} | Out-File $f+".~" -en utf8; mv -fo $f+".~" $f
# If this is an MSI, cleaning up comments is all you need.
# If this is an exe, change installerType and silentArgs
# Auto Uninstaller should be able to detect and handle registry uninstalls (if it is turned on, it is in preview for 0.9.9).
$ErrorActionPreference = 'Stop'; # stop on all errors
$packageName = 'pragmaticworksworkbenchserver'
$softwareName = 'Workbench Server*' #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique
$installerType = 'EXE'
$silentArgs = '/qn /norestart'
# https://msdn.microsoft.com/en-us/library/aa376931(v=vs.85).aspx
$validExitCodes = @(0, 3010, 1605, 1614, 1641)
if ($installerType -ne 'MSI') {
# The below is somewhat naive and built for EXE installers
# Uncomment matching EXE type (sorted by most to least common)
#$silentArgs = '/S' # NSIS
#$silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-' # Inno Setup
#$silentArgs = '/s' # InstallShield
#$silentArgs = '/s /v"/qn"' # InstallShield with MSI
#$silentArgs = '/s' # Wise InstallMaster
#$silentArgs = '-s' # Squirrel
#$silentArgs = '-q' # Install4j
#$silentArgs = '-s -u' # Ghost
# Note that some installers, in addition to the silentArgs above, may also need assistance of AHK to achieve silence.
#$silentArgs = '' # none; make silent with input macro script like AutoHotKey (AHK)
# https://chocolatey.org/packages/autohotkey.portable
#$validExitCodes = @(0)
}
$uninstalled = $false
$local_key = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key6432 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*'
$key = Get-ItemProperty -Path @($machine_key6432,$machine_key, $local_key) `
-ErrorAction SilentlyContinue `
| ? { $_.DisplayName -like "$softwareName" }
if ($key.Count -eq 1) {
$key | % {
$file = "$($_.UninstallString)"
if ($installerType -eq 'MSI') {
# The Product Code GUID is all that should be passed for MSI, and very
# FIRST, because it comes directly after /x, which is already set in the
# Uninstall-ChocolateyPackage msiargs (facepalm).
$silentArgs = "$($_.PSChildName) $silentArgs"
# Don't pass anything for file, it is ignored for msi (facepalm number 2)
# Alternatively if you need to pass a path to an msi, determine that and
# use it instead of the above in silentArgs, still very first
$file = ''
}
Uninstall-ChocolateyPackage -PackageName $packageName `
-FileType $installerType `
-SilentArgs "$silentArgs" `
-ValidExitCodes $validExitCodes `
-File "$file"
}
} elseif ($key.Count -eq 0) {
Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
Write-Warning "$key.Count matches found!"
Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
Write-Warning "Please alert package maintainer the following keys were matched:"
$key | % {Write-Warning "- $_.DisplayName"}
}
## OTHER HELPERS
## https://github.com/chocolatey/choco/wiki/HelpersReference
#Uninstall-ChocolateyZipPackage
#Uninstall-BinFile # Only needed if you added one in the installer script, choco will remove the ones it added automatically.
#remove any shortcuts you added
## Summary
How do I create packages? See https://github.com/chocolatey/choco/wiki/CreatePackages
If you are submitting packages to the community feed (https://chocolatey.org)
always try to ensure you have read, understood and adhere to the create
packages wiki link above.
## Automatic Packages?
Consider making this package an automatic package, for the best
maintainability over time. Read up at https://github.com/chocolatey/choco/wiki/AutomaticPackages
## Shim Generation
Any executables you include in the package or download (but don't call
install against using the built-in functions) will be automatically shimmed.
This means those executables will automatically be included on the path.
Shim generation runs whether the package is self-contained or uses automation
scripts.
By default, these are considered console applications.
If the application is a GUI, you should create an empty file next to the exe
named 'name.exe.gui' e.g. 'bob.exe' would need a file named 'bob.exe.gui'.
See https://github.com/chocolatey/choco/wiki/CreatePackages#how-do-i-set-up-batch-redirects-for-applications-that-have-a-gui
If you want to ignore the executable, create an empty file next to the exe
named 'name.exe.ignore' e.g. 'bob.exe' would need a file named
'bob.exe.ignore'.
See https://github.com/chocolatey/choco/wiki/CreatePackages#how-do-i-exclude-executables-from-getting-batch-redirects
## Self-Contained?
If you have a self-contained package, you can remove the automation scripts
entirely and just include the executables, they will automatically get shimmed,
which puts them on the path. Ensure you have the legal right to distribute
the application though. See https://github.com/chocolatey/choco/wiki/Legal.
You should read up on the Shim Generation section to familiarize yourself
on what to do with GUI applications and/or ignoring shims.
## Automation Scripts
You have a powerful use of Chocolatey, as you are using PowerShell. So you
can do just about anything you need. Choco has some very handy built-in
functions that you can use, these are sometimes called the helpers.
### Built-In Functions
https://github.com/chocolatey/choco/wiki/HelpersReference
A note about a couple:
* Get-BinRoot - this is a horribly named function that doesn't do what new folks think it does. It gets you the 'tools' root, which by default is set to 'c:\tools', not the chocolateyInstall bin folder.
* Install-BinFile - used for non-exe files - executables are automatically shimmed...
* Uninstall-BinFile - used for non-exe files - executables are automatically shimmed
### Getting package specific information
Use the package parameters pattern - see https://github.com/chocolatey/choco/wiki/How-To-Parse-PackageParameters-Argument
### Need to mount an ISO?
https://github.com/chocolatey/choco/wiki/How-To-Mount-An-Iso-In-Chocolatey-Package
### Environment Variables
Chocolatey makes a number of environment variables available (You can access any of these with $env:TheVariableNameBelow):
* TEMP = Overridden to the CacheLocation, but may be the same as the original TEMP folder
* ChocolateyInstall = Top level folder where Chocolatey is installed
* chocolateyPackageName = The name of the package, equivalent to the id in the nuspec (0.9.9+)
* chocolateyPackageVersion = The version of the package, equivalent to the version in the nuspec (0.9.9+)
* chocolateyPackageFolder = The top level location of the package folder
#### Advanced Environment Variables
The following are more advanced settings:
* chocolateyPackageParameters = (0.9.8.22+)
* CHOCOLATEY_VERSION = The version of Choco you normally see. Use if you are 'lighting' things up based on choco version. (0.9.9+)
- Otherwise take a dependency on the specific version you need.
* chocolateyForceX86 = If available and set to 'true', then user has requested 32bit version. (0.9.9+)
- Automatically handled in built in Choco functions.
* OS_PLATFORM = Like Windows, OSX, Linux. (0.9.9+)
* OS_VERSION = The version of OS, like 6.1 something something for Windows. (0.9.9+)
* OS_NAME = The reported name of the OS. (0.9.9+)
* IS_PROCESSELEVATED = Is the process elevated? (0.9.9+)
#### Experimental Environment Variables
The following are experimental or use not recommended:
* OS_IS64BIT = This may not return correctly - it may depend on the process the app is running under (0.9.9+)
* CHOCOLATEY_VERSION_PRODUCT = the version of Choco that may match CHOCOLATEY_VERSION but may be different (0.9.9+)
- it's based on git describe
* IS_ADMIN = Is the user an administrator? But doesn't tell you if the process is elevated. (0.9.9+)
* chocolateyInstallOverride = Not for use in package automation scripts. (0.9.9+)
* chocolateyInstallArguments = the installer arguments meant for the native installer. You should use chocolateyPackageParameters intead. (0.9.9+)
Log in or click on link to see number of positives.
- pragmaticworksworkbenchserver.2016.1.2-beta2.nupkg (12dc1d26c0d0) - ## / 57
- BETA_Workbench_Server_2016.1.2.1130.exe (92d849eb4573) - ## / 57
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
Workbench Server 2018.2.4.504 | 752 | Wednesday, June 27, 2018 | Approved | |
Workbench Server 2018.2.4.503 | 316 | Thursday, May 3, 2018 | Approved | |
Workbench Server 2018.2.3.412-beta | 287 | Thursday, April 12, 2018 | Exempted | |
Workbench Server 2018.2.2.302-beta | 439 | Friday, March 2, 2018 | Exempted | |
Workbench Server 2018.1.5.312 | 345 | Monday, March 12, 2018 | Approved | |
Workbench Server 2018.1.4.208 | 355 | Friday, February 9, 2018 | Approved | |
Workbench Server 2018.1.4.129-beta | 333 | Monday, January 29, 2018 | Exempted | |
Workbench Server 2018.1.3.122-beta | 361 | Monday, January 22, 2018 | Exempted | |
Workbench Server 2018.1.2.1206-beta | 385 | Wednesday, December 6, 2017 | Approved | |
Workbench Server 2018.1.1.1030-beta | 352 | Monday, October 30, 2017 | Approved | |
Workbench Server 2017.4.7.1127 | 340 | Tuesday, November 28, 2017 | Approved | |
Workbench Server 2017.4.6.1107 | 334 | Tuesday, November 7, 2017 | Approved | |
Workbench Server 2017.4.5.1106 | 344 | Monday, November 6, 2017 | Approved | |
Workbench Server 2017.4.5.1018-beta | 369 | Wednesday, October 18, 2017 | Exempted | |
Workbench Server 2017.4.3.1010-beta | 379 | Tuesday, October 10, 2017 | Approved | |
Workbench Server 2017.3.3.807 | 385 | Monday, August 7, 2017 | Approved | |
Workbench Server 2017.3.3.710-beta | 391 | Monday, July 10, 2017 | Approved | |
Workbench Server 2017.3.2.605-beta | 410 | Monday, June 5, 2017 | Approved | |
Workbench Server 2017.3.1.502-beta | 416 | Tuesday, May 2, 2017 | Approved | |
Workbench Server 2017.2.3.501 | 396 | Monday, May 1, 2017 | Approved | |
Workbench Server 2017.2.3.330-beta | 392 | Thursday, March 30, 2017 | Approved | |
Workbench Server 2017.1.6 | 384 | Friday, March 3, 2017 | Approved | |
Workbench Server 2017.1.5 | 426 | Thursday, February 9, 2017 | Approved | |
Workbench Server 2017.1.4 | 442 | Thursday, February 2, 2017 | Approved | |
Workbench Server 2017.1.3 | 434 | Thursday, January 12, 2017 | Approved | |
Workbench Server 2017.1.2-beta | 434 | Tuesday, November 29, 2016 | Approved | |
Workbench Server 2016.4.5 | 423 | Thursday, November 3, 2016 | Approved | |
Workbench Server 2016.4.4 | 441 | Tuesday, November 1, 2016 | Approved | |
Workbench Server 2016.3.1-beta1 | 381 | Monday, May 2, 2016 | Exempted | |
Workbench Server 2016.1.5-beta5 | 414 | Tuesday, January 19, 2016 | Exempted | |
Workbench Server 2016.1.3-beta4 | 408 | Monday, January 11, 2016 | Exempted | |
Workbench Server 2016.1.3-beta3 | 490 | Thursday, January 7, 2016 | Exempted | |
Workbench Server 2016.1.2-beta2 | 412 | Monday, November 30, 2015 | Exempted |
© 2015
Workbench Server 2015.4.1-beta1 Release Notes
Please visit the following links for each feature's release notes:
BI xPress Server: http://help.pragmaticworks.com/bixpress/
DOC xPress Server: http://help.pragmaticworks.com/docxpress/
LegiTest Server: http://help.pragmaticworks.com/LegiTest/
This package has no dependencies.
Ground Rules:
- This discussion is only about Workbench Server and the Workbench Server package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or Workbench Server, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.