Help Center>Foundation Help

Applies to:

Winshuttle Server 10.x release notes

Winshuttle Server 10.7 Hotfix 2

New features

  • Server support for Async Web services

Winshuttle Server 10.7 FCS / GA

New features

  • Added support for EHP 7

Winshuttle Workflow 10.6.1 GA Hotfix 9

(WF Server: 10.6.1.81292-GA Hotfix 9)

Bug Fixes

  • Fixed an error opening a document-controlled library in a Docex site

Hotfix merges

  • 10.6.1 GA Hotfix 8 

Winshuttle Workflow 10.6.1 GA Hotfix 8

(WF Server: 10.6.1.78987 -GA Hotfix 8)

Bug Fixes:

  • Fixed functionality of the SV Configurator key "AllowNoAssignmentSwimlanes" so It allow users to not specify the swimlane users when initiating the process
  • Fixed online validations timeouts that can occur for long running web services
  • Fixed issues of duplicate items seen in the form library webpart
  • Improved performance for running the archival command by itemid
  • Fixed an issue with the "All tasks" view of the Winshuttle task list webpart

Winshuttle Server 10.6.1 GA

Back to top

New features

  • Server is now fully HA (High Availability) compliant, and the Queue can also be deployed in a HA environment.
  • Support for IF condition in published TRANSACTION Web services.
  • SiteMinder support for the execution of Web services and auopost requests from Central.
  • SQL Server is now the default database for Winshuttle Server and the installer can now create a SQL server database.
  • You can now define a custom username/password for the WinshuttleWorker service through the installer.
  • A new Queue Deployment utility has been introduced that also checks the file integrity of the Erlang cookie file integrity.

Bug fixes

  • Winshuttle SAP Error Messages have been fixed
  • Multiple Sheets run as RUN LATER (SERVER) only returning data to the first sheet
  • Autopost responses getting blocked by status messages due to the same queue.

Winshuttle Server 10.6 GA (General Availability)

New Features

  • Support for SSO (Single sign on) in FormWorker (i.e. for Transaction scripts with launch GUI and for Transaction scripts with GUI scripting recording)
  • Support for fully qualified domain name in SNC_MYNAME parameter and is passed through Central.
  • Support for linked query scripts through the ‘Run Later Server’ feature.
  • Support for Query scripts that have destination type as Sharepoint List.

NOTE: Please also see Winshuttle Workflow release notes for a complete list of related release notes, known issues, and new features.

Improved architecture

Beginning with Server 10.5, additional features include:

  • Manager – Server Manager manages the workers. All requests are first handled by the Manager before placing them in subsequent queues. Worker specifies its capabilities while registering itself with the Manager
  • Worker - Workers are distributed agents that process user requests. A single Worker can reside on a given machine. Each worker can have single/multiple capabilities to process the requests.

New Worker capabilities

  • Transaction Excel Posting (Transaction Autopost)
  • Query Excel Posting (Query Autopost)
  • Transaction Services
  • Query Services
  • Service Publish
  • Portability of existing functionality to the new architecture
  • Support for Launch GUI and GUI Scripting for Autopost
  • Support for Launch GUI and GUI Scripting for Web Services (ASync and Sync Mode)
  • Support for Enterprise Portal Logon using User Credentials / SP Nego
  • Improved scalability without using a NLB/HLB. Server no longer requires NLB/HLB. The workers (request processing agents) can be deployed on any machine
  • Built-in queuing support in the new architectures:
    - Support for Transaction WFM
    - Support for Kerberos SSO and X509 certificate SSO.
    - SSO for Launch GUI and GUI Scripting is not supported

Bug Fixes

  • Server Installation issues on Windows Server 2012.

Known Issues

  • When scheduling Query scripts that have destination type set to a SharePoint list using the Run Later Server option: If you want to use the AppPool Identity feature, you must manually change the identity of the worker service. (By default, the worker service runs under the Network Service account.) Also this change is required to all worker services deployed.
  • Installation: If Rabbit MQ and the Queue Deployment utility are deployed on different partitions of the same machine, the Queue Deployment utility throws an error "Rabbitmqctl is not a recognized command".
  • The mapped SAP username and Windows username cannot be different for X509 SSO.

Winshuttle Server 10.5

Back to top

New Features

Improved architecture using Manager and Worker

  • Manager – Server Manager manages the workers. All requests are first handled by the Manager before placing them in subsequent queues. Worker specifies its capabilities while registering itself with the Manager
  • Worker - Workers are distributed agents that process user requests. A single Worker can reside on a given machine. Each worker can have single/multiple capabilities to process the requests.

Worker capabilities include the following:

  • Transaction Excel Posting (Transaction Autopost)
  • Query Excel Posting (Query Autopost)
  • Transaction Services
  • Query Services
  • Service Publish
  • Portability of existing functionality to the new architecture
  • Support for Launch GUI and GUI Scripting for Autopost
  • Support for Launch GUI and GUI Scripting for Web Services ( ASync and Sync Mode)
  • Support for Enterprise Portal Logon using User Credentials / SP Nego
  • Improved scalability without using a NLB/HLB. Server no longer requires NLB/HLB. The workers (request processing agents) can be deployed on any machine
  • Inbuilt queuing support in the new architectures:
    - Support for Transaction WFM
    - Support for Kerberos SSO and X509 certificate SSO.
    - SSO for Launch GUI and GUI Scripting is not supported

Known Issues

  • Rabbit MQ version 2.8.6 must be downloaded and installed; other versions of RabbitMQ might not work properly.
  • Install Winshuttle Server 10.5 by running WinshuttleServer.msi from a command prompt with administrator privileges. Double-clicking the Winshuttle.msi file (even as an administrative user) generates the message "Please run the installer as admin".
  • Worker service does not start using 32 bit Winshuttle Server installer, but the manual deployment of the same works fine.
  • FormWorker is not supported with SAP SSO logon.
  • When Query service is used through Query Service Proxies created in .NET framework, a timeout exception appears after 8-10 calls on Winshuttle Server.
  • For Launch GUI and GUI scripting requests, FormWorker can handle only one request at a time. The default Pre-fetch count for both types of request is 1.
  • You must manually attend to any SAP GUI pop-up dialogs that launch at the runtime of Launch GUI or GUI scripting requests for SAP GUI installed on the machine having FormWorker. Otherwise the launch GUI and GUI scripting requests will fail.
  • For Winshuttle Server deployed on IIS 6.0, application gets started and services can be browsed even if the application has database connectivity and configuration related problems. Such errors are shown at startup but the application still starts. However in order to run the services, database connectivity and configuration errors must be fixed.
  • Server does not support .Net Framework 4.0 and therefore cannot be installed on the same physical machine if Sharepoint 2013 is installed.