Perceptive Document Composition

Transcription

1 Perceptive Document Composition WebClient Installation and Setup Guide PDC Version: 5.4 Written by: Product Documentation, R&D Date: February 2014

2 2014 Perceptive Software. All rights reserved Perceptive Software is a trademark of Lexmark International Technology S.A., registered in the U.S. and other countries. All other brands and product names mentioned in this document are trademarks or registered trademarks of their respective owners. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or any other media embodiments now known or hereafter to become known without the prior written permission of Lexmark.

3 Table of Contents Target Audience... 4 Update... 4 Compatibility... 4 Update from Version to Version Setup... 4 General... 4 Deploying the WebClient... 5 Setting Up the WebClient on a Client Computer Private / Protected Mode in a Web Browser Known Problems Page 3 of 28

4 Perceptive Document Composition WebClient Setup Target Audience This document is designed for system administrators or users with basic system knowledge. Experience of Windows server and client platforms used here and of the IIS platform used to host web applications is expected. To install and set up the WebClient you will require knowledge of a Document Composition installation and the concept behind the configuration. Update Compatibility Perceptive Document Composition WebClient 5.4 is not compatible with previous versions of Perceptive Document Composition and can only connect to a Modus_MWS service version 5.4. Update from Version to Version To update to version 5.4.0, on the web server, complete the following steps. 1. Unzip the PDC.WebClient.zip file to a local directory. 2. From the PDC.WebClient directory, copy the PDC.WebClient.xap file to the virtual directory in IIS. For more information, refer to Create a virtual directory in IIS. 3. Optional. Complete the following substeps. 1. In the virtual directory in IIS, open the PDC.WebClient.xml file with an UTF-8 compatible editor 2. Find the following line. <add key="supportedfirefoxproductversion" value="10.0.9" /> 3. Change value to your current Firefox version using the number before and after the first period. Example <add key="supportedfirefoxproductversion" value="24.2" /> 4. From the PDC.WebClient directory, copy the Help directory to the virtual directory in IIS. Setup General Silverlight Application The WebClient has been built as a Microsoft Silverlight application. Silverlight applications are downloaded from a web server and can be run on a client computer either in in-browser or out-of-browser mode. Elevated permissions are required in order to use the full functionality of Microsoft Office interaction. The WebClient must be run as a Trusted Application. Page 4 of 28

5 Following the official release of Silverlight 5, Perceptive Document Composition release and higher will support the use of the WebClient in In-Browser mode as a trusted application offering the full functionality of interaction with Microsoft Office. Two-Step Installation Installation is done in two steps. Step 1 Set up via the web server. This requires server-side preparation. Step 2 Installation of the Silverlight runtime environment on the Client Preparing to run the WebClient as a Trusted Application Out-of-Browser-Modus Local Installation of the WebClient In-Browser-Mode with Silverlight 5 - Client-side installation of the certificate PDC.WebClient.cer provided with the installation set. - Configuring how to run a Trusted Application in a browser - Loading the Client from the loading page in a web browser Deploying the WebClient Server-Side Requirements for Deployment and Operation Requirements For a server-side installation a minimum release base of version is required. Installation package for the WebClient (PDC.WebClient.zip) The PDC.WebClientLauncher if required (PDC.WebClientLauncher.exe) System Requirements for Windows Server / IIS and MIME Types IIS In addition to the requirements of the server operating system for running a Document Composition Server, hosting the WebClient on a Document Composition Server also requires the installation or activation of the WWW service of the Internet Information Services (IIS). Activation of TCP Ports If there is a firewall between the WebClients and the Server, the following ports must be activated during a standard installation: Page 5 of 28

