Enterprise Advanced Configuration

Transcription

1 Enterprise Advanced Configuration Winfried de Vries May 13, 2009

2 Enterprise Advanced Configuration Performance Hardware set-up Issues Security Trouble-shooting

3 Enterprise System Components Database Application Server Clients: InDesign, InCopy, Content Station etc. FileStore

4 Enterprise System Components Application Server nts: InDesign, Memory++ opy, Content Station etc.

5 Enterprise System Components Database Application Server Memory++ Disk IO++

6 Database THE FAST TRACK TO ONLINE Enterprise System Components Application Server FileStore Memory++ Disk IO++

7 Enterprise System Components Database Application Server Clients: InDesign, InCopy, Content Station etc. FileStore

8 Performance Issues How is your system performing

9 Performance Issues How is your system performing

10 Performance Issues How is your system performing or

11 Performance Issues How is your system performing or

12 Why can there be performace issues?

13 Why can there be performace issues? Woodwing has got no control over the setup of the components

14 Why can there be performace issues? Woodwing has got no control over the setup of the components Because the hardware, OS and database choices are a partner/customer decision.

15 Why can there be performace issues? Woodwing has got no control over the setup of the components Because the hardware, OS and database choices are a partner/customer decision. Customizations and interfaces that are not optimized.

16 Measuring performace, how?

17 Measuring performace, how? specify the ʻscopeʼ of the measurement: limit the scope to what can be measured accurately.

18 Measuring performace, how? specify the ʻscopeʼ of the measurement: limit the scope to what can be measured accurately. create a reproducible scenario and prerequisites. Make a copy of the used files for future comparisons.

19 Measuring performace, how? specify the ʻscopeʼ of the measurement: limit the scope to what can be measured accurately. create a reproducible scenario and prerequisites. Make a copy of the used files for future comparisons. Test on a ʻcleanʼ system: switch off additional server-plugins and client side scripting.

20 Measuring performace keep in mind that writing down logfiles has got influence on performance. look ʻtop-downʼ, first total time, then start narrowing down. User functions Enterprise commands, Database actions, Data transfer, Client Performance

21 Performance logging Switch on debugging on server Configserver.php // // Debugging - Low-level logging of SQL, SOAP details etc. // define ('DEBUGLEVEL', 'INFO'); // NONE, ERROR, WARN, INFO, DEBUG define ('OUTPUTDIRECTORY', '/log/'); // including '/', e.g. "c:/enterpriselog/output/" define ('PROFILELEVEL', 1); // [0,5] 0: no profiling, 5: most detailed define ('LOGSQL', false); // log the SQL, requires DEBUGLEVEL DEBUG or INFO For performance logging, use INFO For functional debugging, use DEBUG

22 Performance logging Set profilelevel to 5 to get maximum server info peformanceprofiler.dat sce_profile_mysq.htm

23 Database performance pitfall Table scans, caused by: Queries on columns that have no index Mostly in interfaces and customizations Use database monitoring tools: phpmyadmin:

24 Security

25 Why security?

26 Why security? Information abuse

27 Why security? Information abuse Production disturbance

28 Why security? Information abuse Production disturbance User mistakes

29 Why security? Information abuse Production disturbance User mistakes Hardware failure

30 Secure Enterprise installation

31 Secure Enterprise installation Change password of default WoodWing user

32 Secure Enterprise installation Change password of default WoodWing user SSL (HTTPS)

33 Secure Enterprise installation Change password of default WoodWing user SSL (HTTPS) Separate database user for woodwing

34 Secure Enterprise installation Change password of default WoodWing user SSL (HTTPS) Separate database user for woodwing File access (config.php, directories,...)

35 Secure Enterprise set-up

36 Secure Enterprise set-up Full / Limited Administrators

37 Secure Enterprise set-up Full / Limited Administrators Workflow

38 Secure Enterprise set-up Full / Limited Administrators Workflow Password rules

39 Secure Enterprise set-up Full / Limited Administrators Workflow Password rules config/configserver.php

40 Secure Enterprise set-up Full / Limited Administrators Workflow Password rules config/configserver.php Customize with a plug-in

41 Enterprise backup Standard version control Settings in config/configserver.php Workflow Status property Trash Can Database / FileStore / AS backup

