Launch GUI : Configuring the hosting utility

To publish TRANSACTION scripts that have Launch GUI enabled, or to use them in Winshuttle Forms, you must start the Winshuttle SERVER service hosting environment on any servers that are part of the deployment. Without the hosting utility, Winshuttle SERVER does not allow published web services to be consumed.

To configure Launch GUI

1. Log onto the server where Winshuttle SERVER is installed.
2. Install SAP GUI if it's not already installed.
3. Obtain the version of “WinshuttleServer.FormHost” utility that matches your installation from Winshuttle Support.
4. Extract all the files for the Winshuttle SERVER hosting utility. These are located in WinshuttleServer.FormHost.zip.
5. Use any text editor to open the WinshuttleServer.FormHost.exe.config file. Copy the file as a backup.

Locate the <AllowedIdentities> section and add an allowed identity of the account that will run the utility.

Locate the <WinshuttleServerConfiguration> section in this configuration file. Define the Winshuttle SERVER database path in the serverDatabase element as shown below:

<winshuttleServerConfiguration>
<serverDatabase type="SQLITE" connectionString="Data Source= C:\inetpub\wwwroot\Winshuttle\SERVER\App_Data \WinshuttleServerDB.db;Version=3;New=True;" />

1. Update the TRANSACTION service URL in the <serverHost> element.
   
   <serverHost transactionServiceUrl="http://10.10.1.150:8083/WinshuttleServer/TransactionService" />
2. Save the configuration file and close it.
3. Double-click WinshuttleServer.FormHost.exe. The Winshuttle SERVER hosting environment for launch GUI functionality is started and appears in the notification area.
   
   The updates should look similar to this:
   
   <allowedIdentities>
   <allowedIdentity name="wse\testadmin1" />
   <allowedIdentity name="wse\centraluser" />
   <allowedIdentity name="wse\formsserviceuser" /> </allowedIdentities>
   <serverDatabase type="MSSQL2005" connectionString="Server=WSSQLSP01\SQLExpress;database=WinshuttleServer DB;Integrated Security=SSPI;User Id=sa Password=****" />
   <serverHost transactionServiceUrl="http://10.10.1.150:8083/WinshuttleServer/TransactionService" />

Configuring Winshuttle SERVER to use scripts that include Launch GUI

1. In the Winshuttle SERVER folder, right-click the web.config file, point to Open With, and click Notepad or any other text editing program. Copy the file for backup.

Locate winshuttleServerConfiguration section and define the URL for the TransactionService deployed on FormHost utility. For example,

http://[IP:Port]/WinshuttleServer/TransactionService

1. Define this URL in the transactionServiceUrl attribute of the serverHost element.
   
   <winshuttleServerConfiguration>
   <allowedIdentities>
   <allowedIdentity name="" />
   </allowedIdentities>
   <serverDatabase type="SQLITE" connectionString="" />
   <serverHost transactionServiceUrl="http://10.26.8.203:8080/WinshuttleServer/TransactionService" />
   <serverQueryCache enabled="false" type="MEMORY">
   <memoryCache />
   <databaseCache connectionString="Server=\SQLExpress;database=WinshuttleServerCacheDB;Integrated Security=SSPI;" type="MSSQL2008" />
   </serverQueryCache>
   <integratedLogon value="false" />
   <validateRequestSchema value="true" />
   <delayForCpuPerformance value="100"/>
   <anonymousCallUserIdentity value="" />
   <enablePerfCounters value="false" qsqRun="false" txrRun="false" autopostTxr="false" autopostQsq="false" />
   </winshuttleServerConfiguration>
2. Save the Web.Config file and close it. You can now publish and use a TRANSACTION script that includes steps to launch GUI.

Test Winshuttle Server connectivity with Winshuttle Central

1. Open Internet Explorer, and then navigate to your CENTRAL site.

In the left navigation bar of the page, click Winshuttle CENTRAL Administration.

Under SERVER, click TRANSACTION Services Configuration *or* QUERY Services Configuration.

1. In the Winshuttle SERVER for TRANSACTION URL box, paste the URL from your AutoPostService.svc.

Click the Test Connection button.

1. The Connection test was successful message appears.