6 If SSL is used to protect the communication between the WebClients and the Server, the following ports must be activated during a standard installation: Deploying the WebClient Deploying the WebClient does not normally entail having to make any extra modifications. However, depending on the Windows Server version used and thus the IIS version in operation, you may have to add certain MIME types to support the deployment of Silverlight applications. This step is only necessary if your IIS version is lower than 7.0 and the operating system used is Windows XP, Windows 2003 or Windows Vista RTM. All MIME types needed to support Silverlight are implemented by default in Windows 2008 or Windows Vista SP1. With regard to the recommended platforms for Document Composition Server installations, this only applies to Windows Server 2003 IIS 6.0. Check for the following MIME types and add any that may be missing:.xap application/x-silverlight-app.xaml application/xaml+xml.xbap application/x-ms-xbap If you are using Windows Server 2003 IIS 6.0 alter the settings by running the IIS Manager which can be accessed from the property dialog for the local Computer. Click on the button MIME Types to open the properties dialog where you can add the required MIME types. For a more detailed description of this (and also for other Windows platforms), refer to the article Configuring IIS for Silverlight Applications (KBA Q0ZNL) on the website direct link: Unpacking and Preparing WebClient Files Required Files Zip file PDC.WebClient.zip: contains all necessary set up and configuration files. Installation Package PDC.WebClientEnableFullTrust.msi as an alternative to manual configuration: For a simplified configuration of the WebClient as a Trusted Application inside a browser with Silverlight 5. Page 6 of 28

7 PDC.WebClientLauncher.exe Optional tool to start the WebClient in Out-of-Browser mode. Content of PDC.WebClient.zip The zip file PDC.WebClient.zip contains three directories: PDC PDCWebClient SL5_Setup Directory PDC Contains configuration files. These must be copied to the installation directory (environment variable %PDCdir%) or compared to existing files as the case may be. File modus_core.exe.config modus_mws.exe.config ClientAccessPolicy.xml Function Configuration file for modus_core services Needs to be compared to the existing file from the original Document Composition installation. Configuration file for modus_mws services. Needs to be compared to the existing file from the original Document Composition installation. Configuration file for the new cross domain services. Must be copied to the Document Composition installation directory if not already available. Directory PDCWebClient Web folder for web server deployment. File PDC.WebClient.xml Function Configuration file containing destination addresses for the WebClient. The values for the following configuration keys need to be adapted to customer requirements mwsprocessservicebasic Page 7 of 28

8 PDC.WebClient.xap PDC.WebClient.html \Help\de\ \Help\en \Help\fr \Help\nl mwsrepositoryservicebasic MURServiceBasic and if required mwsprocessservicerest The WebClient's Silverlight application package. This contains the compressed assemblies and resources of the Silverlight application. HTML code to download the WebClient from a web browser. HTML help files German version HTML help files English version HTML help files French version HTML help files Dutch version Directory SL5_setup Files for manual configuration of the WebClient on a client computer. File PDC.WebClient.cer Silverlight_AppTrust_x32.reg Silverlight_AppTrust_x64.reg Function Digital certificate for the WebClient. Needed to check manufacturer authenticity. Registry settings for 32-Bit systems Registry settings for 64-Bit systems Preparatory Steps Carry out the following steps to prepare your system for WebClient deployment. 1. Deploying the Microsoft Silverlight Application Create a folder in the Document Composition or web server file system, for example %PDCdir%\PDCWebClient and copy the following files in the folder: PDC.WebClient.xap PDC.WebClient.xml Page 8 of 28

9 PDC.WebClient.html Help\* (complete directory structure) Make sure when copying the folder Help that you include all the subfolders for the Document Composition WebClient help system. As described above, the target folder is the same folder the.xap file was copied to. In this case: %PDCdir%\PDCWebClient Only when the help files are located in a subfolder relative to the.xap file in the form of Help/{LANGUAGE-ISOCODE} is it guaranteed that the Document Composition WebClient will find the files. Call the XAP file from a web page in a way demonstrated in the enclosed test page (PDC.WebClient.html). If you do not yet have a web folder or web page at your disposal in which you can copy the code for the XAP call, you can also use the above-mentioned test page for a test deployment. 2. Modify the Configuration File PDC.WebClient.xml Open the configuration file PDC.WebClient.xml with a UTF-8 compatible editor. Adapt the server address values in the following configuration keys mwsprocessservicebasic mwsrepositoryservicebasic MURServiceBasic to those of the Document Composition Server IP address and DNS name. Standard setting is localhost. Depending on the configuration of the new component mws-process REST services included in release version and above (See Modifying the Document Composition Installation) you must also parameterize the configuration key mwsprocessservicerest as follows if the new service is to run on another server/port as the normal mws-process BASIC service. <appsettings>... <add key="mwsprocessservicerest" value= " />... </appsettings> If this key does not exist or the key is empty, the parameter of the mws Basic Service is used by default. Using a SSL connection requires a SSL certificate. Uncomment the following section in the default installation - marked in red below - and comment out the preceding section so that both sections look as follows: <!-- non SSL Variant <add key="mwsprocessservicebasic" value=" /> Page 9 of 28