42 Troubleshooting

43 Troubleshooting in Enterprise

44 Troubleshooting in Enterprise Why: To get detailed information about a problem in the system.

45 Troubleshooting in Enterprise Why: To get detailed information about a problem in the system. With as goal: To solve the problem yourself! To send an issue report to woodwing

46 Approach

47 Approach Make sure the issue is reproducible:

48 Approach Make sure the issue is reproducible: Write down/collect prerequisites (if any). upload attached image ʻproblem1.jpgʻ to Enterprise

49 Approach Make sure the issue is reproducible: Write down/collect prerequisites (if any). upload attached image ʻproblem1.jpgʻ to Enterprise Write a scenario.

50 Approach Make sure the issue is reproducible: Write down/collect prerequisites (if any). upload attached image ʻproblem1.jpgʻ to Enterprise Write a scenario. 1. from InDesign, logon as user ʻxxxʼ on server ʻmyserverʼ

51 Approach Make sure the issue is reproducible: Write down/collect prerequisites (if any). upload attached image ʻproblem1.jpgʻ to Enterprise Write a scenario. 1. from InDesign, logon as user ʻxxxʼ on server ʻmyserverʼ 2. create a layout and save-version with name ʻlayout1ʼ

52 Approach Make sure the issue is reproducible: Write down/collect prerequisites (if any). upload attached image ʻproblem1.jpgʻ to Enterprise Write a scenario. 1. from InDesign, logon as user ʻxxxʼ on server ʻmyserverʼ 2. create a layout and save-version with name ʻlayout1ʼ 3. place uploaded image with name ʻproblem1.jpgʼ on layout ʻlayout1ʼ

53 Approach Make sure the issue is reproducible: Write down/collect prerequisites (if any). upload attached image ʻproblem1.jpgʻ to Enterprise Write a scenario. 1. from InDesign, logon as user ʻxxxʼ on server ʻmyserverʼ 2. create a layout and save-version with name ʻlayout1ʼ 3. place uploaded image with name ʻproblem1.jpgʼ on layout ʻlayout1ʼ 4. From SCE-panel, rename ʻlayout1ʼ to ʻlayout123ʼ Result: Error back from server ʻUnable to renameʼ On client, switch of all client side scripting.

54 Test on a clean system To create a clean system: Remove or switch of all non-standard server plugins. test without any other users, or : create a separate Application Server with debug on, using the same database and filestore create a complete copy of the system as test system. Production Debug Application Server Application Server

55 Is the scenario still valid? Replay the scenario on the clean system. Is the issue still there? No? -> Switch on customizations one-by-one until problem appears again. Yes? -> Switch on logging and run scenario

56 Switch on logging Server side: configserver.php Text // // Debugging - Low-level logging of SQL, SOAP details etc. // define ('DEBUGLEVEL', 'DEBUG'); // NONE, ERROR, WARN, INFO, DEBUG define ('OUTPUTDIRECTORY', '/log/'); // including '/', e.g. "c:/enterpriselog/output/" define ('PROFILELEVEL', 1); // [0,5] 0: no profiling, 5: most detailed define ('LOGSQL', false); // log the SQL, requires DEBUGLEVEL DEBUG or INFO Client side wwsettings.xml <SCEnt:LogFile RequestBuffer ="Macintosh HD:ClientLog:" ResponseBuffer="Macintosh HD:ClientLog:" SOAPResponse ="Macintosh HD:ClientLog:" SOAPRequest ="Macintosh HD:ClientLog:" Advanced ="true"/>

57

58 Send all info to woodwing support:

59 Send all info to woodwing support: System information. OS, PHP version, database type

60 Send all info to woodwing support: System information. OS, PHP version, database type Prerequisites & Scenario

61 Send all info to woodwing support: System information. OS, PHP version, database type Prerequisites & Scenario Logfiles

62 Send all info to woodwing support: System information. OS, PHP version, database type Prerequisites & Scenario Logfiles Severity of the issue (reseller guide)

63 Send all info to woodwing support: System information. OS, PHP version, database type Prerequisites & Scenario Logfiles Severity of the issue (reseller guide)

64 Questions?

65 Questions? Thank you for your attention