Applies to:
Configuring the Server Manager for Winshuttle SAP Integration Server 11x
Winshuttle Server 11.x Admin Tool Guide
Use the Manager section of the SAPIS Admin tool to configure the server database and connection string, enable and configure logging, and/or make changes to the WSDL (Web Service Definition Language) binding, protocol, and authentication settings.
On this page
Winshuttle Manager Configuration | Load the Web.config file and apply any changes made in other sections (Deployment, Log4Net, and System Service Model). |
Deployment options | Configure the Server database and connection string. |
Log4Net section | Enable and configure logging for SAP Integration Server. |
System.ServiceModel section | Enable and configure the WSDL (Web Service Definition Language) binding, authentication, and connection protocols (HTTP/HTTPS). |
Winshuttle Manager Configuration
Back to topUse the Manager section to open the SAPIS Web.config file, as well as apply any changes made in other sections (Deployment Options, Log4Net, and SystemServiceModel).
- Click [...] to browse to your web.config for the Winshuttle Server Manager.
The default location for the Server Manager web.config file is C:\Program Files\Server\Manager\web.config. - Click Load Configuration to load it.
- Click Apply Changes to apply any changes you make on this screen.
Deployment Options section
Back to topUse Deployment Options to configure the server database type (SQL 2008, for example) and the connection string for the database.
Server Database (Type)
Select the type of SQL Server Database (SQL 2008/2012/2014) from the drop down. (If you've loaded the web.config file, your connection string should appear in the Connection String field.
Connection String
To set the connection string for the Server Manager database, click [...] to open the SQL Server dialog box and connect to a database server.
The current database connection string will be displayed here after you load the web.config file for the Server Manager.
Log4Net section
Back to topUse the Log4Net section to enable and configure logging for SAP Integration Server.
Winshuttle Manager Developer Logs
This setting enables/disables the developer logs in Winshuttle Manager. These logs are enabled by default to ERROR. Logging levels are as follows:
- OFF—Disables all logging.
- ALL—Logs everything.
- ERROR—Logs errors only.
To enable and access Winshuttle SAP Integration Server Manager log files
- On the Server desktop, right-click the Winshuttle Server Administration tool, and then click Run as Administrator.
- Click the Manager tab, and then click Load Configuration.
- In the Log4Net Section, next to Winshuttle Manager Developer Logs, set logging to the desired logging level (ALL or ERROR).
- Click Apply Changes.
NOTE:
- You will need to enable logging on each Winshuttle SAP Integration Server you wish to log.
- SAPIS log files will be stored in the directory where SAPIS was installed, in the Manager/Temp (for Server Manager) and Worker/Temp (for Server Worker) folders.
System.ServiceModel section
Back to topUse the System Service Model section to enable and configure the WSDL (Web Service Definition Language) binding, authentication settings, and connection protocols (HTTP/HTTPS).
Authenticated WSDL Get Binding
Check to enable/disable WSDL binding. This option is disabled by default.
Enable this option if you want to securely retrieve the WSDL (Web Service Definition Language) information for a published web service. The WSDL get process is secured using Windows authentication.
Client Authentication Scheme for Published Services
Windows—Client uses Windows authentication. Windows Authentication is used by default when using published Web services in Winshuttle SAP Integration Server. Most clients support this authentication scheme. Note: Workflow Forms require Windows Authentication.
Protocol Used to Connect to Winshuttle Manager
This setting defines the method of communication with the Winshuttle Server —either HTTP or HTTPS (SSL over HTTP).
The default setting is HTTP.
Note: If you wish to use HTTPS, you will need to install Server as an IIS HTTPS Web site, and install a valid Windows Certificate.