10 <add key="mwsrepositoryservicebasic" value=" /> <add key="murservicebasic" value=" /> --> <add key="mwsprocessservicebasic" value=" /> <add key="mwsrepositoryservicebasic" value=" /> <add key="murservicebasic" value=" /> 3. UTF-8 Encoding Take particular care to observe UTF-8 encoding requirements when saving all XML configuration files! Create a Virtual Directory in IIS If the directory designated in the previous section has been newly created and has not yet been defined as a component of a web application, you will need to define it as a virtual directory in IIS before being able to access it as a web application. URL Choosing the name PDCWebClient for the virtual directory will result in it becoming part of the applications URL, which is later used to access the WebClient: You will need to replace the placeholder [PDCServerName] with the respective host name of your server. Standard Documents in the Web Folder To ensure successful access and prevent an error such as HTTP the website declined to show this webpage the HTML page from which the WebClient will be downloaded from must be located in the list of web folder default documents. If you are going to use the test document PDC.WebClient.html provided in the set up, then you must add the name PDC.WebClient.html to the list of standard documents or rename the file to Default.htm or index.html as these names are usually already defined and added by default. Access It is not necessary to assign any other access rights than Read for the document you have defined. You can set the authentication procedure to Anonymous authentication as authentication and login to the Document Composition Server are performed via the WebClient itself. Configuration Using the external configuration file PDC.WebClient.xml the WebClient always loads its configuration settings before the login dialog is displayed. This enables you to alter the configuration even while the WebClient is still running. Simply logging on again is enough for any alterations made to take effect. Page 10 of 28

11 Note The IIS and the browser both cache the configuration and the XAP. If you wish to make sure that any changes you make to the application - as described above - take immediate effect, you must configure the settings for the expiration date for web content accordingly. This can be done in IIS using the property dialog and setting the http Headers property for the corresponding files. After activating the switch Enable content expiration or Expire Web content you can define the expiration date of the selected content to force the browser to reload updated content. Defining the setting Expire immediately will ensure any changes take immediate effect. Modifying the Perceptive Document Composition Installation If you have not already done so, update the Document Composition installation to Version As of version Document Composition now contains new components to support the WebClient: CrossDomainService, REST-Services and CORS-Support (Cross Originate Resource Sharing). These new components need to be configured before the WebClient can function correctly. Complete the following steps: 1. Copy Files First of all, copy the file ClientAccessPolicy.xml to the Perceptive Document Composition installation directory (%PDCdir%), if not already existing. 2. Modify Configuration Files 1. Modify the configuration files modus_core.exe.config and modus_mws.exe.config of your existing Document Composition installation. 2. Merge these templates with your existing Document Composition configuration files into one file. You can use tools like WinMerge or BeyondCompare to do this. 3. Check the File modus_core.exe.config If you have updated an existing Document Composition installation to the version 5.3.0, check the file modus_core.exe.config for the existence and correctness of the following content (Note Content may be missing or have been commented out). Take particular care that the crossdomain Service in the sections configsections and runtimeservices is activated in the event that the code has been commented out. The code line should look like this: <configsections> <section name="crossdomainservices" type="modussuite.runtime.crossdomainserviceconfiguration, ModusSuite.Runtime.CrossDomainService" /> </configsections> Page 11 of 28

12 <runtimeservices> <service name="crossdomain" assembly="modussuite.runtime.crossdomainservice" type="modussuite.runtime.crossdomainruntimeservice"/> </runtimeservices> Configuration for using a SSL connection: Complete both of the following steps to use a SSL connection (requires a SSL certificate): Step 1: Uncomment the following lines in the default installation - marked in red below - so that the section looks as follows: <crossdomainservices policy=""%pdcdir%clientaccesspolicy.xml"> <add baseaddress=" <add baseaddress=" <add baseaddress=" <add baseaddress=" </crossdomainservices> Step 2: Uncomment the following section in the default installation - marked in red below - and comment out the preceding section so that both sections look as follows: <!-- non SSL Variant <service name="modususerrepositoryservicebasic" behaviorconfiguration ="BasicBehaviour" > <host> <add baseaddress =" /> </host> <endpoint address ="data" binding ="basichttpbinding" bindingconfiguration ="BasicBinding" contract ="ModusSuite.Security.Types.IModusUserRepository"/> </service> --> <service name="modususerrepositoryservicebasic" behaviorconfiguration ="BasicBehaviour_SSL" > <host> Page 12 of 28

