Features

Winshuttle CENTRAL is a unified management interface within SharePoint for TRANSACTION, QUERY, and RUNNER files. The key benefits of Winshuttle CENTRAL include the following:

• Centralized administration of Winshuttle users and licenses
• File sharing and collaboration
• Activity dashboard and centralized reporting
• Version control and workflow management
• Native Microsoft Office and SharePoint integration
• Autopost capability through Winshuttle SERVER through reviewer and creator credentials or with system account login
• Post immediately or at a specific time through Winshuttle SERVER
• Allows IT ease of control for Winshuttle user access to the SAP environment
• Full traceability and ROI analysis through comprehensive logging of records uploaded and total time saved by the user
• Winshuttle CENTRAL installation is non-disruptive to SQL and the SharePoint content database instances. You should ensure that no connection to your target Site Collections is active during the installation. Multiple IIS resets must occur during deployment.

Below are key considerations for the Winshuttle CENTRAL deployment:

• Winshuttle CENTRAL installs into the GAC. For SharePoint 2010, Winshuttle CENTRAL installs custom layouts in the following location:
  • %systemroot%\Program Files\Common Files\Microsoft Shared\web server extensions\14\TEMPLATE\LAYOUTS\Winshuttle.Winshuttle CENTRAL
• Winshuttle loads Content Types in the Site Content Type Gallery as Sealed. You cannot change sealed content types through the Windows SharePoint Services user interface, and you must be a site collection administrator to unseal the content type using the object model.
• CENTRAL installs a custom SQL database named eShuttleDB. The minimum role memberships for eShuttleDB are "db_owner" and "public" using the BUILTIN\Users user login. All CENTRAL configuration, transactional data, and licensing information is stored in eShuttleDB.
• All CENTRAL features are scoped at the site level.
• All CENTRAL database connection strings are done on the farm level.
• CENTRAL workflows are designed in Microsoft Visual Studio.
• No MIME creation takes place on IIS.