REV. NO. CHANGES DATE. 000 New Document 5 May 2014

Size: px

Start display at page:

Download "REV. NO. CHANGES DATE. 000 New Document 5 May 2014"

Terence Reed
6 years ago
Views:

2 DOCUMENT HISTORY REV. NO. CHANGES DATE 000 New Document 5 May 2014 PROPRIETARY INFORMATION The information contained in this document is the property of Global Vision, Inc. Information contained in this document is intended for the internal usage of clients of Global Vision, Inc. systems only. Re-production or reprints complete or partial for other purpose is illegal. 2014, Global Vision Inc., All Rights Reserved. Page 2 of 21 Published 5 May 2014

3 TABLE OF CONTENTS 1. PURPOSE SYSTEM REQUIREMENTS HARDWARE MINIMUM REQUIREMENTS CLIENT SIDE SOFTWARE MINIMUM REQUIREMENTS CLIENT SIDE HARDWARE MINIMUM REQUIREMENTS SERVER SIDE SOFTWARE MINIMUM REQUIREMENTS SERVER SIDE SERVER SIDE INSTALLATION APACHE TOMCAT INSTALLATION KODAK WORKING DIRECTORY GLOBAL SETTINGS WINDOW SERVER FIREWALL CONFIGURATION CLIENT SIDE INSTALLATION DOCU-PROOF ENTERPRISE KODAK UPLOADER Installation XML Configuration WORKFLOW Page 3 of 21 Published 5 May 2014

4 1. PURPOSE The purpose of this document is to outline the installation of the components needed for the integration of Docu-Proof Enterprise (DCPE) with the Kodak Artwork Management System (AMS). The Kodak AMS is a web-based solution for managing brand assets and content creation. DCPE is a client/server based document inspection tool used to compare one electronic document to another to verify that the content matches between the two documents. 2. SYSTEM REQUIREMENTS 1.1 HARDWARE MINIMUM REQUIREMENTS CLIENT SIDE SOFTWARE PROCESSOR MEMORY HARD DISK SPACE DATABASE SPACE SYNERGY 32 bit or 64 bit 4.0 GB RAM 200 MB 20 GB SERVER 2.0 GHZ DUAL CORE SYNERGY 32 bit or 64 bit 2.0 GB RAM 200 MB N/A CLIENT 2.0 GHZ DUAL CORE DOCU- PROOF ENTERPRISE 32 bit or 64 bit 2.0 GHZ DUAL CORE 4.0 GB RAM 20.0 GB N/A 1.2 SOFTWARE MINIMUM REQUIREMENTS CLIENT SIDE SOFTWARE OPERATING SYSTEMS DATABASE OTHER SOFTWARE SYNERGY WINDOWS 7 WINDOWS SERVER 2008 WINDOWS SERVER 2008 R2 MYSQL V.5.0 / 5.5 MYSQL 2008 ORACLE 11g Microsoft.NET Framework 4.0 or later must be installed before Proceeding with this install. DOCU-PROOF ENTERPRISE WINDOWS 7 WINDOWS SERVER 2008 WINDOWS SERVER 2008 R2 Microsoft C x86 Redistributable file must be installed before proceeding with this install. N/A MS-WORD 2007 / 2010 / 2013 ADOBE READER CLIENT APPLICATION Page 4 of 21 Published 5 May 2014

5 1.3 HARDWARE MINIMUM REQUIREMENTS SERVER SIDE PROCESSOR MEMORY HARD DISK SPACE DATABASE SPACE 64 bit 2.0 GHZ 6 CORE 16 GB RAM 200 GB 50 GB 1.4 SOFTWARE MINIMUM REQUIREMENTS SERVER SIDE SOFTWARE OPERATING SYSTEMS DATABASE OTHER SOFTWARE KodakD2L Connector WINDOWS SERVER 2008 R2 (64 bit) n/a Apache Tomcat 6.0 Java Runtime Environment (JRE) 1.7 Page 5 of 21 Published 5 May 2014

6 3. SERVER SIDE INSTALLATION The Kodak Design2Launch Connector installation files are stored in G:\Product Development\Software Control\TEST EXEs\Kodak Design2Launch Connector\1.0.0\Web components. Note: The Java SE Development Kit 7 must be installed prior to executing the steps below.. The installation file jdk-7u51-windows-x64.exe is found at G:\Product Development\Software Control\Released Software\Proofware\Proofware Install Folder\Installers\JAVA. Take note of the java installation path. 3.1 APACHE TOMCAT INSTALLATION The Apache Tomcat provides a Java HTTP web server environment for the Kodak D2L Connector Java code to run in. The installation executable is stored in G:\Product Development\Software Control\Released Software\Proofware\Proofware Install Folder\Installers\ApacheTomcat. Run all installations as Administrator. 1. Double-click on the apache-tomcat exe to launch it. 2. Click Next. Page 6 of 21 Published 5 May 2014

