Downloads:
13,436
Downloads of v 2016.4.5:
423
Last Update:
03 Nov 2016
Package Maintainer(s):
Software Author(s):
- Pragmatic Works Software
Tags:
admin bixpress dbaxpress docxpress documentation excel hive inspect licensed lineage monitoring oracle pragmaticworks salesforce sharepoint sql ssas ssis ssrs surf trialWorkbench Server
This is not the latest version of Workbench Server available.
- 1
- 2
- 3
2016.4.5 | Updated: 03 Nov 2016
Downloads:
13,436
Downloads of v 2016.4.5:
423
Maintainer(s):
Software Author(s):
- Pragmatic Works Software
Workbench Server 2016.4.5
This is not the latest version of Workbench Server available.
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
All Checks are Passing
3 Passing Tests
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.4.5 --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.4.5'" [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.4.5'"
$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.4.5'
source: INTERNAL REPO URL
state: present
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.4.5'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller pragmaticworksworkbenchserver
{
Name = "pragmaticworksworkbenchserver"
Version = "2016.4.5"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'pragmaticworksworkbenchserver':
ensure => '2016.4.5',
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.
Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...
This package was approved by moderator gep13 on 07 Nov 2016.
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.
$ErrorActionPreference = 'Stop';
$packageName = 'pragmaticworksworkbenchserver'
$softwareName = 'Workbench Server*'
$installerType = 'EXE'
$silentArgs = '/qn /norestart'
$validExitCodes = @(0, 3010, 1605, 1614, 1641)
$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') {
$silentArgs = "$($_.PSChildName) $silentArgs"
$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"}
}
Log in or click on link to see number of positives.
- pragmaticworksworkbenchserver.2016.4.5.nupkg (31260b9c5807) - ## / 56
- Workbench_Server_2016.4.5.1103.exe (513e4cdc309b) - ## / 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 | 753 | 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 | 341 | 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 |
© 2016
BI xPress Server version 2016.4.5
New Features
1491: Control Flows now contain precedence constraints for nested tasks
- Control Flows now support showing the precedence constraints for nested tasks such as Sequence Container, ForEach Container, and others. Also, users can now move the tasks and components around freely on the page in order to get a better view of some clustered items.
1618: BI xPress Server Administrators can now clean up orphaned activities and files within the Auditing Framework
- This feature removes any activity that references a file that no longer exists. It also removes all user deployed files older than a day that are not associated with an activity.
1620: BI xPress Server's SSIS Monitoring Console is even more mobile device friendly.
6802: BI xPress Server notification engine now includes a default template for creating VSTS notifications
Updated Features
6279: SQL notification provider now supports batches
Fixes
4838: SSIS Monitoring Console's filter type drop down removes filter if filter value isn't first populated
4981: Users can't toggling between Project and Package Connection within Auditing Framework
5536: Notification template syntax errors aren't being logged within the Event Execution History
6214: BI xPress Server "Unspecified Error" when attempting to applying auditing framework to certain packages
6773: Event names are no longer being cached in-memory for Notification Subscriptions.
DOC xPress Server version 2016.4.5
Fixes
1548: NullReferenceException when running Snapshot Comparison
7409: Solutions won't load when viewed within Microsoft Edge Anniversary Update
7831: DOC xPress Server's dates and times appear as "Invalid Date Invalid Date" on various pages.
LegiTest Server version 2016.4.5
New Features
4960: Scheduling tests no longer has a dependency on the LegiTest Command Line
6229: Expanded items in LegiTest Server dashboard now remain expanded when done managing tags.
6258: Enhanced LegiTest notifications to include grids from comparisons and validations
- Grids are now shown in LegiTest notification emails so that data mismatches or validations show the data in question in the notification email (HTML only)
6266: User can now specify the End Time for scheduled test runs
- Allow the user to specify the end time on the end date when scheduling a task. If not specified, default it to end of day instead of using the start time.
6278: Added ability to create VSTS work items as a notification engine target
- Notification can now automatically create work items in Visual Studio Team Services
- The template is applied to create a title for the created work item
6280: Added ability to run executable as a notification engine target
- Notification engine can now run an executable on the server in response to a notification
- Optionally the templated output is passed to the executable as a file
6281: Added ability to make URI GETs/POSTs/PUTs as a notification engine target
- Use notification engine to interact with HTTP APIs
- Configure the payload using the standard templating engine
- Support for basic authentication, as well as OAUTH1 and OAUTH2
6282: Added ability to manually run notifications for specific tests from the LegiTest Dashboard
6284: Added ability to defer population of notification engine collection objects
- Notification engine now defers some of the work in creating a notification until the notification fires, resulting in higher performance.
6286: Implemented Role Based Security
- Manage Access to LegiTest Server actions based on roles.
- Manage access to tests based on roles and tags.
6784: Allowed custom name for LegiTest Tile
6828: Added Test Management Page
- Manage Parameters, Scheduled Tasks, Tags, and certain actions all from one page.
7809: Data driven tests are displayed as separate tests on the details page and as a single item on the summary page.
Updated Features
6827: Improvements made to LegiTest Server home page
- LegiTest Server Dashboard is now the LegiTest Server Summary page.
- Clicking on a failed test from the Summary will take you to the details of the failed assert.
- Tags are now listed to the right of the Summary page, with the ability to filter tags moved, and takes up less real estate on the screen.
Fixes
6226: Parameter and Data Type Name no longer overlap when editing parameters.
6733: Navigation breadcrumb trail is not visible on the details page
6734: Command line configuration values are not being retained when upgrading LegiTest Server to the newest version
6735: User is now alerted if the command line can not find a valid test runner
6738: Summary page does not refresh after a test suite is manually run from the server
6744: Annotations now show up on the results page.
6781: LegiTest Server does not display any error if no coverage reports load
6800: Command Line error message reflects incorrect log location
7331: Notification events fire multiple times for each Test Group within a suite if configured to an assembly
Workbench Server version 2016.4.5
New Features
6723: Upgrading Workbench Server will now display a message indicating that all previous versions will be uninstalled during the upgrade process
- Users upgrading Workbench Server will now see a message indicating that all previous versions of Workbench Server will be uninstalled prior to upgrading. This is not a change in behavior from previous releases, only an update to the user interface to make it more clear as to what is happening behind the scenes. This message is only visible when upgrading.
7373: Added PowerShell 3.0 or later to the system requirements for Workbench Server
Updated Features
4718: Activating or Deactivating a license now redirects users to license overview page upon completion
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.