13 <add baseaddress =" /> </host> <endpoint address ="data" binding ="basichttpbinding" bindingconfiguration ="BasicBinding_SSL" contract ="ModusSuite.Security.Types.IModusUserRepository"/> </service> 4. Check the File modus_mws.exe.config Check the file modus_mws.exe.config for the existence and correctness of the following content (N.B. content may be missing or have been commented out). Configuration of MWS REST-Service and CORS Support <modusruntime> <runtimeservices> <service name="mwsrest" assembly="modussuite.runtime.mwsruntimeservice" type="modussuite.runtime.mwsruntimeservicerest"/> </runtimeservices> </modusruntime> <system.servicemodel> <services> <service name="modussuite.mws.mwsprocessservicerest" behaviorconfiguration ="RestBehaviour" > <host> <!-- configure base address provided by host --> <add baseaddress =" /> </host> <endpoint address ="mwsprocess" binding ="webhttpbinding" contract ="ModusSuite.MWS.Types.IMWSProcessServiceBasic" bindingconfiguration="" behaviorconfiguration = "WebBehavior" /> </service> </services> <behaviors> Page 13 of 28

14 <servicebehaviors> <behavior name ="RestBehaviour" > <!-- The servicemetadata behavior allows one to enable metadata (for example WSDL, Policy) publishing. This configuration enables publishing of such data over HTTP GET. --> <servicemetadata httpgetenabled="true"/> </behavior> </servicebehaviors> <endpointbehaviors> <behavior name="webbehavior"> <webhttp/> <CorsSupport/> </behavior> </endpointbehaviors> </behaviors> <extensions> <behaviorextensions> <!-- Note: type must be entered exactly as here, otherwise the ConfigurationLoader will not recognize the extension! -> Microsoft Bug!! --> <add name="corssupport" type="modussuite.runtime.corssupportbehaviorelement, ModusSuite.Runtime.Cors, Version= , Culture=neutral, PublicKeyToken=null"/> </behaviorextensions> </extensions> </system.servicemodel> Configuration for using a SSL connection (requires a SSL certificate): <!-- non SSL Variant <service name="mwsrepositoryservicebasic" behaviorconfiguration ="BasicBehaviour" > <host> <add baseaddress =" /> </host> <endpoint address ="mwsrepository" binding ="basichttpbinding" bindingconfiguration ="BasicBinding" contract ="IMWSRepositoryService"/> Page 14 of 28

15 </service> --> <!-- SSL Variant --> <service name="mwsrepositoryservicebasic" behaviorconfiguration ="BasicBehaviour_SSL" > <host> <add baseaddress =" /> </host> <endpoint address ="mwsrepository" binding ="basichttpbinding" bindingconfiguration ="BasicBinding_SSL" contract ="IMWSRepositoryService"/> </service> <!-- non SSL Variant <service name="modussuite.mws.mwsprocessservicebasic" behaviorconfiguration ="BasicBehaviour" > <host> <add baseaddress =" /> </host> <endpoint address ="mwsprocess" binding ="basichttpbinding" bindingconfiguration ="BasicBinding" contract ="ModusSuite.MWS.Types.IMWSProcessServiceBasic"/> </service> --> <!-- SSL Variant --> <service name="modussuite.mws.mwsprocessservicebasic" behaviorconfiguration ="BasicBehaviour_SSL" > <host> <add baseaddress =" /> </host> <endpoint address ="mwsprocess" binding ="basichttpbinding" bindingconfiguration ="BasicBinding_SSL" contract ="ModusSuite.MWS.Types.IMWSProcessServiceBasic"/> </service> Page 15 of 28