7 3. Click I Agree. 4. Click Next. Page 7 of 21 Published 5 May 2014

8 5. Enter the following configuration parameters: o Server Shutdown Port = 8006 o HTTP/1.1 Connector Port = 80 o AJP.1.3 Connector Port = 8008 o Windows Service Name = <Enter a Service Name> For example: KodakD2LConnector Click Next. Page 8 of 21 Published 5 May 2014

$For example :C:\Program Files\Java\jre7 Click Next. 7.$ Enter the Tomcat installation directory as the destination folder.

9 6. Enter the path to where Java JRE resides on the server. For example :C:\Program Files\Java\jre7 Click Next. 7. Enter the Tomcat installation directory as the destination folder. There is no pre-determined pathway. This is determined by the administrator. You can use the Browse button to navigate to the selected directory. Then click Install. Page 9 of 21 Published 5 May 2014

10 8. Uncheck Show Readme. Click Finish. 9. Select Properties for the Kodak D2L Connector service created in step 5 above from the Services panel in the Server Manager Console. 10. Change the Startup Type from Manual to Automatic. Page 10 of 21 Published 5 May 2014

3.2 KODAK WORKING DIRECTORY o Copy the folder KodakD2L from the Installer directory into the webapps folder in the Tomcat installation directory as

11 3.2 KODAK WORKING DIRECTORY o Copy the folder KodakD2L from the Installer directory into the webapps folder in the Tomcat installation directory as determined during the Apache Tomcat installation in step 7 in Section 3.1. Example of KodakD2L working directory Page 11 of 21 Published 5 May 2014

12 3.3 GLOBAL SETTINGS o Configure the yellow highlighted items below in the web.xml file located in the KodakD2L\WEB- INF folder as follows: <?xml version="1.0" encoding="utf-8"?> - <web-app> <display-name>abbott</display-name> - <context-param> <param-name>serverurl</param-name> <param-value> </context-param> - <context-param> <param-name>clientsidepath</param-name> <param-value>c:\\abbottd2l\\</param-value> </context-param> - <context-param> <param-name>clientsideexepath</param-name> <param-value>c:\\dev\\src\\dcp\\bin\\gvedocuproof2ud.exe</param-value> </context-param> - <context-param> <param-name>serversideartr_exe_path</param-name> <param-value>c:\\program Files\\QCanywhere\\QCartwork\\TVSCS.exe</paramvalue> </context-param> - <context-param> <param-name>serversidepath</param-name> <paramvalue>c:\\qcanywhere\\webserver\\webapps\\kodakd2l\\files\\</paramvalue> </context-param> - <context-param> <param-name>webservice</param-name> <param-value> </context-param> - <context-param> <param-name>useproxy</param-name> <param-value>no</param-value> </context-param> - <context-param> <param-name>proxy</param-name> <param-value> </context-param> + <servlet> - <session-config> <session-timeout>45</session-timeout> </session-config> - <welcome-file-list> <welcome-file>applet.html</welcome-file> <welcome-file>applet.htm</welcome-file> <welcome-file>applet.jsp</welcome-file> Page 12 of 21 Published 5 May 2014

13 <welcome-file>applet.html</welcome-file> <welcome-file>applet.htm</welcome-file> <welcome-file>applet.jsp</welcome-file> </welcome-file-list> </web-app> Param-name ServerURL ServerSidePath WebService Proxy Param-value Replace with the IP address or name of the server Replace with the location of the Files directory in the KodakD2L folder that was copied into the Tomcat folder. The path must point to the Tomcat installation directory as determined during the Apache Tomcat installation in step 7 in Section 3.1 followed by \\webapps \\KodakD2L\\Files Replace with the correct location of the Kodak web service Replace with the correct proxy information 3.4 WINDOW SERVER FIREWALL CONFIGURATION Configure Windows Server Firewall to open Port Launch Control Panel and select Windows Firewall 2. Click Advanced Settings 3. Click Inbound Rules and select New Rule 4. Select Port and click Next 5. Enter 80 in the Specific local posts field and click Next 6. Ensure that Allow the connection is selected and click Next 7. Ensure that Domain, Private and Public are checked and click Next 8. Enter QCanywhere Port in the Name field and click Finish. o Restart the Tomcat service created in step 5, Section 3.1 from the Services panel in the Server Manager Console for the changes to take effect. Page 13 of 21 Published 5 May 2014

$Installation executables are stored in G:\Product Development\Software Control\Released Software\Docu-Proof Enterprise\Current. Follow the steps outlined in the DCPE Installation Guide.$

14 4. CLIENT SIDE INSTALLATION 4.1 DOCU-PROOF ENTERPRISE Install the latest version of Global Vision Unified Installer.exe. Installation executables are stored in G:\Product Development\Software Control\Released Software\Docu-Proof Enterprise\Current. Follow the steps outlined in the DCPE Installation Guide. DCPE must be installed prior to executing the steps below. 4.2 KODAK UPLOADER Installation The Kodak Uploader is a utility that enables communication between Kodak D2L and DCPE. It enables files in Kodak D2L to be launched into DCPE for comparison and the upload of Docu-Proof reports from DCPE back into Kodak D2L. 1. Double-click Setup.msi to install. 2. Click Next. 3. Select the I accept the terms in the License Agreement checkbox and click Next. Page 14 of 21 Published 5 May 2014

15 4. Click Next. Note: The path as shown above must appear. 5. Click Install. Page 15 of 21 Published 5 May 2014

6. Click Finish. 4.2.2 XML Configuration Specific parameters in the <DocumentManagementSystem> node of the <docuproof.

The Kodak Uploader installer will modify these parameters automatically at the time of installation.

16 6. Click Finish XML Configuration Specific parameters in the <DocumentManagementSystem> node of the <docuproof.xml> file have to be configured in order to allow the upload of reports from DCPE back into Kodak D2L. The Kodak Uploader installer will modify these parameters automatically at the time of installation. The modifications that are made to the <docuproof.xml> are shown below. Original <docuproof.xml> Modified <docuproof.xml> Page 16 of 21 Published 5 May 2014

5. WORKFLOW 1. Enter the following web address in a web browser: https://ppls-integration.d2ls.kodak.com/d2l/faces/login.jsp 2.

Password: Gve12345 [Case sensitive] Note: Click Commandeer to take over an active session, if already existed. 3.

17 5. WORKFLOW 1. Enter the following web address in a web browser: 2. Log in using the following information: a. User ID: jhou b. Password: Gve12345 [Case sensitive] Note: Click Commandeer to take over an active session, if already existed. 3. Select All Tasks from the Task List dropdown menu. 4. Type proof in the Task Name textbox in the Filter Results panel. Tasks with proof in the task name will be filtered and dsiplayed in the All Tasks panel. Page 17 of 21 Published 5 May 2014

Click on one of the Proofread Artwork links.

18 5. Look for any task named Proofread Artwork with an Active status. Note: Ignore task names starting with SRS. 6. Click on one of the Proofread Artwork links. The Main Page panel for the selected task expands. Note: If Main Page panel does not expand, click Hold Task Open. Page 18 of 21 Published 5 May 2014

Select a Revision file by clicking on the checkmark beside the file then click Submit. The D2L download dialog window opens. DCPE launches.

19 7. Scroll down to the Files subsection and select 2 files for comparison. 8. Select Asset - Launch in Docu-Proof from the Batch Action drop down menu found in the Files subsection. 9. Click Apply. 10. Select a Revision file by clicking on the checkmark beside the file then click Submit. The D2L download dialog window opens. DCPE launches. The login dialog box displays. Note: A Java message box Do you want to run this application? will appear when the application is used for the first time. Select the Do not show this again for apps from the publisher and location above checkbox and click Run. Page 19 of 21 Published 5 May 2014

11. Enter a valid DCPE user name and password.

The file categorized as a revision will load in the

Start a comparison and generate a report.

Click on the Kodak icon at the bottom left of the report

20 11. Enter a valid DCPE user name and password. The files are loaded in to DCPE. The file categorized as a revision will load in the revision panel. 12. Start a comparison and generate a report. Report is generated. 13. Click on the Kodak icon at the bottom left of the report panel. A Kodak Connector window launches. 14. Add a description in the description box: gvetest, then click Ok. 15. Click OK on the success window. Page 20 of 21 Published 5 May 2014

16. Exit DCPE by selecting Exit from the File drop down menu. 17. Go back to the Kodak Design2Launch webpage and Refresh/Reload the page. Proofread Artwork Saved window launches. 18. Click Close.

21 16. Exit DCPE by selecting Exit from the File drop down menu. 17. Go back to the Kodak Design2Launch webpage and Refresh/Reload the page. Proofread Artwork Saved window launches. 18. Click Close. Note: If Main Page panel does not expand, click Hold Task Open. 19. Check that the report is added to the Files subsection. Note: Document Description should match the description typed in the Kodak Connector in step 14. Page 21 of 21 Published 5 May 2014

DOCUMENT HISTORY REV. NO. CHANGES DATE. 000 New Document 30 Mar Document Revision:

DOCUMENT HISTORY REV. NO. CHANGES DATE. 000 New Document 30 Mar Document Revision: DOCUMENT HISTORY DOCU-PROOF ENTERPRISE INSTALLATION GUIDE REV. NO. CHANGES DATE 000 New Document 30 Mar. 2010 001 Document Revision: 23 Jun. 2010 Added database support for MS SQL Server and ORACLE. 002