16 5. Replace Server Addresses Replace the server addresses with the host name of the Document Composition server in the following sections of the configuration files modus_core.exe.config and modus_mws.exe.config : appsettings services crossdomainservices Use the template versions of these files included in the WebClient installation package as a reference for replacing the names. The respective sections are marked with the placeholder [PDCServerName]. 6. Restart Services Stop and restart the Perceptive Document Composition services for the new configuration to take effect. The Document Composition Server is now ready to accept requests from the WebClient. SSL connection As of Release the WebClient can also be run using a SSL connection. This requires a SSL-Certificate. In addition to the above, the following modifications are also required: File ClientAccessPolicy.xml Add the following two lines marked in red to the file: <?xml version="1.0" encoding="utf-8"?> <access-policy> <cross-domain-access> <policy> <allow-from http-request-headers="*"> <domain uri="*"/> <domain uri=" <domain uri=" /> </allow-from> <grant-to> <resource include-subpaths="true" path="/"/> </grant-to> </policy> </cross-domain-access> </access-policy> File modus_core.exe.config 1. Add the following two lines marked in red to the file: <crossdomainservices policy=""%pdcdir%clientaccesspolicy.xml"> <add baseaddress=" <add baseaddress=" Page 16 of 28

17 <add baseaddress=" <add baseaddress=" </crossdomainservices> 2. Add the new binding configuration BasicBinding_SSL: Copy the already existing bindingconfiguration BasicBinding. Rename the new bindingconfiguration to BasicBinding_SSL. Change the security mode from None to Transport. <basichttpbinding> <binding name="basicbinding" maxbufferpoolsize=" " maxreceivedmessagesize=" " receivetimeout="infinite"> <readerquotas maxstringcontentlength=" " maxarraylength=" " /> <security mode="none" /> </binding> <binding name="basicbinding_ssl" maxbufferpoolsize=" " maxreceivedmessagesize=" " receivetimeout="infinite"> <readerquotas maxstringcontentlength=" " maxarraylength=" " /> <security mode="transport" /> </binding> </basichttpbinding> 3. Add the new behavior configuration BasicBehavior_SSL: Copy the already existing behavior configuration BasicBehavior and rename the new configuration to BasicBehavior_SSL. Change the servicemetadata-attribute httpgetenabled to httpsgetenabled. <behavior name ="BasicBehaviour" > <servicethrottling maxconcurrentcalls=" " maxconcurrentinstances=" " maxconcurrentsessions=" "/> <servicedebug includeexceptiondetailinfaults ="true"/> <servicemetadata httpgetenabled="true"/> </behavior> <behavior name ="BasicBehaviour_SSL" > <servicethrottling maxconcurrentcalls=" " maxconcurrentinstances=" " maxconcurrentsessions=" "/> <servicedebug includeexceptiondetailinfaults ="true"/> <servicemetadata httpsgetenabled="true"/> </behavior> Page 17 of 28

18 4. Modify the service configuration ModusUserRepositoryServiceBasic to allow the use of SSL: Copy the existing configuration and comment the lines out. Change the behaviorconfiguration from BasicBehavior_SSL to BasicBehavior_SSL. Inadd baseaddress change the entry http to https and 8010 to Change the bindingconfiguration to BasicBinding_SSL. <!-- non SSL Variant <service name="modususerrepositoryservicebasic" behaviorconfiguration ="BasicBehaviour" > <host> <add baseaddress =" /> </host> <endpoint address ="data" binding ="basichttpbinding" bindingconfiguration ="BasicBinding" contract ="ModusSuite.Security.Types.IModusUserRepository"/> </service> --> <!-- SSL Variant --> <service name="modususerrepositoryservicebasic" behaviorconfiguration ="BasicBehaviour_SSL" > <host> <add baseaddress =" /> </host> <endpoint address ="data" binding ="basichttpbinding" bindingconfiguration ="BasicBinding_SSL" contract ="ModusSuite.Security.Types.IModusUserRepository"/> </service> File modus_mws.exe.config 1. Add the new binding configuration BasicBinding_SSL: Copy the already existing bindingconfiguration BasicBinding. Rename the new bindingconfiguration to BasicBinding_SSL. Change the security mode from None to Transport. <basichttpbinding> <binding name="basicbinding" Page 18 of 28

19 maxbufferpoolsize=" " maxreceivedmessagesize=" " receivetimeout="infinite"> <readerquotas maxstringcontentlength=" " maxarraylength=" " /> <security mode="none" /> </binding> <binding name="basicbinding_ssl" maxbufferpoolsize=" " maxreceivedmessagesize=" " receivetimeout="infinite"> <readerquotas maxstringcontentlength=" " maxarraylength=" " /> <security mode="transport" /> </binding> </basichttpbinding> 2. Add the new behavior configuration BasicBehavior_SSL: Copy the already existing behavior configuration BasicBehavior and rename the new configuration to BasicBehavior_SSL. Change the servicemetadata-attribute httpgetenabled to httpsgetenabled. <behavior name ="BasicBehaviour" > <servicethrottling maxconcurrentcalls=" " maxconcurrentinstances=" " maxconcurrentsessions=" "/> <servicedebug includeexceptiondetailinfaults ="true"/> <servicemetadata httpgetenabled="true"/> </behavior> <behavior name ="BasicBehaviour_SSL" > <servicethrottling maxconcurrentcalls=" " maxconcurrentinstances=" " maxconcurrentsessions=" "/> <servicedebug includeexceptiondetailinfaults ="true"/> <servicemetadata httpsgetenabled="true"/> </behavior> 3. Modify the service configuration MwsRepositoryServiceBasic to allow the use of SSL: Copy the existing configuration and comment the lines out. Change the behaviorconfiguration to BasicBehaviour_SSL. In add baseaddress change the entry http to https and 8010 to Change the bindingconfiguration from BasicBinding to BasicBinding_SSL. <!-- non SSL Variant <service name="mwsrepositoryservicebasic" behaviorconfiguration ="BasicBehaviour" > <host> Page 19 of 28

20 <add baseaddress =" /> </host> <endpoint address ="mwsrepository" binding ="basichttpbinding" bindingconfiguration ="BasicBinding" contract ="IMWSRepositoryService"/> </service> --> <!-- SSL Variant --> <service name="mwsrepositoryservicebasic" behaviorconfiguration ="BasicBehaviour_SSL" > <host> <add baseaddress =" /> </host> <endpoint address ="mwsrepository" binding ="basichttpbinding" bindingconfiguration ="BasicBinding_SSL" contract ="IMWSRepositoryService"/> </service> 4. Modify the service configuration ModusSuite.MWS.MWSProcessServiceBasic to allow the use of SSL: Copy the existing configuration and comment the lines out. Change the behaviorconfiguration to BasicBehaviour_SSL. In add baseaddress change the entry http to https and 8010 to Change the bindingconfiguration from BasicBinding to BasicBinding_SSL. <!-- non SSL Variant <service name="modussuite.mws.mwsprocessservicebasic" behaviorconfiguration ="BasicBehaviour" > <host> <add baseaddress =" /> </host> <endpoint address ="mwsprocess" binding ="basichttpbinding" bindingconfiguration ="BasicBinding" contract ="ModusSuite.MWS.Types.IMWSProcessServiceBasic"/> </service> --> Page 20 of 28

21 <!-- SSL Variant --> <service name="modussuite.mws.mwsprocessservicebasic" behaviorconfiguration ="BasicBehaviour_SSL" > <host> <add baseaddress =" /> </host> <endpoint address ="mwsprocess" binding ="basichttpbinding" bindingconfiguration ="BasicBinding_SSL" contract ="ModusSuite.MWS.Types.IMWSProcessServiceBasic"/> </service> File PDC.WebClient.xml In the following appsettings change the entries http to https, 8011 to 8111 and 8010 to 8110: <!-- non SSL Variant <add key="mwsprocessservicebasic" value=" /> <add key="mwsrepositoryservicebasic" value=" /> <add key="murservicebasic" value=" /> --> <!-- SSL Variant --> <add key="mwsprocessservicebasic" value=" /> <add key="mwsrepositoryservicebasic" value=" /> <add key="murservicebasic" value=" /> Hint After activating or deactivating a SSL connection you must delete the browser history and restart the browser. Setting Up the WebClient on a Client Computer Client Computer Requirements Microsoft Silverlight 5 Runtime Environment If the Silverlight plugin is missing when the WebClient is first launched, the system will prompt a download link for the plugin. Alternatively, the Silverlight 5 runtime environment can be installed and rolled out to the client computer in preparation of first use. Microsoft provides all the necessary resources. Page 21 of 28

22 to download the required installation package..net Framework 3.5SP1 If you wish to use optional PDC.WebClientLauncher, you will need to have.net Framework SP1 installed. Microsoft Word To use the full functionality of the WebClient Microsoft Word 2007 or Microsoft Word 2010 must be installed on the client computer. Web browser The following browser are supported: Internet Explorer 8 and 9 Internet Explorer 10 on Windows 7 Firefox until version 17 Extended Support Release First Launch on a Client Computer Complete the following steps to launch the WebClient: 1. Start a Web browser (Internet Explorer or Firefox). 2. Open the preconfigured WebClient Web page: 3. Enter your user name and password in the log in dialog box. Choose the User Language The WebClient usually selects the language version according to the language of the operating system it is launched from. The following languages are available: German English (US) Dutch French Spanish Italian Portuguese (BR) Running in in-browser mode If the WebClient is to be run in a language other than that of the operating system itself,complete the following steps to do this: 1. Open the file PDC.WebClient.htmlin the web folder. Use an editor that supports UTF-16 to do this, for example Notepad++. Page 22 of 28

23 2. Find the following lines: <param name="culture" value="{language-isocode}" /> <param name="uiculture" value="{language-isocode}" /> 3. Replace the placeholder {LANGUAGE-ISOCODE} with one of the following codes: de-de for German en-us for English (US) nl-nl for Dutch fr-fr for French es-es for Spanish it-it for Italian pt-br for Portuguese (BR) Running in out-of-browser mode See The PDC.WebClientLauncher - Set Language Version. Elevated Permissions Elevated permissions are required in order to use the full functionality of Microsoft Office interaction. The WebClient must be run as a Trusted Application. This is possible as Out-of-Browser and In-Browser. Elevated Permissions in WebClient run in Out-of-Browser mode To be run Out-of-Browser the WebClient has to be installed locally on the client computer. Complete the following steps to do this: 1. Start a Web browser. 2. Open the preconfigured WebClient Web page ( 3. Move the mouse cursor over the Client user interface. 4. Open the context menu with the right mouse button and select the option Install Document Composition WebClient on this Computer. 5. Confirm the following pop up by pressing the OK button. To be run Out-of-Browser the WebClient has to be installed locally on the client computer. A menu item called Document Composition WebClient has been created in the Start menu. 6. Use this menu item to start the WebClient in Out-of-Browser mode. Double-clicking on documents generated in the WebClient with the status created now opens them in Word. Elevated Permissions in WebClient run in In-Browser mode Silverlight 5 allows elevated permissions to be used directly in a browser. Installation Page 23 of 28

24 Run the installation package PDC.WebClientEnableFullTrust.msi. The MSI package installs the required certificate and makes all registry entries necessary. It does not require user input and can be run in both 32-bit and 643-bit Windows environments. Alternative: Manual Configuration If you have problems with the MSI, manual configuration is possible using the resources provided in the zip package. To run a Trusted Application in a browser, you must first of all install the certificate PDC.WebClient.cer provided with the installation set contained in the zip file and then configure the registry to run a Trusted Application in a browser. Complete the following steps to do this: 1. Double click on the file PDC.WebClient.cer. 2. Click on the button Install Certificate in the following dialog. The certificate import wizard is then started. 3. Click on the button Continue. 4. Select the option Save all certificates to the following store in the following dialog. 5. Click on the button Browse next to the field certificate store. 6. Select the certificate store Trusted Publisher. In some cases you may also need to save the certificate in the certificate store Trusted Root Certification Authorities. For more information, see / and / and 7. Confirm the following three dialog boxes with Continue, Finish and OK to complete the installation of the certificate. 8. Import one of the two registry import files provided: Silverlight_AppTrust_x32.reg for 32-Bit Systems Silverlight_AppTrust_x64.reg for 64-Bit Systems. Importing the registry files will add the following settings to the registry: In HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Silverlight (32bit) or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Silverlight (64bit) the Registry DWORD (32 bit) - AllowElevatedTrustAppsInBrowser and the value changed to 0x (1) where (1-> enabled, 0-> disabled). Additional optional keys can be configured if required: AllowLaunchOfElevatedTrustApps: enable/disable launching of elevated trust applications. Page 24 of 28

25 AllowInstallOfElevatedTrustApps: enable/disable installing of elevated trust applications. These settings can also be deployed by a central software distribution or configuration management, for example via a Group Policy set by a central administrator. Note for Internet Explorer If after having completed all the above, you still do not have the elevated permissions required, check whether the Internet Explorer is being run in protected mode and, if so, deactivate it or run Internet Explorer as an administrator. The PDC.WebClientLauncher The PDC.WebClientLauncher can optionally be used to launch the WebClient in out-of-browser mode. The Launcher allows you to pass specific start parameters to the WebClient. Installation The file PDC.WebClientLauncher.exe is contained in the installation package (PDC.WebClient.zip). Copy the file to a local folder that the user also has access to. Launch Syntax PDC.WebClientLauncher.exe -URL:"URL" -APPID:"AppId" [-INFO] {Client- Parameter} You will need either the URL or the APPID to start the WebClient via the PDC.WebClientLauncher. You can detect the APPID by using the parameter -INFO: PDC.WebClientLauncher.exe -INFO This shows information about all Silverlight applications currently installed. PDC.WebClientLauncher Version PDC Client - Copyright 2013 Lexmark International Technology S.A. Information about installed Silverlight applications: Name: PDC WebClient AppID: megatron Title: PDC WebClient Description: A PDC WebClient on your desktop; at home, in the office or on the road. OriginalSourceUri: LaunchPath: C:\Documents and Settings\tester\Local Settings\Appdata\Microsoft\Silverlight\OutOfBrowser\ megatron\index. html Page 25 of 28

26 User Documentation You can find more information on starting the PDC.WebClientLauncher in the WebClient user documentation. Choose the User Language If the WebClient is to be run in a language other than that of the operating system itself,complete the following steps to do this: 1. Detect the LaunchPath by starting the PDC.WebClientLauncher with the parameter -INFO as described in the section Launch above. In the example above, the directory LaunchPath: C:\Documents and Settings\tester\Local Settings\Appdata\Microsoft\Silverlight\OutOfBrowser\ megatron\ 2. Open the file index.html in this directory. Use an editor that supports UTF-16 to do this, for example Notepad Find the following lines: <param name="culture" value="{language-isocode}" /> <param name="uiculture" value="{language-isocode}" /> 4. Replace the placeholder {LANGUAGE-ISOCODE} with one of the following codes: de-de for German en-us for English (US) nl-nl for Dutch fr-fr for French es-es for Spanish it-it for Italian pt-br for Portuguese (BR) Private / Protected Mode in a Web Browser The use of private mode in a browser is not recommended as a number of WebClient functions are not available in private mode. Known Problems The WebClient does not start in Firefox when the parameter initparams contains an empty value. If the parameter initparms is left empty in the start document (PDC.WebClient.html), the user is prompted to install Silverlight. If the user follows the instruction, a message appears stating that Silverlight is already installed, but the application is not loaded. This problem has been passed on to Microsoft (Error Id: ). Page 26 of 28

27 WebClient Version 5.1 is not updated in Out-of-Browser mode. After calling the OOB WebClient, then user is prompted to install a new Silverlight version and then to restart the Out-of-Browser application. After installing the update and restarting the Client the above message is displayed again the application was not updated. The problem has been solved with Silverlight 5 Build The WebClient cannot be closed in Firefox using the menu item Close Client. This problem has been passed on to Mozilla. Complete the following steps to resolve the problem: 1. Start Firefox. Note Firefox up to Version 17 is supported. 2. Enter about:config in the browser address bar. 3. Acknowledge the warning dialog box by clicking on the button I'll be careful, I promise! A table of configuration elements is now displayed. 4. Set the key dom.allow_scripts_to_close_windows to true. A Document is not displayed in Word. When using the Internet Explorer, a document may not be displayed after successfully being download. Either you have to disable the protected mode of the Internet Explorer (not recommended) or follow these steps to add the used website to the list of trusted sites: 1. In the Internet Explorer, select Internet options from the Tools menu. 2. Click on the Security tab. 3. Click on the Icon Trusted Sites. 4. Click on the button Sites and add the Web Client website to the list of trusted sites. Page 27 of 28

28 Index Client Computer Client Computer Requirements Create a Virtual Directory in IIS Elevated Permissions First Launch General Information... 4 IIS... 5, 10 MIME Types... 5 Installation Requirements... 5 ModusWebClientLauncher Preparatory Steps... 8 Private Mode Problems Protected Mode Required Files... 6 Set Language Version System Requirements... 5 Target Audience... 4 Virtual Directory Web Browser Windows Server... 5 Page 28 of 28